Planned Maintenance Percentage (PMP) Metric

Planned maintenance percentage (PMP) is the share of total maintenance labor hours spent on work that was planned before it started, planned hours divided by total maintenance hours, times 100. It measures how proactive a department is: how much of the crew's time goes to prepared, parts-in-hand jobs versus reactive scrambling. The commonly cited world-class target is 80% or higher.

Of all the maintenance metrics, PMP is the one that most reliably separates a department that runs its equipment from one that is run by its equipment. It is a leading indicator, you can move it this quarter by changing how work is prepared, and where it goes, the lagging outcomes (downtime, cost, reliability) tend to follow. This guide covers the formula, the crucial difference between "planned" and "scheduled," the 80% benchmark, and how PMP differs from PM compliance, a metric it is constantly confused with.

What is planned maintenance percentage?

PMP is the fraction of maintenance work, measured in labor hours, not work-order counts, that was planned in advance. A job is planned when someone prepared it before execution: identified the task, estimated the labor, staged the parts and tools, and wrote enough of a plan that the technician could walk up and do the work without hunting. Unplanned work is the opposite: a machine breaks, and the crew reacts, figuring out the job, chasing parts, and improvising as they go.

Measuring in hours is not a detail, it is the whole point. Counting work orders makes a department look better than it is, because reactive jobs eat disproportionate hours. One overnight breakdown can burn more crew hours than a week of planned PMs, so a plant that is 80% planned by work-order count can be 50% planned by hours. Hours are where the money and the disruption actually live.

What counts as "planned"? Planned is not scheduled

The most common mistake with PMP is treating "planned," "scheduled," and "preventive" as the same word. They are three different things, and mixing them up corrupts the metric.

Two consequences trip people up. A preventive task done in a hurry, without a plan or parts, is unplanned work even though it is a PM. And a condition-based repair, caught early on a trend, planned, and executed with parts in hand, is planned work even though it is corrective. That is exactly the point of catching failures inside the P-F interval: it converts what would have been reactive breakdowns into planned repairs, which is how good condition monitoring drives PMP up.

How do you calculate PMP?

Add up the planned labor hours for a period, divide by the total maintenance labor hours for the same period, and multiply by 100. Work the example: in a month the crew logs 900 planned hours and 300 unplanned hours, for 1,200 total. PMP is 900 ÷ 1,200 × 100 = 75%. To reach 80%, either the planned hours rise or, better, the unplanned hours fall, because every hour of firefighting eliminated improves both the numerator ratio and the plant.

How do you raise planned maintenance percentage? Six steps

1. Give someone the planner role. PMP rises when a dedicated planner prepares work before it hits the floor, scoping the job, estimating labor, and identifying parts. Without a planner, everything is improvised, and improvised is unplanned. This is the heart of maintenance planning and scheduling.
2. Build a backlog of planned work. A healthy, planned backlog is the fuel for proactive scheduling: when the crew finishes a job, the next planned job is ready. An empty planned backlog forces reactive work by default.
3. Kit the parts before the job. Staging parts and tools ahead of time is what makes a job "planned" in the metric and fast on the floor. It also exposes stockouts before they become downtime, the link to spare parts management.
4. Catch failures early so repairs can be planned. Condition monitoring and inspections turn surprise breakdowns into scheduled repairs. Every failure caught on a trend instead of at 2 a.m. is a chunk of hours that moves from unplanned to planned.
5. Root-cause the repeat reactive jobs. The same breakdowns recurring are the biggest drain on PMP. Eliminating their causes removes unplanned hours permanently rather than planning around them forever.
6. Measure in hours and review weekly. Track planned versus total hours every week alongside your other maintenance KPIs. What gets reviewed on a rhythm gets managed; an annual glance at PMP changes nothing.

What is a good planned maintenance percentage?

The widely cited world-class benchmark is 80% or higher roughly the 80/20 planned-to-unplanned split that maintenance and reliability professionals aim for. The Society for Maintenance and Reliability Professionals (SMRP) publishes formal definitions for proactive-work and related metrics in its Best Practices library, the closest thing the field has to a standard, and it is the right place to anchor any benchmark rather than a vendor blog number (SMRP Best Practices, Metrics & Guidelines). The payoff for climbing toward that target is documented by the U.S. Department of Energy's FEMP O&M guidance, maintained by Pacific Northwest National Laboratory: shifting from reactive toward planned and condition-driven maintenance offers savings that can exceed 30-40% (PNNL, O&M Best Practices). Treat 80% as a direction and a discipline, not a number to game, and remember that planned hours on the wrong work is still waste.

How is PMP different from PM compliance and schedule compliance?

These three metrics get used interchangeably and should not be. They answer different questions, and a department can pass one while failing another.

The distinction matters because they fail in different ways. A plant can hit high PM compliance every PM done on time, while PMP stays low because all the corrective work is still reactive firefighting. Another plant can plan its work well (high PMP) but blow its schedule constantly (low schedule compliance) because emergencies keep bumping the plan. Read together, the three tell you whether work is prepared, whether the plan holds, and whether the proactive tasks actually happen.

Why does PMP predict everything downstream?

PMP is a leading indicator because planned work and reactive work sit in a feedback loop. Planned work is faster, safer, and more thorough, so it fails less; fewer failures mean fewer surprise breakdowns; fewer breakdowns free up hours that can be spent planning the next jobs, which raises PMP further. Reactive work runs the loop in reverse: unplanned corrective work consumes the hours that would have gone to preparation, so planning starves, more things break, and the department spirals into firefighting. The huge cost of unplanned downtime is the price of being stuck on the wrong side of that loop.

Where PMP fits your reliability program

PMP is the proactivity gauge, and it sits near the top of the leading-indicator stack because it is upstream of almost everything else good. Raising it means preparing work, which means a planner, a planned backlog, kitted parts, and enough early failure detection to convert breakdowns into scheduled repairs. Those same disciplines raise equipment reliability and cut the reactive spend that dominates a struggling department's budget. Pair PMP with PM compliance and watch them move together as the program matures.

The measurement itself is where plants stumble: PMP in hours requires that every work order carry a planned flag and honest labor hours, and that reactive jobs actually get written up instead of fixed off the books. When that data is scattered or missing, PMP becomes a guess. Capturing labor hours and the planned/unplanned split cleanly, and putting the trend on a weekly dashboard next to backlog and compliance, is the pattern on our platform overview; the CLS case study shows connected reporting that makes metrics like this trustworthy without ripping out the systems already in place. To see how a struggling department climbs the ladder, start at planning and scheduling.