Alarms and event implemenation in application server and runtime applications

Alarm configured or detected by

Within a tag

Within an object

Alarm Classes
(client column)

Only certain classes of alarms are supported or detected: DSC, VALUE, DEV, ROC, SPC.

No system-wide distinction for classes. Alarms are tied to a Boolean that can be triggered from any logic.

Alarm Type
(Sub-class)
(client column)

Discrete, LoLo, Lo, Hi, HiHi, MinorDev, MajorDev, ROC, SPC. Client column.

No sub-class. The Alarm feature name is the closest concept. For example, ".PVHiAlarm". Mapped from Category.

Priority
(client column)

1-999 (1 most urgent)

Priority 0-999. 0 most urgent. 0 is mapped to 1 in InTouch.

Name
(client column)

Alarm name = Tag name.

Object.attribute

Comment
(client comment)

Separate alarm comment, which is different from the tag comment.

Object short description or alarm message where available.

Group

Alarm group allows client-side filtering. Sub-groups must be on same InTouch.

No alarm group. But Area provides mappable concept. Sub-Areas can be on different nodes.

State

No behavioral differences between Application Server/OMI and InTouch HMI.

Four states, which are combinations of ACK/UNACK and ALARM/RTN. Optionally, a fifth state, Latched, can be enabled for the Galaxy.

• UNACK/ALARM (usually displayed as UNACK)

• ACK/ALARM (usually displayed as ACK)

• UNACK/RTN (usually displayed as UNACK_RTN)

• ACK/RTN (usually displayed as ACK_RTN)

• LATCHED (optional)

  These states have a 1:1 correspondence with states of the Alarm feature, which keeps track of whether the alarm is InAlarm and IsAcked.

  Alarms in the state ACK/RTN are not shown in the SUMMARY alarm display because they do not need any further action from the operator unless Latched is enabled for the Galaxy. But, all four states appear in the HISTORY display, and in the Alarm Database.

  If the Latched state is enabled, ACK/RTN alarms remain visible in the alarm display until the operator sends a Dismiss command.

Value, CheckValue

Only static values sent with alarm message.

Static values and dynamic references are provided.

Ack

No behavioral differences between Application Server/OMI and InTouch HMI.

All alarms are sent to the client and require acknowledgement regardless of priority.

Dismiss

If the Latched alarm feature has been enabled for the Galaxy, all alarms in LATCHED state require a dismiss command.

History

No behavioral differences between Application Server/OMI and InTouch HMI.

Alarm state changes are logged to event history and shown on historical client.