Root cause analysis
In science and engineering, root cause analysis (RCA) is a method of problem solving used for identifying the root causes of faults or problems. It is widely used in IT operations, manufacturing, telecommunications, industrial process control, accident analysis (e.g., in aviation, rail transport, or nuclear plants), medicine (for medical diagnosis), healthcare industry (e.g., for epidemiology), etc. Root cause analysis is a form of deductive inference since it requires an understanding of the underlying causal mechanisms of the potential root causes and the problem.
RCA can be decomposed into four steps:
- Identify and describe the problem clearly
- Establish a timeline from the normal situation until the problem occurs
- Distinguish between the root cause and other causal factors (e.g., using event correlation)
- Establish a causal graph between the root cause and the problem
RCA generally serves as input to a remediation process whereby corrective actions are taken to prevent the problem from recurring. The name of this process varies from one application domain to another. According to ISO/IEC 31010, RCA may include the techniques Five whys, Failure mode and effects analysis (FMEA), Fault tree analysis, Ishikawa diagram, and Pareto analysis.
There are essentially two ways of repairing faults and solving problems in science and engineering.
Reactive management consists of reacting quickly after the problem occurs, by treating the symptoms. This type of management is implemented by reactive systems, self-adaptive systems, self-organized systems, and complex adaptive systems. The goal here is to react quickly and alleviate the effects of the problem as soon as possible.
Proactive management, conversely, consists of preventing problems from occurring. Many techniques can be used for this purpose, ranging from good practices in design to analyzing in detail problems that have already occurred and taking actions to make sure they never recur. Speed is not as important here as the accuracy and precision of the diagnosis. The focus is on addressing the real cause of the problem rather than its effects.
Root cause analysis is often used in proactive management to identify the root cause of a problem, that is, the factor that was the leading cause. It is customary to refer to the "root cause" in singular form, but one or several factors may constitute the root cause(s) of the problem under study.
A factor is considered the "root cause" of a problem if removing it prevents the problem from recurring. Conversely, a "causal factor" is a contributing action that affects an incident/event's outcome but is not the root cause. Although removing a causal factor can benefit an outcome, it does not prevent its recurrence with certainty.
Imagine an investigation into a machine that stopped because it was overloaded and the fuse blew. Investigation shows that the machine was overloaded because it had a bearing that wasn't being sufficiently lubricated. The investigation proceeds further and finds that the automatic lubrication mechanism had a pump that was not pumping sufficiently, hence the lack of lubrication. Investigation of the pump shows that it has a worn shaft. Investigation of why the shaft was worn discovers that there isn't an adequate mechanism to prevent metal scrap getting into the pump. This enabled scrap to get into the pump, and damage it.
The apparent root cause of the problem is that metal scrap can contaminate the lubrication system. Fixing this problem ought to prevent the whole sequence of events recurring. The real root cause could be a design issue if there is no filter to prevent the metal scrap getting into the system. Or if it has a filter that was blocked due to lack of routine inspection, then the real root cause is a maintenance issue.
Compare this with an investigation that does not find the root cause: replacing the fuse, the bearing, or the lubrication pump will probably allow the machine to go back into operation for a while. But there is a risk that the problem will simply recur, until the root cause is dealt with.
The above doesn't include cost/benefit analysis: does the cost of replacing one or more machines exceed the cost of downtime until the fuse is replaced? This situation is sometimes referred to as the cure being worse than the disease.
As an unrelated example of the conclusions that can be drawn in the absence of the cost/benefit analysis, consider the tradeoff between some claimed benefits of population decline: In the short term there will be fewer payers into pension/retirement systems; whereas halting the population will require higher taxes to cover the cost of building more schools. This can help explain the problem of the cure being worse than the disease.
Costs to consider go beyond finances when considering the personnel who operate the machinery. Ultimately, the goal is to prevent downtime; but more so prevent catastrophic injuries. Prevention begins with being proactive.
Root cause analysis is used in many application domains.
Manufacturing and industrial process control
The example above illustrates how RCA can be used in manufacturing. RCA is also routinely used in industrial process control, e.g. to control the production of chemicals (quality control).
RCA is also used for failure analysis in engineering and maintenance.
IT and telecommunications
Root cause analysis is frequently used in IT and telecommunications to detect the root causes of serious problems. For example, in the ITIL service management framework, the goal of incident management is to resume a faulty IT service as soon as possible (reactive management), whereas problem management deals with solving recurring problems for good by addressing their root causes (proactive management).
Another example is the computer security incident management process, where root-cause analysis is often used to investigate security breaches.
RCA is also used in conjunction with business activity monitoring and complex event processing to analyze faults in business processes.
Its use in the IT industry cannot always be compared to its use in safety critical industries, since in normality the use of RCA in IT industry is not supported by pre-existing fault trees or other design specs. Instead a mixture of debugging, event based detection and monitoring systems (where the services are individually modelled) is normally supporting the analysis. Training and supporting tools like simulation or different in-depth runbooks for all expected scenarios do not exist, instead they are created after the fact based on issues seen as 'worthy'. As a result the analysis is often limited to those things that have monitoring/observation interfaces and not the actual planned/seen function with focus on verification of inputs and outputs. Hence, the saying "there is no root cause" has become common in the IT industry.
Health and safety
In the domains of health and safety, RCA is routinely used in medicine (diagnosis) and epidemiology (e.g., to identify the source of an infectious disease), where causal inference methods often require both clinical and statistical expertise to make sense of the complexities of the processes.
RCA is used in environmental science (e.g., to analyze environmental disasters), accident analysis (aviation and rail industry), and occupational safety and health. In the manufacture of medical devices, pharmaceuticals, food, and dietary supplements, root cause analysis is a regulatory requirement.
RCA is also used in change management, risk management, and systems analysis.
Despite the different approaches among the various schools of root cause analysis and the specifics of each application domain, RCA generally follows the same four steps:
- Identification and description: Effective problem statements and event descriptions (as failures, for example) are helpful and usually required to ensure the execution of appropriate root cause analyses.
- Chronology: RCA should establish a sequence of events or timeline for understanding the relationships between contributory (causal) factors, the root cause, and the problem under investigation.
- Differentiation: By correlating this sequence of events with the nature, the magnitude, the location, and the timing of the problem, and possibly also with a library of previously analyzed problems, RCA should enable the investigator(s) to distinguish between the root cause, causal factors, and non-causal factors. One way to trace down root causes consists in using hierarchical clustering and data-mining solutions (such as graph-theory-based data mining). Another consists in comparing the situation under investigation with past situations stored in case libraries, using case-based reasoning tools.
- Causal graphing: Finally, the investigator should be able to extract from the sequences of events a subsequence of key events that explain the problem, and convert it into a causal graph.
To be effective, root cause analysis must be performed systematically. The process enables the chance to not miss any other important details. A team effort is typically required, and ideally all persons involved should arrive at the same conclusion. In aircraft accident analyses, for example, the conclusions of the investigation and the root causes that are identified must be backed up by documented evidence.
Transition to corrective actions
The goal of RCA is to identify the root cause of the problem with the intent to stop the problem from recurring or worsening. The next step is to trigger long-term corrective actions to address the root cause identified during RCA, and make sure that the problem does not resurface. Correcting a problem is not formally part of RCA, however; these are different steps in a problem-solving process known as fault management in IT and telecommunications, repair in engineering, remediation in aviation, environmental remediation in ecology, therapy in medicine, etc.
Without delving in the idiosyncrasies of specific problems, several general conditions can make RCA more difficult than it may appear at first sight.
First, important information is often missing because it is generally not possible, in practice, to monitor everything and store all monitoring data for a long time.
Second, gathering data and evidence, and classifying them along a timeline of events to the final problem, can be nontrivial. In telecommunications, for instance, distributed monitoring systems typically manage between a million and a billion events per day. Finding a few relevant events in such a mass of irrelevant events is asking to find the proverbial needle in a haystack.
Third, there may be more than one root cause for a given problem, and this multiplicity can make the causal graph very difficult to establish.
Fourth, causal graphs often have many levels, and root-cause analysis terminates at a level that is "root" to the eyes of the investigator. Looking again at the example above in industrial process control, a deeper investigation could reveal that the maintenance procedures at the plant included periodic inspection of the lubrication subsystem every two years, while the current lubrication subsystem vendor's product specified a 6-month period. Switching vendors may have been due to management's desire to save money, and a failure to consult with engineering staff on the implication of the change on maintenance procedures. Thus, while the "root cause" shown above may have prevented the quoted recurrence, it would not have prevented other – perhaps more severe – failures affecting other machines.
- Five whys – Iterative interrogative technique
- A3 problem solving – Structured problem improvement approach
- Eight disciplines problem solving – Eight Disciplines of Team-Oriented Problem Solving Method
- Factor analysis – Statistical method
- Failure mode and effects analysis – Analysis of potential system failures
- Engineering:Fault tree analysis – Failure analysis system used in safety engineering and reliability engineering
- Engineering:Forensic engineering – Investigation of failures associated with legal intervention
- Ishikawa diagram – Causal diagrams created by Kaoru Ishikawa
- Issue-based information system – Argumentation scheme
- Issue tree
- Orthogonal Defect Classification
- Structural fix
- ↑ See Wilson 1993, pp. 8–17.
- ↑ See IATA 2016 and Sofema 2017.
- ↑ See Manna 1995.
- ↑ See Lewerentz 1995.
- ↑ See Babaoglu 2005.
- ↑ See Ohno 1988.
- ↑ "The Cure Worse Than the Disease". The New York Times. November 5, 1927. https://www.nytimes.com/1927/11/05/archives/the-cure-worse-than-the-disease.html.
- ↑ Andrew C. Revkin (December 7, 2000). "Dredging River's PCB's Could Be a Cure Worse Than the disease, G. E. insists". The New York Times. https://www.nytimes.com/2000/12/07/nyregion/dredging-river-s-pcb-s-could-be-a-cure-worse-than-the-disease-ge-insists.html.
- ↑ Phillip Longman (June 9, 2004). "The Global Baby Bust". The New York Times. https://archive.nytimes.com/www.nytimes.com/cfr/international/20040501faessay_v83n3_longman.html.
- ↑ See Abubakar 2016.
- ↑ Landsittel, Douglas; Srivastava, Avantika; Kropf, Kristin (2020). "A Narrative Review of Methods for Causal Inference and Associated Educational Resources" (in en). Quality Management in Health Care 29 (4): 260–269. doi:10.1097/QMH.0000000000000276. ISSN 1063-8628. PMID 32991545. https://dx.doi.org/10.1097%2FQMH.0000000000000276.
- ↑ See OSHA 2019.
- ↑ Office of Regulatory Affairs (2019-12-26). "Corrective and Preventive Actions (CAPA)" (in en). FDA. https://www.fda.gov/corrective-and-preventive-actions-capa.
- ↑ US-FDA. "CURRENT GOOD MANUFACTURING PRACTICE FOR FINISHED PHARMACEUTICALS" (in en). https://www.ecfr.gov/.
- ↑ US-FDA. "CURRENT GOOD MANUFACTURING PRACTICE, HAZARD ANALYSIS, AND RISK-BASED PREVENTIVE CONTROLS FOR HUMAN FOOD" (in en). https://www.ecfr.gov/.
- ↑ US-FDA. "CURRENT GOOD MANUFACTURING PRACTICE IN MANUFACTURING, PACKAGING, LABELING, OR HOLDING OPERATIONS FOR DIETARY SUPPLEMENTS" (in en). https://www.ecfr.gov/.
- ↑ See IATA 2016.
- Abubakar, Aisha; Bagheri Zadeh, Pooneh; Janicke, Helge; Howley, Richard (2016). "Proc. 2016 International Conference On Cyber Security And Protection Of Digital Services (Cyber Security)".
- "Self-star Properties in Complex Information Systems; Conceptual and Practical Foundations". 3460. Springer. 2005.
- IATA (8 April 2016). "Root Cause Analysis for Civil Aviation Authorities and Air Navigation Service Providers". http://www.iata.org/training/courses/Pages/root-cause-analysis-talp37.aspx. "Key steps to conducting an effective root cause analysis, which tools to use for root cause identification, and how to develop effective corrective actions plans."
- "Formal Development of Reactive Systems; Case Study Production Cell". 891. Springer. 1995.
- Manna, Zohar; Pnueli, Amir (1995). Temporal Verification of Reactive Systems: Safety. Springer. ISBN 978-0387944593.
- Ohno, Taiichi (1988). Toyota Production System: Beyond Large-Scale Production. Portland, Oregon: Productivity Press. p. 17. ISBN 0-915299-14-3.
- "FactSheet: The Importance of Root Cause Analysis During Incident Investigation". https://www.osha.gov/Publications/OSHA3895.pdf.
- Sofema (17 November 2017). "Root Cause Analysis for Safety Management Practitioners & Business Area Owners". https://sassofia.com/course/root-cause-analysis-safety-management-practitioners-business-area-owners-2-days/. "Identify best practice techniques and behaviours to perform effective Root Cause Analysis (RCA)"
- Wilson, Paul F.; Dell, Larry D.; Anderson, Gaylord F. (1993). Root Cause Analysis: A Tool for Total Quality Management. Milwaukee, Wisconsin: ASQ Quality Press. ISBN 0-87389-163-5.
- "Cause Mapping a visual explanation"
- "Sologic Root Cause Analysis Method"
- "Fundamentals of Root Cause Analysis"
Original source: https://en.wikipedia.org/wiki/Root cause analysis. Read more