What is a maintenance strategy?
A maintenance strategy is the governed set of failure-management policies used to preserve required asset functions in a specific operating context. It determines when maintenance should be reactive, time- or cycle-directed, condition-based, predictive, failure-finding, redesigned, or deliberately run to failure based on credible failure modes, consequence, detectability, technical effectiveness, operating evidence, and controlling requirements.
One asset can require several maintenance strategies at the same time.
A gearbox may have condition-based vibration monitoring for bearing degradation, periodic lubrication tasks for lubricant condition, a scheduled inspection for guards, and deliberate run-to-failure for a low-consequence indicator lamp.
Whole assets should not be forced into one label when different failure modes behave differently.
Start with how the function can fail and whether deterioration can be detected or prevented.
Time-directed replacement only makes sense when age, cycles, exposure, or a controlled requirement provides a valid basis. Condition-based work requires detectable degradation and enough warning time to act. Failure-finding applies to hidden protective functions.
When no proactive task can manage the failure effectively, redesign, operating control, spare strategy, or deliberate run-to-failure may be more appropriate than adding another PM.
The same failure mode can deserve a different policy in a different operating context.
Criticality, redundancy, duty cycle, environment, production role, quality exposure, spare availability, maintainability, and failure detectability all affect the right policy.
Copying a PM from an identical machine without understanding its service can create activity without controlling the real risk.
Maintenance strategy should change when field evidence disproves the assumption.
Repeat failures, PM findings, bad actors, condition trends, emergency work, RCA results, and technician feedback are all strategy feedback.
When a covered failure mode keeps returning, investigate whether the mode was missing, the task was ineffective, the interval was unsupported, execution failed, or the operating context changed.
Strategy decisions must preserve controlling technical and safety authority.
OEM instructions, engineering standards, regulatory requirements, quality controls, statutory inspections, and site safety procedures can define mandatory tasks or limits.
A strategy review can identify a question or optimization opportunity, but it does not authorize the organization to ignore controlling requirements.
What is the simplest test of a maintenance strategy?
For each significant task or run-to-failure decision, the team should be able to explain which failure mode it addresses, why the chosen policy fits the failure behavior, what consequence it controls, and what evidence would trigger a change.
- Define the required function and credible failure mode.
- Match policy to failure behavior and detectability.
- Apply consequence and operating context.
- Use field evidence to challenge the strategy over time.
Technical references
- SAE JA1011_202411 — Current criteria for processes represented as Reliability-Centered Maintenance.
- NASA Reliability-Centered Maintenance Guide — Practical reliability-centered maintenance and condition-monitoring guidance.
Build strategy around failure behavior, not maintenance labels.
Use credible failure modes, consequence, detectability, and operating evidence to decide what work belongs in the program and why.
PM Optimization See facility-specific XRVE services