Author: Pratik Baldota/Mihir Pewekar
Date: 05/06/2020
Home / Blogs / Root Cause Analysis

ROOT CAUSE ANALYSIS

We, humans, have a natural gift of creativity, memory and imagination and we can attribute our ability to develop complex engineering systems to these gifts. Inevitably, the rise in complexity is accompanied by a rise in the problems that need troubleshooting. In this result-oriented world, often we don’t invest time in performing in-depth analysis in problem-solving. Instead, we opt for remedial actions to make the problem less visible or employ a patchwork type of solutions, hoping the problem won't resurface. When such solutions are employed, the probability of recurrence of that problem becomes high. Engineers at this junction employ the "Root cause Analysis".

This article intends to acquaint the reader with the philosophy of Root-Cause analysis and its underlying methodologies. This article also puts forth the tools that aid the analysis.

TERMINOLOGY

Problem statement: A problem statement is a concise description of an issue to be addressed or a condition to be improved upon.

Cause: It is efficacy, by which one event, process or state contributes to the production of another event, process, or state.

Different Levels of Causes:

Root-Cause Analysis: The root-cause analysis is a set of mental activities that help in the identification of the true cause of a problem and then suggesting actions necessary to eliminate it.

OBJECTIVES

TOOLS IN RCA

Flowcharts

Flow charts can be used in various stages of the RCA process. It is a fundamental tool in understanding the process. It helps in converting the actual work process to a logical flow diagram portraying the activities involved in the process. The flow charts are created using the ANSI standard symbols for flow charts. Inclusion of all working elements in the flow chart is essential. Inputs from all the departments concerned are very important. Define the role of the customers, in the chart, as they receive the output and provide part of the input. Also, include the suppliers in the chart, they are the other half of the input.

Figure 1: Schematic of a Flowchart

Brain Storming

Brainstorming is an essential tool in root cause analysis. Brainstorming involves a team of knowledgeable people coming together and generating hypotheses for the causes or generating solutions for the identified cause. Brainstorming should ideally be divided into two phases:

Cause and Effect Diagram

The cause and effect diagram was created by Professor Kaoru Ishikawa in 1943. This diagram is popularly known as the Fish-Bone Diagram. This tool enables the team to focus on the content of the problems rather than the history (i.e. when and rate of recurrence). The development of the Cause- Effect Diagram is a part of the Structured Brainstorming Exercise.

Steps for creating the diagram are as follows:

Step 1: Decide on the problem to improve or control.

Step 2: Define the characteristic Effect

Step 3: Write the main factors that may be causing the problem by drawing major branch arrows to the main arrow.

step 4: Detailed causal factors are written as twigs on each major branch of the diagram.

Step 5: Ensure all the factors are considered.

Figure 2: Illustration of Cause and effect Diagram

Statistical Analysis

The statistical analysis is very effective tool in analysing the data collected about the problem. The data may follow a normal or non-normal distribution. Depending on the type of distribution, different tests can be used to do statistical comparisons. Design of experiment (DOE) can be setup to categorically collect and compare the results between different variables. There are myriad of statistical tools and techniques that can be used to analyse the large data. This approach is data driven and helps you make decision more objectively. This data is also useful for Quality assessment.

Figure 3: Normal distribution curve for estimation of quality by statistical analysis (Courtesy: Wikimedia)

Logic Tree

A logic tree is quite similar to a flowchart. It is specifically used when there is no standardised work process. The logic tree is a visual illustration of the Ask why five times approach. The logic tree can be constructed using different mindsets.

Figure 4: Illustration for Logic Tree- For a simple Wireless Printer Error

METHODOLOGIES

Ask Why Five times- This process is used for simple problems, wherein the manager, repeatedly asks questions until the actual root cause comes forth. This is a simple and elegant way to approach routine day to day problems. Generally, by the 3rd why the probable root causes start appearing.

Events and causal factor analysis— This process is widely used for major, single event problems such as a fire in the electrical system of machinery. It creates a timeline of activities that took place leading to the event and is based on the analysis of the methodically gathered evidence. Contributing factors can be thus identified.

Figure 5: Illustration for Event Causal Analysis

Change analysis— This approach applies to situations where a system's performance has shifted significantly. It deals with the changes made to the working elements of the process under consideration for Root- Cause analysis. It analyses the changes brought about by the problem under consideration. The technique useful for this analysis is evaluating the time frame when changes occurred and when the problem was detected.

Change analysis— This technique base on the detection and prevention of occurrence of a problem. When designing a system, the designer installs certain controls that prevent the occurrence of a problem. When a problem occurs, one of these barriers may have failed. The barrier is categorised as soft (Administrative) barriers and hard (Physical) barriers.

Further, they can be classified as

Kepner-Tregoe Problem Solving— This model is quite extensive. And helps in the solution of complex problems methodically. This model makes sure that at the end of the undertaken analysis an informed decision is made.

This model provides four distinct phases for resolving problems:

Figure 6: Illustration for a Kepner and Tregoe Process

Six Sigma DMAIC (Define- Measure- Analyse -Improve -Control) — DMAIC is a data-driven quality assurance strategy for improving the process. It is a standalone methodology to address a problem.

Advantages of using this model:

Plan-Do-Check-Act (PDCA) — It is an iterative process to control and continually improve the process or performance of a product.

This model is highly used in lean Manufacturing.

Figure 7: Schematic Flow of the PDCA Model (Courtesy: Wikipedia)

ADVANTAGES

LIMITATIONS

IMPROVIANS TAKE

The application of the discussed methodologies are as follows:

Ask Why Five times- This model is implemented when the nature of the problem is less complex. This methodology is should be the first response to the detection of a symptom of a problem. These apply in all types of processes from the Design of a product to large scale production.

Events and causal factor analysis— This process is widely used for major, single event problems. This cannot be used in case of continually recurring problems in a manufacturing setup.

Change analysis and Barrier analysis— These methods are used to find the probable causes in any Study of Root cause analysis.

Kepner-Tregoe Problem Solving— This model is quite extensive. These were used by NASA in many spaceflight operations. Used in solving the complex problems methodically. They are generally not used in the case of defectives in large production.

Six Sigma DMAIC (Define- Measure- Analyse -Improve -Control) —This method is used for improving the quality standards of a manufacturing process.

Plan-Do-Check-Act (PDCA)— Being an iterative process, it focuses on continual improvement. It assumes that skills and Knowledge are limited. Thus, it is used in cases where the team consists of numerous people. In such a condition, the knowledge and skill increase gradually. Root-Cause analysis using this method is more gradually than fast.

Eight Discipline (8D) model- It provides concrete disciplines to produce a permanent corrective action based on statistical data analysis. These are more evidently employed in the automotive industry.

At Improvians, we can help you with all your problem-solving requirements.

+
-
References
  1. https://en.wikipedia.org/wiki/Pareto_principle
  2. https://asq.org/quality-resources/eight-disciplines-8d
  3. https://en.wikipedia.org/wiki/Flowchart
  4. https://en.wikipedia.org/wiki/PDCA
  5. A. Mark Doggett (2005) Root Cause Analysis: A Framework for Tool Selection, Quality Management Journal, 12:4, 3445 , DOI: 10.1080/10686967.2005.11919269
  6. Anderson, Bjorn: Root Cause Analysis: Simplified Tools and techniques, ASQ Quality Press,2006
  7. Okes, Duke: Root cause Analysis, ASQ Quality Press,2019
  8. https://en.wikipedia.org/wiki/Causality
  9. https://en.wikipedia.org/wiki/Problem_statement
  10. https://en.wikipedia.org/wiki/Normal_distribution
  11. https://commons.wikimedia.org/wiki/File:Empirical_Rule.PNG

COMPUTER AIDED DESIGN

Design Engineering and prototyping

PRODUCT VALIDATION AND SUPPORT

We are ready to get started. Are you?