Workflow design to resolve false positive incidents - Genetec Mission Control™

Genetec Mission Control™ Administrator Guide

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

You can configure incidents and workflows in Genetec Mission Control™ to automatically resolve false alarms.

Workflow design considerations for validating false alarms

To validate a Door held open incident, after the incident is triggered, the system must wait for a predetermined interval to check if the door is closed. If the door is closed, the workflow can automatically resolve and close the incident. If the door remains open, the workflow and incident procedure must guide the operator towards incident resolution.

To include processes for both possibilities, the workflow requires two activity branches:
  • Validate a false alarm and close the incident without the operator's involvement.
  • Call for investigation

You can configure multiple activity branches using the Parallel tasks activity. You can use the Wait for dynamic procedure steps activity or another activity as a checkpoint to direct the system to the right activity branch.

Workflow for automatic resolution of false positive incidents

In this example, the incident is triggered automatically when the Genetec Mission Control™ Rules Engine detects a Door open too long event.

After the incident is triggered, the first step in the incident workflow must be to validate the incident.

In this scenario, the system is configured to wait for one of two events to occur first:
  • A 30 second time delay.
  • The door to close, which is confirmed by the Wait for event activity.
If the door closes automatically within 30 seconds, the system executes the sequence of tasks in the False alarm: Door open activity box.

The Exit when all branches are completed option is cleared to allow the system to exit the Parallel tasks activity as soon as either of the activity branches are executed.

However, if the door remains open after 30 seconds, the system exits the Parallel tasks activity and proceeds to the next series of steps that escalate the incident priority.

Because the incident is not a false positive and further action needs to be taken, the system waits for the operator's response to the dynamic incident procedure. Based on the operator’s selection, the system executes an activity branch in the second set of parallel tasks.