8 Dpro
8 Dpro
Formel D
Zentrales Qualitätsmanagement Technik
11 Intern | C/QMT | 08.03.2005 | © Alle Rechte bei Robert Bosch GmbH, auch für den Fall von Schutzrechtsanmeldungen. Jede Verfügungsbefugnis, wie Kopier-
und Weitergaberecht, bei uns.
Problem Solving Process
Introduction
To lead Bosch to world class quality and to obtain customer satisfaction it is essential to use a highly
improved Problem Solving Process. Only then we will be able to improve and sustain our component and
process quality.
We will achieve long term business only by best in class quality of our products and services. Day by day
consequent improvement of quality is the responsibility of everybody personally.
To become the benchmark in quality it is absolutely crucial to apply the new Problem Solving Process
consistently incident by incident. This will create the necessary in depth root cause analysis and ultimately
will eliminate the problems.
Ausgabe: V3.0 (10.10.2005)
The new Problem Solving Process integrates the lessons learned process and will force us to share detailed
information about problems with our colleagues. We as an organization will be able to prevent reoccurrence
of a mistake in other divisions, plants or production lines.
To teach you the specific methods of the Robert Bosch Problem Solving
Process in order to improve and sustain the part, component and
process quality.
8D
Good for non-technical and technical Problems
Supports 8D
Non- technical
Root Cause Investigation during Mass Production
•Customer not satisfied
• Late delivery Supports 8D
during Design-Phases or Re-Engineering
•Innovation Checklist
• 7 Quality Tools •Multi Vary Charts
•Checklist Idea Comparison
•Concept Comparison
•Local Distribution
• 3X5XWhy •Pair Comparison
•Pair wise Comparison
•Morphological Box
•Variable Comparison •Tauguschi
•Component Comparison •Etc., etc., etc.
•Complete Fractional Comparison
Ausgabe: V3.0 (10.10.2005)
Technical
• Design Faulty
• Product non-conformance
Please consider here the Robert Bosch Brochure: Elementary Quality Assurance Tools
(EWQe)
Activity 2: Answers
8D Context
3x 5x Why
7Q Tools Transparency
QAM
Ausgabe: V3.0 (10.10.2005)
Lessons
DRBFM
learned
Focus on
8D - Process Who & How
Problem Solving What
3x 5x Why Why
7Q-Tools Monitors and Aids
Lessons Learned Teach
Overview of
Design Review Based on Failure Mode (DRBFM)
Ausgabe: V3.0 (10.10.2005)
Root
Internal or
Causes Prevent
External Describe Short term
Problem Found Reoccur- Zero
Non- the corrective
Solving rence Defects
Conformities Problem action
Corrective
Ausgabe: V3.0 (10.10.2005)
Actions
PQC a PQC a
Plant 1 Plant 1
PQC a PQC a
Plant n Plant n
8D - Process
8D Process
Root
Causes Prevent
Describe Short term
Ausgabe: V3.0 (10.10.2005)
2 Within 2 days*:
Initial results of defect analysis and containment actions to
prevent customers from further defects must be reported
(written statement) to him (head data, D1, D2, D3 converted).
Within 14 days*:
Proof of elimination of the defect must be presented in form
of an 8D report. The results and 8D report have to be
submitted to the customer (complete 8D report is filled out).
*: If any of these deadlines can’t be met, this must be
Ausgabe: V3.0 (10.10.2005)
14
QSP0508 Eng
Containment
Prevent customer to receive non-conforming parts or products.
8D Process
Ausgabe: V3.0 (10.10.2005)
Root
Causes Prevent
Describe Short term
Problem Found Reoccur-
the corrective
Solving rence
Problem action
Corrective
Actions
3x 5x Why Technique
Root
Causes Prevent
Describe Short term
Ausgabe: V3.0 (10.10.2005)
Root
Causes Prevent
Describe Short term
Problem Found Reoccur- Zero
the corrective
Solving rence Defects
Ausgabe: V3.0 (10.10.2005)
Problem action
Corrective
Actions
QAM
Root
Causes Prevent
Describe Short term
Problem Found Reoccur- Zero
the corrective
Solving rence Defects
Ausgabe: V3.0 (10.10.2005)
Problem action
Corrective
Actions
Lessons Learned
Approach to prevent known quality problems to be repeated
Creates the basis for best practice QAM
8D Process
Root
Causes Prevent
Describe Short term
Problem Found Reoccur- Zero
the corrective
Solving rence Defects
Problem action
Ausgabe: V3.0 (10.10.2005)
Corrective
Actions
Root
Internal or
Causes Prevent
External Describe Short term
Problem Found Reoccur- Zero
Non- the corrective
Solving rence Defects
Conformities Problem action
Corrective
Ausgabe: V3.0 (10.10.2005)
Actions
Purpose
8-D History
Late 1960´s – in the U.S.A. the Jet Propulsion Laboratory JPL developed the 4 D
method. These were the 4 “Do’s”:
1. Do: Describe the Problem
2. Do: Immediate Action
3. Do: Cause of Problem Analysis
4. Do: Corrective action
Ausgabe: V3.0 (10.10.2005)
Early 1970´s – the method was taken over by Ford and weeks later by many of the
other Automobile producers.
Interim Actions – D3
Root Causes - D4
Improve until
Verify actions – D5 Satisfied
Ausgabe: V3.0 (10.10.2005)
Implement actions – D6
Prevent Reoccurrence – D7
Lessons Learned – D8
8D - 8 Disciplines – 8 Steps
8D - 8 Disciplines – 8 Steps
Process
PROBLEM
8D - 8 Disciplines – 8 Steps
vehicles, etc).
Review team structure
Are all necessary people on board?
8D - 8 Disciplines – 8 Steps
Within 1 day*:
Written reaction to the customer regarding future procedure in particular
the introduction of immediate measures (head data, D1, D2 filled out as far
1 as possible).
2 Within 2 days*:
Initial results of defect analysis and containment actions to prevent
customers from further defects must be reported (written statement)
to him (head data, D1, D2, D3 converted).
Within 14 days*:
Ausgabe: V3.0 (10.10.2005)
14
8D - 8 Disciplines – 8 Steps
8D - 8 Disciplines – 8 Steps
Within 1 day*:
Written reaction to the customer regarding future procedure in particular
the introduction of immediate measures (head data, D1, D2 filled out as far
1 as possible).
2 Within 2 days*:
Initial results of defect analysis and containment actions to prevent
customers from further defects must be reported (written statement)
to him (head data, D1, D2, D3 converted).
Within 14 days*:
Ausgabe: V3.0 (10.10.2005)
14
QSP0508 Eng
8D - 8 Disciplines – 8 Steps
Step 4: Identify and prove the root causes
Search for all possible causes that could explain what caused the
problem
Check through the analysis if one or more of the causes can be
identified as the root cause
Make sure you can switch on / off the root causes and see the expected
result
Verify the findings and probable root causes through tests and
Ausgabe: V3.0 (10.10.2005)
experiments
8D - 8 Disciplines – 8 Steps
Step 4: Identify and prove the root cause (cont.)
*Error = Outside the specification **Deviation = inside the specification, however outliers occur
8D - 8 Disciplines – 8 Steps
NOTE: Steps 4 and 5 have to be repeated until the effect of the measure
to resolve the problem and the root cause has been proven.
8D - 8 Disciplines – 8 Steps
8D - 8 Disciplines – 8 Steps
Within 1 day*:
Written reaction to the customer regarding future procedure in particular
the introduction of immediate measures (head data, D1, D2 filled out as far
1 as possible).
2 Within 2 days*:
Initial results of defect analysis and containment actions to prevent
customers from further defects must be reported (written statement)
to him (head data, D1, D2, D3 converted).
Within 14 days*:
Ausgabe: V3.0 (10.10.2005)
14
QSP0508 Eng
8D - 8 Disciplines – 8 Steps
8D - 8 Disciplines – 8 Steps
8D - 8 Disciplines – 8 Steps
8D - 8 Disciplines – 8 Steps
Within 1 day*:
Written reaction to the customer regarding future procedure in particular
the introduction of immediate measures (head data, D1, D2 filled out as far
1 as possible).
2 Within 2 days*:
Initial results of defect analysis and containment actions to prevent
customers from further defects must be reported (written statement)
to him (head data, D1, D2, D3 converted).
Within 14 days*:
Ausgabe: V3.0 (10.10.2005)
14
QSP0508 Eng
Team Work
Interim Actions – D3
Root Causes - D4
Verify actions – D5
Ausgabe: V3.0 (10.10.2005)
Implement actions – D6
Prevent Reoccurrence – D7
Lessons Learned – D8
Activity 3: Answers
8D – Workshop D0 to D3
Activity 4: 8D
Root
Internal or
Causes Prevent
External Describe Short term
Problem Found Reoccur- Zero
Non- the corrective
Solving rence Defects
Conformities Problem action
Corrective
Actions
Ausgabe: V3.0 (10.10.2005)
Purpose:
3x 5x Why is not used to understand what failed but why the system
failed.
Predict
Predict
Check/Act Planning process - Plan
Planning process
informational content- in
informational
FMEAscontent
and
in FMEAs and CPs
Control Plans
Protect
Protect Prevent
Prevent
Quality
Qualityprocess
process - Manufacturing
Manufacturingprocess
process - -
containment
detection &
& standardizedwork
standardized workand
anderror
Ausgabe: V3.0 (10.10.2005)
responsiveness
responsiveness errorproofing
proofing
Do
Defect on Part
the defect?
Q2
Why? Prevent Root Cause
Q3
Why?
Q4
Why? Protect
Qn
Why? Corrective Action
Customer ordered Part No. 124.012 and received Part No. 123.012
Production Line
(Part Assembly)
Production Shedule
012
First Shift 123.012
Part Change over
022
Second Shift 124.012
Market Place
3x 5x Why, Worksheet
A B
Part 123 Antenna housing Part 124
C Gasket # 022 C
8D – Workshop D4
Activity 4: 8D
Root
Internal or
Causes Prevent
External Describe Short term
Problem Found Reoccur- Zero
Non- the corrective
Solving rence Defects
Conformities Problem action
Corrective
Ausgabe: V3.0 (10.10.2005)
Actions
Purpose:
Seven basic tools: These tools are used to define and analyze discrete
processes that usually produce quantitative data.
Only the last 5% of the problems need to use other instruments to find
solutions.” ASQ (American Society for Quality) 1999
Purpose:
The first four are used primarily to help understand the process, to identify
potential causes for process performance problems, and to collect and display
data indicating which causes are most prevalent.
Ishikawa
Tally Charts (Check lists)
Histogram
Pareto-Charts
The last three are used for more precise data [Link] can help you identify
Ausgabe: V3.0 (10.10.2005)
Supervisor
Worker Instructions
Issue /
Problem
Ausgabe: V3.0 (10.10.2005)
machine
Supplier material
Supervisor
Worker Instructions
Issue /
Problem
Ausgabe: V3.0 (10.10.2005)
machine
Supplier material
measurability
human methodology Ishikawa and the M´s
are frequently used
together.
Issue /
Problem
Ausgabe: V3.0 (10.10.2005)
machine
environment material
management
How to Construct:
1. Place the main problem under investigation in a box on the right.
2. Have the team generate and clarify all the potential sources of
variation.
3. Sort the process variables into naturally related groups. The labels of
these groups are the names for the major bones on the Ishikawa
diagram.
4. Place the process variables on the appropriate bones of the Ishikawa
diagram.
5. Combine each bone in turn, insuring that the process variables are
Ausgabe: V3.0 (10.10.2005)
Quality tools are primarily used to understand, analyze and improve processes.
Using the right tool for the right application is critical. It not only helps ensure
the desired results are achieved, but it also ensures snap decisions that do not
cause time to be wasted on the wrong solutions.
Example
Let’s say the work team on a continuous process wanted to reduce the
downtime of a fabrication line, because it was costing the company several
Ausgabe: V3.0 (10.10.2005)
thousand dollars per hour. The team could have simply brain-stormed some
changes but instead realized a data driven decision was more consistent with
the principles of improvement.
Problem Solving
First, the team flowcharted the process. This was a simple but important
step because it ensured each member of the team was considering the
entire line, rather than only the step of the process for which he or she
was responsible.
the data, they would not have chosen the same one indicated by the
Pareto chart.
measurability
human Records of Unplanned methodology
Training records of maintenance Plan down time General Procedure for
maintenance time Maintenance of machine
Employees Records of
machine tool Too much
Procedure s for Maintenance of unplanned
Records of replacement
specific machine x, y or z
planned time machine
machine down
Procedure s for install or Remove down time
time
machine Tool
Issue /
Problem
Records of Maintenance Planned
Replacement Part specific
Housekeeping records per General Machine
parts Tools
machine Maintenance Plan for
Tool
Ausgabe: V3.0 (10.10.2005)
Production area
Manufacture maintenance
recommendations plan Parts actually
for Maintenance and machine replaced
Maintenance plan Goals for
Maintenance
environment material
management
Sometimes the tool chosen is less about process analysis and more about getting
members of the organization to see things differently.
Machine
Material Environment
Issue /
Problem
Ausgabe: V3.0 (10.10.2005)
Human Process
Root
Internal or
Causes Prevent
External Describe Short term
Problem Found Reoccur- Zero
Non- the corrective
Solving rence Defects
Conformities Problem action
Corrective
Ausgabe: V3.0 (10.10.2005)
Actions
Quiz:
1. Which 4 of the Quality Tools are used primarily to help understand the process,
to identify potential causes for process performance problems, and to collect
and display data indicating which causes are most prevalent?
2. Please make a list, in the proper order, of all 8 Do´s.
3. Which methods have you learned that aid you in your search to find the true
root cause?
4. What is the Bosch Rapid Customer Information rule?
Ausgabe: V3.0 (10.10.2005)
Root
Internal or
Causes Prevent
External Describe Short term
Problem Found Reoccur- Zero
Non- the corrective
Solving rence Defects
Conformities Problem action
Corrective
Ausgabe: V3.0 (10.10.2005)
Actions
Sound familiar?
Some problems, we may think are solved but we can learn the hard way
that they aren’t.
We are always learning the same lessons over and over and over and
over again!
Ausgabe: V3.0 (10.10.2005)
Purpose:
A lesson learned is knowledge or understanding gained by experience:
Negative experience
Positive experience
Success
Mistakes
failures
A lesson must be significant, valid and applicable.
A lesson is not simply restating or paraphrasing existing
Ausgabe: V3.0 (10.10.2005)
doctrine, policy, process, etc. This does not qualify as an appropriate and bona
fide lesson learned.
It is therefore necessary to define how your organization will collect,validate, store,
distribute and reuse knowledge in order to achieve organizational goals and
objectives.
Observe Lesson
Learned
Re-use
Lessons Learned
Problem Description
The problem concerns a power loss of the electric motor type EM12345 due to a loose pole housing even with a tied up attachment screws (see attachment 1).
Root Cause(s)
1. Surface coating of the attachment screws lead to a higher force to tied uo the screws properly (see attachment 2 and 3).
2.
3.
Ausgabe: V3.0 (10.10.2005)
4.
5.
Lessons Learned
1. After surface coating the tolerance indication for the layer thickness has to be adapted for the right purpose (new specification: surface thickness 8 - 12µm)
2. If the coating involves screws, then the thread depth must be increased during production by the value of the coating thickness
3. Lubrication to improve the easiness of the thread
4. After assembly of a motor a functional test has to be implemented to ensure the functionality of the assembled unit. In this case a power test of the electric motor was implemented and control
using a SPC chart (see attachment 4)
5.
6.
7.
4.
After assembly of a motor a functional test has to be implemented to ensure the
4 functionality of the assembled unit. In this case a power test of the electric motor GB1 N/A
was implemented and controlled by using a SPC chart (see attachment 4)
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
Ausgabe: V3.0 (10.10.2005)
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
Ris k of Failure Action plan available Actions com pleted / No ris k of Failure N/A Not Applicable (N/A)
1 Problem description
3 Root Cause
4 SPC chart
6
Ausgabe: V3.0 (10.10.2005)
10
Root
Internal or
Causes Prevent
External Describe Short term
Problem Found Reoccur- Zero
Non- the corrective
Solving rence Defects
Conformities Problem action
Corrective
Ausgabe: V3.0 (10.10.2005)
Actions
QAM Customer
Lessons
Learned
Quality
Gates Zero Defects
Ausgabe: V3.0 (10.10.2005)
Production Area
Manufacturing Process
Example of an information
Ausgabe: V3.0 (10.10.2005)
N N Check action
Customer Is it a New 8D-
plan for current
reclamation reoccurrence? report?
dates
Y Y
N Create Problem
Are root causes Deep investigation
Solving Team /
known? (3x5xWhy)
apply 8D
Y
Ausgabe: V3.0 (10.10.2005)
Put description,
Action plan for
responsibility, date in
failure detection
action plan
Management
Standardized documentation
Fast and objective overview about process quality
Example of QAM
Ausgabe: V3.0 (10.10.2005)
Root
Internal or
Causes Prevent
External Describe Short term
Problem Found Reoccur- Zero
Non- the corrective
Solving rence Defects
Conformities Problem action
Corrective
Ausgabe: V3.0 (10.10.2005)
Actions
Unimaginable without the basic principles of GD 3 (Good Design, Good Discussion, Good
Design Review).
An open discussion about problems and failures including “Yokoten“ = spreading
knowledge and “Kaizen“ = continuous improvement.
Courage to common sense.
Further Information
Organization at Bosch
G2/PJ-BES Sub-Project DRBFM
Core Team RBJP/EDR Ishii, G2/PJ-BES Welting, C/QMT Angerbauer
More Information:
see Flyer
[Link]
[Link]
Ausgabe: V3.0 (10.10.2005)
Root
Internal or
Causes Prevent
External Describe Short term
Problem Found Reoccur- Zero
Non- the corrective
Solving rence Defects
Conformities Problem action
Corrective
Ausgabe: V3.0 (10.10.2005)
Actions
91
91
• Select/Plan Project
• Train Team on 6 sigma tools
• Create Product / Process Tree
• Identify Customer Requirements
• Define/Analyze Process
0%
• Develop Presentation
Six Sigma Project
• Develop Presentation
Six Sigma Project Scorecard
• Develop Presentation
Improve
40%
30%
90%
80%
70%
60%
50%
20%
10%
100%
Problem Solving Process
Six Sigma and Design for Six Sigma (DFSS)
Further Information
Organization at Bosch
GS/PJ-BES Sub-Project DFSS
G2/PJ-BES Suchowerskyj
8D – Workshop D5 – D8
Activity 4: 8D
Root
Internal or
Causes Prevent
External Describe Short term
Problem Found Reoccur- Zero
Non- the corrective
Solving rence Defects
Conformities Problem action
Corrective
Actions
Ausgabe: V3.0 (10.10.2005)
Root
Internal or
Causes Prevent
External Describe Short term
Problem Found Reoccur-
Zero
Non- defects, define
Anticipate the corrective
Solving rence
Defects
Conformities
measures, Problem
avoid problems action Lessons Learned process
Corrective driven by Customer
and achieve a good design
right from the start ActionsOriented Quality Organization
Ausgabe: V3.0 (10.10.2005)
Thank you very much for your attentiveness during this PSPro
training.
How to incorporate the learning into your daily routine.
• Don’t wait until you start your next project
• Utilize the learning right the next day in your job
• Ask for help
•
Ausgabe: V3.0 (10.10.2005)