The Maintenance Execution Gap

Reliability programs do not fail in the conference room. They fail at the wrench.

You are fighting breakdowns, budget cuts, and advice you know is not going to work. Your equipment is running toward failure modes that have been documented for decades—in the manufacturer's manual, in industry standards, in the field experience of everyone who ever built or repaired that machine. The knowledge exists. It has simply never reached the person standing in front of the equipment with tools in hand.

If you are a production manager, maintenance manager, reliability engineer, planner, supervisor, operator, or technician tired of repeating the same reliability interventions while breakdowns continue, this book is the field manual for stopping the failures your own system is creating.

Peter J. Munson argues that most plants have the reliability knowledge they need and lack only the system that delivers it to the person in front of the equipment, at the moment the work is done. Drawing on nearly three decades from Marine Corps aviation to refineries, chemical plants, utilities, and mines, Munson shows why the industry's stock answers—RCM analysis, training, culture campaigns, predictive analytics—cannot close the gap. The gap lives where the work happens, and none of those answers goes there.

The book introduces the Maintenance Execution Framework, a practical system for enabling professional work at the point of action through:

Execution References that replace vague work orders with acceptance criteria, conditional actions, and asset history
Proper tools treated as standard issue, not special requests
On-spec materials and fluids protected from procurement through point of use
Equipment access and job continuity that let precision work actually happen
Safe restart and operation as the final step of repair
A learning loop that turns findings into better references, better work, and fewer repeated failures
Inside, you will learn how to identify maintenance-induced failure, convert weak PMs into usable Execution References, protect critical work from production pressure, build restart checks that catch defects before they become failures, and deploy known reliability practices without rediscovering standard failure modes in another workshop.

The knowledge already exists. The question is whether it reaches the work.

Stop admiring the problem. Close the gap where reliability is actually won.