Reliability Centered Maintenance (RCM): A Practical Guide for Equipment-Heavy Operations
What reliability centered maintenance is, the seven RCM questions and the P-F curve, how to run an analysis step by step, and a worked example on a field pump.
- Equipment Management

Your pump was serviced on schedule. Every box on the PM sheet was ticked. It still failed three weeks later, on location, with a crew standing around and a customer on the phone.
That is the problem reliability centered maintenance was built to solve. A fixed calendar assumes equipment wears out at a predictable age. Most of the time, it does not. RCM gives you a structured way to decide, asset by asset, what maintenance actually prevents the failures that matter, and what you can safely stop doing.
This guide explains what RCM is, its core principles, where it came from, the seven questions at its core, the P-F curve and how to run an analysis yourself, with a worked example on a pump.
What is reliability centered maintenance?
Reliability centered maintenance (RCM) is a structured method for deciding what maintenance each asset needs. It starts with what the asset must do, works out how it can fail and what each failure would cost in safety, operations and money, and then picks the right task for each failure: monitor it, service it on a schedule, test it, redesign it or let it run to failure.
NASA's Reliability-Centered Maintenance Guide describes RCM as a program that combines preventive maintenance, predictive testing and inspection, repair and proactive work to raise the chance that equipment does its job, at the lowest life-cycle cost.
The key idea: RCM maintenance does not ask "how often should we service this?" It asks "what failure are we trying to prevent, and does this task actually prevent it?"
The core principles of RCM
Every RCM program, whatever the industry, rests on the same handful of principles.
Preserve the function, not the machine. The goal is that the asset keeps doing what its users need, to the standard they need, in the conditions it actually runs in.
Manage consequences, not just failures. A failure matters only as much as its effect on safety, the environment, operations or cost. That decides how much effort it deserves.
Every task must be applicable and effective. A task has to be technically able to prevent or detect the failure, and worth more than it costs. If it is neither, drop it.
Maintenance cannot beat the design. Maintenance can keep an asset at its built-in reliability, not raise it. If the design cannot meet the need, change the design or the way it is operated.
RCM is a living program. Every failure that still happens is data that feeds back into the analysis.
Where RCM came from
RCM started in commercial aviation. In the 1960s and 1970s, airlines found that heavy, time-based overhauls were not making aircraft more reliable. Two United Airlines engineers, F. Stanley Nowlan and Howard F. Heap, documented a new approach built around system functions, failure consequences and failure modes. Their report, Reliability-Centered Maintenance, was published in 1978 for the U.S. Department of Defense.
In 1999, SAE International published SAE JA1011, which sets the minimum criteria a process must meet to be called RCM. It was revised in 2009 and again in 2024, and is still the reference most practitioners use. Its companion, SAE JA1012, is a guide to applying it. Commercial aviation builds aircraft maintenance programs with MSG-3, which grew out of the same work, and the U.S. Department of Defense sets out its RCM process in MIL-STD-3034.
Why fixed-interval maintenance often misses
The research behind RCM found that most equipment does not fail on a predictable wear-out curve.
NASA's guide summarizes three studies (airline, Swedish and U.S. Navy data) and reports that random failures made up 77 to 92 percent of all failures. Only 8 to 23 percent were age-related.
The U.S. Department of Energy's Federal Energy Management Program puts it simply: age-related failures account for less than 20 percent of all failures.
Those studies sorted failures into six patterns. Only the first three get more likely as an asset ages.
Pattern | How the chance of failure behaves over time | Type | What it means for maintenance |
I | High at the start, flat, then rising at the end (the "bathtub curve") | Age-related | Scheduled replacement can work, but early failures after service still happen |
II | Flat, then a clear wear-out zone | Age-related | Scheduled restoration or replacement before the wear-out zone |
III | Rising slowly and steadily | Age-related | Condition monitoring usually beats a fixed interval |
IV | Low when new, rising quickly, then flat | Random | Condition monitoring or failure-finding, not age-based overhauls |
V | Flat across the whole life | Random | Condition monitoring, failure-finding or run to failure |
VI | High just after installation or service, then flat | Random | Avoid needless intrusive work; get installation and repair quality right |
If a failure is random, servicing more often does not stop it. Worse, every time you open up a healthy machine, you risk introducing a fault: a pinched seal, a missed torque, a contaminated reservoir. Pattern VI is exactly that effect. RCM points your effort at the failures that a task can actually prevent or catch early.
The 7 questions every RCM analysis answers
SAE JA1011 says a true RCM process answers seven questions, in this order, for each asset you analyze.
Functions: What does the asset need to do, and to what standard, in its current operating context?
Functional failures: In what ways can it fail to do that?
Failure modes: What causes each functional failure?
Failure effects: What happens when each failure occurs?
Failure consequences: In what way does each failure matter (safety, environment, operations or cost only)?
Proactive tasks: What can be done to predict or prevent each failure, and how often?
Default actions: What should you do if no suitable proactive task exists (for example, failure-finding tests, a redesign or running to failure)?
Questions 1 to 5 are about understanding the asset. Questions 6 and 7 are where maintenance tasks come from. Skip the first five and you are just writing a PM schedule with extra steps.
The P-F curve: how RCM sets inspection intervals
Most failures give a warning before they happen. The P-F curve shows that warning period. Point P is the earliest moment you can detect that a failure has started: a rise in vibration, a small weep at a seal, a temperature creeping up. Point F is functional failure, when the asset can no longer do its job. The time between them is the P-F interval.
Condition monitoring only works if you check often enough to catch the problem inside that window, with time left to plan the repair. Many practitioners inspect at no more than half the P-F interval. Different techniques find the same failure at different points: vibration analysis usually spots a worn bearing well before heat or noise does, which buys more planning time.
If the P-F interval for a failure mode is shorter than any practical check, condition monitoring will not work for it, and you move on to the next option in Step 6 below.
RCM vs preventive, predictive and proactive maintenance
RCM is not a fourth type of maintenance. It is the decision method that tells you which type to use for each failure mode.
Approach | What it means | When RCM picks it |
Reactive (run to failure) | Fix it when it breaks | Failure is cheap, safe and has no knock-on effect |
Preventive | Service or replace on a fixed interval (time, hours, cycles) | Failure is clearly age-related and the interval can be set with confidence |
Predictive (condition-based) | Monitor condition and act when it starts to drift | Failure gives a warning that you can measure in time to act |
Proactive | Remove the root cause (design, operating practice, lubrication, alignment) | The same failure keeps coming back |
For a closer look at the last three, see our guide to preventive vs predictive vs proactive maintenance.
Most maintenance teams lean far too hard on the first two. DOE's federal guidance compares the typical mix with what top-performing maintenance programs run:
Maintenance type | Industry average | Top performers |
Reactive | More than 55% | Less than 10% |
Preventive | 30% to 35% | 25% to 35% |
Predictive | 10% to 15% | 45% to 55% |
RCM vs FMEA, risk-based maintenance and risk-based inspection
These methods are often confused with RCM. They overlap, but each does a different job.
Method | What it does | How it relates to RCM |
FMEA (failure modes and effects analysis) | Lists how an asset can fail and what each failure does, often with severity and likelihood ratings | RCM uses an FMEA to answer questions 2 to 4, then adds consequences and task selection |
Risk-based maintenance (RBM) | Ranks assets and tasks by risk, meaning likelihood times consequence, to set priorities and budget | Often used to choose which assets get a full RCM analysis first |
Risk-based inspection (RBI) | Sets inspection plans for static pressure equipment such as vessels, piping and tanks; in oil and gas it follows API RP 580 and API RP 581 | Covers static equipment, while RCM is usually applied to active equipment such as pumps, engines and valves |
How to run an RCM analysis, step by step
You do not need to analyze every asset. Start small, prove it works and expand. NASA uses two levels of RCM: a rigorous, classical analysis for high-cost systems and a streamlined one for facility equipment. A streamlined analysis is faster, but a process that skips any of the seven questions no longer meets SAE JA1011.
Step 1: Pick the assets that matter most
Rank your equipment by criticality. Ask what happens if it fails: does someone get hurt, does a job stop, does a customer get billed late, or does it just cost a part? NASA's guide uses a 1 to 10 criticality scale, from no effect up to a hazard that occurs without warning. Start with the five to ten assets at the top of your list, usually the ones that stop revenue when they fail.
Step 2: Define functions and operating context
Write down what each asset must do, with numbers. "Pump fluid" is not a function. "Deliver fluid at the required rate and pressure for the full job, without leaks" is. Include the operating context: duty cycle, climate, remote site or yard, standby unit available or not.
Step 3: List the functional failures
For each function, list every way the asset can fall short: total loss, partial loss (cannot hold pressure), or doing something it should not (leaking).
Step 4: Find the failure modes
For each functional failure, list the specific causes. This is the FMEA part of the analysis. Pull failure modes from three places: your work order history, your technicians and the manufacturer's manual. Your own history is the most valuable source, which is why clean asset and work order records matter so much.
Step 5: Describe effects and rank consequences
For each failure mode, write what actually happens: what the crew sees, what stops, what it costs. Then sort it into one of four consequence groups: hidden (no one notices until something else fails), safety or environmental, operational, or cost only.
In oil and gas, the safety column deserves real attention. OSHA reports that three of every five on-site fatalities in oil and gas extraction come from struck-by, caught-in or caught-between hazards, and it lists failed high-pressure line connections as one source of struck-by hazards. Any failure mode with that kind of consequence needs a task that reliably prevents or detects it, or a redesign.
Step 6: Choose the right task for each failure mode
Work through the options in this order and stop at the first one that is both technically possible and worth the cost:
Condition monitoring: can you measure a warning sign (vibration, temperature, pressure, oil condition, leaks) early enough to act, inside the P-F interval?
Scheduled restoration or replacement: does the failure clearly follow age or usage?
Failure-finding test: for hidden failures, such as a relief valve or a standby unit, test it on a set interval to confirm it still works.
Redesign or change in practice: for safety failures with no workable task, change the equipment or the procedure.
Run to failure: for cost-only failures where nothing above pays off. NASA's guide is clear that run to failure is acceptable when it is a conscious decision backed by analysis.
Think about spares at the same time. A run-to-failure decision only works if the replacement part is on the shelf. Our guide to spare parts planning covers how to keep the right stock without tying up cash.
Step 7: Put the tasks into your work order system
An RCM analysis on a spreadsheet changes nothing. Each task needs to become a scheduled or triggered work order, assigned to someone, with the checklist and the evidence you need captured on completion. If you are deciding which system should hold this, our guide to CMMS vs EAM explains the difference.
Step 8: Review, measure and refine
Every failure that still happens is data. Review the analysis for each critical asset at least once a year, and straight away after any significant failure. Did a task catch the problem? Was the interval right? Did a new failure mode show up?
Track a few numbers for each critical asset: mean time between failures, availability, the share of maintenance work that is reactive, and how many failures your tasks caught early compared with how many they missed.
Worked example: RCM on a field pump
The table below shows part of an RCM analysis for a positive displacement pump used on a well service unit. The failure modes and tasks are illustrative. Your manufacturer's manual and your own failure history should set the real tasks and intervals. You can use the same columns as your own RCM worksheet.
Function: Deliver fluid at the required rate and pressure for the full job, without leaks.
Failure mode | Effect | Consequence | Chosen task | Task type |
Plunger packing wears and leaks | Visible leak at the fluid end, pressure drops over the job | Operational, with an environmental angle | Check for packing leaks at every rig-up and record the result | Condition monitoring |
Valves and seats wear | Pressure pulsation and lower output | Operational | Track pump hours and output, and inspect valves when pulsation rises or at the manufacturer's hour limit | Condition monitoring plus scheduled inspection |
Power end bearing wears | Rising vibration and heat, then possible seizure | Operational, high repair cost | Take vibration and oil condition readings on a set schedule and trend them | Condition monitoring |
Pressure relief valve sticks closed | Nothing visible until an overpressure event | Hidden, with a safety consequence | Function test on a fixed interval and record the result | Failure-finding test |
Discharge line connection loosens or erodes | Leak or line failure under pressure | Safety | Inspect connections and line condition before each job; replace on any damage | Condition monitoring |
Pressure gauge reads incorrectly | Crew works from wrong readings | Hidden, with a safety consequence | Calibrate on a fixed interval | Scheduled task |
Paint and decals fade | Cosmetic only | Cost only | No task. Repaint at the next shop visit | Run to failure |
Notice what is missing: there is no blanket "overhaul every X months" line. Every task links to a specific failure mode and a reason. That is what makes an RCM program cheaper to run than a calendar-based one, and more reliable.
The P-F curve is at work here too. For the packing, P is the first weep at rig-up and F is a leak the pump cannot hold pressure through. Checking at every rig-up keeps the inspection well inside that window.
Benefits and limits of RCM
What RCM gives you:
Fewer surprise failures on the things that matter. Tasks target the failure modes with real consequences.
Less wasted maintenance. Tasks that do not prevent anything get dropped. NASA's guide reports that savings of 30 to 50 percent of the annual maintenance budget are often obtained through a balanced RCM program.
A clear reason behind every task. When someone asks why a task exists, the analysis answers it.
Better safety decisions. Hidden and safety failures get explicit attention instead of being buried in a generic PM.
The evidence from public sources is consistent. One study cited in DOE's federal guidance found that, per horsepower of mechanical equipment, reactive maintenance cost about 200 percent more than an RCM program, preventive about 150 percent more and predictive about 50 percent more. NASA invested $15 million over three years in test equipment, software, training and staff to set up its program; maintenance work rose at first and then fell, and a study NASA commissioned in 2000 put the cost avoided at $26.8 million to $33.6 million, a return of 1.75 to 2.2 times the investment.
The cost of getting it wrong is high. A NIST study of U.S. manufacturers estimated maintenance costs at $74.5 billion in 2016. Establishments that relied most heavily on reactive maintenance had 3.3 times more downtime than those that relied on it least. Those investing more in preventive and predictive maintenance reported, on average, 44 percent less downtime.
Where RCM falls short:
It takes time up front. A proper analysis of one critical asset can take several working sessions with technicians in the room.
Costs can rise before they fall. NASA's guide notes that maintenance costs often increase for the first two to three years while monitoring is set up and backlogs are cleared.
It needs data. Without work order history and asset records, failure modes are guesses.
It is overkill for low-value assets. For cheap, non-critical equipment, a simple run-to-failure decision is enough.
What you need before you start
An asset register. Every unit, its location, its service history and its certifications.
Work order and failure history. Ideally a year or more, with failure causes recorded, not just "repaired".
A criticality ranking. Agreed by operations, maintenance and safety.
The right people in the room. A facilitator who knows the method, one or two technicians who work on the asset, an operator or crew lead who runs it and someone from safety. For complex equipment, add an engineer or the manufacturer's representative. Technicians know failure modes that no manual lists.
A baseline checklist. If you are starting from paper, our oilfield equipment maintenance checklist is a practical place to begin.
What to look for in RCM software
Two kinds of software support an RCM program. RCM analysis tools hold the FMEA, the decision logic and the reasoning behind each task, and some model intervals and follow standards such as SAE JA1011 or MSG-3. Maintenance management systems run the program day to day: they turn each task into a work order and capture what happened.
You can run your first analysis on a spreadsheet. Running the program needs a maintenance system. Look for:
Asset records that hold each unit's full maintenance, failure and certification history
Work orders that can be triggered by time, usage or condition, not just the calendar
Failure codes captured on every work order, so your analysis improves over time
Mobile checklists that work offline at remote sites and sync later
Alerts before certifications lapse or inspections fall overdue
Reports that show which tasks are catching problems and which are not
Equipt's oil and gas asset management software tracks digital certifications with automated reminders, schedules maintenance proactively to predict and prevent equipment failures, and captures field data offline at remote sites. Its built-in AI assistant, E-Genie, analyzes real-time health data and flags risks early.
To see how your own critical assets would look in a reliability-centered program, book a demo with the Equipt team.
Frequently asked questions
What is reliability centered maintenance in simple terms?
Reliability centered maintenance is a way of deciding what maintenance each piece of equipment really needs. You look at what the equipment must do, how it can fail and how much each failure would matter, then choose the task that best prevents or catches each failure. Tasks that do not prevent anything are dropped.
What are the 7 questions of RCM?
SAE JA1011 lists them as: what are the functions, how can the asset fail to perform them, what causes each failure, what happens when each failure occurs, how each failure matters, what can be done to predict or prevent each failure, and what to do if no suitable task can be found.
What is the difference between RCM and preventive maintenance?
Preventive maintenance is a type of task: service or replace on a fixed interval. RCM is the method that decides whether a fixed interval is the right task at all. For many failure modes, RCM will choose condition monitoring, a failure-finding test or run to failure instead.
What is the difference between RCM and FMEA?
An FMEA lists how an asset can fail and what each failure does. RCM includes that work but goes further: it ranks each failure by its consequences and then chooses the task, test, redesign or run-to-failure decision that manages it. An FMEA is one part of an RCM analysis.
What is the P-F curve in RCM?
The P-F curve shows how a failure develops, from point P, the first moment it can be detected, to point F, when the asset can no longer do its job. The time between them is the P-F interval. RCM uses it to set inspection intervals: check often enough to catch the failure with time left to plan the repair.
Is RCM worth it for a small fleet?
Yes, if you keep the scope small. Analyze only the few assets whose failure stops work or creates a safety risk, and use simple run-to-failure decisions for the rest. Even a handful of well-analyzed critical assets can cut unplanned downtime and wasted maintenance.
What does an RCM analysis produce?
It produces a maintenance plan for each analyzed asset: a list of failure modes, the consequence of each, and the task chosen to manage it, with the task type, interval or trigger, and the reason. Those tasks then become work orders in your maintenance system.
What is reliability centered maintenance software?
Two kinds of software support RCM. Analysis tools record functions, failure modes, consequences and task decisions. Maintenance management systems turn those decisions into scheduled or condition-triggered work orders and capture failure data from every job, which keeps the analysis current.
