CAUSE ANALYSIS CA www.ioas.org.

Slides:



Advertisements
Similar presentations
Accident and Incident Investigation
Advertisements

Facilitating the UCO Action Project Process – Part 4 Analyzing Data – Office of Planning & Analysis University of Central Oklahoma.
5 Why’s Overview.
OSHA’s Voluntary Protection Program (VPP) Job Hazard Analysis Mishap reporting 1 This class is only intended to familiarize you with the programs in place.
Title: The title should accurately describe the issue to be addressed and can never contain a proposed countermeasure. Overview Note: Remember that the.
Root Cause Analysis for Effective Incident Investigation Christy Wolter, CIH Principal Consultant Environmental and Occupational Risk Management (EORM.
ISHIKAWA DIAGRAM – Tool for quality management Marit Laos IS Project Management
ROOT CAUSE ANALYSIS. Outlines What is root causes analysis RCA RCA history RCA importance basic elements of RCA.
Root Cause Analysis Presented By: Team: Incredibles
1.3 ORGANIZATIONAL PLANNING & DECISION MAKING: FISHBONE ANALYSIS HL (HIGHER LEVEL CONTENT)
Product Market Sector: Air Conditioning ASQ Memphis Origin of 8 Discipline Corrective Action April 15, 2014 Prepared by: M. Nick Mahintorabi Date: Jun.
Root Cause Analysis: Why? Why? Why?
The information contained in this presentation, the source code and underlying program are protected by copyright owned by PlusDelta Technologies, LLC.
Training.
How to Implement, Process and Administer the Preventive Action Process
Preventive Action Training
© Mahindra Satyam 2009 Defect Management and Prevention QMS Training.
Root Cause Tutorial Page 1 More on Hazard Identification Techniques 1.Identify potential hazards that could threaten the safety of your employees,
Root Cause Analysis Training and Explanation 1.
Periodic Review of JHA Reviewing job hazard analysis ensures that it remains current and continues to prevent accidents and injuries. It is possible that.
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Monitoring, review and audit.
1 Kevin O’Connor Airworthiness Surveyor Civil and Military Design, Production & Continuing Airworthiness Root Cause Analysis Project…
Accident Investigation. Introduction When an accident happens at your facility- whether an injury occurs.
5 Why analysis By its very nature, a Lean Six Sigma program requires a number of changes throughout the organization. That’s what we are trying to do right?
Root Cause Analysis Roger Brauninger
HOSPITAL ACCREDITATION & RETAINING QUALITY
Lab Standards + Documentation Committee
Inspecting Software Requirement Document
5 Why’s Overview.
A method by which natural phenomena are explained
Introduction paragraph – what looking to investigate.
8D Report training Yu LaiLai Nov
Risk Tolerance Factor # 10 Role Models Accepting Risk
Multilinear Events Sequencing
ROOT CAUSE ANALYSIS RCA
Root Cause Analysis: An Introduction
Materials info consultancy private limited
IAEA E-learning Program
Take-Away Learning To understand why knowledge of how to improve learning isn’t always enough to improve learning. To identify causes and symptoms of the.
Testing Hypotheses about Proportions
What Helped Dana in physics go from a 54 exam score to a 91, and end up with a 90 on the final? Dana’s Problem: She used the example problems in the book.
Question Answer Relationship ?.
Scientific Method Foldable
Overview (1 of 2) Definition Use within organizations
Practicum: Root Cause Analysis
OVID Refresher Inspector Course
Director, Quality and Accreditation
Root Cause Analysis for Effective Incident Investigation
MQii Root Cause Analysis Overview
Root Cause Analysis Thomas S. Arneson 12/26/2018 Focus Consulting.
Project Quality Management
Root Cause Analysis: Why? Why? Why?
5 Why’s Overview.
Quality Risk Management ICH Q9 Frequently Asked Questions (FAQ)
Bellwork Assignment On a sheet of notebook paper, answer the following questions in ONE PARAGRAPH: What do you know about the writing process or writing.
5 Why’s Overview.
Accident Investigation
AS 9100 Awareness Training.
Failure Investigation Process
Fishbone Diagrams (cause and effect, or Ishikawa diagrams)
Measure Phase Wrap Up and Action Items
When should root cause analysis be performed?
by Operational Excellence Consulting LLC
TS
Quality Assurance in Clinical Trials
Safety toolbox Johnnie Stanton-MECA
Formulating Research Questions (RQ’s) Refer EXERCISE # 1
CAPA, Root Cause Analysis, and Risk Management
Presentation transcript:

CAUSE ANALYSIS CA www.ioas.org

What do you know about CA? A tool for systematic investigation and analysis Reactive analysis Incident investigation – may apply to losses, failure, inefficiencies What went wrong? What were the causes? What changes should be made? Cause analysis helps identify what, how and why something happened, thus preventing recurrence. Diving deep to find the source of the problem - to avoid addressing just the symptom. Causes are underlying factors, are reasonably identifiable, can be controlled and allow for generation of recommendations. Various techniques may be used. www.ioas.org

Causes are those that can reasonably be identified. those management has control to fix. those for which effective recommendations for preventing recurrences can be generated. www.ioas.org

Inspector uses wrong version of the inspection form… The typical investigation would probably conclude “inspector error” was the cause, inform the inspector and give him the right form. But if the analysis stops here, it has not probed deeply enough to understand the reasons for the mistake. Not enough is known to prevent it from occurring again or to be sure it is not a widespread problem. An example www.ioas.org

There may be more than 1 cause of a problem… www.ioas.org

Many methodologies are employed in CA Complex Failure Modes and Effects Analysis (FMEA) Causal factor charting Statistical data analysis Fishbone or Ishikawa diagram Simple Five Whys May incorporate simple techniques from complex analysis simple cause and effect maps fishbone diagrams Complex analyses apply more to sectors such as health and safety, transportation industries, and manufacturing. Often employed by consultants who do not have an intimate knowledge of the company or industry Simple analyses are appropriate for sectors such as business processes where the person or team is very familiar with the entire system. A Cause Map provides a visual explanation of why an incident occurred.  It connects individual cause-and-effect relationships to reveal the system of causes within an issue.  A Cause Map can be very basic and it can be extremely detailed depending on the issue. www.ioas.org

5 Whys Problem Cause(s) Analysis Corrective actions www.ioas.org 5 Whys is a Cause Analysis Tool, not a problem solving technique. Focus on 5 Whys because it is appropriate for most of the types of issues we face in certification and accreditation which are generally less complex and the analysis is performed by people who are familiar with the system. The outcome of the analysis is one or several causes that ultimately identify the reason why a problem was originated. There are other similar tools that can be used simultaneously with the 5 Why’s to enhance the thought process and analysis. www.ioas.org

Why did the inspector use the wrong form? It was the only form he had. He has always used that form, no one ever commented. Why did he have only that form? The inspector manager did not provide inspectors with the revised versions. Why did the inspector manager not provide inspectors with revised versions? She doesn’t make the revisions. She doesn’t see reports. She didn’t know it was necessary. She never thought about it. Why did she not think about it? Not part of her training, job description, work instructions or procedures. www.ioas.org

The inspector has been using the wrong form for years The inspector has been using the wrong form for years. Why was this not caught? The review team did not know it was important. Why did they not know it was important? Use of current forms is not part of their training, was never mentioned before and they have no control over what the inspector does anyway. Why? Why? Why? www.ioas.org

In addition to asking why - writing it down may help the analysis. Wrong form Not noticed by reviewers Didn’t know it was important Didn’t have authority Inspector has old forms Manager did not know Write the problem down. Often it helps to use a cause-effect diagram Investigate, interview people, don’t rush to judgement or make assumptions. www.ioas.org

Fishbone diagram Had only old forms No one noticed Unaware of changes Reviewers not trained Unable to access current formats No one responsible Inspector uses wrong form Also referred to as Ishikawa diagram after the person who first used it. Cause 4 www.ioas.org Cause 3

5 Whys rules of thumb State the problem clearly. 5 is the number at which most causes are clearly identified. Do not worry about not meeting or exceeding 5 Whys. Follow your thought process to decide how many Why’s you need to get to the point where the cause is evident. This is an investigative process. You don’t need to answer all Whys at once. The outcome of 5 Whys (or other analysis) is a cause analysis, not the resolution. Corrective actions and effectiveness verification follow. A well defined problem is a half-solved problem www.ioas.org

www.ioas.org