Operator Safety Scorecards Follow

IntelliShift's Operator Scorecards provide a more comprehensive and customizable approach to evaluating driver performance. By considering factors like distance, drive time, and stop time, these scorecards offer a better assessment of operator safety.

Weighted Operator Scorecard Calculations

The Operator Scorecard is a combined score calculated from four exception categories: Acceleration Exceptions, Speeding Exceptions, Idle Exceptions and Ai Dash Cam Exceptions. Each category can be configured and weighted to match specific company needs.

Operator Scorecard Calculation: 

• Operator Score = (Acceleration Weight - Acceleration Score) + (Speeding Weight - Speeding Score) + (Idle Weight - Idle Score) + (Ai Dash Dam Weight - Ai Dash Cam Score)

Example: (Using the defined data from the category based exceptions below.)

Note: If the Point Deduction in a Category, exceeds the Category Weight %, that category will result in a 0 score in that category. 

As shown above in the example; The Operator lost 25 Points in the Acceleration Category, and the weight in the category was 25% of the Operator's Score, This would result within a 0 score within the Acceleration category. The Operator lost 13.33 points in the Idle Category and the weight in the category was 10% of the Operator's Score. This would result with a 0 score within the Idle Category as the score can not exceed 0 within the category. 

Acceleration Exceptions

Acceleration Exceptions Category provides deductions based on telematics data of the operator triggering harsh braking, Rapidly Accelerating, or Harsh Turning. 

• Default Weight: 25%
• Event Types: Harsh Braking, Rapid Acceleration, Harsh Turning
• Calculation:

  Acceleration Score = 100 - ((Company Defined Deduction * Number of Recorded Events)/Miles Driven) * Company Defined Average Miles
  

Example: 

**Note: When Calculating the Score, if your Point deduction exceeds the Default Weight, the max point deduction will be the max weight of the category. 

In This Example above, the driver would have scored a 60 in this category, but since the Acceleration is set to 25% this means that the max point reduction from the Operator's Scorecard will be 25 points. 

Speeding Exceptions

Speeding Exceptions Category provides deductions based on telematics data of the operator triggering High Speed or Posted Speed Limit Violations

• Default Weight: 40%
• Event Types: High Speed, Posted Speed
• Calculation:

  Speeding Score = 100 - ((Company Defined Deduction * Speeding Time [Minutes])/Driving Time [Minutes]) * 100

Example:

Idle Exceptions

Idle Exceptions Category provides deductions based on telematics data of the operator excessively idling the vehicle.  

• Default Weight: 10%
• Event Types: Excessive Idling, Ability to Exclude Business Idle
• Calculation:

  Idle Score = 100 - ((Company Defined Point Deduction * Total Duration of Idle time Above Company Threshold [Minutes]) / Total Stop Time [Minutes]) * 100

Example:

Ai Dash Cam Exceptions

Ai Dash Cam Exceptions provides deductions based on Ai Video Based Events, such as Phone Utilization, Inattentive Driving, Following too Close, Potential Collisions Detected, or Forward Collision Warnings.

• Default Weight: 25%
• Event Types: Phone Utilization, Inattentive Driving, Forward Collision Warning, Following Distance, Potential Collision Detected
• Calculation(Based on Distance):

  Ai Dash Cam Score Score = 100 - ((Company Defined Deduction * Number of Recorded Events)/Miles Driven) * Company Defined Average Miles

• Calculation(Based on Time):

  Ai Dash Cam Score Score = 100 - ((Company Defined Deduction * Number of Recorded Events)/Driving Time[Minutes]) * 100

Example(Based on Distance):

Example(Based on Time):

Configuring New Operator Scorecards

1. Log into IntelliShift and navigate to Operator Scorecard Management.
2. Create a new scorecard, specifying its name, description, and assigned branches.
3. Set the company's average distance policy.
4. Configure each exception category, including event types, deductions, and weights.
5. Save the scorecard.

Tools of the Operator Scorecard

• User Are Able to set the exception points for each event within each category from 1-5 (Higher the Score, the larger effect it has on the operator score).
• Switching the Toggle Switch from On the Off
  • On: This Event if triggered will be used as part of the Operator's Score Calculation
  • Off: This Event if triggered will not be used as part of the Operator's Score Calculation. This will still record as an event within the Intellishift platform, though it will not be used as part of the scoring. 
• Branch Filter allows organizations to filter the scorecard which when running the report would automatically filter what branches within the organization would be scored against the scorecard
  • This is irregardless of your branch filtering within the report itself. setting the branches on the scorecard will only score the operators for time within assets within the defined assets that are assigned to the branches shared with the scorecard. 
• Is Priority within the Speeding Exceptions is used to determine how to handle if an operator exceeds both the High Speed and Posted Speed Limit threshold. 
  • No "Is Priority" Set: The Operator will be deducted from Both High Speed Limit as well as Posted Speed Limit Exceptions
  • High Speed "Is Priority" Set: The Operator will only be deducted for going over the High Speed Exception but not deducted for exceeding the Posted Speed Limit Exceptions 
  • Posted Speed "Is Priority" Set: The Operator will only be deducted for going over the Posted Speed Exception but not deducted for exceeding the High Speed Limit Exceptions 
• Averaged Distance allows organizations to to define the weighted distance that an operator's score is based off. This means that every operator will be based off driving the defined miles. 
  • This means that if the Averaged Distance is set to 500 Miles, but an operator has only actually driven 100 miles; this means that the operator's Events Per Mile will be multiplied by 5 as the platform is accessing that the operator's score will maintain the same over the next 400 miles.
• Assigned Weights allows organizations to define the custom weights per category. allowing Organizations to define how much an operator's score is based on each category.
  • If 25% of the Operator's score is based on a specific category, the operator's total score deduction will only be able to be reduced by 25 points. 
• Including Coachable Events / All Events; within the Ai Dash Cam category, users are able to determine what events from Ai Dash cam effect the Operator's Score. 
  • All Events: Any enabled event within the Ai Dash Cam Category regardless of the video status being defined as "Coaching Needed", "No Coaching Needed",  "Coached" or "New" will be counted as deductions 
  • Coachable Events Only: Any Enabled Event within the ai Dash Cam Category where the Video Status is set to "Coached" or "Coaching Needed" will be deducted from the Operator's Score. 
• Exclude PTO within the Idle Exceptions category is used to determine work related idle of an asset versus non-work related idling of a company asset. 
  • This does require the asset to be installed with Accessory Monitoring
  • Exclude PTO Enabled: When your Asset's Accessory is Engaged, and the idle threshold is exceeded it will not be used as a deduction against the operator's score. If your Asset's Accessory is Disengaged and the Idle threshold is exceeded it will be used as a deduction against the operator's score. 
  • Exclude PTO Disabled: When your Asset's Accessory is Engaged/Disengaged, and the idle threshold is exceeded it will be used as a deduction against the operator's score. 

Frequently Asked Questions

• What is the purpose of Advanced Operator Scorecards?
  • Advanced Operator Scorecards provide a more comprehensive and customizable way to evaluate driver performance by considering factors like distance, drive time, and stop time.
• What are the most common causes of accidents in fleets?
  • Common causes include speeding, distracted driving & fatigue,(Inattentive) Following Too Close,  and adverse weather conditions. Regularly analyze accident data to identify specific risks within your fleet.
• Why would a user choose to disable certain events from affecting a operator score? 
  • In specific industries or regions, certain events might be unavoidable due to unique operating conditions. For example, a fleet operating in a mountainous region might experience frequent harsh braking due to steep inclines and declines. Disabling this event from affecting the score can prevent unfair penalties.
  • Some companies may have specific policies or exceptions that warrant disabling certain events. For instance, a company might have a policy allowing drivers to idle for longer periods of durations as work extends from the site to the vehicle to finalize the work commitment and while int he vehicle the asset is allowed or required to idle. 
• How does the Score setting of an Event affect the operator's Score? 
  • Setting a Score of an event from 1-5 determines the point based deduction that happens when an operator triggers an exception. Since the Operator Scorecards are weighted, the deduction is taken in to consideration when it looks at the total time or Miles Driven, 
    • Example: 
      • If I Drive 100 Miles, and Trigger 5 Hard Braking Events with Each being a 1 point deduction, with a Averaged Distance of 100 Miles
        • Acceleration Score: 100 - ((1 * 5)/100) * 100 = 95
      • If I Drive 100 Miles, and Trigger 5 Hard Braking Events with Each being a 5 point deduction
        • Acceleration Score: 100 - ((5 * 5)/100) * 100 = 75.
  • Depending on the score of the event can determine the impact on the operator's score. 
• What happens if I change the Parameters of my Operator Scorecard? 
  • Intellishift's Operator Scorecards leverage Versioning, meaning that is a change is made to the Operator Scorecard Parameters, starting the day after those changes went into effect the new scoring will go into effect. 
    • Example: If I create a Scorecard on August 1st 2023, and on August 2nd 2024 I make a change and save a scorecard. Starting on August 3rd 2024 -> Future will be the second version of the scorecard. My Initial Scorecard will have the available dates of August 1st 2023 through to August 2nd 2024. 
• If a Change is Made to my Scorecard Parameters how will I know what version of the Scorecard is being used to compute 
  • Within Reports/Analytics that leverage Operator Scorecards, when Selecting the Scorecard you will see Scorecards with the same name but see next to the scorecard name the Start Date/ End date of the Scorecard Version. 
    • Current Versions of the Scorecard will have a (Start Date - ) with no defined end date
    • Versions that have been ended through a modification will have a defined Start and End date (Start Date - End Date)