A fleet preventive maintenance program is not a stack of service reminders — it is a system. Group the wrong vehicles together, trigger on the calendar when the real wear is in the miles, or run service without a fixed task list, and the program drifts: PMs slip, breakdowns climb, and nobody can say why. A repeatable program rests on four things done well — vehicle classes, meter-based triggers, task libraries and the KPIs that prove it is working. This article builds each one, and shows how to run the whole program in OXMAINT AI, or book a demo of fleet PM scheduling.
FLEET PREVENTIVE MAINTENANCE · PLANNING · SCHEDULING · KPIs
Fleet Preventive Maintenance Program: Planning, Scheduling & KPIs
A repeatable PM program is built from four parts that lock together — classes, triggers, task libraries and measures. OXMAINT AI, the AI-powered fleet maintenance software, holds all four: it groups your vehicles into classes, watches every odometer and hour meter, releases the right task list on schedule, and tracks the KPIs that tell you the program is holding.
1Classes
→
2Triggers
→
3Task Libraries
→
4KPIs
Part 1 — Group the Fleet into Classes
A mixed fleet cannot run on one schedule. A pickup, a box truck and a tractor wear at different rates and need different work — so the program starts by sorting every vehicle into a class, and the class carries the schedule. In OXMAINT AI, the class is the template every new vehicle inherits.
Class 1–2
Light-Duty
Pickups, vans, SUVs. Tracked on mileage.
A: 5,000 mi / 6 mo · B: 15,000 mi / 12 mo
Class 3–6
Medium-Duty
Box trucks, delivery, utility vehicles.
A: 10,000 mi / 6 mo · B: 25,000 mi / 12 mo
Class 7–8
Heavy-Duty
Tractors, straight trucks. DOT annual applies.
A: 15,000 mi / 30 d · B: 50,000 mi / 6 mo
Off-Road
Equipment
Tracked and off-road machines, measured in hours.
A: 250 hrs / 3 mo · B: 1,000 hrs / 12 mo
Severe duty — extreme heat or cold, stop-and-go, heavy loads — tightens every interval by roughly 20–30%. Treat it as a duty-cycle modifier on the class, not a separate schedule.
Part 2 — Trigger on Meters, Not Just the Calendar
The most common program mistake is scheduling by date alone. A truck that runs hard crosses its mileage threshold long before the calendar says it is due; one that sits idle hits the date with barely any wear. A real program triggers on whichever comes first — and OXMAINT AI watches both against every unit.
MI
Meter-Based
Odometer and engine-hour readings, pulled from telematics or entered at service. The primary trigger for how hard a vehicle actually works.
whichever
comes
first
CAL
Time-Based
Calendar days and months, so a low-use vehicle still gets its fluids, brakes and safety checks before age — not mileage — catches up with it.
When a unit crosses its next threshold on either meter, OXMAINT AI opens the work order automatically with the right task list attached — no spreadsheet to watch, no PM to miss. Book a demo and see meter-and-calendar triggers fire in OXMAINT AI.
Part 3 — Build Task Libraries, Not One-Off Jobs
Consistency comes from the task list, not the technician's memory. Each service tier is a fixed library of tasks the class inherits, so an A-Service means the same checks on every unit, every time. OXMAINT AI stores these libraries and attaches the right one to each work order it raises.
AA-Service — Light & Frequent
The short-interval safety and wear check
Engine oil and filter change
Fluid levels topped and checked
Tires, brakes and lighting
Basic safety walkaround
Heavy-duty: DOT pre/post-trip review, 5th-wheel
BB-Service — Deep & Periodic
The longer-interval driveline and systems service
Transmission, axle and differential fluid
Air system, exhaust and DPF
Suspension and diagnostic scans
Heavy-duty: wheel bearings, clutch, driveline
Heavy-duty: annual DOT inspection
A B-Service usually includes everything in the A-Service plus its own deeper items, so the libraries nest rather than repeat. Build them once per class in OXMAINT AI and every future unit inherits them.
Part 4 — Measure the Program with KPIs
A program you cannot measure is a program you cannot defend. These are the numbers that tell you whether the plan is holding — and OXMAINT AI reports each one from the work orders and meters it already tracks, so the dashboard builds itself.
PM Compliance
Share of PMs completed on time. The headline health metric — a common target is 95% or better.
PM Drift
How far overdue PMs are running. Spreadsheet programs drift most; a live trigger holds it near zero.
Scheduled vs Unscheduled
The ratio of planned PM work to breakdown repairs. A maturing program shifts the balance toward planned.
Vehicle Availability
Share of the fleet ready to run. PM discipline lifts it by cutting unplanned downtime.
Cost per Mile / Hour
Maintenance cost against distance or hours run. Planned PM reliably costs less than reactive repair.
Breakdowns per Period
Road calls and unplanned stops over time. The outcome everything else is built to reduce.
The Four Parts Only Work Together.
Classes without triggers drift. Triggers without task libraries give inconsistent work. Task libraries without KPIs leave you blind to whether any of it is landing. OXMAINT AI holds all four as one connected program, so planning, scheduling and measurement run off the same data.
How OXMAINT AI Runs the Whole Program
OXMAINT AI is the AI-powered fleet maintenance software that turns these four parts into one running program — classes as templates, meters as triggers, task libraries as the work, and KPIs as the proof. Start free and stand up your fleet PM program in OXMAINT AI.
Class Templates
Set the schedule once per vehicle class; every new unit inherits its intervals and tasks automatically.
Meter Triggers
Odometer and engine-hour feeds watched against thresholds, with work orders raised on whichever comes first.
Task Libraries
A-Service and B-Service built once and attached to every PM, so the work is identical across the fleet.
Auto Work Orders
Each due PM becomes a scheduled, assignable work order — no spreadsheet to chase and no PM missed.
KPI Dashboard
PM compliance, drift, availability and cost reported from live data, so the program proves itself.
Full History
Every service, part and cost logged per vehicle, ready for audits, warranty claims and resale records.
EXPERT REVIEW
Written for fleet managers, maintenance supervisors and operations leaders building or tightening a preventive maintenance program. The vehicle classes, service tiers and interval figures here are common industry references — your real intervals come from each manufacturer's service schedule, your duty cycle and applicable regulations such as the DOT annual inspection for commercial vehicles. Treat them as a starting framework, not fixed values. OXMAINT AI is a maintenance management platform that plans, schedules, tracks and measures the program; it does not replace manufacturer guidance, a qualified inspector, or your own compliance obligations.
Frequently Asked Questions
What is a fleet preventive maintenance program?
It is a planned, repeatable system for servicing vehicles before they fail, rather than fixing them after. A complete program groups vehicles into classes, triggers service on mileage, engine hours or time, applies a fixed task list at each service, and measures the result with KPIs. Done well, it shifts a fleet from reactive repairs toward planned work that costs less and keeps more vehicles on the road.
Start free and build your fleet PM program in OXMAINT AI.
How do I set PM intervals for different vehicle types?
Group vehicles into classes — light-duty, medium-duty, heavy-duty and off-road equipment — and set the interval on the class, not each vehicle. Light-duty might run an A-Service every 5,000 miles, heavy-duty every 15,000, and off-road equipment every 250 engine hours. Then tighten by 20–30% for severe duty. The manufacturer's schedule and your duty cycle set the exact numbers; the class carries them to every unit.
Should PM be triggered by mileage or by time?
Both — on whichever comes first. Mileage and engine hours capture how hard a vehicle actually works, while a calendar trigger protects a low-use vehicle whose fluids and safety items age even without miles. A program that uses only one will either over-service idle vehicles or under-service hard-working ones.
Book a demo and see combined meter and time triggers in OXMAINT AI.
What is the difference between A-Service and B-Service?
A-Service is the short-interval, lighter check — oil and filter, fluids, tires, brakes and safety items. B-Service is the deeper, longer-interval service covering driveline fluids, air and exhaust systems, suspension and diagnostics, and usually includes everything in the A-Service too. Keeping each as a fixed task library is what makes the work consistent across every vehicle and every technician.
Which KPIs should I track for a fleet PM program?
Start with PM compliance (on-time completion, often targeted at 95%+), PM drift (how overdue PMs run), the ratio of scheduled to unscheduled work, vehicle availability, cost per mile or hour, and breakdowns per period. Together they show both whether the program is being followed and whether it is producing the uptime and cost results it is meant to.
Book a demo and see the fleet KPI dashboard in OXMAINT AI.
Build a Program That Runs Itself.
Put your fleet on OXMAINT AI: vehicles grouped into classes, service triggered on meters and time, fixed task libraries behind every work order, and the KPIs that prove the program is holding — planning, scheduling and measurement, all on one platform.
