失效模式(FMEA详解)课件

FMEAFailureModeandEffectsAnalysis失效模式與效應分析1of33FMEA1ofFMEA意義說明FMEA是不良預防的工具,是一種有條理程序可藉由一張包含所有的失效模式的表,並以數據來表示風險的大小和預先採取預防改善措施。

2of33FMEA意義說明FMEA是不良預防的工具,是一種2o導入FMEA的優點Teamwork方式提高部門或Function間連繫溝通,共同預防改善問題

腦力激盪方式,讓每一成員在同一議題上發揮想像力,經由有系統整合提出有效之預防改善對策徹底了解產品功能架構圖或產品製造組合流程圖以魚骨圖分析方式列出失效模式每一種可能因子以失效樹分析(FTA)方法了解產品失效模式各種組合型式

把失效模式量化針對TopFailureMode優先採取對策預防確保所有想像得到失效模式和影響,在正常操作情況之下均被考慮到藉由過去的資料給未來參考,協助分析失效的範圍和影響性提供設計產品或製程管制預防採取對策時使用3of33導入FMEA的優點Teamwork方式提高部門或Fun

Coreteam:列出與FMEAteam相關人員名字,部門與職責

Failuremode:失效模式種類

Effect:失效後對產品產生影響

Cause:造成失效模式之原因

Severity:失效模式發生之嚴重程度等級(1～10)

Occurrence:失效模式之發生頻度等級(1～10)

Detection:失效模式發生可被偵測程度等級(1～10)

RPN:RiskPriorityNumber指評估風險及優先處理指數是Severity*Occurrence*Detection之乘積

FTA:Faulttreeanalysis是失效樹分析是導果為因由頂端事件利用邏輯(OR或AND)持續分析第1.2…層直至真正Rootcause將這些原因謀求徹底改善FMEA相關名詞解說4of33Coreteam:列出與FMEAteam相關人員名

QFD:QualityFunctionDeployment

DOE:DesignofExperiments

VOC:VoiceofCustomer

VOE:VoiceofEngineering

SOP:StandardOperationProcedure

SIP:StandardInspectionProcedure

FRACAS:FailureReportAnalysisandCorrectiveActionSystem

SPC:StatisticProcessControl

TQM:TotalQualityManagement

DVT:DesignValuationTest

MTBF:MeanTimeBetweenFailureFMEA書籍相關名詞解說5of33QFD:QualityFunctionDeployFMEA型式SYSTEM

SFMEADesign

DFMEA*Component*Unit*ModuleProcess

PFMEAMachine

MFMEAEquipment

EFMEAService

SFMEA6of33FMEA型式SYSTEM組成FMEA團隊設計FMEA流程(DFMEA)蒐集資料完成FMEA執行方案系統特性系統功能硬品架構分析失效模式分析設計管制方法分析失效原因分析失效效應分析嚴重度計算關鍵指數分析發生率分析難檢度建議改正行動決定關鍵性失效模式設計審查評估資料設計改善參考資料可靠度分析參考資料標準檢驗程序資料教育訓練參考資料失效報告。分析與改正作業系統(FRACAS)設計改善撰寫報告維護度分析參考資料7of33組成FMEA團隊設計FMEA流程(DFMEA)蒐集資料完組成FMEA團隊製程FMEA流程(PFMEA)蒐集資料完成FMEA執行方案定義製造流程分析產品特性分析製程特性分析失效模式分析現行管制方法分析失效原因分析失效效應分析嚴重度計算關鍵指數分析發生率分析難檢度建議改正行動決定關鍵性失效模式設計審查評估資料設計改善參考資料新製程設計參考資料標準檢驗程序資料教育訓練參考資料失效報告。分析與改正作業系統(FRACAS)製程改善檢驗程序改善撰寫報告8of33組成FMEA團隊製程FMEA流程(PFMEA)蒐集資料完FMEA實施步驟1.決定FMEA對象2.成立&組成FMEAteammembers3.收集&準備相似產品之歷史資料4.列出產品方塊圖或製程流程圖5.列出Failuremode各種可能情況6.列出Failuremode對產品/機器之影響(Effect)7.魚骨圖分析造成此Failuremode之可能原因(Cause)8.根據相關產品之歷史資料定義出Severity/OccurrenceDetection之等級9.根據S/O/D的定義定出每個Failuremode之S/O/D值10.列出相似Model目前採行之Action11.計算出RPN=S*O*D值12.取RPN值≧100(值大小需定義)orTop20%優先採取對策13.針對RPN值超出上述定之項目提出Action再改善14.定出Actionitem之owner及完成日期15.Action切入後檢視其效果及切入時間點16.重新計算Action後之RPN值17.若RPN值未達定義要求RPN≧100orTop20%回覆到item13重提Action18.若RPN達到要求完成FMEA表格9of33FMEA實施步驟1.決定FMEA對象11.計算出RFMEATeamMembers

DFMEA(Design)

Chairperson*ProgramManager(PM)*ElectronicEngineer(EE)*MechanicalEngineer(ME)*QualityEngineer(QE)*QualityEngineer(QA)

*Manufacturing(MES)SupportTeam*Purchasing(Buyer)ifNeed

PFMEA(Process)

Chairperson*ProgramManager(PM)*QualityEngineer(QA)*IndustryEngineer(IE)*MechanicalEngineer(MFGME)*TestEngineer(TE)*ManufactureSupervisor(MFG)*ElectronicEngineer(EE)ifNeed*MechanicalEngineer(ME)ifNeed

10of33FMEATeamMembersDFMEAFailureModeFishboneAnalysisHi-Pot不良FailureMode(Defect)錫面組立加工不良第一層分析Workmanship第二層分析第三層分析第四層分析正面裝插零件插歪斜零件面有異物無線尾零件變形零件碰case零件相碰第一層分析Material變壓器不良PCB不良Y電容不良PowerCable破EMI不良Case不良第二層分析第三層分析絕緣tape破引腳超出base焊點過大造成tape破儀器設備儀器設定Layout安規距離不夠Arcing規定過嚴零件間安規距離不足第一層分析Design第一層分析Test第二層分析第三層分析第二層分析第三層分析鎖螺絲過長套管短零件本体大Layout面積小測試條件設錯O/I寫錯測試線接錯11of33FailureModeFishboneAnalysisHi-PotFailureAnalysisFaultTreeAnalysisForHi-PotFailure5.板邊零件傾斜踫Case,造成安規距離不夠b.Socket上Y電容線腳靠近馬口鐵a.SocketFG線漏焊Process4.錫面3.正面裝插2.組立1.加工不良d.錫面短路︵錫珠,錫渣︶c.線腳過長b.漏焊︵Y電容︶a.異物c.零件插歪斜零件變形碰Case碰T1碰H/S相互碰撞b.零件面有異物a.無線尾h.鎖絲未鎖緊或漏鎖g.掉金屬物進產品f.絕緣片放置不當或漏裝d.PCB沒有卡到位c.組立時,B+B-線壓傷壓破b.絕緣片膠布破a.FG線有無Touch任何零件c.膠布沒貼到位Design2.元件之間安規距離不夠3.Arcing規格過嚴c.鎖螺絲過長b.套管短a.原件本体大Layout面積小4.板邊零件與Case安規距離不夠1.Layout安規距離不夠Material9.變壓器PFC︵電感︶8.膠雜質過多7.Y電容不良6.線材PowerCable破5.PCB4.EMISocket3.Case2.接地小黃豆電容耐壓不夠c.有毛刺b.耳掛有凸起a.碎屑b.本身耐壓不夠a.FG線氧化不吃錫b.Trace近似短路或開路a.PCB受潮e.絕緣Tape破d.零件本体歪斜c.焊點過大,造成錫間賜破絕緣層b.引線腳超出basea.絕緣膠布位置不恰當1.光藕合器不良e.O/I寫錯誤Test2.儀器設定1.儀器c.測試條件設置錯誤b.O/I寫錯誤a.測試線接錯b.儀器本身電壓頻率誤差大a.接觸不良f.本身繞線造成Arcing過大其他2.接地銅箔被燒斷3.接地跳線斷4.未依O/I作業1.SocketY電容線腳斷5.油墨,黑色Mark筆,在初級側導電12of33Hi-PotFaultTreeAnalysisForPartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPNThiscolumnisusedtolistthepartnameandfunction.ListallthefunctionsforthefunctionalblockFMEA格式逐項解說..3.13of33PartFailureMPartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPN2.Inthefailuremodecolumn,listeachofthefailuremodesforthefunction.FMEA格式逐項解說..4of33PartFailureMPartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceDetectionDetectionRPNRPNOccurrence3.Listtheeffectsoffailureforeachofthefailuremodes.FMEA格式逐項解說..5of33PartFailureMPartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPNForeachoneoftheeffects,listtheseverity(scalefrom1to10)4.FMEA格式逐項解說..6of33PartFailureM符合需求,17of33符合需求,17of33PartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPNTheClasscolumnisoptional.Itistypicallyusediftheseverityis9or10.5.FMEA格式逐項解說..8of33PartFailureMPartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPNIntheCausecolumn,listthecausesforeachfailuremode6.FMEA格式逐項解說..9of33PartFailureMFMEAModelLinkingFailureModetoCauseandEffectCauseFailureMode(Defect)Effect20of33FMEAModelLinkingFailureModePartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPNEstimatethelikelihoodofthe“causes”happeningona“1to10”scale.Thehigherthenumberthemorelikelythe“causes”willoccur.7.FMEA格式逐項解說..1of33PartFailureM22of3322of33PartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPNListtheprevention,designvalidation/verification,orotheractivitieswhichwillassurethedesignadequacyforthefailuremodeand/orcause/mechanismunderconsideration.TestsDesignreviews,Mathematicalstudies,Fail/safe(Example:redundantpowersupplies)8.FMEA格式逐項解說..3of33PartFailureMPartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPNEstimatethelikelihoodofthedetectionona“1to10”scale.Thelowerthenumberthemorelikelythecausewillbedetected.9.FMEA格式逐項解說..4of33PartFailureM25of3325of33PartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPNRPN(RiskPriorityNumber)istheproductofSeverity,Occurrence,andDetection.Thehigherthenumber,thehighertherisk.10.FMEA格式逐項解說..6of33PartFailureMPartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPNWhatactionsneedtobetakentopreventtheFailureMode?Ifnoactionistaken,record“none”11.FMEA格式逐項解說..7of33PartFailureMPartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPNAssignappropriateindividual,area,functionorteam.SetarealistictargetforcompletionTargetdatecouldbeestablishedbydevelopmentprogram12.FMEA格式逐項解說..8of33PartFailureMPartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPNListtheresultsoftheactionstaken.Alwaysenterareferencesuchasdataortestreports.13.FMEA格式逐項解說..9of33PartFailureMPartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPNWhenreassessingSEVERITY,theonlyfactorsthatwillinfluenceachangewillbe:newexperiencechangeinregulationsdesignchangechangeincustomerpriorities14.FMEA格式逐項解說..0of33PartFailureMPartFailureMode Effect(s) Cause(s)CurrentorAction(s)toAreaorAction(s)Name * Control(s)betakenIndividualtakenFunction responsibleEnergyManagement Cannot Customer Software Monitor dissatisfaction FailureMonitor BatteryBatteryalert Batteryuserofstatus connections spec.wrong Incorrect batteryused

Cannot Customer Software accurately dissatisfactionfailure IDstatus Battery Connections damage spec.wrong

Unableto detect battery Faults

SeveritySeverityOccurrenceOccurrenceDetectionDetectionRPNRPNIfthisRPNisnotsignificantlylessthanprevious,thenACTIONtakenhasbeenineffective.15.FMEA格式逐項解說...14.13.31of33PartFailureM

FMEAFailureModeandEffectsAnalysis失效模式與效應分析1of33FMEA1ofFMEA意義說明FMEA是不良預防的工具,是一種有條理程序可藉由一張包含所有的失效模式的表,並以數據來表示風險的大小和預先採取預防改善措施。

2of33FMEA意義說明FMEA是不良預防的工具,是一種2o導入FMEA的優點Teamwork方式提高部門或Function間連繫溝通,共同預防改善問題

腦力激盪方式,讓每一成員在同一議題上發揮想像力,經由有系統整合提出有效之預防改善對策徹底了解產品功能架構圖或產品製造組合流程圖以魚骨圖分析方式列出失效模式每一種可能因子以失效樹分析(FTA)方法了解產品失效模式各種組合型式

把失效模式量化針對TopFailureMode優先採取對策預防確保所有想像得到失效模式和影響,在正常操作情況之下均被考慮到藉由過去的資料給未來參考,協助分析失效的範圍和影響性提供設計產品或製程管制預防採取對策時使用3of33導入FMEA的優點Teamwork方式提高部門或Fun

Coreteam:列出與FMEAteam相關人員名字,部門與職責

Failuremode:失效模式種類

Effect:失效後對產品產生影響

Cause:造成失效模式之原因

Severity:失效模式發生之嚴重程度等級(1～10)

Occurrence:失效模式之發生頻度等級(1～10)

Detection:失效模式發生可被偵測程度等級(1～10)

RPN:RiskPriorityNumber指評估風險及優先處理指數是Severity*Occurrence*Detection之乘積

FTA:Faulttreeanalysis是失效樹分析是導果為因由頂端事件利用邏輯(OR或AND)持續分析第1.2…層直至真正Rootcause將這些原因謀求徹底改善FMEA相關名詞解說4of33Coreteam:列出與FMEAteam相關人員名

QFD:QualityFunctionDeployment

DOE:DesignofExperiments

VOC:VoiceofCustomer

VOE:VoiceofEngineering

SOP:StandardOperationProcedure

SIP:StandardInspectionProcedure

FRACAS:FailureReportAnalysisandCorrectiveActionSystem

SPC:StatisticProcessControl

TQM:TotalQualityManagement

DVT:DesignValuationTest

MTBF:MeanTimeBetweenFailureFMEA書籍相關名詞解說5of33QFD:QualityFunctionDeployFMEA型式SYSTEM

SFMEADesign

DFMEA*Component*Unit*ModuleProcess

PFMEAMachine

MFMEAEquipment

EFMEAService

SFMEA6of33FMEA型式SYSTEM組成FMEA團隊設計FMEA流程(DFMEA)蒐集資料完成FMEA執行方案系統特性系統功能硬品架構分析失效模式分析設計管制方法分析失效原因分析失效效應分析嚴重度計算關鍵指數分析發生率分析難檢度建議改正行動決定關鍵性失效模式設計審查評估資料設計改善參考資料可靠度分析參考資料標準檢驗程序資料教育訓練參考資料失效報告。分析與改正作業系統(FRACAS)設計改善撰寫報告維護度分析參考資料7of33組成FMEA團隊設計FMEA流程(DFMEA)蒐集資料完組成FMEA團隊製程FMEA流程(PFMEA)蒐集資料完成FMEA執行方案定義製造流程分析產品特性分析製程特性分析失效模式分析現行管制方法分析失效原因分析失效效應分析嚴重度計算關鍵指數分析發生率分析難檢度建議改正行動決定關鍵性失效模式設計審查評估資料設計改善參考資料新製程設計參考資料標準檢驗程序資料教育訓練參考資料失效報告。分析與改正作業系統(FRACAS)製程改善檢驗程序改善撰寫報告8of33組成FMEA團隊製程FMEA流程(PFMEA)蒐集資料完FMEA實施步驟1.決定FMEA對象2.成立&組成FMEAteammembers3.收集&準備相似產品之歷史資料4.列出產品方塊圖或製程流程圖5.列出Failuremode各種可能情況6.列出Failuremode對產品/機器之影響(Effect)7.魚骨圖分析造成此Failuremode之可能原因(Cause)8.根據相關產品之歷史資料定義出Severity/OccurrenceDetection之等級9.根據S/O/D的定義定出每個Failuremode之S/O/D值10.列出相似Model目前採行之Action11.計算出RPN=S*O*D值12.取RPN值≧100(值大小需定義)orTop20%優先採取對策13.針對RPN值超出上述定之項目提出Action再改善14.定出Actionitem之owner及完成日期15.Action切入後檢視其效果及切入時間點16.重新計算Action後之RPN值17.若RPN值未達定義要求RPN≧100orTop20%回覆到item13重提Action18.若RPN達到要求完成FMEA表格9of33FMEA實施步驟1.決定FMEA對象11.計算出RFMEATeamMembers

DFMEA(Design)

Chairperson*ProgramManager(PM)*ElectronicEngineer(EE)*MechanicalEngineer(ME)*QualityEngineer(QE)*QualityEngineer(QA)

*Manufacturing(MES)SupportTeam*Purchasing(Buyer)ifNeed

PFMEA(Process)

Chairperson*ProgramManager(PM)*QualityEngineer(QA)*IndustryEngineer(IE)*MechanicalEngineer(MFGME)*TestEngineer(TE)*ManufactureSupervisor(MFG)*ElectronicEngineer(EE)ifNeed*MechanicalEngineer(ME)ifNeed

10of33FMEATeamMembersDFMEAFailureModeFishboneAnalysisHi-Pot不良FailureMode(Defect)錫面組立加工不良第一層分析Workmanship第二層分析第三層分析第四層分析正面裝插零件插歪斜零件面有異物無線尾零件變形零件碰case零件相碰第一層分析Material變壓器不良PCB不良Y電容不良PowerCable破EMI不良Case不良第二層分析第三層分析絕緣tape破引腳超出base焊點過大造成tape破儀器設備儀器設定Layout安規距離不夠Arcing規定過嚴零件間安規距離不足第一層分析Design第一層分析Test第二層分析第三層分析第二層分析第三層分析鎖螺絲過長套管短零件本体大Layout面積小測試條件設錯O/I寫錯測試線接錯11of33FailureModeFishboneAnalysisHi-PotFailureAnalysisFaultTreeAnalysisForHi-PotFailure5.板邊零件傾斜踫Case,造成安規距離不夠b.Socket上Y電容線腳靠近馬口鐵a.SocketFG線漏焊Process4.錫面3.正面裝插2.組立1.加工不良d.錫面短路︵錫珠,錫渣︶c.線腳過長b.漏焊︵Y電容︶a.異物c.零件插歪斜零件變形碰Case碰T1碰H/S相互碰