Alarms as incident triggers - 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

To manage incidents effectively in Genetec Mission Control™, you must understand the role of alarms as incident triggers, and how they work with the Genetec Mission Control™ Rules Engine to trigger an incident.

Alarms are entities in Security Center configured to highlight a situation that requires immediate attention. Alarms can include details such as related entities, recipient lists for notification, specifications for user specific alarm display, and so on.

You can view a list of triggered alarms in the Alarm monitoring task in Security Desk.

For incident management, alarms can be useful as triggers or checkpoints in Parallel tasks that guide the workflow into different paths.

Here is an example of an alarm as an incident trigger. In this example, when an alarm for the visitor's parking lot is triggered, the associated incident is also triggered.