Contained Standby Blocks
Add a contained block to a container by selecting the container and then choosing Diagram > Blocks > Add Block.
The properties available for configuring a contained standby block will vary depending on whether it is in an analytical RBD or a simulation RBD. In addition to the common block properties, you will need to describe how the block behaves.
The first step is to assign a URD for the block when it is in an active state and one for when it is in a standby state (i.e., quiescent or dormant). As explained in the topic on standard blocks, each URD uses a failure model to describe the block's reliability characteristics; for blocks in simulation diagrams, the corrective task and/or scheduled tasks associated with the URD are also applied to the block.
Note: In the case that both quiescent and active failure models are the same, the units are in a simple parallel configuration (also called a hot standby configuration). When the probability of failure of the standby component is less in the quiescent state than in the active state, that is called a warm standby configuration. Lastly, when the probability of failure of the standby component is zero in the quiescent state (i.e., the component cannot fail when in standby), that is called a cold standby configuration.
The following options may be available for contained standby blocks in both analytical and simulation diagrams:
- Duty cycle allows you to model situations where the actual usage of a block during system operation is not identical to the usage for which you have data. Continuous operation at the rated load is considered to be a duty cycle of 1. Any other level of usage is expressed as a percentage of the rated load value or operating time. (For more information, see Standard Blocks: Duty Cycle.)
- Active/Standby allows you to specify whether the block is in an active or standby state at the beginning of the simulation.
Tip: You can quickly change a block's state by selecting or clearing the Diagram > Properties > Standby Settings > Set Block to Active (Not Standby) command.
- Consequential Costs allows you to choose or create models to represent costs that are always associated with the block. Cost per failure uses a cost model, and Downtime rate and Uptime rate use cost per unit time models. If no models are assigned, it is assumed that there are no additional costs.
The following options are available only for contained standby blocks in simulation diagrams:
- Reactivate after repair if selected, the block will return to the active state immediately after it has been repaired. Otherwise, the block will remain in the standby state after if has been repaired and will be switched back to the active state only if and when the contained standby block that was activated in the initial switch fails. This option is available only if the active state is selected.
- Operates even if system is down if selected, indicates that the block continues to operate even if the system is not operating. If it is not selected, the block does not continue to accumulate age when the system is down.
In a simulation diagram, you can also assign a maintenance group for the contained standby block. A maintenance group is a set of blocks where some event within the group can trigger either maintenance or state changes for one or more blocks, either within the group or outside of it.
Once the block is configured, you can click the Optimum Replacement icon in the Properties area to open the Optimum Replacement window for the current block; this window allows you to determine the most cost-effective time to replace the component based on costs for planned (i.e., preventive) and unplanned (i.e., corrective) replacement.
