We recently introduced driver-to-vehicle mapping. Now we support driverID buttons and readers to quickly allow drivers to identify the fact they are driving a vehicle. A really obnoxious alarm goes off in 30 seconds after ignition on if they forget this (optional — I left it off my vehicle…)
Here’s how it works:
You touch your driver ID button to the reader before or after turning the vehicle on. In dispatch, a list of all the “unassigned” driver IDs is shown (on the bottom). Note that my driver ID (Robert Donat) is assigned only to “Rob” at this time. The Driver ID reader is on “Rob 4000″ and I used that button earlier today:
After clicking “Assign Driver Button” you can now choose from a list of drivers — I choose myself:
Notice I am now listed on BOTH vehicles (really 2 different devices in the same vehicle, which is not typical, but there for our testing purposes):
Then that “unknown” button is no longer in the list of buttons to assign:
Now whenever I use a different vehicle, I can use my button on that vehicle and I will automatically be “assigned” to it for reporting/mapping/alert purposes.
We recently completed an API to achieve this as well.
This makes things much easier and more automated when assigning drivers to vehicles. That allows you to tell which PEOPLE are speeding, idling, using the vehicles off hours, getting parking tickets, etc. — not which VEHICLES.
Rob.



