Managing abnormal video unit events - Genetec Mission Control™

Preconfigured Genetec Mission Control™ incidents

Applies to
Genetec Mission Control™
Last updated
Content type
Guides > Technotes
English (United States)
Product line
Mission Control > Genetec Mission Control™

Use the Abnormal Events - Video/Camera incident type to automatically alert operators when there are abnormal events related to video units such as camera not recording, lost transmission and so on.

Abnormal Events - Video/Camera incident type: functionality

This incident type is configured to be triggered automatically on detecting one or a combination of selected video unit events. The system then executes a preconfigured automation workflow that emails Administrators about an active incident. The system also sends a confirmation email with selected details when the incident is resolved.
Tip: You must have the following details:
  • At least one valid email address for notification emails.
  • For Genetec Mission Control™ versions, a macro to initiate a reboot of the unit.

    As of Genetec Mission Control™, Reboot unit is available as an automation workflow activity for incident type configuration.

The system automatically closes the incident after the video unit comes back online.

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

Abnormal Events - Video/Camera incident type configuration

The incident type is preconfigured with the following:

Abnormal Events - Video/Camera incident type: triggers

The incident is configured to be automatically triggered when any of the following video unit related events occur:
  • Block camera started
  • Camera tampering
  • Temperature alarm
  • Unit failed to respond to edge video request
  • File deleted
  • Health event:
    • Video signal lost
    • Transmission lost
    • Camera recording problem

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

Abnormal Events - Video/Camera incident type: automation workflow

After the incident is triggered, the system waits to see if the error resolves itself within 2 minutes. If not, the system runs a dedicated macro that restarts the unit. If the unit comes back online, the system automatically closes the incident without any manual intervention.

If manual intervention is required to fix the issue, the system waits for the operator to respond to the dynamic incident procedure with details of unexpected error or scheduled maintenance. If the operator selects the scheduled maintenance option, the system automatically triggers a Camera maintenance incident.

On error resolution, the system them send a notification email to users configured as Administrators with the following details:
  • Latest activity log
  • Last event
  • Incident trigger time
  • Incident owner
  • Incident sources
  • Incident location
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.

Abnormal Events - Video/Camera incident type: user procedure User procedure

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

The incident procedure steps include the following information and directives for the operators:
  1. Verification of event cause: Maintenance, known issue or unknown issue.
  2. Directives for the operator:
    • If the event cause is a maintenance, known hardware or network issue, put the incident on hold and revisit the issue for resolution.
    • If the event cause unknown, reboot the unit.
    • If the unit does not come back online, create a service request.

For more details, see Modifying incident user procedures.

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