What is Reliability Centred Maintenance? The Complete RCM Guide

RCM Defined

The formal definition from SAE JA1011 states that RCM is “a process used to determine what must be done to ensure that any physical asset continues to do what its users want it to do in its present operating context.”

In plain terms, RCM answers a deceptively simple question: given how this asset can fail, what is the right thing to do about it? The answer varies by failure mode. Some failures warrant scheduled replacement. Others are better managed by condition monitoring. Some require redesign. And a small number are best left to run to failure with a defined consequence management plan.

RCM began in commercial aviation. Nowlan and Heap’s 1978 United Airlines study showed that most failure modes gain nothing from fixed-interval overhaul, which upended the maintenance thinking of the day and fed the airline industry’s MSG-3 logic. SAE JA1011, issued in 1999, codified the criteria an RCM process must meet, and it remains the reference standard for industrial RCM.

What RCM changes

• RCM removes maintenance tasks that answer no failure consequence, which is where most programs find their first savings.
• RCM documents why every task exists, so the program survives audits, handovers and staff turnover.
• RCM makes run-to-failure a deliberate, written decision instead of an accident.
• RCM ties maintenance frequency to how failures actually develop, not to OEM defaults or habit.

The 7 RCM Questions

The RCM methodology is built around seven questions, first articulated by Nowlan and Heap in their 1978 United Airlines study and later codified in SAE JA1011. Every RCM analysis — regardless of the software or facilitation approach used — must answer all seven.

1. What are the functions and associated performance standards of the asset in its present operating context? Function definition is the foundation. Without a clear statement of what the asset is supposed to do, and to what standard, it is not possible to identify when it has failed.
2. In what ways can it fail to fulfil its functions? These are functional failures — the states in which the asset no longer meets the required performance standard.
3. What causes each functional failure? Failure modes are the specific causes of each functional failure: wear, fatigue, contamination, operator error, design limits exceeded.
4. What happens when each failure occurs? Failure effects describe what actually happens when a failure mode occurs — including any secondary damage, safety consequences, and production impact.
5. In what way does each failure matter? Failure consequences are categorised as hidden, safety/environmental, operational, or non-operational. The consequence category drives the maintenance strategy selection.
6. What can be done to predict or prevent each failure? The RCM decision logic identifies whether a proactive task (condition-based, scheduled restoration, scheduled discard) is technically feasible and worth doing.
7. What should be done if a suitable proactive task cannot be found? Default actions include run-to-failure with a defined spare parts and response plan, or redesign to eliminate the failure mode entirely.

When Should You Use RCM?

RCM is not a tool for every asset or every situation. It delivers the most value when applied to the right problem at the right time.

• New assets entering service. RCM at the design or commissioning stage prevents the default approach of copying existing PM schedules without evidence. It is significantly cheaper to establish the right maintenance basis before equipment enters service than to correct a flawed program after failures occur.
• Underperforming preventive maintenance programs. If your PM program is generating work without reducing failures, or if reliability data shows stagnant MTBF despite scheduled maintenance spend, RCM provides the analytical basis for a reset.
• Post-failure review on critical assets. When a high-consequence failure occurs, RCM-style analysis — applied to the affected system — identifies whether the maintenance program was the cause, and what needs to change.
• Capital project readiness. Maintenance readiness reviews for greenfield or brownfield expansions benefit from RCM analysis to establish maintenance strategies before handover, not after the first major breakdown.

RCM or a maintenance strategy review?

Full RCM is the most rigorous tool in the maintenance strategy toolbox, and the most expensive. It is not the first tool to reach for on every site, and a consultancy that recommends it reflexively is selling analysis hours, not outcomes.

The decision comes down to what you are starting from and what is at stake:

• Choose full RCM when the asset is critical, the failure consequences are severe, and the maintenance basis needs to be built or rebuilt from the failure modes up. New critical assets entering service, safety-case equipment, and systems recovering from a high-consequence failure sit here. RCM answers all seven questions from scratch and documents why every task exists.
• Choose a maintenance strategy review (also called PM optimisation or maintenance task optimisation) when a maintenance program already exists but is underperforming: PMs generating work without reducing failures, intervals inherited from OEM defaults, tasks nobody can explain. A structured review tests the existing program against failure evidence and fixes the worst of it at a fraction of the analytical cost. Our guide to maintenance task optimisation covers this route in detail.
• Run criticality first in either case. An asset criticality assessment, part of our reliability engineering services, tells you which assets justify the full analysis and which only need the review. In our experience, applying RCM to low-criticality assets is the most common way sites burn their reliability budget for no return.

The two are not rivals; they are different depths of the same discipline. A common pattern on mature sites is a strategy review across the asset base, with full RCM reserved for the handful of systems whose criticality earns it.

RCM vs FMECA — What Is the Difference?

FMECA (Failure Mode, Effects and Criticality Analysis) and RCM are often confused because they share a common analytical foundation. The distinction is important.

FMECA is a risk-ranking tool. It identifies failure modes, documents their effects, and assigns a criticality score based on severity and probability of occurrence. The output is a prioritised list of failure risks. FMECA tells you what your failure risks are and how they rank.

RCM uses that same analytical process as its starting point, then goes further. It applies a structured decision logic to each failure mode to select the appropriate maintenance task. RCM tells you what to do about each failure risk.

The RCM Process Step by Step

A rigorous RCM study follows a defined sequence. Shortcutting any step weakens the output.

1. Define the system boundary and operating context. Establish what is in scope, what operating conditions apply, and what performance is required.
2. Identify functions. Document both primary and secondary functions, including protection and containment functions that are often overlooked.
3. Identify functional failures. State the specific ways in which each function can fail to meet its performance standard.
4. Identify failure modes. For each functional failure, identify all plausible causes. This step requires input from operators, maintainers, and engineers who have worked directly with the asset.
5. Identify failure effects. Describe what actually happens when each failure mode occurs — including detection, secondary damage, and production impact.
6. Evaluate failure consequences. Apply the SAE JA1011 consequence categories to determine what is at stake for each failure mode.
7. Apply the RCM decision logic. Work through the decision tree for each failure mode to select the appropriate task type and interval.
8. Package and implement the maintenance program. Translate RCM outputs into scheduled tasks, condition monitoring routes, and spare parts holdings. Load into the CMMS and establish a review cycle.

Prefer it on one page? See the step-by-step RCM analysis guide and download the one-page RCM analysis infographic there.

RCM in Practice: A Worked Example

Take a slurry pump feeding a processing circuit. The function statement is not “to pump slurry” but “to deliver at least 850 m³/h of slurry to the cyclone cluster at 300 kPa”. One functional failure: it delivers less than 850 m³/h. One failure mode behind it: impeller wear from abrasive slurry. The effect: flow drops over weeks, cyclone efficiency falls, and the circuit loses recovery long before the pump stops. The consequence is operational, so the failure mode earns a proactive task if one is technically feasible and worth doing. Impeller wear develops gradually and is measurable, so condition monitoring wins: a monthly flow-and-pressure check with a defined replacement trigger, instead of a fixed-interval overhaul that replaces good impellers or misses fast wear.

A second failure mode on the same pump, seal flush line blockage, leads to a different answer: a weekly inspection is cheap and catches most blockages before seal damage. A third, motor winding failure, is effectively random in this duty; no scheduled task will prevent it, so the defensible decision is run-to-failure with a spare motor held on site.

Three failure modes on one asset, three different answers. That is RCM doing its job: the consequence and the failure behaviour pick the task, not habit and not the OEM manual.

Common RCM Mistakes

RCM produces weak results when it is treated as a documentation exercise rather than an engineering one. The most common errors seen in practice:

• Conducting RCM as a desktop exercise. Failure modes identified without input from the people who operate and maintain the asset are incomplete. Operators and trades carry failure knowledge that does not exist in any document.
• Not involving operators. RCM is a cross-functional process. Maintenance engineers alone cannot identify all failure modes, especially those involving human factors, operating variability, or latent defects.
• Trying to analyse every asset. Applying RCM to low-criticality assets wastes resources and dilutes focus. The correct approach is to tier assets by criticality — using an asset criticality assessment — and apply RCM only where the consequence of failure justifies the analytical investment.
• Treating RCM as a one-time project. RCM outputs should be living documents. As failure data accumulates and operating conditions change, maintenance strategies need to be reviewed and updated.
• Confusing RCM with a CMMS data entry project. The value of RCM is in the analysis, not the documentation. Organisations that focus on loading tasks into the CMMS before the analysis is sound will systematically perpetuate the wrong maintenance approach.

For a detailed review of implementation failures, see our article on the six most common reasons RCM implementations fail.

RCM Software

Dedicated RCM software structures the analytical process, maintains failure mode libraries, enforces decision logic, and produces task lists that can be exported directly to CMMS platforms.

ReliaSoft RCM++ is the industry-leading platform for RCM analysis. It supports the full SAE JA1011 process, integrates with reliability databases, and produces audit-ready documentation. For organisations running parallel reliability engineering activities, RCM++ integrates with the broader ReliaSoft suite including BlockSim (RAM modelling), XFMEA (FMECA), and Weibull++ (life data analysis).

Holistic Asset Management is the exclusive distributor of ReliaSoft software in Australia and New Zealand. We supply, implement, and support the full ReliaSoft suite for asset-intensive organisations. Details on licensing and implementation support are available on our software page.

RCM Consulting in Australia

Holistic Asset Management has delivered RCM programs across mining, oil and gas, manufacturing, and utilities in Australia. Our approach combines structured facilitation with direct industry experience — our engineers average more than 20 years of on-site reliability and maintenance work.

We do not run desktop RCM exercises. Every analysis is conducted with cross-functional teams that include operators, maintainers, and engineers who work directly with the assets under review. The output is a defensible, implemented maintenance program — not a report that sits in a drawer.

Our Holistic RCM approach is built around the SAE JA1011 standard and scaled to the asset complexity and operating context of each client. Where criticality assessment work is needed first, we conduct that as a precursor to ensure RCM effort is directed at the assets that matter most.

If you are reviewing an existing PM program, scoping a new asset class, or recovering from a significant failure event, our team can help you establish a maintenance strategy that is technically defensible and operationally practical. If you would rather build the capability in-house, the three-day RCM Foundations course teaches the same method your team would see in a facilitated study.

Frequently asked questions

What is RCM?

Reliability Centred Maintenance (RCM) is a structured analytical framework used to determine the most appropriate maintenance strategy for each failure mode of a physical asset. It was developed to preserve asset function, identify failure causes, and select maintenance tasks that are technically feasible and worth doing.

What are the 7 RCM questions?

The 7 RCM questions are: 1. What are the functions and associated performance standards of the asset? 2. In what ways can it fail to fulfil its functions? 3. What causes each functional failure? 4. What happens when each failure occurs? 5. In what way does each failure matter? 6. What can be done to predict or prevent each failure? 7. What should be done if a suitable proactive task cannot be found?

What is the difference between RCM and preventive maintenance?

Preventive maintenance is a task type: work done on a schedule. RCM is the decision process that determines which preventive tasks are worth doing and at what interval, and which failure modes are better managed by condition monitoring, failure-finding tests, redesign or deliberate run-to-failure.

What is the difference between RCM and FMECA?

FMECA (Failure Mode, Effects and Criticality Analysis) is a risk-ranking tool that identifies and prioritises failure modes by their severity and likelihood. RCM goes further by using the output of an FMECA-style analysis to select specific maintenance tasks for each failure mode. In practice, RCM incorporates FMECA as part of its process.

What is an example of reliability centred maintenance?

A slurry pump analysed under RCM can end with three different answers for three failure modes: condition monitoring for gradual impeller wear, a cheap weekly inspection for seal flush blockage, and deliberate run-to-failure with a spare held for random motor failure. The consequence and failure behaviour pick each task.

How long does RCM take?

The duration of an RCM analysis depends on the number of assets, the complexity of failure modes, and team availability. A focused RCM study on a single critical asset system can take two to four weeks. A full plant-level program across multiple asset classes typically runs three to six months when conducted properly with a cross-functional team.

What is RCM software?

RCM software is a dedicated platform that structures and documents the RCM analytical process, stores failure mode libraries, applies decision logic, and outputs maintenance task lists. ReliaSoft RCM++ is the industry-leading RCM software platform. Holistic Asset Management is the exclusive distributor of ReliaSoft software in Australia and New Zealand.