Newer messages are at the top
Previous 5 messages
Posted by: Alberto D'Amico
Date posted: Thu Jan 11 7:00:21 US/Eastern 2001
Subject: Duty cycle and calendar hours
Let's suppose we have a product,
-> whose commercial life is 5 years (so 43600 calendar hours).
-> It is plugged for 5 years (so the high voltage part of its Power supply unit works for 5 years with no interruption).
-> It is on (in std-by mode, electronic board on) for -let's say- 2000 hrs every year (so 10000 hrs in its life)
-> It's mechanical part's life have to be 60000 cycles (during the 5 years)
-> If a single cycle lasts 60 seconds then, in the 5 years, there are 1000 fully operational hrs during its life.
In such a situation,
how do I set the duty cycles for the different modules of the product?
how can I read the failure rate coming out from Prism?
Since it is in calendar hours, is it correct to multiply it for the operational/calendar ratio (43600/1000 = 43.6, in our example)?
A last question (sorry to bother you), how the duty cycles and usage profiles are taken into account if they are different within assemblies of the same system, and their conditions are different from the default ones for the system?
Posted by: Curt Smith
Date posted: Tue Jan 9 12:07:05 US/Eastern 2001
Subject: Capability Maturity Model Integration
As you may know this is an effort to integrate the Software Engineering Institute's Software Capability Maturity Model (maturity used by PRISM) with the Electronic Industries Association's System Engineering Capability Model (Interim Standard 731). Do you plan to update PRISM to use the CMMI software maturity level? Secondly, do you plan to update PRISM to use the CMMI system engineering maturity level in lieu of some or all of the Design and System Management process assessments.
Posted by: Leroy Meyers
Date posted: Tue Nov 21 14:52:21 US/Eastern 2000
Subject: PRISM Acceptance
Now that PRISM as been available for a while, how well has it been accepted in industry internationally as a replacement for 217?
Posted by: Tammy T Sehn
Date posted: Tue Nov 7 11:37:34 US/Eastern 2000
Subject: PRISM 1.2 Installation Notes
PRISM 1.2 has been released! Thank you to all the users who have been very helpful in making PRISM better.
Most importantly are some installation notes for our upgrading users: If at any time during the installation you receive a message indicating that a file should be overwritten and cannot be, please select the ignore option and procede with the installation. No harm will come from doing this. Secondly, if after you have installed PRISM and you receive an message regarding ODBC, please open the Utilities folder on your cd-rom and run the file named mdac_typ.exe. This will install the 2.5 upgrade from Microsoft of their MDAC components. Please feel free to contact me if you should have any questions or concerns regarding the installation of PRISM.
Posted by: Dave Ellis
Organization:Ellis Quality Engineering Services
Date posted: Thu Oct 26 19:12:59 US/Eastern 2000
Subject: System Tree vs Tree Level Report
I have a medium sized system that has a tree structure of level 1 is the system, level 2 has two assys, level 3 has several assys and so on down to level 5 with individual components. If I compare the tree structure on the left of the main screen to the tree structure report - some items are not shown at the correct level on the report - i.e. one level 3 item is shown as a level 4 item. Will this affect the prediction results or is it a bug in the report generator?
Next 5 messages
| 1...5 | 6...10 | 11...15 | 16...20 | 21...25 | 26...30 | 31...35 | 36...40 | 41...45 | 46...50 | 51...55 | 56...60 | 61...65 | 66...70 | 71...75 | 76...80 |