Every failure provides information. It provides time to failure, stress strength relationship, process stability and design margin types of information. In every case. Even failures directly related to human error.
A hardware intermittent failure observed by a firmware engineer should not be dismissed. Rather recorded, explored and examined. Continue reading
Reliability engineering has value. It can improve product reliability, increase uptime, and drive customer satisfaction, for example.
Here are a couple of stories based on real situations that resulted in significant value for the organization.
A telecommunications test device company created a low volume very expensive test system. Continue reading
Roll the dice.
It is about that simple if any one product will survive to a specific time. Every product has a chance, not a guarantee. The time to failure for each product is a function of the use, stresses, assembly, latent defects or imperfections, and many other variables. Continue reading
In the poem by Oliver Wendall Holmes, The One Hoss Shay, a deacon is confounded by the various parts of his carriage the fail.
And, he decides to do something about it.
But the Deacon swore (as Deacons do,
With an “I dew vum,” or an “I tell yeou,”)
He would build one shay to beat the taown
‘n’ the keounty ‘n’ all the kentry raoun’;
It should be so built that it couldn’ break daown:
“Fer,” said the Deacon, “t’s mighty plain
Thut the weakes’ place mus’ stan’ the strain;
‘n’ the way t’ fix it, uz I maintain, Is only jest T’ make that place uz strong uz the rest.”
Coupled with probability is the duration over which the probability applies.
For example, if we desire 99 of 100 to survive, we must state over which period of time this applies. It is proper to state the couplet of 99% reliable over 1 year. Continue reading