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.
|Event||The event that the trigger executes in response to. See below for possible events.|
|Clauses||The logical operation the trigger performs before deciding if it should execute an action in response to the event. See below for possible clauses.|
|Values||Existing data inside the Tulip system. An example value could be: "if the Tulip variable |
|Actions||What the trigger does. Many actions are possible in the Tulip system. See below for possible actions.|
An event can result from multiple sources. Possible sources and examples below:
|A machine outputs any attribute||When machine outputs any attribute|
|A machine outputs a specific attribute||When machine outputs specific attribute spindle speed|
|Time Interval||Every 30 seconds|
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.
Values can be any data-store that is maintained in the context of a machine. Values can come from a number of sources, including:
|153||Ability to configure actions for automaton system or equipment alarms by alarm severity|
|170||Provide a managed way to configure state models so that state models can define definitions of configurable transition rules. The rules may be dependent on equipment status, material attributes, batch.lot attributes, etc.|
|201||Ability to define specialized equipment parameters and configuration for a process step based on assigned equipment or equipment class. Ie liquid handling and hitpick parameters or setup configuration|
|252||Verify equipment is in an appropriate state to begin processing. Eg. clean, calibrated, not already in use, etc.|
|450||Ability to guide operators through equipment specific tasks. Ie loading and unloading of trays, setup, cleaning, etc.|