Posts Tagged ‘reliability’
How Does Reliability Engineering Affect (Not Just Assess) Design?
Reliability Engineering isn’t just about assessments. It’s about providing information to make decisions. How does reliability engineering affect design?
Read MoreOverlapping Ideas: Quality, Reliability, and Safety
What is the intercept of quality and safety? How concerned do we need to be about quality while we’re determining root causes?
Read MoreEnvironmental Stress Testing for Robust Designs
To help plan future tests and projects, we review qualitative accelerated test models that can be used early in a design process.
Read MoreHow Many Do We Need To Test?
In this episode we review sampling for design tests. We talk through a generic thought process for choosing a statistically relevant sample size and propose some basics that we can all learn about to better understand sampling. Our goal is for us to be able to better talk through a sampling scenario with our quality…
Read More5 Aspects of Good Reliability Goals and Requirements
Good reliability requirements are going to drive our design decisions relating to the concept, the components, the materials, and other stuff. So, the moment to start defining reliability requirements is early in the design process. But, what makes a well-defined reliability requirement? There are five aspects it should cover: do you know what they are? We’ll describe…
Read MoreHow to Handle Competing Failure Modes
If we’re not careful with or ignore failure modes, we can choose the wrong reliability model or statistical distribution. If our product performance is close to the required limits and/or we need a very accurate model, this could be a big problem. We talk about the importance of failure modes and step-through a tensile-test example…
Read MoreHALT! Watch out for that weakest link.
HALT (Highly Accelerated Life Test) uses the weakest link mentality. We apply stresses beyond what our designs would normally see in the environment to make something fail. It’s meant to be an iterative test program where you are testing, analyzing the results, determining the root cause, fixing the design, and then testing it, again.
This blog reveals more about its roots, why you should perform HALT (or not), when in the design process it’s best (hint: really early), and who likely needs to be involved. Also understand how HALT is different from ALT.
Read More