【正文】 (如：確認(rèn)，和 /或驗(yàn)證活動(dòng) ) Detection is the rank associated with the best detection control listed in the design control. In order to achieve a lower raking, generally the planned design control (., validation, and/or verification activities) has to be improved. 備註：在訂出難檢度評(píng)分後，小組應(yīng)再審查發(fā)生率，以確定發(fā)生率是否仍然恰當(dāng)。 Prevention: Prevent the cause/mechanism of failure or the failure mode from occurring, or reduce their rate of occurrence. 設(shè)計(jì) FMEA填寫說明 16. 現(xiàn)行設(shè)計(jì)管制 (續(xù) )(Current Design Controls(continued)): (2)檢測：檢測失效原因 /機(jī)制或失效模式，可藉由分析的方法或物理的方法在大批量生產(chǎn)前查出。 2. High severity ranking can sometimes be reduced by making design revisions that pensate or mitigate the resultant severity of failure. For example, “run flat tires” can mitigate the severity of a vehicle crash. 設(shè)計(jì) FMEA填寫說明 建議的 DFMEA嚴(yán)重度評(píng)估標(biāo)準(zhǔn) 效應(yīng) 標(biāo)準(zhǔn)效應(yīng)的嚴(yán)重度 等級(jí) 危險(xiǎn)無警訊 潛在的故障模式如果會(huì)毫無預(yù)警的影響到汽車的安全操作和 /或違反政府的規(guī)定 ,則屬於高度危險(xiǎn) 10 危險(xiǎn)有警訊 潛在的故障模式如果會(huì)有警訊的情況下 ,會(huì)影響到汽車的安全操作和 /或違反政府的規(guī)定 ,則屬於非常危險(xiǎn) 9 極高 汽車 /零組件無法操作 ,失去主要功能 8 高 汽車 /零組件還能運(yùn)作 ,但是性能降低 ,導(dǎo)致顧客非常不滿 7 中等 汽車 /零組件還能運(yùn)作 ,但是舒適 /便利的項(xiàng)目無法運(yùn)作 ,導(dǎo)致顧客感到不滿意 6 低 汽車 /零組件以及舒適 /便利的項(xiàng)目都能運(yùn)作 ,但是性能表現(xiàn)降低 ,讓顧客感到有些不滿意 5 極低 安裝加工 /發(fā)出異音項(xiàng)目不合格 ,而且大部分的顧問都注意到 (大於 75%) 4 輕微 安裝加工 /發(fā)生異音項(xiàng)目不合格 ,而且 50%顧客都注意到 3 極輕微 安裝加工 /發(fā)生異音項(xiàng)目不合格 ,而且挑剔的顧客會(huì)注意到 2 無 無影響 1 Suggested DFMEA Severity Evaluation Criteria Effect Criteria: Severity of Effect Ranking Hazardous without warning Very High severity ranking when a potential failure mode affects safe vehicle operation and/or involves nonpliance with government regulation without warning. 10 Hazardous with warning Very high severity ranking when a potential failure mode affects safe vehicle operation and/or involves nonpliance with government regulation with warning. 9 Very High Vehicle/item inoperable(loss of primary function). 8 High Vehicle/item operable but at reduced level of performance. Customer very dissatisfied. 7 Moderate Vehicle/item operable, but Comfort/Convenience item(s) inoperable. Customer dissatisfied. 6 Low Vehicle/item operable, but Comfort/Convenience item(s) operable at a reduced level of performance. Customer somewhat dissatisfied. 5 Very Low Fit Finish/Squeak Rattle item does not conform. Defect noticed by most customers (greater than 25%). 4 Minor Fit Finish/Squeak Rattle item does not conform. Defect noticed by 50% of customers 3 Very Minor Fit Finish/Squeak Rattle item does not conform. Defect noticed by discriminating customers (less than 25%). 2 None No discernible effect 1 (Classification) 對(duì)於需要近一步設(shè)計(jì)或製程管制的零組件，子系統(tǒng)或系統(tǒng)，可利用此欄位來區(qū)分特殊的產(chǎn)品特性 (關(guān)鍵、主要、重要、重點(diǎn)等 ). This column may be used to classify any special product characteristics (., critical, key, major, significant) for ponents, subsystems, or systems that may require additional design or process controls. 設(shè)計(jì) FMEA填寫說明 如果小組認(rèn)為對(duì)產(chǎn)品更幫助或管理階層更所要求時(shí)，本欄位亦可將工程評(píng)估高優(yōu)先順序模式者予以註記。一般在討論失效效應(yīng)時(shí)要清楚說明該功能是否會(huì)影響到安全性及法規(guī)的符合性並檢討失效發(fā)生時(shí)對(duì)於局部所產(chǎn)生的影響 ,然後循產(chǎn)品的組合架構(gòu)層次，逐層分析一直到最高層級(jí)人員、裝備所可能造成的影響。大前題是這種失效可能發(fā)生的，但不是一定會(huì)發(fā)生的。 (建議將所更小組成員名字、單位、電話號(hào)碼、地址等資料都紀(jì)錄在分發(fā)表上 ) List the names of the responsible individuals and departments that have the authority to identify and/or perform tasks. (It is remended that each team member?s name, department, telephone number, address, etc., be included on a distribution list.) 設(shè)計(jì) F M E A 填寫說明 9. 項(xiàng)目 /功能 (Item/Function): 填入正被分析的名稱和其他相關(guān)資料 (如編號(hào)、零件等級(jí) )。 For example, the front suspension subsystem is a subset of the chassis system. 因此子系統(tǒng) FMEA之重點(diǎn)在於確保構(gòu)成子系統(tǒng)的不同零組件的所更介面及相互作用皆能含蓋在內(nèi)。 Customer wants and needs – as may be determined from sources such as Quality Function Deployment(QFD), Vehicle Requirements Document, known product requirements, and/or manufacturing /assembly/service/recycling requirements – should be incorporated. 期望特性的定義越明確，就越容易識(shí)別潛在的失效模式，以採取預(yù)防 /矯正措施。 In its most rigorous form, an FMEA is a summary of the team?s thoughts (including an analysis of items that could go wrong based on experience) as a ponent, subsystem, or system is designed. ? 根據(jù)潛在失效模式對(duì)顧客的影響程度，列出優(yōu)先順序來，並據(jù)以建立設(shè)計(jì)、改善、開發(fā)及驗(yàn)收測試或分析之優(yōu)先順序系統(tǒng)。 FMEA input should be a team effort. 4. 小組成員應(yīng)由知識(shí)或技術(shù)豐富人員共同組成而非應(yīng)付式的派遣單位助理來權(quán)充人數(shù)。 Team member should be knowledgeable and technical expert, and not the assistants bined from each departments. FMEA的實(shí)施 (FMEA Implementation) 5. 適時(shí)性是成功實(shí)施 FMEA的重要因素之一，強(qiáng)調(diào)「事前的防範(fàn)」，而非事後「事故的補(bǔ)救」。 Developing a ranked list of potential failure modes according to their effect on the “customer”, thus establishing a priority system for design improvements, development, and validation testing/analysis. DFMEA簡介 (Introduction) 顧客的定義 (Customer Defined) 設(shè)計(jì) FMEA中“顧客”的定義，不僅僅是指“最終使用者” ，還包括負(fù)責(zé)車型設(shè)計(jì)或更高一級(jí)裝配過程設(shè)計(jì)的工程師 /小組，以及在生產(chǎn)過程中負(fù)責(zé)製造、裝配和售後服務(wù)的工程師。 The better the definition of desired characteristics, the easier it is to identify potential failure modes for preventive/corrective action. DFMEA的開發(fā) (Development) 設(shè)計(jì) FMEA填寫說明 1. FMEA編號(hào) ： 填入 FMEA文件編號(hào) ,以便追蹤查詢 。 Thus, the focus of the Subsystem FMEA is to ensure that all interfaces and interactions are covered among the various ponents that make up the subsystem. 設(shè)計(jì) FMEA填寫說明 零組件 FMEA的範(fàn)圍 (Component FMEA Scope): 一般而言，零組件 FMEA是著眼於子系統(tǒng)之次一層結(jié)構(gòu) . A Component FMEA is a generally an FMEA focused on the subset of a subsystem. 例如，支柱為前懸吊系統(tǒng)的一個(gè)零組件。利用工程圖面上標(biāo)明的名稱並顯示的設(shè)計(jì)等級(jí)。建議將以往 TGW(錯(cuò)誤的案例 )的研究，問題報(bào)告以及小組的“腦力激盪”的檢討作為出發(fā)點(diǎn)。 Potential effects of failure are defined as the effects of the failure mode on the function, as perceived by the customer. Describe the effects of the failure in terms of what the customer might notice or experience, remembering that the customer may be an internal customer as well as the ultimate end user. State clearly if the failure mode could impact safety or nonpliance to regulations. The effects should always be stated in terms of the specific system, subsystem, or ponent being analyzed. Remember that a hierarchical relationship exists between the ponent, subsystem, and system