8D Top Sheet

8D Problem Solving
Reference Document &
8D Report Number
RUR Number Part Number (P/N): Model Number:
(Moog TIP CA Number)
(E.g.: RUR, NOE)

8D Issued By:
TIP CA Closed date: Part Revision: Moog Site:
(TIP CA Initiated Site)

8D Issue Date: Moog Part Number

8D Closed date: Part Description:
(TIP CA Initiated Date) (If any):

Note-1: This 8D form is equivalent to 9S (Nine Step) Problem Solving Methodology as defined in ARP9136.
Note-2: Refer to comments in each cell for instructions, guidance of the 8D process.
Note-3: Update all the relevant evidences (attachments - PDF Files etc) in the TipQA response.
Note-4: Refer to relevant Non-Conformance, Notice of Escape and Corrective Action managment requirements of SQR-1 Sections A4.15 and A5.3.
Note-5: This 8D form can be tailored when required without affecting the 8D process intent and additional fields, rows can be added based on the requirement.
Note-6: If any action point is "Not Applicable", specify the same in the remarks columns.

D0: Start Immediate Containment Actions:

Objective: To mitigate the impact of the problem, to protect Moog operations (i.e., stop the problem from getting worse), and verify that the situation does not deteriorate until the root cause and contributing causes are known.
Output: Immediate containment actions defined and implemented; Moog protected.

IMMEDIATE CONTAINMENT PLAN AND VERIFICATION Estimated Completion Date Actual Completion Date Responsible Owner Document Reference Status Remarks (if any)

D0.1. Review the problem statement and related documents to get better understanding/
Open
clarity of the problem.
D0.2. Issue Quality Alert and communicate to all concerned (Within Site and Design
center) as applicable.
D0.3. Immediate Containment: Quarantine the Parts at Shipping, Work-In-Progress, Stock
(as applicable) to protect Moog operations and plan for D3.
D0.4. Schedule meeting (at Quality clinic or Business units) to form cross functional team
and describe the problem for next steps of actions.
Immediate Containment Actions, Additional Information (if any):

D1: Build the Team:

Objective: To ensure that all process performers and applicable stakeholders and functions (e.g., organizations, departments, suppliers, customers) that may have an influence on the corrective action process and associated investigation are on the team.
Output: Cross-functional team of experts in place to support the corrective action process.

Team Name Responsibility Email Phone number Location Remarks (if any)

Accountable Business Unit

Manager:
8D Team Leader:

Cross Functional Working Team

Members:

Cross Functional Supporting

Team Members:

D2: Define Problem:

Objective: To understand the significance, impact, and size of the problem (i.e., depth and breadth of current conditions) and ensure the situation (i.e., problem) is accurately defined and thoroughly understood by the team and applicable stakeholders.
Output: Problem defined [e.g., which product, what process(s), actual defect or process deviation] and agreed upon.

Problem Statement:

As applicable, insert picture, drawing, sketch, or chart, Moog report to aid in understanding the problem (use low resolution picture to save memory space as needed):

Current Condition Is:

Required Condition Is:

Where used in next assembly?

Describe what happened?

Who and Where was the problem detected?

When was the problem detected?

How was the problem detected?

How many cases were detected (define units or events)?

Problem Statement Additional Information (if any):

Recurring issue- TIPCA /

Recurring issue? If Yes, Date of original
8D / other CA reference
YES / NO occurrence
numbers
Recurring Issue Additional Information:

D3: Complete and Optimize Containment Actions:

Objective: To ensure containment actions suitably address the problem statement and to verify that containment action is commensurate with the problem, implemented, and effective.
Output: Completed (implemented) and optimized containment actions (issue contained).

CONTAINMENT PLAN AND VERIFICATION Estimated Completion Date Actual Completion Date Responsible Owner Document Reference Status Remarks (if any)

D3.1. Trace the Process records, Production batch, Process stage, Operator, Work
Open
instructions and Inspection plans of affected part (as appropriate)

Supplier WIP

Receiving Area including Receiving Inspection

Stock and Issuance (Kits)

D3.2. Trace, maintain List and
securely quarantine the WIP - Fabrication Shop
affected parts until disposition
WIP - A&T

Final Inspection

Shipping

D3.3. Issue Stop & Release Order (or equivalent) and flow down to applicable stake holder

Perform Trace of Suspect Units

(list the units with serial numbers).
Note: Provide brief explanation :
a. Why they are suspect and how it will be affected.
b. If they are not suspect and not affected justify.
D3.4. Assess Potential Impact
to Shipped Units and
Communicate to Moog
Issue AS9131D (as required)

Issue Notice of Escape (as required)

Complete disposition and release of quarantined parts

D3.5. Engineering Disposition Approve and release the Rework /Repair/ Retest work
and Correction instructions and inspection plan
Update Receiving Inspection Plan for supplied parts as
required

Identify for other models, part numbers, work center,

D3.6. Look / Read Across.
Business unit etc. impacted.
Containment Action Additional Information (if any)

Specify the Date and Batch number of the shipments made to Moog after implementation of the containment action(s):

D4: Identify Root Cause(s):

Objective: To identify, through structured root cause analysis, the root cause for the undesirable condition, situation, nonconformity, or failure, including the reason it was not detected.
Output: Root cause(s) of the problem identified.

List Quality Tools Used Root Cause Verification method

Root Causes Root Cause description
( e.g. Fish bone, 5WHY) ( E.g. Simulation, samples, design analysis etc.)

This document does not contain Technical Data or Technology as defined in the ITAR Part 120.10 or EAR Part 772 Form 810-500 20200207
8D Top Sheet

8D Problem Solving
Reference Document &
8D Report Number
RUR Number Part Number (P/N): Model Number:
(Moog TIP CA Number)
(E.g.: RUR, NOE)

8D Issued By:
TIP CA Closed date: Part Revision: Moog Site:
(TIP CA Initiated Site)

8D Issue Date: Moog Part Number

8D Closed date: Part Description:
(TIP CA Initiated Date) (If any):
Root Cause - Occurrences

Root Cause - 1

Root Cause - 2

Root Cause - 3

Root Cause - Escape / Non-detection

Root Cause - 1

Root Cause - 2

Root Cause - 3

Root Cause Additional Information (if any):

This document does not contain Technical Data or Technology as defined in the ITAR Part 120.10 or EAR Part 772 Form 810-500 20200207
8D Top Sheet

8D Problem Solving
Reference Document &
8D Report Number
RUR Number Part Number (P/N): Model Number:
(Moog TIP CA Number)
(E.g.: RUR, NOE)

8D Issued By:
TIP CA Closed date: Part Revision: Moog Site:
(TIP CA Initiated Site)

8D Issue Date: Moog Part Number

8D Closed date: Part Description:
(TIP CA Initiated Date) (If any):

D5: Define and Select Immediate and Permanent Corrective Actions:

Objective: To define, prioritize, and select Immediate and Permanent corrective actions that should be implemented to address the root causes and permanently prevent the undesirable condition, situation, nonconformity, or failure from recurring.
Output: Immediate and Permanent corrective actions defined.

Responsible Documents Reference

Immediate Corrective Action: Action Item Estimated Completion Date Actual Completion Date Status Remarks (if any)
Owner (e.g. Parts list, WINs)

D5.1. Plan for Replacement

Open
Parts Delivered to Moog

D5.2. Immediate corrective action - Occurrences

D5.2.1 For Root Cause - 1 Open

D5.2.2 For Root Cause - 2

D5.2.3 For Root Cause - 3

D5.3. Immediate corrective action - Escape / Non-Detection

D5.3.1. For Root Cause - 1 Open

D5.3.2. For Root Cause - 2

D5.3.3. For Root Cause - 3

Immediate Corrective Action Additional Information (if any):

Responsible Documents Reference

Permanent Corrective Action: Action Item Estimated Completion Date Actual Completion Date Status Remarks (if any)
Owner (e.g. Parts list, WINs)

D5.4. Permanent corrective action - Occurrences

D5.4.1 For Root Cause - 1 Open

D5.4.2 For Root Cause - 2

D5.4.3 For Root Cause - 3

D5.5. Permanent corrective action - Escape / Non-Detection

D5.5.1. For Root Cause - 1 Open

D5.5.2. For Root Cause - 2

D5.5.3. For Root Cause - 3

Permanent Corrective Action Additional Information (if any):

D6: Implement Permanent Corrective Action and Check Effectiveness: Objective: To ensure all selected corrective actions are implemented (as defined), and to assess their effectiveness in preventing the undesirable condition from recurring and/or in detecting it
sufficiently upstream in the process. Output: Permanent corrective action implemented and efficiency demonstrated (i.e., problem prevented from recurring).

Responsible Documents Reference

REVIEW THE FOLLOWING DOCUMENTS / SYSTEMS Estimated Completion Date Actual Completion Date Status Remarks (if any)
Owner ( e.g. audit reports)

D6.1. Audit that corrective actions are in place and functioning Open

D6.2. Monitor / Review Test Data / NC's / to validate defect is not recurring

D6.3. Other (define)

Corrective Action Validation Additional Information (if any):

Specify the Date (date of embodiment ) and Batch number of the shipments made to Moog after implementation of Corrective Action(s):

D7: Standardize and Transfer the Knowledge Across Business: Objective: To document analysis, results, and changes to capture and share learning with applicable stakeholders to prevent similar undesirable condition, situation, nonconformity, or failure occurring on other
products, production lines, factories, or suppliers. Output: Preventive actions implemented where similar problems could potentially occur (system improved).

Documents Reference
Preventive Actions Estimated Completion Date Actual Completion Date Responsible Owner Status Remarks (if any)
(e.g. Parts list, WINs)

D7.1. List all parts and processes for look across and horizontal deployment of actions (as
Open
applicable).
D7.2. Communicate Corrective Action and Changes implemented
(E.g. Refer Quality Bulletin tab).
D7.3. Other Actions (if any):

Preventive Actions - Document Updates Estimated Completion Date Actual Completion Date Responsible Owner Documents Reference # Status Remarks (if any)

D7.4. Process Flow Chart Open

D7.5. Process Change Request

D7.6. Process FMEA

D7.7. Process Control Plan

D7.8. Work Instructions

D7.9. Inspection Standard - Receiving

D7.10. Inspection Standard - Shipping

D7.11. Engineering / Drawing Change Request

D7.12. Design FMEA

D7.13. PPAP Resubmission

D7.14. Relevant QMS practices

D7.15. Others (define)

Preventive Action Additional Information (if any):

D8: Team Recognition and Closure:

Objective: To ensure all team members and stakeholders are aware of the successful implementation of all corrective action, to confirm that the activity is closed, and to recognize and reward their work and accomplishment.
Output: Synthesis of actions distributed and recorded; team acknowledged and RCCA process closed.

REVIEW THE FOLLOWING DOCUMENTS / SYSTEMS / FEEDBACK Estimated Completion Date Actual Completion Date Responsible Owner Documents Reference # Status Remarks (if any)

This document does not contain Technical Data or Technology as defined in the ITAR Part 120.10 or EAR Part 772 Form 810-500 20200207
8D Top Sheet

8D Problem Solving
Reference Document &
8D Report Number
RUR Number Part Number (P/N): Model Number:
(Moog TIP CA Number)
(E.g.: RUR, NOE)

8D Issued By:
TIP CA Closed date: Part Revision: Moog Site:
(TIP CA Initiated Site)

8D Issue Date: Moog Part Number

8D Closed date: Part Description:
(TIP CA Initiated Date) (If any):

D8.1. Check effectiveness of each action has been demonstrated Open

D8.2. Check lessons learned been communicated to all the stake holders

D8.3. Has the customer(s) provided acknowledgement that the issue is resolved

D8.4. All documents from this 8D reconciled and attached in TIP-QA?

D8.5. The team is formally updated on the success and recognized

Team Recognition Additional Information (if any):

8D Validated by Owner / Team 8D Closed by Site Quality

8D Closed Date:
Leader: Manager

This document does not contain Technical Data or Technology as defined in the ITAR Part 120.10 or EAR Part 772 Form 810-500 20200207