The Four Things

Fifty notes reduce to four actions. In this order, because each depends on the one before.

One: get the register right

Every vehicle: registration, VIN, model, acquisition, finance, site, assigned device.

Delivers: the ability to attribute anything to anything. Without it every per-vehicle figure is unreliable and every replacement decision is a guess.

Costs: an afternoon, and discovering that the register is wrong — which it usually is.

Two: read the vehicle, not just its position

Odometer, engine hours, consumption and fault codes, from the CAN bus where the value justifies the installation.

Delivers: everything else in this collection. A position-only deployment has bought a map.

Costs: an installation per vehicle, which is the decision most fleets get wrong to save a small amount.

Three: service by usage

Triggers on actual distance and hours, with lead time, feeding the maintenance system automatically.

Delivers: the end of over-servicing the light users and under-servicing the heavy ones, and the fall in unscheduled repairs that the business case rests on.

Costs: a conversation with the workshop about rolling demand, which is an operational change more than a technical one.

Four: assemble whole-life cost

Per vehicle, annually, including downtime.

Delivers: replacement decisions from a curve, purchasing decisions from evidence, and the number that justifies everything else.

Costs: a spreadsheet and an afternoon a year.

What these four do together

They convert a fleet from a set of assets someone maintains into a set of assets somebody understands.

None of them requires driver monitoring.

None of them requires consultation or a monitoring policy.

And a fleet with all four is in better condition than most that have just completed a telematics rollout, which is the honest summary of this collection.

What they do not cover

Dispatch, routing, proof of attendance and the safety of people working alone, which are real uses of position data with their own analysis.

They are a separate subject, and deciding on them separately is the point.

A practical configuration prompt

During configuration, use see how the platform works to prompt questions about identifiers, ownership and output. Treat the page as a starting point and document each assumption.