Vous êtes sur la page 1sur 10

G8D REPORT

Problem Title:

Reference Number

Product/Process Information:

Date Opened:

Last Updated:

Organisation & Customer Tracker Information:

D Symptom(s):

D Emergency Response Action(s):

Verification / Validation:

Name

Target Date

% Effective

Date Checked

Name

Target Date

% Effective:

Date Checked

D Is an 8D investigation appropriate?
D1 Team:
Champion:
Team Leader:
Team Members:

Name

Role

D2 Problem Statement:

D2 Problem Description:

D3 Interim Containment Action(s):

Verification / Validation:

D4 Root Cause(s) and Escape Point(s):

Verification:

Date Checked

D5 Chosen Permanent Corrective Action(s):

Page 1 / 10

G8D REPORT
Problem Title:
Product/Process Information:

Reference Number

Date Opened:

Last Updated:

Organisation & Customer Tracker Information:

D6 Implemented Permanent Corrective Action(s):

Validation:

D7 Prevent Actions:

D8 Team and Individual Recognition:

Name

Target Date

% Effective

Date Checked

Name

Target Date

Date Closed:

Rev 2009Nov09

Page 2 / 10

IMAGES RELEVANT TO G8D


Investigation Ref.
Product/Process Information

0
0

Image 1

Image 2

Copy on this box JPEG, GIF PHOTOS

Copy on this box JPEG, GIF PHOTOS

Remarks

Remarks

Image 3

Image 4

Copy on this box JPEG, GIF PHOTOS

Copy on this box JPEG, GIF PHOTOS

Remarks

Remarks

Image 5

Image 6

Copy on this box JPEG, GIF PHOTOS

Copy on this box JPEG, GIF PHOTOS

Remarks

Remarks

Image 7

Image 8

Copy on this box JPEG, GIF PHOTOS

Copy on this box JPEG, GIF PHOTOS

Remarks

Remarks

Image 9

Image 10

Copy on this box JPEG, GIF PHOTOS

Copy on this box JPEG, GIF PHOTOS

Remarks

Created By : Tim Shattock

Remarks

IS - IS NOT Analysis
Problem Statement:

2B

IS
Who is affected by the problem?

Who

Who first observed the problem? (internal/external)


To whom was the problem reported?

What type of problem is it?


What has the problem?

What

What is happening?
Do we have physical evidence of the problem in our possession?

Why

Why is this a problem?


Is the process where the problem occurred stable?

Where

Where was the problem observed?


Where does the problem occur?

When was the problem first noticed?

How Often

How Much
When
/ Many

When has it been noticed since?

Quantity of problem?
How Much is the problem causing in dollars, people, & Time?

What is the trend (continuous, random, cyclical)?

How Often

Has the problem occurred previously? (If so attach previous PSWs & CIFs)

Home

IS NOT
Who is not affected by the problem?
Who did not find the problem?

What does not have the problem?


What could be happening but is not?
What could be the problem but is not?

Why is it not a problem?

Where could the problem be located but is not?


Where else could the problem be located but is not?

When could the problem have been noticed but was not?

How many could have the problem but dont?


How big could the problem be but is not?

What could the trend be but is not?

Ishikawa Diagram Fish Bone


Method

Machine

Man power
text - most
likely

text

Effect

text - problem

Environment

Material

Measurement

5 Whys Study
with Responsibility
Define symptom

A problem well defined is a problem half solved


Use this path for

Specific problem:
Why did we have the problem?
Problem not detected:
Why did the problem reach the Customer?
System failure:
Why did our system allow it to occur?

the specific
nonconformance
being investigated
(Define Problem)

WHY?

Therefore

Home
Cause & Effect
WHY?

Root
Causes

Therefore

Use this path to investigate


why the problem was not
detected
WHY?

WHY?

Therefore

Therefore

WHY?

Therefore

Problem definition

Therefore

WHY?

Use this path to investigate


the systemic root cause
(Quality System Failures)
WHY?

Therefore

Home
Cause & Effect

C
WHY?

Therefore

WHY?

Therefore

B
Next

Reported by

WHY?

Therefore

Break Point

Date

WHY?

Therefore

Home
Cause & Effect

30-Dec-99

Revision

Reference PN

Product / Process

30-Dec-99

#REF!

WHY?

Therefore

C
Next

Problem Resolution Complete

Lessons
Learned:
Team
Members:

/ / /

Communicate to Oetiker Date:

Process Change Break Point Date:

Implement System Change Date:

Date

ACTION PLAN
ID:
Issued Date:
Revion date:

INDEX

PA-1

30 December 1899
30 December 1899
30 December 1899
CORRECTIVE ACTION

Champion:
Team Leader:

TARGET DATE

0
Home

RESPONSIBLE

Pgina 10

%
PROG

CHECK EFFECTIVITY
DATE

METHOD

RESPONSIBLE

C-14