Algorithm Design

Algorithm

Represents a sequence of conditions that must be fulfilled to consider the active Phase successful and proceed to the consecutive phase. It also describes which is the next Phase to continue to.

Each Phase contains one Algorithm sequence, and each Algorithm belongs to one Phase.

The Algorithm sequence contains Conditions.

Condition

A Condition represent an atomic step of the algorithm. It contains information needed for the operators and for the SCADA Systems to take a decision.

A Condition can contain custom fields, but the most relevant fields are:

Type represents the type of condition. Example: ‘Operator input’ indicates that the system should wait for the operator to input specific information.
Description represents the empirical description to easier the understanding of eventual more complicated formulas. Example: ‘Wait for the operator to introduce the desired WFI quantity’
Prompt contains the text to be prompted to the operator at each step. Examples: ‘Wait for T01 to be filled’, ‘Introduce WFI quantity’, etc.
Condition contains a formal logic representation which can be used for SCADA systems or other alternative systems. Example: ‘PIT 01 = Pressure_T01’
Note: See further how this field can be created using a Condition Builder.
Success Action defines the action to be taken upon success of the condition. For example, saving a reading or a specific value to a variable: ‘VariableVolume1 = 34l’.
Note: See further how this field can be created using an Action Builder.
Fail Action defines the action to be taken upon failure to complete the condition. Similar to the action
Note: See further how this field can be created using an Action Builder.
Success Transition represents the next phase to go to when the current condition succeeded. By default, it is the next phase in the sequence of the process.
Fail Transition represents the next phase to go to when the current condition fails. By default, it is the next phase in the sequence of the process.

You can create custom fields for each project.

For example, the following image shows how you can customize the Condition Form Window:

Conditions Editor

This window brings functionalities like search and insert, and automatic recognition to enhance the productivity when defining conditions.

Search and Insert

Type “pi” searches for “pi” and shows all the Pressure Indicators

As you type in any of the fields of a condition, the window automatically searches relevant information in the Module to assist you in referencing the right entities. Alternatively, you can choose a manual search by writing directly in the top right text bar for search.

Double click any result from the right to automatically insert it into the field currently in edit.

You can search for the following types:

Automatic Recognition and Highlighting

By inserting or manually typing any of the types above, The Conditions Editor will automatically recognize and highlight them.

The window below can be used to customize the colouring for the special tokens, for each of the accepted tokens types. See the Module Ribbon to localize the Algorithm Tokens Customization window.