![]() |
|
![]() |
|
|
|
ReliaSoft > Software > BlockSim 7 > Case Studies > Optimized Reliability Allocation
In this example, a system is defined using subdiagrams. A reliability target is set for the entire system and reliability is then allocated to the subsystems, assemblies and components using an optimized allocation methodology. Consider the following system composed of two subsystems, A and B, as shown below:
Subsystem A is composed of two assemblies, A and B. Assembly B is in a 2-out-of-3 redundant configuration.
Subsystem B is composed of two assemblies, C and D.
Assembly A is made up of components 0 and 1.
Assembly B is made up of components 3, 4 and 5. Assembly C is made up of components 6 and 7.
Assembly D is made up of components 8 and 9. Furthermore, assume the following life characteristics for each component:
The system reliability for this configuration at 500 hr is R(t) = 0.925656. Let's assume that the target reliability for this system is R(t = 500) = 0.95. Determine an optimum reliability allocation strategy assuming that the cost/difficulty of increasing an item's reliability is defined by the following function.
Where:
At the system level, we'll set Subsystem 1 to f = 0.9 and Subsystems 2 to f = 0.7. Rmax for both subsystems is 0.99999 at 500 hrs. Then the optimum allocation scheme for each subsystem is the one that satisfies:
While minimizing:
Solving this yields an optimum allocation for each subsystem. Specifically, the new target reliability for Subsystem A is 0.986137 and for Subsystem B is 0.963344. The process can then be repeated for each assembly and component in the system. The results are given in the next table.
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[Home] [Software] [Training] [Consulting] [Resources] [Corporate] [Search] [Site Map] [weibull.com] |
|
|
ReliaSoft is a registered trademark of ReliaSoft Corporation in the United States and other countries. |
LEGAL [Terms of Use] [Linking Guidelines] |
| Copyright ©1992-2009 ReliaSoft Corporation, All Rights Reserved |
Contact Webmaster |