Driver Scorecard Overview
đź’ĄDriver Scorecard is part of a premium product, Safety & Compliance, and requires a separate license. Please contact your Account Manager for more information on premium product licenses or reach out to Customer Support at [email protected] or call 888.836.6269.
This article gives a general overview of the Driver Scorecard feature and the logic behind it, including benefits, thresholds, and violation triggers.
The Driver Scorecard is beneficial for Power Users and users with permissions to configure Driver Scorecard thresholds and grading criteria.
Permissions
To view the Driver Scorecard the "View All Driver Scorecard" permission must be turned ON. To manage driver scorecards, the "Manage Scorecards" permission must be turned ON. To manage the driver scorecard grading criteria, the "Manage Grading Criteria" permission must be turned ON. To manage the driver scorecard thresholds, the "Manage Thresholds" permission must be turned ON.
Overview
Tenna’s Driver Scorecard leverages telematics technology to track and evaluate driver performance data based on various criteria and metrics enabling contractors to view and analyze behavioral trends for improvement in fleet safety. The scorecard has a built-in point system for unique driver grading, enhancing buy-in by incentivizing drivers to improve their performance and scores and enabling management to spot trends over time for corrective action.
- Drivers can assess their driver scorecards for performance insights and improvement to protect themselves and the traveling public. This contributes to the overall company safety record and the safe and efficient operation of vehicles to extend their lifespan and reduce operating costs.
- Management can track and reduce violations with real time alerts and aggregate grading to efficiently streamline and implement safety across assets, personnel, and the business. Scorecards improve record keeping and documentation while increasing compliance, and reward and promote individuals that abide to your culture of safety.
Driver Events, Violations and Thresholds
Speeding
Users have 3 options for configuring the Speeding Threshold:
- Speed X mph over Y mph. Minimum speed of W mph.
- Speed X mph over Speed Limit. Minimum speed of W mph.
- Speed X% over Speed Limit. Minimum speed of W mph.
The X, Y and W variables are determined and filled in by the user.
A speeding violation is only created if any of the below scenarios are true:
- There are > 3 consecutive speed samples within a minute that violate the configured speeding thresholds
- There are 2 consecutive speed samples from the tracker spaced between 58 - 62 seconds that violate the configured speeding thresholds
- Each tracker event will only trigger one violation per threshold type. Only the threshold with the highest priority will be triggered.
EXAMPLE:
Let's say you have set up thresholds named Unsafe Driving Threshold for Speeding 10 MPH over 50 MPH prioritized as High and a second one named Unsafe Driving Threshold 2 Speeding 10 MPH over 40 MPH prioritized as Low.
We gather the following data from our trackers for one of the trips:
- Tracker data point 1 - 3:01 PM - Speed 61 MPH
- Tracker data point 2 - 3:02 PM - Speed 66 MPH
- Tracker data point 3 - 3:03 PM - Speed 37 MPH
The above example triggered a speeding violation because there are 2 consecutive speed samples from the tracker spaced between 58-62 seconds apart (3:01 and 3:02) that violate the configured speeding thresholds: (“Unsafe Driving Threshold”: 10 mph over 50 mph and "Unsafe Driving Threshold 2”: 10 mph over 40 mph).
One Violation will be recorded for Unsafe Driving Threshold based on Tracker Data Point 1, because the violation goes to the first high priority threshold trigger.
Hard Braking
A hard braking violation is only created if any of the below scenarios are true:
Condition 1 - Hardware
Tenna fleet trackers can sense a change in horizontal acceleration/deceleration, depending on the Tenna Hardware Product the following minimum criteria should be met before it can generate a hard braking event.
- TennaFLEET II and TennaCAM 2.0: 350 Milli-g of sustained deceleration for 1.6 seconds
- TennaFLEET JBUS or OBD-II: 300 Milli-g of deceleration
Condition 2 - Tenna Threshold
If you are a Power User or User with appropriate permissions (you can set up thresholds for hard braking) this applies to any assets in your account that have a TennaFLEET tracker installed.
You can set up multiple thresholds for hard braking in Tenna and prioritize them according to how a driver will be scored. If multiple violations are detected, the violation with the highest priority shall constitute a scorecard violation.
Pro Tip! Many safety experts use 0.47 g's as the maximum deceleration that is safe for the average driver to maintain control, good to excellent tires, and dry surface. A reasonably skilled driver can stop at 0.62 g's. Most production street vehicles have maximum braking of around 0.8 g's.
EXAMPLE:
A hard braking threshold was set up with a minimum g-force variable of 0.7 G and a deduction of 4 points for this threshold.
A driver driving at 75 MPH decelerates in 4 seconds to come to a full stop at a red light this approximately translates to a deceleration of 0.85 G-units sustained over 1.6 seconds.
Tenna trackers can sense and report it immediately. Also, since the G-Force is greater than the threshold, it triggers a violation of the threshold rule. This recorded violation is used to score drivers based on your custom grading criteria.
Hard Acceleration
Like Hard Braking, a Hard Acceleration threshold is configured by submitting a value for the minimum G-Force.
A hard acceleration violation is only created if any of the below scenarios are true:
Condition 1 - Hardware
TennaFLEET trackers can sense a change in horizontal acceleration/deceleration. Depending on the Tenna hardware, the minimum criteria should be met before it can generate a hard braking event.
- TennaFLEET II and TennaCAM 2.0: 250 Milli-g of sustained acceleration for 1.6 seconds.
- TennaFLEET JBUS and OBD-II: 300 Milli-g of acceleration.
Condition 2 - Tenna Threshold
A Power User or User with appropriate permissions can set up thresholds for hard acceleration for all assets in their account and prioritize them according to how the driver will be scored.
EXAMPLE:
A hard acceleration threshold was set up with a minimum g-force variable of 0.7 G and a deduction of 4 points for this threshold.
A driver cruising on the highway at 60 MPH, decides to overtake a vehicle and accelerates to a speed of 90 MPH in under 2 seconds. This translates to an approximate g-force of 0.91.
Since the G-Force is greater than the configured hard acceleration threshold, it triggers a violation of the rule. This recorded violation is used to score drivers based on your custom grading criteria.
Idling
The Idling threshold is configured by inputting a value for a minimum of X minutes that an asset is moving under 5 mph (excluding when Power Take Off - PTO is engaged)
An idling violation is only created if any of the below scenarios are true:
TennaFLEET trackers will detect when a vehicle is ON and not in motion. The device starts a timer once the engine is in idling mode, which terminates as soon as motion is detected. This interval is reported by the tracker as a discrete idling event with a duration.
If the idling duration is greater than the configured threshold, it constitutes a violation of the idling threshold. Depending on the configured grading criteria, points can be either deducted or accumulated for the current assignee’s driver scorecard.
EXAMPLE:
You have set up a deduction threshold for idling with a minimum time of 3 mins to deduct 3 points on every incident.
Incident #1: A dump truck delivering gravel to a job site makes a pit stop at station for some supplies.
Incident #2: engine is left running for approximately 4 mins before it resumes its delivery trip.
Once at the yard the driver engages the PTO, and it takes 5 mins to dump all the grave at the job site.
Incident #1 is recorded as a violation of the idling threshold and deducts a total of 3 points from this driver at the conclusion of the trip.
Missed Inspection
Power Users and Users with the appropriate permissions can create a threshold for Missed Inspections.
If a Missed Inspection threshold is created, any time an assignee misses a required inspection, a violation will be recorded. This can be configured as part of the custom scoring distribution in the scorecard feature.
Miles Driven
The Driver Scorecard feature allows you to set up a threshold to award your driver with bonus points for the number of miles driven. Once this threshold is configured, Tenna automatically checks to see if your driver reached the configured number of miles of a completed trip, and the points are automatically awarded.
Miles Driven without Violation
In addition to the Miles Driven bonus, you may configure a threshold for awarding points to drivers who drive X number of miles without a violation (speeding, hard braking, etc.)
NOTE: Only one bonus will be awarded per X miles driven variable. Tenna checks previous 30 days’ worth of trips for already awarded bonus.
The violations count automatically reset once a bonus is awarded.
If any of the trips have a violation the remaining miles from that trip will not be considered for a bonus.
EXAMPLE:
You have a threshold set up with grading criteria for 2 points awarded as a bonus for every 250 miles driven without a violation.
A driver in your fleet is assigned to drive from New York to Chicago (Approximately 800 Miles)
Assuming it takes the driver 4 stops to complete this drive:
- Trip 1: 100 miles driven: Hard braking Violation at Mile 50
- Trip 2: 100 miles driven: No Violation
- Trip 3: 150 miles driven: Hard Braking Violation at Mile 100
- Trip 4: 450 miles driven: No Violation
Points are awarded based on the cumulative miles driven for each trip without violation (550 miles in this example) divided by the configured X variable (250 miles in this example). Trips 1 and 3 had violations, so the miles driven in those trips do not count towards the cumulative miles driven for this bonus.
Total of 550 miles driven without violation = 2 points per configured X variable (250 miles) = 4 points awarded
FAQ's
What is the lowest G force setting for hard breaking?
The lowest setting would be .3 G- anything lower would not generate an event on the scorecard.
Why does the Fleet Tracker and the TennaCAM not display the same event?
The Fleet Tracker and TennaCAM register events independently. Check your settings in Tenna and in Rosco to view the separate events.