【正文】 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。Cut in12/10/2023 8 1 1 82. 誤判4 * 金手指接觸不良 4 定期維護保養(yǎng) 3 48訂定維護保養(yǎng)計劃及定期校正TE Gavin Huang12/3/0039。NCE DETECTIONRPN( 一 ) ICT Function 不良 1. OPEN5 頂針位置錯誤 3 治具廠商 double check 1 15 NONE 5 3 1 15 5 程式漏 Key 3 治具廠商 double check 1 15 NONE 5 3 1 155 Relay Board 故障 3 定期維護保養(yǎng) 1 15 NONE 5 3 1 155 氣壓不足 2 CHECK 氣 壓表 1 10 NONE 5 2 1 105 探針變形 3 定期維護保養(yǎng) 2 30 NONE 5 3 2 302. Short 5 頂針位置錯誤 3 人員做 double check 1 15 NONE 5 3 1 153. Component 6 頂針位置錯誤 3 人員做 double check 1 18 NONE 6 3 1 186 氣壓過高 2 CHECK 氣 壓表 1 12 NONE 6 2 1 12(二) ATS Function 不良 1. 燒機8 配線線路接錯 3 人員 review 1 24 NONE 8 3 1 248 * 散熱不當 4 使用風扇做溫度散熱 3 96製作測試 OI,註明風扇位置 ,風向及距離TE Gavin Huang12/3/0039。 針對類似程序已知有可靠的檢測管制方式2 現(xiàn)行管制方式有非常高的可能性可以檢測出此一失敗模式90 ～ 100%80%高High34756現(xiàn)行管制方式有高度可能性可以檢測出此一失敗模式現(xiàn)行管制方式有中度可能性可以檢測出此一失敗模式現(xiàn)行管制方式有低度可能性可以檢測出此一失敗模式現(xiàn)行管制方式檢出此一失敗模式之可能性非常低現(xiàn)行管制方式有中高度可能性可以檢測出此一失敗模式30%70%60%50%40%25 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 RPN (Risk Priority Number) is the product of Severity, Occurrence, and Detection. The higher the number, the higher the risk. 10. FMEA 格式逐項解說 1. 2. 4. 3. 5. 6. 8. 7. 9. 12. 11. 15. 14. 13. 26 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 What actions need to be taken to prevent the Failure Mode? If no action is taken, record “ none” 11. FMEA 格式逐項解說 1. 10. 4. 3. 5. 6. 8. 7. 9. 12. 2. 15. 14. 13. 27 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 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