Preventive Maintenance (PM) is often one of the largest scheduled activities in mature reliability programs, but this isn’t universal. In lower-maturity plants, corrective work still dominates the labor mix. That’s precisely why PM scrutiny matters: plants that don’t manage PM design rigorously accumulate bloated, inefficient task lists that consume hours while delivering little risk reduction.
Poorly structured PM rarely “creates” failures outright, but it does increase failure probability, especially when tasks are intrusive, require disassembly, or introduce reassembly defects. Studies in the aviation and process industries show that intrusive maintenance can account for 15–30% of induced failures during overhauls. PM must mitigate risk, not inject it.
Here are 12 questions high-performing leaders ask before approving any PM task.
1. What failure mode does this PM actually address?
Every PM must map to a specific, credible failure mode grounded in the physics of failure, such as lubrication starvation, misalignment, corrosion, fatigue, contamination, thermal stress, etc. If the team cannot articulate the failure mode, the task isn’t justified.
2. Is the failure pattern suitable for time-based PM?
Not every failure is age-related. Research by Nowlan & Heap, foundational to modern RCM, found that only ~11% of failures follow predictable wear-out curves. The remaining ~89% exhibit random or condition-driven behavior and are poorly suited for calendar-based PM.
If the failure isn’t age-related, leaders push the team toward condition-based detection rather than interval-based routines.
3. Does this task reduce risk measurably?
A PM task must reduce either:
- the probability of the failure, or
- the consequences of the failure.
If neither moves, the task is a waste. “We’ve always done it” is not justification.
4. Is this PM intrusive – and if so, does the risk tradeoff make sense?
Intrusive tasks carry risk: contamination ingress, misalignment, improper torque, and seal damage. Leaders ask whether the task prevents more harm than it introduces.
Studies from MSG-3 (aviation maintenance) and process-industry overhauls show that intrusive work can meaningfully increase the probability of induced failure. The benefit must clearly outweigh this risk.
5. Has reliability engineering validated the interval?
Intervals aren’t derived from physics alone. Leaders expect intervals to balance:
- historical failure data
- OEM engineering guidance
- regulatory/insurance requirements
- PdM-trend behavior
- operational constraints
But they also expect the team to challenge intervals built purely on tribal knowledge. Over time, fixed frequencies drift toward inefficiency if they’re never reevaluated.
The P–F interval matters:
The P–F interval is the time between when a potential failure becomes detectable (P) and when it progresses to functional failure (F). Effective PM must occur inside this window: not too early, not too late.
6. Could this task be better performed through predictive technology?
PdM technologies – vibration analysis, oil analysis, ultrasonics, thermography – often detect problems earlier and more reliably than manual inspection. But they are not universal. Their effectiveness depends on:
- the failure mode
- the asset type
- the detection threshold
- available skills
- cost versus value
Smart leaders ask whether PdM provides a better cost-to-risk-reduction ratio. If predictive technology detects earlier at a lower total cost, shift strategy. But if a simple, low-cost PM on a non-critical asset is cheaper and “good enough,” PM wins.
7. Is the task clearly defined so that two technicians would perform it the same way?
Ambiguity destroys effectiveness. PMs written as “inspect,” “check,” or “verify” without measurable criteria fail the reliability test.
According to SAE JA1012 (RCM), tasks must be applicable and effective; they must address a known failure mode and reduce risk to an acceptable level at the defined interval.
Good PMs specify:
- method
- measurement
- acceptable limits
- tools
- component location
Clarity = repeatability.
8. Is the task feasible within real operating conditions?
If it requires shutting down the line, special access, scaffolding, or production coordination, feasibility matters just as much as technical logic. Plants often approve tasks that look correct on paper but never occur in the field.
If the PM isn’t executed reliably, the strategy must change.
9. Is the task aligned with asset criticality?
Every PM consumes labor. Criticality directs where that labor should go.
High-criticality assets justify deeper inspection, shorter intervals, and more instrumentation. Low-criticality assets may only merit operator checks or run-to-failure strategies.
Smart leaders ensure PM effort matches asset importance, not tradition.
10. Does this task have a feedback loop?
PMs produce findings, but many plants never analyze them. Leaders require:
- CMMS recording
- trend analysis
- failure mode updates
- interval adjustment
- structured PM optimization cycles
Without a feedback loop, even good PMs stagnate.
11. Does it eliminate defects, or simply manage chronic conditions?
Some tasks deliberately manage unresolved chronic issues, such as periodic realignment for a machine installed on a compromised foundation or scheduled seal changes where contamination-control improvements aren’t economically justified.
That’s legitimate when chronic management is the optimal economic choice.
But leaders must distinguish between:
- necessary chronic condition management, and
- symptom-masking that quietly defers needed correction.
12. What happens if we remove this task entirely?
This question forces clarity. If the team cannot explain the risk of removal, the PM likely lacks engineering justification.
The best plants run structured PM reviews every 18–24 months, typically eliminating 5–15% of tasks while improving reliability.
Where High-Value PM Really Begins
“World-class” isn’t a slogan; it’s measurable. High-performing organizations show:
- >90% PM compliance
- regular PM optimization cycles
- clear risk-based prioritization
- well-defined PM tasks tied to failure modes
They don’t accumulate PMs like barnacles. They deliberately curate them, engineering each task to minimize risk, cost, and complexity.
Innovative leaders ask hard questions because PM approval is a risk decision. And risk decisions demand rigor.
