What the Vehicle Itself Reports

Fleet telematics is sold on knowing where vehicles are. The return is almost entirely in knowing what condition they are in and what they cost.

What comes off a vehicle

Position and movement, which is the headline and the smallest part of the value.

Engine data from the diagnostic port or the CAN bus: engine hours, coolant temperature, battery voltage, fuel level, odometer.

Fault codes, raised by the vehicle's own systems before a driver notices anything.

Fuel or energy consumption, per journey rather than per tank.

Usage: how often the vehicle moves, how far, how long it idles.

Why the second list matters more

Position tells you where an asset is today.

The rest tells you what it will cost you this year — in fuel, in repairs, in downtime, and in when it needs replacing.

And it accumulates. A position record is worthless after a week; an engine hours figure compounds into a maintenance schedule and a replacement decision.

The reframing that changes the business case

Most telematics projects are justified on driver behaviour and route efficiency.

Both are real and both are contested, because they concern people and produce disputes.

Asset data is not contested by anyone. A fault code is a fact about a machine, a fuel figure is arithmetic, and neither requires a consultation or a policy.

Which means the least controversial data is also the most valuable, and it is routinely the part nobody configured.

What the data replaces

Service by calendar becomes service by actual engine hours or distance, which is what the manufacturer intended.

A driver reporting a warning light becomes a fault code arriving before the driver noticed.

A fuel figure from receipts becomes consumption per journey, which is where theft and inefficiency become visible.

An odometer read at annual service becomes a live figure, which is what a replacement decision needs.

What this collection covers

The data the vehicle produces, and which parts of it are usable.

Maintenance driven by condition rather than by date.

Fuel and energy, including electric fleets.

Utilisation, and the vehicles you are paying for and not using.

Whole-life cost and when to replace.

And the compliance obligations that attach to vehicles rather than to drivers.

What it does not cover

Driver monitoring, dispatch, proof of attendance and the privacy analysis that attaches to tracking people.

Those are a separate subject with a different legal weight, and conflating them is how a fleet project becomes an industrial relations problem.

Who this is for

Three audiences with different reasons to be here.

Whoever runs a fleet and has been asked to justify a telematics purchase, or to explain why the last one delivered nothing.

Whoever signs the cheque, for whom the whole-life cost figure matters more than the feature list.

And the drivers, whose cooperation determines whether devices stay plugged in — which is why the boundary between vehicle data and personal data gets its own note.

Turn the boundary into a test

For a concrete product reference, time tracking software for mobile work can help turn this boundary into a test. Verify the current behaviour with representative fields and record what reaches the destination.