In the event that there is more than one assignment type for a vehicle, Samsara uses hierarchy logic to determine which driver to assign to the vehicle for use in trip histories and vehicle trips. If more than one driver has a Driving status during a trip, the driver with the most drive time is assigned to the trip history. The driver assignment will impact events such as fuel efficiency reporting and safety event associations.
For compliance reporting, Samsara uses only compliance-based assignments, such as tachograph or assignments created in the driver app from HOS logs.
The following table summarizes assignment types in order of priority from 1 (highest priority) to 8 (lowest priority):
|
Priority Order (Highest to Lowest) |
Assignment Type |
Description |
|---|---|---|
|
1 |
API Driver |
If you have a separate system to track driver assignments, your API configuration overrides driver assignments |
|
2 |
HOS Driver |
Autoduty and Samsara Driver App Assignments |
|
3 |
Tachograph Driver |
Tachograph device assignments (EU only) |
|
4 |
Manual Driver |
Manual Driver Overrides, derived from Safety Inbox interactions and the Trip History Report |
|
5 |
RFID Scan |
For RFID scanner installations, assignments derived from RFID scanners |
|
6 |
BLE Scan |
Assignments from low-power Bluetooth devices, such as Trip Card, Driver Card, or Driver Token |
|
7 |
Static |
Driver and device assignments made in the Samsara dashboard |
|
8 |
Camera ID / Face ID |
Assignments detected with the Samsara Dash Cam using facial recognition |
