Cause+ block

The Cause+ block provides a platform to run Cause+ through Architect in real time while giving immediate feedback to the operator. Each scenario contains a configured target or monitored variable with user specified limits. Should the target variable for a Cause+ scenario exceed its limits, an alarm is generated and the user is able to see in real-time the possible causes for the deviation as well as a user configured operator message.

Return to Overview of blocks

Description

Cause+ scenarios are built directly on your process data, harnessing the powerful knowledge discovery techniques and features of the Continuous Troubleshooter. Good process conditions are identified and used as a "fingerprint" for the process, describing the ideal behaviour. Should the target variable for the scenario deviate from the ideal process behaviour, possible causes are calculated and displayed using the ideal process "fingerprint" on which the scenario was configured.

CAUSE+ block

Block Type

Rules and Models block

Input port

The input port may contain only double type fields.

During configuration of the block, all the input fields must be mapped to required fields used in the constructing of the selected Cause+ scenario. The input port must contain all the fields used in constructing the loaded Cause+ scenario, and these input fields must be mapped to the required fields of the Cause+ scenario.

Output port

The Cause+ block has two output ports:

Cause fields: This port shows the fields that cause target variation, configured in the scenario used in the Cause+ block.
Outputs: This port contains the following calculated fields for the selected Cause+ scenario:

Active – specifies whether or not the scenario was triggered. A 1 indicates that the trigger was activated and a 0 indicates no activation.
LowerLimitExceeded – specifies whether or not the lower limit was exceeded on a field. A 1 indicates that the limit was exceeded and a 0 indicates that is wasn't.
Message – messages are set up in the creation of the Cause+ scenario in the Continuous Troubleshooter. These are used to notify the user of a scenario being triggered, and what to do in that situation.
TopCauseName_N, where N <= M. N is the number of the specified cause and M is the total number of causes in the scenario.
TopCauseValue_N, where N <= M. N is the number of the specified cause and M is the total number of causes in the scenario. This value is the variable contribution of the input variable to the cause variable.
UpperLimitExceeded – specifies whether or not the upper limit was exceeded on a field. A 1 indicates that the limit was exceeded and a 0 indicates that is wasn't.

You can then connect each output port to other blocks for additional manipulation in the blueprint, or combine both ports using a Port combiner block and sink the output to a sink block for further analysis.

Runnability

Minimum requirements for runnability on the Cause+ block:

Selected and valid Cause+ scenario.
Properly configured and mapped scenario/input fields. The input port must contain all fields used in constructing the loaded Cause+ scenario, and these input fields must be mapped to the required fields of the Cause+ scenario.

Return to top