Overview:
With the April 2021 release of IntelliShift, additional logic was added to the Operator Safety Scorecard logic. This enhancement provides the ability to factor in distance, drive, and stop times in calculating the Operator Scores. Operator Scorecards are now a summarized scorecard based on the number of exception events that occur within the defined period.
Key Changes:
- Driver Scorecards have been rebranded as Operator Scorecards following the standard naming conventions used elsewhere within the platform.
- Weighted Scorecards will show scores from 0 – 100 only. Scores can no longer be negative.
- The Operator Scorecard page has been updated to match the IntelliShift theming.
- A new ‘Advanced Configuration’ option has been added when defining scorecards.
- Points are deducted from the overall category score for each triggered event. Deductions amounts range from 1 to 5 points. The default value for all deductions is 1 point.
- Weighted Operator Scorecard are only available within the Data Analysis Reports at launch.
**If you are using Scorecards within Fleet IQ or In the Field, do not migrate an existing scorecard to the advanced logic. In this case, a new Operator Scorecard should be created.
Weighted Operator Scorecard Calculations(Advanced Configuration)
The Operator Scorecards logic has been expanded to provide a more flexible scoring system. In the default configuration, Operator Scorecards are a combined score calculated from three exception categories, Acceleration Exceptions, Speeding Exceptions, and Idle Exceptions. Each category can be configured and weighted to match the needs of each company. As a default, the Operator Scorecard uses the following calculation (The calculation of the operators score will change based on the weighting of the category):
Operator Score = 100 – (.3 * Acceleration Score) – (.5 * Speeding Score) – (.2 * Idle Score)
Acceleration Exceptions (Default Weight: 30% of the combined score)
Acceleration Exceptions capture rapid changes in G-Force and provides a score based on the number of measure exceptions compared to the company defined ‘Average Distance’. Three event types are included in the Acceleration Exception category:
- Harsh Braking
- Rapid Acceleration
- Hard Turning
Summary of G-Forces by Class:
Event |
Passenger Car (<10,000 lbs) |
Truck/Cube Van (10,001 - 26,000 lbs) |
Heavy-Duty (>26,000 lbs) |
Hard Braking |
< −0.61g |
< −0.54g |
< −0.47g |
Rapid Acceleration |
> 0.43g |
> 0.34g |
> 0.29g |
Harsh Turning |
> 0.47g & < −0.47g |
> 0.4g & < −0.4g |
> 0.32g & < −0.32g |
If desired, each acceleration type can be enabled or disabled.
The Acceleration Exception Score is calculated using the following equation:
Acceleration Score = 100 – ((Company Defined Deduction * Number of Recorded Events)/Miles Driven) * Company Defined Average Miles
Speeding Exceptions (Default Weight: 50% of the combined score)
Operators are scored based on the amount of time spent driving above the company defined speed threshold. There are two speeding event types that used to generate the Speeding Exceptions score, High Speed and Posted Speed (Requires SP Speed License). Both options allow for speed and duration threshold that must be crossed before an operator is speeding. Admins have the option to enable and disable Speeding Types as desired.
If an operator triggers both High Speed and Posted Speed events, both deductions will occur by default. When configuring scorecards, administrators can enable the Is Priority setting. If enabled, only the speeding event type with Is Priority selected will calculate when both thresholds are reached.
Speeding Score = 100 – ((Company Defined Deduction * Speeding Time [Minutes])/Driving Time [Minutes]) * 100
Idling Exceptions
Operators are scored based on the amount of time spent idling above the company defined duration threshold. The Idle Exception score is a comparison between the amount of idle time against the stop duration for the requested period.
If desired, site admins can exclude PTO Usage from the idle time calculation. If enabled and a PTO type event is engaged, the amount of time the engine is running without moving will not be included in the idle time calculation. By default, the ‘Exclude PTO Usage’ is not enabled.
When calculating the idle score, the following formula is used:
Idle Score = 100 - ((Company Defined Point Deduction * Total Duration of Idle time Above Company Threshold [Minutes]) / Total Stop Time [Minutes]) * 100
Assigned Weights
Category Scores support configurable weights that when combined with the other selected categories will produce an overall Operator Score. Each category will make up a percentage of the total score. For example, if a customer is heavily focused on Speeding Exceptions, they could set the Weight to 60. When the total score is calculated, Speeding Exceptions would make up 60% of the combined Operator Score.
At no point, can the total weight of the selected Exception Categories exceed 100. Using the above example, the Speeding weight is set at 60. All other categories cannot exceed 40. To adjust the weight, site admins can move the slider or enter the desired amount for each row.
When creating a new Operator Scorecard:
Configuring New Operator Scorecards
- Log into IntelliShift and select the Silent Passenger menu.
- Go to Tools -> Operator Scorecard Management.
- To add a new scorecard, select the ‘+’ icon.
- Enter a unique Name and Description for the scorecard.
- Selected the Branch(s) assigned to the scorecard.
- Scorecards are assigned by branch. All assets within the selected branch(es) will use the same scorecards.
- If no branch is selected, this scorecard will include all assets.
- Set the company policy for Averaged Distance. This distance will be used calculate the Acceleration Exceptions score. The default for this is 1000.
- Complete the configuration for each Exception Category.
- Acceleration Exceptions – The Acceleration Category scores drivers based on measured, rapid changes in acceleration. By default, the Acceleration Exceptions category makes up 30% of the total operator score. Current scoring metrics support three exception types. All options are enabled by default with a 1-point deduction per event.
- Harsh Braking
- Rapid Acceleration
- Harsh Turning
- Speeding Exceptions – Operators are scored based on compliance with the company policies for following speed limits. By default, the Speeding Exceptions category makes up 50% of the operator combined score. The scoring metrics are dependent on the features purchased by each company.
- High Speed – Operators are scored based on the amount of time spent driving above the company mandated limits for both speed and duration.
- Posted Speed – Operators are scored based on the amount of time spent driving above the company mandated limits for excessive speed and duration.
- Is Priority – If set, only the defined Speeding type will calculate if both thresholds have been exceeded.
- Idling Exceptions – Operators are scored based on the amount of time the asset is idling above the company defined threshold limits.
- Exclude PTO – allows admins the option to not include PTO usage in the idle time calculation.
- Acceleration Exceptions – The Acceleration Category scores drivers based on measured, rapid changes in acceleration. By default, the Acceleration Exceptions category makes up 30% of the total operator score. Current scoring metrics support three exception types. All options are enabled by default with a 1-point deduction per event.
- Adjust the Assigned Weights to define the company priorities for Operator scoring.
- When complete, select Save from the top, right portion of the screen.
- After scorecards are created, administrators can edit the existing options by selecting from the list and changing any desired fields and saving the changes.
- If desired, existing scorecards can be migrated to the Weighted Scorecard logic.
- Select the Scorecard by name from the Operator Scorecard Management list
- Set to the Enable Advanced Configuration setting to True.
- Make the desired changes and save the updated scorecard.
Helpful Hints:
- Changes made to scorecards, whether new or existing, are not retroactive. The new calculations will begin from that point in time forward.
- If a scorecard is migrated to the Weighted Operator Scorecard, there is no undo.
- All new scorecards must follow be Weighted Operator Scorecards. However, all existing scorecards can continue to be used without issue.
- If using Fleet IQ or In the Field with Operator Scorecards, do not migrate existing scorecards to a Weighted Scorecard. New Scorecards should be created in this instance.
- Operator Scorecards will only calculate scores between 0 – 100.
- When entering point deductions, enter 1 – 5 and positive values only.
- Defaults exist for all settings:
- Average Distance = 1000
- Point Deductions = 1 point
- Idle Minimum Threshold = 1 minute
- Minimum Speed Threshold = 25 mph
- Speeding Threshold over Posted Speed = 1 mph
- Category Weights
- Acceleration – 30%
- Speeding – 50%
- Idling – 20%
Comments
0 comments
Article is closed for comments.