没有人想要有缺陷的产品。缺陷是昂贵,令人沮丧的,并且对公司的声誉造成了破坏。
作为项目经理,您将尝试使用所有可能的技术避免可交付的失败。一种是“失败模式和效果分析”或FMEA。这可以帮助您找到产品的潜在问题,并允许您采取纠正措施。
FMEA可以改善您的系统,设计过程和生产过程。
This technique is also known as “Failure Modes Effects and Criticality Analysis” (FMECA) or sometimes simply “failure modes.”
FMEA is a straightforward, qualitative technique that involves brainstorming with experts and listing their comments in a table. It is similar to the process of creating aprobability and impact matrix.
在这里,专家确定了产品故障的可能原因,发生的机会,影响,检测失败的容易性等。这些意见在表中注明了这些意见以进行进一步审查。
这可以帮助您确定许多可能影响可交付的故障。
何时使用FMEA
FMEA对于避免未来错误并提高过程和产品的可靠性很有用。您可以在以下情况下使用它:
- 在开发新产品或过程中。
- Before you make changes to a product or process.
- 在确定过程或产品中的错误之后。
- 收到客户的众多投诉时。
- 当销售支持成本异常高时。
- 当公司的信誉受到威胁时。
This technique is not confined to any industry or technology.
如何使用FMEA
This technique requires expert judgment. You will call experts for one or more brainstorming sessions. They will help you identify, collect, and evaluate the potential defects, their causes, and the impact.
专家应属于所有功能领域,以便您可以覆盖完整的产品生命周期.
Example
您可以使用下表记录专家的输入。您将更多地注意分析可能导致设备故障的原因。
FMEA技术使用三个参数:严重性,发生和检测。
严重程度(SEV)显示了用户缺陷的苛刻性。发生(OCC)预测问题可能发生的频率。检测(DET)表示您很容易找到问题。
For each potential error or defect, experts will assign a value from one to ten, where one is extremely unlikely and ten is extremely likely. After the brainstorming session ends, you will compile the list of problems, causes, and their ratings. Afterward, you will enter this information into a table.
最后,您将每个缺陷的严重程度,发生和检测乘以生成RPN。这代表风险概率编号,并为每个缺陷提供总体风险影响评分。在我们的示例表中,故障的RPN为81。
在为所有可能的缺陷和失败生成RPN后,您将决定每个风险水平的阈值。阈值可以高,中等或低。使用RPN编号,您将确定缺陷原因是高,中还是低级优先级。
You will work on the high-priority RPNs to mitigate or eliminate defects.
For example, the second table shows your recommended action for an identified failure, who will be responsible for the action, and when you should implement it.
您将记录此故障以及一旦发生的动作。
如何实施FMEA
您有可能的错误列表及其潜在的纠正措施。现在,您将向您的团队成员分配责任执行这些行动,以便可以减少这些错误的RPN。
You will review them again after the corrective actions have been implemented to assess the effectiveness of an action plan. If necessary, a new FMEA will be generated to re-assess the risks and defects.
Use the帕累托法while using this technique. Focus on the minority of causes creating most of the issues or defects. This provides the most significant impact while using the least resources. You can take on the other defects, as resources permit, once these high-impact issues are resolved.
You can plan a new corrective action to mitigate the problem if you see that a particular issue is not being resolved currently.
FMEA的好处
FMEA的一些好处是:
- Improved and more reliable products
- 较少的售后支持
- Increased customer satisfaction
- 改善品牌声誉
- 减少失败和保修费用
- Maximizing profits by reducing after-sales expenses
结论
FMEA是一种主动技术,可帮助您在发生之前识别潜在的缺陷和失败。这是一种很棒的定性方法,如果正确使用,可以为您的组织带来许多好处。尽管由于各种参与,这种技术正在耗时stakeholders, it will lead your project to a successful ending.
请在评论部分中分享您在失败模式和效果分析(FMEA)技术方面的经验。
出色的 !!非常容易理解。
Sir, I have done my Diploma in Mechanical Engineering & presently doing AMIE course. For AMIE course I have selected ‘Process FMEA for TATA Hybrid bus’ at ACGL-Goa as my project. Can I do project individually by collecting the required data from company or it is a team project?
I cannot say anything on it. Please consult with your mentor.
非常有效,非常清楚。谢谢您非常清楚地了解。
You are welcome Santhosh.
您能为飞机的FMEA举一个例子吗?还是它的链接?
Sorry Sara, I don’t have any FMEA on aircraft.
我特别喜欢将风险与经济后果联系起来的想法。
多年来,我遇到的另一个问题在于在评估新过程或系统时确定发生的问题,真正的失败率未知。
If the team is composed of individuals with prior understanding of similar systems or historic performance, it is easy to estimate the new occurrence rating by examining historic experience. Often though, the default is to rank occurrence with a high number due to lack of experience.
In a risk adverse environment, the result is that high risk is everywhere due to high occurrence or detection numbers. The FMEA then becomes unmanageable and loses any advantage of prioritization.
http://manufacturing.cioreview.com/whitepaper/why-is-fmea-cost-effective-wid-577.html
Well said John.
Very good explanation.
谢谢Deepak for your comment.
Brief but comprehensive..Easy to understand..Thank u :-) Expecting more topics from you:-)
谢谢Jeya for your comment.
让我知道您要我写什么话题。
欢迎:)您可以在APQP阶段,根本原因分析和为什么分析上写信
我已经注意到您的要求,肯定会撰写有关这些主题的博客文章。
Thank you..
Hi,
Can you please differentiate between occurrence and detection. According to me, occurrence means issue has occurred but not detected by people. Detection means issue occurred and also got detected . Please clarify
你是对的。
Here the occurrence mean how many frequently this issue is likely to happen, and detection implies how easily you can detect it.
Excellent. Very short and to the point. Very easy to learn and implement. Please continue to educate us.
感谢您的评论,并访问Jay。
好话题。解释很好。谢谢
不客气。
您在准备这些博客方面做得非常出色。感谢您准备他们的简洁明了。
谢谢Sara for your comment.
Very clear and concise, thanks so very much.
不客气的Bonos。
非常好的会议。简单有效。thanks
You are welcome Mathew for stopping by and leaving your comment.
良好而简单。
谢谢Venkatesh.
非常好的会议。简单有效。
谢谢
欢迎您Varun。