A fleet manager's day often begins with the same question:
"Where is this vehicle right now?"
The answer looks simple. It isn't.
Three platforms, one question
The vast majority of fleet operations in Türkiye run on more than one GPS provider. The reason isn't preference, it's accumulation. Vehicles were acquired at different times, from different suppliers, under different deals. Each vehicle's tracking device comes from a separate company.
The result: a vehicle on Arvento isn't on Mobiliz. A vehicle on Seyir Mobil doesn't show up on GPS Buddy.
To look up a single plate, you log in to three separate platforms. Each has its own authentication, its own map infrastructure, its own search logic. One platform loads slowly, another has dropped the session, a third uses a different coordinate system.
Ten minutes later, what you end up with is an approximate location of uncertain reliability.
The real problem isn't location, it's infrastructure
The point that gets missed here is this: the problem isn't where the vehicle is, it's how that information is reached.
A location query shouldn't be an infrastructure problem.
The person running the operation shouldn't have to know which vehicle sits with which provider. That is a complexity the system should resolve, not the user.
The right setup
There should be a single search field. You enter the plate. The provider layer is completely abstracted away from the user. Which device a vehicle carries, and which company it came from, stays in the background.
The data that comes back is gathered on one screen:
- Location
- Speed
- Engine status
- Signal quality and last signal time
Query time: seconds, not minutes.
What changes?
The number of providers changes. Fleets grow, shrink, devices get renewed. None of this should be the concern of the person running the operation.
No matter how many pieces the infrastructure layer is made of, the point of control stays single.
You enter the plate, the answer comes back. The rest is the system's job.