8D Template

8D Template
Target Level Excellent Level

D2
Problem description Problem description (Detailed)
D3
1 Problem Definition CP/PQA 6 Situation/problem definition according to KT
D4
Occurance
2 Photos & Drawings CP/PQA 7 Description of problem in assembly or vehicle. CP/PQA
D4
Detection
Prelimenary Risk Management
CP/PQA
3 Timeline Chart
Supplier
D5-D6 8 Estimates the occurrence probability CP/PQA
Occurance
4 Flow Charts Supplier

D5-D6 9 Estimates the damage magnitude
Detection (e.g. number of affected customers,). CP/PQA
5 Trend Charts Supplier

D7 10 Effects on end user / vehicle / product
have o be estimated to be able to initiate CP/PQA
adequate containment actions in D3.
D8
1 CP/PQA-BuP1 | 09.07.2015 | © Robert Bosch GmbH 2009. All rights reserved, also regarding any disposal, exploitation, reproduction, editing,
distribution, as well as in the event of applications for industrial property rights.
8D Template xx.xx.2015
1
Problem Definition D2
Type Nr
Part Name
Batch Nr
Way Bill Nr
Charge Nr
Quantity
Defect
Defect Quantity
Place of detection
HATALI PARÇA FOTOĞRAFLARINI VE GEREKLİ TEKNİK DÖKÜMANI

EKLE!
(Gerektiğinde sayfa sayısını çoğaltabilirsiniz)
3
Timeline Chart D2
Immediate actions ongoing in

supplier.
Possible Risk Area!
Blocked List
Type Nr Batch Nr Quantity Charge Way Bill
F00 XXX XXX XXX XXX XXX XXX Production date (Supplier)
Deliver to BuP1
Detection Date
Start of 8D
Clean date (Start of containment)
4
Flow Chart D2
 (Showing the possible Problem Occurrence and Non-Detection steps)

Possible Occurrence point
5
Trend Chart-Effected Batches D2
CP/PQA-BuP1
Did we face this problem before at Bosch?
Inputs No Yes When
0 km
Field
Production
Assembly Line
Supplier
Did we face this problem before at in-house production?
Inputs No Yes When
Customer
Production
%100 Eddy-liner
%100 Magnaflux
%100 Visual Control
6
Problem Visualization D2
Hatanın enjektör üzerindeki yerini görselleştirilir.
7
Description of problem in assembly or vehicle
Hatanın montaja veya araca olan etkisi ile ilgili Ar-Ge veya QMM’den bilgi alınarak ve bu alana ek’lenir.
Risk Management D2
8  Estimates the occurrence probability

- Inventory has been investigated.
- Stock suspicious btw XX.XX.XXXX and XX.XX.XXXX
1.RBTR warehouse: XXX parts were blocked.
2.RBTR Assembly Line : XXX Injector were blocked.
3.RBTR Production: XXX machined parts were blocked.
Total delivery : X pcs

Defects : X pc / pcs ( faulty part )
Current occurrence probability : X (Defect Quantity) / X (Total Delivery Quantity) *1000000 =? ppm.
9  Which Customers would be effected?

Intern Customer :
Extern Customer:
10  Effects on End Customer:
Immediately Actions
Target Level
D2
Information to; Blocking / Sorting Actions;

D3
1 Warehouse; Supplier 5 Blocking actions; Bosch
D4 (For blocking actions) How many? When? Where? Supplier
Occurrence
2 Production; 6 Sorting actions; Sorting Company
Supplier
(Follow-up shifts, Other prod. lines/plants) Which sorting method used? Supplier
D4
Detection
7 Sorting actions; Sorting Company
3 Effected Bosch Plants; Supplier
Which deliveries effected or suspicious?
Evidence of Sorting effectiveness. Supplier
D5-D6
Occurrence Give information on truck deliveries.
4 Sub-Suppliers; Supplier
(If necessary)
D5-D6
Detection
D7
D8
Information to D3
1  Warehouses :
 “X” was informed on xx.xx.20xx by “Y” per “e-mail / telephone / ...”
(if not necessary please explain why?)
2  Production : (All shifts, other production lines and plants)

3  Other Bosch Plants :

4  Sub-Suppliers :
5
Blocking /Sorting Actions D3
Where Quantity Date Action Results
Supplier-Warehouse
Supplier-Production
Sub-Suppliers
RBTR-Warehouse
MFT Production area
Assembly Line
On The Way
Customer
O-Km
Field
When the sorting action was finished, Supplier and Bosch should be updated the document.
6
Efficiency % By Containment Method D3
Only Examples of Efficiency…..
0% No Sorting
1% - 70% Sorting Person Variable Criteria
80% Sorting Person Attribute Criteria

Assumes 100% of product is sorted with this
Detection Process
90% Sorting Person with Go / No Go
100% Sorting using Camera
100% Sorting using CMM
11 MFM | 09.07.2015 | © Robert Bosch GmbH 2009. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of
applications for industrial property rights.
7
Evidence of Sorting effectiveness : D3
 Effectiveness of sorting method :

(e.g. G R&R or Attributive R&R Result)
Effectiveness of containment actions must be documented. Not all containment actions

ensure a 100% filter, in such cases the evaluation of the efficiency is necessary to feed the
risk assessment.
 Confirmation of the stability of this check over time (especially shift end in case of human
visual control…) ? Multiple checking of same lots ?
Root Cause Analysis for occurrence

D2
The Root Cause (TRC & MRC)
D3
1 In reference to all facts compiled in D2
D4 (In supply-on)
Occurance
2 Using problem solving methods / tools
Ishikawa (Fish Bone)
D4
Detection 3x5xWhy-question technique
D5-D6
Occurance 3 Reproduction of the incident can be validated.
Simulation
Testing
D5-D6
Detection
4 Risk Assessment
D7
D8
13 MFM | 09.07.2015 | © Robert Bosch GmbH 2009. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well
as in the event of applications for industrial property rights.
Root Cause Analysis for occurrence - Ishikawa xx.xx.2015
2 3
2 1 D4
Material Method Machine
Problem
Possible root cause
Human Environment Potential root cause was

6 5 4 eliminated by investigations
14 CP/PQA-RBTR | 09.07.2015 | © Robert Bosch GmbH 2009. All rights reserved, also regarding any disposal, exploitation, reproduction, editing,
Root Cause Analysis for occurrence – 5 Why Analysis xx.xx.2015
2 D4
WHY? WHY? WHY? WHY?
Occurrence Simulation xx.xx.2015
3 D4
Root Cause Analysis for Detection

D2
The Root Cause (TRC & MRC)
D3
1 In reference to all facts compiled in D2
D4 (In supply-on)
Occurance
2 Using problem solving methods / tools

D4 Ishikawa (Fish Bone)
Detection
3x5xWhy-question technique
D5-D6
Occurance
3 Non-detection can be validated with, for
example, a test setup. Otherwise, the reason
D5-D6 must be documented.
Detection
4 Other documents updated

D7
D8
17 MFM | 09.07.2015 | © Robert Bosch GmbH 2009. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well
as in the event of applications for industrial property rights.
Root Cause Analysis for Detection - Ishikawa xx.xx.2015
2 3
2 1 D4
Material Method Machine
Problem
Possible root cause
Human Environment Potential root cause was

6 5 4 eliminated by investigations
18 CP/PQA-RBTR | 09.07.2015 | © Robert Bosch GmbH 2009. All rights reserved, also regarding any disposal, exploitation, reproduction, editing,
Root Cause Analysis for Detection- 5 Why xx.xx.2015
2 D4
WHY? WHY? WHY? WHY?
Detection Simulation xx.xx.2015
3 D4
Risk Assessment xx.xx.2015
Target Level
D2
Risk Assessment
D3
The risk assessment includes;
D4 the severity of the fault, the probability of it occurring or being
Occurance discovered and an estimation of its potential extent.
D4 1 -Severity (Şiddeti)
Detection
2 -Occurrence
D5-D6
Occurance 3 -Detection
4 -Potential extend (Customer)

D5-D6
Detection
D7
D8
Risk Assessment xx.xx.2015
Risk Management D4
8  Estimates the occurrence probability

- Inventory has been investigated.
- Stock suspicious btw XX.XX.2015 and XX.XX.2015
Corrective actions for Occurrence

D2
The Technical Root The Management Root

D3 Cause Cause
(TRC) (MRC)
6 Effectiveness is assessed and evaluated
D4 with regard to risks on other products /
The corrective actions defined, fully cover the processes.
Occurance 1
causes listed in D4 (Side-effects)
D4
Detection
2 Evidence of effectiveness of corrective actions
taken is provided before immediate measures 7 A protection via Poka Yoke could be
D5-D6 are withdrawn. (Photos, Sketches, Tests, introduced.
Occurance Simulations)
D5-D6 3 Persons responsible are designated and dates

Detection
set. (Documented in supply-on)
D7
D8
8D Template
Corrective Actions for Occurrence (TRC) D5/D6
Before Corrective Action
After Corrective Action
8D Template 30.07.2014
Corrective Actions for Occurrence (MRC) D5/D6
Corrective actions for Detection xx.xx.2015

D2
The Technical Root The Management Root

D3 Cause Cause
(TRC) (MRC)
4 Plan for monitoring effectiveness provided.
D4 e.g. Check the Checker, Attribute R&R
Occurance 1 The corrective actions defined, fully cover the
causes listed in D4
D4
Detection
2 Evidence of effectiveness of corrective actions
taken is provided before immediate measures
D5-D6 are withdrawn. (Photos, Sketches, Tests,
Occurance Simulations)
D5-D6 3 Persons responsible are designated and dates

Detection
set.
D7
D8
8D Template XX.XX.2015
Corrective Actions for Detection (TRC&MRC) D5/D6
8D Template XX.XX.2015
Corrective Actions for Detection (MRC) D5/D6

Effectiveness Control xx.xx.2015
Immediately Actions Preventive Actions
2.714.978 pcs.
Diesel Systems
Preventive Actions

D2
Up-dating
D3
1 FMEA
(Before Rpz and after Rpz value must be write in supply-on)
D4
Occurance
2 Training Form
D4 3 Systematic Training Form

Detection
4 Work instruction
D5-D6 5 Capability Analysis Results
Occurance
6 Drawings
D5-D6
Detection
Lessons learned
D7 7 Lessons learned to all concerned
prducts/processes/locations
(e.g IPN, Daily sharing)
D8
30 CP/PQA-BuP1 | 09.07.2015 | © Robert Bosch GmbH 2009. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of
applications for industrial property rights.
Requirement for ‘Basic level’ D7
 FMEA Updated (Nr: ___)
 CP updated (if necessary) (Nr: ___)

 Work Instruction updated (Nr: ___)
 Drawing updated (Nr: ___)
 Maintenance Plan updated (Nr: ___)
 Other documents updated (Description, Nr.)
 LL shared in meeting on XX.XX.XXXX with other line and BaP, HoP ,FeP Plants (all
related plants)
 Note : Attach the updated file or print screens of the updated part.
8D Template
D8
Final Meeting
8D Template
Requirement for ‘Basic level’ D8
 Takım lideri 8D kapanışını yapmadan önce 8D check list ile yapılan çalışmaları içerik
ve metodik açıdan değerlendirir eğer yapılan değerlendirme sonucunda min %67
puana ulaşıyorsa 8D’yi ilgili dokümanlar ile birlikte supply-on üzerinden müşteriye
gönderir.
 Müşteri Supply-on üzerinden gelen 8D çalışmasını içerik ve metodik olarak inceler.

8D evaluation tool ile değerlendirmeyi yapar, eğer min %67 hedefini yakalarsa 8D
kapanışını yapar ve SAP kapanışını yapar. Ekip kutlanır ve sonrasında fes edilir.
 8D’nin %67 puanının altında kalması durumunda sistem üzerinden 8D red edilir.

8D Template

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

8D Template

Uploaded by

Copyright:

Available Formats

8D Template

Target Level Excellent Level

4 Flow Charts Supplier

5 Trend Charts Supplier

HATALI PARÇA FOTOĞRAFLARINI VE GEREKLİ TEKNİK DÖKÜMANI

Immediate actions ongoing in

Possible Risk Area!

Clean date (Start of containment)

 (Showing the possible Problem Occurrence and Non-Detection steps)

8  Estimates the occurrence probability

Total delivery : X pcs

9  Which Customers would be effected?

10  Effects on End Customer:

Information to; Blocking / Sorting Actions;

(if not necessary please explain why?)

2  Production : (All shifts, other production lines and plants)

(if not necessary please explain why?)

3  Other Bosch Plants :

(if not necessary please explain why?)

(if not necessary please explain why?)

Where Quantity Date Action Results

MFT Production area

1% - 70% Sorting Person Variable Criteria

80% Sorting Person Attribute Criteria

90% Sorting Person with Go / No Go

100% Sorting using Camera

100% Sorting using CMM

 Effectiveness of sorting method :

Effectiveness of containment actions must be documented. Not all containment actions

Target Level Excellent Level

Possible root cause

Human Environment Potential root cause was

WHY? WHY? WHY? WHY?

Target Level Excellent Level

2 Using problem solving methods / tools

4 Other documents updated

Possible root cause

Human Environment Potential root cause was

WHY? WHY? WHY? WHY?

4 -Potential extend (Customer)

8  Estimates the occurrence probability

Target Level Excellent Level

The Technical Root The Management Root

D5-D6 3 Persons responsible are designated and dates

Corrective Actions for Occurrence (TRC) D5/D6

Before Corrective Action

After Corrective Action

Corrective Actions for Occurrence (MRC) D5/D6

Before Corrective Action

After Corrective Action

Target Level Excellent Level

The Technical Root The Management Root

D5-D6 3 Persons responsible are designated and dates

Corrective Actions for Detection (TRC&MRC) D5/D6

Before Corrective Action

After Corrective Action

Corrective Actions for Detection (MRC) D5/D6

After Corrective Action

Target Level Excellent Level

D4 3 Systematic Training Form

Requirement for ‘Basic level’ D7

 FMEA Updated (Nr: ___)

 CP updated (if necessary) (Nr: ___)