Www.stangerweb.de Root Cause Analysis Training and Explanation 1.

Slides:



Advertisements
Similar presentations
Quantitative and Scientific Reasoning Standard n Students must demonstrate the math skills needed to enter the working world right out of high school or.
Advertisements

Accident and Incident Investigation
CAUSE & EFFECT DIAGRAM (Fishbone or Ishikawa Diagram) Dr
Help! I’m in an Abusive Relationship
5 Why’s Overview.
8D Corrective Action. 2 8D Problem Solving & Corrective Action: Initiate 8D Corrective Action D1 - Create Problem Solving Team D2 - Define the Problem.
A3 PROBLEM SOLVING TOOL: Date: Contact: SOLUTIONS / COUNTERMEASURES What solutions will solve the root causes? (Tools: Brainstorming and Affinity Diagram)
Title: The title should accurately describe the issue to be addressed and can never contain a proposed countermeasure. Overview Note: Remember that the.
PHD Performance Management Program Matt Gilman Spencer Soderlind Brieshon D’Agostini September 28, 2011 PDCA Training Series 2 PLAN, Part 2.
Root Cause Analysis for Effective Incident Investigation Christy Wolter, CIH Principal Consultant Environmental and Occupational Risk Management (EORM.
Assessment.
SAFETY Is Everyone’s Responsibility
ISHIKAWA DIAGRAM – Tool for quality management Marit Laos IS Project Management
Business Operating System
Event Review Using HFACS (Template)
Root Cause Analysis Presented By: Team: Incredibles
Effective Problem-Solving: Getting to the Heart of the Matter © Copyright 2011– Lean Homecare Consulting Group, LLC This presentation is distributed for.
Leadership & Team Building
Occupational Health, Safety & Environment Training Incident Reporting & Investigation.
JOB HAZARD ANALYSIS Example Guide.
Hazard Identification
Collecting, processing and using… The Importance of Data.
What are the Benefits? Action AKA TPM, Total Preventative Maintenance Total Productive Maintenance Breakdowns 1 Setup / adjustment 2 Idling / minor stoppages.
Topic 5 Understanding and learning from error. LEARNING OBJECTIVE Understand the nature of error and how health care can learn from error to improve patient.
Accident InvestigationSlide 1 The Basics of Accident Investigation.
Quality Directions Australia Improving clinical risk management systems: Root Cause Analysis.
Accident Investigation. Accident Investigation Goals Preparing the investigation team Conducting the investigation Quiz.
Effective Accident Investigation. “Effective Accident Investigation” HSE Inspectors receive approximately 5 solid weeks of classroom training purely on.
The Scientific Method: A Way to Solve a Problem
1. 2 Ergonomics 3 THE ERGONOMIC PROCESS There are two approaches to ergonomics:  Pro-active intervention (NIOSH Model)  Reactive intervention.
2009 Your Opinion Our Future SurveyClarify and Prioritize Clarify & Prioritize Tool Root Cause The 5 Why’s Control & Employee Impact 4 Block Cost & Ease.
Hypotheses tests for means
Re-occurrence Training and Explanation 1.
Problem Description Training and Explanation 1.
Session 5 Review A3 progress Error Proofing Visual Control Workplace organisation Standard Operating Procedures.
1 Team Skill 1 - Analyzing the Problem Continued and Product Features and Challenges Sriram Mohan.
Accident Analysis.
Root Cause Analysis Analyze Kaizen Facilitation. Objectives Learn and be able to apply a fishbone diagram Utilize “Why” analysis technique to uncover.
BES-t Practices Training Phase 3 Counseling – Behavior Modification.
Non-Conformities: The Weakest Link TDI-Brooks International Sep 2014.
1 Kevin O’Connor Airworthiness Surveyor Civil and Military Design, Production & Continuing Airworthiness Root Cause Analysis Project…
Toolbox Meetings What is a toolbox meeting? An informal 5 to 15 minute meeting held by supervisors used to promote safety.
Accident Investigation Root Cause Analysis Accident Investigation Root Cause Analysis.
NOE Human Error Reduction: Schering Plough (Brinny )
Supplier Corrective Action Request (SCAR) Supplier Training
3 Legged “5 Why” Root Cause Analysis
Mistake Proofing Control Kaizen Facilitation.
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?
Human Error Reduction – A Systems Approach.
Root Cause Analysis Roger Brauninger
ROOT CAUSE ANALYSIS RCA
How to Implement an IG Manufacturing Quality Procedure System
Root Cause Analysis Course
Practicum: Root Cause Analysis
PLEASE NOTE: freeleansite
Root Cause Failure Analysis (RCFA) آنالیز ریشه ای خرابی ها
Director, Quality and Accreditation
CAUSE ANALYSIS CA
Root Cause Analysis for Effective Incident Investigation
Accident Reporting and Investigation. Presented by H&S Officer name
Fishbone Diagram Tool Management Is the machine calibrated?
5 Why’s Overview.
Introduction to ISO & The Quality Process.
Quick Response Quality Control QRQC
When should root cause analysis be performed?
Quality Assurance in Clinical Trials
CAPA, Root Cause Analysis, and Risk Management
Supplier Corrective ACTION RESPONSE REVIEW TRAINING
Presentation transcript:

Root Cause Analysis Training and Explanation 1

Purpose of EasyTools There are lots of Quality tools around that can help improving many situations of the daily quality life. The problem with many tools is that you need training and experience to use them effectively. EasyTools is a collection of easy to use and mostly self explaining tools that everybody can use. No need for weeks of training or years of experience. 2 Just use it!

Tools for Root Cause Analysis The root cause analysis is the central method when solving a problem. It can be done by different methods using different tools. Here we discuss an easy to use method using - the 5 why - the fishbone diagram - root cause verification 3

Team work Never do a root cause analysis alone. Nothing against your intelligence and your experience; but you don’t know enough! People of your team will tell you details of the problem you can’t imagine. Put the team together So you need to select the right people for your team. There is no general rule which departments shall be involved. Just think who knows most about the product and the process where the problem occurred. Just as an example assume a welding problem: maybe the welder himself, a welder of another shift, the welding expert, a welding maintenance guy, and maybe a product engineer could be part of your team. 4

The 5 why The 5 why tool 5 why is a tool where you ask “why did that happen” and you get a cause for it. Now you ask for this cause “why did that happen” and you get a cause for the cause. Then you ask again “why did that happen” and so on. Why to ask 5 times? Why not 4 times or 6 times? Some people found out that with 5 whys you dig deep enough. For me it is simple a synonym for “Dig as deep as you can, until there is no sensible answer to your why question.” Is 5 why enough for a root cause analysis? No, it is not! The root causes are like the roots of a tree: from the trunk it goes maybe into 4 roots; each root goes into another 5 roots etc. On the 5th level you may have thousands of roots. So we need to combine the 5 why with a second tool. 5

The fishbone diagram (Ishikawa diagram) The fishbone diagram helps to find causes by putting them into categories: Man, Machine, Measurement, Material, Method, Environment. Some people replace Environment by “Mother Nature” just to make it begin with another M. I think this is stupid because of the completely different meanings of the terms. 6 ManMachineMeasurement MaterialMethodEnvironment Problem

Man 7 Here we check if the problem could have been caused by people related issues such as Lack of training or education Poor employee involvement Previously identified issues which were not eliminated Bad or missing supervision You may find other sub-categories – make your own list!

Machine 8 Here we check if the problem could have been caused by machine or equipment related issues such as Incorrect tool setting Poor maintenance or design Poor equipment or tool placement Defective equipment or tool You may find other sub-categories – make your own list!

Measurement 9 Here we check if the problem could have been caused by measurement related issues such as Poor process capability Bad or missing gages Poka Yokes switched off You may find other sub-categories – make your own list!

Material 10 Material Here we check if the problem could have been caused by material related issues such as Defective material or supplier parts Wrong material or parts Lack of material or parts You may find other sub-categories – make your own list!

Method 11 Method Here we check if the problem could have been caused by the applied method or standard such as No or poor work instructions Work instructions are not followed Practices are not the same as written procedures Poor communication You may find other sub-categories – make your own list!

Environment 12 Environment Here we check if the problem could have been caused by the workplace environment such as Orderly workplace, 5S Bad ergonomics of work place Lights, workplace environment Physical demands of the task You may find other sub-categories – make your own list!

Combine fishbone diagram and 5 why How to combine the fishbone diagram with the 5 why Very easy! For each identified cause apply the 5 why. Example: Assume we had found a bad weld. We go for example to machine in the fishbone diagram: The robot didn’t weld correct – why? The weld tip was dirty – why? Preventive maintenance was not done as planned – Why? The maintenance guy had to do some other emergency work - # Attention: we are not at the end! We can now follow different trees: Maintenance: why was the preventive maintenance not done after the emergency work was completed? – etc. Robot: why did the control unit not indicate a welding problem? – etc. Etc. This example is far away from being completed. We have to consider all other trees of the fishbone diagram! 13

Possible root causes, probable root causes, true root causes What is a possible root cause? When you have asked your why’s you may come to a cause that could be a root cause. But at the moment you don’t know. So you identify this as a possible root cause. Don’t start to say “I don’t believe that this is a root cause – we remove it from the list”. Your opinion is not verified – so you must not remove it from the list until the verification is done. What is a probable root cause? All possible root causes that need further investigations are named probable root causes. What is a true root cause? The investigation proofs whether the probable root cause is a true root cause or not a root cause. 14

Root cause verification - list We use a simple Excel sheet to document the root cause verification. No.A number to identify a possible root cause Possible root causethe possible root cause as written statement LocationOptional; if the problem could be caused by a supplier, indicate it here Root cause Y N PHere you assess if the possible root cause is a true root cause (Y), not a root cause (N), or a probable root cause (P) which needs further investigation Reasonthe reason for your Y N P decision The next 3 columns show a mixture of verification activities and prevention activities. Date ResponsibleDate and responsibility for the action to be done Preventative measuresa) actions to verify a probable root cause (P) into a true root cause (Y) or not a root cause (N) b) Preventive actions to eliminate the true root cause Root cause Y Nindicate a true root cause (Y) or not a root cause (N) 15

Root cause verification - flow 16 Possible root cause from fishbone diagram Assessment Probable root cause (P) Investigation Not a root cause (N)True root cause (Y) Prevention Evidence

Root cause analysis (RCA) – example and template RCA Example The example shows “Management” in the fishbone diagram instead of “Measurement”. The example shows “time” in the analysis sheet instead of Date and Responsible. But it gives a good example how to proceed. RCA template 17