System Reliability, Availability, and Maintainability

From SEBoK
Jump to navigation Jump to search

Reliability, availability, and maintainability (RAM) are three system attributes of tremendous interest to systems engineers, logisticians, and users alike. Collectively, they affect economic life-cycle costs of a system and its utility.

This article focuses primarily on the reliability of physical system elements. Software reliability is a separate discipline. Readers interested in software reliability are referred to The IEEE Recommended Practice on Software Reliability.

Probability Models for Populations

Reliability reliability is defined as the probability of a system or system element performing its intended function under stated conditions without failure for a given period of time (ASQ 2011). A precise definition must include a detailed description of the function and what constitutes a failure, the environment, and a definition of the time scale. Each can be surprisingly difficult to precisely define. Different failure mechanisms are referred to as failure modes, and can be modeled separately or aggregated into a single failure model.

Let T be a random time to failure. Reliability can be thought of as the complement of the cumulative distribution function (CDF) for T for a given set e of environmental conditions:

SEBoKv05 KA-SpecialtyEng RAM Eqation1.png

Maintainability maintainability is defined as the probability that a system or system element can be repaired in a defined environment within a specified period of time. Increased maintainability implies shorter repair times.

Availability availability is the probability that a repairable system or system element is operational at a given point in time, under a given set of environmental conditions. Availability depends on reliability and maintainability, and is discussed in detail later in this topic.

Each of these probability models is usually specified by a continuous, non-negative distribution. Typical distributions used in practice include exponential (possibly with a threshold parameter), Weibull (possibly with a threshold parameter), log-normal, and generalized gamma.

Maintainability models present some interesting challenges. The time to repair an item is the sum of the time required for evacuation, diagnosis, assembly of resources (parts, bays, tool, and mechanics), repair, inspection, and return. Administrative delay (such as holidays) can also affect repair times. Often these sub-processes have a minimum time to complete that is not zero, resulting in the distribution used to model maintainability having a threshold parameter. A threshold parameter is defined as the minimum time to repair that has positive probability. Estimation of the maintainability can be further complicated by queuing effects, resulting in times to repair that are not independent. This dependency frequently makes analytical solution of problems involving maintainability intractable and promotes the use of simulation to support analysis.

Data Issues

True RAM models for a system are generally never known. Data on a given system is assumed or collected, used to select a distribution for a model, and then to fit the parameters of the distribution. This process differs significantly from the one usually taught in an introductory statistics course. First, the normal distribution is seldom used as a life distribution, since it is defined for all negative times. Second, and more importantly, reliability data is different from classic experimental data. Reliability data is often censored, biased, observational, and missing information about covariates such as environmental conditions. Data from testing is often expensive, resulting in small sample sizes. These problems with reliability data require sophisticated strategies and processes to mitigate them. One consequence of these issues is that estimates based on limited data can be very imprecise.

Design Issues

System requirements should include specifications for reliability, maintainability, and availability, and each should be conditioned on the projected operating environments.

A proposed design should be analyzed prior to development to estimate if it meets those specifications. This is usually done by assuming historical data on actual or similar components represents the future performance of the components for the proposed system. If no data is available, conservative engineering judgment is often applied. The system dependency on the reliability of its components can be captured in several ways, including reliability block diagrams, fault trees, and failure mode effects and criticality analyses.

If a proposed design does not meet the preliminary RAM specifications, it can be adjusted. Critical failures are mitigated so that the overall risk is reduced to acceptable levels. This can be done in several ways.

Fault tolerance is a strategy that seeks to make the system robust against the failure of a component. This can be done by introducing redundancy. Redundant units can operate in a ‘stand-by’ mode. A second tolerance strategy is to have the redundant components share the load, so that one or more of them may fail yet the system continues to operate. There are modeling issues associated with redundancy, including switching between components, warm-up, and increased failure rates for surviving units under increased load when another load-sharing unit fails.

Redundancy can be an expensive strategy as there are cost, weight, volume, and power penalties associated with stand-by components.

Fault avoidance seeks to improve individual components so that they are more reliable. This too can be an expensive strategy, but it avoids the power, weight, and volume penalties associated with using redundant components, as well as the switching issues.

A third strategy is to repair or replace a component following a preventive maintenance schedule. This usually requires the assumption that the repair returns the component to “good as new” status, or possibly to an earlier age-equivalent. These assumptions can cause difficulties --- for example, an oil change on a vehicle does not return the engine to ‘good as new’ status. Scheduled replacement can return a unit to good as new, but at the cost of wasting potential life for the replaced unit. As a result, the selection of a replacement period is a non-linear optimization problem that minimizes total expected life-cycle costs. These costs are the sum of the expected costs of planned and unplanned maintenance actions.

A fourth strategy is to control the environment so that a system is not operated under conditions that accelerate the aging of its components.

Any or all of the above strategies (fault tolerance, fault avoidance, preventive maintenance, and environmental control) may be applied to improve the designed reliability of a system.

Post-Production Management Systems

Once a system is fielded, its reliability and availability should be tracked. Doing so allows the producer / owner to verify that the design has met its RAM objectives, to identify unexpected failure modes, to record fixes, to assess the utilization of maintenance resources, and to assess the operating environment.

One such tracking system is generically known as a FRACAS system (Failure Reporting and Corrective Action System). Such a system captures data on failures and improvements to correct failures. This database is separate from a warranty data base, which is typically run by the financial function of an organization and tracks costs only.

A FRACAS for an organization is a system, and itself should be designed following systems engineering principles. In particular, a FRACAS system supports later analyses, and those analyses impose data requirements. Unfortunately, the lack of careful consideration of the backward flow from decision to analysis to model to required data too often leads to inadequate data collection systems and missing essential information. Proper prior planning prevents this poor performance.

Of particular importance is a plan to track data on units that have not failed. Units whose precise times of failure are unknown are referred to as censored units. Inexperienced analysts frequently do not know how to analyze censored data, and omit the censored units as a result. This can badly bias an analysis.

An organization should have an integrated data system that allows reliability data to be considered with logistical data, such as parts, personnel, tools, bays, transportation and evacuation, queues, and costs, allowing a total awareness of the interplay of logistical and RAM issues. These issues in turn must be integrated with management and operational systems, for an organization to reap the benefits that can occur from complete situational awareness with respect to RAM.


There are a wide range of models that estimate and predict reliability. Simple models, such as the exponential distribution, can be useful for ‘back of the envelope’ calculations. There are more sophisticated probability models used for life data analysis. These are best characterized by their failure rate behavior, which is defined as the probability that a unit fails in the next small interval of time, given it has lived until the beginning of the interval, and divided by the length of the interval.

Models can be considered for a fixed environmental condition, or they can be extended to include the effect of environmental conditions on system life. Such extended models can in turn be used for accelerated life testing (ALT), where a system is deliberately and carefully overstressed to induce failures more quickly, and the data extrapolated to usual use conditions. This is often the only way to obtain estimates of the life of highly reliable products in a reasonable amount of time.

Also useful are degradation models, where some characteristic of the system is associated with the propensity of the unit to fail. As that characteristic degrades, we can estimate times of failure before they occur. The initial developmental units of a system often do not meet their RAM specifications. Reliability growth models allow estimation of resources (particularly testing time) necessary before a system will mature to meet those goals.

Maintainability models describe the time necessary to return a failed repairable system to service. They are usually the sum of a set of models describing different aspects of the maintenance process --- for example, diagnosis, repair, inspection, reporting, and evacuation. These models often have threshold parameters, which are minimum times until an event can occur.

Logistical support models attempt to describe flows through a logistics system, and quantify the interaction between maintenance activities and the resources available to support those activities. Queue delays, in particular, are a major source of down-time for a repairable system and a logistical support model allows one to explore the trade space between resources and availability.

All these models are abstractions of reality, and so at best approximations to reality. To the extent they provide useful insights, they are still very valuable. The more complicated the model, the more data necessary to estimate it precisely. The greater the extrapolation required for a prediction, the greater the imprecision. Extrapolation is often unavoidable, because high reliability equipment typically can have long life, and the amount of time required to observe failures may exceed test times. This requires strong assumptions be made about future life (such as the absence of masked failure modes) and these assumptions increase uncertainty about predictions. The uncertainty introduced by strong model assumptions is often not quantified, and presents a risk to the system engineer.

System Metrics

Probabilistic metrics describe system performance for RAM. Quantiles, means, and modes of the distributions used to model RAM are also useful.

Availability has some additional definitions, characterizing what downtime is counted against a system. For inherent availability, only downtime associated with corrective maintenance counts against the system. For achieved availability, downtime associated with both corrective and preventive maintenance counts against a system. Finally, operational availability counts all sources of downtime, including logistical and administrative, against a system.

Availability can also be calculated instantaneously, averaged over an interval, or reported as an asymptotic value. Asymptotic availability can be calculated easily, but care must be taken to analyze whether or not a systems settles down or settles up to the asymptotic value, and how long it takes until the system approaches that asymptotic value.

Reliability importance measures the effect on the system reliability of a small improvement in a component’s reliability. It is defined as the partial derivative of the system reliability with respect to the reliability of a component.

Criticality is the product of a component’s reliability, the consequences of a component failure, and the frequency with which a component failure results in a system failure. Criticality is a guide to prioritizing reliability improvement efforts.

Many of these metrics cannot be calculated directly because the integrals involved are intractable. They are usually estimated using simulation.

System Models

There are many ways to characterize the reliability of a system, including fault trees, reliability block diagrams, and failure mode effects analysis.

A Fault Tree (Kececioglu 1991) is a graphical representation of the failure modes of a system. It is constructed using logical gates, with AND, OR, NOT, and K of N gates predominating. Fault trees can be complete or partial; a partial fault tree focuses on a failure mode or modes of interest. They allow 'drill down' to see the dependencies of systems on nested systems and system elements. Fault trees date back to the 1960s and were pioneered by Bell Labs.

Figure 1. Fault Tree (Figure Developed for BKCASE)

A Reliability Block Diagram (RBD) is a graphical representation of the reliability dependence of a system on its components. It is a directed, acyclic graph. Each path through the graph represents a subset of system components, and if the components in that path are operational, the system is operational. Component lives are usually assumed to be independent in a RBD. Simple topologies include a series system, a parallel system, a k of n system, and combinations of these.

RBDs are often nested, with one RBD serving as a component in a higher level model. These hierarchical models allow the analyst to have the appropriate resolution of detail while still permitting abstraction.

RBDs depict paths that lead to success, while fault trees depict paths that lead to failure.

Figure 2. Simple Reliability Block Diagram (Figure Developed for BKCASE)

A Failure Mode Effects Analysis is a table that lists the possible failure modes for a system, their likelihood, and the effects of the failure. A Failure Modes Effects Criticality Analysis scores the effects by the magnitude of the product of the consequence and likelihood, allowing ranking of the severity of failure modes. (Kececioglu 1991)

System models require even more data to fit them well. “Garbage in, garbage out” (GIGO) applies with particular strength to system models.

Software Tools

The specialized analyses required for RAM drive the need for specialized software. While general purpose statistical languages or spreadsheets can, with sufficient effort, be used for reliability analysis, almost every serious practitioner uses specialized software.

Minitab (versions 13 and later) includes functions for life data analysis. Win Smith is a specialized package that fits reliability models to life data, and can be extended for reliability growth analysis and other analyses. Relex has an extensive historical database of component reliability data, and is useful for estimating system reliability in the design phase.

There is a suite of products from ReliaSoft (2007). Weibull++ fits life models to life data. ALTA fits accelerated life models to accelerated life test data. BlockSim models system reliability, given component data.


Works Cited

American Society for Quality (ASQ). 2011. Glossary: Reliability. Accessed on September 11, 2011. Available at

Kececioglu, D. 1991. Reliability Engineering Handbook, Volume 2. Upper Saddle River, NJ, USA: Prentice Hall.

ReliaSoft. 2007. Failure Modes and Effects Analysis (FMEA) and Failure Modes, Effects and Criticality Analysis (FMECA). Accessed on September 11, 2011. Available at

Primary References

Blischke, W.R. and D.N. Prabhakar Murthy. 2000. Reliability Modeling, Prediction, and Optimization. New York, NY, USA: Wiley and Sons.

DoD. 2005. DOD Guide for Achieving Reliability, Availability, and Maintainability. Arlington, VA, USA: U.S. Department of Defense (DoD). Accessed on September 11, 2011. Available at:

Kececioglu, D. 1991. Reliability Engineering Handbook, Volume 2. Upper Saddle River, NJ, USA: Prentice Hall.

Lawless, J.F. 1982. Statistical Models and Methods for Lifetime Data. New York, NY, USA: Wiley and Sons.

Martz, H.F. and R.A. Waller. 1991. Bayesian Reliability Analysis. Malabar, FL, USA: Kreiger.

Meeker, W.O. and L.A. Escobar. 1998. Statistical Methods for Reliability Data. New York, NY, USA: Wiley and Sons.

Additional References

Olwell, D.H. 2011. "Reliability Leadership." Proceedings of the 2001 Reliability and Maintainability M Symposium. Philadelphia, PA, USA: IEEE. Accessed 7 March 2012 at [IEEE web site.]

ReliaSoft. 2007. "Availability." Accessed on September 11, 2011. Available at:

SAE. 2000a. Aerospace Recommended Practice ARP5580: Recommended Failure Modes and Effects Analysis (FMEA) Practices for Non-Automobile Applications. Warrendale, PA, USA: Society of Automotive Engineers (SAE) International.

SAE. 2000b. Surface Vehicle Recommended Practice J1739: (R) Potential Failure Mode and Effects Analysis in Design (Design FMEA), Potential Failure Mode and Effects Analysis in Manufacturing and Assembly Processes (Process FMEA), and Potential Failure Mode and Effects Analysis for Machinery (Machinery FMEA). Warrendale, PA, USA: Society of Automotive Engineers (SAE) International.

< Previous Article | Parent Article | Next Article >

Comments from SEBok 0.5 Wiki

No comments were logged for this article in the SEBoK 0.5 wiki. Because of this, it is especially important for reviewers to provide feedback on this article. Please see the discussion prompts below.

SEBoK v. 1.9.1 released 30 September 2018

SEBoK Discussion

Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.

If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.

blog comments powered by Disqus