We'll show you the basic alarm response and event escalation workflows
Note: Before you can use the Cobalt Access Control Monitoring integration, you'll have to follow the Installation Checklist.
When an alarm is triggered (for example a door is forced open), Cobalt will decide whether to respond to the alarm. If you have specified that the robot should respond to this alarm (and device), the robot will be dispatched immediately to the alarm location.
As the robot proceeds to the alarm location, you will get some updates long the way, in the form of in-progress notes on the original alarm ("Door Forced Open") as well as new alarms notifying of the robot's progress.
When the robot arrives at the alarm location, it will (in conjunction with the Cobalt Command Center) either escalate or acknowledge the alarm. Whether the alarm is acknowledged depends completely on the post orders that you have specified that we follow.
If the robot acknowledges the alarm, it will acknowledge the original alarm "Door Forced Open" and send an event to notify that it has done so.
If the robot escalates the alarm, it will updates the notes for the original alarm and trigger an additional alarm to raise awareness.
When the robot detects an anomaly that its post orders warrant escalating to your GSOC, a new alarm will appear in your OnGuard alarm monitoring station. This alarm contains a URL to view more details about the escalated information on Cobalt's dashboard.
You can process the alarm in OnGuard according to your own standard operating procedure.
Triggering Events with "Global I/O"
Cobalt's alarms can be set up to trigger events using Global I/O. For example, if you want to trigger a strobe light or siren when particular events like a carbon monoxide alarm occur, you can use Global I/O to achieve that. Simply connect Cobalt's Logical Sub-Devices and use the Generic Event's text to configure any function in OnGuard.