Reliability Growth Planning: Difference between revisions

From ReliaWiki
Jump to navigation Jump to search
Line 1: Line 1:
{{template:RGA BOOK|11|Reliability Growth Planning}}
{{template:RGA BOOK|11|Reliability Growth Planning}}


=Reliability Growth Planning=
{{reliability growth planning rga}}
==Background==
In developmental reliability growth testing, the objective is to test a system, find problem failure modes, at some point incorporate corrective actions, and therefore increase the reliability of the system. This process is continued for the duration of the test time. If the corrective actions are effective then the system Mean Time Between Failures (MTBF) will move from an initial low value to a higher value.
Typically the objective of reliability growth testing is not to just increase the MTBF, but to increase it to a particular value. In other words, increase the MTBF to meet a goal or requirement. Therefore, determining how much test time is needed for a particular system is generally always of interest in reliability growth testing.
This brings us to the topic of growth planning.
 
<br>
In this chapter, we will address the common questions engineers and managers face at the planning stage of product development, in terms of meeting the design reliability goals. Planning for required test time, setting realistic reliability goals and creating a strategy for meeting those goals are all essential parts of project management. It is therefore necessary to have a tool that can be utilized for such planning purposes. The basis of the tool will be the Duane Postulate and a model will be developed which incorporates the realities faced during development and generates a plan that can be used as a guideline during developmental testing.
The Duane Postulate is based on empirical observations and reflects a learning curve pattern for reliability growth. This identical learning curve pattern forms the basis of the Crow-AMSAA (NHPP) model. The Duane Postulate is also reflected in the Crow Extended model in the form of the discovery function  <math>h(t)</math> .
 
<br>
The discovery function is the rate in which new, distinct problems are being discovered during reliability growth development testing. The Crow-AMSAA (NHPP) model is a special case of the discovery function. Consider that when a new, distinct failure mode is first seen the testing is stopped and a corrective action is incorporated before the testing is resumed. In addition, suppose that the corrective action is highly effective so that the failure mode is unlikely to be seen again. In this case, the only failures observed during the reliability growth test are first occurrences of failure modes. Therefore, if the Crow-AMSAA (NHPP) model and the Duane Postulate are accepted as the pattern for a test-fix-test reliability growth testing program, then the form of the Crow-AMSAA (NHPP) model must be the form for the discovery function,  <math>h(t)</math> .
 
<br>
To be consistent with the Duane Postulate and the Crow-AMSAA (NHPP) model the discovery function must be of the same form. This form of the discovery function is an important property of the Crow Extended model and its application in growth planning. As with the Crow-AMSAA (NHPP) model, this form of the discovery function ties the model directly to real-world data and experiences
The use of the Duane Postulate as a reliability growth planning model poses two significant drawbacks:The first drawback is that the Duane Postulate's MTBF is zero at time equal to zero. This was addressed in MIL-HDBK-189 by specifying a time  <math>{{T}_{i}}</math>  where growth starts after  <math>{{T}_{i}}</math>  and the Duane Postulate applies [13]. However, determining  <math>{{T}_{i}}</math>  is subjective and is not a desirable property of MIL-HDBK-189. The second drawback is that the MTBF for the Duane Postulate increases indefinitely to infinity, which is not realistic.
<br>
<br>
Therefore a desirable feature of a planning model is that:
<br>
:1) The discovery function must have the form of the Crow-AMSAA (NHPP) model and the Duane Postulate.
:2) The start time  <math>{{T}_{i}}</math>  is not required as an input.
:3) An upper bound on the system MTBF is specified in the model.
All of these desirable features are included in the planning model discussed in this chapter, which is based on the Crow Extended model.
 
==Crow Extended Model==
===Introduction===
The Crow Extended model for reliability growth planning is a revised and improved version of the MIL-HDBK-189 growth curve [13]. MIL-HDBK-189 can be considered as the growth curve based on the Crow-AMSAA (NHPP) model. Using MIL-HDBK-189 for reliability growth planning assumes that the corrective actions for the observed failure modes are incorporated during the test and at the specific time of failure. However, in actual practice, fixes may be delayed until after the completion of the test or some fixes may be implemented during the test while others are delayed and some are not fixed at all. The Crow Extended model for reliability growth planning provides additional input to be able to account for a specific management strategy and delayed fixes with specified effectiveness factors.
<br>
<br>
===Definitions===
<br>
====Management Strategy Ratio & Initial Failure Intensity====
When a system is tested and failure modes are observed, management can make one of two possible decisions, either to fix or not fix the failure mode. Therefore, the management strategy places failure modes into two categories: A modes and B modes. A modes are all failure modes such that, when seen during the test, no corrective action will be taken. This accounts for all modes for which management determines that it is not economically or otherwise justified to take a corrective action. B modes are either corrected during the test or the corrective action is delayed to a later time. The management strategy is defined by what portion of the failures will be fixed.
<br>
Let  <math>{{\lambda }_{I}}</math>  be the initial failure intensity of the system in test.  <math>{{\lambda }_{A}}</math>  is defined as the A mode initial failure intensity and  <math>{{\lambda }_{B}}</math>  is defined as the B mode initial failure intensity.  <math>{{\lambda }_{A}}</math>  is the failure intensity of the system that will not be addressed by corrective actions even if a failure mode is seen during test.  <math>{{\lambda }_{B}}</math>  is the failure intensity of the system that will be addressed by corrective actions if a failure mode is seen during testing.
<br>
Then, the initial failure intensity of the system is:
 
 
::<math>{{\lambda }_{I}}={{\lambda }_{A}}+{{\lambda }_{B}}</math>
 
 
The initial system MTBF is:
 
 
::<math>{{M}_{I}}=\frac{1}{{{\lambda }_{I}}}</math>
 
 
Based on the initial failure intensity definitions, the management strategy ratio is defined as:
 
 
::<math>msr=\frac{{{\lambda }_{B}}}{{{\lambda }_{A}}+{{\lambda }_{B}}}</math>
 
 
The  <math>msr</math>  is the portion of the initial system failure intensity that will be addressed by corrective actions, if seen during the test.
The Type A and B failure mode initial failure mode intensity is:
 
 
::<math>\begin{align}
  & {{\lambda }_{A}}= & \left( 1-msr \right)\cdot {{\lambda }_{I}} \\
& {{\lambda }_{B}}= & msr\cdot {{\lambda }_{I}} 
\end{align}</math>
 
 
====Effectiveness Factor====
<br>
When a delayed corrective action is implemented for a Type B failure mode, in other words a BD mode, the failure intensity for that mode is reduced if the corrective action is effective. Once a BD mode failure mode is discovered, it is rarely totally eliminated by a corrective action. After a BD mode has been found and fixed, a certain percentage of the failure intensity will be removed, but a certain percentage of the failure intensity will generally remain. The fraction decrease in the BD mode failure intensity due to corrective actions,  <math>d</math> ,  <math>\left( 0<d<1 \right),</math>  is called the effectiveness factor. A study on EFs showed that an average EF,  <math>d,</math>  was about 70%. Therefore, typically about 30%, i.e.  <math>100(1-d)%</math> , of the BD mode failure intensity will remain in the system after all of the corrective actions have been implemented. However, individual EFs for the failure modes may be larger or smaller than the average. This average value of 70% can be used for planning purposes, or if such information is recorded, an average effectiveness factor from a previous reliability growth program can be used.
<br>
<br>
====MTBF Goal====
<br>
When putting together a reliability growth plan, a goal MTBF  <math>{{M}_{G}}</math>  (or goal failure intensity  <math>{{\lambda }_{G}}</math> ) is defined as the requirement or target for the product at the end of the growth program.
<br>
====Growth Potential====
The failure intensity remaining in the system at the end of the test will depend on the management strategy given by the classification of the Type A and Type B failure modes. The engineering effort applied to the corrective actions determines the effectiveness factors. In addition, the failure intensity depends on  <math>h(t)</math> , which is the rate at which problem failure modes are being discovered during testing. The rate of discovery drives the opportunity to take corrective actions based on the seen failure modes and it is an important factor in the overall reliability growth rate. The reliability growth potential is the limiting value of the failure intensity as time  <math>T</math>  increases. This limit is the maximum MTBF that can be attained with the current management strategy. The maximum MTBF will be attained when all Type B modes have been observed and fixed.
<br>
If all seen Type B modes are corrected by time  <math>T</math> , that is, no deferred corrective actions at time  <math>T</math> , then the growth potential is the maximum attainable with the Type B designation of the failure modes and the corresponding assigned effectiveness factors. This is called the nominal growth potential. In other words, the nominal growth potential is the maximum attainable growth potential assuming corrective actions are implemented for every mode that is planned to be fixed. In reality, some fixes to modes might be implemented at a later time due to schedule, budget, engineering, etc.
<br>
If some seen Type B modes are not corrected at the end of the current test phase then the prevailing growth potential is below the maximum attainable with the Type B designation of the failure modes and the corresponding assigned effectiveness factors.
If all Type B failure modes are seen and corrected with an average effectiveness factor,  <math>d</math> , then the maximum reduction in the initial system failure intensity is the growth potential failure intensity:
 
 
::<math>{{\lambda }_{GP}}={{\lambda }_{A}}+\left( 1-d \right){{\lambda }_{B}}</math>
 
 
The growth potential MTBF is:
 
 
::<math>{{M}_{GP}}=\frac{1}{{{\lambda }_{GP}}}</math>
 
 
Note that based Eqns. (lambda GP), (lambda initial) and (msr), the initial failure intensity is equal to:
 
 
::<math>{{\lambda }_{I}}=\frac{{{\lambda }_{GP}}}{1-d\cdot msr}</math>
 
 
====Growth Potential Design Margin====
<br>
The Growth Potential Design Margin ( <math>GPDM</math> ) can be considered as a safety margin when setting target MTBF values for the reliability growth plan. It is common for systems to degrade in terms of reliability when a prototype product is going into full manufacturing due to variation in material, processes, etc. Furthermore, the in-house reliability growth testing usually overestimates the actual product reliability, since the field usage conditions may not be perfectly simulated during growth testing. Typical values for the  <math>GPDM</math>  are around 1.2. Higher values yield less risk for the program, but require a more rigorous reliability growth test plan. Lower values imply higher program risk, with less safety margin.
 
During the planning stage, the growth potential MTBF,  <math>{{M}_{GP}},</math>  can be calculated based on the goal MTBF,  <math>{{M}_{G}},</math>  and the growth potential design margin,  <math>GPDM</math> :
 
 
::<math>{{M}_{GP}}=GPDM\cdot {{M}_{G}}</math>
 
 
or in terms of failure intensity:
 
 
::<math>{{\lambda }_{GP}}=\frac{{{\lambda }_{G}}}{GPDM}</math>
 
 
===Nominal Idealized Growth Curve===
<br>
During developmental testing, management should expect that certain levels of reliability will be attained at various points in the program in order to have assurance that reliability growth is progressing at a sufficient rate to meet the product reliability requirement. The idealized curve portrays an overall characteristic pattern, which is used to determine and evaluate intermediate levels of reliability and construct the program planned growth curve. Note that growth profiles on previously developed, similar systems provide significant insight into the reliability growth process and are valuable in the construction of idealized growth curves.
The nominal idealized growth curve portrays a general profile for reliability growth throughout system testing. The idealized curve has the baseline value  <math>{{\lambda }_{I}}</math>  until an initialization time,  <math>{{t}_{0}},</math>  when reliability growth occurs. From that time and until the end of testing, which can be one or, most commonly, multiple test phases, the idealized curve increases steadily according to a learning curve pattern until it reaches the final reliability requirement,  <math>{{M}_{F}}</math> . The slope of this curve on a log-log plot is the growth rate of the Crow Extended model [13].
 
====Nominal Failure Intensity Function====
The nominal idealized growth curve failure intensity as a function of test time  <math>t</math>  is:
 
::<math>{{r}_{NI}}(t)={{\lambda }_{A}}+(1-d){{\lambda }_{B}}+d\lambda \beta {{t}^{\left( \beta -1 \right)}}\text{ for }t\ge {{t}_{0}}</math>
 
:and:
 
::<math>{{r}_{NI}}(t)={{\lambda }_{I}}\text{ for }t\le {{t}_{0}}</math>
 
where  <math>{{\lambda }_{I}}</math>  is the initial system failure intensity,  <math>t</math>  is test time and  <math>{{t}_{0}}</math>  is the initialization time, which is discussed in the next section.
<br>
It can be seen that Eqn. (Nominal FI) is the failure intensity equation of the Crow Extended model.
<br>
<br>
 
====Initialization Time====
<br>
Reliability growth can only begin after a Type B failure mode occurs, which cannot be at a time equal to zero. Therefore, there is a need for an initialization time, different than zero, to be defined. The nominal idealized growth curve failure intensity is initially set equal to the initial failure intensity,  <math>{{\lambda }_{I}},</math>  until the initialization time,  <math>{{t}_{0}}</math> :
 
 
::<math>{{r}_{NI}}({{t}_{0}})={{\lambda }_{A}}+(1-d){{\lambda }_{B}}+d\lambda \beta t_{0}^{(\beta -1)}</math>
 
:Therefore:
 
::<math>{{\lambda }_{I}}={{\lambda }_{A}}+(1-d){{\lambda }_{B}}+d\lambda \beta t_{0}^{(\beta -1)}</math>
 
:Then:
 
::<math>{{t}_{0}}={{\left[ \frac{{{\lambda }_{I}}-{{\lambda }_{A}}-(1-d){{\lambda }_{B}}}{d\lambda \beta } \right]}^{\tfrac{1}{\beta -1}}}</math>
 
Using Eqn. (lambda initial) to substitute  <math>{{\lambda }_{I}}</math>  we have:
 
::<math>{{t}_{0}}={{\left[ \frac{{{\lambda }_{A}}+{{\lambda }_{B}}-{{\lambda }_{A}}-(1-d){{\lambda }_{B}}}{d\cdot \lambda \cdot \beta } \right]}^{\tfrac{1}{\beta -1}}}</math>
 
:Then:
 
::<math>{{t}_{0}}={{\left( \frac{{{\lambda }_{B}}}{\lambda \cdot \beta } \right)}^{\tfrac{1}{\beta -1}}}</math>
 
The initialization time,  <math>{{t}_{0}},</math>  allows for growth to start after a Type B failure mode has occurred.
<br>
<br>
 
====Nominal Time to Reach Goal====
<br>
Assuming that we have a target MTBF or failure intensity goal, we can solve Eqn. (Nominal FI) to find out how much test time,  , is required, (based on the Crow Extended model and the nominal idealized growth curve) to reach that goal:
 
 
::<math>{{t}_{N,G}}={{\left[ \frac{{{r}_{G}}-{{\lambda }_{A}}-(1-d){{\lambda }_{B}}}{d\cdot \lambda \cdot \beta } \right]}^{\tfrac{1}{\beta -1}}}</math>
 
 
Note that when  <math>{{\lambda }_{I}}<{{r}_{G}}</math>  or, in other words, the initial failure intensity is lower than the goal failure intensity, there is no need to solve for the nominal time to reach the goal, because the goal is already met. In this case, no further reliability growth testing is needed.
====Growth Rate for Nominal Idealized Curve====
<br>
The growth rate for the nominal idealized curve is defined in the same context as the growth rate for the Duane Postulate [8]. The nominal idealized curve has the same functional form for the growth rate as the Duane Postulate and the Crow-AMSAA (NHPP) model.
For both the Duane Postulate and the Crow-AMSAA (NHPP) model, the average failure intensity is given by:
 
 
::<math>C(t)=\frac{\lambda {{t}^{\beta }}}{t}=\lambda {{t}^{(\beta -1)}}</math>
 
 
Also, for both the Duane Postulate and the Crow-AMSAA (NHPP) model, the instantaneous failure intensity is given by:
 
 
::<math>r(t)=\lambda \beta {{t}^{(\beta -1)}}</math>
 
 
Taking the difference,  <math>D(t),</math>  between the average failure intensity,  <math>C(t)</math> , and the instantaneous failure intensity,  <math>r(t)</math> , yields:
 
 
::<math>D(t)=\lambda {{t}^{(\beta -1)}}-\lambda \beta {{t}^{(\beta -1)}}</math>
 
 
:Then:
 
 
::<math>D(t)=\lambda {{t}^{(\beta -1)}}[1-\beta ]</math>
 
 
For reliability growth to occur,  <math>D(t)</math>  must be decreasing.
The growth rate for both the Duane Postulate and the Crow-AMSAA (NHPP) model is the negative of the slope of  <math>\log (D(t))</math>  as a function of  <math>\log (t)</math> :
 
 
::<math>{{\log }_{e}}(D(t))=\text{constant}-(1-\beta ){{\log }_{e}}(t)</math>
 
 
 
The slope is negative under reliability growth and equals:
 
 
::<math>\text{slope}=-(1-\beta )</math>
 
 
The growth rate for both the Duane Postulate and the Crow-AMSAA (NHPP) model is equal to the negative of this slope:
 
 
::<math>\text{Growth Rate}=(1-\beta )</math>
 
 
The instantaneous failure intensity for the nominal idealized curve is:
 
 
::<math>{{r}_{NI}}(t)={{\lambda }_{A}}+(1-d){{\lambda }_{B}}+d\lambda \beta {{(t)}^{(\beta -1)}}</math>
 
 
The cumulative failure intensity for the nominal idealized curve is:
 
 
::<math>{{C}_{NI}}(t)={{\lambda }_{A}}+(1-d){{\lambda }_{B}}+d\lambda {{(t)}^{(\beta -1)}}</math>
 
 
:Therefore:
 
 
::<math>{{D}_{NI}}(t)=[{{C}_{NI}}(t)-{{r}_{NI}}(t)]=\lambda {{t}^{(\beta -1)}}[1-\beta ]</math>
 
 
:and:
 
 
::<math>{{\log }_{e}}({{D}_{NI}}(t))=\text{constant}-(1-\beta ){{\log }_{e}}(t)</math>
 
 
Therefore, in accordance with the Duane Postulate and the Crow-AMSAA (NHPP) model,  <math>a=1-\beta </math>  is the growth rate for the reliability growth plan.
<br>
 
====Lambda - Beta Parameter Relationship====
<br>
Under the Crow-AMSAA (NHPP) model, the time to first failure is a Weibull random variable. The MTTF of a Weibull distributed random variable with parameters  <math>\beta </math>  and  <math>\eta </math>  is:
 
 
::<math>MTTF=\eta \cdot \Gamma \left( 1+\frac{1}{\beta } \right)</math>
 
 
The parameter lambda is defined as:
 
 
::<math>\lambda =\frac{1}{{{\eta }^{\beta }}}</math>
 
 
Using Eqn. (lambda eta relationship), the MTTF relationship shown in Eqn. (Weibull MTTF) becomes:
 
 
::<math>MTB{{F}_{B}}=\frac{\Gamma \left( 1+\tfrac{1}{\beta } \right)}{{{\lambda }^{\left( \tfrac{1}{\beta } \right)}}}</math>
 
 
Or, in terms of failure intensity:
 
 
::<math>{{\lambda }_{B}}=\frac{{{\lambda }^{\left( \tfrac{1}{\beta } \right)}}}{\Gamma \left( 1+\tfrac{1}{\beta } \right)}</math>
 
 
===Actual Idealized Growth Curve===
<br>
The actual idealized growth curve differs from the nominal idealized curve in that it takes into account the average fix delay that might occur in each test phase. The actual idealized growth curve is continuous and goes through each of the test phase target MTBFs.
 
====Fix Delays and Test Phase Target MTBF====
<br>
Fix delays reflect how long it takes from the time a problem failure mode is discovered in testing, to the time the corrective action is incorporated into the system and reliability growth is realized. The consideration of the fix delay is often in terms of how much calendar time it takes to incorporate a corrective action fix after the problem is first seem. However, the impact of the delay on reliability growth is reflected in the average test time it takes between finding a problem failure mode and incorporating a corrective action. The fix delay is reflected in the actual idealized growth curve in terms of test time.
In other words, the average fix delay is calendar time converted to test hours. For example, say that we expect an average fix delay of two weeks: if in two weeks the total test time is 1000 hours, the average fix delay is 1000 hours. If in the same two weeks the total test time is 2000 hours (maybe there are more units available or more shifts) then the average fix delay is 2000 hours.
<br>
There can be a constant fix delay across all test phases or, as a practical matter, each test phase can have a different fix delay time. In practice, the fix delay will generally be constant over a particular test phase.  <math>{{L}_{i}}</math>  denotes the fix delay for phase  <math>i=1,...,P,</math>  where  <math>P</math>  is the total number of phases in the test. RGA 7 allows for a maximum of seven test phases.
<br>
<br>
====Actual Failure Intensity Function====
<br>
Consider a test plan consisting of  <math>i</math>  phases. Taking into account the fix delay within each phase, we expect the actual failure intensity to be different (i.e. shifted) from the nominal failure intensity. This is because fixes are not incorporated instantaneously, thus growth is realized at a later time compared to the nominal case.
Specifically, the actual failure intensity will be estimated as follows:
 
'''Test Phase 1'''
<br>
For the first phase of a test plan, the actual idealized curve failure intensity,  <math>{{r}_{AI}}(t)</math> , is <math>:</math>
 
 
::<math>{{r}_{AI}}(t)={{\lambda }_{A}}+(1-d){{\lambda }_{B}}+d\lambda \beta {{\left[ \left( \frac{{{T}_{1}}-{{L}_{1}}}{{{T}_{1}}} \right)t \right]}^{(\beta -1)}}\text{ for }0<t\le {{T}_{1}}</math>
 
 
Note that the end time of Phase 1,  <math>{{T}_{1}},</math>  must be greater than  <math>{{L}_{1}}+{{t}_{0}}</math> . That is,  <math>{{T}_{1}}>{{L}_{1}}+{{t}_{0}}</math> .
The actual idealized curve initialization time for Phase 1,  <math>T_{0}^{AIC},</math>  is calculated from:
 
 
::<math>{{r}_{AI}}(T_{0}^{AIC})={{\lambda }_{A}}+(1-d){{\lambda }_{B}}+d\lambda \beta {{\left[ \left( \frac{{{T}_{1}}-{{L}_{1}}}{{{T}_{1}}} \right)T_{0}^{AIC} \right]}^{(\beta -1)}}</math>
 
 
Where  <math>{{r}_{AI}}(T_{0}^{AIC})={{r}_{I}}.</math>
Therefore, using Eqn. (lambdaqualsominal):
 
 
::<math>{{\lambda }_{A}}+(1-d){{\lambda }_{B}}+d\lambda \beta {{\left[ \left( \frac{{{T}_{1}}-{{L}_{1}}}{{{T}_{1}}} \right)T_{0}^{AIC} \right]}^{(\beta -1)}}={{\lambda }_{A}}+(1-d){{\lambda }_{B}}+d\lambda \beta t_{0}^{(\beta -1)}</math>
 
 
Solving Eqn. (ActIhase1) for  <math>T_{0}^{AIC}</math>  we get:
 
 
::<math>T_{0}^{AIC}=\frac{{{t}_{0}}}{\left( \tfrac{{{T}_{1}}-{{L}_{1}}}{{{T}_{1}}} \right)}</math>
 
 
 
'''Test Phase  <math>i</math>'''
<br>
For any test phase  <math>i</math> , the actual idealized curve failure intensity is given by:
 
 
::<math>{{r}_{AI}}(t)={{\lambda }_{A}}+(1-d){{\lambda }_{B}}+d\lambda \beta {{\left[ {{T}_{i-1}}-{{L}_{i-1}}+\left( \frac{{{T}_{i}}-{{L}_{i}}-{{T}_{i-1}}+{{L}_{i-1}}}{{{T}_{i}}-{{T}_{i-1}}} \right)(t-{{T}_{i-1}}) \right]}^{(\beta -1)}}</math>
 
 
where  <math>{{T}_{i-1}}\le t\le {{T}_{i}}</math>  and  <math>{{T}_{i}}</math>  is the test time of each corresponding test phase.
<br>
The actual idealized curve MTBF is:
 
 
::<math>{{M}_{AI}}=\frac{1}{{{r}_{AI}}(t)}</math>
 
 
====Actual Time to Reach Goal====
<br>
The actual time to reach the target MTBF or failure intensity goal,  <math>{{t}_{AC,G}},</math>  can be found by solving Eqn. (ActIhase):
 
 
::<math>\begin{align}
  & {{r}_{AI}}({{t}_{AC,G}})= & {{\lambda }_{A}}+(1-d){{\lambda }_{B}} \\
&  & +d\lambda \beta {{\left[ {{T}_{i-1}}-{{L}_{i-1}}+\left( \frac{{{T}_{i}}-{{L}_{i}}-{{T}_{i-1}}+{{L}_{i-1}}}{{{T}_{i}}-{{T}_{i-1}}} \right)({{t}_{AC,G}}-{{T}_{i-1}}) \right]}^{(\beta -1)}} 
\end{align}</math>
 
 
Since the actual idealized growth curve depends on the phase durations and average fix delays, there are three different cases that need to be treated differently in order to determine the actual time to reach the MTBF goal. The cases depend on when the actual MTBF that can be reached within the specific phase durations and fix delays becomes equal to the MTBF goal. This can be determined by solving Eqn. (ActIhase) for phases  <math>1</math>  through  <math>i</math> , then solving in terms of actual MTBF using Eqn. (MTBFctualq) for each phase and finding the phase during which the actual MTBF becomes equal to the goal MTBF. The three cases are presented next.
 
''Case 1: MTBF goal is met during the last phase''
<br>
If  <math>{{T}_{F}}</math>  indicates the cumulative end phase time for the last phase and  <math>{{L}_{F}}</math>  indicates the fix delay for the last phase, then we have:
 
 
::<math>\begin{align}
  & {{r}_{G}}= & {{\lambda }_{A}}+(1-d){{\lambda }_{B}} \\
&  & +d\lambda \beta {{\left[ {{T}_{F-1}}-{{L}_{F-1}}+\left( \frac{{{T}_{F}}-{{L}_{F}}-{{T}_{F-1}}+{{L}_{F-1}}}{{{T}_{F}}-{{T}_{F-1}}} \right)({{t}_{AC,G}}-{{T}_{F-1}}) \right]}^{(\beta -1)}} 
\end{align}</math>
 
 
Starting to solve for  <math>{{t}_{AC,G}}</math>  yields:
 
 
::<math>{{\left[ \frac{{{r}_{G}}-{{\lambda }_{A}}-(1-d){{\lambda }_{B}}}{d\lambda \beta } \right]}^{\tfrac{1}{\beta -1}}}={{T}_{F-1}}-{{L}_{F-1}}+\left( \frac{{{T}_{F}}-{{L}_{i}}-{{T}_{F-1}}+{{L}_{F-1}}}{{{T}_{F}}-{{T}_{F-1}}} \right)({{t}_{AC,G}}-{{T}_{F-1}})</math>
 
 
We can substitute the left term by using Eqn. (tgoalominal), thus we have:
 
 
::<math>{{t}_{N,G}}={{T}_{F-1}}-{{L}_{F-1}}+\left( \frac{{{T}_{F}}-{{L}_{F}}-{{T}_{F-1}}+{{L}_{F-1}}}{{{T}_{F}}-{{T}_{F-1}}} \right)({{t}_{AC,G}}-{{T}_{i-1}})</math>
 
 
:Therefore:
 
 
::<math>{{t}_{AC,G}}=\frac{{{t}_{N,G}}-{{T}_{F-1}}+{{L}_{F-1}}}{\left( \tfrac{{{T}_{F}}-{{L}_{F}}-{{T}_{F-1}}+{{L}_{F-1}}}{{{T}_{F}}-{{T}_{F-1}}} \right)}+{{T}_{F-1}}</math>
 
 
''Case 2: MTBF goal is met before the last phase''
<br>
Eqn. (toalctual) still applies, but in this case  <math>{{T}_{F}}</math>  and  <math>{{L}_{F}}</math>  are the time and fix delay of the phase during which the goal is met.
<br>
<br>
''Case 3: MTBF goal is met after the final phase''
<br>
If the goal MTBF,  <math>{{M}_{G}},</math>  is met after the final test phase, then the actual time to reach the goal is not calculated, since additional phases have to be added with specific duration and fix delays. The reliability growth program needs to be re-evaluated with the following options:
<br>
<br>
:• Add more phase(s) to the program.
:• Re-examine the phase duration of the existing phases.
:• Investigate whether there are potential process improvements in the program that can <br>
reduce the average fix delay for the phases.
<br>
Other alternative routes for consideration would be to investigate the rest of the inputs in the model:
<br>
<br>
:• Change the management strategy.
:• Consider if further program risk can be acceptable, and if so, reduce the growth potential design margin.
:• Consider if it is feasible to increase the effectiveness factors of the delayed fixes by using more robust engineering redesign methods.
<br>
Note that each change of input variables into the model can significantly influence the results. <br>
With that in mind, any alteration in the input parameters should be justified by actionable decisions that will influence the reliability growth program. For example, increasing the average effectiveness factor value should be done only when there is proof that the program will pursue a different, more effective path in terms of addressing fixes.
<br>
<br>
 
==Reliability Growth Planning Examples==
<br>
===Example 1===
<br>
A complex system is under design. The reliability team wants to create an overall reliability growth plan based on the Crow Extended model. The inputs to the model are the following:
<br>
<br>
:• The requirement or goal MTBF is  <math>{{M}_{G}}=56</math>  hours.
:• The Growth Potential Design Margin Factor is  <math>GPDM=1.35</math> .
:• The Average Effectiveness Factor is  <math>d\quad =0.7.</math>
:• The Management Strategy is  <math>msr=0.95</math> .
:• The beta parameter for the discovery function,  <math>h\left( t \right),</math>  of the Type B failure modes is  <math>\beta =0.7.</math>
:• The test will be conducted in three phases. The cumulative phase end times are  <math>{{T}_{1}}=1500,{{T}_{2}}=3500</math>  and  <math>{{T}_{3}}=4500</math>  hours. The average fix delays for each phase are    and  <math>{{L}_{3}}=1000</math>  test hours, respectively.
<br>
<br>
Find the following:
<br>
:1) The growth potential MTBF and failure intensity.
:2) The initial failure intensity.
:3) The Type A and Type B initial failure intensity.
:4) The parameter  <math>\lambda </math>  of the Crow Extended model.
:5) The Type B failure mode discovery function.
:6) The initialization time,  <math>{{t}_{0}},</math>  for the nominal failure intensity function.
:7) The nominal idealized failure intensity function.
:8) The nominal time to reach the MTBF goal.
:9) The MTBF that can be reached at the end of the last test phase based on the nominal idealized growth curve.
:10) The actual initialization time for Phase 1,  <math>T_{0}^{AIC}.</math>
:11) The MTBF that can be reached at the end of the last test phase based on the actual idealized growth curve.
:12) The actual time to reach the MTBF goal.
:13) The actual time to reach the MTBF goal if the cumulative end phase time for the third (last) phase is  <math>{{T}_{3}}=6000</math>  hours.
:14) Use RGA 7 to generate the results for this example. Consider the cumulative last phase as  <math>{{T}_{3}}=6000</math>  hours, as given in question 13.
 
'''Solution'''
<br>
:1) Based on Eqn. (MP), the growth potential MTBF is:
 
::<math>\begin{align}
  & {{M}_{GP}}= & 56\cdot 1.35 \\
& = & 75.6 
\end{align}</math>
 
From Eqn. (lambda GP), the growth potential failure intensity is:
 
::<math>\begin{align}
  & {{\lambda }_{GP}}= & \frac{1}{{{M}_{GP}}} \\
& = & \frac{1}{75.6} \\
& = & 0.0132 
\end{align}</math>
 
:2) The initial failure intensity is given by Eqn. (lambda):
 
::<math>\begin{align}
  & {{\lambda }_{I}}= & \frac{{{\lambda }_{GP}}}{1-d\cdot msr} \\
& = & \frac{0.0132}{\left( 1-0.7\cdot 0.95 \right)} \\
& = & 0.0394 
\end{align}</math>
 
:3) From Eqn. (lambda), the Type A failure mode intensity,  <math>{{\lambda }_{A}},</math>  is:
 
From Eqn. (Lambda), the Type B failure mode intensity,  <math>{{\lambda }_{B}},</math>  is:
 
::<math>\begin{align}
  & {{\lambda }_{B}}= & msr\cdot {{\lambda }_{I}} \\
& = & 0.95\cdot 0.0394 \\
& = & 0.0375 
\end{align}</math>
 
:4) Using the inputs of  <math>{{\lambda }_{B}}</math>  and  <math>\beta </math>  in Eqn. (lambdaithamma) we have:
 
::<math>0.0375=\frac{{{\lambda }^{\left( \tfrac{1}{0.7} \right)}}}{\Gamma \left( 1+\tfrac{1}{0.7} \right)}</math>
 
:or:
 
::<math>0.0375=\frac{{{\lambda }^{1.428}}}{1.2658}</math>
 
:or:
 
::<math>\begin{align}
  & \lambda = & {{\left( 0.0375\cdot 1.2658 \right)}^{\left( \tfrac{1}{1.428} \right)}} \\
& = & 0.1184 
\end{align}</math>
 
:5) The Type B failure mode discovery function is:
 
::<math>h\left( t \right)=\lambda \beta {{t}^{\beta -1}}</math>
 
Since we know the  <math>\lambda </math>  and  <math>\beta </math>  parameters, we have:
 
::<math>\begin{align}
  & h\left( t \right)= & 0.1183\cdot 0.7{{t}^{0.7-1}} \\
& = & 0.0828{{t}^{-0.3}} 
\end{align}</math>
 
:6) Based on Eqn. (initilization time), the initialization time,  <math>{{t}_{0}},</math>  is:
 
::<math>\begin{align}
  & {{t}_{0}}= & {{\left[ \frac{{{\lambda }_{I}}-{{\lambda }_{A}}-(1-d){{\lambda }_{B}}}{d\lambda \beta } \right]}^{\tfrac{1}{\beta -1}}} \\
& = & {{\left[ \frac{0.0394-0.001974-(1-0.7)0.0375}{0.7\cdot 0.1183\cdot 0.7} \right]}^{\tfrac{1}{0.7-1}}} 
\end{align}</math>
 
:or:
 
::<math>{{t}_{0}}=14.07</math>
 
:7) Based on Eqns. (Nominal FI) and (Nominal FI for time less than t0), the nominal idealized growth curve is given by the following equation:
 
::<math>{{r}_{NI}}\left( t \right)=\left\{ \begin{matrix}
  {{\lambda }_{I}} & t\le {{t}_{0}}  \\
  \begin{matrix}
  {{r}_{IT}}(t)={{\lambda }_{A}}+(1-d){{\lambda }_{B}}+d\lambda \beta {{t}^{\left( \beta -1 \right)}}  \\
\end{matrix} & t>{{t}_{0}}  \\
\end{matrix} \right\}</math>
 
:or:
 
::<math>{{r}_{NI}}\left( t \right)=\left\{ \begin{matrix}
  0.0394 & t\le 14.07  \\
  =0.0013+0.058\cdot {{t}^{-0.3}} & t>14.07  \\
\end{matrix} \right\}</math>
 
:8) Based on Eqn. (tgoalominal), the nominal time to reach the MTBF goal is:
 
::<math>{{t}_{N,goal}}={{\left[ \frac{{{r}_{G}}-{{\lambda }_{A}}-(1-d){{\lambda }_{B}}}{d\lambda \beta } \right]}^{\tfrac{1}{\beta -1}}}</math>
 
For the goal failure intensity we have:
 
::<math>\begin{align}
  & {{r}_{G}}= & \frac{1}{{{M}_{G}}} \\
& = & \frac{1}{56} \\
& = & 0.01785 
\end{align}</math>
 
So the nominal time to reach the MTBF goal is:
 
::<math>\begin{align}
  & {{t}_{N,G}}= & {{\left[ \frac{0.01785-0.001974-(1-0.7)0.0375}{0.7\cdot 0.1184\cdot 0.7} \right]}^{^{\tfrac{1}{\beta -1}}}} \\
& = & 4578\text{ hours} 
\end{align}</math>
 
:9) Using Eqn. (Nominal FI) we find the failure intensity that can be reached at the end of the last test phase based on the nominal idealized growth curve,  <math>{{r}_{NI,final}}</math> . The total (cumulative) test time is  <math>T=4500</math>  hours. Therefore we have:
 
::<math>\begin{align}
  & {{r}_{NI,final}}= & {{\lambda }_{A}}+(1-d){{\lambda }_{B}}+d\lambda \beta {{T}^{\left( \beta -1 \right)}}\text{ } \\
& = & 0.0019+\left( 1-0.7 \right)0.0375+0.7\cdot 0.1184\cdot 0.7\cdot {{(4500)}^{0.7-1}} \\
& = & 0.01788 
\end{align}</math>
 
So the nominal final MTBF that can be reached at 4500 hours of test time is:
 
::<math>\begin{align}
  & {{M}_{NI,final}}= & \frac{1}{{{r}_{NI,final}}} \\
& = & \frac{1}{0.01788} \\
& = & 55.92 
\end{align}</math>
 
:10) We can find the actual initialization time by using Eqn. (actualnitilizationime):
 
 
::<math>T_{0}^{AIC}=\frac{{{t}_{0}}}{\left( \tfrac{{{T}_{1}}-{{L}_{1}}}{{{T}_{1}}} \right)}</math>
 
For question 6, we had found that  <math>{{t}_{0}}=14.07</math> . So we have:
 
::<math>\begin{align}
  & T_{0}^{AIC}= & \frac{14.07}{\left( \tfrac{1500-500}{1500} \right)} \\
& = & 21.10887 
\end{align}</math>
 
:11) The failure intensity that can be reached at the end of the last test phase based on the actual idealized growth curve is given by Eqn. (ActIhase) for  <math>T=4500</math>  hours:
 
::<math>\begin{align}
  & {{r}_{AI,final}}(T)= & {{\lambda }_{A}}+(1-d){{\lambda }_{B}} \\
&  & +d\lambda \beta {{\left[ {{T}_{2}}-{{L}_{2}}+\left( \frac{{{T}_{3}}-{{L}_{3}}-{{T}_{2}}+{{L}_{2}}}{{{T}_{3}}-{{T}_{2}}} \right)(T-{{T}_{2}}) \right]}^{(\beta -1)}} 
\end{align}</math>
 
:Therefore:
 
::<math>\begin{align}
  & {{r}_{AI,final}}(T)= & 0.0019+\left( 1-0.7 \right)0.0375+0.7\cdot 0.1184\cdot 0.7 \\
&  & \cdot {{\left[ 3500-700+\left( \frac{4500-1000-3500+700}{4500-3500} \right)(4500-3500) \right]}^{(0.7-1)}} 
\end{align}</math>
 
:Therefore:
 
::<math>{{r}_{AI,final}}(T)=0.0182</math>
 
So the actual final MTBF that can be reached at 4500 hours of test time is:
 
::<math>\begin{align}
  & {{M}_{AI,final}}= & \frac{1}{{{r}_{AI,final}}} \\
& = & \frac{1}{0.0182} \\
& = & 54.80 
\end{align}</math>
 
:12) From question 11, it is shown that the actual final MTBF that can be reached at 4500 hours of test time is less than the MTBF goal for the program. So, in accordance with the third case that is described in Section 11.2.4.3, this is the scenario where the actual time to meet the MTBF goal will not be calculated since the reliability growth program needs to be redesigned.
 
:13) The failure intensity that can be reached at the end of the last test phase based on the actual idealized growth curve is given by Eqn. (ActIhase) for  <math>T={{T}_{3}}=6000</math>  hours:
 
::<math>\begin{align}
  & {{r}_{AI,final}}(T)= & {{\lambda }_{A}}+(1-d){{\lambda }_{B}} \\
&  & +d\lambda \beta {{\left[ {{T}_{2}}-{{L}_{2}}+\left( \frac{{{T}_{3}}-{{L}_{3}}-{{T}_{2}}+{{L}_{2}}}{{{T}_{3}}-{{T}_{2}}} \right)(T-{{T}_{2}}) \right]}^{(\beta -1)}} 
\end{align}</math>
 
:Therefore:
 
::<math>\begin{align}
  & {{r}_{AI,final}}(T)= & 0.0019+\left( 1-0.7 \right)0.0375+0.7\cdot 0.1184\cdot 0.7 \\
&  & \cdot {{\left[ 3500-700+\left( \frac{6000-1000-3500+700}{6000-3500} \right)(6000-3500) \right]}^{(0.7-1)}} 
\end{align}</math>
 
:Therefore:
 
::<math>{{r}_{AI,final}}(T)=0.0177</math>
 
So, the actual final MTBF that can be reached at 6000 hours of test time is:
 
::<math>\begin{align}
  & {{M}_{AI,final}}= & \frac{1}{{{r}_{AI,final}}} \\
& = & \frac{1}{0.0177} \\
& = & 56.38 
\end{align}</math>
 
In this case, the actual MTBF goal becomes higher than the target MTBF sometime during the last phase. Using Eqn. (toalctual), we can determine the actual time to reach the MTBF goal:
 
::<math>{{t}_{AC,G}}=\frac{{{t}_{N,G}}-{{T}_{F-1}}+{{L}_{F-1}}}{\left( \tfrac{{{T}_{F}}-{{L}_{F}}-{{T}_{F-1}}+{{L}_{F-1}}}{{{T}_{F}}-{{T}_{F-1}}} \right)}+{{T}_{F-1}}</math>
 
:Therefore:
 
::<math>{{t}_{AC,G}}=\frac{4578-3500+700}{\left( \tfrac{6000-1000-3500+700}{6000-3500} \right)}+3500</math>
 
:Then:
 
::<math>{{t}_{AC,G}}=5521</math>
 
:14) In the RGA 7 Project Explorer we right-click Growth Planning and select Add Growth Planning. We then specify the number of phases, and the cumulative phase time and average fix delays for each of the three phases, as shown in Figure phases.
 
<br>
[[Image:rga11.1.png|thumb|center|300px|Specifying number of phases, phase time and average fix delay.]]
<br>
<br>
When we click the Calculate icon, the input window for the Crow Extended model parameters appears, as shown in Figure calculations. The input provided is the required MTBF goal of 56, the growth potential design margin of 1.35, the management strategy of 0.95  and the discovery beta of 0.7. The results show the initialization time,  <math>{{t}_{o}}</math> , the initial MTBF, the final actual MTBF that can be reached for this growth program and the actual time when the MTBF goal is met. Note that in this case we provided the goal MTBF and solved for the initial MTBF.
 
 
Different calculation options are available depending on the desired input and output. For example, we could provide the initial and goal MTBF and solve for the growth potential design margin, as shown in Figure calculations2.
By clicking the Calculate icon in the Planning Calculations window, we can then return to the main growth planning window where the planning information and results are presented, as shown in Figure Planning information panel.
<math></math>
 
By clicking the Plot icon, we can then generate a plot that shows the nominal and actual idealized growth curve, the test termination time, the MTBF goal and the planned growth for each phase, as shown in Figure Growth Planning plot.
 
<math></math>
[[Image:rga11.2.png|thumb|center|300px|Inputs for the Crow Extended model, when calculating the initial MTBF.]]
<br>
<br>
[[Image:rga11.3.png|thumb|center|300px|Inputs for the Crow Extended model when calculating the Growth Potential Design Margin.]]
<br>
<br>
[[Image:rga11.4.png|thumb|center|300px|Growth Planning window showing phase information, model inputs and results.]]
<br>
<br>
[[Image:rga11.5.png|thumb|center|300px|Growth planning plot.]]
<br>
<br>
 
===Example 2===
The reliability team of a product manufacturer is putting together a reliability growth plan for one of the new products under design. The reliability team wants to create an overall reliability growth plan based on the Crow Extended model. The inputs to the model are the following:
<br>
:• The requirement or goal MTBF is  <math>{{M}_{G}}=100</math>  hours.
:• The Growth Potential Design Margin Factor is  <math>GPDM=1.15</math> .
:• The Average Effectiveness Factor is  <math>d\quad =0.6,</math>  based on historical information for similar products developed by the company.
:• The Management Strategy is  <math>msr=0.90</math> .
:• The beta parameter for the discovery function,  <math>h\left( t \right),</math>  of the Type B failure modes is  <math>\beta =0.71</math> , based on data analysis of the previous product development project that was of similar nature.
:• The test will be conducted in seven phases. The cumulative phase end times are  <math>{{T}_{1}}=4000,{{T}_{2}}=8000</math> ,  <math>{{T}_{3}}=12000,</math>  <math>{{T}_{4}}=20000,</math> 
:• <math>{{T}_{5}}=25000,</math>  <math>{{T}_{6}}=30000</math>  and  <math>{{T}_{7}}=40000</math>  hours. The average fix delay for each phase is one week. For the first two phases, the plan is to test 1000 hours per week, so the average fix delay in terms of test hours for Phases 1 and 2 is  <math>{{L}_{1}}=1000</math>  and    hours. For Phases 3 and 4, the prototype test units are planned to be doubled, so the average fix delay in terms of test hours within one week also is going to be doubled, so we have:  <math>{{L}_{3}}=2000</math>  and  <math>{{L}_{4}}=2000</math>  hours. For Phases 5 and 6, a second shift is going to be added, so the amount of test hours within a week is going to be doubled again. Therefore, the average fix delay in terms of test hours within one week also is going to be doubled:  <math>{{L}_{5}}=4000</math>  and  <math>{{L}_{6}}=4000</math>  hours. For the last phase, more units and weekend shifts are planned to be added, so the total test hours within one week are going to be 6000 hours. In accordance, the average fix delay in terms of test hours will be  <math>{{L}_{7}}=6000</math>  hours.
<br>
Construct a reliability growth plan with RGA 7 and make sure that the goal MTBF can be met within the total test hours allocated for growth testing. If not, make necessary changes in the phase durations in order to meet the goal.
 
'''Solution'''
<br>
Figure 7 phases  shows the planning input in RGA 7, in terms of test phases and average fix delays.
Figure Examplelanningalculations shows the planning calculations based on the goal MTBF of 100 hours and the rest of the known inputs into the model. As seen by the planning calculation results, the final actual MTBF at the end of the seventh phase is 98.66 hours, which is less than the MTBF goal of 100 hours. Also, in Figure results example 2, it is shown that the nominal time to meet the MTBF goal is 48420 hours, which is higher than the total test time that is currently planned to be allocated for reliability growth.
 
<math></math>
[[Image:rga11.6.png|thumb|center|300px|Growth planning in seven phases.]]
 
<br>
[[Image:rga11.7.png|thumb|center|300px|Planning model inputs and results for the initial plan.]]
 
<math></math>
[[Image:rga11.8.png|thumb|center|300px|Planning model with results for the initial plan.]]
<br>
<br>
[[Image:rga11.9.png|thumb|center|300px|Reliability growth plan with revised phase durations.]]
 
<br>
<br>
A new plan needs to be considered. The reliability team decides to increase the test time for Phases 5 and 6 to be 10000 hours each, instead of the 5000 hours that were considered in the initial plan. Also, the team decides to increase the duration of the seventh phase to 15000 hours. Since this is going to be achieved by testing for more calendar time in Phases 5, 6 and 7, the average fix delay during those phases is the same as the one in the initial plan. The test time per week is not going to be affected, only more weeks will be added to the schedule. Figure resived plan shows the revised plan, together with the calculated results. The actual time to meet the MTBF goal is now 54331 hours. The final MTBF that can be achieved at the end of the 55000 hours of growth testing is 100.04, which is slightly higher than the goal MTBF of 100 hours. The reliability team considers this plan as acceptable, since the MTBF goal will be met. Figure growth plot example 2 shows the overall reliability growth plan, with the nominal and actual growth curves, the MTBF goal line and the planned MTBF for each of the seven phases.
 
<math></math>
[[Image:rga11.10.png|thumb|center|300px|Growth planning plot for the seven plhases with the revised plan.]]
 
===Example 3===
<br>
The reliability team of a product manufacturer has put together a reliability growth plan, based on the Crow Extended model, for one of their new products. The reliability growth model was constructed with the following inputs:
<br>
<br>
:• The requirement or goal MTBF is  <math>{{M}_{G}}=910</math>  hours.
:• The Growth Potential Design Margin Factor is  <math>GPDM=1.35</math> .
:• The Average Effectiveness Factor is  <math>d\quad =0.7.</math>
:• The Management Strategy is 
:• <math>msr=0.95</math> .
:• The beta parameter for the discovery function,  <math>h\left( t \right),</math>  of the Type B failure modes is  <math>\beta =0.70</math> .
:• The test is planned to be conducted in four phases. The cumulative phase end times are  <math>{{T}_{1}}=19000,{{T}_{2}}=38000</math> ,  <math>{{T}_{3}}=70000</math>  and  <math>{{T}_{4}}=100000</math> . The average fix delay in terms of test hours for each phase is:  <math>{{L}_{1}}=10000</math> ,  <math>{{L}_{2}}=15000,</math>  <math>{{L}_{3}}=20000</math>  and  <math>{{L}_{4}}=25000</math>  hours.
<br>
<br>
:1) Plot the nominal and actual reliability growth curves for this program, using RGA 7.
<br>
:2) The reliability program was initiated and actual test data from Phase 1 is now available. The test data were analyzed using the Crow Extended - Continuous Evaluation model and Figure CECE data phase 1 shows the results. Note that the I events, which represent the times for implementation of fixes for BD modes, occur at least 10000 hours after the first occurrence of the specific BD mode. This is a reflection of the average fix delay being equal to 10000 hours for the first test phase. Of course we could have some exceptions that could have been fixed before 10000 hours after the first occurrence (i.e. discovery) of the mode, but on average, they should be fixed after 10000 hours.
The same applies to the delayed fixes at the end of Phase 1; on average there should be at least 10000 test hours between the discovery of the failure mode and the implementation of a fix for that mode, so failure modes discovered after 9000 hours of testing in the first phase cannot be implemented at the end of the first phase.
<br>
 
Figure EF window Example 3 shows the effectiveness factor window, where it is shown that fixes for failure modes BD 11000, BD 12000 and BD 13000 are not implemented at the end of the first phase due to the fix delay. The effectiveness factor used is in accordance with the planning model and has been fixed to 0.7.
 
<math></math>
[[Image:rga11.11.png|thumb|center|300px|Phase 1 data, analyzed with the Crow Extended- Continuous Evaluation model.]]
<br>
<br>
[[Image:rga11.12.png|thumb|center|300px|Fixed effectiveness factor and phase of implementation for unfixed BD modes in Phase 1.]]
<br>
<br>
Construct a multi-phase graph that shows the analysis points for the test data in Phase 1, as compared to the nominal and actual idealized growth curves for this reliability growth plan. Is the program on track, so far, as compared to the plan?
 
'''Solution'''
<br>
:1) Figures inputs example 3 and planning info show the plan inputs, phase durations and average fix delays as entered in RGA 7, together with the results of the growth model. Figure plan plot shows the nominal and actual idealized growth curves for this program, together with the program MTBF goal.
 
<math></math>
[[Image:rga11.13.png|thumb|center|300px|Inputs in reliability growth planning model.]]
 
<math></math>
[[Image:rga11.14.png|thumb|center|300px|Reliability growth planning information and results.]]
<br>
<br>
<br>
[[Image:rga11.15.png|thumb|center|300px|Nominal and actual idealized growth curves with planned growth in four phases.]]
 
<br>
:2) The next step is to associate the reliability growth plan with the data from phase 1. To do that, we right-click Additional Plots in the Project Explorer and choose Add MultiPhase Plot from the shortcut menu then follow the wizard to specify the data sheet that contains the phase 1 data with the Folio that defines the growth plan. Figure Multi-Phase shows the generated Multiple Phase Plot, which brings together the reliability growth planning model with the actual test results. This plot shows the demonstrated MTBF for each analysis point during the first phase of testing. Analysis points for projected and growth potential MTBF also can be plotted. For this example, it can be said that the program is on track since the demonstrated MTBF of the first phase is higher than the planned MTBF for that phase.
The Multiple Phase Plot can be continuously updated as the growth program progresses and more test data becomes available. In that manner, the reliability team can assess actual reliability performance against the established goals.
 
<math></math>
[[Image:rga11.16.png|thumb|center|300px|Multi-Phase plot containing the overall growth plan and the actual test results for Phase 1.]]

Revision as of 21:34, 10 January 2012

New format available! This reference is now available in a new format that offers faster page load, improved display for calculations and images, more targeted search and the latest content available as a PDF. As of September 2023, this Reliawiki page will not continue to be updated. Please update all links and bookmarks to the latest reference at help.reliasoft.com/reference/reliability_growth_and_repairable_system_analysis

Chapter 11: Reliability Growth Planning


RGAbox.png

Chapter 11  
Reliability Growth Planning  

Synthesis-icon.png

Available Software:
RGA

Examples icon.png

More Resources:
RGA examples


New format available! This reference is now available in a new format that offers faster page load, improved display for calculations and images, more targeted search and the latest content available as a PDF. As of September 2023, this Reliawiki page will not continue to be updated. Please update all links and bookmarks to the latest reference at help.reliasoft.com/reference/reliability_growth_and_repairable_system_analysis

Chapter 11: Reliability Growth Planning


RGAbox.png

Chapter 11  
Reliability Growth Planning  

Synthesis-icon.png

Available Software:
RGA

Examples icon.png

More Resources:
RGA examples


Template loop detected: Template:Reliability growth planning rga

Retrieved from "https://www.reliawiki.com/index.php?title=Reliability_Growth_Planning&oldid=11628"