Related Topics:

Fault Trees

Block Properties

Standby Gates

Standby gates in fault trees behave just like standby containers in RBDs. The blocks connected to a standby gate are called dependent events and are similar to contained standby blocks in an RBD in that one or more of the dependent events are active while one or more are dormant (i.e., standby or quiescent). Also, just like standby containers, standby gates act as switches that can fail and define the number of active blocks whose failures would cause system failure (or the active vote number required). Additional gates are not allowed below a standby gate.

The next two figures show both the fault tree diagram and reliability block diagram representation of a system with two units, A and B, in a standby configuration where unit A is active and unit B is in a standby state.

To configure a standby gate, in addition to the common block properties, you will need to specify the Active Vote Number, which is the number of events leading to the gate that must succeed in order for the gate to succeed. If the required number of events does not succeed, then the gate is considered to be failed.

Additional options are available for the standby gate, including:

When this option is selected, no other properties will be available for the block; note, however, that any properties you have already specified are simply hidden because they are not relevant. The settings will reappear if you clear the Set block as failed option.

If a standby gate has more than one dependent event in a standby state, you can specify the order in which the standby events are used. To do this, select the standby gate and choose Fault Tree > Properties > Standby Settings > Set Standby Orders or click the Set Standby Orders icon in the Block Properties window for the standby gate.

In the Standby Blocks Order window that appears, the standby events are displayed in the order in which they will be used. Select an event and use the up and down arrows that appear in its order number cell to move the event up and down the list. For example, in the window shown next, you would click the down arrow once to move Event 5 down one position; the result would be that Event 4 would be used first, then Event 5, then Event 3.

 

© 1992-2015. ReliaSoft Corporation. ALL RIGHTS RESERVED.