5-Why methodology.pptVIP

5-Why Methodology Why 5-Why? Motorola customers currently require 8D analysis for product returns Delphi Delco requires 5-Why analysis on all product returns that are assigned a Covisint number Both of these methodologies are industry-accepted techniques for root cause investigation 5-Why builds on the 8D analysis findings 8D analysis determines the root cause at that particular incident level 5-Why analysis drives to the root cause at the process and system level Project Plan To integrate Delphi’s 5-Why problem solving methodology into Motorola’s customer returns process Today, 8D data is converted to 5-Why data and then manually transcribed into Problem Solver “Interim” Go-Live 18 May 2003 To implement the 5-Why problem solving methodology, and to enhance the Customer Quality Incident CQI Tracking system by developing a module for the management of the Delphi 5-Why process and data CQI 5-Why data will still have to be manually transcribed into Problem Solver “Automated” Go-Live tentative: 15 October 2003 To integrate the CQI 5-Why module with the Problem Solver application residing in the Covisint e-business portal CQI will interface directly with Problem Solver, eliminating the need for manual data transcription High-Level Process Ideal Problem Solving, cont. Before conducting a 5-Why analysis to determine the root cause, it is necessary to evaluate and eliminate other potential causes A recommended method for evaluating potential causes is Fault Tree Analysis Fault Tree Analysis: Captures all potential causes Provides the input to 5-Why for root cause Major Changes Related to 5-Why Methodology 5-Why drives to three root causes instead of one: Non-conformance Detection Systemic Incorporates more formalized Lessons Learned element Screen changes to CQI tool to support the new process Return Types Affected Return Type 5-Why Owner Type PNCA CQE Interim PNVO FQE Interim NNIO FQE Interim NNCA CQE Interim PNIO N/A N/A IXXX N/A N/A XCXX N/A N/A 5-Why Problem-