搜索
您的当前位置:首页正文

8D format

2024-02-29 来源:独旅网
DOC:#.4.14.01.F002a Rev.2004.12.1 Unit Name单位名称 TRW LVLB Concern Tracking Number 问题跟踪号码 Customer 客户 CMT LVLB Step步骤 Action行动 PROBLEM SOLVING WORKSHEET 问题解决方案 DO Prepare准备 C D7 Prevent 预防措施 D1 Team 建立小组 D2 Describe 进行描述 D3 Contain 遏制措施 D4 Root 查找原因 D5 Correct修改 D6 Verify证实 D8 Wrap Initiate this report within 2 hours after problem communication. Any potential PPAC issue needs to be escalated to Management. See corporate procedure B65 “PPAC Process” or consult your manager if in doubt.问题讨论后2小时内分发此报告。任何潜在PPAC问题需向管理层汇报。见企业程序文件B65“PPAC程序管理”或仍有疑问请向上级经理询问 DO Part Number零件号: Part Name零件名: Preparation & Problem Awareness 准备并对问题的认识 Attach an Sketch of the Issue here 附带略图 不良写真 Platform & Vehicle级别平台及车辆: Raised By提出人: Location地点: Contact Phone联系电话: Date Raised提出日期: Hour小时: Type of Concern问题类型: Suspect Quantity估计数量: CTS Number CTS号码 Yes No Conduct a preliminary “Containment Report” & “Is/Is Not Analysis” worksheet review to gain deeper knowledge of the situation prior to team assembly. Then select individuals from appropriate functions and with the right level of authority. 为了在建组之前对情况有更深的了解,对“遏制措施报告”以及“是/否问题分析”进行前期评审,然后,选出适当的职能及合适的负责人 D1A Function职能 Team Definition 小组定义 Name姓名 D1B Issue Close-Off 项目完成 Date日期 Closure Approval 完成确认 1

DOC:#.4.14.01.F002a Rev.2004.12.1

Use the “Is/Is Not” tool to structure team thinking about the definition of the issue you want to investigate. Use it especially when you suspect there is only partial knowledge of the situation. Rephrase the questions should you feel they do not apply.运用“是/否问题分析”这个工具来引导小组对问题定义的调查,尤其是当大家对问题的情况了解的还不够全面。同时可以按需要对提问进行改述 D2A D2B Who谁 Problem Description问题描述 2月9日反馈给ATL Tiguan钳体21H批次缸孔多肉,导致加工时撞刀。 IS是 Who is experiencing the problem? 谁对此类问题有一定的经验? Who noticed the problem first time? 谁最先通告这个问题的? Will somebody else notice it in the future? 今后会有人负责报告此类问题吗? Who is aware of the problem? 谁清楚这个问题? What has the problem? 什么出现这个问题? IS NOT否 Who is not affected by the problem? 这个问题没有波及到谁? Who did not notice the problem? 谁没有通告这个问题? Who will not ever notice it? 谁不需要通告这个问题? Who is not? 不用谁? What是什么 What are the criteria to say this a problem? 什么标准判定这个问题? What is the effect? 问题的影响是什么? What is the severity? 什么样的严重程度? Why did this problem occur? 为什么会出现这个问题? Why did it escape undetected? 为什么发现了它? Why did it manifest where it did? 它为什么会出现?在哪出现? Where was the problem first detected? 问题第一次在哪被发现的? Where does the problem occur now? 现在问题在哪出现? Where else can it occur? 还出现在其它地方吗? When was the problem first observed? 问题在什么时间第一次被发现的? When was the last time it was noticed? 上一次在什么时间通告的这个问题? How many units are affected? 有多少个单位受到影响? How many people are involved? 与多少人有关? How much is this problem costing? 这个问题引起了多大的成本? How many hours being spent? 用了多少工时? What is the cycle trend of the problem? 这个问题的循环趋势怎么样? Is the process in statistical control? 程序在统计控制中吗? Has this problem occurred previously? If so, attach previous 8D reports. 以前这个问题发生过吗?如果是,请将上一次的8D报告附上。 What does not have it? 什么不会存在这样的问题? To what this criteria does not apply? 什么样的标准不适用? What could be the problem but it is not? 什么会成为问题,但现在还不是? Why this is not a problem? 为什么它不是问题? Why should it have been detected? 为什么它被发现了? Why is not manifesting beyond where it was detected? 它为什么没有继续隐藏?在哪被发现的? Where should have been detected but was not? 哪里应该发现问题但没发现? Where could be occurring but is not? 哪里应该发生问题但没有? When could the problem be first observed but was not? 该在什么时间就发现这个问题,但没发现? When 时间 Where哪 Why为什么 How Much/ Many数量 How many units do not have the problem? 有多少单位不存在这个问题? 2

How Often频率 What could be the trend but it is not? 如果没有循环,那么它的趋势有是怎样的呢? Why this is not a manifestation of an old problem? 为什么它不是某个旧问题的表现? DOC:#.4.14.01.F002a Rev.2004.12.1

Combine the information collected above to explain the problem in the field below. Include Information regarding Who, What, Why, Where, When, How many and How often is the problem appearing. 结合上述信息来对下面的问题进行解释。包括有关谁,什么,文身么,哪,什么时间,多少以及频率这些都是问题的表现

D2C Problem Definition问题定义 2月9日反馈给ATL Tiguan钳体21H批次缸孔多肉,导致加工时撞刀。 D3A Location位置 Containment遏制措施 Method of Sort分类方法 Containment Quantity涉及数量 Verified Quantity被证实的数量 Rejects Found不合格处理 Responsible & Contact Information责任及联系信息 OEM Customer OEM 客户 (Include all if multiple) (如果是多重的,就要包括所有的客户) Final Customer (Public) 最终客户(公共) Dealerships 代理 In-Transit to Dealerships 代理在途 Assembly Plant Yard 组装厂内 Assembly Plant In-process 组装线 In-Transit to OEM Customer OEM客户在途 Warehouse 库房 Shipping Dock 发运台 Assembly Area 组装区 Rework Areas 返修区 Non-conforming Areas 不符合项区域 Receiving Area 接收区域 In Transit 在途 Warehouse 库房 Shipping Dock 发运台 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ No ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ Yard Hold仍在厂内: Yes ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ No ○ Interdivisional TRW Customer TRW地区客户 (Shipping Plant)(发运公司) ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ Stop Shipments 停止发货: Yes ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ No ○ ○ ○ ○ ○ ○ ○ ○ TRW Assembly Area 组装区 Rework Areas 返修区 Non-conforming Areas 不符合项区域 Receiving Area 接收区 Stop Shipments 停止发货: Yes ○ Supliré供应商 In Transit to TRW TRW在途 Warehouse 库房 Shipping Dock 发货平台 In-Process 在制 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ Stop Shipments 停止发货: Yes √ No 3

D4A

Use this path for

通过这种途径对不合格项 目进行详细调查

WHY?为什么?

Root Cause Investigation 原因调查

WHY?为什么?

WHY?为什么?

Root Causes 根源

加工

通过这种 途径来调查 问题未被及 时发现的原 因

the specific Nonconformance being investigated OP31加工缸孔时撞刀

WHY?为什么?

Use this path to

investigate why the problem was not detected.

不良品流到LVLB

WHY?为什么?

A

Corrective Action 纠正措施 with Responsibility 及负责人

1.

Date 日期

缸孔内由于光线和角度问 题不容易发现

WHY?为什么? 《成品检验基准书》没有要求对缸孔进行100%检查

WHY?为什么? CTS Ref. No. CTS资料号 WHY?为什么?

Date of Issue 日期

Product / Process产品/过程 TRW Location TRW位置 Content Latest Rev Date

Use this path to 途径来调查 investigate the 是否体系存 systemic root cause 在导致问题 的原因

Communicate to TRW Date: 与TRW交流的日期:

通过这种 WHY?为什么?

WHY?为什么?

WHY?为什么?

最后一次内容更改日期

Problem Resolution Complete 问题决议完成

Lessons Learned所获经验:

Process Change Break Point Date: 过程改变日期:

B C

Implement System Change Date: 实现体系更改日期:

4

D4B Cause and Effect Diagram (Ishikawa) 因果图表 Why Happened? 为什么发生问题? Why Undetected? 为什么未被发现? Men 人力 Materials/Info 材料/信息 Machine 设备 People 人力 Materials/Info 材料/信息 Machine 设备 PROBLEM 问题(Effect)(影响) The symptoms of the problem are (Write Here问题的征兆是 , Method 方式 Environment 环境

Measurement 措施

Measurement 措施

Environment 环境

Method 方式

5

D5A Nr 6M Item # 6M 项目 1 2 3 4 5 6 7 8 Corrective Actions 纠正措施 Containment/ Permanent Corrective 遏制措施/永久纠正措施 D6A C or P Corrective Corrective Corrective Corrective Verification of Efficiency 效率确认 Target Verification Method Date 目标确认方式 时间 Who? 谁? Actual Date 实际日期 Status 状态 Open Open Open Open Click Here Click Here Click Here Click Here Corrective Corrective Corrective Corrective Initiate review of similar systems that might be affected by the same problem. Open a problem solving worksheet for each individual product/process subject to recurrence. 开始对相似体系进行检查,也许会受到同一问题的影响。利用问题解决方案对每一个产品/过程进行复查。 D7A Vehicle/ Platform车/等级平台 Address Similar Systems处理相似体系 Review Product/ Process (Reason Why/Why Does Not Apply) 核查产品/过程(为什么适用/不适用的原因) Who? 谁? Actual Date 实际日期 Status 状态 Open Open Open Ensure all relevant documentation is reviewed and updated with the team findings. Feel free to expand the Document Review table should any other documentation need to be reviewed. 确保审核并更新小组找到的所有相关文件。请随时根据需要审核其它文件的情况,对文档审核表进行扩展。 6

D7B Document Review 文档审核 Completion Date完成日期 Function 职能 Target 目标 Document 文件 Mistake Proofing 错误证实 Special Work Instructions 特殊工作结构 Non-Conforming Material 不合格材料 In-Process Stock 在制品 Training Status 培训状态 Process Checks 过程核对 Boundary Samples 边界样件 Calibration 校对 Changeover Instructions 结构改变 Standard Operating Procs. 标准操作过程 Quality Points 质量要点 Flowchart 流程图 DFMEA 设计分析 PFMEA 过程分析 Control Plan 控制计划 Incoming Inspection 来件检验 Specifications 规范 Drawings 图纸 ECRs Responsible 责任 Actual 实际 Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Click to Choose Conduct follow up meetings on the issue at least once per week until close-off. Record individuals’ attendance and keep meeting minutes as an attachment to this report. 直到结束每周至少一次对于此问题的跟踪会议。 记录参加会议人员并做好会议记录附到这份报告上。 7

D8A Place/ Room 地点/房间 Issue Follow up 问题进度跟踪 Called by 组织人 Date 日期 Attendance 参加人员 Submission dates should be in line with response timelines defined in your internal QRCM system. 提交日期应与在QRCM系统中的反应时间一致 D8B 8D Type 8D类型 8D Response Time Deadlines 8D反应时间期限 Submitted by 提交人 Submitted to 提交至 Submission Date 提交日期 Response Time 反应时间 Containment 遏制措施 Corrective 纠正 Closure 完成结束 D8C When? 时间 Where? 地点 Team Recognition 团队表彰 How? 形式 Quality Manager’s Approval. 质量经理批准 Signature & Date. 签字&日期

8

因篇幅问题不能全部显示,请点此查看更多更全内容

Top