The server-side tiered speed event allows you to monitor and manage speeding efficiently in areas where the map providers do not consistently provide posted speed or where drivers need to be monitored against geofenced speed limits and customers have created specific locations, with associated speed limits. This makes sure drivers are still monitored on the prevalent priority speed limits at all times.
A server-side event called, speeding - tiered, has been added for this purpose.
Another tiered speed solution that works with on-board speed and locations on the MiX Rovi can also be enabled. Note however that this is dependent on the MiX Rovi implementation. If you are interested in using the tiered speed on the MiX Rovi device, read more in Enabling location speed monitoring using MiX Rovi.
This article focuses on server-side tiered speed for which you do not need a MiX Rovi.
You need the same permission as you do to enable road speed over-speeding to make use of the Speeding – tiered server-side event.
Server-side tiered speed events ensure that there are no overlaps in the different types of over-speeding events that are raised, taking into account multiple over-speeding limit sources in the following order of priority (geofence, posted and fixed), but the event is only triggered once.
Positions come into the server from assets in the field and then the positions are evaluated against the following server-side speed limit sources (tiers).
- Tier 1 - The positions are first processed against any locations that are set up with a speed limit in the server-side tiered speed section in the organization settings. These locations also make use of any speed buffer thresholds set up for the organization for SSE road speed over speeding events.
- Tier 2 - If tier 1 is not true, the positions are then processed against the posted road speed limit. This makes use of any speed buffer thresholds set up for the organization for SSE road speed over speeding.
- Tier 3 - If Tier 1 and 2 are not true, the positions are then finally processed against the fixed speed value provided in the device config of the asset. (Refers to Event ID 1)
This process ensures that over-speeding events are not duplicated and only the relevant priority of over speeding events is triggered.
How does the server-side tiered speed event work?
When an organisation is enabled for server-side tiered speed events, the system will monitor the speed of the positions coming into the server and check whether that asset was speeding in a specified location and if the travelled speed exceeded the speed for that location it will trigger an event at that location (tier 1).
If there was no over speeding at location violation, then the system will check for a speeding violation on tier 2, which is the posted road speed limits. If the traveled speed exceeded the speed for that location it will trigger an event (tier 2).
If there was no road speed over speeding violation, the system will validate speed against the fixed speed setup for an asset in the device configuration (tier 3).
Example 1, the asset enters a housing complex or estate where it is allowed to drive 40 km/hour as per the location speed setup (tier 1). The posted road speed in that particular section is 80 km/hour (tier 2) and the vehicle fixed speed threshold is configured for 60 km/hour (tier 3).
If the asset drove 55 km/hour, the tiered speed event will trigger tier 1, which is location speed because the asset was driving above 40 km/hour (allowed per the location setup).
Example 2 , the asset is not in a specified location (no tier1), the posted speed limit is 80km/h (tier 2) and the vehicle fixed speed threshold is configured for 60 km/h (tier 3).
If the asset drove 90 km/h, the event will fire for the violation of road speed limits (tier 2).
Example 3 , the asset is in a specified location with a speed limit of 70km/h (tier1), the posted road speed limit is 80km/h (tier 2) and the vehicle fixed speed threshold is configured for 60 km/h (tier 3).
If the asset drove 65 km/h, the event will fire for the violation of fixed speed (tier 3).
Setting the default values for the different tiers
- Specify any locations with their custom speed limits in the server-side tiered speed setup in organisation settings for tier 1.
- Enable road speed over speeding events in organisation settings and set a speed buffer threshold percentage if required to allow grace before the event fires for tier 2.
- Set up the fixed speed for the asset in the relevant event template.