Avatar

Driver Feedback / Driver ID

0

A couple questions about Driver ID.

1. With the feedback turned on I know that it just times out and starts beeping after the vehicle ign has been off for the designated time, does the go device forget the driver also?

2. If a driver logs into multiple vehicles (for example, construction company warming up tractors before employees come in to take them) after the driver ID is inserted into the second vehicle, does the first vehicle "forget" or "logout" the driver's ID?

 

Garret - Fleet Profit Center

Please sign in to leave a comment.

11 comments

0
Avatar

1. It records the driver records.  You set how long you want the device to "remember" the driver by setting the "Enable driver identification reminder" to a length of time you want the device to "assume" the same driver is driving the vehicle.  Otherwise the driver should be "Unknown".

2. No it does not work that way.  You need to define "forget" in your terms.  The data is always kept for records.

It sounds like you are mixing up your information.  I get the impression you are referring to the Map showing you who is "logged" into a device.  In that case the Map will routinely show you who last logged into the device even though they are not currently in the device.

Michael Head 0 votes
0
Avatar
1. Not a clear answer. Is that a long winded yes that it "forgets" or logs the driver out once the time limit expires (by changing it to "unknown")?

2. Also not a clear answer, to re word the question, if one driver id fob is used to log in to multiple vehicles within a few minutes of each other, will all three vehicles show the same driver id logged if no one else uses their id fob after? So basically data is all attached to the one driver for three vehicles.

Side note: please try and refrain from assuming things. It can be taken as an insult by some. I was not mixing information up between screens like the live map. My questions were directed strictly to driver id functionality and the outcome of the above mentioned questions. If you needed clarification please ask instead of assuming implied directions. The live map is simply a side affect of what my questions are about but that wasn't the goal of my questions.
Garret - Fleet Profit Center 0 votes
0
Avatar

Garret,

Most people's questions directed toward this are related to how the map shows the user as logged in when they currently are not.  There was a feature request submitted to try to not list the user if they were not currently logged in.  I have not heard of any results since it was submitted.

I was most definitely not insulting you and I am sorry that it came across that way. 

1. Once the device ignition is off for over the time that is set in the "Enable driver identification reminder".  The driver should be considered logged out.  Yes you may see it on the map with that user after that until someone else has logged in.  You may also still see the user in reports on the device even though the user was not currently logged into the device such as Exception reporting.  So it is possible that a report could be produced that listed the driver that last logged in even though that driver was not driving at that time after supposedly being logged out.  I have seen this in 5.7 databases with the NFC reader.  I have a device here that was being used with the NFC reader.  I later turned off the driver feedback.  That was over a month ago.  The device still reports as if the old driver is driving the vehicle.

Now I have also seen the driver report as "Unknown" like it should in some other 5.7 databases. 

I also submitted a question regarding this issue.

So there is no clear answer to your question as it is possible you may see both scenarios.

2. Yes it will record the same user in the logs.  If a driver logs into a different device, there is no logging out of another device.

To recap: It is most definitely possible for a user to be logged into more than one device.  It is also possible for a user to be reported as a driver when they really are not driving.  I questioned this also.

To get this question cleared up I would recommend you call Geotab support and let them explain it to you in their words.  I have proof of both scenarios I gave you in question 1. 

 

 

Michael Head 0 votes
0
Avatar
Based on the over all answer it seems you aren't with geotab support whom I thought was answering...

1. I have seen both scenarios also (ps I am a reseller, and former client pushing 5 years exp with geotab products) but haven't ever really gotten a clear explanation of the driver id staying logged in or not when the notification time limit expires in the feedback area for a device. I guess all in all it would make the most sense for it to change the driver to unknown automatically when the time limit expires. I'll throw that in a feature request. I have only seen this with the USB keys. Have not tested with NFC yet. But maybe I will make a point of it next week.

2. I guess crowd sourced concurring wins out on that. So I appreciate the confirmation it's not just happening to our client.
Garret - Fleet Profit Center 0 votes
0
Avatar

Garret,

I am an Authorized Technology Partner.  I am with Fleet Hoster.  I am an integrator and I work with the Geotab SDK every day.  I have access to multiple databases across different resellers and I can tell you that what I said is true.  When I get bored, I answer all the questions that don't have answers on the forum until I am tired.  LOL.

I first questioned this with the green key fobs that were used with the Go4 devices.  Now I am seeing it in 5.7 also.  I could never get a clear answer to this either.  I can tell you that the records are stored as "DriverChange" records in the database.  There is no real "logging out" record.  It just records when the NFC reader recorded, the device, and driver.

I wish that Geotab would record a "DriverChange" when the ignition is off and the "Enable driver identification reminder" time has passed.  They should record a "DriverChange" record with the time, device, and "Unknown" user.  That would solve all of this as far as I can tell from the data we can see.

Please submit a feature request.  Copy the above about my recommendation if you want to.

You can visit my site at FleetHoster.com.  I work with resellers to help integrate customer's systems and also to extend Geotab's offering.

Thanks, 

Michael

Michael Head 0 votes
0
Avatar

Hi Garret,

Here are some answers to your questions which may hopefully clear things up:

1. With the "Enable Driver Identification reminder" turned on, the GO device drops the driver ID based on what time you set for this feedback after ignition off. For example, if you set this feedback for thirty seconds, the GO device will drop the driver ID 30 seconds after you turned the ignition off. To clarify about the beeping, whenever you turn this feedback on the device will beep whenever the vehicle does not have a driver ID and has the ignition turned on. Using the previous example again where you set this feedback for 30 seconds, when you use the key you will have 30 seconds to turn on the ignition. If you fail to to turn on the ignition by 30 seconds, the GO device will beep because the GO device would have dropped the driver ID. 

2. The only way a device will drop the driver id is to have the "Enable Driver Identification Reminder" turned on, and turn off the ignition for the vehicle for the amount of time set for this feedback. So if you used the driver key on one vehicle and then use it again on another vehicle, the first vehicle may not drop the driver ID. With that being said, if these two vehicles were in the same database and the keys were used on vehicle one, and then on vehicle two shortly afterwards. What happens is that the database will dissociate the trips with the driver for vehicle one because the key was last used on vehicle two. The database will take note of which vehicle the driver key was used last and will associate the driver to the vehicle where the key was used last. 

Dom 0 votes
0
Avatar

Dominic,

On number 2.  I went out and tested this after this discussion.  I was able to release the driver from the device only after turning the enable driver identification reminder to on.  So this is true and required.  (Be nice to have note of this somewhere).

Can you please explain why the map will show the driver who last used the device even if it has been months?

Can you please explain why a device that was using NFC, then turned off driver identification reminder, but still shows as the old driver?  Seems like the Geotab software should automatically disassociate the driver from the device in this case also?

I can see this on a database now where the driver is being recorded on exceptions and reports and the driver has not logged into the device for over a month.  This is definitely false reporting and could be possibly used against an employee when the employee was not involved.

Michael Head 0 votes
0
Avatar

Mike,

You are right that there should be an explanation somewhere in the Product Guide, it is just such an old feature (that has not changed) that most resellers are well aware of how it works.

The way that MyGeotab associates a driver to a vehicle for trips, exceptions, etc is based on the key insert logs; last key insert log will dictate what vehicle the driver is associated to.

There are two main reasons why it does not automatically disassociate the driver from the vehicle if you do not have driver identification reminder enabled:

1. For a company to properly enforce driver-vehicle association it is logical that the driver identification reminder be enabled as the drivers would need some kind of warning/reminder to use them or, if used in conjunction with the hrn-relay kit, even impede ignition all together if the driver ID is not used.

2. There is no one right answer as to when to disassociate a driver from a vehicle, should it be after ignition off? At the end of the day? At the end of the week? month? Maybe it should be by shift, but how do you define a shift?  etc.

The above two reasons are also valid when you say these are false positives or stating that it could be used against an employee.

Mauricio Muniz 0 votes
0
Avatar

I agree.  If the sytsem is used properly it would all work nicely.

Thanks.

Michael Head 0 votes
0
Avatar

Not sure if my question is directly related, but our question is regarding updating past history records with Driver ID.  We are currently using GetFeed to populate an external database with historical information (GPS, trips, exceptions, etc).  We are finding some records are not associated with drivers (Ie, driver forgot to use key fob to "login" to the vehicle on a given day or for a given part of the day).  So we are now looking for best way to capture Geotab record updates when our customer end users update Trips History  (left click on the Star and select "add driver").  

 

Can someone point us in the right direction to identify when these prior trips history records are updated in Geotab by our customer end users so we can isolate and pull those updates into our external database?  Is this also done through GetFeed?

Justin Moyer 0 votes
0
Avatar

Justin,

I don't think Geotab updates any prior trips with the driver to that vehicle.  If Geotab is adding a "DriverChange" record at the time a person assigns it on the map, then it would apply to any future trips for the vehicle.  You can update the driver Id for a trip in history directly in the SDK but you may have to reprocess the data in the database so that the exceptions relating to those trips have the driver Id.  For the most part, when assigning a driver it is for any "future" trips for that vehicle.  Call Geotab support and speak with Siam or Jason Widla.

Michael Head 0 votes