Alarm settings control the number and nature of alarms related to the Fleet Monitoring plugin. Alarm settings include alarm age and Genetec Mission Control™ incident triggering.
Before you begin
NOTE: If you want to use alarms to generate MC incidents, you must
configure the following.
After you connect the Fleet Monitoring plugin with Mission Control, you can define incident mappings that display the incident types available in Mission Control.
- Ensure that you have configured a default map.
- Create a new Security Center user in the same directory as Mission Control (where the
Web API and Incident Manager are running) with privileges:
- Application privileges → sign in using the SDK
- Action privileges → Incidents (Genetec Mission Control) → Third-party integration mode
NOTE: Assigning these privileges to a user allows the plugin to communicate with Mission Control using the web API.
Setting name | Description |
---|---|
Recent alarms | |
Max age | Select a time period after which an alarm is no longer considered recent. This age limit ensures that outdated alarms do not trigger unwanted data offloads or Mission Control incidents. |
Max alarms | Select a maximum number of alarms that can be considered recent at the same time. This alarm limit helps prevent performance issues if a vehicle is generating many alarms due to a technical issue. |
Mission Control | |
Enter your Mission Control connection information
to create Mission Control incidents associated with on-vehicle alarms. Tip: The incident that is created in Mission Control can
be associated with the location of the vehicle when the alarm was
triggered.
|
|
Mission Control incident mappings | |
Alarm | Configure the alarm for the vehicle that, when triggered automatically, creates an incident in Mission Control. If available, the vehicle's location at the time of the alarm is included in the incident details. |
Incident type | Configure the Mission Control incident type that applies when this alarm is detected. In Mission Control, incident types are used to automate incident detection and enforce standard operating procedures for teams working on the incident. |