Events define what should be monitored and/or recorded by the unit as well as what other actions the unit should take when an event is detected, for example sending a message back to the office, switching on or off a device etc. Examples of standard events are Over Speeding, Harsh Braking and Excessive Idle. Within this library you can perform the following:
- Enable an event on the organisation
- Edit or define an existing event's settings.
- Add a new user defined event for use by the organisation.
There are different types of events:
- System - these events are available to all organisations to make use of and need to be included in the assets configuration in order for them to trigger. The event ID’s are the same across organisations. Users with the edit event permissions are able to edit the event thresholds and settings of these events. If users have the Advanced - Manage system events permission then they are able to add and remove conditions from these events.
- Custom - these events are created for a specific organisation. They need to be included in the assets' configuration in order to trigger. A user with edit event permissions can edit these events. No special sensitive settings permissions apply.
- Default - these events are available to all organisations to make use of and do NOT need to be included in the assets configuration in order for them to trigger. These events are included by default based on the unit type and cannot be removed from the configuration. The event ID’s are the same across organisations. A user with the edit event permissions is able to edit the event thresholds and settings of these events. There are no special permissions for sensitive settings.
- Diagnostic - these events are used to assist with vehicle diagnostics and troubleshooting issues and are available to all organisations to make use of. They need to be included in the assets configuration in order for them to trigger. The event ID’s are the same across organisations. A user with the edit event permissions is able to edit the event thresholds and settings of these events. If they have the Advanced - Manage diagnostic events permission then they are able to add and remove conditions from these events.
- Server-side - these are events that are not loaded to the mobile device and fire server-side based on the vehicles AVL’s (Active vehicle location). These events exist in the library but are hidden from the user.
- Hidden - these are events that are required to make the unit function but are hidden from the library and everywhere in the UI.
All the events require the parameters in their conditions to be present and measured in order for the event to fire (e.g. we need to monitor the seat belt parameter in order for the conditions on the seat belt event to be true and therefore trigger the event). Parameters can either be unit based (e.g. GPS speed from the units GPS), installation based (Panic button connected to the OBC) or CAN based (Fuel level based on CAN data)
To enable an event on the organisation, follow these steps:
- Click Manage.
- Under Config Admin, click Libraries.
- In the events library, search for the relevant event, for example, the relevant cold chain events, e.g. cold chain cooling unit off while driving and then make it available.
- Edit this if required.