When you have data from developmental testing in which the systems were operated continuously until failure, you can use the Crow-AMSAA (NHPP) or Duane models. The module provides a choice of data types for individual or grouped failure times, and for combining data from multiple identical systems. This can include situations, where all systems operate concurrently, you have recorded the exact operating times for both the failed and non-failed systems or you have recorded the calendar date for each failure so you can estimate the operating times of the non-failed systems based on the average daily usage rate for the relevant time period.
With the Crow-AMSAA (NHPP) model, there are additional analysis options for certain situations, such as Gap analysis (if you believe that some portion of the data is erroneous or missing) or change of slope (if a major change in the system design or operational environment has caused a significant change in the failure intensity observed during testing).
When you have data from one-shot (pass/fail) reliability growth tests (and depending on the data type), the module supports mixed data models that can be used with Crow Extended and Crow Extended-Continuous Evaluation models. For discrete data, there is a choice of data types that can handle tests in which a single trial is performed for each design configuration, multiple trials per configuration, or a combination of both. The module also supports Failure Discounting, if you have recorded the specific failure modes from sequential one-shot tests.
When you simply wish to analyze the calculated reliability values for different times/stages within developmental testing, you can use the Standard Gompertz, Modified Gompertz, Lloyd-Lipow or Logistic models.
Reliability Growth module supports several innovative approaches that expand upon traditional reliability growth methods in ways that better represent real-world testing practices and practical applications.
For traditional reliability growth analysis, you can calculate the MTBF, failure intensity or reliability for a given time/stage. You can determine the amount of testing that will be required to demonstrate a specified MTBF, failure intensity or reliability. Additionally, you can estimate the expected number of failures for a given time/stage. The module makes it easy to create a complete array of plots and charts to present your analysis graphically.
Although traditional reliability growth analysis requires the assumption that all design improvements are incorporated before the end of the test (test-fix-test), many real-world testing scenarios may also include some failure modes that are not fixed, and others where some or all of the fixes are delayed until a later time (test-fix-find-test or test-find-test). With the Crow Extended and Crow Extended – Continuous Evaluation models, you can use Failure Mode Classifications to provide the appropriate analysis treatment for any of these management strategies. For delayed fixes, both models use Effectiveness Factors to indicate how much the failure intensity of each mode will be reduced once the fix has been implemented.
The Reliability Growth module provides opportunities for fielded repairable system analysis. Repairable systems analysis to analyze data from repairable systems operating in the field under typical customer usage conditions. Such data might be obtained from a warranty system, repair depot, operational testing, etc. Specifically, you can use the Power Law or Crow-AMSAA (NHPP) models for repairable system analysis based on the assumption of minimal repair (i.e., the system is "as bad as old" after each repair) to calculate a variety of useful metrics, including:
You can also use the Crow Extended model for fielded repairable systems if you want to evaluate the improvement (i.e., the jump in MTBF) that could be achieved by rolling out a set of fixes for all systems operating in the field.
Reliability test design for repairable systems uses the NHPP model to determine the test time required per system (or the number of systems that must be tested) in order to demonstrate a specified reliability goal, defined in terms of MTBF or failure intensity at a given time.
Operational mission profiles to make sure that the testing is applied in a balanced manner that will yield data suitable for reliability growth analysis. Mission Profile folios can help you to create an operational test plan, track the expected vs. actual usage for all mission profiles and verify that the testing has been conducted. It helps you automatically group the data at specified "convergence points" so the growth model can be applied appropriately.
Create data sets that can be analyzed directly in one of the Reliability Growth’s standard folios. You can also use the SimuMatic® utility to automatically analyze and plot results from a large number of data sets that have been created via simulation. These integrated simulation tools can be used to perform a wide variety of reliability tasks, such as: