KZK Solutions blog - KZK Solutions /kzoli62/

KZK Solutions
Go to content

Fill 8D reports (Part 2)

KZK Solutions /kzoli62/
Published by Z. Kovács in Quality · 8 May 2021
Tags: QA8D
In the last part of my series, we have come to the definition of D4 - Possible actions.

Today I will continue to describe D5 - Planned actions.

D5 - Planned actions

Here, we document possible corrective actions related to the technical and systemic trigger analyzed.

Actions must be assigned to each of the reasons listed under D4.

Where possible, several options should be identified for each cause and the effectiveness of the measure should be assessed.

Make sure you evaluate the possible side effects.

As with all items, the related documents should be listed and attached. Attaching photo and video documents is a good thing.

Attention !!!

The maximum score is given only if a decision matrix is ​​attached to this point.

D5.1 – Actions for technical reasons
It includes:

  • Introductory text (For the technical reasons for this, we can do the following.)
  • List of actions - Action must be taken for all the reasons listed in D4.1. If a action is not feasible, e.g. design change should be listed, but specifying that this is not possible.
  • Possible unwanted side effects. - If not, it must also be given, if any, the reasons must be given.
  • Efficiency estimation. - It must be given as a percentage, which must be justified. (Qualifiers prefer figures over general statements.)
  • Verification - The certificate usually includes sorting and sample production. You must give the date and the result.
  • Documentations:

Obligatory:

  • PB xxxxxxxxx_yyyyyyyyyy.pdf    – Presentation, indicating which page contains the following information:
         - Action plan
  • Sorting PB xxxxxxxxx hh-nn.pdf  – Selection report

It's not neccessary:

  • AA PB xxxxxxxxx.pdf  – Work instructions only if they have been changed.
  • Responsible:
    • Name - Function (CQE)

D5.2 – Actions for causes of system formation

It includes:

  • Introductory text (For the causes of the formation system, we can do the following.)
  • List of actions - Action must be taken for all the reasons listed in D4.2. If a action is not feasible, it should be listed, but stating that this is not possible.
  • Possible unwanted side effects. - If not, it must also be given, if any, the reasons must be given.
  • Efficiency estimation. - It must be given as a percentage, which must be justified. (Qualifiers prefer figures over general statements.)
  • Verification - The certificate usually includes sorting and sample production. You must give the date and the result.
  • Documentations:

Obligatory:

  • PB xxxxxxxxx_yyyyyyyyyy.pdf    – Presentation, indicating which page contains the following information:
         - Action plan
  • Sorting PB xxxxxxxxx hh-nn.pdf  – Selection report

It's not neccessary:

  • AA PB xxxxxxxxx.pdf  – Work instructions only if they have been changed.
  • Responsible:

    • Name - Function (CQE)

D5.3 – Actions for technical reasons of undisclosed

It includes:

  • Introductory text (For technical reasons of undiscovery, the following can be done.)
  • List of actions - Action must be taken for all the reasons listed in D4.3. If a action is not feasible, it should be listed, but stating that this is not possible.
  • Possible unwanted side effects. - If not, it must also be given, if any, the reasons must be given.
  • Efficiency estimation. - It must be given as a percentage, which must be justified.
  • Verification / verification. - The certificate usually includes sorting and sample production. You must give the date and the result. (Qualifiers prefer figures over general statements.)
  • Documentations:

Obligatory:

  • PB xxxxxxxxx_yyyyyyyyyy.pdf    – Presentation, indicating which page contains the following information:
         - Action plan
  • Sorting PB xxxxxxxxx hh-nn.pdf  – Selection report

It's not neccessary:

  • AA xxxxxxxxx.pdf  –Work instructions if changed.
  • Responsible:

    • Name - Function (CQE)

D5.4 – Actions for reasons of undisclosed system

It includes:

  • Introductory text (For the reasons of the undiscovered system, we can do the following.)
  • List of actions - All the reasons listed in D4.4 must be taken. If a action is not feasible, e.g. design change should be listed, but specifying that this is not possible.
  • Possible unwanted side effects. - If not, it must also be given, if any, the reasons must be given.
  • Efficiency estimation. - It must be given as a percentage, which must be justified.
  • Verification  - The certificate usually includes sorting and sample production. You must give the date and the result. (Qualifiers prefer figures over general statements.)
  • Documentations:

Obligatory:

  • PB xxxxxxxxx_yyyyyyyyyy.pdf    – Presentation, indicating which page contains the following information:
         - Action plan
  • Sorting PB xxxxxxxxx hh-nn.pdf  – Selection report

It's not neccessary:

  • FMEA.pdf(.jpg)  – PFMEA only if changed.
  • Responsible:

    • Name - Function (CQE)

Introduced actions

This chapter should list the actions that have been introduced at each of the points in D5.

If we do not implement all the plans, we need to justify which and why.

This point, as well as D4 and D5, are discussed separately in:

  • Cause / origin

    • Technical
    • System

  • Undiscovered

    • Technical
    • System

points. In any case, these are supplemented by a point 5, withdrawing the immediate actions.
This is forgotten by many and many times, which is why the evaluators deduct points !!!

D6.1 – Actions for technical reasons

It includes:

  • Introductory text (For the technical reasons for the creation, the following has been introduced.)
  • List of actions - All actions listed in D5.1 must be provided. If a action has not been implemented, it should be listed, but specifying why it was not implemented.
  • Validation / efficiency - Validation usually involves sorting and sample production. You must give the date and the result. (Qualifiers prefer figures over general statements.) Efficiency can be demonstrated if the error did not recur.
  • Documentations:

    • PB xxxxxxxxx_yyyyyyyyyy.pdf    – Presentation
    • Sorting PB xxxxxxxxx hh-nn.pdf  – Selection report

  • Responsible:

    • Name - Function (CQE)

D6.2 – Actions for causes of system formation

It includes:

  • Introductory text (For the reasons of the origin system, the following has been introduced.)
  • List of actions - All actions listed in D5.2 must be provided. If a action has not been implemented, it should be listed, but stating why it has not been implemented.
  • Validation / efficiency - Validation usually involves sorting and sample production. You must give the date and the result. (Qualifiers prefer figures over general statements.) Efficiency can be demonstrated if the error did not recur.
  • Documentations:

    • PB xxxxxxxxx_yyyyyyyyyy.pdf    – Presentation
    • Sorting PB xxxxxxxxx hh-nn.pdf  – Selection report

  • Responsible:

    • Name - Function (CQE)

D6.3 – Actions for technical reasons of undisclosed

It includes:

  • Introductory text (For technical reasons of undiscovery, the following has been introduced.)
  • List of actions - All actions listed in D5.3 must be provided. If a action has not been implemented, it should be listed, but stating why it has not been implemented.
  • Validation / efficiency - Validation usually involves sorting and sample production. You must give the date and the result. (Qualifiers prefer figures over general statements.) Efficiency can be demonstrated if the error did not recur.
  • Documentations:

    • PB xxxxxxxxx_yyyyyyyyyy.pdf    – Presentation
    • Sorting PB xxxxxxxxx hh-nn.pdf  – Selection report

  • Responsible:

    • Name - Function (CQE)

D6.4 – Actions for reasons of undisclosed system

It includes:

  • Introductory text (For the reasons of the undisclosed system, the following has been introduced.)
  • List of actions - All actions listed in D5.4 must be provided. If a action has not been implemented, it should be listed, but stating why it has not been implemented.
  • Validation / efficiency - Validation usually involves sorting and sample production. You must give the date and the result. (Qualifiers prefer figures over general statements.) Efficiency can be demonstrated if the error did not recur.
  • Documentations:

    • PB xxxxxxxxx_yyyyyyyyyy.pdf    – Presentation
    • Sorting PB xxxxxxxxx hh-nn.pdf  – Selection report

  • Responsible:

    • Name - Function (CQE)

D6.5 – Withdrawal of immediate actions

It includes:

  • The measures do not need to be revoked at the manufacturer, as the quality warning (QA) is only valid for three months.
  • Withdrawal is not necessary for BMW either, as no action has been initiated there. (If there was a selection, your details must be provided and the relevant documentation attached.)

Preventive actions

  • PFMEA and work instructions were checked
  • Lessons Learned

    • A lesson learned discussion was held on the following points:

      • Can other products and processes benefit from the experience?
      • Can the changes be applied to other lines?
      • Can the changes be implemented in other products?
      • Checked and modified documents must be uploaded to the system

  • FMEA.pdf(.jpg)   – Process FMEA
  • AA xxxxxxxxx.pdf  – Procedure
  • LL_ PB xxxxxxxxx.pdf  – Lessons Learned

Closing discussion

Includes:

  • The full 8D report was approved by the sponsor (Champion) and the team leader! Team members were exempted from the 8D project. Thanks to the team.
  • The 8D report was reviewed and approved by the neutral evaluator according to the evaluation matrix.
  • See also: D7.2 Lessons Learned


There are no reviews yet.
0
0
0
0
0
Copyright KZK Solutions © 2010 - 2021 All rights reserved
Back to content