Seems it could matter. Theoretically, in 6 minutes you could be up to 5 miles from the represented location. This could make dispatching an OCA to the closest driver rather difficult.
Is this delay showing a continuous 6 minutes "off" or is it a "snapshot" taken every 6 minutes?
Combine that with the fact that there were locations on my area that had no cellular service (delaying diad messaging) and you could be a long way from where it would be feasible to get this OCA.
P-man.....you got any input on this?
Yes....
The DIAD is sending up things to the database all the time after a delivery.
If your DIAD didn't send anything for some amount of time (I think 14 minutes, it will send up a message saying where it is.)
The center screen refreshes every 10 minutes I think.
So, for some stops, its only 2 to 3 minutes delayed. For others, it could be as long as 20.
The center's PC screen shows the delay for each driver, and can use this for the decision process.
I think the key here, and this is what I teach is to not look at where a driver is. Not look at what area they cover. But instead look at where they will be.
This is why they show the uncompleted stops on the map. The map shows the non-dispatched ODS stops and they can see who is going to be there.
If its off by 5 minutes, that's really not a problem. Also, I think there is a way to force a refresh if its needed.
Finally, they told us that the parameters (refresh time of 10 minutes and 14 minutes no transmit upload) are configurable. If needed, they can make them closer to real time. They are trying to reduce cost for hardware and telecommunications.
By the way, a warning.....
Some drivers in my area have figured out that they can turn off communictions in the DIAD so the ODSe system doesn't know where they are.
Please don't do this. The systems can track this and they will be sending us reports on who is doing this. Don't get in trouble over this.
P-Man