IMHO it's futile to try to evaluate an FMEA on it's own. As a tool used within the overall product/process development process, it's going to be difficult to separate out. If the previous work/tools are flawed, then the FMEA will be similarly flawed. For example, the (product design) FMEA is normally developed from the customer, regulatroy and organization's requirements. If the processes which develope those are flawed the resulting FMEA will not necessarily be any better. Similarly with the process FMEA; if the process flow is inaccurate the FMEA will be too, and subsequently so will the Control Plans (for both phases).
I posed the question as to why would anyone want to know this answer - to justify why they should be done? The justification is in looking at the ($$$) results of not doing them! Every organization can look at their failures and have someone say - "Didn't you know that was going to happen? It happened before............"
If I had a $1 for everytime I've heard that.......
I posed the question as to why would anyone want to know this answer - to justify why they should be done? The justification is in looking at the ($$$) results of not doing them! Every organization can look at their failures and have someone say - "Didn't you know that was going to happen? It happened before............"
If I had a $1 for everytime I've heard that.......

