Professional Documents
Culture Documents
From ReliaWiki
These examples also appear in the Life Data Analysis Reference book.
In this example, we will determine the median rank value used for plotting the 6th failure from a sample size of 10. This
example will use Weibull++'s Quick Statistical Reference (QSR) tool to show how the points in the plot of the following
example are calculated.
First, open the Quick Statistical Reference tool and select the Inverse F-Distribution Values option.
Use the QSR to calculate the value of F0.5;10;12 = 0.9886, as shown next:
Consequently:
Another method is to use the Median Ranks option directly, which yields MR(%) = 54.8305%, as shown next:
Solution
Create a new Weibull++ standard folio that is configured for grouped times-to-failure data with suspensions.
Enter the data in the appropriate columns. Note that there are 4 suspensions, as only 6 of the 10 units were tested to failure
(the next figure shows the data as entered). Use the 3-parameter Weibull and MLE for the calculations.
Plot the data.
Note that the original data points, on the curved line, were adjusted by subtracting 30.92 hours to yield a straight line as
shown above.
Suspension Data Example
ACME company manufactures widgets, and it is currently engaged in reliability testing a new widget design. 19 units are
being reliability tested, but due to the tremendous demand for widgets, units are removed from the test whenever the
production cannot cover the demand. The test is terminated at the 67th day when the last widget is removed from the test.
The following table contains the collected data.
Solution
In this example, we see that the number of failures is less than the number of suspensions. This is a very common situation,
since reliability tests are often terminated before all units fail due to financial or time constraints. Furthermore, some
suspensions will be recorded when a failure occurs that is not due to a legitimate failure mode, such as operator error. In
cases such as this, a suspension is recorded, since the unit under test cannot be said to have had a legitimate failure.
Enter the data into a Weibull++ standard folio that is configured for times-to-failure data with suspensions. The folio will
appear as shown next:
We will use the 2-parameter Weibull to solve this problem. The parameters using maximum likelihood are:
Using RRX:
Using RRY:
Analyze the data using several different parameter estimation techniques and compare the results.
Solution
Enter the data into a Weibull++ standard folio that is configured for interval data. The data is entered as follows:
The plot of the MLE solution with the two-sided 90% confidence bounds is:
Estimate the parameters for the 3-parameter Weibull, for a sample of 10 units that are all tested to failure. The recorded
failure times are 200; 370; 500; 620; 730; 840; 950; 1,050; 1,160 and 1,400 hours.
Published Results:
, ,
The small difference between the published results and the ones obtained from Weibull++ are due to the difference in the
estimation method. In the publication the parameters were estimated using probability plotting (i.e., the fitted line was "eye-
balled"). In Weibull++, the parameters were estimated using non-linear regression (a more accurate, mathematically fitted
line). Note that γ in this example is negative. This means that the unadjusted for γ line is concave up, as shown next.
1. What is the unreliability of the units for a mission duration of 30 hours, starting the mission at age zero?
2. What is the reliability for a mission duration of 10 hours, starting the new mission at the age of T = 30 hours?
3. What is the longest mission that this product should undertake for a reliability of 90%?
Solution
Then, we investigate several methods of solution for this problem. The first, and more laborious, method is to extract the
information directly from the plot. You may do this with either the screen plot in RS Draw or the printed copy of the plot.
(When extracting information from the screen plot in RS Draw, note that the translated axis position of your mouse is
always shown on the bottom right corner.)
Using this first method, enter either the screen plot or the printed plot with T = 30 hours, go up vertically to the straight line
fitted to the data, then go horizontally to the ordinate, and read off the result. A good estimate of the unreliability is 23%.
(Also, the reliability estimate is 1.0 - 0.23 = 0.77 or 77%.)
The second method involves the use of the Quick Calculation Pad (QCP).
Select the Prob. of Failure calculation option and enter 30 hours in the Mission End Time field.
Note that the results in QCP vary according to the parameter estimation method used. The above results are obtained using
RRX.
or:
Again, the QCP can provide this result directly and more accurately than the plot.
3. To use the QCP to solve for the longest mission that this product should undertake for a reliability of 90%, choose
Reliable Life and enter 0.9 for the required reliability. The result is 15.9933 hours.
From Dimitri Kececioglu, Reliability & Life Testing Handbook, Page 418 [20].
Sample of 10 units, all tested to failure. The failures were recorded at 16, 34, 53, 75, 93, 120, 150, 191, 240 and 339 hours.
Published Results
This same data set can be entered into a Weibull++ standard data sheet. Use RRY for the estimation method.
You will also notice that in the examples that follow, a small difference may exist between the published results and the ones
obtained from Weibull++. This can be attributed to the difference between the computer numerical precision employed by
Weibull++ and the lower number of significant digits used by the original authors. In most of these publications, no
information was given as to the numerical precision used.
From Wayne Nelson, Fan Example, Applied Life Data Analysis, page 317 [30].
70 diesel engine fans accumulated 344,440 hours in service and 12 of them failed. A table of their life data is shown next (+
denotes non-failed units or suspensions, using Dr. Nelson's nomenclature). Evaluate the parameters with their two-sided
95% confidence bounds, using MLE for the 2-parameter Weibull distribution.
Published Results:
This same data set can be entered into a Weibull++ standard folio, using 2-parameter Weibull and MLE to calculate the
parameter estimates.
You can also enter the data as given in table without grouping them by opening a data sheet configured for suspension data.
Then click the Group Data icon and chose Group exactly identical values.
The data will be automatically grouped and put into a new grouped data sheet.
The two-sided 95% bounds on the parameters can be determined from the QCP. Calculate and then click Report to see the
results.
From Wayne Nelson, Applied Life Data Analysis, Page 415 [30]. 167 identical parts were inspected for cracks. The
following is a table of their last inspection times and times-to-failure:
Published Results:
This same data set can be entered into a Weibull++ standard folio that's configured for grouped times-to-failure data with
suspensions and interval data.
From Dallas R. Wingo, IEEE Transactions on Reliability Vol. R-22, No 2, June 1973, Pages 96-100.
Wingo uses the following times-to-failure: 37, 55, 64, 72, 74, 87, 88, 89, 91, 92, 94, 95, 97, 98, 100, 101, 102, 102, 105,
105, 107, 113, 117, 120, 120, 120, 122, 124, 126, 130, 135, 138, 182. In addition, the following suspensions are used: 4 at
70, 5 at 80, 4 at 99, 3 at 121 and 1 at 150.
Note that you must select the Use True 3-P MLEoption in the Weibull++ Application Setup to replicate these results.
Suppose we want to model a left censored, right censored, interval, and complete data set, consisting of 274 units under test
of which 185 units fail. The following table contains the data.
Solution
Since standard ranking methods for dealing with these different data types are inadequate, we will want to use the ReliaSoft
ranking method. This option is the default in Weibull++ when dealing with interval data. The filled-out standard folio is
shown next:
Using RRY:
The plot with the two-sided 90% confidence bounds for the rank regression on X solution is:
Copyright Information.