Reliability-Centered Maintenance was invented by the aviation industry — literally. The methodology that every serious manufacturing, energy, and heavy-equipment reliability program uses today traces directly back to United Airlines' MSG-1 and MSG-2 work in the 1960s and to Nowlan and Heap's landmark 1978 report to the Department of Defense that formalized the RCM approach the FAA and civil aviation regulators now require in some form for every certified aircraft. Yet the same aviation MRO facilities that gave the world RCM often struggle to operationalize it inside their own CMMS platforms. The failure modes get identified during MSG-3 working group sessions and end up in binders on a shelf. The task selections get documented in the MRB report and end up in a PDF nobody reads. The CMMS gets populated with time-based PMs that reflect what technicians have always done — not what the RCM analysis actually concluded. The gap between the analysis and the execution is where reliability programs die. This guide walks through the seven classic RCM questions that structure every rigorous reliability analysis, the failure consequence classification framework that determines task selection, the six RCM task types every program must map onto, the CMMS-RCM data hierarchy that turns analysis output into executed maintenance work, and the phased implementation roadmap that mature aviation MRO facilities actually follow. OxMaint gives Directors of Maintenance, Reliability Engineering Managers, and Chief Engineers the CMMS platform that operationalizes RCM output as tracked, executed, auditable maintenance work. Book a free demo to see CMMS-RCM integration inside OxMaint.
Q1
Functions & Performance Standards
What are the functions of the asset in its operating context, and what performance standards must it meet?
Q2
Functional Failures
In what ways can the asset fail to fulfill its functions or meet the performance standards?
Q3
Failure Modes
What causes each functional failure? (This is the foundational failure mode identification.)
Q4
Failure Effects
What happens when each failure occurs? (Physical evidence, secondary damage, operational impact.)
Q5
Failure Consequences
In what way does each failure matter? (Safety, environmental, operational, non-operational.)
Q6
Proactive Tasks
What proactive task can be done to predict or prevent each failure? (Condition-based, restoration, discard, failure-finding.)
Q7
Default Actions
What should be done if a suitable proactive task cannot be found? (Redesign, run-to-failure, hidden-failure protection.)
Every answer captured in OxMaint against the specific asset · the analysis output becomes the source data for PM triggers, work order libraries, and reliability KPIs
1978
the year Nowlan & Heap formalized RCM · developed for aviation · now the global standard for reliability engineering
SAE JA1011
the international standard that defines what qualifies as an RCM process · every rigorous program complies with these criteria
MSG-3
the aviation industry's task-oriented RCM methodology · foundation of every commercial aircraft's MRB document
Failure Consequence Classification — What Determines Task Selection
The single most consequential decision in RCM analysis is how you classify the consequences of each failure mode — because the consequence category directly determines what task type is appropriate. A failure with safety consequences must be addressed by a proactive task if one exists, regardless of cost. A failure with only non-operational consequences may legitimately be run-to-failure if the cost of prevention exceeds the cost of the failure itself. The classification matrix below reflects the RCM consequence framework every rigorous analysis applies. OxMaint stores the consequence classification against every failure mode so task type selection has a defensible audit trail. Start a free trial to structure your failure mode library inside OxMaint.
Failure Consequence Classification · The 2×4 RCM Matrix
Consequence classification drives task type · safety and hidden failures cannot be defaulted to reactive · every classification captured in the CMMS record
The RCM Task Framework — Six Task Types & When Each Applies
RCM analysis outputs one of six task types for every identified failure mode, and the appropriateness of each task type depends on the consequence classification, the failure pattern, and whether a technically feasible task actually exists. The framework below reflects the standard RCM task hierarchy applied in aviation MRO programs. OxMaint operationalizes each task type as a specific PM trigger configuration — condition monitoring runs against sensor data, scheduled restoration runs against runtime hours, scheduled discard runs against cycles or calendar, and failure-finding runs against operator-check schedules. Book a demo to see task-type-specific PM triggers inside OxMaint.
RCM Task Types · Six Categories with Trigger Logic
On-Condition
Condition-Based Monitoring
Sensor or inspection detects potential failure before functional failure · P-F interval determines cadence
Trigger: sensor threshold · inspection routine
Scheduled Restoration
Time or Cycle Overhaul
Restore item to as-new condition at fixed interval · applies when age-related failure pattern exists
Trigger: flight hours · cycles · calendar time
Scheduled Discard
Life-Limited Replacement
Replace item at defined life · life-limited parts (LLPs) · rotables with fixed cycle limits
Trigger: cycle count · hours to life limit
Failure Finding
Hidden Failure Detection
Verify function of normally-dormant protective device · applies to hidden failures only
Trigger: interval calculated from availability target
Redesign
Engineering Change
Modify design to eliminate the failure mode · applies when no proactive task is feasible for a safety consequence
Trigger: engineering change order · not PM-based
Run-to-Failure
No Scheduled Task
Repair or replace when failure occurs · legitimate only for non-safety non-hidden failures where prevention costs exceed failure cost
Trigger: reactive · failure event opens work order
Every Failure Mode · Every Task · Every Trigger — One Platform
OxMaint holds the RCM output as native operational data · failure mode libraries linked to work orders · PM triggers configured per task type · reliability KPIs generated from live maintenance execution.
CMMS-RCM Data Hierarchy — How Analysis Becomes Executed Work
The bridge between RCM analysis and operational execution is the CMMS data model. Rigorous RCM programs organize their asset data in a specific hierarchy — from the physical asset down through its functions, functional failures, failure modes, causes, and effects, ultimately terminating in the specific task or trigger that prevents the failure. When the CMMS mirrors this hierarchy, RCM analysis outputs flow directly into PM libraries, work order templates, and reliability reporting. When it does not, the analysis stays in binders and the CMMS runs on default time-based PMs. The framework below reflects the data hierarchy every mature RCM-integrated CMMS implements. Start a free trial to see the RCM-aligned asset hierarchy inside OxMaint.
CMMS-RCM Data Hierarchy · Asset to Task Traceability
Level 1
Asset
Physical asset · aircraft · engine · APU · component · registration / serial number
Level 2
Function
Intended function with performance standard · "provide takeoff thrust of 27,000 lbf ±2%"
Level 3
Functional Failure
Loss of function against performance standard · "unable to produce rated thrust"
Level 4
Failure Mode
Specific way failure manifests · "compressor blade fatigue fracture" · "fuel nozzle coking"
Level 5
Cause & Effect
Root cause with predicted effect · "high-cycle fatigue from resonance · leads to blade separation and secondary damage"
Level 6
Task & Trigger
Specific proactive task and its trigger · "borescope inspection every 500 cycles · replace at 15,000 cycle life limit"
Every RCM output stored in OxMaint at the correct hierarchy level · task-to-failure-mode traceability audit-ready for FAA and EASA inspection
Implementation Roadmap — Five Phases from Pilot to Enterprise
Aviation MRO RCM programs succeed or fail on sequencing. Attempting to run RCM analysis across an entire fleet or across every asset in a maintenance base simultaneously produces stalled analyses, disillusioned reliability engineers, and reverted programs. The mature approach follows a defined five-phase roadmap starting with a single critical asset pilot, expanding to a system-level analysis, then to a fleet-wide rollout with steady-state continuous review built in from Phase 4 onward. The framework below reflects how aviation MRO RCM programs actually reach steady state. Book a demo to see the phased RCM roadmap inside OxMaint.
RCM Implementation Roadmap · Five Phases · 12-24 Months
Phase 1
Pilot Asset Selection & Analysis
Months 1-3
Select single critical asset · assemble RCM working group · document functions and functional failures · establish baseline reliability metrics
Phase 2
Failure Mode Library & Task Selection
Months 3-6
Complete FMECA · classify consequences · select task types · document rationale · load failure mode library into CMMS
Phase 3
CMMS Integration & PM Deployment
Months 6-9
Configure PM triggers per task type · link work orders to failure modes · train technicians on new procedures · begin measuring impact
Phase 4
System & Fleet Expansion
Months 9-18
Roll out to additional systems and asset classes · scale reliability engineering capacity · integrate with airworthiness directives
Phase 5
Continuous Review & Optimization
Months 18-24+
Steady-state operation · reliability KPI reviews · task frequency optimization · MRB update cycle · closed-loop analysis on failure events
Phase 3 delivers first measurable ROI · Phase 4 achieves organizational scale · Phase 5 unlocks continuous reliability improvement
Director of Maintenance Perspective · Why the Analysis Alone Isn't Enough
The single most common failure mode of aviation MRO reliability programs is that the RCM analysis gets completed and then goes nowhere. I have seen it repeatedly across the industry — reliability engineering teams spend six months on a rigorous FMECA for a critical system, document every failure mode with proper consequence classification and task selection, produce a 200-page analysis binder, and then the CMMS keeps running the same time-based PMs it was running before the analysis started. The analysis lives in a shared drive. The CMMS lives in a different reality. That is not an RCM program. That is an RCM report. What changes everything is a CMMS that mirrors the RCM data hierarchy natively — where the asset record links to its functions, the functions link to their functional failures, the failure modes carry their consequence classification, and the tasks trace back to the specific failure mode they were selected to prevent. When we moved to OxMaint, that structural integration happened cleanly. Every PM in our library now traces to a specific failure mode. Every reliability KPI report shows which tasks are actually preventing which failures. And when an audit team asks why we perform a specific task at a specific interval, the answer is one click away rather than a two-week reconstruction from binders. That is the operational transformation. RCM analysis is only half the reliability program. The other half is the CMMS that makes the analysis executable and auditable at operational scale.
Failure Mode Library Live
OxMaint stores every failure mode with consequence classification · linked to the specific tasks that prevent it.
Task-to-Failure Traceability
Every PM traces to its underlying failure mode · audit response is one click, not two-week reconstruction.
Reliability KPIs Auto-Generated
MTBF, MTBUR, task effectiveness produced from live work order data · not manually assembled quarterly.
Make Your RCM Program Executable at Operational Scale
If your RCM analysis lives in binders and shared drives while your CMMS keeps running the same time-based PMs it always ran, the reliability program is not real. See what OxMaint — a CMMS built for RCM-integrated aviation MRO operations — looks like against your maintenance program.
Frequently Asked Questions
What are the seven classic RCM questions?
The seven questions defined by SAE JA1011: (1) What are the functions and performance standards of the asset? (2) In what ways can it fail to fulfill 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 proactive task can be done to predict or prevent each failure? (7) What should be done if a suitable proactive task cannot be found? Every rigorous RCM analysis answers all seven in sequence.
What is MSG-3 and how does it relate to RCM?
MSG-3 (Maintenance Steering Group - 3) is the aviation industry's task-oriented RCM methodology, developed by the Air Transport Association. Every commercial aircraft's Maintenance Review Board (MRB) document is built using MSG-3 analysis, which categorizes failure consequences and selects task types using a decision-tree logic derived from classic RCM principles. MSG-3 is essentially RCM operationalized for aviation certification requirements.
What are the six RCM task types?
On-Condition (condition-based monitoring using sensors or inspection); Scheduled Restoration (time or cycle-based overhaul); Scheduled Discard (life-limited replacement at defined life); Failure Finding (verification of dormant protective device function); Redesign (engineering change to eliminate the failure mode); and Run-to-Failure (no scheduled task, legitimate only for non-safety non-hidden failures where prevention cost exceeds failure cost). Task selection depends on consequence classification and technical feasibility.
How does failure consequence classification work?
Failures are classified across two dimensions: whether the failure is hidden (not evident to operating crew under normal conditions) or evident, and the consequence category (safety, environmental, operational, or non-operational). The intersection determines what task types are appropriate. Safety consequences require a proactive task if one is technically feasible, regardless of cost. Hidden failures require failure-finding tasks. Non-operational evident failures can legitimately be run-to-failure. OxMaint stores the classification per failure mode with defensible audit trail.
How does a CMMS integrate with RCM analysis?
Through a data hierarchy that mirrors RCM analysis structure: Asset → Function → Functional Failure → Failure Mode → Cause & Effect → Task & Trigger. Every RCM analysis output is stored at the correct hierarchy level. PM triggers are configured per task type (condition-based, restoration, discard, failure-finding). Work orders trace back to specific failure modes. Reliability KPIs generate from live operational data. This is the difference between RCM as a shelf document and RCM as executed operational discipline.
What KPIs do aviation MRO reliability programs track?
Standard metrics include Mean Time Between Failures (MTBF), Mean Time Between Unscheduled Removals (MTBUR), Mean Time Between Shop Visits (MTBSV), component reliability index, dispatch reliability, delay and cancellation rates attributable to maintenance, and task effectiveness measured against predicted failure rates. Mature programs also track P-F interval data for condition-based tasks and life-limited-part utilization trends. OxMaint generates these KPIs from live work order data rather than requiring manual quarterly assembly.
