Our devices (both TR500 and VX60s) have a 6-axis accelerometer that can detect movement through G-forces based on the following:

Moving forward and backward on the X-axis. (Surge)

We refer to this as Harsh Breaking (Forward) or Harsh Acceleration (Backward)

Moving left and right on the Y-axis. (Sway)

We refer to this as Harsh Cornering (left and right)

Moving up and down on the Z-axis. (Heave)

Contributes calculations based on the X and Y axis.



Our devices take 7 days to calibrate, as it learns location and "learns" how the driver drives.

How Are the Driver Behaviour Scores Calculated?

Linxio uses several calculation methods to determine driver behavioural scores in the Driver Behaviour Module. The methods are designed to normalise scores for each exception rule category, ensuring they are uniformly scaled and calibrated in order to accurately gauge Driver Behaviour.

Methods

All scoring methods utilise Total Distance. This is to ensure that scores stay proportional and fair regardless of distance driven. A driver who travels twice the distance of another driver is likely to incur twice the exception events; considering distance traveled allows for an accurate and fair grading system.

Note: The Driver Behaviour Score takes into account the distance unit of measurement; meaning the scores will be the same regardless of whether the distance is in miles or kilometres.

1 — Event Count

This scoring method is the Exception Rule Event Count in relation to the Total Distance. The scoring has been calibrated to award a score of 0 if a driver incurs 10 events or more, over 100 miles driven or fewer, or the equivalent (i.e. 5 events over 50 miles).

100 - (Exception Rule Event Count x 1000) / Total Distance

For example, if a driver’s Exception Rule Event Count is 3 and their Total Distance is 100 miles, the score would be 70.

100 - (3 events x 1000) / 100 miles = 70

2 — Violation Percentage

This scoring method considers the severity of the exception rule event(s) in relation to the Total Distance. The Exception Rule Event Percentage is calculated by dividing the Exception Rule Event Distance (distance traveled in violation) by the Total Distance (total distance traveled). This computes the percentage of distance traveled in violation. This percentage is then multiplied by the specific Multiplier which applies (see definition below) to determine the deduction factor, and then deducted from 100.

100 - (Exception Rule Event Distance / Total Distance) x Multiplier

For example, if a driver’s Exception Rule Event Distance is 10 miles and their Total Distance is 400 miles, their Exception Rule Percentage is 2.5%. The Multiplier for the percentile this Exception Rule Percentage falls in is 13, therefore the driver’s score would be 67.5.

100 - (10 miles / 400 miles) x 13 = 67.5

Multipliers:

The purpose of using multipliers to calculate driver safety scores is to

normalise, calibrate and score exception rule events out of 100. The chart below displays the Exception Rule Event Percentage range for each multiplier. For Driver Safety Scorecard calculations, the multiplier rises as the Exception Rule Event Percentage rises. In other words, the worse a driver performs, the greater the penalty to their score.

When a driver repeats unsafe driving behavior, the multiplication factor increases proportionately and dramatically lowers their score. The more the behavior is repeated, the higher the risk profile, and the higher the visibility to the fleet manager. Repeated exceptions not only elevate the risk of the driver, they elevate the risk of the entire fleet. Conversely, the better a driver performs, the lower their multiplication factor, and the higher their safety score.

Range	Multiplier
0	0
0 < % > 0.3	6
0.3 ≤ % > 0.7	7
0.7 ≤ % > 1	8
1 ≤ % > 1.3	9
1.3 ≤ % > 1.7	10
1.7 ≤ % > 2	11
2 ≤ % > 2.3	12
2.3 ≤ % > 2.7	13
2.7 ≤ % > 3	14
3 ≤ % > 3.3	15
3.3 ≤ % > 3.7	16
3.7 ≤ % > 4	17
4 ≤ % > 4.3	18
4.3 ≤ % > 4.7	19
4.7 ≤ % > 5	20

3 — Hybrid

This scoring method is a hybrid of the Event Count Method and Violation

Percentage Method. The Hybrid Method assigns a weight to each of the

scoring calculation methods to consider both the Exception Rule Event

Count and the Exception Rule Event Percentage when evaluating safety

risk. This scoring method puts a higher weight on the Exception Rule

Event Percentage (70%) and a lower weight on the Exception Rule Event

Count (30%) so that the severity of the exception rule event(s) remains

the focal point of the scoring calculation methodology.

0.3 x Event Count Method + 0.7 x Violation Percentage Method

For example, a driver’s Exception Rule Event Count is 10, Exception Rule Event Distance is 5 miles, and Total Distance is 250 miles. Their Exception Rule Percentage is 2.0% with the Multiplier for this percentile being 12. The driver’s score would be 71.2.

Event Count Method Score: 100 - (10 events x 1000) / 250 = 60  
Violation Percentage Method Score: 100 - (5 miles / 250 miles) x 12 = 76  
Final [Hybrid Method] Score: 0.3(60) + 0.7(76) = 18 + 53.2 = 71.2

Calculations -

ECO SPEED: 100 — (Event Count x 1000) / Total Distance  
EXCESSIVE IDLING: 100 — (Event Count x 1000) / Total Distance  
HARSH BRAKING: 100 — (Event Count x 1000) / Total Distance  
HARSH ACCELERATION: 100 — (Event Count x 1000) / Total Distance  
HARSH CORNERING: 100 — (Event Count x 1000) / Total Distance

Default Values

Eco Speed: Default is 85 km/hr
Eco-Driving is the entire process of the best outcome to reduce ongoing costs for vehicle utilisation:



Eco speed, and what we aim to educate, notify and deliver on, is surpassing the optimal speed (ie one component) for eco-driving at which a vehicle travels burning excessive fuel to not only power the vehicle but minimise carbon emissions and general engine wear and tear. This speed is default set to 85 km/hr on Linxio (the optimal speed limit is between 50-80 km/hr).

For more information on this topic, head over to the NSW Transport website.

Excessive Idling: Universally set to 2 minutes (so event will occur if idling for longer than this amount)

To set default Global settings for both Eco Speed and Excessive Idling can be configured via the Configuration > Driving Options:



Individual vehicle settings will override default global settings and be found via Fleet > Vehicle Profile > Specification:



Harsh Accelerating: 0.25gs over 400ms (just under half a second)
Harsh Braking: 0.35gs over 400ms
Harsh Turning (Left and Right): 0.3gs over 400ms
Potential Crash Detection: 2.5Gs exhibited immediately.

These are the default values if calibration is inconsistent or invalid.

Updated on: 14/03/2025