Automation workflow design for Bomb threat incidents - Genetec Mission Control™

Genetec Mission Control™ Administrator Guide

Applies to
Genetec Mission Control™
Last updated
Content type
Guides > Administrator guides
Genetec Mission Control™

You can configure incident automation workflows that guide the system to act based on operator response to established incident management procedures for Bomb threat incidents.

Automation workflow design considerations for Bomb threat incidents

For emergency situations such as Bomb threat incidents, there are key steps that must be performed by the incident's automation workflow:
  1. Notify selected recipients.
  2. Sound the alarm.
  3. Wait for direction from dynamic user procedures to update state of the incident in real-time.
  4. Perform post resolution activities such as neutralizing threat levels, changing the incident state to resolved, exporting incident details to selected location, and send an email to administrators with selected details of the incident.

Automation workflow for Bomb threat incidents

In Genetec Mission Control™, you can configure incident automation workflows to provide real-time updates to operators on the status of the incident. You can use the change in incident states and operator's response to dynamic user procedures to take decisive action towards incident resolution.

In this example, the automation workflow for bomb threat resolution is grouped into two sets of activities, each with its own goal:
  1. Sound alarm: Bomb threat
  2. Post resolution activities
The automation workflow uses the Sequence activity to group the system actions to present a more streamlined view. You can see the list of activities included in a Sequence activity by double-clicking it.

Automating system actions

In this example, the incident is triggered when a bomb threat is detected. The automation workflow is configured to direct the system to perform a series of activities to notify selected personnel of an active threat:
  • The preconfigured Evacuate threat level is activated. The system performs activities associated with the threat level, such as arming the zone, sounding the buzzer and so on. An active threat level highlights the operator's entire Security Desk application in the selected color for the threat level. In this case, red.
  • The incident listing in the operator's Incident monitoring task in Security Desk is highlighted in red to alert them to an immediate threat.
  • The doors in the incident location are automatically unlocked to facilitate evacuation.
  • The administrators are notified by email with details of the threat.

System response to dynamic user procedure steps

When the incident is triggered, the system guides the operator using the dynamic procedure steps. You can include documents with guidelines for handling threats, emergency contacts, and so on for this specific incident. The operators can access all the required information from the Documents section in the Incident page.

Automating incident resolution activities based on operator's response

By automation design, the system waits for the operator's response to one of three paths in the dynamic user procedures:

When the operator confirms that the threat is clear, the system asks the operator to comment on the incident resolution and executes a series of activities to resolve and log the incident details.

The Export incident activity exports details of the incident such as incident trigger time, external ID, operator actions, system actions, and more into an XML document. These details are stored in the specified location and can be accessed later for a forensic analysis of the incident and the incident resolution process.