Is Testing Always Necessary?
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
Fundamentals of Reliability Testing
Testing is expensive. Reliability testing is often complex. Let’s break down the basic of planning and conducting reliability testing the provides meaningful results in a cost-effective and timely manner. Let’s do testing right.
Dealing with the Occurrence of Failure
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
Do Reliability Testing That Adds Value, Informs Decisions, and Provides Information
Reliability testing is expensive, time-consuming, and fraught with errors. Is it really worth the effort? Is it necessary? Let’s explore relegating testing to only when absolutely necessary status. Let’s explore what you and your team can do to instead.