2014-07-09

8D report template

Version, status 2.0 Approved

Date 2014-07-09

Creator Tomi Hardén

Owner Tomi Hardén

Function NET Quality/GOPS

Approver Olli Hossi

Doc location GOPS 8D Reporting Library

Change History

Version Status Date Handled by

2.0 Approved 7/9/2014 Tomi Hardén

 This material, including documentation
and any related computer programs, is protected by copyright con
All rights are reserved. Copying, including reproducing, storing, a
translating, any or all of this material requires the prior written co
This material also contains confidential information, which may n
others without the prior written consent of Nokia.

Comments

Contents reviewed and updated. Nokia Excel template taken into use.
 © Nokia 2014

ng documentation
uter programs, is protected by copyright controlled by Nokia.
. Copying, including reproducing, storing, adapting or
of this material requires the prior written consent of Nokia.
tains confidential information, which may not be disclosed to
or written consent of Nokia.
 INSTRUCTIONS
PURPOSE
The purpose of this workbook is to help the users of the 8 disciplines (8D) problem solving method to carry out the 8 steps systematically,
thoroughly and with high quality.

You can delete sheets/contents of this workbook you don't need!

TARGET GROUPS
The main target groups for this 8D excel workbook are those GOPS emplooyees who are using the 8D method to solve problems or evaluate
the 8D reports created by others. These include, but are not limited to, employees using the COMPL tool, colleagues using the Material
Corrective Action Reporting (MCAR) tool and colleagues working with the Quality Issue Resolution System (QIRS) tool. The employees
who aren't familiar with the 8D methodology can use the 8D report template to practice to go through the 8 steps in sequence alone or with a
team. These colleagues will find the additional resources on the other worsheets especially useful.For the more experienced 8D users who are
working on open cases the 8D report template may alone be sufficient.

CONTENTS
Sheet 2. When to use 8D: A quick overview of the events/situations when to use 8D
Sheet 3. 8D report template: Template for problem solving, collaboration and communication using the 8D methodology
Sheet 4. 8D tool library: Excel tools for problem visualization, root cause analysis, planning, execution, risk mgnt, etc.
Sheet 5. 8D attachment library: Placeholder for your attachements such as pictures, etc.
Sheet 6. Additional Info: GOPS 8D support contacts, 8D report self evaluation questions and links

VERSION INFORMATION
2.0 Tomi Hardén 09-07-2014
Note: protect/unproctect worksheet password is 8D
WHEN TO USE 8D?

C&E = Cause & Effect

 8D REPORT
CASE IDENTIFICATION DATES (d.m.yy) TITLE METADATA
Solver unit <unit> Start 12/2/16 Product Mismtach in Same FG One lot(8 Pcs) have impated
COMPL ID Intrnal LE 30/02/16 pallet ( FRCG 1 pc Placed in during OBA Inspection.
FHFB FG Pallet)
Other ref <ref> Closed
Time -30295
BACKGROUND BUSINESS CASE (financial benefits and costs)
On 11th Feb 9:55 Pm, FRCG and FHFB production were running in corona line2, Packing If the wrong FG shipped to customer this will lead as customer complaint a
person chosen wrong pallet that FHFB, instead of FRCG . occur as penalty charges for replacement

1D ESTABLISH TEAM 2D DESCRIBE PROBLEM

Role Initials Email Current situation
Sponsor Pitty Sudarshan sudarshan.pitty@nsn.com Defect: Product Mismatch
Model: FRCG
SFC No: K9160633063
Date:11/02/2016
Shift:B
Time:09:50 PM
Operator Name:Ramesh.G
Coach Javed javed.3.khan@nokia.com Failure Histroy:FRCG and FHFB FG Boxes are looks similar ( Label conte
Dimesion, Pallet Qty). During run of FHFB operator chose wrong FG palle
and offered the OBA lot.

Leader Sellam Saravanakumar Saravanakumar.sellam@nokia.com Desired situation

Expert Parthiban.T Parthiban.t@nokia.com Each FG pallet should have same model products only. NO Mix-up are all
Expert Vinod Chander vinod.c.s@nsn.com
Expert Jayanarayana Singh singh.jayanarayana@nokia.com Gap
Additional relevant problem related details 2 Products are mixed with one FG pallet.
Customer Various
Delivery <affected delivery no>
Facility <affected facility, site, etc.> Action
Product FRCG Eliminate product mismatch case
Process Packing
Service
System/tool
Other <affected service (provider); supplier, etc.>
3D IMPLEMENT TEMPORARY SOLUTION
Who? What? When?
RFM TL and Quality Hold the FG pallet for Rescreening 2/13/2016
Tech
RFM TL and Quality Cross verification of all rest of 4 Pallets which is waiting for OBA Inspaction 2/13/2016
Tech

Approval needed? If yes, date received? Approver email

NA <d.m.yy> <first.last@nsn.com>
4D FIND ROOT CAUSE

FHFB

FHFB 1 FG Pallet- 2
Models
FRCG ( FHFB-03, FRCG-
01)
FHFB

<root cause described clearly and precisely>

ENVIROINMENT MACHINE MATERIAL
<root cause described clearly and precisely>
ENVIROINMENT MACHINE MATERIAL
Shortage of FG pallet FG Carton boxes are same
Strapping machine or DImension
Vaccum lifter are
breakdown Packing label dimesion
and fonts sizes are same
Product
Mismatch
Low competant Person Last hour overload
Wrong FG pallet selection during offloading Same dimesnion pallet
from conveyor used for all FG units.

D:\userdata\pat\
MAN METHOD Desktop\Why Why.

Challenges:
Volume requirement will vary day to day basis, Creating of standard pallet location for each model is difficuilt.
All corona Line-2 FG Carton boxes are same dimension as well packing label also common for all models.( FRCG,
FHFB,FRBG,FRHG,FHFB,FHCG)

5D DEVELOP PERMANENT SOLUTION

Who? What?
Parthiban.T Physical verification of FG units to prevent mismatch
Parthiban.T Systamatic measure to detect model mismatch cases before offering OBA Inspction
Parthiban.T Buffer FG pallets keep ready to use
Approval needed? If yes, date received? Approver email
No <d.m.yy> <first.last@nsn.com>
6D IMPLEMENT PERMANENT SOLUTION
Who? What? When?
Parthiban.T/Prakash Traveller card method to ensure no mismatch products in each FG pallet 2/13/2016
Traveller card help s as check sheet to
identify any product mismatch

THis also help to check and prevent 8

Model other OBA defects which is possible at
verification
packing stage.
Double verification is used to ensure
100% Complaince of check sheet usage

Parthiban.T/Vagale Individual pallet check operation at completing of each pallet 2/21/2016

SFC Pallet check

option in ONline
portal

Shift TL Maintain buffer of FG pallets are ready 2/29/2016

Parthiban/Shift TL Focus on hourly output ( Mainly on first hour) to avoid last hour over load at packing stages 3/1/2016

Risks identified and mitigated? <y/n>

7D PREVENT RECURRENCE
Area What? Who? When?
Environment <action> <first last> dd.mm.yy
Machine <action> <first last> dd.mm.yy
Manpower Current Total Mix Model Lines in Assembly -04 Parthiban 2/29/2016
Traveller card usage started for all mix model line packing resources.

Material <action> <first last> dd.mm.yy

Measure Pallet check option horizontally deployed in All packing stations Parthiban 2/29/2016

When Using pallet check

option,
If any product mismatch
this will show FAIL Status,
and No.of Models as 2
If no Mismatch this will
show Pass Status, No of
models as 1.

Method <action> <first last> dd.mm.yy

8D EVALUATE OUTCOME If yes, date
Permanent solution satisfies customer and team? Y 16.3.16
Team's efforts have been recognized? Y 16.3.16
Lessons learned recorded and shared? Y 16.3.16
METADATA SEVERITY
ne lot(8 Pcs) have impated High
uring OBA Inspection.

nefits and costs)

mer this will lead as customer complaint and may
cement

D:\userdata\pat\
Desktop\Why Why.
FG Boxes are looks similar ( Label content, Box
n of FHFB operator chose wrong FG pallet( FRCG)

model products only. NO Mix-up are allowed.

G pallet.

Status? Verified?
Closed Yes

Closed Yes

pprover email
first.last@nsn.com>
Verified root cause?

Yes
 Yes

Yes

When?
2/13/2016
2/20/2016
2/28/2016
pprover email
first.last@nsn.com>

Status? Verified?
Closed Yes

Closed Yes

Closed Yes

Closed Yes

Status? Verified?
<open/closed> <y/n>
<open/closed> <y/n>
Closed Yes

<open/closed> <y/n>
Closed QA - 2016 -036

D:\userdata\
kumaren\Desktop\

<open/closed> <y/n>
 8D REPORT TOOL LIBRARY
1D ESTABLISH TEAM

CM200 stakeholder
analysis template.xl

2D DESCRIBE PROBLEM

5 whys.xlsx Control chart.xlsx Fishbone Flow chart.xlsm Histogram.xlsx Pareto chart.xlsx Scatter
diagram.xlsx diagram.xlsx

Please visit http://asq.org/learn-about-quality/tools-templates.html in case of problems!

3D IMPLEMENT TEMPORARY SOLUTION

Use same tools as in the step 5D for temporary solution planning and implementation if needed.

4D FIND ROOT CAUSE

Use same tool as in the step 2D descibe problem for root cause analysis if needed.

5D DEVELOP PERMANENT SOLUTION

12 month FMEA.xlsx GANTT chart.xlsx

execution planning.

6D IMPLEMENT PERMANENT SOLUTION

Use the same tools as in the step 5D develop permanent solution for permanent solution implementation if needed.

7D PREVENT RECURRENCE
Use the same tools as in the step 2D describe the problem and 5 D develop permanent solution to prevent recurrence if needed.

8D EVALUATE OUTCOME

MA920 lessons
learned.xlsx
 8D REPORT ATTACHMENT LIBRARY
1D ESTABLISH TEAM
<embed relevant attachments>

2D DESCRIBE PROBLEM
<embed relevant attachments>

3D IMPLEMENT TEMPORARY SOLUTION

<embed relevant attachments>

4D FIND ROOT CAUSE

<embed relevant attachments>

5 DEVELOP PERMANENT SOLUTION

<embed relevant attachments>

6D IMPLEMENT PERMANENT SOLUTION

<embed relevant attachments>

7D PREVENT RECURRENCE
<embed relevant attachments>

8D EVALUATE OUTCOME
<embed relevant attachments>
 ADDITIONAL INFORMATION
8D SUPPORT CONTACTS
GPR Peter Wanner
GOPS Tomi Hardén
MO Sami Peltonen
OPM Pekka Kivioja
SCM Susan Ehren
8D REPORT SELF-EVALUATION : IN THE 8D REPORT THERE IS EVIDENCE THAT
Step 1D 1. Project team, team leader (and sponsor, if required) have been nominated and recorded into the 8D report.
2. Roles and responsibilities of each member of the team are clear.
Step 2D 3. The problem has been analyzed and described clearly, precisely and is understandable.
4. The problem was clearly visualized (e.g use of graphs, photos etc.): We know now where, when or how often the problem occurs.
Step 3D 5. Temporary solutions have been identified and clearly described to contain the present situation.
6. Responsibilities and ownership is clear for all temporary solutions.
7. Proof of verification of containment solutions is recorded.
Step 4D 8. The causes found were based on the description of the problem in step 2D.
9. Root causes have been described in a very clear and understandable manner.
10. The team’s root cause is really a cause and not a symptom of the problem.
Step 5D 11. The solutions are clearly described and designed to remove the identified root cause(s).
12. Costs/benefits of solving the problem have been estimated (if applicable).
Step 6D 13. Team’s action plan clearly states who does what by when.
14. Team has identified the risks of their action plan and have back-up plans in place if the risk(s) occur (if applicable).
15. Proof of verification of permanent solutions is recorded.
Step 7D 16. Any weak points in current systems and/or processes that allowed the root causes to emerge have been identified.
17. Appropriate action to eliminate these weak points has been taken (e.g. modify management and control systems, procedures and general practices).
18. Planning, execution and monitoring of implementation of prevention of a recurrence of the identified problem has been carried out and recorded.
Step 8D 19. The permanent solution(s) satisfies the customer and the team.
20. Team has carried out a lessons learned exercise and has shared what it has learnt to the organization.
21. Costs/benefits of solving the problem have been proven (if applicable).
8D LINKS
8 disciplines problem solving (Wikipedia)
8D homepage
8D trainings in the GOPS Purple Level Recognition Curriculum
COMPL homepage
GOPS 8D reporting library
GOPS continuous improvement
MCAR training materials
QIRS training materials
TION

en the problem occurs.

plicable).

ntified.
stems, procedures and general practices).
em has been carried out and recorded.