Geotab already counts every mile your fleet turns. AssetOS will read those odometer and engine-hour figures and service each vehicle on how hard it actually worked — not on a date somebody typed into a spreadsheet in March. In build now, with the first fleets live in September 2026.
Geotab records every kilometre, every engine hour and every fault code your fleet throws. Then someone copies a number into a spreadsheet on a Friday — if they remember. Service intervals get estimated, the busiest van runs 4,000 miles past its oil change, and the first hard evidence of a problem arrives on the back of a recovery truck.
AssetOS reads four values from the MyGeotab API — odometer, engine hours, position, and engine fault codes — and turns them into maintenance your workshop can act on.
Odometer and engine hours count against the service interval on each vehicle record. At 90% of interval the work order is drafted; at the interval it is in the workshop queue with parts attached.
A DTC from Geotab raises a work order against the right vehicle with the code, description, and time it first fired. Severity rules decide what reaches the queue and what stays a note.
Last known position and home depot sit beside the certs, service history, and open work orders — enough to schedule a job without three phone calls.
Distance and engine hours arrive from Geotab and post to the meter on the AssetOS asset record. Preventive maintenance schedules read that meter, so an oil change lands at 10,000 miles because the vehicle covered 10,000 miles — not because it's the first Tuesday of the quarter.
Engine fault codes reach the workshop queue the same day they fire, attached to the vehicle that threw them. Pair that with driver walk-round checks already running in the AssetOS mobile app and the workshop sees both halves of the picture: what the engine reported and what the driver saw.
Most CMMS vendors list a telematics logo and let you assume the rest. Here is the boundary of version one, in plain terms. If something on this list is the reason you'd switch, tell us — it moves up the queue.
Version one reads from MyGeotab and pushes nothing back. Two-way sync is on the list, but a read that works beats a write that surprises you.
Live tracking, routing and driver scoring stay in Geotab, which does them better. AssetOS keeps last known position for scheduling context — that's it.
Not in version one. AssetOS runs its own walk-round checks with photo evidence today, so you're covered — it's just two apps rather than one until we get there.
If the data reaches the MyGeotab API, we can read it. If your device or plan doesn't expose it, we'll say so on the call rather than after go-live.
Meter readings drive preventive maintenance in AssetOS today. The Geotab connector automates where the numbers come from — it isn't what makes the schedules work.
Pull an odometer report out of MyGeotab, import it against your asset records. Monthly takes about ten minutes for a 100-vehicle fleet.
The same endpoints our mobile app uses. A scheduled job that reads MyGeotab and posts meter readings to AssetOS is an afternoon of work — we'll help you wire it.
Drivers and technicians enter readings from the mobile app — scan the vehicle, type the number, done. Works offline, syncs when signal returns.
Early access fleets decide what version one gets right — which fault codes matter, which intervals break, which report the depot manager actually opens. Join the list and you get the connector first, plus help wiring the API version up in the meantime.
Not yet — the native Geotab connector is in build, with the first fleets going live in September 2026. It reads odometer, engine hours, GPS position and engine fault codes from the MyGeotab API into AssetOS asset records. Early access fleets get it first. Today you can move the same data across with a CSV import or the AssetOS REST API.
Version one reads four things: odometer, engine hours, last known position, and engine fault codes (DTCs). Odometer and engine hours drive usage-based preventive maintenance. Fault codes raise work orders. Position lands on the vehicle record so you can schedule against where the vehicle actually is.
No. Version one is read-only — AssetOS pulls from MyGeotab and pushes nothing back. Two-way sync is on the list, but we would rather ship a read that works than a write that surprises you.
Yes. Geotab tracks vehicles — position, driver behaviour, routing. AssetOS maintains them — work orders, preventive maintenance, certs, parts and cost. The integration connects the two so mileage recorded by Geotab triggers the service AssetOS schedules.
No. It is included on paid AssetOS plans with no telematics add-on. Operator and requester seats stay free, so drivers reporting defects never count against your bill.
Yes — today by logging meter readings on the mobile app or importing them, and once the connector ships, automatically from Geotab. Intervals can run on distance, engine hours, or date, whichever comes first.
Geotab is first because our fleet customers asked for it first. It is built on a shared meter-reading pipeline, so other telematics providers follow the same path. Tell us which system you run and it goes on the queue.
We use cookies to analyse site traffic and improve your experience. Read our cookie policy