Determining the Reliability of a System with Standby Redundancy
In the last issue of the HotWire, we discussed the case of a system with load sharing components. Load sharing is a form of redundancy with dependent components, i.e. the failure of one component affects the likelihood of failure for the other component(s). In this issue, we will discuss another form of redundancy, namely standby. This article describes the three types of standby configurations (hot, warm and cold) and presents an example analysis for a system with one active and one standby component.
Under standby redundancy, the redundant components do not share any of the load, and they start operating only when active components fail. In standby redundancy, the components are divided into two types, Active and Standby. The standby components have two failure distributions. One for when they are in standby (quiescent distribution) and one for when they operate (active distribution).
When the failure rate of the standby component is the same in quiescent mode as it is in active mode, then components are in a "hot standby" configuration. This is the same type of redundancy as the simple parallel. When the failure rate of the standby component is less in quiescent mode than in active mode, then you have a "warm standby" configuration. Lastly, when the failure rate of the standby component is zero in quiescent mode (i.e. the component cannot fail when in standby), then you have a "cold standby" configuration.
1. Same distribution as when in operation (hot standby).
What is the system reliability at 1000 hours? Note: For this example, we will only consider the non-repairable case, i.e. when a component fails, it is not repaired/replaced.
The reliability of the system at some time, t, can be calculated using the following equation:
Solving Eqn. (2) with respect to te, you can obtain an expression for the equivalent time, which can then be substituted into Eqn. (1).
BlockSim 6 (anticipated for release in Winter 2002) will include the ability to calculate standby redundancy. The following figure illustrates the reliability block diagram (RBD) for the system as entered in BlockSim 6.
The Start and End blocks have no failure information (i.e. reliability of 100%) and therefore do not affect the reliability of the system. The active and standby blocks are within a Standby Container, which is used within BlockSim 6 RBDs to specify standby redundancy. Note: An article in Volume 3, Issue 2 of the Reliability Edge newsletter provides more detailed information on the use of Container blocks within BlockSim 6.
Since the standby component has two distributions (active and quiescent), the Block Properties window of the standby block has two pages for specifying each one.
Note that even though the beta for the quiescent distribution is the same as in the active distribution, it is possible that the two can be different. In other words, there may be different failure modes present during the quiescent mode than during the active mode. For the same reason, it is also possible that two different distribution types may be used to describe the active and quiescent modes (e.g. lognormal when quiescent and Weibull when active).
The results for this example are given in the following table:
In many cases when considering standby systems, there is also a switching device that switches from the failed active component to the standby component. The reliability of the switch can also be incorporated into Eqn. (1). The incorporation of the switch reliability in the standby configuration will be discussed in the next issue of the HotWire.
Copyright 2002 ReliaSoft Corporation, ALL RIGHTS RESERVED