Walk into almost any plant that has operated for a decade and ask a simple question: which of your preventive maintenance tasks would you defend, one by one, in front of a reliability engineer? Most maintenance managers can't — not because they aren't competent, but because their PM program was never designed. It accumulated.

OEM recommendations were loaded wholesale at startup. Tasks were added after every incident, but none were ever removed. Intervals were set once and never challenged against actual failure data. The result is a program where a significant share of the hours — in our experience typically 25 to 35 percent — addresses no credible failure mode at all.

Where PM hours typically go — before and after a PMO review Before ~30% waste After Right-sized program Removed: duplicated tasks, intrusive PMs on benign failure modes, intervals copied from OEM manuals never challenged against real failure data. Freed hours → condition monitoring, backlog reduction, defect elimination.
A typical PMO review removes or converts roughly a third of PM hours without increasing risk.

Why waste hides so well

PM waste is invisible in the metrics most sites track. Schedule compliance can be excellent while technicians dutifully execute tasks that do nothing. Worse, intrusive PMs on healthy equipment actively introduce failures: every unnecessary opening of a machine is an opportunity for infant mortality. The busiest maintenance departments are often the ones maintaining their own workload.

What a PMO review actually does

Preventive Maintenance Optimisation puts every task on trial. For each one we ask: which failure mode does this address? Is that failure mode credible for this equipment in this service? Is the task technically capable of detecting or preventing it? Is the interval justified by failure behavior, or by habit? Tasks that fail the trial are removed, merged, retimed, or converted to condition-based monitoring where the failure develops gradually enough to be detected.

The payoff runs both ways

The freed hours are not a headcount reduction exercise — they are capacity you redirect to the work that was always underfunded: condition monitoring routes, backlog reduction, and defect elimination. Sites that complete a rigorous PMO typically see corrective work drop within a year, because the program finally concentrates effort where failures actually develop.

Key takeaways

  • If your PM program was never designed top-down, assume 25–35% of it is waste until proven otherwise.
  • Schedule compliance measures effort, not effectiveness — a program can be 100% compliant and 30% useless.
  • Every task must trace to a credible failure mode, a capable technique, and a justified interval.
  • Convert intrusive PMs to condition-based tasks wherever failure behavior allows.