VISTEON 8D REPORT

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
General Info: Customer Name: Customer Site : Customer Report No: Programme: D0. Symptoms / Problem definition: Supplier: Customer Contact (Name / Tel / e-mail): Customer Part No Quantity rejected; Supplier Code:

Description: Quantity at risk: Recurrence: D1. Establish Team / Team ( Name / Title / Telephone / Dept:/ e-mail ) Team Leader: Team :

YES / NO

D0. Emergency Response Actions: Action: Verification: Validation:

Key Problem Description Summary (Is / Is Not) What Where When How Big Other D3. Develop Interim Containment Action ( ICA ) / Plan temporary countermeasures to protect customer ACTIONS Quantity OK Quantity N-OK D2. Describe the problem / Detailed Description of Problem: Problem Statement: Typically 20 words or less

Responsibility

When

% Effective

VERIFICATION Test to confirm ICA is effective VALIDATION Data to prove ICA is effective D4. Root Cause Occur (RCA) / Originating cause of problem CAUSE (Consider MAN,MATERIAL, MACHINE, METHOD, WHO, WHERE, WHY, HOW) Responsible % Contribution

VERIFICATION Test to Prove RCA by switching RCA on and off

D4. Root Cause Escape (RCA) CAUSE

(Consider WHY defect escaped to next stage of process / customer) Responsible

% Contribution

VERIFICATION Test to Prove RCA by switching RCA on and off

D5. Select Permanent Corrective Actions (PCAs)- Occur / Select permanent corrective action ACTIONS

ACCEPT

REJECT

VERIFICATION of chosen PCA

D5. Select Permanent Corrective Actions (PCAs)- Escape / Select permanent corrective action ACTIONS

ACCEPT

REJECT

VERIFICATION of chosen PCA

D6. Implement Permanent Corrective Actions (PCAs) / Effectiveness confirmation of implemented actions OCCUR ACTIONS

Who

When

Status

ESCAPE ACTIONS

Who

When

Status

Implementation Documentation (required) Action 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 VALIDATION Data / Activity Confirming that PCA is effective over time / cycles and has no adverse effects

Responsibility

Date

D7. Prevent Recurrence Similar Parts and Processes / Occur and Escape Actions implemented to prevent recurrence Review and update other similar products or lines Action duplicate D6 1. Similar Part / Process a

Responsibility

Date

D7. Prevent Recurrence Systemic issues / Actions resulting from Predict root cause analysis for new product introduction and / or Quality Systems Review and update systems / procedures Action

Responsibility

Date

D8. Recognize Team and Individual Contributions The team has been informed of action results and their effectiveness and congratulated. 8D SP GL SF 1021 report closure date: Date: July 6, 2007 Approved by:

8D Report Coversheet

VISTEON 8D REPORT Guidance for Report completion in "blue"

Supplier 8D Ref. Initiated Date : Updated: Supplier reference data

General Info: Including details from customer identifying the issue and supplier reference information Customer Name: Typically Visteon Supplier: Supplier Code: Example GSDB Customer Site : Typically Visteon site Customer Contact (Name / Tel / e-mail): Customer Report No: Customer Part No Description: Part Description Programme: Quantity rejected; Quantity at risk: Is this a Recurrence: YES / NO D0. Symptoms / Problem definition: D1. Establish Team / Team ( Name / Title / Telephone / Dept:/ e-mail ) The symptom is what the customer tells you he is seeing. You should also use this section to record Team Leader: how you were informed of the problem and by whom Team : D0. Emergency Response Actions: Action: How did you respond to the symptom(s) Detail exactly how the action(s) will be performed and when. List the team members and contact details. The team should consist of more than one person. If possible Verification: Proof developed before implementation that the action will do what is 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 intended - providing before and after data comparison 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. D2. Describe the problem / Detailed Description of Problem: Problem Statement: Typically 20 words or less 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

What What Object or Part / What Concern (defect) Where Where seen on the object / In the process / The geographical location When When first discovered / When else seen / When seen in the process How Big What is the trend / How big is the problem / How many objects affected Other D3. Develop Interim Containment Action ( ICA ) / Plan temporary countermeasures to protect customer ACTIONS Quantity OK Quantity N-OK Responsibility When % Effective Details of actions taken to isolate the customer from the effects of the Resulting data from Resulting data Actions MUST have responsible PERSON Actions must have a Resulting problem, based on evidence from problem description, until the Permanent containment to add to from containment assigned to a team member listed in D1 commitment date for effectiveness of corrective action can be introduced. This is typically "Firewall" containments + the problem description to add to the implementation containment purge and sort activities data problem introduced description data VERIFICATION Test to confirm ICA is effective Proof developed before implementation that the action will do what is intended and does not introduce a new problem - providing before What defect is ocurring to what? This should be developed from the customer's symptom. It should be more directed and focused than symptom. and after data comparison VALIDATION Data to prove ICA is effective D4. Root Cause Occur (RCA) / Originating cause of problem Ongoing evidence that the implemented action is doing what was intended without introducing a new problem.

(Consider MAN,MATERIAL, MACHINE, METHOD, WHO, WHERE, WHY, HOW) Responsible % Contribution Actions MUST have responsible PERSON Data based definition of root cause(s). Percentage assigned to a team member listed in D1 Use the problem solving worksheet as this will assist to confirm changes and differences from IS / IS NOT analysis. contribution assigned Why did the problem OCCUR on the object - challenge the conclusion by continually asking WHY? to each root cause CAUSE

VERIFICATION Test to Prove RCA by switching RCA on and off Have you been able to make the problem come and go (ABA testing)? Does your customer agree with your identified root cause? (Consider WHY defect escaped to next stage of process / customer) CAUSE Responsible % Contribution Actions MUST have responsible PERSON Data based definition of root cause(s). Percentage assigned to a team member listed in D1 Use the problem solving worksheet as this will assist to confirm changes and differences from IS / IS NOT analysis. contribution assigned Why did the issue ESCAPE beyond this process step - challenge the conclusion by continually asking WHY? to each root cause

D4. Root Cause Escape (RCA)

VERIFICATION Test to Prove RCA by switching RCA on and off 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)- Occur / Select permanent corrective action ACTIONS 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. 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 D5. Select Permanent Corrective Actions (PCAs)- Escape / Select permanent corrective action ACTIONS 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. 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 D6. Implement Permanent Corrective Actions (PCAs) / Effectiveness confirmation of implemented actions OCCUR ACTIONS Who Action or actions listed to stop the non-conformancy from being created again Responsible PERSON for implemented corrective action. Note: NOT organisation ESCAPE ACTIONS Action or actions listed to stop the non-conformancy passing beyond point of creation or beyond the supplier to Visteon or its customers Who Responsible PERSON for implemented corrective action. Note: NOT organisation ACCEPT REJECT PCA listed is PCA listed is rejected confirmed as selected for use for use

ACCEPT REJECT PCA listed is PCA listed is rejected confirmed as selected for use for use

When Actions must have a commitment date for implementation When Actions must have a commitment date for implementation

Status Current status of action

Status Current status of action

Implementation Documentation (required) Action DFMEA Yes / No Drawing Yes / No PFMEA Yes / No Changes or Updates to DOCUMENTATION to stop the non-conformancy being created or passing beyond Control Plan Yes / No point of creation or beyond the supplier to Visteon or its customers Process instructions Yes / No Training Matrix Yes / No Others specify Yes / No VALIDATION Data / Activity Confirming that PCA is effective over time / cycles and has no adverse effects Ongoing evidence that the implemented action is doing what was intended without introducing a new problem. D7. Prevent Recurrence Similar Parts and Processes / Occur and Escape Actions implemented to prevent recurrence Review and update other similar products or lines Action Action or actions listed to stop the POTENTIAL of non-conformancy from a similar part or List similar parts or processes that need to be updated process, passing beyond point of creation or beyond the supplier to Visteon or its in line with lessons learned from this non-conformancy customers D7. Prevent Recurrence Systemic issues / Actions resulting from Predict root cause analysis for new product introduction and / or Quality Systems Review and update systems / procedures Action 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 D8. Recognize Team and Individual Contributions The team has been informed of action results and their effectiveness and congratulated. 8D report closure date:
SP GL SF 1021 Date: July 6, 2007

Responsibility

Date

Responsible PERSON for implemented Actions must have a corrective action. commitment date for Note: NOT implementation organisation

Responsibility Responsible PERSON for implemented corrective action. Note: NOT organisation Responsibility Responsible PERSON for implemented corrective action. Note: NOT organisation

Date Actions must have a commitment date for implementation Date Actions must have a commitment date for implementation

Action or actions listed to correct the SYSTEMIC FAILURE to stop the POTENTIAL of nonconformancy from ANY SIMILAR FUTURE PART OR PROCESS being created or passing beyond point of creation or beyond the supplier to Visteon or its customers.

Approved by:

Closure to be approved by Champion listed in the Team members

8D Report - Completion Guidance