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
- At least one valid email address for notification emails.
- For Genetec Mission
Control™ versions 18.104.22.168, a
macro to initiate a reboot of the unit.
As of Genetec Mission Control™ 22.214.171.124, 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
- 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.
- Latest activity log
- Last event
- Incident trigger time
- Incident owner
- Incident sources
- Incident location
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.
- Verification of event cause: Maintenance, known issue or unknown issue.
- 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.