|
This configuration window is used to set the parameters for the Unresponsive Alarm, and is accessible on the Alarms Tab > Add Alarm > Unresponsive Alarms.
Click on the interactive image below for more information.
.png)
|
.png)
|
Unresponsive Period
|
|
Indicate here the duration that a vehicle must be unresponsive before an alarm is triggered. This can be as short as a few minutes or as long as a several days. Whenever specified a time-of-day or day-of-week filter for an unresponsive alarm understand that the unresponsive timer automatically resets whenever the time goes out of scope and back in. Ex., It is not possible to specify an unresponsive period of 48hrs if an alarm is also specified that the alarm only applies from 7am to 4pm. Because every day at 7am the unresponsive clock gets reset and so it will never reach 48hrs and thus no alarm will ever occur.
|
Notes:
•The tricky thing about creating an unresponsive alarm is limiting the notifications to only those vehicles that SHOULD be reporting. Otherwise notifications may send every time someone shuts their car off for the night. Everyone's vehicle utilization practices are different, so the below filtering can help find the best solution for the department.
oFollowing a practice of assigning an label to each AVL unit whenever they are on shift, then one way to avoid false unresponsive alarms is to limit the scope of the alarm to all but <blank> labels. That way when no one is assigned to this vehicle there is no expectation that it should be reporting. To do this click "All but" next to labels on the Unresponsive alarm setup form and then in the box type <blank> (including the brackets).
oIf certain vehicles work fixed shifts week after week then create a separate unresponsive alarm for each vehicle and assign a time of day and day of week filter so that the alarm only applies at those times.
|