The Powerfleet system allows you to create and customize events according to your specific requirements.
Events define what should be monitored and/or recorded by the mobile device.
They determine what actions the mobile device should take when an event is detected, for example sending a message back to the office, switching a device on or off, etc. On-board events used within an organization reside in the Event Library.
Examples of events include:
- Over speeding
- Harsh braking
- Excessive idle time
Various default and system events are available to simplify the configuration process. These events are loaded to the onboard computers (i.e. mobile devices installed in your assets) and are reported back into the Unity system when triggered. The events are then displayed in On-Road IoT, or the mobile apps, or you can choose to be notified via email by setting up event notifications.
Event Types
You can configure server-side events that are not loaded onto the onboard computer (OBC) and thus generate 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.
Read the Event types article for an explanation of the different events available in On-Road IoT.
Conditions
Events are recognized by the mobile device when a combination of one or more conditions becomes true. You can set up these conditions when editing an event in the event library or when editing the events in the event template.
Please note: Changes made to events in the Event library will not automatically cascade to the event templates or the configuration groups using the event template. Please select the "Cascade to templates" option in the actions dropdown next to the event in the Library to cascade the changes.
Read Event conditions to learn more about these settings.