Most fleets know which trucks "feel" unreliable, but few can prove it. Replacement debates, shop priorities, and spare-vehicle decisions often rest on memory and loud opinions. A fleet condition score replaces that with a repeatable ranking built from inspection results, open defects, repair history, and preventive maintenance compliance. This guide shows how to design a score your technicians trust, and how a fleet maintenance CMMS keeps the inputs current.
Fleet Condition Score: Vehicle Health Ranking Without Guesswork
One comparable health number per vehicle, built from maintenance records instead of opinion.Unit 114Healthy
Unit 207Watch
Unit 331Intervene
Why guesswork fails
- Opinions follow the last breakdown, not the full history.
- Drivers of newer trucks rarely complain, so slow decline goes unseen.
- Shop priority goes to whoever calls loudest, not to highest risk.
- Replacement and disposal choices lack a defensible basis.
What a score should do
- Rank vehicles within the same class so comparisons are fair.
- Show why a vehicle scored low, not just the number.
- Update automatically as work orders and inspections close.
Inputs that belong in the score
Weights below are an example starting point. Adjust them to your duty cycle and safety priorities.| Input | What it measures | Example weight |
|---|---|---|
| Open safety defects | Count and age of unresolved stop-level defects | 25% |
| Preventive maintenance compliance | Services completed on time versus due | 20% |
| Repeat repairs | Same component failing again within a set window | 20% |
| Unplanned downtime | Days out of service from breakdowns | 15% |
| Inspection pass rate | Share of walkaround items passed | 10% |
| Age and meter position | Mileage or hours against expected life | 10% |
Reading the ranking: four health bands
HealthyRoutine preventive maintenance only. Candidate for front-line duty.
WatchTrending down. Review open defects at the next service.
IntervenePlan a focused repair or inspection. Limit high-risk routes.
Review for retirementCompare repair spend to replacement cost before more work.
Building the score step by step
1Group vehicles. Compare like with like, such as tractors with tractors.
2Clean the data. Fix duplicate assets, missing meter readings, and open work orders that were never closed.
3Normalize each input. Convert each to a 0 to 100 scale so no single metric dominates.
4Apply weights. Start simple. Safety items should carry the most weight.
5Back-test. Check whether low scores matched recent breakdowns. Adjust until they do.
6Publish the drivers. Show the top reasons behind each score so technicians can challenge it.
Rank vehicles on records, not on reputation
Bring inspections, defects, and work orders into one asset history that a score can be built on.Common mistakes
| Mistake | Consequence | Better approach |
|---|---|---|
| Scoring only on age | Well-kept old units look bad, neglected new ones look fine | Blend age with condition and history |
| Too many inputs | Nobody can explain the result | Keep to five or six measurable inputs |
| Stale data | Scores lag reality | Update on every closed work order |
| Hidden formula | Technicians ignore the score | Share weights and reasons |
| Using it to punish drivers | Reporting quality drops | Use it to direct maintenance effort |
Practical uses
- Order the shop queue when several vehicles wait for a bay.
- Choose which units cover critical routes or customers.
- Build the case for replacement in capital planning.
- Target extra inspections where condition is slipping.
Where Oxmaint fits
- Asset management. One record per vehicle with meter readings, history, and documents.
- Preventive maintenance. Schedules and compliance data for the PM input.
- Work orders. Corrective and repeat repair history by component.
- Inspections. Mobile checklists that feed pass rates and open defects.
- Reporting and dashboards. Views of downtime, cost, and overdue work to support scoring.
A simple illustration of the scoring logic
The numbers below are invented to show the method. They are not benchmarks.| Input | Unit 114 raw | Normalized (0-100) | Unit 331 raw | Normalized (0-100) |
|---|---|---|---|---|
| Open stop-level defects | 0 | 100 | 2, one aged 12 days | 20 |
| PM completed on time | 95% | 95 | 55% | 55 |
| Repeat repairs in 90 days | 0 | 100 | 3 | 30 |
| Unplanned downtime days | 1 | 90 | 9 | 25 |
| Inspection pass rate | 97% | 97 | 81% | 60 |
How to read it
- Normalizing turns different units, such as days and percentages, into one comparable scale.
- Multiplying each result by its weight and adding them gives the final score.
- The most useful output is the list of lowest-scoring inputs for each unit, because that tells the shop where to look first.
Segment before you rank
A refuse truck and a delivery van face different duty cycles, so ranking them together is unfair. Segment first, score second.
- By vehicle class. Heavy tractors, medium trucks, vans, trailers, and specialty equipment each get their own comparison group.
- By duty cycle. Stop-and-go urban routes wear brakes and drivetrains faster than steady highway work.
- By age band. Compare new, mid-life, and late-life units separately, or adjust expected values for age.
- By depot or region. Climate, road conditions, and shop capability can change results.
Why segmentation protects trust
- Technicians accept the ranking when it compares similar units.
- Managers avoid unfair conclusions about a depot with harder routes.
- Outliers within a group stand out clearly.
Snapshot versus trend
A single score tells you where a vehicle stands today. The direction of change often matters more.
Stable highHealthy and holding. Keep the preventive plan.
Falling fastStill acceptable but dropping. Investigate now.
Stable lowKnown problem unit. Decide repair or replace.
RecoveringImproving after repair. Verify the fix held.
- Track the score weekly or monthly, not just at review time.
- Flag any unit that drops by a set amount between periods.
- After a major repair, check whether the score recovers.
Handling data gaps honestly
| Gap | Risk | Suggested handling |
|---|---|---|
| Missing meter readings | Age and interval inputs are wrong | Require a reading on every work order and inspection |
| Work orders left open | Downtime and defects look worse than reality | Weekly clean-up of stale orders |
| Inspections skipped | Pass rate looks perfect by accident | Count skipped inspections as a separate input |
| New vehicles with no history | Score is unreliable | Show as "insufficient data" until a minimum history exists |
| Inconsistent defect wording | Repeat repairs go undetected | Use a standard component and symptom list |
Putting the score to work in weekly routines
1Monday review. Look at the bottom ten units in each class and confirm each has a plan.
2Shop queue. Use the score and open defect severity to order bay assignments.
3Preventive adjustments. Bring forward services for units trending down.
4Operations alignment. Share the list of units to avoid on critical routes.
5Monthly reflection. Compare scores with actual breakdowns and adjust weights.
Connecting the score to replacement planning
A low score is a signal to look closely, not an automatic verdict. Replacement choices should combine health, cost, and operational need.
- Compare cumulative repair cost against the expected cost of a replacement over the same period.
- Consider downtime cost, including missed deliveries or substitute rentals.
- Check whether low scores come from fixable causes, such as skipped preventive maintenance, rather than true wear-out.
- Look at resale value, warranty status, and regulatory changes that may affect the unit.
- Review the specific components dragging the score down.
Questions to ask before retiring a unit
- Is the poor score driven by one repairable system?
- Has maintenance been consistent, or did it lapse?
- Would a spare unit cover the same work at lower risk?
Keeping technicians and drivers on board
- Be transparent. Publish inputs and weights in plain language.
- Invite challenge. If technicians believe a score is wrong, review the data together.
- Avoid blame. The score describes vehicles, not people.
- Show wins. Share examples where the score caught a problem early.
- Revise openly. Record each change to the formula with a date and reason.
Rollout checklist
- Asset records are unique, with correct class and meter type.
- Preventive maintenance schedules exist for every vehicle.
- Defect severity levels are defined and used.
- Work orders are closed with cause, parts, and labor.
- Weights and bands are agreed with shop leads and operations.
- A pilot group has been scored and compared with known problem units.
- A weekly review meeting has an owner.
Choosing weights: three approaches
| Approach | How it works | Strength | Weakness |
|---|---|---|---|
| Expert judgment | Shop leads and safety staff agree weights in a workshop | Fast and easy to explain | Reflects opinion and may carry bias |
| Safety-first tiers | Safety inputs always outweigh cost or age inputs | Aligns with risk and compliance | May under-weight cost drivers |
| Back-tested tuning | Adjust weights until low scores match past breakdowns | Grounded in your own history | Needs clean historical data |
A practical blend
- Start with expert weights so the first version is understood.
- Apply a safety override: any unit with an open stop-level defect is capped at the lowest band regardless of other inputs.
- Back-test after one quarter and adjust gradually.
- Document each change so scores stay comparable over time.
Component-level scores for deeper diagnosis
A vehicle-level score shows who needs attention. System-level scores show where.
- Brakes. Wear readings, defect reports, overdue inspections, and repair frequency.
- Tires and wheels. Tread checks, pressure issues, and replacement history.
- Engine and cooling. Leaks, warning lights, oil analysis where used, and repeat repairs.
- Electrical. Battery changes, intermittent faults, and lighting defects.
- Body and safety equipment. Doors, mirrors, restraints, and required equipment checks.
Benefits of the layered view
- A fair overall score can still hide one failing system.
- Planners can target a specific subsystem inspection rather than a general overhaul.
- Parts planning follows the weakest systems across the fleet.
Alerts that follow the score
ABand change. Notify the planner when a unit moves down a band.
BRapid drop. Flag a large fall between two periods for inspection.
CSafety cap. Alert the shop lead when a stop-level defect caps a score.
DOverdue preventive maintenance. Escalate when overdue services are dragging the score.
EStale data. Warn when a unit has no inspection or meter reading for a set period.
Who uses the score, and for what
| Role | Question answered | Typical action |
|---|---|---|
| Fleet manager | Which units carry the most risk and cost? | Approve repairs, plan replacements |
| Maintenance planner | What should enter the shop next? | Sequence work orders and bays |
| Lead technician | Why is this unit scoring low? | Focus inspection on the weak system |
| Operations or dispatch | Which units are safest for critical routes? | Assign vehicles to routes |
| Finance or procurement | Which units justify capital spend? | Build replacement budgets |
Metrics that complement the score
- Availability. Percentage of time vehicles are ready for service.
- Mean time between failures. Average operating time between unplanned breakdowns, by class.
- Preventive versus corrective ratio. A rising corrective share suggests slipping preventive discipline.
- Cost per mile or hour. Maintenance spend normalized for use.
- Backlog age. Average age of open work orders.
- Roadside events. Breakdowns that happen away from the depot and cost the most.
Using them together
- The score ranks vehicles, while these metrics explain fleet-wide trends.
- If the score improves but roadside events rise, review what the score misses.
- Present a small set at monthly reviews, not every available figure.
Typical journey from first score to routine use
Month 1Clean asset data, define classes, and pick inputs.
Month 2Pilot scoring on one class and compare with known problem units.
Month 3Publish scores to shop leads and run the weekly review.
Month 4 onExtend to all classes and tune weights on actual results.
Making the score visible on the shop floor
- Show reasons beside the number. For example, list the top three factors lowering a unit's score so technicians know where to start.
- Link to the records. Each factor should open the underlying defects, work orders, or inspections.
- Use plain band names. Healthy, watch, intervene, and review for retirement are easier to discuss than raw numbers.
- Keep a change log. Show when a score moved and which event caused it.
- Offer mobile access. Supervisors checking vehicles in the yard should see the score and open defects on a phone.
What good adoption looks like
- Technicians quote the score reasons in shift handovers.
- Planners use it to justify sequencing decisions.
- Drivers and dispatchers understand why a unit was held back.
- Disputes lead to better data, not abandonment of the score.
Reviewing the score model each quarter
- Compare the lowest-scoring units with actual breakdowns over the last quarter.
- List vehicles that failed unexpectedly while scoring well, and find which input was missing.
- Check whether any single input dominates results more than intended.
- Confirm data completeness: meter readings, closed work orders, and inspection coverage.
- Gather feedback from technicians, planners, and operations on whether rankings feel credible.
- Record every weight or band change with the date, reason, and owner.
