Incident Manager configuration tabs - Genetec Mission Control™

Genetec Mission Control™ Administrator Guide

Applies to
Genetec Mission Control™
Last updated
Content type
Guides > User guides
Genetec Mission Control™

You can configure the settings for the Genetec Mission Control™ Incident Manager role from the Roles view of the System task in Security Center Config Tool.

Incident Manager - Properties

On the Incident Manager Properties page, you can configure the general settings for the Incident Manager role.
Retention period
Specify how long you want to keep incidents in the system after they are closed. This value can be individually defined for each incident type.
You can add custom values to the predefined incident priorities: Low, Medium, High, and Critical. Use the arrow buttons to change the order of the priorities. You cannot rename or delete the predefined priorities.
Auto-assign mode
Enable this option to let the system automatically assign incident management profiles to users when they log on.
RabbitMQ is the message broker software used by Genetec Mission Control™ and other Security Center components. The RabbitMQ server runs on your main server by default. If your RabbitMQ server runs on a different server or uses different logon parameters, change them here. If you have set up RabbitMQ failover, add the IP address of all your RabbitMQ servers here.
Document management
You must configure the document location before you can add support documents for Genetec Mission Control™.
Document API port
Port (default=8083) used by the role to upload and download web documents.
Document location
Path to the Genetec Mission Control™ document library folder (\MCLibrary) on the server hosting the Incident Manager role. If you are setting up role failover, you must enter a network path that is accessible from all servers assigned to the role.
Tip: If you use a shared network drive for documents related to incidents, when you copy incident configurations to a new system or restore the Genetec Mission Control™ database you need not recreate the document library.
Open document trash folder
The Trash folder () button is enabled only if you have deleted documents from your library. For auditing purposes, the system never deletes your documents. Documents that you replace or delete from the library are moved to the trash folder (\MCLibrary\Trash). If the document library uses a local folder on the Incident Manager server, you can only open the trash folder if you are running Config Tool on that server.
Export settings
You can choose the logo for your incident exports. By default, the incident exports include the Genetec Mission Control™ logo.
Branding image
You can choose one of the following options to appear on your incident exports:
No branding logo.
Mission Control logo
The default Genetec Mission Control™ logo.
Custom logo
Your own logo. You can click the folder icon and choose an image with 256 x 256 pixels or above in size. The image is resized to 300 x 300 pixels with the same aspect ratio.
Custom columns
You can choose additional information you want to display in the Incident report task and the incident list view in the Incident monitoring task:
Alarm context
Display the context of a triggered alarm related to an active incident. This option is not selected by default.

Incident Manager - States

On the Incident Manager States page, you can configure the incident states. You can modify the transition rules for the predefined states for incidents and add custom states to suit your specific needs, but you cannot rename or delete the predefined states.
The predefined incident states are:
The incident has just been triggered and no activity is recorded. If using the default settings, you can change a new incident to In progress or Closed.
In progress
Actions are being taken for this incident. If using the default settings, you can change an incident from In progress to any other state.
On hold
The incident is paused. For example, you might do this if higher priority incident requires your attention, or if you are waiting for external information before moving forward with the procedure. If using the default settings, you can change an incident from On hold to any other state.
The situation is resolved and ready to be closed. If using the default settings, you must complete all the steps in the standard operating procedure (SOP) before you can set an incident to Resolved. You can change the incident from Resolved to any other state.

You need the Forcibly resolve incidents with incomplete SOPs privilege to resolve incidents without completing all the steps in the SOP.

Everything that needs to be done for this incident has been done. If using the default settings, you must resolve an incident before you can close it. After an incident is closed, you can no longer make any changes to it. Closed incidents are removed from the Incident monitoring task, but all information remains available in the system for auditing, investigation, and analysis.

You need the Forcibly close unresolved incidents privilege to close unresolved incidents.

Incident Manager - Resources

On the Incident Manager Resources page, you can configure the servers and database assigned to this role.
Servers hosting this role. All of them must have access to the role database.
Database status
Current status of the database.
Database server
Name of the SQL Server service. The value (local)\SQLEXPRESS corresponds to Microsoft SQL Server 2014 Express Edition installed by default with Security Center Server.
Name of the database instance.
Maintenance functions you can perform on the role database:
Create a database ()
Create a new database with the option to overwrite the existing one.
Delete the database ()
Delete the database.
Database info ()
Show the database information.
Notifications ()
Set up notifications for when the database space is running low.
Backup/Restore ()
Back up or restore the database.
IMPORTANT: When you restore the Incident Manager database, the icons for your incident types are not restored because they are stored in the Directory database with the Incident Manager role settings.
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.