Your Reliability Engineering Professional Development Site
A listing in reverse chronological order of articles by:
In a recent blog post, Seth Goin discussed the need for ongoing investment to maintain infrastructure. Whether a road or building or even your own skills, it takes regular care to avoid system failures or obsolesce. [Read more…]
Statistical process control, SPC, is a set of tools to enable monitoring the stability of a process. SPC is also the first step to checking process capability with measures such as Cpk. Many consider SPC a quality or manufacturing tool. Yet, having and maintaining a stable process is also essential to creating a reliable product. Let me explain why. [Read more…]
We made a cool “Reliability Culture” book launch website. The best part is that they let me put a big countdown timer on it like they have in James Bond films. Ya know, when the villain leaves James Bond in an easily escapable situation and there is a totally unnecessary timer building suspense to his (probably unlikely) demise.
The big difference being that in the Bond film we all know the big delivery will be before the timer goes off. In this situation the timer will go off and the delivery still won’t have happened because of Covid delays. Anyway it’s still cool.
But to save the day you can pre-order right now on Amazon or at Wiley right now.
-Adam
Very few reliability decisions are made by reliability engineers. Yet, reliability engineers are asked many questions concerning reliability. How reliable will this design be for customers? How will the system likely fail? How many failures should we expect next month?
How you answer these and the many other questions received does impact the reliability of your product or system. The information provided those that ask reliability related questions, with useful and practical information, can make better decisions which improves reliability performance.
An immediate purpose is to earn a living. You also may suggest the work is to improve the reliability of the product or system. Reduce downtime, reduce warranty, increase profit, etc.
That is fine for the overall purpose of reliability engineering work, yet in the day to day work, the specific task level, what is the purpose behind what we do?
There is an issue up for vote this year in my home state of Massachusetts. It’s called “Right to Repair.” The proposed law states that automotive manufacturers can not lock owners and independent repair shops out of vehicles on-board diagnostic computers. These are the arguments on either side of the issue:
Auto manufacturers don’t want independent repair shops completing work on their vehicles with technicians who are not factory trained. They are also concerned about repairs being completed with non-factory parts that could potentially be sub-standard. These manufacturers believe they should have control regarding repairs because they are held responsible when issues occur under warranty. So why is this an issue now?
Sometimes we can only test one use case before we ship our product. So what should it be? Should it be the hardest use case? The nominal use case? The 95th percentile use case?
No! It should be the “midlife crisis use case.” What is it? I’ll show you.
Well, it’s time for another exploration in Use Case 7. Unfamiliar with UC7? It’s simply when customers do unexpected things to our products. We often ignore it, but in fact, it is one of our best ways to learn about our product’s reliability. [Read more…]
This is a direct followup to my post last week.
I usually don’t do two part posts but….
I got some great responses to my post last week. I then got this image from my buddies at NASA (on the ground, not on the space station). One is actually my roommate from college. His hair is much shorter now.
Sometimes I see images that speak strongly to how reliability engineering affects us everyday. Think of how many items you own or use systems that you wouldn’t touch/interact with if you couldn’t be absolutely sure they would work as expected. I wouldn’t use my microwave if I thought there was a 1/1000 chance it would catch fire. The amount of faith I have in traffic lights working correctly is astounding. If they malfunction it could be fatal.
I found, while working at HP as a reliability engineer, that most managers of new products had little to no understanding of reliability concepts. They usually had the basic concept that reliability engineers should be brought into the project as the design was being finalized but had no clue what they would work on. [Read more…]
The clock in my ’79 Porsche 911 works perfectly. I don’t remember the last time I set it. Maybe I made a small adjustment six months ago, a year ago, don’t know? A modern day quartz clock does this no problem, a mechanical spring clock might struggle in such a rough environment. So was it quartz or mechanical? the ’70s was when quartz came on the scene, so either was a possibility. First I wanted to find out if it was ever replaced or serviced. So what did I do? I contacted the previous two owners. One purchased it new in ’79 and the other owned it for a five year period before I bought it. Neither recalls it ever being serviced or having a problem.
This is our fifth article about the 3 ways to do reliability allocation. We have been taken on a journey through the reliability design cycle, key steps for reliability allocation, allocation factors used to get these goals and key pitfalls. Now we finish off our conversation by looking at a few variations and applications. Allocating MTBF (… though we recommend against it), allocating availability, allocating maintainability (… another thing we recommend against) and allocating for different system reliability goals.
If you want to finish off your understanding of reliability allocation – read this!
This is our fourth article about the 3 ways to do reliability allocation. The first three articles describe the reliability design cycle and how reliability allocation is a part of this cycle. Our last article focused on what options you, as a design team leader, have at your disposal when you realize that your components aren’t on track to meet their allocated goals (or doing something!) Now we talk about working out what these allocated goals are. And how to get them. And don’t worry – it is much easier than you probably think!
If you want to learn more about a straightforward approach to reliability allocation – read this!
This is our third article about the 3 ways to do reliability allocation. In the first article, we set the scene. We talked about the reliability design cycle that needs to be implemented to make sure what we do will actually work. Will actually matter. In the second article, we cover the six steps of reliability allocation. In this article, we go through the six steps of reliability allocation.
You should have already read these articles – and if you haven’t please do! Once we have our reliability design cycle up and running, there are six key steps to making reliability allocation happen. And this article is about the sixth step – doing something!
If you want to learn more about a straightforward approach to reliability allocation – read this!