Workflow design for Camera offline 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 configure incident management workflows to manage camera offline incidents efficiently.

Workflow design considerations

There are different approaches that you can take to configure workflows to resolve a Camera offline incident.

In this example, when the IP camera goes offline, the Genetec Mission Control™ Rules Engine evaluates the Connection lost event generated by Security Center and triggers the Camera offline incident.

The workflow is designed to take one of two paths:
  • Automatically resolve and close the incident if it is a systemic glitch.

    In this case, operator intervention is not required.

  • Request help.

Workflow for Camera offline incidents

In this example, the workflow is grouped into three parts, each with a set of activities for a particular goal:
  • Notifying the operators of an active incident.
  • Validating the incident.
  • Resolving the incident.
Step 1: Active incident alert

When the incident is triggered, the operators must be notified of an active incident but action is not required yet.

In this example, an active incident notification is executed using the Column color activity and Change description activity.

You can associate different colors with different actions and incident priorities to inform your operators how to handle active incidents.

In this example, the incident is highlighted in the Incident monitoring task incident list, to indicate that an incident has been triggered but does not require operator intervention.

Step 2: Waiting to see if the system auto-corrects

You can use the Parallel tasks activity as logical IF to determine the path the system should take to resolve the incident by clearing the Exit when all branches are completed option.

In this scenario, the system waits to see if the camera comes back online within a preset time. If the 3-minute delay transpires or if the Wait for event activity detects the camera connection reestablished, the system exits the Parallel tasks activity.

If the camera connection is reestablished, the workflow directs the system to change the incident state to Resolved. However, if the camera does not come back online after the 3-minute delay, the system moves forward to the next activity.

Step 3: Verifying cause of camera signal loss

If the incident remains unresolved, the system executes either the Signal found: Camera online activity sequence or Video offline: Dispatch to facilities activity sequence. The operator's response to the dynamic incident procedure determines which parallel task in the workflow is taken.

When the incident is a false-positive

If the camera connection is reestablished after the 3-minute delay, you can still dismiss the incident as a minor glitch and your workflow can direct the system to close the incident without any operator intervention.

The Wait for dynamic procedure steps activity awaits confirmation from the operator on camera connection status. If the operator confirms active video feed, the system considers the incident resolved and automatically performs the necessary post-resolution activities to close the incident:
  1. Display the camera at the incident location.
  2. Change the incident state to Resolved.
  3. Export the incident to a predetermined location.
  4. Send an automated email with a selected list of information to selected recipients.
  5. Close the incident and remove it from the incident list in the Incident monitoring task.

By automating these activities, your operators can save time and focus on higher-priority incidents.

When the incident requires manual intervention

If the operator verifies that the camera is still offline after a 3-minute delay, there is a malfunction that requires maintenance. You can configure the system to wait for operator verification using the Wait for dynamic procedure steps activity. For more information, see Procedure for Camera offline incidents.

In this example, after the operator confirms that the error is not a system glitch and that help has been requested, the system is configured to execute the following activities:
  1. Change the incident state to the Repair needed custom state.

    For more information, see Custom incident states for Camera offline incidents.

  2. Use the Change priority activity to increase priority of the incident to High.
  3. Email selected recipients with information about the incident.
  4. Trigger the dedicated Camera maintenance incident.

Linked incidents

You can track all the incidents linked to your primary incident from the Related incidents page as shown in the example here: