DEMBLA 8D-report No of pages: 1 Date: 24.01.
2019
Issued by:
Telephone:
Fax:
Supplier number: 446200 E-mail
Factory:
Please send acknowledgment of receipt of the claim to Dembla within 24 hours!
Reference
Notification number Creation date
Our material number Material short text Spacing bush 9mm
Your material number Complaint quantity 1 PC
Purchase order: Reference quantity 1 PC
1. Team assembled - Establish a small group of people with the process/product knowledge, allocated time, authority and skill in the
requirred techncal disciplins to solve the problem and implement corrective actions.
Department Name( Team leader first) Position (job)
2. Problem description - Provide the starting point for the solving of the problem. Use terms understood by all, and try to analyse all
aspect of the problem by using relevant analysis (WH-analysis).
Parallelism measures 0.92mm instead of 0.02 mm
3. Implement containment actions - Temporary actions for limiting Planned finish date: Implemented on (date):
damange to contain the problem and "fix" until permanent correction is in
place (Attach validation that the action taken works) 28.01.2019
Containment action must be completed and reported to Dembla within 48 hours after receipt of the
claim.
4. Root cause analysis - Why occurred, why not detected? Analyze for root cause of the problem by Implemented on (date):
brainstorming ( attach) making and cause and effect diagram( attach) and a Why analysis(attach). Identify
and verify the escape point. (Escape Point is where in the process the defect should have been first
detected but was not.)
5. Chosen permanent corrective actions against occurence and non- Planned finish date: Implemented on (date):
detection - Select the best Permanent Corrective Action (PCA) for
removal of the root cause and for elimination of escape points. Document
and verify the PCA and attach. 07.02.2019
Root cause identification and action plan for permanent corrective actions must be completed and
sent to Dembla within 2 weeks.
6. Verification of permanent Corrective action - Implement and monitor the success and effectiveness Implemented on (date):
of the improvements and long term corrective actions. Detect any deviations or side effect and document
these and attach.
Grundfos Revised 20. June 2011 Page 1 of 9
7. Actions to prevent recurrence - Determine what improvements in systems and processes would Implemented on (date):
prevent problem from recurring. Ensure that corrective actions remain in place and stay succesful.
Remarks:
Consequence of other products and processes?
Yes No
Product FMEA updated?
Yes No
Process FMEA updated?
Yes No
Control plans updated?
Yes No
Work flows. Instructions updated?
Yes No
Processing documents adapted?
Yes No
Management system manual updated?
Yes No
Inspection work instructions?
Yes No
Training plan adapted?
Yes No
Training accomplished?
Yes No
Other:
Yes No
8. Closing report Planned finish date: Closed on (date):
21.02.2019
Problem solved: YES
Yes NONo
Justification of "no"
Team leader: Construction: Quality-Management:
Date, signature Date, signature Date, signature
The report must be send to Dembla according to agreement.
Approved by Dembla
Date, signature
Grundfos Revised 20. June 2011 Page 2 of 9
IS IS NOT
Who is affected by the problem? Who is not affected by the problem?
Who first observed the problem? Who did not find the problem?
(internal/external)
To whom was the problem reported?
Who
What type of problem is it? What does not have the problem?
What has the problem? What could be happening but is not?
What is happening? What could be the problem but is not?
Do we have physical evidence of the problem
What
in our possession?
Why is this a problem? Why is it not a problem?
Is the process where the problem occurred
stable?
Why
Where was the problem observed? Where could the problem be located but is not?
Where
Where does the problem occur? Where else could the problem be located but is
not?
When was the problem first noticed? When could the problem have been noticed but
was not?
When has it been noticed since?
When
Quantity of problem? How many could have the problem but don’t?
How Much/
How Much is the problem causing in dollars, How big could the problem be but is not?
people, & Time?
Many
What is the trend (continuous, random, What could the trend be but is not?
cyclical)?
How Often
Has the problem occurred previously? (If so
attach previous PSWs & CIFs)
Brainstorm
How made? Why did it get out?
People Materials/Info Machine Problem (effect) People Materials/Info Machine
Method Environment Measurement Method Environment Measurement
Note on Diagram(s) circle the most likely contributors (3 max) from each side.
Why Analysis
Ask – Why did this happen?
Ask – Why did this happen?
Ask – Why did this happen?
Ask – Why did this happen?
Ask – Why did this happen?
