Your Reliability Engineering Professional Development Site
“It was impossible to get a conversation going, everybody was talking too much.” – Yogi Berra
Based on actual surveys of FMEA team leaders, the most common concern is how to control discussion during team meetings. This article will provide insight into this critical facilitation skill, and is a companion to the previous article in this series: Facilitation Skill #1: – Encouraging Participation.
“If a man does not keep pace with his companions, perhaps it is because he hears a different drummer. Let him step to the music he hears, however measured or far away.” Henry David Thoreau
One of the most important skills in facilitating team meetings is to be able to encourage balanced participation by all team members.
“Team leadership is the secret that makes common people achieve uncommon results.” – Ifeanyi Onuoha
One of the key factors for successful application of FMEAs is skillful facilitation of FMEA teams. The skills needed for excellent facilitation are different from the skills needed to be a good FMEA team member. [Read more…]
FMEA has an important relationship with risk management. This article provides an example of this relationship.
The suggested sequence is to first read the article “Relationship between FMEA and Risk Management” to learn about the interactions between FMEA and Risk Management at a high level. [Read more…]
“If no one ever took risks, Michelangelo would have painted the Sistine floor.” – Neil Simon
FMEA and Risk Management are two distinct bodies of knowledge. This article explores some of the interactions between these two important methods. It is not intended to be a complete analysis of the similarities, differences, and linkages between FMEA and risk management. Rather, it is a high-level overview.
“Many ideas grow better when transplanted into another mind than the one where they sprang up.”
Oliver Wendell Holmes
In the international FMEA community, one of the hot topics is how much of an FMEA can be automated versus how much needs to be team-based. Some experts say the future of FMEA requires an automated approach, as systems are getting more and more complex. Others say FMEA must always be grounded in a team of subject matter experts, narrowly focused on the highest priority issues.
In this article, I will share my thoughts on why FMEA needs to be team-based, and what elements can be prepopulated or automated.
“Number rules the universe.” – Pythagoras
Risk Priority Number (RPN) . . . by definition, a single number that represents relative risk for prioritizing issues in an FMEA. Sounds simple. But, how well does it work in practice? And, is there a better way?
This article highlights shortcomings and concerns when using RPN in FMEA, and discusses an alternative. It is a companion article to “Prioritizing risk for corrective actions in an FMEA.”
“Time is money” – Benjamin Franklin
One of the most common complaints about FMEAs is that they can take a long time to do. This article presents solutions to this challenge.
One of the most important concepts in designing for reliability is robust design. This article is a high-level overview of robust design and its relationship to FMEA.
“For the robust, an error is information.” Nassim Nicholas Taleb
“The danger which is least expected soonest comes to us.” Voltaire
This article discusses the application of Hazard Analysis, why it is used, and the similarities and differences with FMEA.
“My software never has bugs. It just develops random features.” Anonymous
More and more mechanical and electrical systems include software integration. The FMEA methodology applies very well to software as well as hardware. It is possible to include software functionality in the System FMEA as part of the functional descriptions. However, for complex software functionality such as embedded control systems, it may be useful to perform a separate software FMEA.
FMEAs are legal documents that support the demonstration of due care in product development. FMEA teams should ensure their worksheets are consistent with good legal practices for documents, and follow company legal guidelines.
“Common sense often makes good law.” William Orville Douglas, past Justice of the Supreme Court
[This is a companion article to “Using Design FMEAs to Identify Special Product Characteristics.” These two articles should be read in sequence.]
Identification and application of special product and process characteristics help to focus assembly and manufacturing processes on the most important areas, in order to achieve the right outcomes.
“Science is the process that takes us from confusion to understanding” – Brian Greene
One of the most important principles in reliability engineering and management is the differentiation between the vital few and the trivial many. The application of special product characteristics uses that principle.
“The whole of science is nothing more than the refinement of thinking.” – Albert Einstein
In last month’s article we discussed the most common FMEA mistakes and how to convert them into quality objectives. This month we will focus on how to audit FMEAs, using the FMEA quality objectives as a guideline.
“Twice and thrice over, as they say, good is it to repeat and review what is good.” Plato