Template:Time-to-failure data: Difference between revisions

From ReliaWiki
Jump to navigation Jump to search
(Redirected page to RGA Data Types)
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
===Time-to-Failure Data===
#REDIRECT [[RGA_Data_Types]]
Time-to-failure (continuous) data is the most commonly observed type of reliability growth data. It involves recording the times-to-failure for the unit(s) under test. Time-to-failure data can be applied to a single unit or system or to multiple units or systems. There are multiple data entry schemes for this data type and each is presented next.
{{failure times data}}
 
 
{{grouped failure times}}
 
====Multiple Systems (Known Operating Times)====
This data type is used for tests where a number of systems are tested. If a failure occurs in any system, a corrective action is taken on the failed unit and any design changes are incorporated into all test systems. Once the corrective actions have been implemented, the test is resumed. The time-to-failure for the failed system, along with the current operating times of all other systems, are recorded. The data can be cumulative or non-cumulative. Consider the following table where the Failed Unit ID column indicates which unit failed. For example, if you enter 2 into the Failed Unit ID column, this indicates that the unit in the Time Unit 2 column is the one that failed. For the units that did not fail, you must enter the operating time at the time of the other unit's failure.
<br>
<math></math>
[[Image:rga3.6.png|thumb|center|400px|Multiple Systems(Known Operating Times) data.]]
<br>
<br>
In this table, two units are undergoing testing and the units do not accumulate age at the same rate. At 10 hours into the test, unit 1 fails and corrective action is taken on both units 1 and 2. By this time, both units have accumulated 10 hours of operation. At 17 hours, unit 2 fails and corrective action is again implemented on both units; however, unit 1 has accumulated 5 hours and unit 2 has accumulated 7 hours since the last event, and so forth.
 
====Multiple Systems (Concurrent Operating Times)====
This data type is used for tests where a number of systems are tested and the start, end of failure times are recorded. This data type assumes uniform time accumulation and that the systems are tested simultaneously. As an example, consider the data of two systems shown in Figure fignormview. System 1 begins testing at time equals 0 (with a start event, S) and failures are encountered and corrected at 281, 312 and 776 (with failure events, F). Testing stops at 1000 hours (with an end event, E). System 2 begins testing at time equals 0 and failures are encountered and corrected at 40, 222 and 436. Testing stops at 500 hours. RGA has two options to view this type of data. Figure fignormview shows the normal view, while Figure figadvview shows the advanced view. Both figures represent the same data.
<br>
<br>
<math></math>
[[Image:rga3.7.png|thumb|center|400px|Normal view for Multiple Systems (Concurrent Operating Times) data]]
 
<math></math>
 
When entering data within the normal view, each system must be initiated with a start event. Figure fignormview shows an example of that format.
<br>
<br>
<br>
[[Image:rga3.8.png|thumb|center|400px|Advanced view for Multiple Systems (Concurrent Operating Times) data, data for one of two systems displayed]]
 
====Multiple Systems (Concurrent Operating Times) - Using Dates====
This is similar to the previous data type except that dates are utilized along with operating hours. This assumes noncontinuous usage and the software computes equivalent (average) usage rates. Figure fignormviewdates shows an example of this in RGA.
 
 
 
[[Image:rga3.9.png|thumb|center|400px|Normal view for Concurrent Operating Times for Multiple Systems data with dates]]
 
====Multiple Systems with Event Codes====
The Multiple Systems with Event Codes data type is used to analyze the failure data from a reliability growth test in which a number of systems are tested concurrently and the implemented fixes are tracked during the test phase. With this data type, all of the systems under test are assumed to have the same system hours at any given time. Figure Figdvancedultipleventodes shows an example of this type of data.
 
<br>
[[Image:rga3.10.png|thumb|center|400px|Advanced view for Multiple Systems with Event Codes]]
 
====Models for Time-to-Failure (Continuous) Data====
The following models can be used to analyze time-to-failure (continuous) data sets. Models and examples using the different data types are discussed in later chapters.
<br>
:1) Duane (Chapter 4)
<br>
:2) Crow-AMSAA (NHPP) (Chapter 5)
<br>
:3) Crow Extended (Chapter 9)
<br>
:4) Crow Extended - Continuous Evaluation (Chapter 10)
<br>

Latest revision as of 01:05, 24 August 2012

Redirect to: