Corporate Supplier Manual Guideline: 8D Method: Huf Hülsbeck & Fürst
Corporate Supplier Manual Guideline: 8D Method: Huf Hülsbeck & Fürst
Huf Group
Guideline: 8D Method
… the intelligent
touch to cars
Huf Hülsbeck & Fürst
Huf Group
Contents:
1. Objective
2. Area of Applicability
3. Definitions and Explanations
4. Proceedings and Procedures
4.1 The 8D Steps
5. Appendix
Appendix A: Explanations
Appendix B: Checklist
Appendix C: Template 8 D Report
Appendix D: Template 8 D Worksheets
1. Objective
The objective of this attachment is to define and require an 8 D problem solving and
reporting method for suppliers of the Huf Group.
2. Area of Applicability
• a standard method
• a problem solving process
• a reporting format
Every Huf complaint has to be processed by using this method. As a first step Huf
requires a fast interim 4D report (D0-D4) up to the information about containment
actions. For complaint closure the fulfillment of complete 8D method has to be
shown. Both interim 4D and final 8D report have to be submitted timely at the
request of Huf.
In the table below the 8D steps are listed including a link to all supporting documents
(e.g.: checklists, flow charts, templates). Additionally all supporting documents are
printed in the attachments.
8D- Table
5. Appendix
Appendix A: Explanations
Appendix B: Checklist
Appendix A: Explanations
Preparing for the 8D, ensure that all relevant information needed for the 8D are
available. If needed emergency actions must be implemented to separate the NOK
parts ant to protect the customer.
Establish a small team consisting of people who can contribute to solving the
problem and implementing a solution. A champion and team leader has to be
designated
Define, verify, and implement the interim containment action to isolate effects of the
problem until a permanent corrective action can be found. Validate the effectiveness.
Isolate and verify the root cause by testing each possible cause against the problem
description and test data. Also isolate and verify the place in the process where the
effect of the root cause should have been detected and contained.
List possible actions that could resolve the root cause(s) of the problem. Select the
'best' permanent corrective action(s). Verify the chosen action(s) will solve the
problem without causing undesirable effects.
Plan and implement selected permanent corrective actions. Define how the
effectiveness of the permanent corrective action(s) can be monitored continuously.
Complete the team work. Evaluate the achieved experience and decide who should
be informed about it.
Appendix B: Checklist
Common Tasks for every step
1. Do we have the right team composition to proceed the (next) step and make
decisions?
2. Has the factual information in the 8D report been reviewed and updated?
3. Have we informed all involved departments within our company/plants about 8D
status, its content with results, decisions and planned activities?
4. Have all changes been documented (FMEA, control plan, process flow, etc.)?
D0 – Preliminary step
1. Did Huf require emergency response actions or are those actions necessary
from our point of view?
2. How was the emergency response action verified and validated?
3. Is the symptom complexity known? Have the symptoms been quantified and
confirmed with measurements?
4. Does already an 8D report exist for this problem? Is it a repeated problem?
D1 – Establish a Team
1. Has the Team Leader/Champion of the team been identified?
2. How is Huf represented in the 8D team?
3. Are the departments/plants affected by the problem represented in the team?
Does the team structure ensure all necessary input and required experience? Is
the team small enough to act effectively?
4. Are the roles and responsibilities of the team members clear?
5. Does the team have sufficient decision-making authority and/or is the decision
process clear?
D2 – Problem Description
1. Do we have a clear description of the specific problem?
2. Is/Are the symptom(s) clear? Are the conditions clear when symptoms occur? If
more than one symptom exists, is it possible to separate them clearly?
3. Have 'Repeated Whys' been used? What's wrong with what? Has Is/Is-Not
Analysis been performed (what, where, when, how big)?
4. Has this problem appeared before? If yes, where in the process?
5. Is it a 'something changed' or a 'never been there' situation?
6. Does this process flow reflect the last approved status?
7. Are samples with these symptoms available?
8. Have all required data been collected and analyzed?
9. Do we have enough information to investigate and evaluate potential root
cause(s)? If not, which information and analysis are missing?
10. Which influence has the emergency response actions to the deviation?
11. Could the problem affect other/similar components or assemblies?
12. Has the Problem Description been confirmed by team and Huf?
D3 – Containment Actions
1. Are Containment Actions necessary and/or required by Huf? Have criteria been
established for selection of Containment Actions?
2. Have the appropriate departments/plants been involved in this containment
action decision?
3. Have appropriate Advanced Product Quality Planning (APQP) tools (e.g., FMEA,
control plans, instructions) been considered? Have we considered the
experience from the emergency response actions?
4. Is it ensured that the Containment Actions protect Huf totally from the effect?
How have all containment actions been successfully verified?
5. Do the Containment Actions show an adequate balance of benefits and risks?
Are implementation resources adequate?
6. Do we have a clear plan to implement the Containment Actions (who has to do
what and when)?
7. Did we inform Huf via 8D report? Is Huf approval required and given?
8. How is the effectiveness of the containment action? Which improvements are
necessary?
D4 – Root Cause(s)
1. What sources of information have been used to develop the potential root-cause
list? Do we have all needed information and analysis results?
2. Which quality tools are in use to find the root cause(s)? Has a Cause & Effect
Diagram been completed? Have 'Repeated Whys' been used?
3. Can we clearly identify factor(s) changed which contributes to this problem?
What data make us sure that these changed factors are responsible for the
problem?
4. If we indicated more than one potential root cause, does the sum account for 100
percent the problem? Do all known data confirm this?
5. Do(es) the root cause(s) match to the problem according the Problem
Description?
6. Is the desired performance level (specification) achievable?
7. If the desired performance level is not achievable, which other changes (e.g.
design) can solve the problem?
8. Is it useful to split the 8D investigations with regard to the single potential root
causes (sub-8D e.g. with supplier)?
9. Has the root-cause analysis gone deep enough? How did we verify the root
cause(s)?
10. Is a control system for relevant parameters available and verified to detect the
problem? Is there a need to improve the control system?
D7 – Prevent Recurrence
1. Where in our process did this problem enter and how could this happen?
2. What procedures or conditions allowed this problem to occur without detection?
3. Have all affected processes, production lines and/or products been identified?
4. What will be done differently to prevent recurrence of the root cause?
5. Who needs to be informed about the identified opportunities for improvement? Is
a plan available to coordinate preventive actions and standardize the practices
(who has to do what and when)?
6. How can we verify and validate the preventive actions?
7. Does the champion confirm these preventive actions?
8. Did we publish and transfer all knowledge from present 8D to the knowledge
data base? If applicable is also information included about not implemented – but
as most effective identified - corrective actions? How is ensured that results and
experiences will be saved?
D8 – Problem solved
1. Has the 8D published to the Huf and internal addressees?
2. Are there opportunities to provide recognition from Leader to Team, Team
Member to Team Member, Team to Leader, Team to Champion? Significant
contributions by individual team members?
3. Review of 8D objectives. What was done well in this problem solving process
and what gives opportunity for improvement?
4. Is the 8D report officially closed / signed off?
5. Is the 8D report completed?
% Beteiligung/
4. Fehlerursache(n)/Root cause(s): Wer/Who Wann/When
Contribution
Wirksamkeit/
5. Geplante Abstellmaßnahmen/Select Permanent Corrective Actions: Wer/Who Wann/When
Efficiency
Wirksamkeit/
6. Eingeführte Abstellmaßnahme/Choose Permanent Corrective Action: Wer/Who Wann/When
Efficiency
Design-FMEA/Design FMEA
Prozess-FMEA/Process FMEA
Kontrollplan/Control Plan
Inspektionsplan, Produktprüfung/Inspect.Plan, Prod.Inspect.
Prozessbeschreibung/Procedure
Abschlussdatum/
8. Problem gelöst/Problem solved
Close date:
Unterschrift Teamleiter/Sign off Team Leader:
Verteiler/Distribution:
Anhänge/Attachments:
Ursache(n)/Root cause(s):
Fehlerbild/Picture of failure:
8D Worksheet D0 – D3
Lieferant/Supplier:
2. Problembeschreibung/Problem Description:
Art der Rückweisung/ Gewährleistung/ intern/ extern/ Serienproduktion/ Projekt/
0 km
Kind of reject: Warranty internal external Serial Production Project
Menge der von Huf zurück gewiesenen Teile/ Menge der fehlerhaften Teile/ bei/at Huf:
Qty. of rejected parts by Huf: Qty. of defect parts: innerbetrieblich/in house
Chargen-Nr. der fehlerhaften Teile/ Produktiondatum/
Lot No. of defect parts: Production date:
8D Worksheet D4 – D5
Lieferant/Supplier:
4. Ursache(n)/Root cause(s):
Bei mehreren Ursachen muss hier die Gesamtheit 100% der Problemursachen darlegen. Wer/Who Wann/When Anteil/
If more than one root cause are existent, the total must be 100% contribution of the problem. Contribution
1. Ursache/1st root cause
Anhänge/Attachments: ∑ 100 %
Zur Ermittlung der Ursache sollten Methoden wie FTA, Ishikawa, 5 Why´s angewendet und angehängt werden./
For root cause identification the methods like FTA, Ishikawa, 5 Why´s should be used and attached.
waru m/why
Problem
warum/wh y
Problem
w arum/why
warum/wh y
w arum/wh y
Anhänge/Attachments:
Problem warum/why
Methode/Method
warum/why
Measurement to Method
Management to Man Material Mitwelt/Mother nature
warum/why
(environmental)
derzeitige
5M Kategorie/ Faktor/ Warum Frage/ Warum Antwort/ Fehlerermittlung/ Ursache/
5M category Factor Why question Why answer current failure detection root cause
(FMEA, Control Plan)
Mann/
Man
Maschine/
Machine
Methode/
Method
Material
Mitwelt/
Mother Nature