Driver Behaviour Monitoring

There are a number of ways to monitor driver behaviour on Telematics Guru. 

First drivers need to be set up in the system (some of the functionality below can still be utilised even if drivers arent set up) l. If you have one driver assigned to one vehicle this is an easy process that doesnt require any additional hardware.

If vehicles are shared then additional hardware will need to be installed to capture drivers, this is typically done via keypad which driver must enter their PIN code before a trip is started, but a fob/keycard system may also be used.

Head to the drivers page, which can be found under the admin dropdown. On this page you can see all drivers that are on the system. Here you can click new to add a new driver.

Add the drivers name and other info that might be needed. Then the ID type needs to be specified. If you only have one driver per vehicle, select “none” from the list. 

Otherwise you will need to select the specific type depending on the hardware that is installed, we will advise you of this as needed. Typically for a keypad, the “ibutton” type will need to be selected, then the ID data will need to be entered. This is what assigns the PIN code, enter the pin code with zeros before hand so that there is a total of 12 digits in the ID field. Ie: if the PIN code was 123456, we need to add six zeros before the PIN code to make 000000123456.

If a driver is in the address book and set up as a user, this can be used to send end of trip push notifications so trips can be entered as business/private.

Next on the manage assets page, if you click on an asset and go to the drivers tab we can either assign a permanently allocated driver (if only one driver uses one vehicle) or if driver ID hardware is installed select “enable driver management” we can then either allow all enabled drivers in the driver list to use the asset or choose specific drivers whos PIN code will be accepted. When finished click save.

Now that drivers have been set up we need to set up the behaviours we want tracked. Again in the assets editing box, go to the Log Events tab and select which behaviours you would like logged. 

First we can log speed, in this case it is a specified limit and not compared to local speed limits. We can set up monitoring based on the local speed limits, however this will incur an extra cost (please contact us if you would like to set this up). Speed limits can also be set for specific geofences (this can be done from the edit geofence page).

Next we can log excessive idling, we need to set the speed threshold that is considered idle. Its recommended that the threshold is not zero, so a small amount of GPS drift can be taken into account. We also need to specify how long an asset can stay under that threshold before it is considered as idle.

Lastly harsh event will log, harsh acceleration, harsh braking and harsh cornering, please note that the harsh events are set up at a default level, if the tracker has been installed loosely or operation of the machine in usually reasonably harsh these thresholds can be increased to show more realistic events.

Once this is done click save again. After the assets have been used for a while data will start coming through.

Any logged events will be shown on the trip history and will show what the specific event was. 

Now we can run reports to monitor the driver behaviour. A list of useful reports are:

Speeding detail/summary will show all speed logs from the above method. 

Speeding report allows you to set any speed as the limit and return all logs above the limit.

Speed band reports can be used to see severity of speeding against local limits (if set up)

Excessive Idling detail/summary will show all idle logs from the above method.

Harsh Driving detail/summary will show all harsh logs from the above method.

RAG (Red Amber Green) reports will show events averaged on an assets usage and colour coded depending on a lower and upper value. Useful for quick summaries of large fleets,

Driver Scorecard will deduct points from a driver based on the number of events per 100km.