When a part breaks unexpectedly, it usually sets off a flurry of activity. Often, a team is formed and charged with finding the root cause of the failure. In my career, I have led or been a member of many failure analysis teams. Based on my experience, there are five mistakes that engineers often make when investigating failures. (I know because I've made them all myself.) Recognizing these mistakes can help you avoid them.
1. Looking at a part in isolation. As a materials engineer, people often send me a broken part in a cardboard box and ask, "Why did it break?" Of course, if the part had been in a cardboard box the whole time, it's unlikely that it would have broken.
Although there are many things that can be learned by inspecting a failed part, the part itself rarely tells the whole story. It's important to understand the mechanical system to which the part belongs and the part's role in that system. What loads does the part feel? Where do the loads come from? What might cause the loads to be higher or lower? It's also important to understand the environment in which the mechanical system operates. In what ways might the operating environment differ from what was anticipated in design?
Remember, no part ever fails by itself. It fails as a part of a given mechanical system under a given set of environmental conditions.
2. Focusing on conformance to specifications rather than root cause. When a part breaks, one of the first questions asked is, "Did it meet the print?" Of course, it's important to establish whether or not the part conformed with the design requirements.
But finding a non-conformance is not the same as finding the root cause of the failure. If a part is found to be defective, it's important to understand what role (if any) the defect played in the failure. In some cases, a defect may be a red herring, which leads you away from the root cause. In other cases, early failure of a defective part may reveal an underlying problem, which would also cause non-defective parts to fail over a longer period of time.
There's another reason not to focus excessively on the issue of conformance or non-conformance: It can result in a confrontational relationship with parts suppliers. This can undermine cooperation, which may be necessary for the success of the investigation. Failure analysis should always be about solving problems, not assigning blame. Of course, this is not to say that suppliers shouldn't correct non-conformances, or that there shouldn't be consequences for suppliers who consistently provide non-conforming parts. But this should be separate from the work of the failure analysis team.
I worked with an engineer who said "If I can break it, I can fix it." meaning if he can demonstrate the exact failure, he has a pretty good handle on what failed and how to keep it fixed.
@Tigertom: That's a very good point. For those of us who are materials engineers, there's a temptation not only to take apart assemblies, but to cut parts up so that we can look at the microstructure. We end up with beautiful micrographs, but the original part falls victim to the chop saw.
As you point out, it's very important to get all of the information you can before taking apart an assembly. Once you get to the component level, it's also important to get all of the information you can from non-destructive testing before proceeding to destructive testing.
More than once, I've been in the position of realizing that I wanted to check something on a part after I had already performed a destructive test on it. As Homer Simpson says: D'oh!
Can I suggest one more big mistake to add to your list?
6. Quickly dismantle a failed assembly. If you have an assembly that doesn't work, it's very tempting to take it apart to see what's broken. You probably have one or two theories as to what might be broken inside. But if you dismantle it and nothing is broken, then you're in real trouble. When you re-assemble, the chances are it will work perfectly, and you've destroyed the bug you've been commissioned to identify.
Instead, before you dismantle, get every relevant bit of information you can from the failed assembly. What are the resistances and capacitances at the terminals, or what is the frictional torque to move it, or how much does it weigh, or does it rattle when shaken etc. etc. If possible, x-ray. Develop a list of failure modes that could produce the observed symptoms, and see if you can prove or disprove any before dismantling. As you dismantle, measure the torque on bolts, look for dirt or misassembled components and for parts that have moved to unexpected positions. Once the disassembly is complete, all these clues will have been lost.
Dave. I couldn't agree more. Thanks for a dose of sanity. I too have been part of similar investigative teams. As noted, it seems that one of the biggest issues that pops up is getting management (or the customer) to be patient while the investigation proceeds. There are no shortcuts for a good analysis.
Great Article, Dave.I found myself thinking back to many different scenarios over the years, after reading each of your points, 1 thru 5.One which loudly resonates is touched upon in both your #2, andyour #5 – jumping to conclusions, and management pressure to fix it quickly. Many times, I have dealt with a manager who forced his suggestion to be the fix, without going thru the necessary trials to prove it.I preach again and again, "a sample of one doth not constitute a statistical lot".
Product failure analysis covers two different types of products, those that have been working properly for a long time, and those that don't have a history of having worked. The failure analysis of the two types would be a bit different, at least after the start. The first question would be "did it ever work correctly?", since if it did not, then the design may be suspect. But it is also possible that the design is good but the part was not made to the design. Amazingly, not every design is produced faithfully the first time.
The conclusion, then, is that in order to correctly understand why some part failed, it is mandatory to understand just how the system including that part was supposed to work. Having an adequate understanding of a system is seldom a trivial task, but it is important. A part will fail because it was subjected to forces beyond it's strengths. That is the fact in a majority of instances. At that point the question becomes one of: was the part made to the design specification, or was the specification adequate? Again, in order to be able to answer correctly there must be an adequate understanding of the system.
Interestingly enough, sometimes the problem is caused by there not being an adequuate understanding of the system from the very beginning. And I am not sure how to solve that problem.
One of the other key points I think when solving problems is not to focus on one area or not focus on one area. If you are in design don't automatically focus on if the part is to print and then point the finger at quality. If you are in quality don't ignore if the part is to print and focus on the design.
True problem solving is a skill that takes a lot of patience and discipline. You must let the data lead you but still be open to engineering decisions and insight. As well as remembering the problem is that the part is breaking. We are all together in trying to solve this problem. Not point fingers at who caused the problem.
An analysis of what’s needed to implement Design for Disassembly and Design for Recycling results in eight strategies engineers can use to design an intentional end-of-life stage into their products.
Government regulations, coupled with growing consumer sensitivity about data and identity theft, require that data storage organizations demonstrate proper protection and due diligence in protecting sensitive information stored inside datacenter enclosures.
When a crane doesn't have a monitoring system, crane owners schedule service every six months and simply scrap the parts they replace, even if a part has had little use and doesn't need replacing. This can cost thousands.
From Dell / Intel® New Paradigms in Design Work Scott Hamilton, vertical market strategist for Dell Precision workstations, 5/2/2013 3
Early in my career, I worked as a draftsman and remember the days of drawing on vellum with numbered pencils and Mylar with plastic lead. This was a fun experience in the sense that I ...
I've been using workstations for more than 10 years and love finding ways to get more performance from my system. With demanding professional applications that require more power each ...
A lasting memory from my first job as an engineer in an auto assembly plant is standing on hard concrete at six in the morning, vending-machine coffee clutched in hand, listening to ...
A quick look into the merger of two powerhouse 3D printing OEMs and the new leader in rapid prototyping solutions, Stratasys. The industrial revolution is now led by 3D printing and engineers are given the opportunity to fully maximize their design capabilities, reduce their time-to-market and functionally test prototypes cheaper, faster and easier. Bruce Bradshaw, Director of Marketing in North America, will explore the large product offering and variety of materials that will help CAD designers articulate their product design with actual, physical prototypes. This broadcast will dive deep into technical information including application specific stories from real world customers and their experiences with 3D printing. 3D Printing is
To save this item to your list of favorite Design News content so you can find it later in your Profile page, click the "Save It" button next to the item.
If you found this interesting or useful, please use the links to the services below to share it with other readers. You will need a free account with each service to share an item via that service.
Tweet This
9 
