Equivalent System Example: Difference between revisions

From ReliaWiki
Jump to navigation Jump to search
(Created page with '<noinclude>{{Banner RGA Examples}} ''This example appears in the Reliability Growth and Repairable System Analysis Reference''.</noinclude> This example uses …')
 
No edit summary
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<noinclude>{{Banner RGA Examples}}
<noinclude>{{Banner RGA Examples}}
''This example appears in the [[Crow_Extended|Reliability Growth and Repairable System Analysis Reference]]''.</noinclude>
''This example appears in the [https://help.reliasoft.com/reference/reliability_growth_and_repairable_system_analysis Reliability growth reference]''.
</noinclude>


<noinclude>This example uses the Multiple with Event Codes data type to demonstrate how implemented fixes (I events) are taken into account when building an equivalent system.</noinclude>
Consider the data set shown in the following figure. <!-- IMPORTANT: If you edit the data in this example, you must edit the reference to the results in Crow_Extended#Transferring_Data_to_an_Equivalent_Single_System-->


This example uses the Multiple with Event Codes data type to demonstrate how implemented fixes (I events) are taken into account when building an equivalent system. Consider the data set shown in the following figure.
[[Image:rga9.15.png|center|600px]]
 
[[Image:rga9.15.png|center|500px|Three systems with event codes.]]


'''Solution'''
'''Solution'''


The first step to creating the equivalent system is to isolate each failure mode and its implemented fixes independently from each other. The numbered items follow the five rules <noinclude>mentioned in the article [[Crow_Extended#Equivalent_Single_System|Equivalent Single System]]</noinclude> and are presented in the same numbering sequence. 
The first step to creating the equivalent system is to isolate each failure mode and its implemented fixes independently from each other. The numbered steps follow the five rules <noinclude>mentioned in the article [[Crow_Extended#Equivalent_Single_System|Equivalent Single System]]</noinclude> and are presented in the same numbering sequence. 
 
:1. The next figure illustrates the application of rule #1 for mode BD1. The mode in the equivalent single system is calculated as <math>(75+75+75)=225\,\!</math> or <math>75*3=225.\,\!</math>
 
[[Image:rga9.16.png|thumb|center|400px|Calculating a BD mode.]]
 
 
::While the next figure illustrates the application of rule #1 for mode A110. The mode in the equivalent single system is calculated as <math>(280+280+280)=840\,\!</math> or <math>280*3=840.\,\!</math>
 
[[Image:rga9.17.png|thumb|center|400px|Calculating an A mode.]]
 
 
:2. The next figure illustrates the application of rule #2 for the first occurrence of the mode BC10 in system 1. The mode in the equivalent single system is calculated as <math>(150+150+150)=450\,\!</math> or <math>150*3=450.\,\!</math>


[[Image:rga9.18.png|thumb|center|400px|Calculating a BC mode that occurred before an implemented fix.]]
<ol>
<li>The next figure illustrates the application of rule #1 for mode BD1. The mode in the equivalent single system is calculated as <math>(75+75+75)=225\,\!</math> or <math>75*3=225.\,\!</math>


[[Image:rga9.16.png|center|450px]]


:3. The next figure illustrates the application of rule #3 for implemented fixes (''I'' events) of the mode BC10. In the graph, the ''I'' events are symbolized by having the letter "I" before the naming of the mode. In this case, IBC10 is for the implemented fix of mode BC10. The IBC10 in the equivalent single system is calculated as <math>(200+175+200)=575\,\!</math>.  
The next figure illustrates the application of rule #1 for mode A110. The mode in the equivalent single system is calculated as <math>(280+280+280)=840\,\!</math> or <math>280*3=840.\,\!</math>


[[Image:rga9.19.png|thumb|center|400px|Calculating an implementation event.]]
[[Image:rga9.17.png|center|450px]]
</li>
<li>The next figure illustrates the application of rule #2 for the first occurrence of the mode BC10 in system 1. The mode in the equivalent single system is calculated as <math>(150+150+150)=450\,\!</math> or <math>150*3=450.\,\!</math>


[[Image:rga9.18.png|center|450px]]


:4. The next figure illustrates the application of rule #4 for the mode BC20 in system 1, which occurs after a fix for the same mode was implemented in system 2. The mode in the equivalent single system is calculated as <math>(350+300+350)=1000.\,\!</math>  
</li>
<li>The next figure illustrates the application of rule #3 for implemented fixes (''I'' events) of the mode BC10. In the graph, the ''I'' events are symbolized by having the letter "I" before the naming of the mode. In this case, IBC10 is for the implemented fix of mode BC10. The IBC10 in the equivalent single system is calculated as <math>(200+175+200)=575\,\!</math>.


[[Image:rga9.20.png|thumb|center|400px|Calculating a BC mode that occurred after I events.]]
[[Image:rga9.19.png|center|450px]]


</li>
<li>The next figure illustrates the application of rule #4 for the mode BC20 in system 1, which occurs after a fix for the same mode was implemented in system 2. The mode in the equivalent single system is calculated as <math>(350+300+350)=1000.\,\!</math>


:5. The next figure illustrates the application of rule #5 for the second occurrence of the mode BC10 in system 1, which occurs after an implemented fix (''I'' event) has occurred for that mode in the same system. The mode in the equivalent single system is calculated as <math>575+(175+200+175)=1125.\,\!</math>
[[Image:rga9.20.png|center|450px]]


[[Image:rga9.21.png|thumb|center|400px|Calculating a second occurrence of a BC mode in the same system, after I events have been implemented.]]
</li>
<li>The next figure illustrates the application of rule #5 for the second occurrence of the mode BC10 in system 1, which occurs after an implemented fix (''I'' event) has occurred for that mode in the same system. The mode in the equivalent single system is calculated as <math>575+(175+200+175)=1125.\,\!</math>


[[Image:rga9.21.png|center|450px]]


After having transferred the data set to the Crow Extended equivalent system, the data set is analyzed using the Crow Extended model. The last figure shows the growth potential MTBF plot.
After having transferred the data set to the Crow Extended equivalent system, the data set is analyzed using the Crow Extended model. The last figure shows the growth potential MTBF plot.


[[Image:rga9.22.png|thumb|center|400px|Growth Potential MTBF plot from three systems with event codes.]]
[[Image:rga9.22.png|center|450px]]
</li>
</ol>

Latest revision as of 20:53, 18 September 2023

RGA Examples Banner.png


New format available! This reference is now available in a new format that offers faster page load, improved display for calculations and images and more targeted search.

As of January 2024, this Reliawiki page will not continue to be updated. Please update all links and bookmarks to the latest references at RGA examples and RGA reference examples.



This example appears in the Reliability growth reference.


This example uses the Multiple with Event Codes data type to demonstrate how implemented fixes (I events) are taken into account when building an equivalent system. Consider the data set shown in the following figure.

Rga9.15.png

Solution

The first step to creating the equivalent system is to isolate each failure mode and its implemented fixes independently from each other. The numbered steps follow the five rules mentioned in the article Equivalent Single System and are presented in the same numbering sequence. 

  1. The next figure illustrates the application of rule #1 for mode BD1. The mode in the equivalent single system is calculated as [math]\displaystyle{ (75+75+75)=225\,\! }[/math] or [math]\displaystyle{ 75*3=225.\,\! }[/math]
    Rga9.16.png

    The next figure illustrates the application of rule #1 for mode A110. The mode in the equivalent single system is calculated as [math]\displaystyle{ (280+280+280)=840\,\! }[/math] or [math]\displaystyle{ 280*3=840.\,\! }[/math]

    Rga9.17.png
  2. The next figure illustrates the application of rule #2 for the first occurrence of the mode BC10 in system 1. The mode in the equivalent single system is calculated as [math]\displaystyle{ (150+150+150)=450\,\! }[/math] or [math]\displaystyle{ 150*3=450.\,\! }[/math]
    Rga9.18.png
  3. The next figure illustrates the application of rule #3 for implemented fixes (I events) of the mode BC10. In the graph, the I events are symbolized by having the letter "I" before the naming of the mode. In this case, IBC10 is for the implemented fix of mode BC10. The IBC10 in the equivalent single system is calculated as [math]\displaystyle{ (200+175+200)=575\,\! }[/math].
    Rga9.19.png
  4. The next figure illustrates the application of rule #4 for the mode BC20 in system 1, which occurs after a fix for the same mode was implemented in system 2. The mode in the equivalent single system is calculated as [math]\displaystyle{ (350+300+350)=1000.\,\! }[/math]
    Rga9.20.png
  5. The next figure illustrates the application of rule #5 for the second occurrence of the mode BC10 in system 1, which occurs after an implemented fix (I event) has occurred for that mode in the same system. The mode in the equivalent single system is calculated as [math]\displaystyle{ 575+(175+200+175)=1125.\,\! }[/math]
    Rga9.21.png

    After having transferred the data set to the Crow Extended equivalent system, the data set is analyzed using the Crow Extended model. The last figure shows the growth potential MTBF plot.

    Rga9.22.png
Retrieved from "https://www.reliawiki.com/index.php?title=Equivalent_System_Example&oldid=66053"