How to manage fleet maintenance by mileage and engine hours
Usage-based maintenance connects each vehicle with mileage, engine-hour or time thresholds and surfaces priorities before a deadline is passed. The system organises alerts and service history; available signals support technical review but do not guarantee that every failure can be predicted.
- Published
- Updated
Rules for building a readable maintenance plan
A threshold is useful only when it starts with reliable data and produces a tracked action.
Key takeaways
- Choose the unit that represents how the vehicle actually wears.
- Verify mileage and engine-hour availability before creating rules.
- Set advance alerts that leave time to schedule the workshop.
- Connect each intervention with its outcome, meter reading and next threshold.
- Treat abnormal signals as inspection priorities, not automatic diagnoses.
When should maintenance use time, mileage or engine hours?
The three measures describe different forms of wear and can coexist on the same vehicle.
Threshold comparison
| Threshold | When it is useful | Data to verify |
|---|---|---|
| Calendar | Inspections, documents and components affected by time | Start date and frequency |
| Mileage | Trucks, buses, vans and mainly road-going vehicles | Consistent odometer or mileage record |
| Engine hours | Excavators, loaders and equipment that works while stationary | Available, stable engine-hour signal |
| Combined rule | Where more than one limit applies | A rule that alerts on the first threshold reached |
Which data should a vehicle maintenance record contain?
A complete record makes it possible to reconstruct why work was scheduled, completed or postponed.
Identity and use
- Vehicle, class, depot and owner
- Available mileage and engine hours
- Date of the latest reading and data quality
- Main duty or operating pattern
Work and next deadline
- Type of intervention and planned threshold
- Advance warning and priority
- Date, reading and outcome of completed work
- Documents, allocated cost and new threshold where available
Technical signals
Anomalies and CAN bus data can add context where the vehicle exposes them and the configuration makes them available. They do not replace inspection or justify a certain diagnosis without technical review.
How to turn a maintenance deadline into traceable work
The process does not end with a notification: it must continue through the outcome and next threshold.
1. Configure the rule
Define the threshold by vehicle class and state which data feeds it. A rule copied across the whole fleet can bring work forward for low-use vehicles and delay it for intensively used ones.
2. Create an advance alert
The alert should arrive early enough to coordinate the workshop, vehicle availability and service continuity. A notification at the exact deadline is often already too late.
3. Assign and schedule
Every priority needs an owner, target date and status. This prevents an alert visible to everyone from becoming nobody's responsibility.
4. Close the intervention
Record the outcome, meter reading and new threshold. The history then becomes a source for comparing frequency, cost and actual vehicle use.
Preventive and predictive maintenance: a necessary distinction
Planning before a failure does not mean predicting with certainty which component will fail.
Preventive maintenance
Uses thresholds, time and history to schedule checks or replacement before a failure. Mileage and engine hours make a calendar more consistent with actual use.
Condition-based maintenance
Uses available signals or anomalies to increase the priority of a check. The data identifies a condition to review and should be interpreted by the people responsible for the vehicle.
Predictive maintenance
Requires models, suitable historical data and specific validation of the ability to estimate a failure. This guide does not attribute undocumented automatic failure prediction to Zenit.
How does maintenance differ across trucks, buses and construction equipment?
The principle is shared, but the meter and downtime impact change with the vehicle's work.
Trucks and vans
Mileage, time-based deadlines, history and fuel use help schedule servicing and checks on mainly road-going vehicles. Comparisons should use vehicles with similar duties.
Buses and coaches
Mileage, availability and service schedules make it important to alert early enough to coordinate a replacement vehicle or different assignment.
Excavators, loaders and heavy equipment
Engine hours may represent wear better when equipment works without travelling far. Signal availability must be checked on the machine.
Questions to resolve before setting maintenance alerts
Thresholds, available data and prediction limits explained in operational terms.
Should fleet maintenance be scheduled by date, mileage or engine hours?
It depends on how the vehicle wears. Mileage describes many road vehicles well; engine hours often suit equipment that also works while stationary; calendar rules remain useful for time-based deadlines. A plan can use several thresholds and trigger the one reached first.
Are engine hours available from every vehicle?
No. Availability depends on the vehicle, exposed signals, device and configuration. Before an engine-hour deadline is created, the data should be checked for readability and consistency across that vehicle class.
Are preventive and predictive maintenance the same?
No. Preventive maintenance schedules work before a failure using defined time or usage thresholds. Predictive maintenance attempts to estimate a possible failure from models and signals. Mileage, engine hours and anomalies can prioritise checks, but they do not create a certain prediction on their own.
Can fleet software eliminate vehicle downtime?
No. It can make deadlines, use, history and signals visible, helping a business schedule checks and work. Sudden failures, maintenance quality and operating conditions remain variables that software cannot eliminate.
What should a vehicle maintenance history contain?
It should connect the date, type of work, vehicle, mileage or engine hours, outcome and next threshold. Costs and documents can complete the record when they are available and correctly allocated to the vehicle.
Check which counters your fleet can provide
Bring vehicle classes, the current plan and thresholds to a demo. The Zenit team can define which data is available and how it can become manageable deadlines.
- Validation by vehicle classMileage, engine hours and signals are confirmed before the process is configured.