Ask a delivery hub how maintenance is going and the answer is usually a feeling. The vans seem to be running, the sorter had a rough week, and the backlog feels long. A maintenance KPI program replaces those impressions with a small set of measures that everyone defines the same way and reviews on a fixed rhythm. The goal is not more dashboards but better decisions about staffing, spares, preventive intervals and capital. Those measures only hold up when work orders are completed with consistent data in maintenance management software.
Building a Maintenance KPI Program for Delivery Operations
Measure reliability, cost and uptime across fleets, dock equipment and packaging lines with a tiered KPI set that people actually use.
Why maintenance KPI programs fail before they start
Many sites already track metrics, yet nothing changes. The problem is rarely the choice of formula. It is usually one of four structural weaknesses that can be fixed before a single chart is built.
Too many measures
Twenty indicators on one screen mean nobody owns any of them. A hub needs a handful per tier, each with a named owner.Unreliable source data
If work orders are closed without times, causes or parts, the calculated results are noise. Data discipline comes first.No review rhythm
Metrics reviewed only when something breaks do not change behavior. A fixed meeting with fixed questions does.Measures without actions
A KPI that falls outside its range should trigger a defined response, not just a comment in the next report.The essential KPIs, defined so everyone calculates them the same way
Agree on definitions in writing before collecting any numbers. The table covers the core set for a delivery operation with vehicles, dock equipment and packaging machinery.
| KPI | Common definition | What it tells you | Watch out for |
|---|---|---|---|
| PM compliance | Preventive tasks completed within the allowed window ÷ preventive tasks due | Whether planned work is actually being done | Windows that are too wide hide late work |
| MTBF | Operating time ÷ number of failures | How long an asset runs between failures | Needs a clear failure definition and runtime data |
| MTTR | Total repair time ÷ number of repairs | How quickly service is restored | Decide whether waiting for parts is included |
| Wrench time | Hands-on work time ÷ available labor time | How much of the day goes to real work | Usually estimated by sampling, not by timesheet |
| Backlog | Estimated hours of open, ready work ÷ weekly crew capacity | Weeks of work waiting for the team | Separate ready work from jobs awaiting parts |
| Planned work share | Hours on planned jobs ÷ total maintenance hours | Control versus firefighting | Be consistent about how emergencies are coded |
| Availability | (Scheduled time − unplanned downtime) ÷ scheduled time | Time an asset can do its job | Planned downtime should be reported separately |
| Cost per unit | Maintenance cost ÷ miles, hours or items processed | Efficiency across different assets | Requires costs linked to each asset |
Three tiers, three dashboards, three different questions
A single dashboard cannot serve a technician and a regional director. Tiering keeps each audience focused on what they can influence.
What do I do next?
- Assigned work orders by priority
- Inspections failed this shift
- Parts waiting at the storeroom
- Assets currently down
What is slipping?
- PM compliance by asset class
- Backlog trend and oldest jobs
- Repeat failures and top causes
- MTTR by asset and technician group
Where should we invest?
- Availability of critical assets
- Cost per mile, hour or item
- Planned versus reactive hours
- Assets nearing repair-or-replace review
See the three dashboard tiers on live maintenance data
Look at how PM compliance, backlog, MTTR and cost per asset are calculated from the work orders your team already closes.
Dashboards, reporting and work order history in one connected system.Delivery-specific KPIs for fleets and packaging lines
The core set applies everywhere. Delivery operations benefit from a few extra measures that reflect road exposure and the dependence of throughput on packaging equipment.
Fleet measures
- Vehicle availability at route start, the clearest daily signal for dispatch
- Roadside breakdowns per period, split by cause category
- Inspection defect closure time, from report to verified repair
- Preventive service on time by mileage or hours
- Maintenance cost per mile by vehicle model
Warehouse and packaging measures
- Unplanned stoppage minutes per line per shift
- Availability of sorters, conveyors and sealers during peak waves
- Changeover-related faults, separated from mechanical failures
- Rework and rejected packs linked to equipment causes
- Dock door and leveler defects open past their target
Leading and lagging indicators: balance what happened with what is coming
Lagging indicators confirm results after the fact. Leading indicators show whether the conditions for good results are in place. A healthy program uses both.
| Type | Examples | Best used for |
|---|---|---|
| Leading | PM compliance, inspection completion, work order data completeness, backlog age, planned work share | Early warning and day-to-day management |
| Lagging | Unplanned downtime, MTBF, roadside breakdowns, cost per unit, emergency repairs | Confirming that the program delivers results |
How to use the pairing
- If lagging results worsen while leading indicators look healthy, the preventive tasks or intervals may be wrong.
- If leading indicators decline first, expect lagging results to follow, and act before the next breakdown.
- Report both together so nobody celebrates a good month that was driven by luck.
A review cadence that turns numbers into action
The routine matters more than the dashboard. Short, regular reviews with a fixed agenda keep metrics connected to decisions.
Shift start huddle
Ten minutes on assets down, safety-critical jobs, parts waiting and the day's priorities.Planning and backlog review
Review PM compliance, overdue jobs and next week's schedule. Assign owners to every red item.Reliability review
Examine top failure causes, repeat repairs, cost per unit and whether preventive tasks need changing.Strategy and investment
Review availability trends, repair-or-replace candidates, staffing, spares and training needs.Data quality: the prerequisite nobody wants to discuss
KPIs are arithmetic on work order records. If the records are incomplete, the arithmetic is precise and wrong. A short data standard prevents this.
Minimum fields at work order close
- Asset identifier linked to the correct location
- Work type: preventive, corrective, inspection or improvement
- Failure or cause code from a short list
- Actual start, finish and labor hours
- Parts and external cost, where used
Routine data hygiene
- Weekly review of jobs closed without cause or time
- Quarterly cleanup of duplicate assets and unused codes
- Meter readings updated on a fixed schedule
- Clear rules for emergency work entered after the fact
- Named owner for data quality in each hub
Setting baselines and targets without guesswork
Targets copied from an industry article rarely fit your operation. A better method starts with your own data and improves in steps.
- 1
Collect a baseline
Run the measures for two or three months without targets. Check that definitions and data behave as expected. - 2
Segment by criticality
Set stricter expectations for route vehicles and bottleneck equipment than for spare or low-impact assets. - 3
Choose realistic improvement steps
Aim for achievable gains each quarter and tie each target to a specific action, such as fixing the top three repeat failures. - 4
Define the response
Write down what happens when a KPI is out of range, who acts and by when, so the review ends with decisions.
Common KPI mistakes and what to do instead
These traps appear in most first-year programs. Recognizing them early saves months of unreliable reporting.
| Mistake | Why it hurts | Better practice |
|---|---|---|
| Measuring PM compliance by count only | Easy tasks inflate the figure while critical tasks slip | Report by criticality and by overdue age |
| Averaging MTTR across all assets | A few long repairs hide patterns on important equipment | Track by asset class and review outliers |
| Rewarding low backlog alone | Teams close or delete jobs to look good | Pair backlog with age, data quality and repeat failures |
| Ignoring planned downtime | Availability looks worse than reality, or hides lost production | Report planned and unplanned separately |
| Comparing hubs without context | Different fleets and equipment ages distort rankings | Compare against each site's own trend and similar assets |
Reading KPIs together: diagnostic patterns worth recognizing
A single metric can mislead. The real insight comes from combinations, because each pattern points to a different underlying problem and a different first action.
| Pattern in the data | Likely explanation | First action to take |
|---|---|---|
| High PM compliance, rising breakdowns | Preventive tasks are being done but are the wrong tasks or intervals, or quality of execution is poor | Review failure causes against the PM task list and sample completed PMs |
| Low PM compliance, low backlog | Preventive work is not being generated or is being closed without being done | Audit PM triggers and compare closed tasks with asset condition |
| Long MTTR, low wrench time | Technicians wait for parts, tools, permits or information rather than lacking skill | Sample a week of jobs and list the delays by type |
| Falling availability on one asset class | Wear-out phase, a poor design fit, or operating practices that cause damage | Run a repeat failure review and consider a repair-or-replace analysis |
| Planned share high, availability flat | Over-maintenance, or planned work is not aimed at the real failure modes | Challenge intervals and test condition-based alternatives |
| Good numbers, many unclosed jobs | Records are incomplete, so the calculation looks better than reality | Tighten close-out rules and track data completeness weekly |
A simple routine for investigating a red indicator
- Confirm the data first, since a bad definition or missing records are the most common causes.
- Split the metric by asset class, hub, shift and failure cause to find where the problem is concentrated.
- Look at a small sample of actual work orders to see what the numbers are hiding.
- Agree one action, one owner and one review date before leaving the meeting.
Who owns which KPI
Measures without owners drift. Assigning each KPI to a role, with a clear lever that role controls, makes accountability fair and practical.
Making the KPI program part of normal management
- Include maintenance indicators in the same operations review that covers service levels and safety.
- Recognize improvement in leading indicators, not only the absence of breakdowns.
- Revisit the KPI list every year and retire measures that no longer lead to a decision.
- Share the same definitions with finance and operations so a maintenance cost figure means one thing in every meeting.
- Publish a one-page glossary beside each dashboard so new supervisors and contractors read the numbers correctly.
- Review the glossary whenever a definition changes, and note the change date so trends stay comparable across periods.
A 90-day rollout plan
A modest, staged start builds trust. Each month has one clear objective.
Define and clean
- Agree KPI definitions and owners
- Fix asset records and failure codes
- Set minimum fields for closing jobs
Measure and review
- Publish the Tier 1 and Tier 2 views
- Start the weekly planning review
- Record baselines with no targets yet
Act and refine
- Set first targets by asset criticality
- Launch the monthly reliability review
- Add the Tier 3 leadership view
Frequently asked questions
How many KPIs should a delivery hub track?
Most teams do well with six to ten, split across the three tiers. Add more only when a specific question cannot be answered.
Which KPI should we start with?
PM compliance and unplanned downtime are the easiest to define and the most revealing. Both depend on clean work order records. To see them in practice, book a demo.
Can we measure MTBF without runtime data?
Only roughly. Capturing miles, hours or cycles through meter readings makes MTBF far more reliable, especially for vehicles and packaging machines.
How do we stop technicians gaming the numbers?
Pair each KPI with a quality check, such as repeat failures or data completeness, and review samples of closed jobs. Transparency discourages shortcuts.
Do we need special software to run a KPI program?
A CMMS makes it far easier, because the measures come directly from work orders. You can sign up and test the reports on a small asset list.
Turn maintenance from an art into a managed discipline
Build the work order data, dashboards and review routines that make every maintenance meeting about decisions instead of opinions.
Preventive maintenance, work orders, dashboards and reporting in one platform.
