What is a maintenance KPI
A maintenance KPI (key performance indicator) is a measurable value that shows how well maintenance supports asset availability, reliability, and cost against a defined target. Leaders use it to see whether maintenance work delivers the uptime and cost control the business expects.
This guide covers how a KPI differs from a metric, the five maintenance KPIs that matter most, and how the formulas work. It also covers where they go wrong, which data they depend on, and where EAM software with AI embedded fits. Ultimo has decades of EAM domain expertise.
What is a maintenance KPI, and how does it differ from a metric or a target?
A maintenance KPI is a metric tied to a business objective, such as asset availability or maintenance cost. Maintenance key performance indicators, also called maintenance performance indicators, usually cover three areas: availability, reliability, and cost. Three terms are often mixed up when teams discuss maintenance metrics:
Metric: any measurement, such as the number of work orders closed this week.
KPI: a metric linked to an objective, such as unplanned downtime hours against an availability goal.
Target: the value a KPI is judged against, set from the organization's own baseline.
A KPI without a target and an owner is only a number. Someone has to be accountable for moving it, and the target has to be agreed with operations and finance.
How do the maintenance KPI formulas work?
Each core maintenance KPI is a ratio or an average, and the unit decides whether results can be compared. The formulas below are generic industry definitions:
MTBF: total operating time divided by the number of failures, stated in hours.
MTTR: total repair time divided by the number of repairs, stated in hours.
Unplanned downtime: hours an asset is unavailable because of unplanned stops, in a stated period.
Cost of unplanned downtime: unplanned downtime hours multiplied by the hourly cost of downtime for that asset.
PM compliance: preventive maintenance tasks completed on time divided by tasks scheduled, as a percentage.
Planned maintenance percentage: planned maintenance hours divided by total maintenance hours, as a percentage.
Reactive work ratio: reactive work divided by total work, counted in hours or work orders with the unit stated.
Maintenance backlog: outstanding work order hours divided by available crew hours per week, read as weeks of work.
OEE: availability multiplied by performance multiplied by quality.
Maintenance cost ratio: annual maintenance cost divided by the replacement value of the assets.
A hypothetical example shows the arithmetic and is not a benchmark. Say 30 failures occur over 12,000 operating hours. MTBF is then 400 hours. If those 30 repairs took 90 hours in total, MTTR is 3 hours.
No numeric target is universal. Published benchmarks vary between sources and depend on asset class, criticality, and how a KPI is defined.
Set the baseline first. Track each KPI for a full reporting period before setting a target. A baseline gives any target a factual starting point. The hourly cost of downtime differs by asset and site, so it should come from finance, not from an industry average.
What are the common formula and data traps?
The same KPI name can mean different things between sites, teams, and published sources. That is the most common reason KPI numbers get disputed in a review:
PM compliance versus planned maintenance percentage: the first counts tasks done on time, and the second compares planned hours with total hours. They are often mixed up.
Hours versus work orders: a reactive ratio counted in hours gives a different answer than one counted in work orders.
Backlog units: a backlog shown as a percentage, in hours, or in weeks cannot be compared without conversion.
Averages that hide outliers: one long repair can lift MTTR and mask a team that otherwise repairs quickly.
Loose definitions: if sites define failure and downtime differently, cross-site comparison is unreliable.
Fixing the unit and the definition before comparing sites removes many of these disputes.
What are leading and lagging maintenance KPIs?
Lagging KPIs report outcomes after they happen, and leading KPIs signal outcomes before they happen. A balanced set includes both.
Lagging: MTBF, MTTR, unplanned downtime, cost of unplanned downtime, reactive work ratio, OEE, and maintenance cost. They confirm results.
Leading: PM compliance, planned maintenance percentage, and backlog. They show whether work is on track to prevent failures.
Lagging KPIs tell leaders what already happened. Leading KPIs give maintenance a chance to act first, for example by clearing a growing backlog before it turns into downtime.
What data does a maintenance KPI need?
A KPI is only as credible as the data behind it. When work orders sit in spreadsheets and failure codes differ by site, the numbers become arguable. The discussion then turns from action to doubt about the data.
In practice, maintenance KPIs rely on a few kinds of data:
An asset register and hierarchy, so every number ties to a defined asset
Work orders with type, start, and finish times
Failure and cause data, coded the same way across sites
Downtime start and end times for each stop
Preventive schedules and their completion dates
Cost data for labor, parts, and external work
Each KPI pulls from several of these. The MTTR KPI needs start and finish times and repair counts. PM compliance needs schedules and completion dates. A maintenance cost ratio needs cost data and asset values. Unplanned downtime needs stop times, MTBF needs operating time and failure counts, and the reactive work ratio needs work type. Teams that want one version of the numbers can keep these inputs in one EAM system.
A work order closed without a finish time, or a failure logged without a cause, leaves a gap in every KPI that depends on it. Mandatory fields at the point of work closure help prevent those gaps.
How do teams choose KPIs for their maturity?
The right starting KPIs depend on how a team works today. This is general practice and not part of any standard:
Teams still reacting to breakdowns: start with unplanned downtime, MTTR, and the reactive work ratio.
Teams with planned work in place: add PM compliance and backlog.
Teams working proactively: add maintenance cost against asset value, and track reliability trends such as MTBF.
To see where a team stands, Ultimo's EAM Maturity Model offers a shared frame for the conversation. It is Ultimo's own model and not a KPI standard.
How does EAM software support maintenance KPI tracking?
EAM software supports maintenance KPIs by holding asset data, executing work, and keeping history in one place, so the same data feeds every number. The KPI value still depends on the organization's definitions and data discipline.
Ultimo supports teams that measure maintenance performance. These capabilities support the data behind the KPIs above:
Work order management supports planning, prioritization, execution, and tracking of the complete maintenance work order process. See work order management for the basics.
Reporting and Dashboards give cross-departmental visibility from the same data, with Power BI integration. All key stakeholders work from the same data.
Assisted Troubleshooting surfaces similar historical failures grouped by root cause in seconds. It makes failure history usable without exact keywords. ReliablePlant reports that 80% of MTTR is spent figuring out the cause of failure. Read more on how embedded AI reduces MTTR.
Ultimo's category is Intelligent Asset Management, delivered as EAM software with AI embedded.
How to start tracking maintenance KPIs
Starting does not mean tracking everything. A common sequence looks like this:
Agree the objective with operations and finance, such as availability or cost control.
Pick three to five KPIs from the starter set.
Fix the formula, the unit, and the definitions of failure and downtime.
Confirm the data source for each KPI.
Track for a full reporting period to set a baseline, then set a target.
Assign an owner and a review cadence.
Review each KPI with its owner on a fixed cadence. Leading KPIs such as PM compliance and backlog suit more frequent checks. Lagging KPIs such as MTBF show their trend over longer periods. When a target is missed, investigate the cause before changing the target.
Limited data quality and team capacity are common. Neither has to block a start. Begin with the most critical asset classes, and tailor the number of KPIs to what the team can review each month.
Work and asset history held in one EAM system, such as Ultimo's, gives step four a single source for each KPI. Step five still depends on the organization's own definitions and review period.
Frequently Asked Questions
What is a maintenance KPI?
A maintenance KPI is a metric tied to a business objective, such as availability, reliability, or cost, and judged against a target. It turns maintenance activity into numbers that leaders can review and act on. Common examples include unplanned downtime, MTTR (mean time to repair), MTBF (mean time between failures), and PM compliance.
What are the most important KPIs for maintenance?
No single list fits every site, but five maintenance KPIs make a practical starter set: unplanned downtime, MTTR, MTBF, PM compliance, and reactive work ratio. Together they show availability, repair speed, reliability, plan adherence, and control. Teams then add OEE or maintenance cost against asset value as their measurement matures.
What are the 5 key performance indicators?
In maintenance, five KPIs are commonly tracked together: unplanned downtime, MTTR, MTBF, PM compliance, and reactive work ratio. No standard fixes the set, so each organization chooses from its own objectives. Three to five that the team can review each month work better than a long list. Whatever the set, every KPI needs a stated formula, unit, and owner.
What are the top 3 maintenance KPIs?
Unplanned downtime, MTTR, and PM compliance form a practical top three, because together they cover outcome, repair speed, and plan adherence. Teams still reacting to breakdowns can swap PM compliance for the reactive work ratio. Operations and finance should confirm the three against their own objective and the data they already hold.
What are some good maintenance KPI examples?
Good maintenance KPI examples include MTBF (mean time between failures), which is operating time divided by the number of failures. MTTR (mean time to repair) is repair time divided by the number of repairs. PM compliance is preventive maintenance tasks completed on time divided by tasks scheduled. Reactive work ratio is reactive work divided by total work. Each needs a stated unit so results can be compared across sites.
What is the difference between a KPI and a metric?
A metric is any measurement. A KPI is a metric tied to an objective and judged against a target. The number of work orders closed is a metric. Work orders closed on time against a plan becomes a KPI once someone owns a target for it. Maintenance KPIs add the objective and owner that a plain metric lacks.
Is PM compliance the same as planned maintenance percentage?
No. PM compliance is preventive tasks completed on time divided by preventive tasks scheduled. Planned maintenance percentage is planned maintenance hours divided by total maintenance hours. The first measures plan adherence, and the second measures how much work is planned. Teams should name which one they report.
Can EAM software track maintenance KPIs?
EAM software can hold the data that KPIs depend on, such as work orders, failure history, and downtime. Ultimo supports teams that measure maintenance performance through work order management and Reporting and Dashboards with Power BI integration. Organizations keep ownership of definitions and targets.