Driver Behaviour is an important safety and cost saving measure. Driver behaviour alerts and reports help with Safety and Compliance, and enable you to get the most from your staff and assets.
By using Accelerometer, GPS and smart algorithms, we can produce alerts and reports on driver's behaviour such as idling or parked time while inside work hours.
|OEM Parameters||TG Method One||TG Method Two||Idle Reports|
Idle Monitoring with Vehicle Ignition On
The first method is setting up the device to activate a digital input whenever a condition threshold is met; for example idle time.
The applications for this method are
- When you want a report showing whether a vehicle was idle for more than X minutes, non-accumulative.
- Idling with ignition on reports
In this example, we want an alert that will send an email when an asset has been parked with ignition on for more than 30 mins at a time, not accumulative over a time period.
For idling while the ignition is on, first go into Oemserver.com, search for your device and select it using the checkbox, then set a system parameter choosing Idle Monitoring with the following settings:
using inputs 0-7 might conflict with default inputs on some devices.
In order for the Bolt to be able to effectively monitor idling Run Detect must be set up on the device. This is due to how the Bolt uses Emulated movement to track whether the device is 'In Trip' or not.
On a device like the Dart or G62, the device will be 'in trip when the ignition line is active. Thus if the device is stationary according to the GPS, but the ignition is active, we know it is idling (sitting still with engine running)
However the Bolt will end a trip if it stops moving, since there is no ignition line, even if the vehicle is idling with the engine on - after 240 seconds (4 minutes) by default.
We can use Run Detect to put the device in trip based on the voltage read by the Bolt. Then if the engine is running - and the read external voltage is higher than when not running (due to the alternator being on), the device will be in trip. This will allow the device to still be stationary, but still in trip. It will not end the trip after 240s of no GPS movement.
To configure Run Detect, please read the article on the knowledge base here
Telematics Guru Method One
Go to TG and select Admin from the Top Menu and click Alerts and then select New Alert (Advanced)
This is where you can set up the name of the Alert and how the message format is set up. By using 'Tokens' you can also provide information sourced from TG in the message.
Assign the asset from the list
Under Digital Input, Change the Input number to the one you selected in oemserver. If you've renamed the input under 'Manage Assets' the new name will appear here, for eg. 'Idling'
Choose the addresses to send the alert to
On the Advanced tab, you can format the email that is sent once the alert turns off. Also make sure the 'enabled' check box is ticked.
Inbuilt Idle Monitoring in Telematics Guru (Method Two)
Telematics Guru has an inbuilt idle monitoring tab inside 'Asset Details> Log Events' which declares an asset as 'Idle' after X amounts of minutes below a certain speed and logs it accordingly.
Idling instances will be reported on in the Excessive Idling - Summary and Excessive Idling - Detail reports.
You can also customise the 'Trip list' report to display data such as 'average' idle time