Related Topics and Links:

Phase Diagrams

Node Blocks and Stop Blocks

The two possible outcomes of an operational phase block are modeled using success and failure paths. Node blocks and stop blocks are provided to allow you to build configurations that are both accurate and readable.

Node Blocks

The purpose of a node block is simply to enable configurations that would otherwise not be possible due to limitations on connecting blocks. For example, consider an instance where maintenance is scheduled to be performed after the operational phase has completed successfully, and if a failure occurs during simulation, that maintenance will take place upon failure. In this case, the operational phase block's success and failure outcomes are identical. Success paths and failure paths cannot be identical in phase diagrams, however, so you would model this configuration in one of two ways:

Node blocks can have unlimited incoming connections and a single outgoing connection.

Node blocks have no properties other than their block name. Each block is given a default name that is determined based on the default naming criteria established for the current database (see Default Name Formats window). You can replace this with your own name of up to 150 characters, if desired.

Stop Blocks

Stop blocks indicate that the simulation of the mission ends. A new simulation may then begin, if applicable. This is useful in situations where maintenance is not possible upon failure.

Stop blocks can have unlimited incoming connections. No outgoing connections can be defined for stop blocks.

 

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

E-mail Link