Easy Driver Score
Introduction
EasyDriverScore is a comprehensive tool leveraging telemetry, telecommunications technology, hardware, software, and advanced algorithms to detect moments indicative of poor driving habits. These habits can endanger the lives of drivers and others, increase environmental impact due to excessive or unnecessary fuel consumption, and reduce the useful life of vehicles.
EasyDriverScore is designed to assist in driver education by identifying and highlighting these poor habits in an easy-to-understand manner. It analyzes data obtained through GPS hardware, ECU readers via the CAN bus, and ADAS and DMS sensors.
The primary objective of EasyDriverScore is to assist companies with vehicle fleets, vehicle and cargo insurers, and anyone interested in enhancing safety and fuel efficiency. By identifying and correcting improper driving habits, EasyDriverScore helps reduce fuel costs, spare parts expenses, and fines, while also contributing to improved safety protocols and a reduction in traffic accidents.
EasyDriverScore identifies and detects habits such as the following:
Road Safety:
- Speeding
- Aggressive braking and acceleration
- Drowsiness: detecting driving while intoxicated
- Fatigue: detecting overworking
- Distraction
- Aggressive cornering
- Not wearing a seat belt
- Smoking, eating, or drinking while driving
- Not using turn signals when changing lanes
- Driving too close to other vehicles (tailgating)
Vehicle Misuse Leading to Excessive Wear and Fuel Consumption:
- Idling (having the engine running while the vehicle is stopped for long periods)
- Bad driving habits
- Over-revving
- Clutch misuse
- Excessive braking
- Aggressive use of the accelerator pedal
- Misuse of the gearbox
Operation:
EasyDriverScore utilizes the following to assess drivers:
- Identification: Various methods can be employed to identify a driver, ranging from hardware such as RFID and iButtons to manual identification via the Pegasus Gateway Monitoring platform. Identification is optional and serves to evaluate drivers who use different vehicles. When a single driver is assigned to a single vehicle, identification is optional.
- Distance Traveled: Measuring the distance traveled is crucial for assessing the impact of poor driving habits. This metric provides quantifiable data on the extent to which a vehicle has been driven under conditions influenced by adverse driving practices.
- Ignition Time: Measuring the duration for which the engine remains running while the vehicle is stationary is essential for evaluating the impact of ignition time on driving habits. This metric quantifies instances where drivers unnecessarily idle their engines, contributing to increased fuel consumption, emissions, and engine wear.
- GPS: Through any GPS device, EasyDriverScore detects the following Types of Events:
- Aggressive Accelerations: Accelerating more than 11 km/h within one second is considered aggressive driving, indicating unnecessary fuel consumption.
- Hard Brakings: Decreasing speed by more than -12 km/h within one second is classified as hard braking, indicating aggressive driving due to issues such as speeding, distraction, or following too closely.
- Aggressive Turns: Executing an open curve (50° to 70°) or a sharp curve (70°+) at speeds exceeding 24 km/h and 50 km/h respectively is considered aggressive turning. Such maneuvers pose risks of skidding and rollover.
- Idling Events: Being stationary with the engine running for more than 5 minutes signifies unnecessary fuel consumption.
- Speeding Detected by GPS: Speeding incidents detected based on GPS device settings, used to alert excessive speeds for various vehicle types or critical operational points such as hazardous curves, when combined with geofencing configurations in the GPS device.
- Speeding Events Detected via Road Speed Limits: Exceeding posted speed limits read from private sources or crowdsourcing:
- Moderate Speeding: Exceeding the road speed limit by more than 10 km/h but less than 20 km/h, based on the actual published limit.
- Severe Speeding: Exceeding the road speed limit by more than 20 km/h but less than 30 km/h, based on the actual published limit.
- Critical Speeding: Exceeding the road speed limit by more than 30 km/h, based on the actual published limit.
- Events Read from the ECU: When incorporating data readings obtained via CAN bus from the Engine Control Unit (ECU) of vehicles, the following parameters can also be analyzed:
- Green Zone Driving Analysis: Refers to driving within the established RPM range deemed appropriate for engines, avoiding both under-revving and over-revving.
- Events Detectable by RPM Abnormalities:
- Coasting: Having low revolutions while moving is equivalent to going downhill with the gear in neutral.
- Excessive RPM and Low Torque: Low torque with high RPMs imply improper use of engine gears.
- Excessive RPMs in Motion: Excessive revs in motion may be due to misuse of the gearbox or aggressive driving.
- Excessive RPMs Idling: Excessive RPMs at idle can be related to the use of PTO, but it may also be improper use of the accelerator pedal when stopped.
- Overconsumption: Having a fuel consumption of more than 1.5% of the tank percentage in less than 30 seconds.
- High RPM and Load Above 15%: The revolutions should drop as the engine load increases. High RPM with a load of more than 15% implies improper use of engine gears.
- Brake Assist at Wrong RPMs: The engine brake must not be applied at low revolutions.
- ABS Activated at More Than 30 km/h: Activating ABS while moving involves sudden braking as seen from the engine.
- Events Detectable by Incorrect Pedal Use:
- Brake Pressed for More Than 10 Seconds in Motion: Long braking in motion causes wear of brake pads and discs, and unnecessary fuel consumption.
- Immediate Acceleration When Starting the Engine: Accelerating a vehicle right after starting it can lead to insufficient lubrication, premature engine wear, damage to the exhaust system, increased fuel consumption, and safety risks.
- Clutch for 10 Seconds with No Brake and Speed Less Than 2 km/h: When stopped, the vehicle must be put in neutral, press the brake, and release the clutch. Not releasing the clutch generates unnecessary wear on the clutch discs.
- Clutch Overload: Engine brake activated and clutch at more than 50%.
- Clutch Pressed for More Than 20 Seconds While Moving: It generates wear on the clutch discs and represents fuel waste.
- Clutch Pressed for More Than 30 Seconds at Stop: It generates unnecessary wear on the clutch discs.
- Events Detected by DMS:
- Fatigue Alert: Driver fatigue or drowsiness has been detected.
- No Driver: The camera does not detect the driver. This may be due to a change in position or obstruction caused by manipulation of the camera.
- Distraction: The driver stops looking ahead for prolonged periods.
- Telephone Use: Detection of phone use while driving.
- No Seatbelt: The driver is not using the seatbelt.
- Smoking Alert: The driver is smoking while driving.
- Food and Drinks: Consuming food and drinks while driving.
- Camera Tampering: Manipulation of the camera or its SIM card.
- Events Detected by ADAS:
- Forward Collision Warning: Risk of collision with a vehicle, pedestrian, or object in front.
- Vehicle in Front Too Close: Driving too close to the vehicle in front.
- Left Lane Departure Without Blinker: The driver does not use the turn signals to change to the left lane.
- Right Lane Departure Without Blinker: The driver does not use the turn signals to change to the right lane.
- ADAS Speed Limit Exceeded: The road speed limit detected by the camera was exceeded.
- Aggressive Lane Change: Aggressive lane change.
General Scoring Formula EasyDriverScore:
Having explained the factors affecting operation, as well as the events that identify poor driving habits, the formula used to score drivers is described below:
Where:
S= Score
Ei= Event type (Event types described in "Operation" Section)
D = Distance
Pi = Weighting Factor (It's a number from 0 to 10 that can be configured by the user
according to their preferences in the "Settings" tab of the application.)
= Correction Factor
n = Event types number
Updated 6 months ago