Related Topics and Links:

Phase Diagrams

Simulation Assumptions for Phase Diagrams

The underlying assumptions when performing simulations are:

Maintenance Tasks in Operational Phases

Maintenance tasks in progress during one operational phase can be interrupted if that phase ends before the repair is completed. For example, a crew delay or spare parts order may extend the duration of a repair beyond the duration of the phase. As described next, the software handles these interruptions differently, based on the stage in which the repair was interrupted and whether or not the failed block is present in the next contiguous phase.

Maintenance Phases

A system is considered down and unavailable during the execution of a maintenance phase and remains down until all components have been repaired or maintained according to the properties specified for the maintenance phase. A maintenance phase is executed when the simulation reaches the phase while progressing through the phase diagram, either following a success path or a failure path. The following assumptions apply to both cases.

Within these categories, order is determined according to the priorities specified in the maintenance template (i.e., the higher the task is on the list, the higher the priority).

If the inspection task is not set to bring either the item or the system down, the inspection will still be considered a downing inspection.

State Change Triggers and Phase Diagrams

Starting in Version 11, the on/off state of a block with state change triggers is maintained across phases (i.e., it  is not reset from any previous phase). In previous versions, the state was determined at the beginning of each phase based on the Initial state specified in the block’s properties.

 

© 1992-2019. HBM Prenscia Inc. ALL RIGHTS RESERVED.

E-mail Link