Aggregate multiple alarms associated with an incident - Mission Control 3.2.0.0

Genetec Mission Control™ Administrator Guide 3.2.0.0
Product
Mission Control
Content type
Guides > Administrator guides
Version
3.2
Release
3.2.0.0
Language
English
Last updated
2023-10-19

When the same alarm is triggered multiple times at the same location, you can aggregate all instances of the alarm to the already triggered incident.

Multiple occurrence restriction for an incident

You can choose to limit the number of times a particular incident type is triggered by choosing one of the following options in the Incident configuration > Incident type name > Triggers page:
Restrict multiple occurrence to
Set or remove restrictions on multiple active incidents in the Incident monitoring task using one of the following options (default=One per location):
No restriction
Select this option to allow multiple active incidents of the selected incident type.
One per location
Select this option to allow only one active incident per incident type per location.
One per area
Select this option to allow only one active incident per incident type per area.
One per location per category
Select this option to allow only one active incident per selected incident type under the selected incident category per location.
One per area per category
Select this option to allow only one active incident per incident type under the selected incident category per area.
One per source
Select this option to allow only one active incident per incident type per source.
NOTE:
  • You can also right click an incident type or category in the Incident configuration page of the Config Tool to set the Restrict multiple occurrence to for the incident type or all incident types under selected category.
  • The Restrict multiple occurrence to selection is applicable only to incidents triggered by an event through the Mission Control Rules Engine or the incident automation workflow. It does not apply to incidents triggered either manually in the Incident monitoring task or through the Mission Control Web API.

In this example, the incident trigger is restricted to one incident per location:

Limiting incident trigger by aggregating all related alarms

In this example the incident trigger is Any alarm:

When you have multiple alarm instances from the same alarm at the same location, you can configure the incident type to be triggered only once and aggregate all subsequent alarms to the same incident.

Incident automation workflow configuration

In this example scenario, the incident automation workflow is configured as follows:

In the Wait for event activity is configured with the following selections:
Wait for event > Specific event
A specific set of alarms related to this incident are added.
Event sources
The Incident location refers to the entity on which the incident is active. It may be an area, video entity, door and so on.
Related alarms
The Incident alarms selection aggregates events from a previously aggregated alarm.
Aggregate all related alarm instances
The option is selected to direct the system to aggregate all events of the previously aggregated alarm instance, irrespective of event source and related alarms selection.

The operator's screen

When the alarm triggers the incident, it is visible in the Incident monitoring task in Security Desk. All subsequent instances of the alarm are aggregated to the same incident preventing multiple incidents being triggered for the same alarm in the same location.

Incident trigger scenario when different alarms are triggered from the same source

You can have multiple alarms associated with the same source. When these alarms are triggered, the corresponding incidents associated with the alarms are triggered.