Your Reliability Engineering Professional Development Site
A listing in reverse chronological order of articles by:
Reliability goals are often communicated in Mean Time Between Failure (MTBF) 40,000 hrs, Failure rate 0.00035, or percentage still functioning over time 99.98%. If you are not familiar with actually calculating these numbers they really don’t mean a lot. Are any of those above numbers good? bad? something we will even measure before release?
Are any of those above numbers good? bad? something we will even measure before release? [Read more…]
HASS doesn’t break stuff like HALT. HASS is like a good physical examination from a doctor: It gives you the thumbs up or thumbs down on health based on a quick and thorough examination. But a good thorough examination is possible because of research, education, and practice.
[Read more…]
There are many paths to becoming a reliability engineer.
If you are good with statistics, enjoy the detective work of failure analysis, or simply want to create a durable long lasting product, you likely found yourself in a reliability engineering role.
A science or engineering background is a great start. Time spent working with a design or maintenance team certainly help. An advanced degree in reliability engineering is another path.
The element that is often missing as a precursor become starting a career in reliability is excellent soft skills. We know the engineering and science stuff. The formulas, the testing, the data analysis. We can get stuff done in the lab or on the shop floor.
Yet to become an exceptional reliability engineer, or any type of engineer, add the ability to communicate well. Add the ability to get your point across and to wield influence to help others understand and accept your proposals, ideas, and results. [Read more…]
Why do so few product development programs make that connection between the product specification document content and the released product? It seems to be such a common thing that these two don’t connect that organizations don’t even bother to review or analyze this after release.
The mindset at that point seems to be:
I was in a meeting recently with a customer team. It was on-site with 12 people ranging from mid-level engineers to upper management. Someone defended me earlier in the meeting by saying “Well, he did write a book on it!” Which was nice and kinda cool to hear someone say. But this lead to a later comeback by a crusty, principle engineer, 40 years under his belt, boat captain from “Jaws” kind of guy. “If we can buy your book then why do we need you?”
I took a moment. I knew that not responding wasn’t what I wanted to do but had to tread carefully because a poorly crafted response could easily sound arrogant. This is what I responded with… [Read more…]
Remember that first time you were asked to step into a leadership or management role, or to manage a client relationship? The experience was probably exciting and unsettling at the same time. Something different was asked of you.
While many of us have succeeded as individual contributors or team members, succeeding as a leader or manager requires a new set of skills we have often not been given the opportunity to acquire. This applies whether we carry an official leadership responsibility or not. In a future article it would be interesting to explore the distinction between “leader” and “manager”. [Read more…]
We are all familiar with the base of our car warranties being in both months and miles. 
Some of that is that they want a definitive end to all warranty periods. But another reason is you can’t just boil down all aging factors to one stress. In a product development program, we are always under pressure to keep all activities as short as possible. Accelerated Life Testing ALT can loose almost all of it’s value when not executed with care. [Read more…]
Analyzing and visualizing data that is related to equipment wear-out (fatigue stage) over a specific time span is a challenge. Analyzing systems, equipment and components exposed to spectrum loading as opposed to uniform cyclical loading that span years or decades or centuries requires a special approach. Think of roads, bridges and other assets with long life spans that are susceptible to wear out mechanisms caused by external and internal loads, varying load durations, temperature swings and corrosion. [Read more…]
This video clip looks like a disaster but is actually a visualization of precision reliability engineering………. right after a disaster . [Read more…]
Many of our customers (internal/external) trust us when we say that a Weibull analysis is the best approach to understanding what the data set is telling us. We then take their data set, do something mysterious where no one can see us, and then present these accurate predictions as to what is going to happen with a given population of the product at some future date. [Read more…]
Recently Peter Stuttard asked if I knew of a reference for the perfect strength and perfect stress concepts. I didn’t and asked for a bit of explanation of the phrases.
Here is his reply (via Linkedin, btw a great tool to get and stay in touch) posted with permission with minor formatting edits.
To learn more about Peter check out his Linkedin profile.
Fred
Thanks for responding so quickly, the concepts of Perfect Strength and Perfect Stress are related to your discussion re Parts Count and Parts Stress predictions and reading this on your web site prompted me to ask you about them. [Read more…]
Often when we request an analysis from an engineer we run with the results and don’t ask a lot of questions about the analysis itself. Having done a lot of analysis I am familiar with all the assumptions and estimations that go into making a calculation work. But that means that the results of the analysis are only relevant to those assumptions and estimations. The analyst may have to make the following “calls” without additional input or only a small fact-finding mission. [Read more…]
Convince, don’t confuse! Justify, don’t exaggerate!
Project managers want to deliver their product on time and on schedule. Design engineers want to believe that they have got it right. But your analysis, test results and field data suggest that there might be a problem. What do you do?
The key words here are “suggest” and “might be”. How should you present your evidence and analysis such that it doesn’t exaggerate with certainty, or confuse with statistics? How should you ensure that your conclusions lead to positive action? [Read more…]
In a recent Seth Godin blog, Counting beans he talks about the eventual costs of little compromises. The immediate benefit may be celebration worthy, yet
But overlooked are the unknown costs over time, the erosion in brand, the loss in quality, the subtraction from something that took years to add up.
This certainly applies to reliability as well. Deferring maintenance just one more month, addressing one more software bug can be done after shipping, and similar small shifts erode reliability of your system. [Read more…]
My career path in systems engineering. I don’t mean my professional engineering career exactly. My systems engineering portfolio I would say started at about the age of nine if I had to pick a point in time. At nine I made a small hydro-electric power plant in the stream behind my house so I could have light in the woods. I could have taken a purely electrical approach, battery, wires, bulb, or a chemistry approach, matches, wood, oxygen, or a mechanical approach (actually how do you make light mechanically? Sparks??) anyway… But I took a systems approach. [Read more…]