5 Why's
5 Why's
5 Why's
11/17/2009
11/17/2009
Agenda
When
to Use 5 Why 3 Legged 5 Why Analysis 5 Why Examples Resources and References 5 Why and Customer Problem Solving Formats Where to Find the Blank Forms
11/17/2009
Issues Required for all Covisint Problem Cases May be requested for informal complaints May be requested for warranty issues Internal Issues (optional) Quality System Audit Non-conformances First Time Quality Internal Quality Issue
11/17/2009
Why Analysis can be used with various problem solving formats Internal Problem Solving GM Drill Deep Ford 8 D (Discipline) Chrysler 8 Step
5 Why, when combined with other problem solving methods, is a very effective tool
5
11/17/2009
Corrective Actions
A.
Date
Why?
c i f i ec p S
Why?
W hy d id w
Why?
Root Causes
Use this path to investigate why the problem was not detected
n o i t c e t De
Why?
W hy d
e ha ve t
he p r
obl e m?
B.
A
C.
Why?
the c usto m
Lessons Learned
C
11/17/2009
Problem Definition
c i f i ec p S
n o i t c e t De ic m e t s Sy
5 Why Analysis
General
Guidelines A cross-functional team should be used to problem solve Dont jump to conclusions or assume the answer is obvious Be absolutely objective
11/17/2009
5 Why Analysis
General
Guidelines
If you are using words like because or due to in any box, you will likely need to move to the next Why box Root cause can be turned on and off
Will addressing/correcting the cause prevent recurrence? If not what is the next level of cause?
If you dont ask enough Whys, you may end up with a symptom and not root cause. Corrective action for a symptom is not effective in eliminating the cause
Corrective action for a symptom is usually detective Corrective action for a root cause can be preventive
Problem Definition
c i f i ec p S
n o i t c e t De ic m e t s Sy
10
11/17/2009
Problem Definition
Define
the problem Problem statement clear and accurate Problem defined as the customer sees it Do not add causes into the problem statement
Examples:
GOOD: Customer received a part with a broken mounting pad NOT: Customer received a part that was broken due to improper machining GOOD: Customer received a part that was leaking NOT: Customer received a part that was leaking due to a missing seal
11
11/17/2009
Problem Definition
c i f i ec p S
n o i t c e t De ic m e t s Sy
12
11/17/2009
Specific Problem
Specific Problem Why did we have the specific non-conformance? How was the non-conformance created?
Tooling wear/breaking Set-up incorrect Processing parameters incorrect Part design issue
Specific Problem
Parts damaged by shipping dropped or stacked incorrectly Operator error poorly trained or did not use proper tools Changeover occurred wrong parts used Operator error performed job in wrong sequence Processing parameters changed Excessive tool wear/breakage Machine fault machine stopped mid-cycle
14
11/17/2009
Specific Problem
Do we stop here?
15
11/17/2009
Specific Problem
Operator did not follow instructions Do standard work instructions exist? Create a standard instruction
Train operator
16
11/17/2009
Specific Problem
Specific Problem
Column would not lock in tilt position 2 and 4 Tilt shoe responsible for positions 2 and 4 would not engage pin Shifter assembly screw lodged below shoe preventing full travel Screw fell off gun while pallet was indexing Magnet on the screw bit was weak Exceeded the bits workable life
THEREFORE
WHY??
17
11/17/2009
Specific Problem
Specific Problem
Loss of torque at rack inner tie rod joint Undersized chamfer (thread length on rack) Part shifted axially during drill sequence Insufficient radial clamping load. Machining forces overcame clamp force Air supply not maintained Various leaks, high demand at full plant capacity, bleeder hole plugs caused pressure drop
THEREFORE
WHY??
18
11/17/2009
Problem Definition
c i f i ec p S
n o i t c e t De ic m e t s Sy
19
11/17/2009
Detection
Detection: Why did the problem reach the customer? Why did we not detect the problem? How did the controls fail?
Detection
Detection
No detection process in place cannot be detected in our plant Defect occurs during shipping Detection method failed sample size and frequency inadequate Error proofing not working or bypassed Gage not calibrated
21
11/17/2009
Detection
Detection
Column would not lock in tilt position 2 and 4 On-line test for tilt function is not designed to catch this type of defect
THEREFORE
WHY??
Process flow designed in this manner would not detect shifter assy screw lodged below tilt shoe
22
11/17/2009
Detection
Detection
Loss of torque at rack inner tie rod joint Undersized chamfer/thread length undetected
THEREFORE
WHY??
Inspection frequency is inadequate. Chamfer gage is not robust Process CPK results did not reflect special causes of variation affecting chamfer.
23
11/17/2009
Problem Definition
c i f i ec p S
n o i t c e t De ic m e t s Sy
24
11/17/2009
Systemic
Systemic
Why did our system allow it to occur? What was the breakdown or weakness? Why did the possibility exist for this to occur? Root Cause typically related to management system issues or quality system failures
Rework/repair not considered in process design Lack of effective Preventive Maintenance system Ineffective Advanced Product Quality Planning (FMEA, Control Plans)
25
11/17/2009
Systemic Issue
Systemic
Helpful hint: The root cause of the specific problem leg is typically a good place to start the systemic leg. Root Cause Examples
Failure mode not on PFMEA believed failure mode had zero potential for occurrence New process not properly evaluated Process changed creating a new failure cause PFMEAs generic- not specific to the process Severity of defect not understood by team Occurrence ranking based on external failures only, not actual defects
26
11/17/2009
Systemic
Column would not lock in tilt position 2 and 4
Detection for tilt function done prior to installation of shifter assembly PFMEA did not identify a dropped part interfering with tilt function
THEREFORE
WHY??
27
11/17/2009
Systemic
Loss of torque at rack inner tie rod joint
THEREFORE
WHY??
Dimension was not considered an important characteristic additional controls not required
Insufficient evaluation of machining process and related severity levels during APQP process
28
11/17/2009
Corrective Actions
Corrective
Actions Corrective action for each root cause Corrective actions must be feasible If Customer approval required for corrective action, this must be addressed in the 5 why timing Corrective actions address processes the supplier owns Corrective actions include documentation updates and training as appropriate
29
11/17/2009
Specific Problem
Corrective Action:
Loss of torque at rack inner tie rod joint Undersized chamfer (thread length on rack) Part shifted axially during drill sequence Insufficient radial clamping load. Machining forces overcame clamp force Air supply not maintained
WHY??
Reset alarm limits to sound if <90 PSI. Smith 10/12/10 Disable machine if <90 PSI. Jones 9/28/10 Dropped feed on drill cycle to .0058 from .008. Davis 10/10/10 Clean collets on Kennefec @ PM frequency Smith 10/12/10 Added dedicated accumulator (air) for system or compressor for each Kennefec Smith 10/12/10 Verify system pressure at machines at beginning , middle, and end of shift Smith 10/12/10
Various leaks, high demand at full plant capacity, bleeder hole plugs caused pressure drop
30
11/17/2009
Detection
Corrective Action:
Loss of torque at rack inner tie rod joint Undersized chamfer/thread length undetected Inspection frequency is inadequate. Chamfer gage is not robust Process CPK results did not reflect special causes of variation affecting chamfer.
Implement 100% sort for chamfer length and thread depth. Smith 9/26/10 Create & maintain inspection sheet log to validate Davis 8/22/10 Redesign chamfer gage to make more effective Jones 11/30/10 Increase inspection frequency at machine from 2X per shift to 2X per hour Johnson 10/14/10 Review audit sheets to record data from both ends on an hourly basis Davis 10/4/10 Conduct machine capability studies on thread depth Jones 9/22/10 Perform capability studies on chamfer diameters
WHY??
31
10/14/10 Repair/replace auto thread checking unit to include thread length. 10/18/10
11/17/2009
Systemic
Loss of torque at rack inner tie rod joint Ineffective control plan related to process parameter control (chamfer) Low severity for chamfer control Dimension was not considered an important characteristic additional controls not required Insufficient evaluation of machining process and related severity levels during APQP process Corrective Action: Design record, FMEA, and Control Plan to be reviewed/upgraded by Quality, Manufacturing Engineering Update control plan to reflect 100% inspection of feature PM machine controls all utility/power/pressure Implement layered audit schedule by Management for robustness/compliance to standardized work Lessons Learned: PFMEA severity should focus on affect to subsequent internal process (immediate customer) as well as final customer Measurement system and gage design standard should be robust and supported by R & R studies Evaluate the affect of utility interruptions to all machine processed (air/electric/gas)
WHY??
Steering Solutions Services Corp.
32
11/17/2009
General Guidelines: Dont jump to conclusions..dont assume the answer is obvious Be absolutely objective A cross-functional team should complete the analysis Step 1: Problem Statement State the problem as the Customer sees itdo not add cause to the problem statement
33
11/17/2009
There should be no leaps in logic Ask Why as many times as needed. This may be fewer than 5 or more than 5 Whys There should be a cause and effect path from beginning to end of each path. There should be data/evidence to prove the cause and effect relationship The path should make sense when read in reverse from cause to cause this is the therefore test (e.g. did this, therefore this happened) The specific problem path should tie back to issues such as design, operations, supplier issues, etc. The detection path should tieback to issues such as control plans, error-proofing, etc. The systemic path should tie back to management systems/issues such as change management, preventive maintenance, etc
34
11/17/2009
corrective action for each root cause. If not, does it make sense that the corrective action applies to more than one root cause? The corrective action must be feasible If corrective actions require Customer approval, does timing include this? be communicated as Lessons
Learned
Document completion of in-plant Look Across (communication of Lessons Learned) and global Look Across
35
11/17/2009
a 5 Why using the Critique Sheet and what you have learned
Note: These are actual responses as sent to our Customers! Has probable root cause been determined for:
Do corrective actions address root cause? Have Lessons Learned/Look Across been noted? If any above answers are no, what recommendations would you make to the team working on the 3 Leg 5 Why?
36
11/17/2009
Operator did not return parts to the proper process step after rework
WHY?
No standard rework procedures exist This is still a systemic failure & needs to be addressed, but its not the root cause.
37
11/17/2009
What caused the sensor to get damaged? Sensor to detect thread presence was not working
WHY?
This is still a systemic failure & needs to be addressed, but its not the root cause of the lack of detection.
38
11/17/2009
39
11/17/2009
40
11/17/2009
Click APQP and Current Production Cycle Forms link to open the folder containing the 5-why form
41
11/17/2009
Corrective
actions with date and owner Document lessons learned and look across
Steering Solutions Services Corp.
42
11/17/2009