Five portals and a spreadsheet
One client uses one tracking provider, another uses a second, a third has a mix after buying a smaller business, and some vehicles have no tracker at all. Your team needs current mileage to plan services, locations to answer a fine or accident query, and harsh braking and speeding events for driver risk. Each answer means logging into a different portal, exporting a report and reformatting it.
Mileage for service planning is taken from whichever source someone remembers, and often from months-old readings.
Why telematics data stays in silos
Each provider's system is built for their own customers, not for a fleet manager with many clients.
- Each provider has its own portal, export format and definitions.
- A harsh braking event means different things in different systems.
- Vehicles are identified by the provider's unit ID, not always by registration.
- When a tracker is moved or replaced, the history splits.
- Access is per client, with separate logins held by different staff.
The cost of scattered tracking data
Service planning on stale mileage, so vehicles run overdue. Slow answers to fine and accident queries. Driver risk reporting that only covers some clients. And staff time spent exporting and reformatting instead of using the data.
The telematics data layer we build
- We connect to each provider's API with the access each client grants, and pull mileage, trips, locations and driving events on a schedule.
- Each unit is mapped to a vehicle registration and client, and the mapping is kept when trackers move between vehicles.
- Data is converted to one format: odometer readings, trips with start and end, and events grouped into common types with the provider's original label kept.
- Mileage feeds your service scheduling, lease mileage forecasts and replacement planning.
- Trip and location history is available to the fines and accident desks for a given vehicle and time.
- Driving events feed client risk reports, with a note of which provider each came from, since thresholds differ.
| Use | Data needed | Before | After |
|---|---|---|---|
| Service planning | Current mileage | Stale or manual | Daily from every provider |
| Fines and accidents | Location at a time | Portal lookup | One search by registration |
| Driver risk | Driving events | Some clients only | All clients, labelled by source |
| Lease mileage | Mileage trend | End of contract | Forecast throughout |
Being honest about differences between providers
Different trackers measure things differently, and pretending otherwise leads to unfair comparisons. The data layer keeps each provider's definition alongside the common type, and reports make clear when figures come from different sources. Vehicles without trackers fall back to fuel card odometer entries or driver submissions, and are marked as such. How tracking data is used, and what drivers are told about it, is for each client under their own policy.
One place to look, whichever tracker is fitted
Tracker swaps and new installations are handled as they happen. When a unit is moved from a sold van to its replacement, the mapping is updated with the date, so the old van's history stays with the old van and the new one starts cleanly. Units that stop reporting are listed each morning, since a silent tracker usually means a fault or a disconnected power supply.
When a client rings about a parking notice for a van on a particular afternoon, the fines desk types the registration and time and sees the van's trip that day, whichever tracker it has. When the service desk runs its weekly forecast, every tracked vehicle has yesterday's mileage. When an account manager prepares a risk report, the driving events for all of that client's vehicles are there, including those on the tracker brand that came with the business the client bought last year.
Your team stops logging into portals for routine questions. Mileage is current for every tracked vehicle, so service and lease planning improve. Fines and accident queries are answered in a minute. And when you take on a client with yet another provider, you add one connection rather than another portal to check.
Too many tracking portals?
- Your team logs into several telematics portals.
- Service planning uses mileage that is weeks or months old.
- Driving event data cannot be compared across clients.
- Tracker swaps break the vehicle's history.
- New clients bring new tracking providers every time.