The system will automatically detect that a driver has a new driver card and will associate the new HOS data with the correct driver.
When a driver renews a driver card only the last two digits of the 16-digit driver card number will change. The MiX system only looks at the first 14 digits of the driver card number to check if it is an existing driver or to create a new driver. Thus, when a driver renews their card, that specific card will still be associated with the existing driver.
How this previously worked:
- Old driver card: DB06102167224103
- New driver card would be: DB06102167224104
The last 2 digits are incremented and new trips would be linked to the new driver card. The driver's data would have to be merged, which was a time consuming operation.
What is reported now:
- Old Driver Card: DB06102167224103
- New Driver Card issued: DB06102167224104
However, MiX Fleet Manager will still show the details of the originally entered driver card ending on the '03' as in the example above, i.e, DB06102167224103. At a high-level, the revision number on the card is ignored so the data will always be mapped to the same driver regardless of the revision number.