Audience | Fleet admins |
Applies To | Fleet Dashboard > Safety |
Introduction
Motive dashcams capture driving patterns. These recordings are used to detect any violations with the help of AI. Moreover, few safety risk tags are manually associated with recorded violation videos.
Note: The following safety risk tags are only available to those fleets that have enabled the Additional unsafe behavior tags feature on the Fleet Dashboard. |
How safety risk tags help you
It helps fleet admins and fleet managers to:
- Stay updated with the violations of each driver
- Plan proper training for drivers to help them perform better
- Look at the driving and violation trends to make overall company performance better
Safety risk tags overview
Following are the violations managed using unsafe behavior tags.
Road facing tags
Lane cutoff
When another vehicle cuts off the driver by entering and occupying the driver's safe following distance, the video is marked as Lane Cutoff. It ensures the positive recognition of the driver’s action to quickly adapt to the situation on the road by changing lanes to avoid a collision.
Running a red light
FMCSA rules require drivers to make a complete stop at a red light on the stop line until the traffic light turns green. Hence, not stopping at a red light or stopping after the stop line causes a Running a red light traffic violation. Dashcams detect such events and mark the recording with this tag which the fleet manager and fleet admin can access.
Driver facing tags
In addition to the above tags, if you’re using the Motive Dual Facing Cameras, you can also see the driver facing tag(s).
Smoking detection
The FMCSA prohibits smoking within 25 feet of any vehicle carrying flammable materials or gasses. The Smoking Detection tag is applied to all scenarios where the driver is holding, smoking, or lighting a cigarette/vape. This tag serves to highlight the mentioned activities for the fleet manager.
Related Content
- How to turn on/off safety risk tags on Fleet Dashboard
- How to use the Adverse Driving Conditions Exception in the Driver App