Driver identification means that the current active driver is identified and linked to all the trips, positions and events that are recorded on a specific asset.
To start identifying drivers and linking them to trips and trip information in MiX Fleet Manager you need to:
- Create a driver in MiX Fleet Manager.
- Compile and upload the configuration.
- Create the driver plugs using the Plug Management Utility (PMU).
How does blue plug identification work?
- A driver inserts the driver plug/key into the code plug socket in the vehicle.
- The unit reads the driver ID from the plug and checks if the ID is in the plug list.
- If the ID is in the plug list, an event is generated stating that the driver has been identified.
- All events and AVL's that occur during the trip will be associated with that driver.
If the driver is not identified the unit will sound a long beep after the plug has been inserted - this can occur if the driver ID is not in the plug list or the driver does not have the right access control permission.
Driver cards - Extended driver ID
The steps to use extended driver ID for driver identification is the same as above (i.e. create driver, compile and upload config) but you will not need to generate a driver plug as the extended driver ID will now be used to associate trips and events with the driver.
The driver will instead tap the driver card on the extended driver ID reader to identify themselves, the serial script associated to the extended driver ID reader will read the extended driver ID and try and match it to an extended driver ID in the extended config driver list.
If the driver is matched successfully, all events and AVL's that occur in the trip will be associated to that specific driver.
If no match is found, one of these scenarios can occur depending on the settings on the serial device:
- Unknown Extended Driver IDs will disarm unit, and be matched to a known driver during the data download: If this is checked the driver can disarm the vehicle and at the end of the trip when the trip is processed, the system will check if the driver is an existing driver in MiX Fleet Manager and all passive data will be matched and associated to a known driver during the data download.
Click here to read more on how to set this up. - Actively lookup Unknown Extended Driver ID to facilitate matching to a known driver: If this is enabled, all active events that come in will have that driver associated, meaning this happens during (actively) and not at the end of a trip. An active call will be performed even though the ID is not in the driver list and will associated the relevant driver with these events. Please note however that the DTCO Driver ID cannot do active lookups.
Smartcard / Dallas tag
The driver's unique extended ID can be a hexadecimal number (allowed digits are 0-9 and A-F) of up to 32 characters used to identify the driver to certain third parties.
You have to enable the extended driver ID feature to make use of smartcard readers or the Dallas tag driver identification.
Click here to learn more about using smartcard readers / Dallas tag.
DTCO driver
In 2019, regulation came into effect stating that second generation recording equipment shall be installed in vehicles registered for the first time, which means that vehicles must be fitted with a smart tachograph connected to a positioning service based on a satellite.
navigation system.
The DTCO shall record the driver / workshop card status in relevant smart card slots as the card status for such slot.
The driver identification number for the digital tachograph (DTCO) is 16 ASCII characters.
Please note: Server-side matching only works on extended driver ID and not on DTCO Driver ID. Driver card renewals is for DTCO driver ID and server-side matching is for extended driver ID.
HOS driver
HOS (Hours of service) refers to the maximum amount of time drivers are permitted to be on duty. Logging in as an HOS drivers, assist drivers to comply with the HOS regulations specific to them.
Drivers logging in as HOS drivers will use a red plug to identify themselves.
Default driver
You can set a default driver on an asset from either Fleet Admin/Assets/Access Control or Fleet Admin/Driver/Access Control to either add/remove drivers from an asset or add/remove assets from a driver. Click here to learn how to set a default driver on a specific asset.