8D报告格式模板(英文)

合集下载

8D报告格式(中英文对照)

8D报告格式(中英文对照)

审核日期 Approved Date:
6、纠正措施效果验证(Discipline 6.Verification of Effectiveness)
NO.
效果验证(Verification of Effectiveness)
确认人
1
2 审核 Approved By:吕曲
审核日期 Approved Date:2011-1-5
投诉类型 (Rea For CA)
总批量数 (Occurred Qty)
检验数 ( Qtv Ins)
不良数 (Qtv Rei)
文件投诉
提出日 (Date Raised)
提出人员 (Raised by) 要求完成日期 (Due Date)
1、小组成员(Discipline 1.Team Members)
备注(Memo)
表单编号: KTQA36V2.0-
第2页
NO.
暂时补救的纠正措施(Immediate Containment Actions)
负责人
1
2
审核 Approved By:杨社健
审核日期 Approved Date:吕曲
4、明确和核实根本原因(Discipline 4.Define and Verify Root Causes)
日期
起草Prepared By:
7、预防再现措施(Discipline 7.Prevent Recurrence)
NO.
预防再现措施(Prevent Recurrence)
负责人
日期 日期
1
2
审核 Approved By:吕曲
审核日期 Approved Date:2011-1-5
8、客户确认及评价(Discipline 8.Customer satisfaction degree)

8D报告模板(中英文)

8D报告模板(中英文)

XXX 精密机械有限公司8D-REPORT 异常No.: 产品编号\MFC P/N : 供货商\Supplier :INV NO. S/C NO : 管理代表\Manager Rep : 订单数量\Q'TY : 不良数\DEF Q'TY :Discipline 1 INTERNAL/EXTERNAL MEMBERS/责任归属1.RESPONSIBLE DEPARTMENT \责属单位:2. RESPONSIBLE PERSON\责属人员: Discipline 2 DESCRIBE THE PROBLEM\问题描述Discipline 3 IMMEDIATE ACTION\立即改善措施负责人 预定完成日Discipline 4 DECRIBE ROOT CAUSE\根本原因描述ROOT CAUSE\发生原因WHY WAS NOT DETECTED\ 为何未被侦测到 责属单位 责属人员Discipline 5 LONG-TERM ACTION\长期措施CORRECTIVE ACTION \改善措施 RECHECK FOR RELATIONAL PROCESS AND PRODUCT \类似制程和产品的考量负责人 预定完成日是否修正YES NOFMEA/FLOW CHART/CONTROL PLAN Department Manager/单位主管﹕ Respondor/承办人﹕ Discipline 6 VERIFICATION OF EFFECTIVENESS 效果确认审核者 效果追踪日Discipline 7 PREVENT RECURRENCE\再发防止审核者 效果追踪日Case close(结案) □YES \是 □NO \否Discipline 8 MEMO\备注Discipline 6、7、8由MFC 或客户填写 窗体编号:FM 本单据需由品保部追踪FMEA/CONTROL PLAN/FLOW CHART 已因应相对应改善措施修正完成. Open Date\发生日期 Happen Station\发生地 Close Date\结案日期。

8D报告(中英文)

8D报告(中英文)
Fill in/填写:Send/发送:
Team Member/小组成员:
Approvl/核准:
Root Cause/根本原因:(description of technical or logistical background/技术或内在联系)
Analysis/分析:Approvl/核准:
Containment Action(s)/补救措施:
Define Problem/问题描述:(all relevant data like failure description, failure rate, line or incoming failure - filled-in by customer)
(所有相关数据比如缺陷描述,缺陷比率,在线或进料缺陷-客户提供)
公司LOGO
公司英文名称
公司中文名称
Date/日期:
Complaint No./客诉编号:
8D Report(Customer Complaint)/ 8D报告(客户抱怨)
Company/公司:Linkman/联系人:
Model Name/机型名称:Complaint Date/抱怨日期:
Purchase Order No./定单号:Delivery ./出货日期:
Fill in/填写:Approvl/核准:Send/发送:
Corrective Action/纠正措施:(short-term and mid-term actions/短期及中期预防措施)
Fill in/填写:Approvl/核准:Send/发送:
Verify Corrective Actions/确认纠正措施:(indication that corrective actions are covering the defined problem/

8D分析详细报告(中英翻译)

8D分析详细报告(中英翻译)

(如果有任何说明/附件)(图-1)A. 3Way5Why Methodology(3Way5Why 方法论)No 问题点描述1way 2way 3way 4way 5way1按键功能不良(脏点,水印,白点)/Poor functional key(dirty dot, watermark,white dot)LUPHi人员是否清楚注意事项.(清楚)/ If LUPHistuff are clearabout mattersneedingattention(clear)有没有对应的SOP;(有)/ If LUPHihas thecorrespondingSOP;(yes)有没有相应的培训教育;(有)/ If LUPHihas thecorrespondingprofessionaltraining;(yes)制程中有没有发现此类不良;(有)/ If LUPHIfinds thisproblem inmanufactureprocedure(yes)其它客户有没有反馈类似问题;(较少发生)/ IfLUPHi getsothercostomer’sfeedback likethis;(rarely)C.再现解析:1、通过对客退品分析具体如下:/ The analysis of the return goods as follow:■解析项目:常规测试按键不导通(5PCS)/ analyse program:the button can not connect with normal test(5PCS).■解析结果:analyse result:■发生根本原因:线路断线导致按键失效:(如图-2)/primary cause: the circuit breaks line leads the circuit can not work(as picture 2);■影响因素:/ reason:①、反复多次折弯导致;/the circuit bends many times;②、线路银浆剥离导致;/ the circuit silver paste fall off;③、线路不够柔韧;(线路印刷2次光固(感光固化)UV厚度达到0.21MM)/ the circuit is not enough soft(the circuitUV thickness leads to 0.21mm with printing 2 times);(图-2)/(as picture 2)说明:“/”标示位置为PIN折弯后形成的痕迹,线路漏电路线为分析原因造成。

8D报告格式模板(英文)

8D报告格式模板(英文)

Copyright Autoliv Inc., All Rights Reserved
Step 4 Root Cause Analysis – Verification of Root Cause
Root Cause
(From previous pages)
Data that Supports/Proves the Root Cause
Occurrence Cause
Detection Cause
ACN-C-F010-EN-1.0
Copyright Autoliv Inc., All Rights Reserved
Step 6 Evaluate Results
Confirm the problem is eliminated!
Total Quantity Inspected Post the Permanent Corrective Action Quantity Rejected Quantity Accepted
ACN-C-F010-EN-1.0
Copyright Autoliv Inc., All Rights Reserved
Step 4 Root Cause Analysis
Please include the following overhead of the “Five Why for Occurrence and Detection” OR a fully completed Fault Tree with accompanying analysis.
The following two overheads, the Fishbone and the Cause and Effect Table, are optional problem solving tools and should be used if the other tools were inadequate.

8D报告格式(中英文对照)

8D报告格式(中英文对照)

7、预防再现措施(Discipline 7.Prevent Recurrence)
NO.
预防再现措施(Prevent Recurrence)
确认人 负责人
日期 日期
1
2
审核 Approved By:
审核日期 Approved Date:
8、客户确认及评价(Discipline 8.Customer satisfaction degree)
审核Approved By:
完成日期Completed Date:
第1页
KONGTOP
*****有限公司
5、永久性纠正措施(Discipline 5. Permanent Corrective Actions)
NO.
纠正措施(permanent Corrective Actions)


负责人
日期
第一批产品满意程度:yes( ) 第二批产品满意程度:yes( ) 第三批产品满意程度:yes( )
no( ) no( ) no( )
与客户_________联系,确认此批出货产品有/无以上不良现象。 与客户_________联系,确认此批出货产品有/无以上不良现象。 与客户_________联系,确认此批出货产品有/无以上不良现象。
备注(Memo)
表单编Hale Waihona Puke :保存期限:三年第2页
2、问题描述(Discipline 2. Problem Description)
工程
开发
采购
业务
起草Prepared By:
审核Approved By:
3、即日纠正措施(Discipline 3. Immediate Containment Actions)

8D报告模板(中英文)

8D报告模板(中英文)

商标图案公司英文名称公司中文名称Date/日期:Complaint No./客诉编号:Complaint - 8D-Report/客诉-8D-报告Company/公司: Attn./相关人:Model Name/机型名称:Complaint Date/抱怨日期:Purchase Order No./定单号:Delivery ./出货日期:Define Problem/问题描述:(all relevant data like failure description, failure rate, line or incoming failure - filled-in by customer)(所有相关数据比如缺陷描述,缺陷比率,在线或进料缺陷-客户提供)Fill in/填写:Send/发送:Team Member/小组成员:Approvl/核准:Root Cause/根本原因:(description of technical or logistical background/技术或内在联系)Analysis/分析:Approvl/核准:Containment Action(s)/补救措施:Fill in/填写:Approvl/核准:Send/发送:Corrective Action/纠正措施:(short-term and mid-term actions/短期及中期预防措施)Fill in/填写:Approvl/核准:Send/发送:Verify Corrective Actions/确认纠正措施:(indication that corrective actions are covering the defined problem/指明纠正措施覆盖到描述的问题)p。

8D报告-中英文版

8D报告-中英文版
12
缺乏清楚 的优先级
Discovering the Problem发现问题
A problem occurs when the actual outcome of a process deviates from its expected outcome.当流程的实际结果偏离预期的的结果时问题发生
A problem becomes known when its effect is experienced. The cause of a problem is always a previous event in time.当经历过 结果时问题才会被大家知道.问题的原因永远是以前发生过才知道
The Planned Systematic Process to Resolve (not mask) a Problem. 有计划的系统的流程来解决(而不是掩盖)问题
teamrolescontinued团队角色facilitator协调员encouragesotherteammembersexpressviewswaitsuntillaterexpresspersonalviews鼓励所有团队成员表达观点并等到最后表达个人观点handlesmeetingprotocolgroupdynamics负责会议草案团队动力teaminteraction监控团队交流membersfocusedcommunicationprocessratherthancontent更关注沟通过程而不是内容recorder记录员takingnotesduringactionitemsassignments在会议中作笔记并在会后发布会议纪要和被指派的措施项目collectingprojectdocumentsprojectfile负责收集项目的文件和数据并整理成一个项目文件包4020052006eatoncorp
  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

Copyright Autoliv Inc., All Rights Reserved
Step 2 Describe the Problem
Picture of Non Conforming Condition Picture of Conforming Condition
Condition Is:
ACN-C-F010-EN-1.0
Copyright Autoliv Inc., All Rights Reserved
Step 3 Implement Containment Actions
Copy of Inspection Sorting and/or Containment instructions to workers responsible
ACN-C-F010-EN-1.0 Copyright Autoliv Inc., AllTeam
(Members should include all pertinent groups - Cross-Functional)

Roles
Why
Why
Detection Cause
Occurrence Root Cause
Why
Why
Why
Why
Detection Root Cause
ACN-C-F010-EN-1.0
Copyright Autoliv Inc., All Rights Reserved
Step 4 Root Cause Analysis – Fault Tree Analysis
ACN-C-F010-EN-1.0
Copyright Autoliv Inc., All Rights Reserved
Step 4 Root Cause Analysis –Five Why – Occurrence and Detection
Occurrence Cause
Why
Why
Problem Statement
Desired Condition:
Actual Condition:


How many parts have the problem?
What is the size of the problem? How many times does the problem occur on each part?
Autoliv Requirement is:

What part has the problem? Where was the part when the problem was observed? Where is the problem on the part? When was the problem observed first (clock and calendar time)? When since that time has the problem been observed? Any pattern? When, in the part’s history or life cycle, was the problem first observed?
Autoliv NCM number issued for this problem: Bookend Dates: From:
Problem start date
To:
Clean point by inspection (or otherwise) Date
What is the suspect AIAG label serial number/lots? What are the inventory locations (warehouse, in-transit)? What is the total N/G product produced? List all affected Part Numbers: How many are produced each shift? How many shifts run this product? Supplier Autoliv Customer
Copyright Autoliv Inc., All Rights Reserved
Step 4 Root Cause Analysis – Verification of Root Cause
Root Cause
(From previous pages)
Data that Supports/Proves the Root Cause
Please place your Plant/Location here
Please place a simple phrase that describes your problem here
Name of 8D Owner 8D Number in APSD Date 8D Issued: Place date here
Evaluated for risk using FMEA or other risk analysis tools to prevent secondary problem that could result from the containment action.
Evaluated?
Yes No
Note to user: This form is meant to be a template to better enable you to meet the AS63 standard, which is quite indepth and profound. Due to the uniqueness of each problem, you may need to modify/add to this presentation so that you comply with the actual AS63 standard.
Optional
Measurement Accept Reject Explanation Delete this overhead if not used.
Machine
Accept
Reject
Explanation
Material
Accept
Reject
Explanation
ACN-C-F010-EN-1.0
Occurrence Cause
Detection Cause
ACN-C-F010-EN-1.0
Copyright Autoliv Inc., All Rights Reserved
Step 6 Evaluate Results
Confirm the problem is eliminated!
Total Quantity Inspected Post the Permanent Corrective Action Quantity Rejected Quantity Accepted
The following two overheads, the Fishbone and the Cause and Effect Table, are optional problem solving tools and should be used if the other tools were inadequate.
Inspection Method Used Post the Permanent Corrective Action
Gage R&R/Kappa score for this inspection exercise in step 6.
Poka-Yoke?
Yes
(Please include justification.)
ACN-C-F010-EN-1.0
Copyright Autoliv Inc., All Rights Reserved
Step 4 Root Cause Analysis (Fishbone)
Man Method
Measurement
Effect
Optional Delete this overhead if not used.
Add your own fault tree here or delete overhead if you use 5 Why.
ACN-C-F010-EN-1.0
Copyright Autoliv Inc., All Rights Reserved
Step 4 Root Cause Analysis
Note: Insert the appropriate pictures or sketches in the boxes provided above
ACN-C-F010-EN-1.0 Copyright Autoliv Inc., All Rights Reserved
Step 3 Implement Containment Actions
Machine
Material
Note: Circle the accepted causes in red.
To input data in the boxes just highlight the box (you will see cross hatch lines on the boarder) and start typing your text. The text should automatically wrap inside the box.
Inspection Method Used
Kappa Score or Gage R&R (or what is
the validation method sort process)
相关文档
最新文档