Predicted elapsed time between inherent failures of a system during operation
Mean time between failures (MTBF) is the predicted elapsed time between inherent failures of a mechanical or electronic system during normal system operation. MTBF can be calculated as the arithmetic mean (average) time between failures of a system. The term is used for repairable systems while mean time to failure (MTTF) denotes the expected time to failure for a non-repairable system.
The definition of MTBF depends on the definition of what is considered a failure. For complex, repairable systems, failures are considered to be those out of design conditions which place the system out of service and into a state for repair. Failures which occur that can be left or maintained in an unrepaired condition, and do not place the system out of service, are not considered failures under this definition. In addition, units that are taken down for routine scheduled maintenance or inventory control are not considered within the definition of failure. The higher the MTBF, the longer a system is likely to work before failing.
Overview.
Mean time between failures (MTBF) describes the expected time between two failures for a repairable system. For example, three identical systems starting to function properly at time 0 are working until all of them fail. The first system fails after 100 hours, the second after 120 hours and the third after 130 hours. The MTBF of the systems is the average of the three failure times, which is 116.667 hours. If the systems were non-repairable, then their MTTF would be 116.667 hours.
In general, MTBF is the "up-time" between two failure states of a repairable system during operation as outlined here:
For each observation, the "down time" is the instantaneous time it went down, which is after (i.e. greater than) the moment it went up, the "up time". The difference ("down time" minus "up time") is the amount of time it was operating between these two events.
By referring to the figure above, the MTBF of a component is the sum of the lengths of the operational periods divided by the number of observed failures:
formula_1
In a similar manner, mean down time (MDT) can be defined as
formula_2
Mathematical description.
The MTBF is the expected value of the random variable formula_3 indicating the time until failure. Thus, it can be written as
 formula_4
where formula_5 is the probability density function of formula_3. Equivalently, the MTBF can be expressed in terms of the reliability function formula_7 as
 formula_8.
The MTBF and formula_3 have units of time (e.g., hours).
Any practically-relevant calculation of the MTBF assumes that the system is working within its "useful life period", which is characterized by a relatively constant failure rate (the middle part of the "bathtub curve") when only random failures are occurring. In other words, it is assumed that the system has survived initial setup stresses and has not yet approached its expected end of life, both of which often increase the failure rate.
Assuming a constant failure rate formula_10 implies that formula_3 has an exponential distribution with parameter formula_10. Since the MTBF is the expected value of formula_3, it is given by the reciprocal of the failure rate of the system,
 formula_14.
Once the MTBF of a system is known, and assuming a constant failure rate, the probability that any one particular system will be operational for a given duration can be inferred from the reliability function of the exponential distribution, formula_15. In particular, the probability that a particular system will survive to its MTBF is formula_16, or about 37% (i.e., it will fail earlier with probability 63%).
Application.
The MTBF value can be used as a system reliability parameter or to compare different systems or designs. This value should only be understood conditionally as the “mean lifetime” (an average value), and not as a quantitative identity between working and failed units.
Since MTBF can be expressed as “average life (expectancy)”, many engineers assume that 50% of items will have failed by time "t" = MTBF. This inaccuracy can lead to bad design decisions. Furthermore, probabilistic failure prediction based on MTBF implies the total absence of systematic failures (i.e., a constant failure rate with only intrinsic, random failures), which is not easy to verify. Assuming no systematic errors, the probability the system survives during a duration, T, is calculated as exp^(-T/MTBF). Hence the probability a system fails during a duration T, is given by 1 - exp^(-T/MTBF).
MTBF value prediction is an important element in the development of products. Reliability engineers and design engineers often use reliability software to calculate a product's MTBF according to various methods and standards (MIL-HDBK-217F, Telcordia SR332, Siemens SN 29500, FIDES, UTE 80-810 (RDF2000), etc.). The Mil-HDBK-217 reliability calculator manual in combination with RelCalc software (or other comparable tool) enables MTBF reliability rates to be predicted based on design.
A concept which is closely related to MTBF, and is important in the computations involving MTBF, is the mean down time (MDT). MDT can be defined as mean time which the system is down after the failure. Usually, MDT is considered different from MTTR (Mean Time To Repair); in particular, MDT usually includes organizational and logistical factors (such as business days or waiting for components to arrive) while MTTR is usually understood as more narrow and more technical.
Application of MTBF in manufacturing.
MTBF serves as a crucial metric for managing machinery and equipment reliability. Its application is particularly significant in the context of total productive maintenance (TPM), a comprehensive maintenance strategy aimed at maximizing equipment effectiveness. MTBF provides a quantitative measure of the time elapsed between failures of a system during normal operation, offering insights into the reliability and performance of manufacturing equipment.
By integrating MTBF with TPM principles, manufacturers can achieve a more proactive maintenance approach. This synergy allows for the identification of patterns and potential failures before they occur, enabling preventive maintenance and reducing unplanned downtime. As a result, MTBF becomes a key performance indicator (KPI) within TPM, guiding decisions on maintenance schedules, spare parts inventory, and ultimately, optimizing the lifespan and efficiency of machinery. This strategic use of MTBF within TPM frameworks enhances overall production efficiency, reduces costs associated with breakdowns, and contributes to the continuous improvement of manufacturing processes.
MTBF and MDT for networks of components.
Two components formula_17 (for instance hard drives, servers, etc.) may be arranged in a network, in "series" or in "parallel". The terminology is here used by close analogy to electrical circuits, but has a slightly different meaning. We say that the two components are in series if the failure of "either" causes the failure of the network, and that they are in parallel if only the failure of "both" causes the network to fail. The MTBF of the resulting two-component network with repairable components can be computed according to the following formulae, assuming that the MTBF of both individual components is known:
formula_18
where formula_19 is the network in which the components are arranged in series.
For the network containing parallel repairable components, to find out the MTBF of the whole system, in addition to component MTBFs, it is also necessary to know their respective MDTs. Then, assuming that MDTs are negligible compared to MTBFs (which usually stands in practice), the MTBF for the parallel system consisting from two parallel repairable components can be written as follows:
formula_20
where formula_21 is the network in which the components are arranged in parallel, and formula_22 is the probability of failure of component formula_23 during "vulnerability window" formula_24.
Intuitively, both these formulae can be explained from the point of view of failure probabilities. First of all, let's note that the probability of a system failing within a certain timeframe is the inverse of its MTBF. Then, when considering series of components, failure of any component leads to the failure of the whole system, so (assuming that failure probabilities are small, which is usually the case) probability of the failure of the whole system within a given interval can be approximated as a sum of failure probabilities of the components. With parallel components the situation is a bit more complicated: the whole system will fail if and only if after one of the components fails, the other component fails while the first component is being repaired; this is where MDT comes into play: the faster the first component is repaired, the less is the "vulnerability window" for the other component to fail.
Using similar logic, MDT for a system out of two serial components can be calculated as:
formula_25
and for a system out of two parallel components MDT can be calculated as:
formula_26
Through successive application of these four formulae, the MTBF and MDT of any network of repairable components can be computed, provided that the MTBF and MDT is known for each component. In a special but all-important case of several serial components, MTBF calculation can be easily generalised into 
formula_27
which can be shown by induction, and likewise
formula_28
since the formula for the mdt of two components in parallel is identical to that of the mtbf for two components in series.
Variations of MTBF.
There are many variations of MTBF, such as "mean time between system aborts" (MTBSA), "mean time between critical failures" (MTBCF) or "mean time between unscheduled removal" (MTBUR). Such nomenclature is used when it is desirable to differentiate among types of failures, such as critical and non-critical failures. For example, in an automobile, the failure of the FM radio does not prevent the primary operation of the vehicle.
It is recommended to use "Mean time to failure" (MTTF) instead of MTBF in cases where a system is replaced after a failure ("non-repairable system"), since MTBF denotes time between failures in a system which can be repaired.
MTTFd is an extension of MTTF, and is only concerned about failures which would result in a dangerous condition. It can be calculated as follows:
formula_29
where "B"10 is the number of operations that a device will operate prior to 10% of a sample of those devices would fail and "n"op is number of operations. "B"10d is the same calculation, but where 10% of the sample would fail to danger. "n"op is the number of operations/cycle in one year.
MTBF considering censoring.
In fact the MTBF counting only failures with at least some systems still operating that have not yet failed underestimates the MTBF by failing to include in the computations the partial lifetimes of the systems that have not yet failed. With such lifetimes, all we know is that the time to failure exceeds the time they've been running. This is called censoring. In fact with a parametric model of the lifetime, the likelihood for the experience on any given day is as follows:
formula_30, 
where 
formula_31 is the failure time for failures and the censoring time for units that have not yet failed, 
formula_32 = 1 for failures and 0 for censoring times, 
formula_33 = the probability that the lifetime exceeds formula_31, called the survival function, and 
formula_35 is called the hazard function, the instantaneous force of mortality (where formula_36 = the probability density function of the distribution). 
For a constant exponential distribution, the hazard, formula_10, is constant. In this case, the MBTF is 
MTBF = formula_38, 
where formula_39 is the maximum likelihood estimate of formula_10, maximizing the likelihood given above and formula_41 is the number of uncensored observations. 
We see that the difference between the MTBF considering only failures and the MTBF including censored observations is that the censoring times add to the numerator but not the denominator in computing the MTBF.
See also.
 ;templatestyles src="Div col/styles.css"/ ;
References.
 ;templatestyles src="Reflist/styles.css" / ;