Should We Ban the Term Failure?
Abstract
Chris and Fred discuss the term ‘failure’ … and should we use it?
ᐅ Play Episode
Your Reliability Engineering Professional Development Site
by Christopher Jackson Leave a Comment
Chris and Fred discuss the term ‘failure’ … and should we use it?
ᐅ Play Episode
Kirk and Fred discussing a recent failure of an electric range/oven and the troubleshooting, FA and repair. See the show notes to see photos and details of the failure analysis.
ᐅ Play Episode
by James Kovacevic Leave a Comment
We’re excited to have Jim Fitch, the CEO of Noria Corporation and the director of ICML, back. He previously explored ICML 55, the standard around lubrication programs. ICML was founded about 18 years ago as a non-profit. It was to provide certification resources for organizations and individuals who needed certificates for completing their training. Noria Corporation is a for-profit services company that’s 22 years old. It provides training and consulting services globally, relating to oil analysis and lubrication. They also offer transformation services. These are for plants moving from their current state to something closer to the greatest reference state. Noria also publishes machine lubrication magazines among other e-publications. They’re also a conferencing company.
In this episode, we covered:
Kirk discusses the many times his home appliances failing and doing his own failure analysis and the limitations.
ᐅ Play Episode
by Adam Bahret Leave a Comment
Adam discusses why the reliability engineer discipline is unique in that it encourages the “Celebration of Failures”
ᐅ Play Episode
by Carl S. Carlson Leave a Comment
Carl and Fred discussing the importance of discovering and understanding failures during product development.
ᐅ Play Episode
by Christopher Jackson Leave a Comment
Chris and Fred discuss what it means to ‘fail.’ Not from a personal sense! But what does it mean for your product to fail. Engineering or design specifications describe what the product or system must do. So does failure simply occur when the product can no longer meet all these specifications? What if your product or system meets all these criteria – but your customer ‘thinks’ is has failed? We have seen many instances where a group of people who design and make products will vehemently argue that even if the customer thinks something has failed when it meets the specifications, then nothing is wrong. Is it? What do you think the customer will do? Do you think they will be ‘happy’? If this is a problem you come across, then listen to this podcast.
ᐅ Play Episode
by Christopher Jackson Leave a Comment
Chris and Fred discuss what happens when you have failure … but don’t know why. This is a challenging problem that most reliability engineers will face throughout their career. You will always need to use an objective, structured and strategic approach. And you will often find that a lot of information is at your fingertips – you may be able to create a very short list of candidate root causes without having to test. Effort without direction won’t solve problems. If you want to learn more about solving this really challenging problems, then listen to this podcast.
ᐅ Play Episode
by James Kovacevic Leave a Comment
Failure data is very important for leaders to make effective and efficient decisions. That’s why they are always looking for industry best practices and new implementation techniques to understand failure codes and failure modes in a better way. The organizations always focus on understanding failure codes so that they can design their CMMS. They always configure their CMMS to better analyze the failure data. They have a process in place that allows them to run failure data against different fields based on the failure codes. Failure data must be synchronized to hold RCM analysis results. CMMS can be built in way that it perfectly serves the purpose.
In this episode, we covered:
Kirk and Fred discussing a real case of product failure for a OEM sub-supplier and determining how to isolate the cause
ᐅ Play Episode
by Christopher Jackson Leave a Comment
Chris and Fred discussing how different organizations deal with failures. Failures are a ‘bad’ thing in that a system doesn’t do what you hoped it would. But what about failures that occur during the design or production process? This is different. If you have scope to improve your system, then failures that you can analyze in a laboratory or test bed are invaluable. They, more than any other event, will help you understand the vulnerabilities of your system. And you must actively seek vulnerability to improve reliability. But if you are looking for failures, you must first admit that your system is vulnerable. And that is difficult for many people to do.
ᐅ Play Episode
by Christopher Jackson Leave a Comment
Chris and Fred discussing the recent Russian Soyuz rocket failure. With the retirement of NASA’s space shuttle fleet, the Soyuz rocket and spacecraft are now the only viable way to launch humans into space. The 1960s Soyuz rocket propels the 1960s Soyuz spacecraft into orbit … and to be clear it is only the rocket that failed. The Soyuz spacecraft successfully aborted the launch keep the crew safe. The Soyuz rocket has long been the yardstick of rocket safety – it easily has the most impressive reliability track record. But should this recent failure change that perception? And how can the Soyuz system still be operating when other programs have come and gone, primarily due to safety and reliability? This podcast attempts to answer some of these questions.
ᐅ Play Episode
Kirk and Fred discussing the difficulty of keeping the failure data and details of past failures of products in order to make more reliable products.
ᐅ Play Episode
James and Fred discussing resistance to change within an organization, sometimes based on poor assumptions and misunderstood theorems.
ᐅ Play Episode
Kirk and Fred discussing the article that Fred recently posted and the strategy of making a spare parts and service a source of the majority of programs profit.
ᐅ Play Episode