Workflow design for Gas leak incidents - Genetec Mission Control™ 2.12

Genetec Mission Control™ Supplemental Guide for Incident Workflow Configurations 2.12.1.0

Applies to
Genetec Mission Control™ 2.12
Last updated
2019-11-28
Content type
Guides
Guides > User guides
Language
English (United States)
Product line
Mission Control > Genetec Mission Control™
Version
2.12

You can design incident workflows to guide your operators effectively in emergency situations like gas leaks.

Workflow design considerations for Gas leak incidents

For emergency situations such as Gas leak incidents, there are key steps that must be performed by the incident workflow:
  1. Display video feed at incident location to verify the threat.
  2. Wait for direction from dynamic incident procedures to update state of the incident in real-time.
  3. If the threat is escalated by the operators, set appropriate threat levels to sound the alarm, clear the area, and so on.
  4. Wait for incident resolution confirmation from operators and export the incident details to selected location.
  5. Neutralize threat levels.
  6. Notify the administrators via email with selected incident details.

Workflow for Gas leak incidents

You can use incident workflows to improve the efficiency of your emergency procedures. You can design incident workflows to interact with and respond intuitively to dynamic incident procedures.

In this example, when the incident gets triggered, the system automatically performs the following actions:
  1. Arms the zone and attached entities at incident location.
  2. Displays the video feed at incident location for operators to confirm gas leak.
    The Display entity activity displays a selected entity in the Monitoring task in Security Desk for configured recipients. You must configure the following details to get the required video feed:
    User, User group
    Recipients of the select entity.
    Owner only
    When selected, only the incident owner will receive the video feed. This setting overrides other configured recipients.
    Display entity
    The entity to display.
    Video mode
    You can choose one of the following options:
    • Live
    • Playback from current time
    • Playback from incident trigger time

    The current configuration, Display entity: Incident location live shows the camera at incident location only if the incident source includes a camera. If the operator triggers the incident on the camera in the map at incident location or if the system trigger uses a camera entity, this configuration of the Display entity activity shows the configured camera.

    If that is not the case, you must select the exact camera entity to display.

The next set of steps are in a Parallel tasks activity. The Parallel tasks activity serves as a logical IF, guiding the system across two activity paths based on the operator's response to the dynamic incident procedure. This is enabled by leaving the Exit when all branches are completed option unselected.

At this point, the system is waiting for operator confirmation of fire at incident location.

If the operator does not detect any fire in the incident location, the system dispatches the incident to on-site security teams and changes the incident description to reflect that action.

If the operator finds fire at the incident location or confirms that the gas leak is in a public place, the system makes a public announcement, sets a system-wide threat level, and executes all actions associated with the threat level.

After the incident is resolved, the Export incident activity in the workflow, exports incident details such as attached entities, and system and operator actions as an XML file to a preselected location.

You can use these exports to perform audits and improve overall incident management metrics.

The operator's screen for Gas leak incidents

By design, when the Gas leak incident gets triggered, the system directs the operator's attention to the video feed at incident location. Because this is an emergency situation, this incident is configured with a short response and resolution time.

In this example, you can see a notification that the operator did not respond within the allotted time.

You can use the Wait for TTR event activity in the incident workflow to configure countermeasures for cases wherein the operator does not respond or the incident is not resolved within the allotted time.

When the operator responds to the incident, the dynamic incident procedure begins displaying the steps to follow.

You can link multiple documents with emergency contact lists, maps to nearest medical facilities, and so on. You can also include links to articles in external sites, articles in the internal network, or PDF documents specific to this incident.

In this example, there is a link to guidelines from the Canadian government website.

Based on operator response to incident procedure, the system automatically escalates the incident, highlights the incident in the listing to show priority, and makes a system-wide notification.

The activated threat level highlights the operator's Security Desk in the selected color (red in this case), indicating the critical nature of the incident.

After the incident state changes to resolved, the system nullifies the threat level and returns the operator's Security Desk back to normal.