What Do I Do When MTBF is Imposed?
Chris and Fred discuss what happens when you can’t avoid having the MTBF imposed upon you – even if it is your own organization and not the customer. Perhaps you are told that ‘our competitors quote the MTBF … so we have to as well!’ But you can (sneakily) tailor test data to get whatever MTBF you want. You can make life easy on yourself by not challenging this paradigm (noting that you will most likely get an unhappy customer). But it is almost impossible to apportion MTBF goals to individual designers that even allow the motivated ones to create a reliable system. So what do you do? Listen to this podcast to help you on your reliability journey.
ᐅ Play Episode
What To Do When A Customer Requests MTBF
You have carefully crafted a detailed reliability goal including function, environment, probability, and duration, plus apportioned it to critical supplied subsystems and components. Your vendor decides to use MTBF instead.
What can you do? What should you do?
What is MTBF and Why You Shouldn’t Use It
Mean Time Between Failure or MTBF is almost universally recognized in maintenance, reliability, and asset management.
Why is that? And does it actually help an organization improve the reliability of their assets?
The answer is a resounding No.
ᐅ Play Episode
Exploring Alternatives to MTBF
You may already know my position on MTBF.
If not, in short, do not use MTBF at all, ever, in any form. So what should we use instead?
I suggest using reliability, the probability of success over a specific duration.
Let’s discuss what will work for you.