Alarm acknowledgement
- Last UpdatedJul 10, 2024
- 1 minute read
Alarms are acknowledged by users who view unacknowledged alarms from their client applications like InTouch HMI or AVEVA OMI. Only alarms of certain priority levels need to be acknowledged.
The basic workflow to acknowledge an alarm consists of the following general steps:
-
The alarm is detected and reported to any subscribed alarm clients. The alarm is unacknowledged unless it is of a priority level that does not require acknowledgement.
-
An authorized user attempts to acknowledge the alarm from the client. The user can type an optional comment when acknowledging the alarm.
-
The user’s acknowledge request is sent to the detecting object’s alarm feature. The acknowledgment must pass through standard security checks first. The acknowledge request contains the user’s name and any alarm comment.
For the alarm utility, the alarm is acknowledged within the alarm feature immediately. The user name, comment, and acknowledged time are also saved. Alarm comments can be localized into any supported language.
The acknowledge is considered an alarm state change, which is sent to all subscribed clients. When an alarm is acknowledged, the current AppEngine timestamp is used as the acknowledgement time.
After an alarm is acknowledged for the first time, any additional (extra) acknowledgement attempts for the same alarm are rejected and an error is returned.