Fleet maintenance scheduling: from the calendar to real data

Every fleet has a maintenance schedule: services, inspections, insurance, end of lease. In most cases it’s a calendar — fixed dates, kilometre intervals set once. It works, but it’s blind to something that counts: how each individual vehicle is actually working. Moving the schedule from the calendar to real usage data is the first concrete — and least expensive — step towards predictive maintenance.

The classic schedule and its limits

The calendar-based schedule applies the same plan to the whole fleet: a service every X kilometres or every Y months, the same for every vehicle. It’s a big step up from “repair when it breaks”, but it carries the limits of preventive maintenance:

• It treats every vehicle the same, even if one works twice as hard as another or in tougher conditions.
• It relies on an estimate of mileage, often noted by hand, not on the real odometer reading.
• It lives in a separate file — a spreadsheet, a separate system — disconnected from what the vehicle is actually doing.

The result is the usual double error: you act on vehicles that don’t need it yet, and you get caught out by the ones working harder than expected.

The schedule on real data

The alternative isn’t to abolish deadlines: it’s to feed them with vehicle data. A schedule on real data calculates deadlines on the actual mileage and use of the individual vehicle — read directly from telematics, not estimated — and flanks them with the diagnostic alerts that arrive from the ECU.

Concretely, this changes:

• The service triggers when the vehicle reaches the real kilometres, not on a fixed date for everyone.
• An out-of-threshold parameter (battery voltage, tyre pressure) raises an alert before the scheduled deadline, if needed.
• Document deadlines — insurance, inspections, end of lease — live in the same place as the operational data, not in a separate file.

It’s exactly the function OptivoTrack covers: it manages schedules on real usage data, reads diagnostic codes and generates proactive alerts on deviations, across the whole fleet in a single view.

The bridge to predictive maintenance

Here’s the point: the schedule on real data is already predictive maintenance in its most practical and accessible form. It requires no artificial-intelligence models or failure histories: it requires reading the real mileage, the diagnostic codes and a few thresholds on the components that break down most often — battery, tyres, brakes.

It’s the step that takes a fleet from calendar-based maintenance to data-based maintenance, with no leap: you start by moving the deadlines onto real data, and from there you progressively add alerts on the critical components. The data source — OBD, CAN or Cloud OEM — you choose based on the fleet, as explained in which data you need.

The impact on fleet KPIs

A smart schedule isn’t a management nicety: it moves the numbers that count. Fewer unplanned breakdowns means a higher vehicle utilisation rate — one of the fleet manager’s key KPIs — and less vehicle downtime cost, the item where maintenance weighs most. On top of that, a tracked and consistent maintenance history protects residual value at resale or lease return.

Frequently asked questions