MTBF / MTTR / Availability

Use operating hours excluding repair downtime.

This selection changes review context only. Formulas and example inputs stay unchanged. Check the model assumptions and applicability for the actual process.

Identify the actual asset, process, work boundary, source documents, units and assumptions. Confirm that the selected model or template applies before using its results.

1 Inputs

Minimum: 0.01

Minimum: 0

Minimum: 0

2 Results

Inherent availability
98.81%
MTBF
250 h
MTTR
3 h
Failure rate λ
4 /1000h
Availability
98.81%
MTBF = T / n; MTTR = R / n; A = T / (T + R)
Use operating hours excluding repair downtime. Zero observed failures does not prove infinite reliability; MTBF and MTTR are then not estimable. Track the observation duration and failure definition when comparing assets.

Worked example

Example values are illustrative. Replace them with your measured data.

InputValue
Total operating time2000 hours
Number of failures8 count
Total repair (downtime) time24 hours

Inherent availability: 98.81%

Related tools

About this calculator

How it works

From your failure history the tool computes MTBF = operating time ÷ number of failures, MTTR = total repair time ÷ number of failures, failure rate λ = 1 ÷ MTBF (shown per 1,000 hours), and inherent availability = MTBF ÷ (MTBF + MTTR).

Worked example (illustrative inputs)

2,000 operating hours, 8 failures, 24 hours of repair. MTBF = 2,000 ÷ 8 = 250 h. MTTR = 24 ÷ 8 = 3 h. λ = 4 failures per 1,000 h. Availability = 250 ÷ 253 = 98.81%.

How to read the result

Availability is shown as good at 95% or more and as a warning from 90% to 95%. An MTTR of 4 hours or less is shown as good. MTBF reflects reliability (how often the asset fails) and MTTR reflects maintainability (how fast it is restored). They are separate levers: root-cause work and design changes raise MTBF, while spares, access, procedures and training cut MTTR.

When to use it

Use it on one asset or asset class over a defined period, with operating hours and repair hours taken from the same records, to see whether failure frequency or repair duration is limiting uptime.

À propos de ce calculateur

Traduction (brouillon) — à relire.

Fonctionnement

À partir de l'historique des pannes, l'outil calcule MTBF = temps de fonctionnement ÷ nombre de pannes, MTTR = temps total de réparation ÷ nombre de pannes, taux de défaillance λ = 1 ÷ MTBF (affiché pour 1 000 heures) et disponibilité intrinsèque = MTBF ÷ (MTBF + MTTR).

Exemple chiffré (valeurs d'illustration)

2 000 heures de fonctionnement, 8 pannes, 24 heures de réparation. MTBF = 2 000 ÷ 8 = 250 h. MTTR = 24 ÷ 8 = 3 h. λ = 4 pannes pour 1 000 h. Disponibilité = 250 ÷ 253 = 98,81 %.

Lire le résultat

La disponibilité est jugée bonne à 95 % ou plus, et en alerte entre 90 et 95 %. Un MTTR de 4 heures ou moins est jugé bon. Le MTBF traduit la fiabilité (fréquence des pannes) et le MTTR la maintenabilité (rapidité de remise en service). Ce sont deux leviers distincts : l'analyse des causes et les modifications de conception augmentent le MTBF, tandis que les pièces, l'accès, les procédures et la formation réduisent le MTTR.

Quand l'utiliser

À utiliser sur un équipement ou une famille d'équipements sur une période définie, avec des heures issues des mêmes enregistrements, pour voir si c'est la fréquence ou la durée des pannes qui limite la disponibilité.

حول هذه الحاسبة

ترجمة (مسودة) — للمراجعة.

طريقة الحساب

تحسب الأداة من سجل الأعطال: MTBF = زمن التشغيل ÷ عدد الأعطال، وMTTR = إجمالي زمن الإصلاح ÷ عدد الأعطال، ومعدل الأعطال λ = 1 ÷ MTBF (لكل 1000 ساعة)، والإتاحة الذاتية = MTBF ÷ (MTBF + MTTR).

مثال محسوب (قيم توضيحية)

2000 ساعة تشغيل، 8 أعطال، 24 ساعة إصلاح. MTBF = 2000 ÷ 8 = 250 ساعة. MTTR = 24 ÷ 8 = 3 ساعات. λ = 4 أعطال لكل 1000 ساعة. الإتاحة = 250 ÷ 253 = 98.81%.

قراءة النتيجة

تعدّ الإتاحة جيدة عند 95% فأكثر، وتظهر كتحذير بين 90% و95%. ويعدّ MTTR جيداً عند 4 ساعات أو أقل. يعبّر MTBF عن الموثوقية (عدد مرات العطل) ويعبّر MTTR عن قابلية الصيانة (سرعة الإعادة للخدمة). هما رافعتان مختلفتان: تحليل الأسباب الجذرية وتعديل التصميم يرفعان MTBF، بينما قطع الغيار وسهولة الوصول والإجراءات والتدريب تخفض MTTR.

متى تستخدمه

استخدمها لأصل واحد أو فئة أصول خلال فترة محددة، مع ساعات مأخوذة من السجلات نفسها، لمعرفة ما إذا كان تكرار الأعطال أم مدة الإصلاح هو ما يحد من الإتاحة.

In one line

Use operating hours excluding repair downtime. Zero observed failures does not prove infinite reliability; MTBF and MTTR are then not estimable. Track the observation duration and failure definition when comparing assets.

Worked example

EXAMPLE

Illustrative values (the calculator defaults), not data from a real site.

Inputs
Total operating time2000 hours
Number of failures8 count
Total repair (downtime) time24 hours
Results
Inherent availability98.81%
MTBF250 h
MTTR3 h
Failure rate λ4 /1000h
Availability98.81%

Frequently asked questions

What is the difference between MTBF and MTTR?

MTBF (Mean Time Between Failures) measures reliability — how long the asset runs between breakdowns. MTTR (Mean Time To Repair) measures maintainability — how quickly you restore it. Availability combines both.

Is this inherent or operational availability?

This calculates inherent availability, which considers only corrective repair time. Operational availability also includes logistics delays, administrative time and preventive maintenance, so it is always lower.

How many failures do I need for a reliable MTBF figure?

A handful of failures (2–3) gives only a rough estimate with wide statistical uncertainty; ten or more over a meaningful time window gives a much more trustworthy number. Treat single-digit failure counts as directional, not precise.

What if my asset has never failed?

With zero failures the calculator can't compute a meaningful MTBF, so it shows an infinite value — that isn't license to skip maintenance, it just means you don't yet have failure data. Keep tracking operating time so the first failure gives you a real baseline.

Does this account for different failure modes?

No — this is an aggregate calculation that treats every failure the same regardless of cause. For deeper analysis, such as separating infant-mortality failures from wear-out failures, pair this with a Weibull analysis, which models how failure likelihood changes over time instead of just averaging it.

What's a good MTTR to aim for?

There's no universal number — it depends on repair complexity, spares availability and crew skill. Track your own MTTR trend and compare similar asset classes within your own plant; a rising MTTR on a stable asset usually signals a spares, documentation or skills gap worth investigating.

Donate · Faire un don · تبرّع