Fish Market--鱼市场
Fish Market-- Display the defective PCBA stating them as fresh and hot items, thereby eliminating the delayed response for defect prevention. It’s a common area where everybody will review the defect visually. Following Departments personnel’s along with operators will then find probable root causes and eliminate the root cause immediately.
鱼市场---用来展示在制程过程中产生的新鲜的坏品, 消除滞后反馈。这个公共的区域,每个人都能真实的看到这个缺陷, 然后生产部和相关的部门的人一起迅速地找到和消除这个根本原因。
QE: Quality Engineer 品质工程师
PE: Process Engineer 工艺工程师
TE: Test Engineer 测试工程师
EE: Equipment Engineer 设备工程师
MBU: Manufacturing Business Unit 制造业务部
POO:Point of Origin 缺陷发生点
POD: Point of Detect 缺陷发现点
4.0 Responsibility (职责)
Debug: Analyze the defect boards (POD).
Debug: 分析这个缺陷位置(缺陷发现点)
Process Engineer: Keep monitoring the process, dig out the root cause case by case and take action.
工艺工程师:持续跟踪整个流程,找到根本原因针对每个缺陷,然后采取行动。
Quality Engineer: Audit the yield loss and verify the actions taken by relative function team.
品质工程师:监督良率状况和验证相关部门的行动结果的有效性。
MBU: Transfer the defect boards to debug & escalate if preventive action not taken on time.
生产部:把缺陷板到的Debug 每个小时,当不能及时找到解决和预防行动时,往上反馈。
5.1 测试位发现坏板
5.2 MBU Transfer the boards to debug to analyze on hourly basis.
5.2 生产部每个小时把缺陷的板送到Debug 去分析。
5.3 Debug sends the analyzed boards with Defect card and relative picture to Fish market
5.3 Debug 把分析结果包括坏板卡和相关的图片送到Fish Market.
5.4 PE review the defect boards
5.4 PE 查看坏板。
5.5 MBU (MBU PE,TE,EE, Line leader) take lead to dig out the root cause firstly by Using WHY WHY analysis.
5.5 生产部(包括生产部PE, TE,EE, 领班)最先运用连续问5 个为什么挖掘缺陷发生的根本原因。
5.6 After last WHY, the team will do a 7 ways analysis to eliminate the problem.
5.6 通过 最后一个为什么找到根本原因之后,团队就可以运用建议7种可能的方法去消除这个问题。
5.6a Identify POO & POD.
5.6a 定义缺陷发生点和缺陷发现点
5.6b Learn how to make the defect to understand root cause.
5.6b 运用重新制造这个缺陷去进一步理解根本原因
5.6c Talk to the defect.
5.6c 针对缺陷说话,实事求是。
5.7 Idea Evaluation sheet will be filled for the same.
5.6 方法评估表格将可以应用去便于找到最佳方法。
5.8 Kaizen, Poka Yoke, Layout Change or Process change will be notified to all concerned.
5.8 相关的改善,解决缺陷的方法,车间布局的改变或者是流程的改变必须通知到相关的部门。
5.9 QA verify the action’s effectiveness.
5.9 QA去验证行动的有效性
5.10 Return the defect boards to Debug to repair
5.10 把板退还Debug 去维修
5.11 If the problem can’t be solved timely, as escalation path defined, the operator is empowered to dial the trigger system that directly notifies operation manager or higher level.
5.11 如果问题在规定的时间内得不到解决,按照往上反馈的路径定义的,操作员被授权按报警系统直接反映给生产经理或者更高级别。
5.12 Test the repaired boards
5.12 测试部返修缺陷板。
鱼市场---用来展示在制程过程中产生的新鲜的坏品, 消除滞后反馈。这个公共的区域,每个人都能真实的看到这个缺陷, 然后生产部和相关的部门的人一起迅速地找到和消除这个根本原因。
QE: Quality Engineer 品质工程师
PE: Process Engineer 工艺工程师
TE: Test Engineer 测试工程师
EE: Equipment Engineer 设备工程师
MBU: Manufacturing Business Unit 制造业务部
POO:Point of Origin 缺陷发生点
POD: Point of Detect 缺陷发现点
4.0 Responsibility (职责)
Debug: Analyze the defect boards (POD).
Debug: 分析这个缺陷位置(缺陷发现点)
Process Engineer: Keep monitoring the process, dig out the root cause case by case and take action.
工艺工程师:持续跟踪整个流程,找到根本原因针对每个缺陷,然后采取行动。
Quality Engineer: Audit the yield loss and verify the actions taken by relative function team.
品质工程师:监督良率状况和验证相关部门的行动结果的有效性。
MBU: Transfer the defect boards to debug & escalate if preventive action not taken on time.
生产部:把缺陷板到的Debug 每个小时,当不能及时找到解决和预防行动时,往上反馈。
- Procedure
5.1 测试位发现坏板
5.2 MBU Transfer the boards to debug to analyze on hourly basis.
5.2 生产部每个小时把缺陷的板送到Debug 去分析。
5.3 Debug sends the analyzed boards with Defect card and relative picture to Fish market
5.3 Debug 把分析结果包括坏板卡和相关的图片送到Fish Market.
5.4 PE review the defect boards
5.4 PE 查看坏板。
5.5 MBU (MBU PE,TE,EE, Line leader) take lead to dig out the root cause firstly by Using WHY WHY analysis.
5.5 生产部(包括生产部PE, TE,EE, 领班)最先运用连续问5 个为什么挖掘缺陷发生的根本原因。
5.6 After last WHY, the team will do a 7 ways analysis to eliminate the problem.
5.6 通过 最后一个为什么找到根本原因之后,团队就可以运用建议7种可能的方法去消除这个问题。
5.6a Identify POO & POD.
5.6a 定义缺陷发生点和缺陷发现点
5.6b Learn how to make the defect to understand root cause.
5.6b 运用重新制造这个缺陷去进一步理解根本原因
5.6c Talk to the defect.
5.6c 针对缺陷说话,实事求是。
5.7 Idea Evaluation sheet will be filled for the same.
5.6 方法评估表格将可以应用去便于找到最佳方法。
5.8 Kaizen, Poka Yoke, Layout Change or Process change will be notified to all concerned.
5.8 相关的改善,解决缺陷的方法,车间布局的改变或者是流程的改变必须通知到相关的部门。
5.9 QA verify the action’s effectiveness.
5.9 QA去验证行动的有效性
5.10 Return the defect boards to Debug to repair
5.10 把板退还Debug 去维修
5.11 If the problem can’t be solved timely, as escalation path defined, the operator is empowered to dial the trigger system that directly notifies operation manager or higher level.
5.11 如果问题在规定的时间内得不到解决,按照往上反馈的路径定义的,操作员被授权按报警系统直接反映给生产经理或者更高级别。
5.12 Test the repaired boards
5.12 测试部返修缺陷板。
没有找到相关结果
已邀请:
2 个回复
allen_henry (威望:0) - IE的观点看买房:這辈子需求房价钱至少100万,...
赞同来自:
很好,我认为要 要求反应迅速反馈快速
因为感觉真像鱼刺一样...