View source for Test-Fix-Find-Test Data Example

<noinclude>{{Banner RGA Examples}}
''This example appears in the [[Crow_Extended|Reliability Growth and Repairable System Analysis Reference]]''.
</noinclude>

Consider the data given in the first table below. There were 56 total failures and <math>T=400\,\!</math>. The effectiveness factors of the unique BD modes are given in the second table. Determine the following:

#Calculate the demonstrated MTBF and failure intensity.
#Calculate the projected MTBF and failure intensity.
#What is the rate at which unique BD modes are being generated during this test?
#If the test continues for an additional 50 hours, what is the minimum number of new unique BD modes expected to be generated?

<div style="margin-left:auto; margin-right: auto; width: 500px;">
<div style="width: 300px; float: left;">
{{Text-Fix-Find-Test Data}}
</div>

<div style="width: 200px; float: right;">

{|border="1" align="center" style="border-collapse: collapse;" cellpadding="5" cellspacing="5"
|-
|colspan="2" style="text-align:center"|'''Effectiveness Factors for the Unique BD Modes'''
|-
!BD Mode	
!EF <math>{{d}_{i}}\,\!</math> 
|-
|1||	.67
|-
|2||	.72
|-
|3||	.77
|-
|4||	.77
|-
|5||	.87
|-
|6||	.92
|-
|7||	.50
|-
|8||	.85
|-
|9||	.89
|-
|10||	.74
|-
|11||	.70
|-
|12||	.63
|-
|13||	.64
|-
|14||	.72
|-
|15||	.69
|-
|16||	.46
|}
</div>
</div>
<p style="clear: both;"></p>


'''Solution'''
<ol>
<li>In order to obtain <math>{{\widehat{\lambda }}_{CA}}\,\!</math>, use the traditional Crow-AMSAA model for test-fix-test to fit all 56 data points, regardless of the failure mode classification to get: 
	
:<math>\begin{align}
	  \widehat{\beta }= & 0.91026 \\ 
	  \widehat{\lambda }= & 0.23969  
	\end{align}\,\!</math>

Thus the achieved or demonstrated failure intensity is estimated by: 
	
:<math>\begin{align}
	   {{\widehat{\lambda }}_{CA}} = & \widehat{\lambda }\widehat{\beta }{{T}^{\widehat{\beta }-1}} \\ 
	  = & 0.23969\times 0.91026\times {{400}^{(0.91026-1)}} \\ 
	  = & 0.12744  
	\end{align}\,\!</math>
	
The achieved or demonstrated MTBF, <math>{{M}_{CA}}\,\!</math>, is the system reliability attained at the end of test, <math>T=400\,\!</math>, and is estimated by: 

:<math>{{\widehat{M}}_{CA}}={{[{{\widehat{\lambda }}_{CA}}]}^{-1}}=7.84708\,\!</math>
</li>
<li>For this data set, <math>M=16\,\!</math> and <math>T=400\,\!</math>. 
	
:<math>{{\widehat{\lambda }}_{BD}}=\frac{{{N}_{BD}}}{T}=\frac{32}{400}=0.08\,\!</math>
		
:<math>\overline{d}=\underset{i=1}{\overset{M}{\mathop \sum }}\,{{d}_{i}}/M=0.72125\,\!</math>	
		
:<math>\underset{i=1}{\overset{16}{\mathop \sum }}\,(1-{{d}_{i}}){{N}_{i}}/T=0.01955\,\!</math>
	
Calculate maximum likelihood estimates, <math>\hat{\beta }\,\!</math> and <math>\hat{\lambda }\,\!</math>, of the BD modes: 
	
:<math>\begin{align}
	  {{{\hat{\beta }}}_{BD}}= & 0.74715 \\ 
	  {{{\hat{\lambda }}}_{BD}} = & 0.18197  
	\end{align}\,\!</math>

Then: 
	
:<math>\overline{d}\widehat{h}(T|BD)=0.0215\,\!</math>	

Therefore: 
	
:<math>\begin{align}
{{\widehat{\lambda }}_{EM}} = & {{\widehat{\lambda }}_{CA}}-{{\widehat{\lambda }}_{BD}}+\underset{i=1}{\overset{K}{\mathop \sum }}\,(1-{{d}_{i}})\frac{{{N}_{i}}}{T}+\overline{d}\widehat{h}(T|BD) \\ 
	  = & 0.12744-0.08+0.0196+0.0215 \\ 
	  = & 0.08854  
	\end{align}\,\!</math>

The Crow Extended model projected MTBF is: 
	
:<math>\begin{align}
	  {{\widehat{M}}_{EM}} = & {{[{{\widehat{\lambda }}_{EM}}]}^{-1}} \\ 
	  = & 11.29418  
	\end{align}\,\!</math>

Consequently, based on the Crow Extended model and the data shown in the tables above, the MTBF grew to 7.85 as a result of the corrective actions for the BC failure modes during the test. The MTBF then jumped to 11.29 after the test as a result of the delayed corrective actions for the BD failure modes. The management strategy can be summarized by the Failure Mode Strategy plot, as shown next.

[[Image:rga9.6.png|center|400px|Failure Mode Strategy plot.]]

This pie chart shows that 9.48% of the system's failure intensity has been left in (A modes), 31.81% of the failure intensity due to the BC modes has not been seen yet and 13.40% was removed during the test (BC modes - seen). In addition, 33.23% of the failure intensity due to the BD modes has not been seen yet, 3.37% will remain in the system since the corrective actions will not be completely effective at eliminating the identified failure modes, and 8.72% will be removed after the delayed corrective actions.
</li>
<li>The rate at which unique BD modes are being generated is equal to <math>h{{(T|BD)}^{-1}}\,\!</math>, where:

:<math>\begin{align}
  h{{(T|BD)}^{-1}}  = & \frac{1}{{{\widehat{\lambda }}_{BD}}{{\widehat{\beta }}_{BD}}{{T}^{{{\widehat{\beta }}_{BD}}-1}}} \\ 
  = & \frac{T}{M{{\widehat{\beta }}_{BD}}} \\ 
  = & 33.4605  
\end{align}\,\!</math>
</li>
<li>Unique BD modes are being generated every 33.4605 hours. If the test continues for another 50 hours, then at least one new unique BD mode would be expected to be seen from this additional testing.

As shown in the next figure, the MTBF of each individual failure mode can be plotted, and the failure modes with the lowest MTBF can be identified. These are the failure modes that cause the majority of the system failures.

[[Image:rga9.7.png|center|400px|Individual Mode MTBF chart.]]
</li>
</ol>