|
|
|
|
|
 |
 |
About Us | |
Products | |
Enterprise Solutions | |
Services | |
Customers | |
News & Events | |
Support | |
Resources | |
Careers | |
Downloads | |
|
 |
The discipline of reliability engineering consists primarily of applying various principles and reliability techniques throughout a product's lifecycle to aid in evaluating and improving the reliability of the product. Please note that the term product as used here can be meant to be a hardware product, a software product, a manufacturing process, or even a service. Following is an illustration of how the various reliability analysis techniques could be used during a Product Lifecycle Management (PLM) program. A Reliability Prediction can be performed in the conceptual design phase to "ballpark" the expected reliability of the product. If a critical failure is identified, a Reliability Block Diagram analysis can be used to see if redundancy should be considered to mitigate the effect of a single point failure. Then a Life Cycle Cost assessment can be performed to judge whether it is more cost effective to modify an existing design or to create a new one. As the design progresses, if there are particular safety concerns, a Fault Tree analysis can be used to systematically identify the most likely causes of a safety problem. In addition, an FMEA can show the effects of a failure of key pieces of the design. The results of either of these analyses may prompt another look at a Reliability Block Diagram analysis to find a way to reduce the probability of a particular failure occurring. As the design matures, there may be more information showing that certain failure events are dependent on other events, so a Markov analysis would be appropriate to guarantee accurate results. The ease and speed of performing routine maintenance on the product would require usage of preventative maintenance software and Maintainability techniques. And since the optimum number of spare parts will be required for service, a System Optimization and Simulation analysis can be performed. Once prototypes are built and testing begins, you may want to start collecting failure data using Weibull analysis to help identify trends. And once the product is fielded, issues can be tracked using the FRACAS Corrective Action techniques. Please note that although certain analysis types can begin to be used in a certain phase of a product lifecycle, they should not be limited to use during that phase. They should be "living analyses", meaning that as a design matures the analyses should be updated to reflect the changes to allow for early identification of potential issues. Not all of the above analysis types will be appropriate for every product, process, or service. If they are appropriate, the potential advantages gained by doing an analysis need to be weighed against the costs associated with the analysis. But likewise, these same costs need to be weighed against the potential risks of not doing the analyses and not discovering potentially critical issues. The Relex software was designed to effectively manage these reliability activities. Because various analysis types can depend upon information from other types, the Relex software was built from the ground up as a fully integrated tool. Information learned during a particular analysis is automatically available to the other analysis types. You do not need to worry about transferring the data and getting the numbers correct as Relex does it for you. Having the breadth of analysis types, reliability techniques, and preventative maintenance software available, the Relex software is able to support you now and into the future. |
|
|
|
Contact Relex
|
Copyright © 2008, Relex Software Corporation |
|
