Custom Event Setup
Settings > Engine Diagnostics > Custom Event Setup
Administrators use custom events to monitor against specific driver activities, such as hard breaking, excessive idling, and low fuel. These events consist of multiple engine data filters with threshold values associated. Expression-based logic (And/Or) is then applied to trigger the eventEngine data recorded by TrackIt that includes fault codes and driver behaviors like hard braking. for a vehicleAll machines used as a means of production on a construction site or at a batch plant. when one or more conditions are met.
These events are used when establishing an Engine Config Setup and with setting Driver Goals.
Name |
Name or description of the event. |
---|---|
In Use |
This column shows a Yes or No value depending on if the event is assigned to an engine configuration. |
Max Occurrence |
The maximum number of times the event can be triggered before notifications will be sent to the server for the event. |
Notify Dispatch |
When the event is triggered, a True value in the column indicates a notificationA software-generated message or warning triggered by vehicle data. will be sent to dispatch. A False value indicates that dispatch will not receive a notification about the event. |
Notify Email |
This column shows whether or not an email will be sent to an email group when the event is triggered. |
Adding custom events
Custom events are invaluable for providing insight into a driver's activities and the state of a piece of equipmentAll machines used as a means of production on a construction site or at a batch plant.. Without the proper criteria for events and filtering for the data received, you run the risk of incomplete and inaccurate data reporting. Therefore, as you configure an event, consider the goal of the event and how to best establish the criteria conditions under which it is triggered.

In the Event tab, you describe the event and set the criteria for triggering the event.
Name |
A short description of the event to help identify it's purpose. |
||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Driver Performance Event |
Flags the event as pertinent to driver performance tracking functionality.
|
||||||||||||||||||
Probe Event |
Controls whether event occurrences appear on ProbeA probe device mounted in the side of a bin to measure the moisture content of aggregate materials such as sand.-related reporting.
|
||||||||||||||||||
Use Expressions |
Creates additional functionality for handling multiple filters that trigger an event.
|
||||||||||||||||||
Filters |
Each event consists of one or more filters that act as the required criteria for triggering an event occurrence. The filter types selected here will indicate what behavior must occur before the event will occur.
|

From this tab, you indicate the return values that will show up in the Engine Events report, the Driver MessagesText messages exchanged between drivers and dispatchers using TrackIt., Dispatch Notification, and sometimes StatusThe specific activity or task a driver is currently engaged in, typically as part of a process called a "status loop." Changes. Additionally, you use this tab to set up when the event is saved and how often the event can occur.
Save Event when
|
Options for choosing when the event will be saved to the TrackIt system. For certain events, saving the event after it turns off provides more relevant information. This is also sometimes true when the event is turned On or both when the event turns On and Off. |
---|---|
Max Daily Occurrences |
Usually, the maximum number of times the event can be triggered before it will no longer be triggered.
Each occurrence will contribute to the Max Daily Events, which is set at a value of fifty. So, once the Max Daily Events threshold has been reached, alerts will no longer trigger. This could cause an event to stop triggering before its individual daily occurrences have been met.
|

When an event is triggered, certain values can be saved with the event and appear on the Engine Events report. These values can represent data types such as Engine Speed (RPM), Odometer (Miles), probe data, and other vehicle data recorded at the time of the event.

Each time an alertA software-generated message or warning triggered by vehicle data. is triggered for a driver, a messageText messages exchanged between drivers and dispatchers using TrackIt. can be sent with the alert that appears on the driver tablet. The message entered into the message field can more clearly communicate why the alert was triggered and what the driver should do in response, if anything.

A key part of using events properly is making sure the correct parties are aware of relevant information in a timely manner. From the Notification tab, you can adjust how each specific alert will be communicated to dispatch and other groups that may need to be aware of certain information.
Severity |
Classifies the severity of the event and determines which symbol icon to use if displayed on the Equipment Map screen. |
---|---|
Show on map |
Replaces the vehicle icon on the Equipment MapA map view that tracks the locations and statuses of individual equipment in a fleet. The dispatcher's equivalent to a "bird's-eye view." screen with the severity icon. |
Email Group |
Specifies who will receive an email notification for the event. Adding a row using the button will allow you to choose an email group from a drop-down menu. You may add multiple Email Groups as needed to the event. |

This tab may only be used when the Show ED Event Status Change option is set to True.
Vehicle Type |
Lists available vehicle types that may be applied to the event. |
---|---|
On |
Provides a list of statuses associated with the Equipment Type. The status chosen here indicates the starting status in the status loopA series of statuses that constitute the typical process a driver should progress through as part of their daily duties. when the event may be triggered. |
Off |
Lists statuses associated with the Vehicle Type. This Off status indicates after which status the event cannot trigger. For example, if you chose the To Job status as the On status and the At Plant status as the Off status, the Custom Event would only be allowed to trigger when the driver selected the To Job status and any status up until the At Plant status.
|