Machine Triggers

Machine triggers interpret events from Machine Attributes to set the Machine State and manipulate values in the Activity History for a machine. Triggers wait for events to fire then they check various values and compare them inside clauses to determine whether to perform actions. Machine Triggers are a component of a Machine Type and can be deleted by removing from the Machine Type or by deleting directly while editing the trigger.

Fields

Events

An event can result from multiple sources. Possible sources and examples below:

Clauses

Clauses allow users to define a series of boolean logic expressions (if/then statements) that must all evaluate to true before a given action is performed in response to a trigger event. A user can define a series of comparisons and then decide to execute a number of actions if any the statements evaluates to true of if all of the statements evaluate to true.

Clause Options

• Machine Attributes - Clause will use Machine Attributes for evaluation
  • {Specific Attribute} - A single attribute, picked from the available attributes for this Machine Type
    • Current Value - The most recent value of the attribute recorded by Tulip.
    • Previous Value - The second most recent value of the attribute recorded by Tulip.
    • Seconds since output of Current Value - The duration since the Current Value was last output.
• Static Value - A hardcoded value used in evaluation of the clause

• Operator - The method by which a clause will be evaluated, including: =, >, >=, <=, !=, Inside Range, Outside Range, Is Blank, Is Not Blank

• Now - Trigger evaluation considers only a single point in time.
• For any output in previous {x} seconds - Trigger evaluation considers data within a window of time. Any output in this window that meets the defined criteria will cause the clause to evaluate True.
• For all outputs in previous {x} seconds - Trigger evaluation considers data within a window of time. All outputs in this window must meet defined criteria in order to evaluate to True.

Values

Values can be any data-store that is maintained in the context of a machine. Values can come from a number of sources, including:

• Machine Activity History Field - The most recent value from an Activity History column.
• Static Value - Can be set to any unchanging value.
• Machine Attribute

Available Actions

1. Create Machine State - Users can enter the step name or select next or previous as defined in the step list panel.
2. Data manipulation
   • Store in Variable - store a new value in the context of the current execution.
   • Increment Variable - increments a specified numeric value.
   • Decrement Variable - increments a specified numeric value.
   • Clear Variable - set a value to its initial zero-value.
   • Set Downtime Reason - set the reason a specified machine is down.

Tests

Requirements