【正文】 e Occurrence Detection Detection RPN RPN Assign appropriate individual, area, function or team. Set a realistic target for pletion Target date could be established by development program 12. FMEA 格式逐項解說 1. 10. 4. 3. 5. 6. 8. 7. 9. 2. 11. 15. 14. 13. 28 of 33 .~. Part Failure Mode Effect(s) Cause(s) Current or Action(s) to Area or Action(s) Name * Control(s) be taken Individual taken Function responsible Energy Management Cannot Customer Software Monitor dissatisfaction Failure Monitor Battery Battery alert Battery user of status connections spec. wrong Incorrect battery used Cannot Customer Software accurately dissatisfaction failure ID status Battery Connections damage spec. wrong Unable to detect battery Faults Severity Severity Occurrence Occurrence Detection Detection RPN RPN List the results of the actions taken. Always enter a reference such as data or test reports. 13. FMEA 格式逐項解說 1. 10. 4. 3. 5. 6. 8. 7. 9. 12. 11. 15. 14. 2. 29 of 33 .~. Part Failure Mode Effect(s) Cause(s) Current or Action(s) to Area or Action(s) Name * Control(s) be taken Individual taken Function responsible Energy Management Cannot Customer Software Monitor dissatisfaction Failure Monitor Battery Battery alert Battery user of status connections spec. wrong Incorrect battery used Cannot Customer Software accurately dissatisfaction failure ID status Battery Connections damage spec. wrong Unable to detect battery Faults Severity Severity Occurrence Occurrence Detection Detection RPN RPN When reassessing SEVERITY, the only factors that will influence a change will be: ?new experience ?change in regulations ?design change ?change in customer priorities 14. FMEA 格式逐項解說 1. 10. 4. 3. 5. 6. 8. 7. 9. 12. 11. 15. 2. 13. 30 of 33 .~. Part Failure Mode Effect(s) Cause(s) Current or Action(s) to Area or Action(s) Name * Control(s) be taken Individual taken Function responsible Energy Management Cannot Customer Software Monitor dissatisfaction Failure Monitor Battery Battery alert Battery user of status connections spec. wrong Incorrect battery used Cannot Customer Software accurately dissatisfaction failure ID status Battery Connections damage spec. wrong Unable to detect battery Faults Severity Severity Occurrence Occurrence Detection Detection RPN RPN If this RPN is not significantly less than previous, then ACTION taken has been ineffective. 15. FMEA 格式逐項解說 1. 10. 4. 3. 5. 6. 8. 7. 9. 12. 11. 2. 14. 13. 31 of 33 .~. Subsystem/Name : Testing station Suppliers Plants Affected: DELTA Chungli Prepared By: Design Authority: N/A Model Year/Unit: DPSXXXAB A FMEA Date(Orig): Rev 10/5/2023 REV:00Other Areas Involved: N/A Engineering Release Date: N/AProcess NumberPotential FailureModePotentialEffect(s) ofFailureSEVERITYCLASSPotentialCauses(s) ofFailureOCCUR39。Cut in12/10/2023 5 1 1 55 儀器故障 2 專人 review 1 10 NONE 5 2 1 10( 三 ) Tapping Function 不良 Short 不良 5 接線錯誤 3 人員 review 2 30 NONE 5 3 2 305 斷線 3 人員 review 1 15NONE5 3 1 15Tapping 不良 5 接線不良 3 人員 review 1 15 NONE 5 3 1 155 Connector。without warning178系統(tǒng)操作無影響 , 客戶不會注意到此項不良 。非常高的 生產(chǎn)線重要的中斷。 100% 產(chǎn)品可能需要重做。 部份產(chǎn)品 ( 小於 100%) 可能需要在線上重做 , 不Very Minor 需離站, 觀察力較強的顧客 可能會注意到。分析 與改正作業(yè)系統(tǒng) (FRACAS) 製程改善 檢驗程序改善 撰寫報告 8 of 33 .~. FMEA 實施步驟 1. 決定 FMEA 對象 2. 成立 組成 FMEA team members 3. 收集 準備相似產(chǎn)品之歷史資料 4. 列出產(chǎn)品方塊圖或製程流程圖 5. 列出 Failure mode 各種可能情況 6. 列出 Failure mode 對產(chǎn)品 /機器之 影響 (Effect) 7. 魚骨圖分析造成此 Failure mode 之可能原因 (Cause) 8. 根據(jù)相關(guān)產(chǎn)品之歷史資料定義出 Severity /Occurrence Detection 之等級 9. 根據(jù) S/O/D 的定義定出每個 Failure mode 之 S/O/D 值 10. 列出相似 Model 目前採行之 Action 11. 計算出 RPN=S*O*D 值 12. 取 RPN 值 ≧ 100 (值大小需定義 ) or Top 20% 優(yōu)先採取對策 13. 針對 RPN 值超出上述定之項目提 出 Action 再改善 14. 定出 Action item 之 owner 及完成 日期 15. Action 切入後檢視其效果及切入時 間點 16. 重新計算 Action 後之 RPN 值 17. 若 RPN 值未達定義要求 RPN ≧ 100 or Top 20% 回覆到 item 13 重提 Action 18. 若 RPN 達到要求完成 FMEA 表格 9 of 33 .~. FMEA Team Members DFMEA (Design) Chairperson * Program Manager (PM) * Electronic Engineer (EE) * Mechanical Engineer (ME) * Quality Engineer (QE) * Quality Engineer (QA) * Manufacturing (MES) Support Team * Purchasing (Buyer) if Need