What Is RCA (Root Cause Analysis)? Definition, Methods, and Manufacturing Examples

RCA (Root Cause Analysis) is a systematic process for identifying the fundamental cause of a problem — not the symptom — so that corrective actions prevent recurrence rather than just fixing the immediate issue.

Definition

RCA meaning: Root Cause Analysis. The term is sometimes expanded to RCCA (Root Cause and Corrective Action) in formal quality management systems, which underscores that finding the root cause is only half the work — implementing an effective corrective action that prevents recurrence is the other half.

The core principle of RCA is that every undesirable event has at least one root cause, and that root cause is almost never the same as the symptom that was first observed. A machine stops producing — that is the symptom. The root cause might be a worn bearing, a lack of lubrication, an absent PM schedule, or a procurement decision to use a lower-rated lubricant. Addressing only the symptom (restart the machine) guarantees the problem will return.

RCA is required or strongly expected in several manufacturing quality standards: AS9100 (nonconformance investigation), ISO 13485 (Corrective and Preventive Action — CAPA), IATF 16949 (8D customer complaint response), and FDA 21 CFR Part 820 (medical device quality system). Even manufacturers not subject to regulatory requirements benefit from systematic RCA — it is one of the highest-leverage quality and operations improvement tools available.

The 4 Most Common RCA Methods in Manufacturing

1. 5 Whys

The simplest and most widely used RCA method. Ask "why?" iteratively until you reach a cause you can control and fix. Works best for relatively simple, linear failures.

Example: A machine stopped on the production floor.

• Why? The fuse blew.
• Why? The circuit was overloaded.
• Why? The motor was pulling excess current.
• Why? The motor bearings were not lubricated.
• Why? No lubrication schedule existed for this machine.

Root cause: no preventive maintenance lubrication schedule. Corrective action: create and implement a PM schedule for all production equipment, starting with this machine.

2. Fishbone Diagram (Ishikawa Diagram)

A visual cause-and-effect diagram that organizes potential causes into six standard categories — the 6Ms: Machine, Method, Material, Man (People), Measurement, and Mother Nature (Environment). Useful for complex problems with multiple contributing factors across different functions.

The team writes the problem statement in the "head" of the fish and brainstorms causes in each category branch. Sub-causes are added to each branch. The completed diagram visually shows which category has the most potential causes and where investigation should focus first.

3. Fault Tree Analysis (FTA)

A top-down, deductive approach that maps all possible failure paths leading to an undesired event using boolean logic gates (AND, OR). Particularly useful for complex systems where multiple simultaneous failures are possible — common in aerospace, defense, and process industries. FTA produces a quantitative probability estimate for the top-level failure event if component failure rates are known.

4. 8D (Eight Disciplines)

A structured, team-based problem-solving process originally developed by Ford and now required by many automotive OEMs (IATF 16949). The 8 disciplines are:

1. D1 — Form the team
2. D2 — Describe the problem
3. D3 — Implement interim containment actions
4. D4 — Identify and verify root causes
5. D5 — Choose and verify permanent corrective actions
6. D6 — Implement permanent corrective actions
7. D7 — Prevent recurrence (update FMEAs, work instructions, standards)
8. D8 — Recognize the team

8D produces a formal report submitted to the customer. It is the expected response format for customer complaints in automotive and is increasingly used in aerospace and medical device manufacturing.

Manufacturing Example: On-Time Delivery RCA Using 5 Whys

A contract manufacturer's on-time delivery (OTD) fell from 91% to 72% in Q2. The operations manager initiates an RCA.

5 Whys:

• Why did OTD fall to 72%? Jobs are finishing late at the CNC turning center.
• Why is the turning center behind? It is a bottleneck with a 3-4 day queue depth.
• Why is there a 3-4 day queue? One of the two certified CNC lathe operators left in March and was not replaced.
• Why was the operator not replaced? The skills matrix showed only two certified operators and no cross-training plan existed.
• Why did no cross-training plan exist? Cross-training was never prioritized because capacity always seemed sufficient until now.

Root cause: no cross-training program for operators on critical equipment, combined with no early-warning system when certified operator count falls below minimum coverage threshold.

Corrective actions:

1. Cross-train two additional operators on CNC turning within 60 days
2. Add certified operator count by work center to the monthly capacity review dashboard
3. Define a minimum certified operator threshold for each critical work center and trigger an alert when the count falls below it
4. Update the FMEA for the turning work center to reflect operator coverage as an occurrence factor

After implementing these actions, OTD returned to 93% in Q3 — above the pre-Q2 baseline.

RCA in Production Scheduling

Late deliveries, schedule disruptions, machine breakdowns, and quality holds should all trigger RCA. The production schedule should not be adjusted for the same root cause twice without a corrective action in place. If a shop adjusts for a supplier late delivery once by pulling forward other jobs, that is a reasonable response. If the same supplier delivers late three months in a row and the response is always another schedule scramble, that is a systemic failure requiring RCA — not another schedule adjustment.

EDGEBI provides the historical data foundation that makes manufacturing RCA effective. Schedule adherence rates by work center, machine downtime logs by shift and operator, and on-time delivery trends over rolling 12-week windows surface the patterns that point investigators toward root causes. Without this data, RCA teams are working from memory and anecdote. With it, they can quantify the impact, identify the exact onset date, and correlate the problem to specific changes in personnel, equipment, suppliers, or process parameters.

When RCA is required by regulation, the documentation standard matters as much as the analysis itself. AS9100 requires that nonconformance investigations document the root cause determination method used. ISO 13485 CAPA records must show that the root cause was verified (not just assumed) and that the corrective action effectiveness was checked at a defined interval.

How to Implement RCA

• Define the problem precisely before starting — "quality is bad" is not an RCA problem statement; "surface finish rejections at the grinding operation increased from 2.1% to 8.7% in March" is
• Choose the right method for the problem complexity — 5 Whys for simple linear failures; Fishbone for multi-factor problems; 8D for customer-facing quality escapes
• Involve the people closest to the process — operators and technicians almost always know contributing factors that management does not
• Distinguish containment from correction — containment stops the bleeding (quarantine bad parts, add 100% inspection); corrective action addresses the root cause and prevents recurrence
• Verify effectiveness — close the RCA only after monitoring data confirms the failure rate has returned to baseline or better
• Update your FMEA and work instructions — D7 is the most skipped step and the most important for preventing recurrence at scale

---

---

Learn more: See how RMDB and EDGEBI provide the historical scheduling and performance data that powers effective manufacturing RCA. Contact User Solutions for a demo.