Improve Preventive Maintenance So the Interval Survives a Busy Week
Almost every fleet has a preventive maintenance plan. Far fewer have one that holds when a vehicle is needed on Friday and the service was due on Wednesday. KO Fleetz reads the meters itself, runs distance, hours and calendar triggers side by side, and makes the slip visible while it is still a decision rather than a failure.
Fleet and logistics operators run KO Fleetz in production
A late service is not a cheaper service
The intuition that kills PM programmes is that stretching an interval saves money. It feels true: a service done at fourteen thousand kilometres instead of ten thousand is fewer services a year, and the invoice agrees. The physics do not. Oil shears and loses viscosity on a curve rather than a cliff, and a filter that has reached its capacity goes into bypass and passes unfiltered oil straight to the bearings it was fitted to protect. You did not skip a cost. You moved it from the service schedule to the engine.
The second leak is the price gap between planned and unplanned work. The same repair costs one thing in your own bay on a Tuesday with the part on the shelf, and something else entirely on a hard shoulder at 9pm with a recovery truck, a premium part from whoever has one in stock, and a load that now needs re-planning. The work is identical. The circumstances are what you are paying for, and the PM schedule is what chooses the circumstances.
Then there is what a deferred defect does to an asset's life. A vehicle running on worn brakes destroys discs as well as pads. Misaligned steering eats tyres across a whole axle rather than one shoulder. Those bills arrive late and get attributed to the vehicle being old. Work out what your maintenance genuinely costs per kilometre with the free maintenance cost per km calculator, then compare your best-maintained vehicles against your worst.
Three clocks, and nobody can run three clocks by hand
Real PM scheduling is a first-to-occur rule: service at ten thousand kilometres, or three hundred engine hours, or six months, whichever arrives first. That rule exists because the three things measure different kinds of wear. Distance measures the road. Engine hours measure the load, which is why a tipper idling at a site all morning ages its engine while its odometer sits still. Calendar measures what degrades whether or not anybody drives, like coolant and brake fluid.
A spreadsheet can hold one of those clocks. It cannot hold three, because two of them need a live meter reading and a spreadsheet only knows what somebody typed into it last. So fleets quietly collapse the rule to whichever clock is easiest to read, which is almost always the odometer, which is the one that under-reports wear on exactly the assets working hardest. The plan on the wall says first-to-occur. The plan being executed is distance-only, and nobody has said this out loud. KO Fleetz runs all three clocks at once and makes the service due on whichever fires first, which is the first-to-occur rule the wall chart claims and the spreadsheet quietly abandons.
- The odometer figure comes from a driver's photograph, a fuel slip, or the last time the vehicle happened to visit the workshop. It is out of date before the row is saved.
- The 'due' column in the sheet does not refresh itself. It is correct on the morning somebody recalculated it and drifts from that moment onward.
- Engine hours are usually not tracked at all outside plant fleets, which puts the assets that idle hardest on the wrong schedule entirely.
- Calendar reminders sit in one person's mailbox. They go on holiday and the fleet skips a month with no record that it happened.
- A service pushed because the vehicle was needed gets rescheduled in someone's head. No artefact records that the interval was consciously stretched.
- Defects found during a service get fixed if there is time and deferred if there is not. The deferral is verbal, so the backlog has no age and no owner.
How KO Fleetz resolves this
The KO Fleetz modules that fix it
Improve Preventive Maintenance is not one feature — it is a few KO Fleetz modules working off the same records. These are the ones that carry it.
The workflow
Let the meters run the schedule
Step 1: Take the meter readings out of human hands
KO Fleetz takes odometer and engine hours off the telematics unit or the CAN bus continuously, so the schedule recalculates against real usage rather than against the last number somebody remembered to enter.
Step 2: Define the rule per vehicle class, not per fleet
A refrigerated trailer, a service van and a tipper wear differently and get their own trigger sets. Each task carries its own distance, hour and calendar thresholds, and fires on whichever lands first.
Step 3: Raise the work order before the vehicle is due
KO Fleetz opens the job far enough ahead that parts can be checked, reserved or ordered and a bay booked. The point of a preventive service is that nothing about it is a surprise on the day.
Step 4: Close the inspection loop
Defects raised on daily walk-arounds land in the same backlog as scheduled tasks, with an age and an owner, so a deferred item is a dated decision rather than a memory.
Step 5: Measure compliance against a stated grace window
Every fleet runs a tolerance. Write it down, then report what fell inside it and what did not. A compliance figure without a declared grace window is not a measurement.
What you use
The capabilities that do the work
Drawn from across the platform — this problem is not solved by one module.
First-to-occur trigger sets
KO Fleetz runs distance, engine hours and calendar simultaneously per task, and the service becomes due on whichever threshold arrives first. No clock is quietly dropped.
Automatic meter capture
Odometer and hour readings come off the device rather than off a slip of paper, so the due date is recalculated by usage instead of by whoever last did the maths.
Advance work orders
The job is created before the threshold, not after it, giving procurement and the workshop a window to have the parts and the bay ready.
Escalating service reminders
Approaching, due and overdue are three states with three different audiences. An overdue service reaches somebody senior enough to stop the vehicle.
Inspection defects in the same backlog
A fault raised at a walk-around joins the scheduled tasks in one prioritised list, so it competes for the bay on merit rather than on who shouted.
Parts demand from the schedule
Because KO Fleetz knows which services fall due next month, it knows which filters and consumables that implies. Stocking becomes a forecast instead of a reaction.
Tyre position and wear tracking
Tyres are tracked by position and rotation rather than by vehicle, which is what makes an alignment fault visible as a wear pattern across an axle.
Compliance and drift reporting
Reports show the compliance rate against your grace window and the average overshoot beside it, because a fleet passing on compliance can still be running everything late.
Cost per service task
Labour and parts are captured against the individual task, so you can see what a service actually costs and defend the budget with something other than an assertion.
In the product
What this looks like in KO Fleetz
What changes
The difference it makes
- Distance, hours and calendar run first-to-occur
- Three clocks
- The due date recalculates off usage, not memory
- Meters read
- A stretched interval becomes a dated decision
- Deferral named
- Compliance reported against a written tolerance
- Honest grace
How you will know it worked
Measure these
We publish no savings figure for your fleet, because we have not measured your fleet. These are the metrics that will move if this works.
| Metric | How to measure it |
|---|---|
| PM compliance rate within a declared grace window | Services completed on time divided by services due, where 'on time' means inside a tolerance you wrote down in advance. Publish the tolerance alongside the number or the number means nothing. |
| Interval overshoot | For each completed service, record the meter reading at completion minus the target threshold, then average it per vehicle class. Compliance tells you whether you passed; overshoot tells you how far you were creeping. |
| Deferred defect backlog age | Track open defects by days since raised, not just by count. A stable count with a rising age means the list is being managed by ignoring the old items. |
| Ratio of scheduled to unscheduled work orders | Split every work order by whether it came from the plan or from a failure. Watch the trend across quarters rather than the value in any one month, because a single bad week distorts it. |
| Services completed with parts already reserved | Count the jobs where components were allocated before the vehicle entered the bay. This is the practical test of whether the schedule is genuinely running ahead of the work. |
| Defects found per inspection | Track by driver and by depot. A driver reporting zero defects for months is not evidence of a healthy vehicle. It is evidence that nobody is looking, and it is the earliest warning you get. |
Put a number on it before you talk to anyone
The maintenance cost per km calculator is free, shows its formula, and asks nothing of you. Work out your own figure, then bring it to a demo.
Customer evidence
Fleets using KO Fleetz to do this
Customer story pending. A short, attributed quote from a fleet that used KO Fleetz for improve preventive maintenance belongs here — the result, in their words.
Frequently asked questions
This page is about how often a vehicle stops. That one is about how long it stays stopped. Preventive maintenance changes the frequency of outages through interval discipline, meter accuracy and defect follow-through. Downtime reduction changes the duration of an outage through parts availability, bay scheduling and approval speed. Most fleets need both eventually, but they are separate programmes with separate owners, and running them as one is how each ends up half-done.
You do, and the platform will not pretend otherwise. Intervals come from the manufacturer's schedule, your operating conditions, your regulator and your own failure history. A tipper on a dusty site needs air filters far more often than the handbook suggests, and no software knows your sites. What KO Fleetz does is execute the rule you define, against real meter readings, without forgetting. Choosing the rule is engineering judgement. Applying it consistently across two hundred assets is the part humans are bad at.
Yes, with a real trade-off you should understand before committing. Calendar triggers work with no hardware at all. Distance and engine-hour triggers need a meter reading from somewhere, and if that somewhere is a person typing a number, the schedule is only as fresh as the last entry. Manual readings are workable on a small fleet with a disciplined routine. They degrade badly with scale, because the failure mode is silent: nobody notices a stale reading, they just notice a service that was three thousand kilometres late.
No, and this is worth being blunt about. PM has an optimum, not a maximum. Servicing everything at half the recommended interval buys you more downtime, more labour, more consumables and more opportunities to introduce a fault by taking apart something that was working. The goal is hitting the right interval consistently, not hitting an aggressive one occasionally. If your unscheduled work is already rare and costs are still climbing, the problem is probably elsewhere and reduce fleet operating costs is the better starting point.
It does not fix it, but it does make it undeniable, which is the necessary first step. The platform records how long an inspection took, in what order items were completed, where the vehicle was, and how many defects that driver has raised over the last quarter. None of that forces anyone to look at a brake line. What it does is turn a suspicion held by the workshop manager into a pattern on a screen, and that is a conversation you can actually have. The rest is supervision, and no vendor should tell you otherwise.
It gets deferred, because that is the real world, and the platform expects it rather than pretending it does not happen. The difference is that KO Fleetz turns the deferral into an artefact: who authorised it, when, against which task, and how far past the threshold the vehicle then ran. That record turns interval stretching from an invisible habit into a visible decision with a name on it. Fleets that start recording deferrals usually find the count is much higher than anyone in the room believed.
Test your PM plan against your real meter readings
Send us one depot's service schedule and a month of telematics data, and we will run it through KO Fleetz to show you which vehicles are on the wrong clock.