Root Cause Analysis

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 4: Line 4:
 
A Root Cause Analysis can be divided into three steps:
 
A Root Cause Analysis can be divided into three steps:
  
*'''Identify''' – What went wrong? Do not look at symptoms of the fault or problem, but discover what specifically went wrong and caused the fault or problem
+
*'''Identify''' – What went wrong? Do not look at symptoms of the fault or problem, but discover what specifically went wrong and caused the fault or problem.
  
*'''Establish a timeline''' – Establish a timeline that specifies how the situation went from normal to problematical
+
*'''Establish a timeline''' – Establish a timeline that specifies how the situation went from normal to problematical.
  
*'''Distinguish root causes from other casual factors''' – Sort out factors that actually made the failure or problem occur. This can e.g. be done using event correlation
+
*'''Distinguish root causes from other casual factors''' – Sort out factors that actually made the failure or problem occur. This can e.g. be done using event correlation.
  
*'''Establish an overview between the root cause and the problem''' – Document how the root cause caused the fault or problem, this can be done e.g. with a casual graph
+
*'''Establish an overview between the root cause and the problem''' – Document how the root cause caused the fault or problem, this can be done e.g. with a casual graph.
  
  
  
 
__TOC__
 
__TOC__
 +
 +
==Introduction==
  
 
==General principles==
 
==General principles==
 +
 +
 +
 +
 +
 +
==Challenges==

Revision as of 14:48, 24 February 2022

Root Cause Analysis (RCA) is a method of problem solving that can be used in a project, program or portfolio (PPP) to identify root causes of faults and problems in order to identify appropriate solutions. It is broadly used in several industries, among the health care, infrastructure and information technology industry. A Root Cause Analysis supposes that it is more effective to go in-depth of occurring problems, so that the underlaying issue can be treated, instead of only treating ad hoc symptoms. Root Cause Analyses can be performed with several different methodologies, principles and techniques together to identify the root causes of a fault or problem. The goal is to find out where processes or systems failed or caused an issue in the first place.


A Root Cause Analysis can be divided into three steps:

  • Identify – What went wrong? Do not look at symptoms of the fault or problem, but discover what specifically went wrong and caused the fault or problem.
  • Establish a timeline – Establish a timeline that specifies how the situation went from normal to problematical.
  • Distinguish root causes from other casual factors – Sort out factors that actually made the failure or problem occur. This can e.g. be done using event correlation.
  • Establish an overview between the root cause and the problem – Document how the root cause caused the fault or problem, this can be done e.g. with a casual graph.


Contents


Introduction

General principles

Challenges

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox