Dealing with alarms
Prerequisites
- Release >= v5.1
An alarm can have the following statuses:
| Icon | Operation | Description |
|---|---|---|
| Notified | An alarm has come from the PLC. | |
| Closed | Alarm is closed/machine is online. | |
| Gone, not acknowledged | Alarm has gone from PLC, but no user has acknowledged. | |
| Received, and acknowledged | Alarm has come from PLC, and user has acknowledged. However, PLC has not yet reported that the alarm has gone. |
The corresponding users are notified when the alarm status is "Arrived" (until a user acknowledges the alarm or the alarm cancels itself).
Note
If an alarm is not acknowledged by a user and the status is "Not acknowledged", the alarm is still "active". If the alarm is repeated by the PLC, the time of the original alarm applies. The alarm history can be viewed in the details.
Alarm Escalation
If an alarm is triggered at a priority level where, due to individual notification settings, no user is currently receiving alarms, the alarm immediately escalates through the higher priority levels until an active user is found. This process can be tracked in the alarm history.
If no user is active at the time the alarm is triggered, no notification is sent. This is also reflected in the alarm history. Ensuring that at least one user is always active in order not to miss critical alarms is the responsibility of the user configuration.
If an alarm is not acknowledged within a predefined time period, it is sent again in the next cycle — this time with a higher priority level.