Server-side events allow the generation of location-based and movement events (server-side) through the monitoring of the live AVLs and passive data downloads against the server-side event rules for an organization.
Each position that is received by the server is processed through a server-side event engine. Where a particular server-side event engine rule is found to be true e.g. asset is in a location, a server-side event engine is raised.
These events can be viewed actively in the Info Hub and Live Tracking, or retrospectively in Historical Tracking, and Insight Reports.
Read Add a server-side event to learn how to set them up.
The trip definition of a server-side event is not configurable.
- In trip = Where speed > 5 km/h and distance traveled is greater than 300m.
- Out of trip = Where speed drops below 5km/h for longer than 5 minutes.
Live tracking
The information displayed in Live Tracking and Info Hub includes:
- Date and time of the event
- Location name
- Maximum speed
Historical tracking
The information displayed in Historical Tracking includes:
- Date and time of the event
- Location name
- Speed Limit – only on the Over-speeding in location event
- Maximum speed – only on the Over-speeding in location event
- Duration – only on the Over-speeding in location event
Viewing Events on the Trip Timeline
Server-side events are always displayed as notification events on the Trip Timeline. Notification events are displayed as single orange bars and fill the height of the row. Notification events are displayed each time the condition became true.
The information displayed on the Activity Timeline includes:
- Date and time of the event
- Location name
- Speed Limit – only on the Over-speeding in location event
- Maximum speed – only on the Over-speeding in location event