You can create and manage alerts from the Alerts page. In addition, you can view alert details (e.g., data source, selected options, active or inactive status, etc.) at a glance, filter displayed alerts, and search for a previously created alert by title.
You can also check the Show All option box to display all created alerts at once without having to click through pages of alerts.
There are 25+ configurable alert types available. Please view the following list of alert types and corresponding descriptions and use-cases in the table below.
|Accel||Alert when a vehicle violates the specified accel threshold (in g-force or Gs). The default threshold is set at .50 Gs. This alert requires device to be installed with bracket/frame hardware and high-bond tape to avoid inaccurate readings (due to whip effect).
Example: Truck 150 just accelerated at .70 gs, which could indicate aggressive driving. Alert the fleet manager to schedule driver coaching.
|Asset Inputs||Alert when an asset's input changes status.
Example: Company XYZ equips its generators with lights. Alert the fleet manager, whenever the asset's light is activated.
|Braking (Decel)||Alert when a vehicle violates the specified decel threshold in (g-force or Gs). The default threshold is set at .50 Gs. This alert requires device to be installed with bracket/frame hardware and high-bond tape to avoid inaccurate readings (due to whip effect).
Example: Truck 150 just decelerated at .70 gs, which could indicate aggressive driving. Alert the fleet manager to schedule driver coaching.
|Diagnostic||Alert when a specific threshold is passed (either greater or lower). Specify a Diagnostic Type: Temperature, Coolant Temperature, or Engine Speed. The system does not check for alert conditions when the ignition is turned off. Temperatures reported are those provided by the sensor at the time of the update.
Example: Company XYZ transports cargo that must be stored in temperatures below 80 degrees. Alert the Fleet Manager and optionally the driver if the trailer temperature reaches a temperature above the threshold.
|Driver Login||Alert when a driver does not log in when starting a trip.
Example: Truck 150 is on the move, but the driver did not log in to the vehicle's Driver ID keyfob reader. Either the driver forgot or the vehicle could be subject to unauthorized use (possible theft). Alert the fleet manager after 2 minutes, and optionally send the driver a login reminder message.
|Driver Assign||Alert when a driver has successfully been assigned to a vehicle via Driver ID key fob or another method. (Buzzer or light in-cab notification of successful login requires additional equipment and installation.)
Example: The driver of Truck 150 just logged into the vehicle using the keyfob reader. Using SMS, a Buzzer, or Light (if installed), alert the fleet manager and/or driver that his login was successful.
|DTC||Alert on Diagnostic Trouble Codes for supported devices*.
Example: The axle for 54 MIKE is below normal operational range according to J1365005BA. Alert the fleet manager to schedule immediate maintenance, and optionally notify the driver to go to the maintenance lot after his last delivery today.
|DVIR||Alert when a Driver Vehicle Inspection Report is received with defects. (Requires HOS enabled on your account.)
Example: Bill just noted that his driver-side mirror was missing (high priority) on his DVIR and submitted the report. Alert Bill's immediate supervisor indicating that a DVIR was submitted by Bill, the defects included, and the time/date of the defect.
|DVIR Status||Alert when a vehicle is moving without a DVIR completed or marked unsafe. (Requires HOS enabled on your account.)
Example: Steven has started driving the company vehicle without completing a DVIR. Alert Steven's immediate supervisor that a DVIR has not been submitted on a vehicle that is currently being operated and notify the driver that a DVIR must be submitted.
|Heartbeat||Alert when a heartbeat is received (usually once a day).
Example: Company XYZ tracks its assets (yellow iron) but does not have motion-based reporting. The heartbeat for an excavator that had been sitting on a trailer just occurred outside of their yard (via landmark), which alerted the fleet manager that the equipment had been stolen.
|Hours of Service||Alert before daily hours of service limit is reached. (Only available to accounts with Hours of Service.)
Example: Joe Marks is within 30 minutes of reaching his daily hours of service limit. Alert the fleet manager and the driver to avoid a violation.
|HOS Driver Assign||Alert when vehicle moves without HOS driver assigned. Device ID and Driver Reference ID must match exactly. (Only available to accounts with Hours of Service.)
Example: A vehicle is moving without a driver signing into the tablet. Alert the vehicle’s fleet manager.
|Idle Time||Alert when a vehicle idles more than the specified limit.
Example: Company XYZ's policy for consecutive idle time is no more than 15 minutes. 51 LINDA has just exceeded the threshold. Alert the fleet manager, and optionally send the driver a reminder to turn off the vehicle.
|Ignition||Alert when a vehicle turns on or off.
Example: Company XYZ is following vehicle ABC's activity. Alert the fleet manager when vehicle ABC ignition status changes.
|Inputs||Alert when an input changes status. (Inputs are configured at the time of installation.)
Example: Company XYZ equips its vehicles with sirens/lights to be used in the event of an emergency. For oversight purposes, alert the fleet manager, whenever the siren/light is activated.
|Landmark||Alert when a vehicle enters or exits a landmark.
Example: Company XYZ's fleet policy prohibits drivers from making stops to their personal home addresses (uploaded as landmarks) during their shifts. 52 JEFF just entered one of those landmarks during regular business hours. Alert the fleet manager that the vehicle may be subject to unauthorized use, and optionally send the driver a reminder to return to work.
|Odd-Hours||Alert on movement within an odd-hours violation window.
Example: Drivers at Company XYZ are not allowed to use company vehicles on weekends or between the hours of 9:00 PM and 4:00 AM. It's Saturday, and 54 MIKE just reported movement outside the perimeters of the company parking lot. Alert the fleet manager that the vehicle may be subject to unauthorized use, and optionally remind the driver to return the vehicle.
|Out-of-Range||Alert on vehicles that have not reported for a time.
Example: 53 STACY has been running for 60 minutes without reporting data. 50 BRAD has been parked for 2 days without reporting data. The vehicles could have been subject to tampering or are in locations that are obstructing signal. Alert the fleet manager, and optionally remind the driver to check for physical obstructions within the cab itself.
|Posted Speed Alert||Alert on vehicles violating posted speed limits. Posted speeds are based on available speed limit information. This data does not include temporary speed reductions such as construction or school zones. Posted speed violations are calculated using the Inst speed
Example: Company XYZ's policy for speeding violation limit is 10 miles over posted speed. 51 LINDA has just exceeded the threshold (89 MPH in a posted 75 MPH zone). Alert the fleet manager, and optionally remind the driver to slow down**.
|Service Reminders||Alert when scheduled service is close or overdue.
Example: 53 STACY has a service schedule defined for oil changes every 3,000 miles. The truck's odometer just reached a threshold of 500 miles before service is due. Alert the fleet manager, and optionally remind the driver to schedule maintenance.
|Speeding||Alert when a vehicle violates a specified speed limit.
Example: Company XYZ's policy for speed is 75 MPH (regardless of zone). 54 MIKE just reported speed of 80 MPH. Alert the fleet manager, and optionally remind the driver to slow down*.
|Stop/Idle||Alert on a stop or idle longer than a specific duration.
Company XYZ's delivery stops are targeted to take between 15-20 minutes. 51 LINDA recently made a stop, and the ignition has now been off for 60 minutes. Alert the fleet manager, and optionally remind the driver to get back on schedule.
|Switch||Alert on device switches. Available switch types include Battery Voltage, External Power Lost, Panic Switch, Power Cycle, and Temperature. Low Battery Voltage occurs when a vehicle's battery is below 11.9 volts for 30 minutes or more. External Power Lost indicates when a device may have been unplugged/unwired (relies on backup battery). Power Cycle indicates when all power is lost and regained. If the device has a backup battery, the alert will trigger only if all power (including backup battery) had been lost prior to regaining power. Temperature threshold must be programmed by Support (for supported devices only).
Example 1: Truck 150 just reported the panic switch has been turned on. Alert the fleet manager, and optionally send the driver a message to indicate that the alert has been received or will be acted upon according to company protocol (e.g., potential safety issue). Example 2: 52 JEFF just reported a loss of external power, which indicates the device is now relying on battery power. Alert the fleet manager that a device has been disconnected, and optionally send the driver a message to indicate that the alert has been received or will be acted upon according to company protocol.
|Towing||Alert when vehicle moves and ignition is off. This alert is currently supported on GPSI-5000, ELD-2000D, and AT-3000 devices (PNP support anticipated Q3 2020).
Example: Company XYZ has several mowers in various locations throughout the city. The Fleet Manager wants to be notified when any of these assets are moving without ignition (i.e., towing stolen, etc.).
*Diagnostic data is an additional paid feature for vehicles equipped with PNP devices. Available diagnostic data varies by vehicle make/model. Data may include engine speed, fuel level, fuel level remaining, fuel rate, odometer, seatbelt, and more.
**If you plan to notify drivers when alerts are triggered (e.g., whenever a speeding violation occurs), consider asking drivers to assign messages from 477-477 (GPSGPS) to a unique ring/SMS tone. When drivers hear this tone, they can know immediately that they’ve triggered a violation without having to look at their mobile devices.
While Alerts are highly accurate, they are optimized for real-time situations as subscribed. Due to occasional cellular network or processing delays, very occasionally alerts will miss an event and should not be considered a reliable substitute for regularly scheduled reports on the same situation of interest. For this reason, we suggest customers also utilize scheduled reports whenever a potentially missed alert would cause difficulty for any reason.