Related Topics:

Phase Diagrams

Operational Phase Blocks

In phase diagrams, operational phase blocks are used to represent any stage of the system's mission that is not dedicated exclusively to the execution of maintenance tasks. Operational phases are always defined by (linked to) a simulation RBD in the current project. Each operational phase has a fixed, predefined duration unless a failure occurs during the phase and then it depends on how the properties of the phase block have been configured.

Operational phase blocks can have unlimited incoming connections and up to two outgoing connections, which may include one success path and one failure path. The success path and the failure path must be different; if both success and failure of the block actually lead to the same outcome, there are two ways to model this:

By default, the first connection that you create from an operational phase block is the success path and the second is the failure path. You can right-click either connector and choose Set to Success or Set to Failure to swap the two paths.

You can add an operational phase block to a phase diagram by choosing Phase > Phase > Add Operational Phase.

The Select Diagram for the Block window will appear. The list of available diagrams will show the simulation RBDs in the project. You can use the View area to sort the list hierarchically or alphabetically. The Filter field allows you to enter text to search for in the names of the available diagrams. If the diagram that the operational phase block will be linked to does not yet exist, click the Add RBD icon to add a new diagram to the project.

To open an operational phase block that already appears in the phase diagram, double-click the block or choose Phase > Settings > Block Properties to open the Phase Properties window.

The following properties are available to configure an operational phase block:

The Phase name field must be populated. Description text is optional. Note that an asterisk is used (*) to represent default block names. The block name that is displayed in the diagram will replace the asterisk with the block's default name; this allows the block name to be updated dynamically.

In these cases, 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 example, consider the DVD drive mentioned above; its duty cycle value would be 18 min / 60 min = 0.3. A duty cycle value higher than 1 indicates a load in excess of the rated value.

If a duty cycle is specified for the phase and there are also duty cycles specified for blocks within the RBD, their effects are compounded. For instance, consider the aircraft example given earlier. During the take-off phase, the subsystems experience 1.5 times the normal stress, so you would use a phase duty cycle value of 1.5. We also know that the landing gear is not used continuously during take-off. Assume that the landing gear is actually in use only 30% of the time during take-off. Each landing gear block in the RBD, then, would have a duty cycle value of 0.3. For each block, the effects of the phase duty cycle and the block duty cycle are compounded, yielding an effective duty cycle value of 1.5 x 0.3 = 0.45.

The Active Phase drop-down list at the bottom of the window allows you to choose another phase that you want to edit without the need to close and reopen the Phase Properties window. This option works in exactly the same way as the Active Block feature in the Block Properties window.

 

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