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.
- Priorities
- 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
- Turn this option on (default=off) to let the system automatically assign incident management profiles to users as soon as they log on.
- RabbitMQ
- RabbitMQ is the messaging 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.
- 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.
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:
- New
- 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. You might do this if, for example, higher priority incident requires your attention, or if you are waiting for external information before moving forward with the procedure. When changing the state of an incident to On hold, indicate for how long you want to pause the incident and click Apply. The incident reverts to its original state as soon as the hold time expires. If using the default settings, you can change an incident from On hold to any other state.
- Resolved
- 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.
- Closed
- Everything that needs to be done for this incident has been done. If using the
default settings, you must first resolve an incident before you can close it. After an
incident is closed, you can no longer make any changes to the incident. A closed incident is 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
- Servers hosting this role.
- Database status
- Current status of the database.
- Database server
- Name of the SQL Server service (default=(local)\SQLEXPRESS).
- Database
- Name of the database instance.
- Actions
- Maintenance functions you can perform on the role’s database:
- Create a database (
) - Create a new database.
- 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.
- Create a 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.
Watch this video to learn more. Click the Captions icon (CC) to turn on video captions in one of the available languages. If using Internet Explorer, the video might not display. To fix this, open the Compatibility View Settings and clear Display intranet sites in Compatibility View.