Preventive Maintenance Scheduling That Survives Contact With the Road
A maintenance schedule only works if it counts the thing the wear actually follows. KO Fleetz triggers services on distance, engine hours or elapsed time, whichever arrives first for that vehicle, and records how far each service slipped past its due point.
The schedule exists. Nobody can tell you who is behind on it.
Every fleet has a service interval written down somewhere. The trouble starts when you ask which vehicles are past it right now. The answer lives in a workshop diary, a spreadsheet that one person updates, and an odometer reading that was accurate the last time somebody walked the yard with a clipboard.
So services drift. A truck comes in at 22,000 km on a 15,000 km oil interval because it was on a long contract and nobody wanted to pull it off the run. Nothing breaks that week, which quietly teaches everyone that the interval was too conservative anyway. Six months later the same unit is in for an engine repair that costs more than a year of oil changes.
The other half of the drift runs the opposite way. Vehicles get serviced early because they happened to be in the yard and a bay was free. That is not maintenance discipline, it is convenience, and it shows up as parts and labour spent ahead of need on units that were nowhere close to due.
Trigger on the meter that matches the wear
Different components wear against different counters. Brake linings track distance. Hydraulic pumps and generators track engine hours. Coolant and brake fluid degrade against the calendar whether the vehicle moves or not. A service task here can carry any of those triggers and fires on whichever arrives first, so a low-mileage tipper on a construction site is not treated like a long-haul tractor unit.
KO Fleetz reads odometer and hour-meter values off the telematics feed rather than a monthly walk-round, so the due point moves as the vehicle actually works. A unit that picks up a heavy contract becomes due sooner, visibly, and lands in the workshop plan before the interval is blown rather than after.
What this module deliberately does not do is predict component failure. There is no model here claiming a water pump has six weeks left in it. Condition-based prediction needs fault-code history and sensor coverage that most mixed fleets do not have on every unit. This is interval discipline done properly, which is both achievable and the part most fleets are still losing.
Capabilities
What KO Fleetz preventive maintenance gives your team
Multi-trigger service tasks
One task can be due at 15,000 km, 400 engine hours or six months, and fires on whichever threshold the vehicle reaches first.
Telematics-fed meters
Odometer and engine-hour readings arrive from the tracking device, so a due point reflects the work the vehicle did this week.
Service programme templates
Build an A/B/C service ladder once per vehicle class and apply it to every unit in that class, including the ones bought last month.
Schedule adherence tracking
KO Fleetz records how far past due each service was actually performed, so interval discipline becomes a number instead of an opinion.
Due and overdue forecasting
Projects upcoming due points from recent usage rate, giving the workshop a view of next month's load rather than this morning's surprises.
Automatic work order raising
When a service falls due, KO Fleetz opens a work order with its task list attached rather than waiting for someone to remember to write one.
Interval tuning by evidence
Compare oil analysis, defect findings and component life against the current interval before shortening or extending it.
Per-vehicle service history
Every completed service stays against the unit with its meter reading, tasks done and parts fitted, through to resale.
How it works
How KO Fleetz does it
Step 1: Define the programme per vehicle class
Set the task list and trigger for each service level. A 3.5t van and a 40t tractor unit share almost nothing, so they should not share a schedule.
Step 2: Bind vehicles to the programme
Each unit inherits its class schedule and its own current meter readings, including the offset for a vehicle bought part-way through its life.
Step 3: Let usage drive the due point
Distance and hours accumulate from the telematics feed. The due point moves toward the vehicles doing the work, with nobody re-keying a reading.
Step 4: Plan the bay, not the panic
The forward view shows what falls due over the coming weeks, so services are booked against workshop capacity and route availability together.
Step 5: Close and re-arm
Completing the work order stamps the actual meter reading and starts the next interval from there, not from where the service was theoretically due.
Outcomes
What changes
- Distance, hours or date, whichever lands first
- First-due wins
- Due points move with real vehicle usage
- Live meters
- Adherence recorded, not assumed
- Measured slip
- Workshop load visible weeks ahead
- Planned bays
Frequently asked questions
By all three, per task, and let the first one to arrive win. Distance suits brakes, tyres and driveline. Engine hours suit anything that runs while the vehicle is stationary, which is why a refuse truck or a crane wears its engine far faster than its odometer suggests. Calendar triggers catch fluids and certifications that degrade regardless of use. A single-trigger schedule always over-services one part of the fleet and under-services another.
Preferably from the telematics device already fitted to the vehicle, which reports them continuously. KO Fleetz also supports manual entry for units without a device, and readings can be captured when a work order is closed. The practical difference is that a telematics-fed meter keeps the due point honest between visits, while a manual meter is only as current as the last person who wrote a number down.
No, and that is deliberate. Predicting a specific component failure needs dense sensor and fault-code history across every unit, plus a model trained on it, and most mixed fleets have neither. What this module does is interval-based prevention executed reliably: the right task, on the right trigger, on every vehicle, with the slip measured. Getting that right removes far more unplanned downtime than a prediction nobody trusts.
Enter its current meter readings and the date of its last known service. The unit immediately shows as overdue against the programme, which is the correct and useful answer even though it looks bad on day one. Fleets typically work through that backlog over a few weeks. Suppressing it to make the dashboard green on launch simply hides the vehicles most likely to fail.
Yes, and most fleets should. Manufacturer intervals assume a duty cycle your vehicles may not have. Severe-service conditions such as dust, heavy idling, short urban trips or constant maximum load justify shorter intervals. Extending an interval is the riskier direction and should be backed by evidence: oil analysis results, defect findings and component life on the units you actually run. Warranty terms may also constrain how far you can move it.
Preventive maintenance defines the schedule and measures adherence to it. Service reminders are the delivery layer that gets a due item in front of a person before the date passes, and they also cover non-workshop dates such as registration, insurance and permit expiry. The two are built to run together: the schedule decides what is due, the reminder decides who hears about it and when it escalates.
Put a real schedule against your real meters
Bring one vehicle class and its current service intervals. We will put them into KO Fleetz against your live odometer feed and show you what falls due next month.