Driving Behavior

The safety and efficiency of your fleet drivers can make or break your bottom line. Zendrive SDK was built to give fleet managers insight into the quality and safety of their drivers based on detailed driving behavior.

Zendrive accesses phone sensor data with the trip time and place to identify safe and risky driving. By doing this, Zendrive allows fleet managers to take action before poor driving becomes a liability.

Events

Zendrive SDK detects a trip on the driver's smartphone and collects sensor data throughout the trip. It is capable of detecting the following trip events:

• Hard brake

• Hard turn

• Over-speeding

• Phone use

• Phone screen interaction

• Rapid acceleration

• Hands-free phone calls

• Soft distraction (user's phone screen is not but the user is not actively interacting with the phone)

These events lend themselves to user's driving behavior analysis, which helps Zendrive create the user's driving-style profile. Customers can use this driving-style profile to incorporate specific training and re-learning practices to help drivers become safer.

The following driving events do not affect scoring:

• Hands-free phone calls.

• Soft distraction.

Scores and Event Ratings

Zendrive employs state-of-the-art data analysis and machine learning algorithms to compute various driver-behavior scores. The overall Zendrive Score is expressed as a number between 0 to 100, with a higher value corresponding to better driving practices.

Drivers are also rated on individual driving events, which are on a scale from 1-5, with 5 being the highest. In a customer-facing application, this can be expressed as a number or letter grading, or a star rating.

A value of -1 for an event rating indicates that the driver or the trip cannot be rated on that particular event. This happens most often for the 'Phone Use' rating for drivers with phones that do not have gyroscope sensors, which are necessary to detect phone use events. In these cases, the Zendrive Dashboard displays NA instead of a letter grade for the phone use score, and the overall Zendrive score is calculated from the remaining events, without consideration of phone use.

As of Zendrive SDK v9.2.0, the following changes have been made to distracted driving detectors:

• A minimum event threshold of 10 seconds, aimed at reducing spurious passive distraction events. This minimum event duration applies to all distracted driving events.

• Distracted driving events are now mutually exclusive with the following priority order for detection.

  • Hand-held phone calls

  • Hands-free phone calls

  • Active distraction

  • Passive distraction

• From SDK v9.2.0 onwards, it is possible to correctly identify the hands-free and hand-held portions of a continuous phone call event.

How to Use

1. Integrate the Zendrive SDK - Android, iOS.

2. Collect information via trips and test drives, or use our testing framework.

3. Log in to the Zendrive Dashboard and locate the trip.

4. View the driving events, the trip score, and other relevant information.