When the asset’s speed is compared to the speed limit data and a speed violation is detected, an over speeding event is generated. These over speeding events are either generated on the on-board computer or on the server.
If the speed limit data is stored on the on-board computer (for fixed speed and location monitoring) these events are generated by the on-board computer in real-time. These real-time events can be used to alert the driver in-cab of the violation and are available for reporting and RAG scoring.
NOTE: Events that are generated on the server against server-side speed limit information cannot be used to alert drivers immediately and are limited to the resolution of the AVL frequency.
The following are all default events and do not need to be included in the event templates. They can however be made available at library level for the translation of the event name.
- Over speeding event - generated on-board against the fixed speed limits.
- Over speeding in location event (geo-fence speed zone) - generated on-board against the location speed limit data stored on the on-board computer. This is not an active event.
- Over speeding in location - excessive speed (Active Message only) - generated on-board against the location speed limit data stored on the on-board computer.
- Over speeding in location - excessive duration (Active Message only) - generated on-board by the location speed limit data stored on the on-board computer.
- Tiered Over Speeding event - generated on-board. The event will prioritize the speed limit data in the following order:
- Location speed limit
- Fixed speed limit
This event is used for RAG scoring reporting purposes.
Over speeding in location event rule:
For overlapping locations, the location with the lowest speed value will always get priority.
RECOMMENDED READING
Add a location by selecting a point on the map
Export and import locations (provide MiX Telematics with GIS data that can be transformed into a compatible format and imported into the system.)