失效模式(FMEA詳解)
《失效模式(FMEA詳解)》由會員分享,可在線閱讀,更多相關(guān)《失效模式(FMEA詳解)(31頁珍藏版)》請在裝配圖網(wǎng)上搜索。
1、Delta Confidential,,FMEA,,Failure Mode and Effects Analysis,,失效模式與效應分析,1 of 33,FMEA 意義說明,,FMEA,是不良,預防的工具,,,是一種,,有條理程序可藉由一張包含所有,,的失效模式的表,,,並以數(shù)據(jù)來表,,示風險的大小和預先採取預防改,,善措施。,,,,2 of 33,導入FMEA的優(yōu)點,,Team work,方式提高部門或,Function,間連繫溝通,,,共同預防改善問題,,,,腦力激盪方式,,,讓每一成員在同一議題上發(fā)揮想像力,,,經(jīng)由有系統(tǒng)整合,,提出有效之預防改善對策,,,徹底了解產(chǎn)品功能架構(gòu)圖或產(chǎn)
2、品製造組合流程圖,,,以魚骨圖分析方式列出失效模式每一種可能因子,,,以失效樹分析,(FTA),方法了解產(chǎn)品失效模式各種組合型式,,,,把失效模式量化針對,Top Failure Mode,優(yōu)先採取對策預防,,,確保所有想像得到失效模式和影響,,,在正常操作情況之下均被考慮到,,,藉由過去的資料給未來參考,,,協(xié)助分析失效的範圍和影響性,,提供設計產(chǎn)品或製程管制預防採取對策時使用,3 of 33,,Core team,:,列出與,FMEA team,相關(guān)人員名字,,,部門與職責,,,,Failure mode,:,失效模式種類,,,,Effect,:,失效後對產(chǎn)品產(chǎn)生影響,,,,Cause,:
3、,造成失效模式之原因,,,,Severity,:,失效模式發(fā)生之嚴重程度等級,(1,~,10),,,,Occurrence,:,失效模式之發(fā)生頻度等級,(1,~,10),,,,Detection,:,失效模式發(fā)生可被偵測程度等級,(1,~,10),,,,RPN,: Risk Priority Number,指評估風險及優(yōu)先處理指數(shù),,是,Severity * Occurrence * Detection,之乘積,,,,FTA,:Fault tree analysis,是失效樹分析是導果為因由頂端,,事件利用邏輯,(OR,或,AND),持續(xù)分析第,1.2…,層直,,至真正,Root cause,
4、將這些原因謀求徹底改善,FMEA相關(guān)名詞解說,4 of 33,,QFD,: Quality Function Deployment,,,DOE,: Design of Experiments,,,VOC,: Voice of Customer,,,VOE,: Voice of Engineering,,,SOP,: Standard Operation Procedure,,,SIP,: Standard Inspection Procedure,,,FRACAS,: Failure Report Analysis and,,Corrective Action System,,,SPC,: S
5、tatistic Process Control,,,TQM,: Total Quality Management,,,DVT,: Design Valuation Test,,,MTBF,: Mean Time Between Failure,FMEA書籍相關(guān)名詞解說,5 of 33,FMEA 型式,SYSTEM,,SFMEA,,,Design,,DFMEA,,,* Component,,,* Unit,,,* Module,,,Process,,PFMEA,,,Machine,,MFMEA,,,Equipment,,EFMEA,,,Service,,SFMEA,6 of 33,組成FMEA
6、團隊,設計 FMEA 流程(DFMEA),蒐集資料,完成FMEA執(zhí)行方案,系統(tǒng)特性,系統(tǒng)功能,硬品架構(gòu),分析失效模式,分析設計管制方法,分析失效原因,分析失效效應,分析嚴重度,計算關(guān)鍵指數(shù),分析發(fā)生率,分析難檢度,建議改正行動,決定關(guān)鍵性,,失效模式,設計審查,,評估資料,設計改善,,參考資料,可靠度分析,,參考資料,標準檢驗,,程序資料,教育訓練,,參考資料,失效報告。分析,,與改正作業(yè)系統(tǒng),,(FRACAS),設計改善,撰寫報告,維護度分析,,參考資料,7 of 33,組成FMEA團隊,製程 FMEA 流程(PFMEA),蒐集資料,完成FMEA執(zhí)行方案,定義製造流程,分析產(chǎn)品特性,分析製程
7、特性,分析失效模式,分析現(xiàn)行管制方法,分析失效原因,分析失效效應,分析嚴重度,計算關(guān)鍵指數(shù),分析發(fā)生率,分析難檢度,建議改正行動,決定關(guān)鍵性,,失效模式,設計審查,,評估資料,設計改善,,參考資料,新製程設計,,參考資料,標準檢驗,,程序資料,教育訓練,,參考資料,失效報告。分析,,與改正作業(yè)系統(tǒng),,(FRACAS),製程改善,檢驗程序改善,撰寫報告,8 of 33,FMEA 實施步驟,1,.,決定FMEA 對象,,2,. 成立&組成FMEA team members,,3,. 收集&準備相似產(chǎn)品之歷史資料,,4,. 列出產(chǎn)品方塊圖或製程流程圖,,5,. 列出Failure mode 各種可能
8、情況,,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 值超
9、出上述定之項目提,,出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
10、 Engineer,(EE),,* Mechanical Engineer,(ME),,* Quality Engineer,(QE),,* Quality Engineer,(QA),,,* Manufacturing,(MES),,Support Team,,* Purchasing (Buyer) if Need,,,,PFMEA (Process),,,,Chairperson,,* Program Manager,(PM),,* Quality Engineer,(QA),,* Industry Engineer,(IE),,* Mechanical Engineer,(MFG ME
11、),,* Test Engineer,(TE),,* Manufacture Supervisor,(MFG),,* Electronic Engineer,(EE),if Need,,* Mechanical Engineer,(ME),if Need,,,10 of 33,Failure Mode Fishbone Analysis,Hi-Pot 不良,,Failure,,Mode,,(Defect),錫面,組立,加工不良,第一層分析,,Workmanship,第二層分析,第三層分析,第四層分析,正面裝插,零件插歪斜,零件面有異物,無線尾,零件變形,零件碰case,零件相碰,第一層分析,,
12、Material,變壓器不良,PCB不良,Y電容不良,Power Cable破,EMI不良,Case不良,第二層分析,第三層分析,絕緣tape破,引腳超出base,焊點過大造成tape破,儀器設備,儀器設定,Layout 安規(guī)距離不夠,Arcing 規(guī)定過嚴,零件間安規(guī)距離不足,第一層分析,,Design,第一層分析,,Test,第二層分析,第三層分析,第二層分析,第三層分析,鎖螺絲過長,套管短,零件本體大Layout 面積小,測試條件設錯,O/I寫錯,測試線接錯,11 of 33,Hi-Pot,,Failure,,Analysis,Fault Tree Analysis For Hi-Pot
13、 Failure,5.,,板,,邊,,零,,件,,傾,,斜,,踫,,Case,,,造,,成,,安,,規(guī),,距,,離,,不,,夠,b.,,Socket,,上,,Y,,電,,容,,線,,腳,,靠,,近,,馬,,口,,鐵,a.,,Socket,,FG,,線,,漏,,焊,Process,4.,,錫,,面,,3.,,正,,面,,裝,,插,2.,,組,,立,1.,,加,,工,,不,,良,d.,,錫,,面,,短,,路,,︵,,錫,,珠,,,錫,,渣,,︶,c.,,線,,腳,,過,,長,b.,,漏,,焊,,︵,,Y,,電,,容,,︶,a.,,異,,物,c.,,零,,件,,插,,歪,,斜,零,,件,,變,,形,
14、碰,,Case,碰,,T1,碰,,H/S,相,,互,,碰,,撞,b.,,零,,件,,面,,有,,異,,物,a.,,無,,線,,尾,h.,,鎖,,絲,,未,,鎖,,緊,,或,,漏,,鎖,g.,,掉,,金,,屬,,物,,進,,產(chǎn),,品,f.,,絕,,緣,,片,,放,,置,,不,,當,,或,,漏,,裝,d.,,PCB,,沒,,有,,卡,,到位,c.,,組,,立,,時,,,B+,,B-,,線,,壓,,傷,,壓,,破,,b.,,絕,,緣,,片,,膠,,布,,破,a.,,FG,,線,,有,,無,,Touch,,任,,何,,零,,件,c.,,膠,,布,,沒,,貼,,到,,位,Design,2.,,元,,件,
15、,之,,間,,安,,規(guī),,距,,離,,不夠,,3.,,Arcing,,規(guī),,格,,過,,嚴,c.,,鎖,,螺,,絲,,過,,長,b.,,套,,管,,短,a.,,原,,件,,本,,體,,大,,Layout,,面,,積,,小,4.,,板,,邊,,零,,件,,與,,Case,,安,,規(guī),,距,,離,,不,,夠,,1.,,Layout,,安,,規(guī),,距,,離,,不,,夠,Material,9.,,變,,壓,,器,,PFC,,︵,,電,,感,,︶,,8.,,膠,,雜,,質(zhì),,過,,多,7.,,Y,,電,,容,,不,,良,6.,,線,,材,,Power,,Cable,,破,5.,,PCB,4.,,EMI,
16、,Socket,3.,,Case,2.,,接,,地,,小,,黃,,豆,,電,,容,,耐,,壓,,不,,夠,,c.,,有,,毛,,刺,b.,,耳,,掛,,有,,凸,,起,a.,,碎,,屑,b.,,本,,身,,耐,,壓,,不,,夠,a.,,FG,,線,,氧,,化,,不,,吃,,錫,b.,,Trace,,近,,似,,短,,路,,或,,開,,路,a.,,PCB,,受,,潮,e.,,絕,,緣 Tape,,破,d.,,零,,件,,本,,體,,歪,,斜,c.,,焊,,點,,過,,大,,,造,,成,,錫,,間,,賜,,破,,絕,,緣,,層,b.,,引,,線,,腳,,超,,出,,base,a.,,絕,,緣,,膠
17、,,布,,位,,置,,不,,恰,,當,1.,,光,,藕,,合,,器,,不,,良,,e.,,O/I,,寫,,錯,,誤,Test,2.,,儀,,器,,設,,定,,1.,,儀,,器,c.,,測,,試,,條,,件,,設,,置,,錯,,誤,b.,,O/I,,寫,,錯,,誤,a.,,測,,試,,線,,接,,錯,b.,,儀,,器,,本,,身,,電,,壓,,頻,,率,,誤,,差,,大,a.,,接,,觸,,不,,良,f.,,本,,身,,繞,,線,,造,,成,,Arcing,,過,,大,其,,他,2.,,接,,地,,銅,,箔,,被,,燒,,斷,,3.,,接,,地,,跳,,線,,斷,,4.,,未,,依,,O/I,,
18、作,,業(yè),1.,,Socket,,Y,,電,,容,,線,,腳,,斷,5.,,油,,墨,,,黑,,色,,Mark,,筆,,,在,,初,,級,,側(cè),,導,,電,,,,12 of 33,Part Failure Mode Effect(s) Cause(s) Current or Action(s) to Area or Action(s),,Name,* Control(s)
19、 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,
20、,,,,,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,This column is used to list the par
21、t name,,and function. List all the functions for the functional block,FMEA 格式逐項解說,1.,2.,10.,4.,3.,5.,6.,8.,7.,9.,12.,11.,15.,14.,13.,13 of 33,Part Failure Mode Effect(s) Cause(s) Current or Action(s) to Area or Action(
22、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
23、 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,
24、Detection,RPN,RPN,2.,In the failure mode column, list each of the failure,,modes for the function.,FMEA 格式逐項解說,1.,10.,4.,3.,5.,6.,8.,7.,9.,12.,11.,15.,14.,13.,14 of 33,Part Failure Mode Effect(s) Cause(s) Current or Action(s) to
25、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,
26、,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,Occurre
27、nce,Detection,Detection,RPN,RPN,Occurrence,3.,List the effects of failure for each of the,,failure modes.,FMEA 格式逐項解說,1.,10.,4.,2.,5.,6.,8.,7.,9.,12.,11.,15.,14.,13.,15 of 33,Part Failure Mode Effect(s) Cause(s) Current or Action(s) to
28、 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 B
29、attery,,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,
30、Occurrence,Occurrence,Detection,Detection,RPN,RPN,For each one of the effects, list the,,severity (scale from 1 to 10),4.,FMEA 格式逐項解說,1.,10.,3.,2.,5.,6.,8.,7.,9.,12.,11.,15.,14.,13.,16 of 33,符合需求 ,,17 of 33,Part Failure Mode Effect(s) Cause(s) Current o
31、r 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 B
32、attery,,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,,bat
33、tery,,Faults,,,,Severity,Severity,Occurrence,Occurrence,Detection,Detection,RPN,RPN,The Class column is optional. It is,,typically used if the severity is 9 or 10.,5.,FMEA 格式逐項解說,1.,10.,3.,2.,4.,6.,8.,7.,9.,12.,11.,15.,14.,13.,18 of 33,Part Failure Mode Effect(s) Cause(
34、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
35、 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. wro
36、ng,,,,Unable to,,detect,,battery,,Faults,,,,Severity,Severity,Occurrence,Occurrence,Detection,Detection,RPN,RPN,,In the Cause column, list the causes,,for each failure mode,6.,FMEA 格式逐項解說,1.,10.,3.,2.,4.,5.,8.,7.,9.,12.,11.,15.,14.,13.,19 of 33,FMEA Model,Linking Failure Mode to,,Cause and Effect,Ca
37、use,Failure Mode,,(Defect),Effect,20 of 33,Part Failure Mode Effect(s) Cause(s) Current or Action(s) to Area or Action(s),,Name,* Control(s) be taken Individual t
38、aken,,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,,accura
39、tely dissatisfaction failure,,ID status,,Battery Connections,,damage spec. wrong,,,,Unable to,,detect,,battery,,Faults,,,,Severity,Severity,Occurrence,Occurrence,Detection,Detection,RPN,RPN,Estimate the likelihood of the,,“causes” happening on a “1 to,,10” scale. The hig
40、her the,,number the more likely the,,“causes” will occur.,7.,FMEA 格式逐項解說,1.,10.,3.,2.,4.,5.,8.,6.,9.,12.,11.,15.,14.,13.,21 of 33,22 of 33,Part Failure Mode Effect(s) Cause(s) Current or Action(s) to Area or Action(s),,
41、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 co
42、nnections,,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,Dete
43、ction,RPN,RPN,List the prevention, design validation/,,verification, or other activities which,,will assure the design adequacy for the,,failure mode and/or cause / mechanism,,under consideration.,,,Tests,,Design reviews,,,Mathematical studies,,,Fail/safe (Example: redundant,,power supplies),8.,FMEA
44、 格式逐項解說,1.,10.,3.,2.,5.,4.,6.,7.,9.,12.,11.,15.,14.,13.,23 of 33,Part Failure Mode Effect(s) Cause(s) Current or Action(s) to Area or Action(s),,Name,* Control(s) be taken
45、 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
46、 Software,,accurately dissatisfaction failure,,ID status,,Battery Connections,,damage spec. wrong,,,,Unable to,,detect,,battery,,Faults,,,,Severity,Severity,Occurrence,Occurrence,Detection,Detection,RPN,RPN,Estimate the likelihood of the,,detection on a “1 to 10” sca
47、le. The lower the number the more likely the cause will be detected.,9.,FMEA 格式逐項解說,1.,10.,3.,2.,5.,4.,8.,7.,6.,12.,11.,15.,14.,13.,24 of 33,25 of 33,Part Failure Mode Effect(s) Cause(s) Current or Action(s) to Area or
48、 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
49、 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,De
50、tection,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)
51、 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
52、 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,,,,Una
53、ble 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 Failur
54、e 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
55、 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 Co
56、nnections,,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 completion,,Target date could be established,,by development program
57、,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
58、 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 Cust
59、omer 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 ent
60、er 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,*
61、 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
62、,,,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 rea
63、ssessing 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)
64、 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
65、 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,
- 溫馨提示:
1: 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
2: 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
3.本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預覽,若沒有圖紙預覽就沒有圖紙。
4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
5. 裝配圖網(wǎng)僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負責。
6. 下載文件中如有侵權(quán)或不適當內(nèi)容,請與我們聯(lián)系,我們立即糾正。
7. 本站不保證下載資源的準確性、安全性和完整性, 同時也不承擔用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。
最新文檔
- 110中國人民警察節(jié)(筑牢忠誠警魂感受別樣警彩)
- 2025正字當頭廉字入心爭當公安隊伍鐵軍
- XX國企干部警示教育片觀后感筑牢信仰之基堅守廉潔底線
- 2025做擔當時代大任的中國青年P(guān)PT青年思想教育微黨課
- 2025新年工作部署會圍繞六個干字提要求
- XX地區(qū)中小學期末考試經(jīng)驗總結(jié)(認真復習輕松應考)
- 支部書記上黨課筑牢清廉信念為高質(zhì)量發(fā)展營造風清氣正的環(huán)境
- 冬季消防安全知識培訓冬季用電防火安全
- 2025加強政治引領(政治引領是現(xiàn)代政黨的重要功能)
- 主播直播培訓直播技巧與方法
- 2025六廉六進持續(xù)涵養(yǎng)良好政治生態(tài)
- 員工職業(yè)生涯規(guī)劃方案制定個人職業(yè)生涯規(guī)劃
- 2024年XX地區(qū)黨建引領鄉(xiāng)村振興工作總結(jié)
- XX中小學期末考試經(jīng)驗總結(jié)(認真復習輕松應考)
- 幼兒園期末家長會長長的路慢慢地走