Acknowledgements Workflow

Alarm acknowledgement is the act of an operator confirming they have seen and are taking responsibility for an alarm condition, such as a door forced open or an unauthorized access attempt. It indicates awareness and that the alarm is being addressed, but it does not mean the problem is solved. Acknowledging an alarm changes its status, making it clear to other operators who is handling the issue and removing it from the immediate “new” or “unacknowledged” list.

The system records who acknowledged the alarm and when, creating an important record of events.

To acknowledge (confirm) an alarm the operator needs to open Alarms View, locate the alarm record, and double-click on the record. That will open the confirmation form, where the operator will be able to add the comment or select an appropriate one from the list. The operator then clicks on ‘Acknowledge’ button, which may trigger acknowledgement routing sequence if routing template is configured for this type of alarm.

Alarms processing is based on the Alarm Definition which is is a complex object, combining

• Event Source
• Acknowledgement Template
• Routing Template
• Time Period
• Hot Command.

More details here: Alarm Definitions

Note, that Alarm Definition form may also be used to specify Event Definition with a simplified processing flow.

Operators may also acknowledge events on the Event View form.