Genetec Mission Control™ incident - Properties tab - Genetec Mission Control™ 2.13.4.0

Genetec Mission Control™ Administrator Guide 2.13.4.0

series
Genetec Mission Control™ 2.13.4.0
revised_modified
2020-10-27

On the Incident Properties page, you can configure the sub-incidents (for collaborative incidents), the priority, the retention period, and many other characteristics of the incident type.

General

Sub-incidents
(Collaborative incident only) Other incidents that must be triggered automatically when the collaborative incident is triggered and that must be resolved for the collaborative incident to be resolved.
Play a sound
The sound that plays when an incident of this type occurs. Click Play () to hear the sound. The sounds are defined in the General settings - Audio page of the Config Tool's System task.
Priority
Default priority for this type of incident. The incident priority can be changed by the incident owner while the incident is still active. The incident owner needs the Change incident priorities privilege to do so. The incident priority values are defined in the Incident Manager - Properties page.
Retention period
Specify how long you want to keep incidents of this type in the system after they are closed. This parameter overrides the one defined at the Incident Manager role level.
Video display option
When cameras are attached to this type of incident, select whether to display live video, playback video (default), or both, when the incident is displayed.
Live
Display live video.
Playback
Display playback video.
Live and playback
Rotate between displaying live and playback video.
Allow manual trigger
Turn this option on (default=off) to allow this incident to be triggered manually or through an event-to-action. For example, the Child lost incident cannot be automatically detected by the system, and must therefore be triggered manually.
Auto-close
Turn this option on (default=off) if you want the system to close the incident automatically if no one takes ownership of it after a specified time. When an incident is triggered with the Auto-close option on, the starting state is set to New (Closed - Pending).
Auto-open in Monitoring task
Turn this option on (default=off) if you want the system to automatically open the triggered incident in the Monitoring task. When multiple incidents configured for auto-open are triggered, they get queued. The number of incidents queued with auto-open is displayed in the Security Desk notification tray.
NOTE:
  • This does not assign ownership of the incident.
  • Logging off clears the queue.

Automatic trigger restriction

Multiple occurrence restriction
Set or remove restrictions on multiple active incidents in the Incident monitoring task using one of the following options (default=One per location):
None
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.
NOTE:
  • You can also right click an incident type or category in the Incident configuration page of the Config Tool to set the Multiple occurrence restriction for the incident type or all incident types under selected category.
  • The Multiple occurrence restriction selection is applicable only to incidents triggered by an event through the Genetec 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 Genetec Mission Control™ Web API.
Effective
Select the time period during which the system can trigger the incident. The default schedule selected is Always.

The schedules are configured in System > Schedules. If the selected schedule is invalid, default schedule is assigned.

NOTE: The schedule selected does not apply when the incident is triggered manually.

Response and resolution time

Maximum response time granted
Turn this option on (default=off) to specify a maximum amount of time in days, hours, minutes, or seconds to move incidents of this type from New to any other state.
Send notification when time is not respected
Select this option to notify the supervisor of the incident recipients, incident recipients, or the supervisor and incident recipients that the maximum response time was not respected. These notifications are received in the notification tray.
Minimum resolution time granted
Turn this option on (default=off) to specify a minimum amount of time in days, hours, minutes, or seconds to move incidents of this type from initial response to Resolved.
Send notification when time is not respected
Select this option to notify the supervisor of the incident recipients, incident recipients, or the supervisor and incident recipients that the minimum resolution time was not respected. These notifications are received in the notification tray.
Maximum resolution time granted
Turn this option on (default=off) to specify a maximum amount of time in days, hours, minutes, or seconds to move incidents of this type from initial response to Resolved.
Send notification when time is not respected
Select this option to notify the supervisor of the incident recipients, incident recipients, or the supervisor and incident recipients that the maximum resolution time was not respected. These notifications are received in the notification tray.
NOTE: Maximum response time granted, Minimum resolution time granted, and Maximum resolution time granted are independent values.
When any response and resolution time properties are turned on:
  • Granted time not respected events are logged with incident activities.
  • Granted time not respected criteria can be used to filter incidents when generating an incident report.
  • A granted time not respected event can be used to trigger the Wait for TTR event automation workflow activity.