The Telematics Guru Alerts system allows you to send notifications on one or a set of criteria, or record specific occurrences into events to report on. The most common alerts that all organisations should look at setting up are detailed in this article. This is not an exhaustive list by any means, but is just to give an idea of what the function can facilitate.
|Low Battery||Movement Alert||Device in trip for more than X||Out of Hours movement|
Basic Alert Screens
This guide will primarily deal with the 'Conditions' tab which holds all of the different states and attributes that we can generate alerts off. The other screens of General and Advanced cover off the message content when these alerts start and finish, The Notifications tab lets you apply the destination where the alerts will be sent to, in either SMS, Email or Push notifications.
The Assets tab contains your fleet and you can designate which assets you assign the alert to. You can also assign alerts when you create an asset in the Alerts tab in Asset Manage -> Create Asset.
Alerts asset assign tab
|Edit Asset Alerts assign tab|
Low Battery Alerts
Low Battery & Battery Good Flag
See this article for a discussion about Digital matter battery powered devices and low battery alerts
There are a couple of different ways to set up low battery alerts in TG, depending on device type. All Devices , wired and battery powered, have a 'battery good flag' - which is mapped to Digital Input 25 in Telematics Guru.
You can use the Alert Wizard to create a Low Battery Alert, which will use this input and the condition that the digital input is inactive. The wizard has the 'Conditions' tab preset, so you just need to input your message on Alert conditions being active and finished and assign it to an asset.
The benefit of this alert is that it is common across all device types. You can simply set up one single alert and apply it to all assets. For devices with the Coulomb counter/Battery Meter - this alert will fire when the estimated remaining battery % is less than 20%. For other battery powered devices e.g Yabby, Oyster v1, it fires based on voltage, and equates to around 10% remaining. For powered devices, it is when the internal back up battery drops below a certain voltage threshold.
Battery Meter Enabled Devices
Due to the Battery Meter, the Falcon, Eagle, Oyster2 and Remora2, can have more specific alerts set up by using analogue input 6 (Battery Level) to fire the low Battery alert as shown below. This allows for multiple alerts on 50%, 30% or 20% for example if more are desired to provide earlier warning rather than just a single alert.
If you have the Alert assigned to an asset, the Analogues will have a more meaningful name, for e.g. Analogue 6 will read as "Battery meter"
You can set up an alert on a device's ignition bit to be notified to whenever the asset starts moving i.e declares a trip. You can set this up in your initial organistion creation and assign it to all assets that are being monitored for movement, as opposed to assets that continually make trips. i.e. Theft protection. As before, If you have an asset assigned in the 'Assets' tab, the ignition bit0 will read as 'Ignition'.
This is different function to the 'Movement Alert' from the Live Map, as it does not have to be re-set after each movement.
please see our "How do I Activate a Movement Alert?" article for more details
Device in trip for more than X
This alert can be set up as either a wiring check to ensure that the installer has wired the ignition to the correct alternating power source, or as a basic safety measure for monitoring fatigue. (Can be subverted by toggling ignition, for fatigue alerts you can also look at G62/G100/G120's fatigue monitor feature.)
- Use Digital Input 0/Ignition is active and;
- Duration for X seconds. Used below is 14,400 seconds which is 4 hours.
Out of Hours Movement
If you're after a restriction on operation based on the time of day or week day, for example; company cars operating outside work hours, you can set up an alert to fire when an asset begins a trip outside of a timeframe.
Reporting on Alerts
For generating reports based off alerts and the conditions being met, please see the article Events Vs Alerts
More on Alerts
For more guides on Alerts, please see the category here