You can use the Incident report task to search and review incident-related activities, generate reports based on specific criteria, and export incident details with all associated evidence.
NOTE: The Incident task should not be confused with the
Incident report task. The Incident task is for
Security Center incidents, and the
Incident report task is for Genetec Mission Control™ incidents. This section describes the
Incident report task.
The following figure shows the Incident report task with an example of a generated report:
Incident report filters
You can generate incident reports from the Incident report page, using the following filters:- Incident ID
- Unique ID assigned to each incident.
- Incident type
- Incident types and categories.
- State
- Incident states.
- Location
- Areas where incidents occurred.
- Priority
- Incident priorities.
- Trigger time
- Incident trigger time range. You can set a relative or absolute time range.
- Owner
- Incident owner. If the incident is closed, it is the user who closed the incident.
- Description
- Search for a specific text in the incident description field.
- Response time
- The time it took for the incident to transition from New to any other state.
You can specify an upper bound and a lower bound in days, hours, minutes, and
seconds.
Under Granted time not respected, use Maximum time for incident to specify incidents that exceeded the maximum response time for that incident type.
- Resolution time
- The time it took for the incident to transition from the initial incident response to
the most recent Resolved state change. You can specify an upper bound and a lower
bound in days, hours, minutes, and seconds.
Under Granted time not respected:
- Use Minimum time for incident and Maximum time for incident to specify incidents that did not meet the minimum or maximum resolution time for that incident type.
- Use Minimum time for dynamic user procedure step and Maximum time for dynamic user procedure step to specify incidents that did not meet the minimum or maximum resolution time for one or more dynamic standard operating procedure steps.
- Include incidents set to Testing mode
- Include incidents set to Testing mode in the results.
- Additional fields
- Restrict the search to incidents with specific values for selected predefined user created fields. Additional fields are available if they are defined in the Incident Manager role in Config Tool.
- Custom fields
- Restrict the search to a predefined custom field for the incident. Custom fields are
available if they are defined through a custom plugin or if custom columns are enabled
in the Incident Manager role in Config
Tool. The following custom filter can be selected:
- Alarm context
- Context of triggered alarm associated with an active incident.
Incident report columns
The following columns are available for the incident report:- Incident
- Unique ID assigned to each incident.
- Name
- Incident type name.
- Priority
- Incident priority.
- State
- Incident state.
- Description
- Incident description.
- Events triggered
- Events that triggered the incident.
- Trigger time
- Time when the incident was triggered in Genetec Mission Control™.
- Source entities
- Entity on which the incident is triggered.
- Area
- Physical or virtual location (room, floor, building, zone, and so on) where the incident is active.
- Location
- Entity (area, video entity, door, and so on) on which the incident is active.
- External ID
- ID that links the incident to an external system.
- Category
- Incident category name.
- Response time
- The time it took for the incident to transition from New to any other state.
- Resolution time
- The time it took for the incident to transition from the initial incident response to
the most recent Resolved state change.NOTE: Moving an incident from updates the resolution time to include time spent in the previous Resolved state.
- Recipients
- Users and user groups the incident has been dispatched to.
- Owner
- Incident owner (user) name.
- Response time granted
- The maximum response time for that incident type. The TTR Metrics privilege is needed to see this column.
- Minimum resolution time granted
- The minimum resolution time for that incident type. The TTR Metrics privilege is needed to see this column.
- Maximum resolution time granted
- The maximum resolution time for that incident type. The TTR Metrics privilege is needed to see this column.
- Latest event
- Latest event aggregated to the incident.
- Latest event time
- Time of occurrence of the latest event aggregated to the incident.
- Latitude
- Latitude of the incident on the georeferenced map.
- Longitude
- Longitude of the incident on the georeferenced map.
- Response time (grouped)
- The response time grouped into time periods (1-10 sec, 10-60 sec, and so on).
- Resolution time (grouped)
- The resolution time grouped into time periods (10-60 sec, 1-10 min, and so on).
- Custom columns
- You can see the following information if enabled in the Incident Manager role in
Config
Tool:
- Alarm context
- Context of triggered alarm associated with an active incident.
- <Additional fields name>
- Additional information associated with an active incident.
Watch this video to learn more. Click the
Captions icon (CC) to turn on video
captions in one of the available languages.
For more videos on Genetec Mission Control™ operations, see the Using Genetec Mission Control™ in Security Desk video
book.
Tip: There is a cheat sheet available for Genetec Mission Control™ operations in Security
Desk.
NOTE: Although we do our best to keep our videos current, the
information presented in this video might become outdated with each new release. If you
find anything wrong with this video, feel free to contact
us.