14.03.2014 Views

Quality and Reliability Methods - SAS

Quality and Reliability Methods - SAS

Quality and Reliability Methods - SAS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 18 <strong>Reliability</strong> Growth 325<br />

Example Using the <strong>Reliability</strong> Growth Platform<br />

Model-fitting in the <strong>Reliability</strong> Growth platform relies on the likelihood function. The likelihood function<br />

takes into account whether interval-censoring is present or not. So, mixing interval-censored with exact<br />

failure times is permitted.<br />

Failure <strong>and</strong> Time Termination<br />

Test Phases<br />

A test plan can call for test termination once a specific number of failures has been achieved or once a<br />

certain span of time has elapsed. For example, a test plan might terminate testing after 50 failures occur.<br />

Another plan might terminate testing after a six-month period.<br />

If testing terminates based on a specified number of failures, we say that the test is failure terminated. If<br />

testing is terminated based on a specified time interval, we say that the test is time terminated. The<br />

likelihood functions used in the <strong>Reliability</strong> Growth platform reflect whether the test phases are failure or<br />

time terminated.<br />

<strong>Reliability</strong> growth testing often involves several phases of testing. For example, the system being developed or<br />

the testing program might experience substantial changes at specific time points. The data table conveys the<br />

start time for each phase <strong>and</strong> whether each phase is failure or time terminated, as described below.<br />

Single Test Phase<br />

When there is a single test phase, the platform infers whether the test is failure or time terminated from the<br />

time <strong>and</strong> event count entries in the last row of the data table.<br />

• If the last row contains an exact failure time with a nonzero event count, the test is considered failure<br />

terminated.<br />

• If the last row contains an exact failure time with a zero event count, the test is considered time<br />

terminated.<br />

• If the last row contains an interval with nonzero width, the test is considered time terminated with<br />

termination time equal to the right endpoint of that interval.<br />

Note: To indicate that a test has been time terminated, be sure to include a last row in your data table<br />

showing the test termination time. If you are entering a single column as Time to Event or Timestamp, the<br />

last row should show a zero event count. If you are entering two columns as Time to Event or Timestamp,<br />

the right endpoint of the last interval should be the test-termination time. In this case, if there were no<br />

failures during the last interval, you should enter a zero event count.<br />

Multiple Test Phases<br />

When using Time to Event Format, the start time for any phase other than the first should be included in<br />

the time column(s). When using Dates Format, the start times for all phases should be included in the time<br />

column(s). If no events occurred at a phase start time, the corresponding entry in the Event Count column<br />

should be zero. For times given in two columns, it might be necessary to reflect the phase start time using an<br />

interval with identical endpoints <strong>and</strong> an event count of zero.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!