Workflow - Alarms
|
Alarm Field Name |
Description |
|---|---|
|
ID object |
An auto generated field by process client. |
|
Input |
The command channel for the input |
|
Transform |
The condition for the alarm, less than, equals greater than |
|
Priority |
The alarm priority is set with the toggle arrows in advanced view. |
|
Severity |
When alarms have been registered by the operator, they can be acknowledged. Acknowledging an alarm will not make the alarm go away, rather it is just an indication to the system that the operator has taken notice of an alarm and is aware that is currently in an alarm state. If the acknowledged alarms are still “alarming”, they will reappear even after their acknowledgment. If the alarm does not return after being acknowledged, that means it is no longer in an alarm state. The operator may choose to acknowledge all active alarms or smaller set of alarms using the following two buttons.
To create an alarm, first determine what signal is to be monitored. Once the signal is specified, the operator can populate the channel, signal, comparator, trigger time, and alarm severity fields. After filling in these fields, simply click add alarm to place it into the alarm manager's queue.
In the illustrated example, the unix_time signal on the OPENINS_NAV_SOLUTION channel is set to trigger a Severe warning to the operator if the timestamp is greater than 1500 seconds for a trigger time of 0 seconds.
