- The degree to which a system, subsystem or equipment is in a specified operable and committable state at the start of a mission, when the mission is called for at an unknown, i.e. a random, time. Simply put, availability is the proportion of time a system is in a functioning condition. This is often described as a mission capable rate. Mathematically, this is expressed as 100% minus unavailability.
- The ratio of (a) the total time a functional unit is capable of being used during a given interval to (b) the length of the interval.
For example, a unit that is capable of being used 100 hours per week (168 hours) would have an availability of 100/168. However, typical availability values are specified in decimal (such as 0.9998). In high availability applications, a metric known as nines, corresponding to the number of nines following the decimal point, is used. With this convention, "five nines" equals 0.99999 (or 99.999%) availability.
Introduction[edit | edit source]
Availability of a system is typically measured as a factor of its reliability – as reliability increases, so does availability.
Availability of a system may also be increased by the strategy of focusing on increasing testability, diagnostics and maintainability and not on reliability. Improving maintainability during the early design phase is generally easier than reliability (and Testability & diagnostics). Maintainability estimates (item Repair [by replacement] rates) are also generally more accurate. However, because the uncertainties in the reliability estimates (and also in diagnostic times) are in most cases very large, it is likely to dominate the availability (and the prediction uncertainty) problem, even while maintainability levels are very high. Furthermore, when reliability is not under control, then many and different sorts of issues may arise, for example:
- The need for complex testability (built in test sensors, hardware and software) requirements,
- The need for detailed diagnostic procedures,
- Manpower (maintainers / customer service capability) availability,
- Spare part availability,
- Dead on arrival issues (non-quality impact on system availability),
- Logistic delays of spares or manpower due to any reason,
- Lack of repair facilities and tools – also lack software development (e.g. software caused many delays in the DoD F22 Raptor program),
- Lack of repair knowledge and expert-personnel
- Extensive retro-fit and complex configuration management costs and others.
The problem of unreliability may also become out of control due to the "domino effect" of maintenance induced failures after repairs and more and more increasing efforts of problem solving, re-engineering en service efforts. Only focusing on maintainability is therefore not enough!
- If failures are prevented, none of the others are of any importance and therefore reliability is generally regarded as the most important part of availability!
Reliability needs to be evaluated and improved related to both availability and the cost of ownership (due to cost of spare parts, maintenance man-hours, transport costs, storage cost, part obsolete risks etc.). Often a trade-off is needed between the two. There might be a maximum ratio between availability and cost of ownership. Testability of a system should also be addressed in the availability plan as this is the link between reliability and maintainability. The maintenance strategy can influence the reliability of a system (e.g. by preventive and/or predictive maintenance), although it can never bring it above the inherent reliability. So, Maintainability and Maintenance strategies influences the availability of a system. In theory this can be almost unlimited if one would be able to always repair any fault in an infinitely short time. This is in practice impossible. Repair-ability is always limited due to testability, manpower and logistic considerations. Reliability is not limited (Reliable items can be made that outlast the life of a machine with almost 100% certainty). For high levels of system availability (e.g. the availability of engine trust in an aircraft), the use of redundancy may be the only option. Refer to reliability engineering.
An availability plan should clearly provide a strategy for availability control. Whether only Availability or also Cost of Ownership is more important depends on the use of the system. For example, a system that is a critical link in a production system – e.g. a big oil platform – is normally allowed to have a very high cost of ownership if this translates to even a minor increase in availability, as the unavailability of the platform results in a massive loss of revenue which can easily exceed the high cost of ownership. A proper reliability plan should always address RAMT analysis in its total context. RAMT stands in this case for Reliability, Availability, Maintainability/Maintenance and Testability in context to the customer needs.
Representation[edit | edit source]
The most simple representation for availability is as a ratio of the expected value of the uptime of a system to the aggregate of the expected values of up and down time, or
If we define the status function as
therefore, the availability A(t) at time t > 0 is represented by
Average availability must be defined on an interval of the real line. If we consider an arbitrary constant , then average availability is represented as
Limiting (or steady-state) availability is represented by
Limiting average availability is also defined on an interval as,
Availability is the probability that an item will be in an operable and commitable state at the start of a mission when the mission is called for at a random time, and is generally defined as uptime divided by total time (uptime plus downtime).
Methods and techniques to model availability[edit | edit source]
Fault tree analysis and related software are developed to calculate (analytic or by simulation) availability of a system or a functional failure condition within a system including many factors like:
- Reliability models
- Maintainability models
- Maintenance concepts
- Common cause failure
- Level of repair
- Repair status (as good as new, as good as old)
- Test coverage
- Active operational times / missions / sub system states
- Logistical aspects like; spare part (stocking) levels at different depots, transport times, repair times at different repair lines, manpower availability and more.
- Uncertainty in parameters
Furthermore, these methods are capable to identify the most critical items and failure modes or events that impact availability.
Definitions within systems engineering[edit | edit source]
Availability, inherent (Ai)  The probability that an item will operate satisfactorily at a given point in time when used under stated conditions in an ideal support environment. It excludes logistics time, waiting or administrative downtime, and preventive maintenance downtime. It includes corrective maintenance downtime. Inherent availability is generally derived from analysis of an engineering design and is calculated as the mean time to failure (MTTF) divided by the mean time to failure plus the mean time to repair (MTTR). It is based on quantities under control of the designer.
Availability, achieved (Aa)  The probability that an item will operate satisfactorily at a given point in time when used under stated conditions in an ideal support environment (i.e., that personnel, tools, spares, etc. are instantaneously available). It excludes logistics time and waiting or administrative downtime. It includes active preventive and corrective maintenance downtime.
Availability, operational (Ao)  The probability that an item will operate satisfactorily at a given point in time when used in an actual or realistic operating and support environment. It includes logistics time, ready time, and waiting or administrative downtime, and both preventive and corrective maintenance downtime. This value is equal to the mean time between failure (MTBF) divided by the mean time between failure plus the mean downtime (MDT). This measure extends the definition of availability to elements controlled by the logisticians and mission planners such as quantity and proximity of spares, tools and manpower to the hardware item.
Refer to Systems engineering for more details
Basic example[edit | edit source]
- MTTF in hours = 81.5 × 365 × 24 = 713940 (This is a reliability parameter and often has a high level of uncertainty!)
- Inherent availability (Ai) = 713940 / (713940+1) = 713940 / 713941 = 99.999860%
- Inherent unavailability = 1 / 713940 = 0.000140%
Outage due to equipment in hours per year = 1/rate = 1/MTTF = 0.01235 hours per year.
Literature[edit | edit source]
Availability is well established in the literature of stochastic modeling and optimal maintenance. Barlow and Proschan  define availability of a repairable system as "the probability that the system is operating at a specified time t." Blanchard  gives a qualitative definition of availability as "a measure of the degree of a system which is in the operable and committable state at the start of mission when the mission is called for at an unknown random point in time." This definition comes from the MIL-STD-721. Lie, Hwang, and Tillman  developed a complete survey along with a systematic classification of availability.
Availability measures are classified by either the time interval of interest or the mechanisms for the system downtime. If the time interval of interest is the primary concern, we consider instantaneous, limiting, average, and limiting average availability. The aforementioned definitions are developed in Barlow and Proschan , Lie, Hwang, and Tillman , and Nachlas . The second primary classification for availability is contingent on the various mechanisms for downtime such as the inherent availability, achieved availability, and operational availability. (Blanchard , Lie, Hwang, and Tillman ). Mi  gives some comparison results of availability considering inherent availability.
Availability considered in maintenance modeling can be found in Barlow and Proschan  for replacement models, Fawzi and Hawkes  for an R-out-of-N system with spares and repairs, Fawzi and Hawkes  for a series system with replacement and repair, Iyer  for imperfect repair models, Murdock  for age replacement preventive maintenance models, Nachlas [1998, 1989] for preventive maintenance models, and Wang and Pham  for imperfect maintenance models. A very comprehensive recent book is by Trivedi and Bobbio .
Applications[edit | edit source]
See also[edit | edit source]
- Reliability engineering
- Safety engineering
- List of system quality attributes
- Spurious trip level
- Condition-based maintenance
- Fault reporting
- High availability
References[edit | edit source]
- Elsayed, E., Reliability Engineering, Addison Wesley, Reading, MA,1996
- "Inherent Availability (AI)". Glossary of Defense Acquisition Acronyms and Terms. Department of Defense. Archived from the original on 13 April 2014. Retrieved 10 April 2014.
- "Achieved Availability (AI)". Glossary of Defense Acquisition Acronyms and Terms. Department of Defense. Archived from the original on 13 April 2014. Retrieved 10 April 2014.
- "Operational Availability (AI)". Glossary of Defense Acquisition Acronyms and Terms. Department of Defense. Archived from the original on 12 March 2013. Retrieved 10 April 2014.
- "Mandatory Reporting of Conventional Generation Performance Data" (PDF). Generating Availability Data System. North American Electric Reliability Corporation. July 2011. pp. 7, 17. Retrieved 13 March 2014.
This article incorporates public domain material from the General Services Administration document "Federal Standard 1037C" (in support of MIL-STD-188). K. Trivedi and A. Bobbio, Reliability and Availability Engineering: Modeling, Analysis and Applications, Cambridge University Press, 2017.
[edit | edit source]
- Reliability and Availability Basics
- System Reliability and Availability
- Availability and the Different Ways to Calculate It
|This article uses material from Availability on Wikipedia, which is released under the Creative Commons Attribution-ShareAlike 3.0 Unported License (view authors).|