DOCSLIB.ORG

Root Cause Analysis Tools, Tips and Tricks

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Root Cause Analysis Tools, Tips and Tricks Root Cause Analysis Tools, Tips and Tricks Presented by: Sean Banayan Presented on: 8th June 2016 Sean Banayan • Business Improvement Manager, Etel Limited • [email protected] • +64 27 511 9212 • LinkedIn Qualifications • Master of Mechanical Engineering, Auckland University of Technology, NZ • PRINCE2 Practioner, APMG Australasia, NZ • Six Sixma Black Belt Certified, Aveta Business Institute, USA • Lean Manufacturing Operations Management, Aveta Business Institute, USA • TQM(Total Quality Management), Aveta Business Institute, USA • ISO 9001 Management Systems, Telarc, NZ And… •Have learned the Japanese thinking behind Lean and its successful application across a range of industries in Lean Japan Tour, Shinka Management, Australia Agenda •Definition •Direct Cause vs. Root Cause •Data Driven Decisions •Data Collection & Visual Control •Clarify the Problem •Quality & Data at Source •Basic Problem Solving • Practical Example •Visual Control •Problem Description •Problem Solving Steps •Identifying the Direct Cause • Fishbone (Cause & Effect Analysis) •Identifying the Root Cause (5 Why) •Sustain & Share Best Practice •Questions Definition Root Cause Analysis (RCA) is: •A method of problem solving used for identifying the root cause of faults or problems. •Is the fundamental breakdown or failure of a process which, when resolved, prevents a recurrence of the problem. •It is a systematic approach to get to the true root causes of our process problems. Direct Cause vs. Root Cause Direct Cause •It does not prevent its recurrence within certainty. • Its only as good as a Band-Aid •Usually blames someone Direct Cause vs. Root Cause Root Cause •It is a proven source of the Direct Cause •It will prevent recurrence of the Direct Cause •It does not attribute blame to anyone. It looks for failure in the system, or process. Root Cause Sample Machine that stopped because it Investigation shows that the machine overloaded The investigation proceeds further and finds overloaded and the fuse blew because it had a bearing that wasn't being that the automatic lubrication mechanism sufficiently lubricated had a pump which was not pumping sufficiently, hence the lack of lubrication. Investigation of why the shaft was worn discovers that the Pump Cover which prevents metal scrap getting into the pump has been damaged. This enabled scrap to get into the pump, and damage the shaft. Investigation of the pump shows that it has a worn shaft. Data Driven Decisions Reason for choosing the problem • Background information or KPI’s • Effect on you or your group • Links to higher level goals • Customer identified Data Collection & Visual Control Gather data and use facts • Record what is happening • Manually gather information • Grasp the situation before trying to fix it Data Collection & Visual Control Collect DATA on defects, changes, incidents and other Key Performance Indicators (KPI’s) Display the DATA as graphs to display combination of standard or target with current situation Supplier Issues Defects per month (%) for 2016 - 2017 3.0% 2.5% 2.0% 1.5% 1.0% 0.5% 0.0% Clarify the Problem Category Department Level of & Type Importance Level of Urgency Employees & Shift Level of Impact Problem Breakdown Problem Prioritisation Breakdown the initial Problem Perception to “one problem you can solve”. This should be the one which has the largest overall impact. Quality & Data at Source •Quality is built-in to each process – Never send Quality defects to next process Process 1 Process 2 Process 3 Process 4 Quality Check Data Gathering Process 1 Process 2 Process 3 Process 4 Quality Check Quality Check Quality Check Quality Check Data Gathering Data Gathering Data Gathering Data Gathering Basic Problem Solving • A problem goes into the Problem Solving funnel PROBLEM Root Cause Fix STATEMENT • Then leaves with a Root Cause Fix Basic Problem Solving Initial Problem Description – Explain the problem Fishbone Analysis 5 Why Investigation PROBLEM ROOT CAUSE FIX STATEMENT Follow Up Check Standardisation Share Best Practice Basic Problem Solving (Practical Example) Please note – This is a training simulation A problem has occurred in Fabrication department! A number of jobs have failed final quality inspection due to incorrect build We will work through this problem using some basic problem solving tools during this training presentation Visual Control (Practical Example) Quality MONTH/YEAR: Sep-15 AREA: FABRICATION DATE 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 OK NG > DATE > 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 5 4 3 Defects 2 1 KEY - Where Defects Found Final Inspection Test Bay Other Dept Own Dept No. of defects found during month Defect Category 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Incorrect Part Position Incorrect Plasma Cutting Incorrect Folding Not to Drawing Problem Description (Practical Example) We are going to use this example from our Quality Balanced Score Card in Fabrication So, what was the Problem Description….? … Jobs failing fabrication inspection due to incorrect build…(Not to Drawing) Problem Solving Steps (Practical Example) Now that we have a clear Problem Description, we are going to work through the following steps – • Identifying the Direct Cause 1 • Applying a short term immediate action (Band-Aid) 2 • Identifying the Root Cause 3 • Applying a long term Root Cause Fix 4 • Sustain & Sharing Best Practice 5 Identifying the Direct Cause First we must identify the Direct Cause and implement a short term immediate action (band aid) It usually means we have to add more cost to our process by adding activities such as more inspection etc. This is a very reactive way of working, but we need to do it until a Root Cause to the problem can be found. We can use a Data Analysis graphs to look at a lot of different breakdowns to guide us to what can possibly be directly causing the problem. Root Cause Analysis Problem Solving Describe Describe the problem Quality Defects in Fabrication Clarify Clarify the size of the problem 16 Farbrication Defects 14 0 5 10 15 Feb-15 12 Fabrication Error 10 Jan/15 CARS in Fabrication 8 Leaking Welds Dec/14 6 Oil Leak Defect Inspection in Nov/14 4 Fabrication Welding Quality 2 Oct/14 0 Operator error Sep/14 Missing ID Aug/14 Welding Pole FABRICATION ERROR BREAKDOWN "WELDED IN WRONG POSITION" BREAKDOWN Splatter mounting Base hold down Door locking 2% bracket brackets Missing ID lifting lugs brackets 5% 4% Welded 2% 5% 5% Wrong M8 set screws on Excessive Weld Parts the HV door. Splatter 11% 5% 5% Missing Welds 11% Welded in Wrong Oil Leak Position 13% 55% Internal locating Parts Missing brackets 6% 71% Fishbone (Cause & Effect Analysis) This is a good Team brainstorming event which helps to bring lots of ideas forward, regarding the Direct Cause of the Effect, in a short period of time Use your Problem Solving Template – Write down lots of ideas that could be causing the problem in the head of the fish Enter your Problem Quality Check Lack of Welder’s Neglecting to Method Training check Description in METHOD MAN No Std Method No Procedures for the head of the of Positioning Attention to Details Checking Parts fish IncorrectEFFECT Position (Problemof Internal LocatingObserved) Bracket Torches to Wrong check inside Tools tanks Measuring Tools MATERIAL MACHINE Drawing Not Clear Key Point – No Idea is a Bad Try to group your ideas into the correct categories Idea! Fishbone (Cause & Effect Analysis) Get the Team to vote on what they believe are the most likely direct causes of the problem in the head of the fish. This can be done by placing a tick on the idea PNo Std PMethodP QualityP Drawing is of Positioning P Check P P unclear Method P P METHOD P MAN P No procedure for checking parts P Incorrect P Position of Internal Locating Bracket Torches to Wrong check inside Tools tanks MATERIAL P MACHINE Measuring Tools Direct Cause Drawing Not Operators do not have Clear standard way of positioning the Internal Locating Brackets Fishbone – Direct Cause • Remember the importance of CAPTURING DATA? P Let’s enter that into our Problem Solving Template • The next thing we must do is put a short term immediate action in place to act as a band aid whilst we find the Root Cause • What could we do? Talk to the Operators? Re-train? More inspection? Manager to check that the job is correct every hour? P Update your Problem Solving Template with your short term immediate action (band aid)… Problem & Containment Action Also document the Problem Description and Short Term immediate Paction into the Problem, Cause, Countermeasure Sheet on the Board September Fabrication Re-train the operator & ask Internal Locating Bracket Q A 07 Jun quality inspector to double not in correct position check Identifying the Root Cause • So, we have our Direct Cause ‘No Standard Procedure for Positing the Internal Locating Bracket’… • …we can use a tool called 5 Why to drill further into the Direct Cause to uncover the Root Cause of the problem • It is called 5 Why, but you don’t need to ask “Why” 5 times, you can use as many or as little as you like! 5 Why Example Direct Cause of problem – No Standard Method of Positioning Part •Why No Standard Method of Positioning Part? – Because operators don’t follow instruction of the drawing •Why operators don’t follow instruction of the drawing? – Because not all drawings are up to date. •Why aren’t the drawings up to date? – The Operators never feedback to engineers for drawing updates.
Load more

Recommended publications
  • Root Cause Analysis in Context of WHO International Classification for Patient Safety
    Root cause analysis in context of WHO International Classification for Patient Safety Dr David Cousins Associate Director Safe Medication Practice and Medical Devices 1 NHS | Presentation to [XXXX Company] | [Type Date] How heath care provider organisations manage patient safety incidents Incident External organisation Healthcare Patient/Carer or agency professional Department of Health Incident report Complaint Regulators Health & Safety Request Risk/complaint Request additional manager additional Healthcare information information commissioners and purchasers Local analysis and learning Industry Feed back External report Root Cause AnalysisWhy RCA? (RCA) To identify the root causes and key learning from serious incidents and use this information to significantly reduce the likelihood of future harm to patients Objectives To establish the facts i.e. what happened (effect), to whom, when, where, how and why To establish whether failings occurred in care or treatment To look for improvements rather than to apportion blame To establish how recurrence may be reduced or eliminated To formulate recommendations and an action plan To provide a report and record of the investigation process & outcome To provide a means of sharing learning from the incident To identify routes of sharing learning from the incident Basic elements of RCA WHAT HOW it WHY it happened happened happened Human Contributory Unsafe Acts Behaviour Factors Direct Care Delivery Problems – unsafe acts or omissions by staff Service Delivery Problems – unsafe systems, procedures
    [Show full text]
  • Guidance for Performing Root Cause Analysis (RCA) with Pips
    Guidance for Performing Root Cause Analysis (RCA) with Performance Improvement Projects (PIPs) Overview: RCA is a structured facilitated team process to identify root causes of an event that resulted in an undesired outcome and develop corrective actions. The RCA process provides you with a way to identify breakdowns in processes and systems that contributed to the event and how to prevent future events. The purpose of an RCA is to find out what happened, why it happened, and determine what changes need to be made. It can be an early step in a PIP, helping to identify what needs to be changed to improve performance. Once you have identified what changes need to be made, the steps you will follow are those you would use in any type of PIP. Note there are a number of tools you can use to perform RCA, described below. Directions: Use this guide to walk through a Root Cause Analysis (RCA) to investigate events in your facility (e.g., adverse event, incident, near miss, complaint). Facilities accredited by the Joint Commission or in states with regulations governing completion of RCAs should refer to those requirements to be sure all necessary steps are followed. Below is a quick overview of the steps a PIP team might use to conduct RCA. Steps Explanation 1. Identify the event to be Events and issues can come from many sources (e.g., incident report, investigated and gather risk management referral, resident or family complaint, health preliminary information department citation). The facility should have a process for selecting events that will undergo an RCA.
    [Show full text]
  • Root Cause Analysis in Surgical Site Infections (Ssis) 1Mashood Ahmed, 2Mohd
    International Journal of Pharmaceutical Science Invention ISSN (Online): 2319 – 6718, ISSN (Print): 2319 – 670X www.ijpsi.org Volume 1 Issue 1 ‖‖ December. 2012 ‖‖ PP.11-15 Root cause analysis in surgical site infections (SSIs) 1Mashood Ahmed, 2Mohd. Shahimi Mustapha, 3 4 Mohd. Gousuddin, Ms. Sandeep kaur 1Mashood Ahmed Shah (Master of Medical Laboratory Technology, Lecturer, Faculty of Pharmacy, Lincoln University College, Malaysia) 2Prof.Dr.Mohd. Shahimi Mustapha,(Dean, Faculty of Pharmacy, Lincoln University College, Malaysia) 3Mohd.Gousuddin, Master of Pharmacy (Lecturer, Faculty of Pharmacy, Lincoln University College, Malaysia) 4Sandeep kaur,(Student of Infection Prevention and control, Wairiki Institute of Technology, School of Nursing and Health Studies, Rotorua: NZ ) ABSTRACT: Surgical site infections (SSIs) are wound infections that usually occur within 30 days after invasive procedures. The development of infections at surgical incision site leads to extend of infection to adjacent tissues and structures.Wound infections are the most common infections in surgical patients, about 38% of all surgical patients will develop a SSI.The studies show that among post-surgical procedures, there is an increased risk of acquiring a nosocomial infection.Root cause analysis is a method used to investigate and analyze a serious event to identify causes and contributing factors, and to recommend actions to prevent a recurrence including clinical as well as administrative review. It is particularly useful for improving patient safety systems. The risk management process is done for any given scenario in three steps: perioperative condition, during operation and post-operative condition. Based upon the extensive searches in several biomedical science journals and web-based reports, we discussed the updated facts and phenomena related to the surgical site infections (SSIs) with emphasis on the root causes and various preventive measures of surgical site infections in this review.
    [Show full text]
  • Root Cause Analysis: the Essential Ingredient Las Vegas IIA Chapter February 22, 2018 Agenda • Overview
    Root Cause Analysis: The Essential Ingredient Las Vegas IIA Chapter February 22, 2018 Agenda • Overview . Concept . Guidance . Required Skills . Level of Effort . RCA Process . Benefits . Considerations • Planning . Information Gathering • Fieldwork . RCA Tools and Techniques • Reporting . 5 C’s Screen 2 of 65 OVERVIEW Root Cause Analysis (RCA) A root cause is the most reasonably identified basic causal factor or factors, which, when corrected or removed, will prevent (or significantly reduce) the recurrence of a situation, such as an error in performing a procedure. It is also the earliest point where you can take action that will reduce the chance of the incident happening. RCA is an objective, structured approach employed to identify the most likely underlying causes of a problem or undesired events within an organization. Screen 4 of 65 IPPF Standards, Implementation Guide, and Additional Guidance IIA guidance includes: • Standard 2320 – Analysis and Evaluation • Implementation Guide: Standard 2320 – Analysis and Evaluation Additional guidance includes: • PCAOB Initiatives to Improve Audit Quality – Root Cause Analysis, Audit Quality Indicators, and Quality Control Standards Screen 5 of 65 Required Auditor Skills for RCA Collaboration Critical Thinking Creative Problem Solving Communication Business Acumen Screen 6 of 65 Level of Effort The resources spent on RCA should be commensurate with the impact of the issue or potential future issues and risks. Screen 7 of 65 Steps for Performing RCA 04 02 Formulate and implement Identify the corrective actions contributing to eliminate the factors. root cause(s). 01 03 Define the Identify the root problem. cause(s). Screen 8 of 65 Steps for Performing RCA Risk Assessment Root Cause Analysis 1.
    [Show full text]
  • Root Cause Analysis in Health Care Tools and Techniques
    Root Cause Analysis in Health Care Tools and Techniques SIXTH EDITION Includes Flash Drive! Senior Editor: Laura Hible Project Manager: Lisa King Associate Director, Publications: Helen M. Fry, MA Associate Director, Production: Johanna Harris Executive Director, Global Publishing: Catherine Chopp Hinckley, MA, PhD Joint Commission/JCR Reviewers for the sixth edition: Dawn Allbee; Anne Marie Benedicto; Kathy Brooks; Lisa Buczkowski; Gerard Castro; Patty Chappell; Adam Fonseca; Brian Patterson; Jessica Gacki-Smith Joint Commission Resources Mission The mission of Joint Commission Resources (JCR) is to continuously improve the safety and quality of health care in the United States and in the international community through the provision of education, publications, consultation, and evaluation services. Joint Commission Resources educational programs and publications support, but are separate from, the accreditation activities of The Joint Commission. Attendees at Joint Commission Resources educational programs and purchasers of Joint Commission Resources publications receive no special consideration or treatment in, or confidential information about, the accreditation process. The inclusion of an organization name, product, or service in a Joint Commission Resources publication should not be construed as an endorsement of such organization, product, or service, nor is failure to include an organization name, product, or service to be construed as disapproval. This publication is designed to provide accurate and authoritative information in regard to the subject matter covered. Every attempt has been made to ensure accuracy at the time of publication; however, please note that laws, regulations, and standards are subject to change. Please also note that some of the examples in this publication are specific to the laws and regulations of the locality of the facility.
    [Show full text]
  • An Empirical Approach to Improve the Quality and Dependability of Critical Systems Engineering
    Nuno Pedro de Jesus Silva An Empirical Approach to Improve the Quality and Dependability of Critical Systems Engineering PhD Thesis in Doctoral Program in Information Science and Technology, supervised by Professor Marco Vieira and presented to the Department of Informatics Engineering of the Faculty of Sciences and Technology of the University of Coimbra August 2017 An Empirical Approach to Improve the Quality and Dependability of Critical Systems Engineering Nuno Pedro de Jesus Silva Thesis submitted to the University of Coimbra in partial fulfillment of the requirements for the degree of Doctor of Philosophy August 2017 Department of Informatics Engineering Faculty of Sciences and Technology University of Coimbra This research has been developed as part of the requirements of the Doctoral Program in Information Science and Technology of the Faculty of Sciences and Technology of the University of Coimbra. This work is within the Dependable Systems specialization domain and was carried out in the Software and Systems Engineering Group of the Center for Informatics and Systems of the University of Coimbra (CISUC). This work was supported financially by the Top-Knowledge program of CRITICAL Software, S.A. and carried out partially in the frame of the European Marie Curie Project FP7-2012-324334-CECRIS (Certification of CRItical Systems). This work has been supervised by Professor Marco Vieira, Full Professor (Professor Catedrático), Department of Informatics Engineering, Faculty of Sciences and Technology, University of Coimbra. iii iv “Safety is not an option!” James H. Miller Miller, James H. "2009 CEOs Who "Get It"" Interview. Safety and Health Magazine.” February 1, 2009. Accessed October 13, 2016.
    [Show full text]
  • Statistical Process Control, Part 5: Cause-And-Effect Diagrams
    Performance Excellence in the Wood Products Industry Statistical Process Control Part 5: Cause-and-Effect Diagrams EM 8984 • August 2009 Scott Leavengood and James E. Reeb ur focus for the first four publications in this series has been on introducing you to Statistical Process Control (SPC)—what it is, how and why it works, and then Odiscussing some hands-on tools for determining where to focus initial efforts to use SPC in your company. Experience has shown that SPC is most effective when focused on a few key areas as opposed to the shotgun approach of measuring anything and every- thing. With that in mind, we presented check sheets and Pareto charts (Part 3) in the context of project selection. These tools help reveal the most frequent and costly quality problems. Flowcharts (Part 4) help to build consensus on the actual steps involved in a process, which in turn helps define precisely where quality problems might be occurring and what quality characteristics to monitor to help solve the problems. In Part 5, we now turn our attention to cause-and-effect diagrams (CE diagrams). CE diagrams are designed to help quality improvement teams identify the root causes of problems. In Part 6, we will continue this concept of root cause analysis with a brief intro- duction to a more advanced set of statistical tools: Design of Experiments. It is important, however, that we do not lose sight of our primary goal: improving quality and in so doing, improving customer satisfaction and the profitability of the company. We’ve identified the problem; now how can we solve it? In previous publications in this series, we have identified the overarching quality prob- lem we need to focus on and developed a flowchart identifying the specific steps in the process where problems may occur.
    [Show full text]
  • Mistakeproofing the Design of Construction Processes Using Inventive Problem Solving (TRIZ)
    www.cpwr.com • www.elcosh.org Mistakeproofing The Design of Construction Processes Using Inventive Problem Solving (TRIZ) Iris D. Tommelein Sevilay Demirkesen University of California, Berkeley February 2018 8484 Georgia Avenue Suite 1000 Silver Spring, MD 20910 phone: 301.578.8500 fax: 301.578.8572 ©2018, CPWR-The Center for Construction Research and Training. All rights reserved. CPWR is the research and training arm of NABTU. Production of this document was supported by cooperative agreement OH 009762 from the National Institute for Occupational Safety and Health (NIOSH). The contents are solely the responsibility of the authors and do not necessarily represent the official views of NIOSH. MISTAKEPROOFING THE DESIGN OF CONSTRUCTION PROCESSES USING INVENTIVE PROBLEM SOLVING (TRIZ) Iris D. Tommelein and Sevilay Demirkesen University of California, Berkeley February 2018 CPWR Small Study Final Report 8484 Georgia Avenue, Suite 1000 Silver Spring, MD 20910 www. cpwr.com • www.elcosh.org TEL: 301.578.8500 © 2018, CPWR – The Center for Construction Research and Training. CPWR, the research and training arm of the Building and Construction Trades Department, AFL-CIO, is uniquely situated to serve construction workers, contractors, practitioners, and the scientific community. This report was prepared by the authors noted. Funding for this research study was made possible by a cooperative agreement (U60 OH009762, CFDA #93.262) with the National Institute for Occupational Safety and Health (NIOSH). The contents are solely the responsibility of the authors and do not necessarily represent the official views of NIOSH or CPWR. i ABOUT THE PROJECT PRODUCTION SYSTEMS LABORATORY (P2SL) AT UC BERKELEY The Project Production Systems Laboratory (P2SL) at UC Berkeley is a research institute dedicated to developing and deploying knowledge and tools for project management.
    [Show full text]
  • Extending the A3: a Study of Kaizen and Problem Solving
    VOLUME 30, NUMBER 3 July through September 2014 Abstract/Article 2 Extending the A3: A Study of References 14 Kaizen and Problem Solving Authors: Dr. Eric O. Olsen Keywords: Dr. Darren Kraker Lean Manufacturing / Six Sigma, Ms. Jessie Wilkie Management, Teaching Methods, Teamwork, Visual Communications, Information Technology, Quality Control PEER-REFEREED PAPER n PEDAGOGICAL PAPERS The Journal of Technology, Management, and Applied Engineering© is an official publication of the Association of Technology, Managment, and Applied Engineering, Copyright 2014 ATMAE 275 N. YORK ST Ste 401 ELMHURST, IL 60126 www.atmae.org VOLUME 30, NUMBER 2 The Journal of Technology, Management, and Applied Engineering JULY– SEPTEMBER 2014 Dr. Eric Olsen is Professor of Indus- Extending the A3: trial and Packaging Technology at Cal Poly in San Luis Obispo, California. A Study of Kaizen and Problem Solving Dr. Olsen teaches Dr. Eric O. Olsen, Mr. Darren Kraker, and Ms. Jessie Wilkie undergraduate and master’s courses in lean thinking, six sigma, and operations management. Dr. Olsen had over 20 years of industry experience in engineer- ing and manufacturing management ABSTRACT before getting his PhD at The Ohio State A case study of a continuous improvement, or kaizen, event is used to demonstrate how allowing “extended” University. His dissertation compared responses to the respective sections of lean A3 problem solving format can enhance student, teacher, and the financial performance of lean versus researcher understanding of problem solving. Extended responses provide background and reasoning that non-lean companies. Dr. Olsen continues are not readily provided by the frugal statements and graphics typically provided in A3s.
    [Show full text]
  • Application of Root Cause Analysis in Improvement of Product Quality and Productivity
    doi:10.3926/jiem.2008.v1n2.p16-53 ©© JIEM, 2008 – 01(02):16-53 - ISSN: 2013-0953 Application of root cause analysis in improvement of product quality and productivity Dalgobind Mahto; Anjani Kumar National Institute of Technology (INDIA) [email protected]; [email protected] Received July 2008 Accepted December 2008 Abstract: Root-cause identification for quality and productivity related problems are key issues for manufacturing processes. It has been a very challenging engineering problem particularly in a multistage manufacturing, where maximum number of processes and activities are performed. However, it may also be implemented with ease in each and every individual set up and activities in any manufacturing process. In this paper, root-cause identification methodology has been adopted to eliminate the dimensional defects in cutting operation in CNC oxy flame cutting machine and a rejection has been reduced from 11.87% to 1.92% on an average. A detailed experimental study has illustrated the effectiveness of the proposed methodology. Keywords: root cause analysis, cause and effect diagram, interrelationship diagram and current reality tree 1. Introduction In Root Cause Analysis (RCA) is the process of identifying causal factors using a structured approach with techniques designed to provide a focus for identifying and resolving problems. Tools that assist groups or individuals in identifying the root causes of problems are known as root cause analysis tools. Every equipment failure happens for a number of reasons. There is a definite progression of actions and consequences that lead to a failure. Root Cause Analysis is a step-by-step method Application of root cause analysis in improvement of product quality and productivity 16 D.
    [Show full text]
  • Root Cause Analysis and Corrective Action
    The following slides are not contractual in nature and are for information purposes only as of June 2015. 1 ©2015, Lockheed Martin Corporation. All Rights Reserved. Corrective Action Root Cause Analysis and Corrective Action 2 ©2015, Lockheed Martin Corporation. All Rights Reserved. Overview Webinar 6: Root Cause Analysis and Corrective Action • What is Root Cause Analysis (RCA)? • Why is RCA important? • When is RCA required? • Overview of the Corrective Action Process • Root Cause Analysis Tools: The 5-Whys Ishikawa Cause & Effect (Fishbone) Diagrams Cause Mapping Failure Modes & Effects Analysis Design of Experiments 3 What is Root Cause Analysis (RCA)? Root Cause Analysis (RCA): The process of identifying all the causes (root causes and contributing causes) that have or may have generated an undesirable condition, situation, nonconformity, or failure. » IAQG – Root Cause Analysis and Problem Solving April 2014. 4 Root Cause Analysis (RCA) PROBLEM = Weed (obvious) CAUSE = ROOT Cause (not obvious) Cause 5 Why Root Cause Analysis (RCA)? • Helps prevent problems from repeating or occurring. • Focus on Continuous Improvement throughout the Enterprise. • Drives Breakthrough Performance. • Focus on improving processes that actually effect organization performance metrics. 6 When is RCA required? • Undesirable condition, defect, or failure is detected • Safety • Product strength, performance, reliability • High impact on Operations • Repetitive Problems • Customer Request • Significant Quality Management System (QMS) issues » IAQG – Root Cause Analysis and Problem Solving, April 2014 7 The Corrective Action (CA) Process Identify Problem • Objective: Identify the cause(s) of problems and initiate actions to prevent recurrence. Define Problem • Extent of corrective actions shall be proportional to the effects of the related problems.
    [Show full text]
  • The Mapping Tree Hierarchical Tool Selection and Use
    The Mapping Tree Hierarchical Tool Selection and Use 1 Session Objectives . Discuss the hierarchical linkage and transparency of mapping using this methodology. Understand how and when to apply each mapping tool and its application in the Lean tool set. Understand how mapping helps to reveal Value and Non-Value Added actions as well as Constraints in the process. 2 Why Do We Care? “Hierarchical Mapping“is necessary because: • Hierarchical mapping is critical in maintaining the organization’s strategic plan during a Lean deployment. • Hierarchical mapping is critical in achieving greater “Value to the Customer”, in revealing of wastes and improving processes. • Until we know all of the “players in the process”, we cannot begin to understand the process, its “Value to the Customer” and the impact on the strategic plan. 3 Keys To Success . Always use your team of experts for mapping exercises. Mapping in “silos” is a “design for failure”. Always follow a hierarchical procedure for mapping to root cause. Always begin at the high level first, then capture detailed maps as needed. 4 Why use the Mapping Tree methodology ? • Before any improvement exercise is undertaken, a clear definition of “what to work on” must be developed. • Without utilizing a mapping hierarchy, any attempt to attack a process for improvement effort would be just a “shot in the dark”. • We need a methodology that will link the lowest level effort to the high level organizational objectives, and do it transparently. • The hierarchical approach of the Mapping Tree helps to ensure that the lowest task efforts remain focused on the Customer requirements and support the Strategic Objectives.
    [Show full text]