Supplier 8D Ref.

Initiated Date:
Updated:
in cells, to add a new line of text press 'Alt + Enter', row height will need to be adjusted
Customer Name: Supplier: Supplier Code:
Customer Site :
Customer Report No: Customer Part No Description:
Programme: Quantity rejected; Quantityat risk: Recurrence: YES / NO
D1. Establish Team / Team ( Name / Title / Telephone / Dept:/ e-mail )
Team Leader:
Team :
D0. Emergency Response Actions:
D2. Describe the problem / Detailed Description of Problem: Key Problem Description Summary (Is / Is Not)
What
Where
When
How Big
Other
Quantity OK Quantity N-OK When % Effective
D4. Root Cause Occur (RCA) / Originating cause of problem
% Contribution
D4. Root Cause Escape (RCA) (Consider WHY defect escaped to next stage of process / customer)
% Contribution
ACCEPT REJECT
ACCEPT REJECT
When
When
Responsibility Date
DFMEA Yes / No
Drawing Yes / No
PFMEA Yes / No
Control Plan Yes / No
Process instructions Yes / No
Training Matrix Yes / No
Others specify Yes / No
Date
Review and update systems / procedures Date
The team has been informed of action results and their effectiveness and congratulated.
8D report closure date: Approved by:
VERIFICATION Test to confirm ICA is effective
1. Similar Part / Process a
D8. Recognize Team and Individual Contributions
Action
Action Implementation Documentation (required)
Responsibility
Action Responsibility
Review and update other similar products or lines
VERIFICATION Test to Prove RCA by switching RCA on and off
ACTIONS
duplicate D6
D7. Prevent Recurrence Similar Parts and Processes / Occur and Escape Actions implemented to prevent recurrence
VERIFICATION Test to Prove RCA by switching RCA on and off
CAUSE Responsible
VISTEON 8D REPORT
General Info:
D0. Symptoms / Problem definition:
Customer Contact (Name / Tel / e-mail):
Responsible CAUSE
OCCUR ACTIONS Who
VERIFICATION of chosen PCA
D5. Select Permanent Corrective Actions (PCAs)- Occur / Select permanent corrective action
VERIFICATION of chosen PCA
D5. Select Permanent Corrective Actions (PCAs)- Escape / Select permanent corrective action
ACTIONS
D6. Implement Permanent Corrective Actions (PCAs) / Effectiveness confirmation of implemented actions
Status
D7. Prevent Recurrence Systemic issues / Actions resulting from Predict root cause analysis for new product introduction and / or Quality Systems
Status
D3. Develop Interim Containment Action ( ICA ) / Plan temporary countermeasures to protect customer
(Consider MAN,MATERIAL, MACHINE, METHOD, WHO, WHERE, WHY, HOW)
VALIDATION Data to prove ICA is effective
Responsibility
Validation:
VALIDATION Data / Activity Confirming that PCA is effective over time / cycles and has no adverse effects
ACTIONS
Verification:
Action:
Problem Statement:
Typically 20 words or less
ESCAPE ACTIONS Who
SP GL SF 1021
Date: July 6, 2007
8D Report Coversheet
Supplier 8D Ref.
Initiated Date:
Updated:
Customer Name: Supplier: Supplier Code: Example GSDB
Customer Site :
Customer Report No: Customer Part No Description:
Programme: Quantity rejected; Quantityat risk: Is this a Recurrence: YES / NO
D1. Establish Team / Team ( Name / Title / Telephone / Dept:/ e-mail )
Team Leader:
Team :
D0. Emergency Response Actions:
D2. Describe the problem / Detailed Description of Problem:
What
Where
When
How Big
Other
Quantity OK Quantity N-OK When % Effective
D4. Root Cause Occur (RCA) / Originating cause of problem
% Contribution
D4. Root Cause Escape (RCA) (Consider WHY defect escaped to next stage of process / customer)
% Contribution
ACCEPT REJECT
ACCEPT REJECT
When
When
Responsibility Date
DFMEA Yes / No
Drawing Yes / No
PFMEA Yes / No
Control Plan Yes / No
Process instructions Yes / No
Training Matrix Yes / No
Others specify Yes / No
Date
Review and update systems / procedures Date
The team has been informed of action results and their effectiveness and congratulated.
8D report closure date: Approved by:
Proof developed before implementation that the action will do what is intended and does not introduce a new problem - providing before
and after data comparison
Details of actions taken to isolate the customer from the effects of the
problem, based on evidence from problem description, until the Permanent
corrective action can be introduced. This is typically "Firewall" containments +
purge and sort activities
Resulting data from
containment to add to
the problem description
data
Resulting data
from containment
to add to the
problem
description data
Actions MUST have responsible PERSON
assigned to a team member listed in D1
Actions must have a
commitment date for
implementation
Resulting
effectiveness of
containment
introduced
VERIFICATION Test to confirm ICA is effective
Verification:
Action:
Proof developed before implementation that the action will do what is
intended - providing before and after data comparison
How did you respond to the symptom(s) Detail exactly how the
action(s) will be performed and when.
Key Problem Description Summary (Is / Is Not) - Once a problem is defined continue to ask why until you reach a level that can be acted
upon
List the team members and contact details. The team should consist of more than one person. If possible
consider including the customer on the team. The role of Leader or Champion should be assigned to a person
who has ownership of the problem and the authority to implement actions, provided necessary support and
leadership for the team's recomendations and actions.
Validation:
Ongoing evidence that the implemented action is doing what was
intended without introducing a new problem.
ACTIONS
What Object or Part / What Concern (defect)
Where seen on the object / In the process / The geographical location
When first discovered / When else seen / When seen in the process
What is the trend / How big is the problem / How many objects affected
What defect is ocurring to what?
This should be developed from the
customer's symptom. It should be more
directed and focused than symptom.
D3. Develop Interim Containment Action ( ICA ) / Plan temporary countermeasures to protect customer
Problem Statement:
Typically 20 words or less
ESCAPE ACTIONS Who Status
CAUSE
CAUSE
Data based definition of root cause(s).
Use the problem solving worksheet as this will assist to confirm changes and differences from IS / IS NOT analysis.
Why did the problem OCCUR on the object - challenge the conclusion by continually asking WHY?
Using the data collated, Identify the best Permanent Corrective Action to remove the root cause - use the decision making worksheet and focus on Impact and Risk.
PCA listed is
confirmed as selected
for use
VERIFICATION of chosen PCA
Proof developed before implementation that the action will do what is intended and does not introduce a new problem - providing before and after data comparison
VALIDATION Data to prove ICA is effective
Closure to be approved by Champion listed in the Team members
D7. Prevent Recurrence Systemic issues / Actions resulting from Predict root cause analysis for new product introduction and / or Quality Systems
(Consider MAN,MATERIAL, MACHINE, METHOD, WHO, WHERE, WHY, HOW)
Ongoing evidence that the implemented action is doing what was intended without introducing a new problem.
Actions MUST have responsible PERSON
assigned to a team member listed in D1
Percentage
contribution assigned
to each root cause
VALIDATION Data / Activity Confirming that PCA is effective over time / cycles and has no adverse effects
Current status of action
Who
D0. Symptoms / Problem definition:
Customer Contact (Name / Tel / e-mail):
The symptom is what the customer tells you he is seeing. You should also use this section to record
how you were informed of the problem and by whom
VISTEON 8D REPORT
Typically Visteon site
General Info: Including details from customer identifying the issue and supplier reference information
Part Description
Typically Visteon
Supplier reference
data
Guidance for Report completion in "blue"
Current status of action
VERIFICATION of chosen PCA
D5. Select Permanent Corrective Actions (PCAs)- Occur / Select permanent corrective action
PCA listed is rejected
for use
Using the data collated, Identify the best Permanent Corrective Action to remove the root cause - use the decision making worksheet and focus on Impact and Risk.
Proof developed before implementation that the action will do what is intended and does not introduce a new problem - providing before and after data comparison
Actions must have
a commitment date
for implementation
Action or actions listed to stop the non-conformancy from being created again Responsible PERSON for implemented
corrective action.
Note: NOT organisation
Actions must have
a commitment date
for implementation
Responsibility
Have you been able to make the problem come and go (ABA testing)?
Does your customer agree with your identified root cause?
D5. Select Permanent Corrective Actions (PCAs)- Escape / Select permanent corrective action
ACTIONS
D6. Implement Permanent Corrective Actions (PCAs) / Effectiveness confirmation of implemented actions
Status OCCUR ACTIONS
Have you been able to make the problem come and go (ABA testing)?
Does your customer agree with your identified root cause?
Action or actions listed to stop the non-conformancy passing beyond point of creation or beyond the
supplier to Visteon or its customers
D7. Prevent Recurrence Similar Parts and Processes / Occur and Escape Actions implemented to prevent recurrence
Ongoing evidence that the implemented action is doing what was intended without introducing a new problem.
Action Implementation Documentation (required)
Actions must have a
commitment date for
implementation
Responsible PERSON
for implemented
corrective action.
Note: NOT
organisation
Changes or Updates to DOCUMENTATION to stop the non-conformancy being created or passing beyond
point of creation or beyond the supplier to Visteon or its customers
Responsible
VERIFICATION Test to Prove RCA by switching RCA on and off
PCA listed is
confirmed as selected
for use
ACTIONS
PCA listed is rejected
for use
VERIFICATION Test to Prove RCA by switching RCA on and off
Responsible
Data based definition of root cause(s).
Use the problem solving worksheet as this will assist to confirm changes and differences from IS / IS NOT analysis.
Why did the issue ESCAPE beyond this process step - challenge the conclusion by continually asking WHY?
Actions MUST have responsible PERSON
assigned to a team member listed in D1
Percentage
contribution assigned
to each root cause
Responsible PERSON for implemented
corrective action.
Note: NOT organisation
D8. Recognize Team and Individual Contributions
Action Responsibility
Action Responsibility
Review and update other similar products or lines
Review SYSTEMIC TOOLS (Product or Process
design and control tools) to establish what system
failed to identify or correctly control the risk and failure
mode
Responsible PERSON for implemented
corrective action.
Note: NOT organisation
Action or actions listed to correct the SYSTEMIC FAILURE to stop the POTENTIAL of non-
conformancy from ANY SIMILAR FUTURE PART OR PROCESS being created or
passing beyond point of creation or beyond the supplier to Visteon or its customers.
List similar parts or processes that need to be updated
in line with lessons learned from this non-conformancy
Actions must have a
commitment date for
implementation
Action or actions listed to stop the POTENTIAL of non-conformancy from a similar part or
process, passing beyond point of creation or beyond the supplier to Visteon or its
customers
Responsible PERSON for implemented
corrective action.
Note: NOT organisation
Actions must have a
commitment date for
implementation
SP GL SF 1021
Date: July 6, 2007
8D Report - Completion Guidance