steveo wrote:
Barnsley wrote:
We went live with the EVO system this week. Got to say we are having a few problems. Like when the computer sends you a job for the town centre when you are ten mile away and there are plenty of cars sat empty in town. But the quality of work for me seems to have gone up which makes me think their must have been some serious feeding going on before.
Did you have data before EVO or id this you first one?
alway better to be a couple of zones ahead of where you are cos there nothing worse than the system being slow and sending you back to where you were 5 minutes ago. cos as we all know you can cover a lot of ground at 3 in the morning in not a lot of time.

The main reason for this sort of problem is the reporting times that are setup in the majority of data systems. There is only so many data transmissions that a data channel can take before it starts too slow down.
On some systems cars report back their position dependant on the following:
1. Free
2. POB
3. Allocated
On any system you would want the "FREE" cars to send in their postion more often than the cars that are allocated or POB. Then you have to decided on how often you want "FREE" cars to send back their position and a car miles out from your working area might not send in his/her position as often as cars that are in the main working area.
Other problems that happen on data systems is bad zone layout and its even worse when people try to make three zones join at one point especially things like major junctions and round abouts.
I have seen various data systems where one of the main problems has been the area layouts.
Anyway, does Evocab do closest car location and dispatch of work?