8D教材中英文版（希望能多多交流）

做SQE差不多半年了，实际接触到很多8D报告，全是供应商针对物料在我司制程上出现异常所做的回复。而且也要求用8D做改善分析。
但自己从来没有写过，通过了解掌握了一些基本知识。
发出来给大家分亨一下，希望能多多交流。
8D只是回复给客户的一个形式吗？
怎么样才能去评估供应商所写的8D是否有做到位呢？
是不是看供应商后续的来料品质？

请大家多多指教。

Customer Incident Analysis Procedure

1. Use the team approach矫正措施团队

1.1 Name the champion (will be responsible for completing CAR).
填写负责此事件主要领队名字 (此人将负责完成CAR ) 。
1.2 The team met prior to the CAR being written and signed.
此事件成员有哪些,填写他们名字。
1.3 The team brainstormed the CAR response.
这队有人提供脑力激荡或意见者。

1. Problem description问题描述

2.1 State all known data given by customer. 所有知道的资料讯息从客户端得知。
Customer name (IBM, UK) 顾客名字 ( 如 : IBM, UK )
Model (MS-6188 1.0A) 模型 : ( MS - XXXX 1.0 一 )
Phenomenon (Failed on IAT test program) 现象 : (如XXX测验程序方面失败或XXX组装不良)
Time – 04/10/2001发生时间 : XX年XX点XX分
Station – First burn-in, Post test, and so on. 发生站别- 修补站, 测试站…..并且依此类推。
Test configuration – Equipment brand, model, speed ……
2.2 State the product affected. 状态。
- Customer bar code ( xxxxxxxxxxxxx ) 客户端的条形码 ( xxxxxxxxxxxxx )
- Control code (04) 客户端控管代码 ( XX )
2.3 State if there has been multiple occurrences of problem. 是否还有其它问题发生(多重不良状态)。
2.4 State the specification requirements. (2mm – 5mm) 实际状态规格需要为多少。
2.5 What is the deviation. (measurement 6mm which is out of spec.) 问题发生偏差为多少。

1. Containment action隔离动作 / 立即措施

3.1 Define the suspect product.
定义嫌疑批产品。
Do some experiment if necessary 如有必要需做一些实验找出嫌疑批
3.2 All stock locations purged/sequestered of suspect stock.
嫌疑批所有库存的位置需做隔离。如:
- Supplier site. 协力厂商场内储存地点
- Working in process. (include hub) 在制程当中(包含厂外仓库)
- Ship-out. 出货旅途运送当中。
3.3 Suspect product is identified by customer bar code.
从顾客条形码识别出嫌疑批产品。( 号码 : 起 ~ 迄 )
3.4 The containment action can detect the suspect product.
从这隔离动作能够探查这个嫌疑批产品。
3.5 Inspection/Analysis results list below items.
检查或分析报表需要有以下产生下列结果。
- #Sorted. 分类(良品与不良品)
- #Found.
- % Defective. 不良率 %是多少 .
3.5 Containment actions are validated as effective.
证明出隔离做法实施是有效。
3.6 The containment will not introduce other issues/defects.
这项隔离做法将不会引起其它缺陷问题发生。

1. Root cause analysis and identification原因分析

4.1 Fishbone analysis completed (if applicable). 用鱼骨图分析 。
4.2 All pertinent data been provided.
所有相关资料需被各相关人员深思熟虑过了
4.3 If issue is a "repeat", has deficiency of previous corrective action been identified?
如果问题被" 重复"发生 , 那表示以前的矫正行动的不足吗?
4.4 Process of continuous to ask why until true root cause is identified.
需要不断的过程问5次为什么,直到真实根源原因被确定。
4.5 List why other potential root causes has been dismissed.
列出一张表,为什么其它潜在根源已经解除。
4.6 Reason for "escape" from system is identified.
列出原因为什么这个系统会(侦测不到)的原因。
4.7 List both process and system root cause.
列出制程和系统的发生根源原因。
4.8 Stated root causes are causes, not symptom or effects.
陈述的根源是原因, 不可说明这问题表面现象症状。
4.9 Verification of root cause has been done. Simulation done.

1. Implement corrective actions执行矫正措施

5.1 Alternatives are examined/screened. 提出方法可选择性来执行检查 / 监控。
5.2 Poka Yoke solutions are considered. 需使用防呆方式考量。
5.3 No other potential issues/defects are introduced from corrective action.
任何其它有潜在问题 / 缺陷是从这矫正行动不被导入的。
5.4 Stated actions cover all process root cause.
这项矫正措施必需包含所有生产流程的真正问题发生原因。
5.5 Stated actions cover all system root cause. System corrective action can prevent"escapes".
这项矫正措施必需包含所有品质系统的真正问题发生原因。
5.6 Corrective actions are demonstrated to be effective? List evidence to support it.
矫正行动演示有效吗? 把证据列成表以支持它。
5.7 State the targeted implementation dates of all corrective action.
所有矫正行动目标的需填写执行日期。

1. Verify the corrective action证实矫正措施 (改善效果确认)

6.1 Conduct the pi-lot build to verify the effectiveness of corrective action.
引导试验建立出并证实这项矫正行动是有效的。
6.2 Continue to monitor the effectiveness after the action taken.
用这项有效的矫正行动,以后继续使用监控。

1. Prevent recurrence预防对策(防止复发)

7.1 All process documents are revised and deployed.
所有生产流程文件需被修正与展开。
7.2 Are process corrective actions applicable elsewhere?
所有生产流程在其它地方是矫正行动可适用吗?
7.3 Are system corrective actions applicable elsewhere?
品质系统在其它地方是矫正行动可适用吗?
7.4 Identify the target date for accomplishing the prevent actions from above.
从上述7.1~7.3 ,完成预防行动必须确定这个目标日期。

1. Congratulation 恭喜完成此份8D Form (MSI QA改善效果确认 / 制程稽核 )