【正文】
Step by StepFMEA。 Step by StepFMEA。 Step by StepFMEA。 Step by StepFMEA。 Step by StepFMEA。 逐步展開Failure Mode Effects Analysis, ContinuedFMEA分析, 續(xù)前頁Define the scope for the FMEA, cont.定義FMEA的范圍, 續(xù)前頁Step 12Identify corrective action步驟十二決定矯正措施12 Identify Corrective ActionIn this step you identify the corrective actions needed to eliminate / control the causes, and reduce the risk level to or below the agreed upon threshold.There will be times when you cannot work on the root cause。 逐步展開Failure Mode Effects Analysis, ContinuedFMEA分析, 中國最大的資料庫下載 Define the scope for the FMEA, cont.定義FMEA的范圍, 續(xù)前頁Step 11Prioritize based on RPN and severity, or as requiredby customer步驟十一依據(jù)風(fēng)險等級數(shù)和嚴(yán)重性, 或客戶要求排定優(yōu)先次序11 Prioritize based on RPN and severity, or as required by customerArrive at the order in which you will start addressing the failure modes and causes for corrective action. Although RPN and severity based prioritization seems the most logical, your decision to proceed must be made with customer input. This step is easily acplished by sorting the data, in descending order. You can do this within each failure mode to maintain data integrity.Documentation on work sheet is important to ensure the whole team is in sync.依據(jù)風(fēng)險等級數(shù)和嚴(yán)重性, 或客戶要求排定優(yōu)先次序這個優(yōu)先次序是您將用以處理與矯正失效模式及原因. 雖然依據(jù)RPN與嚴(yán)重性所訂出的優(yōu)先次序看來是最合理的, 但您最後的決定必須要納入客戶的意見.這個步驟可以很容易的藉由將數(shù)據(jù)以由大到小的順序排列出來而完成. 您可以將這個步驟分別運用於每一個失效模式之中以保持資料的完整性.將作業(yè)過程與結(jié)果記錄於工作表上以確保整個小組的步調(diào)一致是很重要的.FMEA。 逐步展開Cumulative RPN Curve累計RPN曲線80% of Cumulative RPN80%累計RPNCumulative RPN累計RPNCauses原因Failure Mode Effects Analysis, ContinuedFMEA分析, 續(xù)前頁10 Decide on a threshold RPN, without ignoring high severity failure modes在不勿視高嚴(yán)重性失效模式項目前提之下決定RPN門檻 Example using RPN=200 for each failure mode:以RPN = 200作為失效模式門檻的舉例FMEA。 逐步展開Failure Mode Effects Analysis, ContinuedFMEA分析, 續(xù)前頁 Define the scope for the FMEA, cont.定義FMEA的范圍, 續(xù)前頁Step 10Decide on a threshold RPN, without ignoring high severity failure modes步驟十在不勿視高嚴(yán)重性失效模式項目前提之下決定RPN門坎10 Decide on a threshold RPN, without ignoring high severity failure modes在不勿視高嚴(yán)重性失效模式項目前提之下決定RPN門檻 Example using Pareto Chart:運用柏拉圖的舉例:FMEA。 逐步展開8 Assign ratings for Severity, Occurrence, and Detection列出嚴(yán)重性, 發(fā)生機(jī)率, 和偵測能力的等級Example: 舉例Failure Mode Effects Analysis, ContinuedFMEA分析, 續(xù)前頁數(shù)目Define the scope for the FMEA, cont.定義FMEA的范圍, 續(xù)前頁Step 9Calculate RPN (Risk Priority Number)步驟九計算RPN (風(fēng)險等級數(shù))9 Calculate RPN (Risk Priority Number)Simply assigning ratings for Severity, Occurrence, and Detection doesn’t help quantify the risk into a single measurable value. Multiplying the rating scores thus fills this gap. Note that in this approach we have maintained equal weight for each of the three S, O, and D.計算 RPN (Risk Priority Number)單單是列出嚴(yán)重性, 發(fā)生機(jī)率, 和偵測能力的等級無助於將風(fēng)險量化成為一個可評估數(shù)值, 將這些評比等級分?jǐn)?shù)相乘可以達(dá)到這個目的. 請注意在這個方法中三個 S, O, 和 D的加權(quán)值是一樣的. Example: 舉例 FMEA。 逐步展開7 List the effects, causes, and current controls for each failure mode列出每一個失效模式的所有影響, 原因, 與目前的管制辦法 Example: 舉例Failure Mode Effects Analysis, ContinuedFMEA分析, 續(xù)前頁 Define the scope for the FMEA, cont.定義FMEA的范圍, 續(xù)前頁Step 8Assign ratings for Severity, Occurrence, and DetectionWork to reach team consensus步驟八列出嚴(yán)重性, 發(fā)生機(jī)率, 和偵測能力的評比等級致力于達(dá)成小組共識FMEA。 逐步展開5 Develop rating scales for Severity, Occurrence,and Detection Example from Process FMEA:Severity effect1 – No effect on operators, users, or current and down stream processes2 – Minor rework at current step / no dysfunction introduced in product3 – Rework at current / subsequent steps causing some delayed schedules, or product is rendered partially dysfunctional4 – Heavy rework at subsequent operation, major delays in schedules, or product function is severely impacted5 – Risk of injury or fatal Occurrence cause1 – Very rare occurrence, X00 ppb or once in 3 to 5 years2 – Rare occurrence, X to X000 ppm, 2 to 5 occurrences in 3 years3 – Frequent occurrence, X000 to X0,000 ppm, 1 to 3 occurrences in 1 year4 – High frequency of occurrence, X0,000 to XM ppm, over 4 occurrences per year5 – Almost certainDetection – failure mode (or cause in some cases) 1 – Certain to be detected, before any measurable damage is done2 – Automated inspection / detection or strong process controls exist at current step or within the system boundaries3 – Sampling plans used for inspection