Managing door forced open events - Mission Control

Preconfigured Genetec Mission Control™ incidents
Applies to
Mission Control
Last updated
2024-04-24
Language
English
Product
Mission Control
Version
3.2
3.1
3.0
2.13

Use the Door Forced Open (Multiple Instances) incident type to manage unauthorized intrusion events.

Door Forced Open (Multiple Instances) incident type: functionality

This incident type is configured to be triggered automatically on events such as Door forced open, Door open too long, and so on.

The system waits for operator to respond to the incident procedure with the cause of door event. Depending on operator response the system performs one of the following actions:
  • If event cause is an unauthorized person, the system automatically emails the Administrators alerting them to the need for patrol.
  • If the event cause is a malfunction, the incident procedure guides the operators to request for maintenance and the system workflow adds snapshots of incident location at trigger time for additional detail.

The system is also configured to send a notification email to the Administrators when operators do not respond to the active incident.

Tip: You must specify at least one valid email address for notification emails.

For more information on the how the operator can monitor and manage the incident, see the Genetec Mission Control™ User Guide .

Door Forced Open (Multiple Instances) incident type configuration

The incident type is preconfigured with the following:

Door Forced Open (Multiple Instances) incident type: triggers

The incident is configured to be automatically triggered when any of the following events occur consecutively 3 times within a 3 hour time interval:
  • Any Door forced open
  • Any Door open too long
  • Any door unsecured

Based on your setup, you can add, remove or modify triggers as required. For more details, see Modifying incident triggers.

Door Forced Open (Multiple Instances) incident type: automation workflow

After the incident is triggered, the system waits for operator response to determine which series of actions to perform:

Cause PERSON - NO ENTRY

If the intruder has not gained access to the facility, the system decreases incident priority, exports the incident details to specified location and emails Administrators about the incident.

Cause PERSON - ENTRY

If the intruder has gained entry to the facility, the system changes incident priority to Critical, emails Administrators alerting them to the breach and advising immediate patrol dispatch.

Cause OBJECT inform MAINTENANCE

If the cause is a maintenance issue, the system lowers incident priority, waits for maintenance personnel to resolve the malfunction, exports the incident details to the specified location and emails Administrators about the incident.

If there is no operator response, the system emails the Administrators alerting them to a lack of response from operators.

You can modify any of these details such as email recipients, details included in the notification email, and so on by selecting the incident type from the Incident configuration page in Config Tool and modifying the corresponding automation workflow activity in the incident's Automation tab.

For more details, see Modifying incident automation workflow activities.

Door Forced Open (Multiple Instances) incident type: user procedure User procedure

The incident is configured with a dynamic procedure, that accepts operator responds and directs system action accordingly.

The incident procedure steps include the following directives for the operators:
  1. Confirming cause of door event.
  2. Instructions to dispatch maintenance or patrol based on door event cause.

For more details, see Modifying incident user procedures.

For more information on incident type configuration, see the Mission Control Administrator Guide.