# MTBF and MTTR Worksheet

> Source: https://netray.co/tools/mtbf-mttr-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Track failures, operating hours and repair hours per asset and calculate MTBF, MTTR and availability for each row and for the fleet.

## Category

maintenance

## Audience

- Maintenance manager
- Reliability engineer
- Plant manager

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Asset

**Key:** asset

**Type:** text

#### Area

**Key:** area

**Type:** select

**Options:**

- Machining
- Assembly
- Packaging
- Utilities
- Material handling

#### Failures

**Key:** failures

**Type:** number

**Help:** Count of unplanned stops caused by failure in the period.

#### Operating hours

**Key:** op_hours

**Type:** number

**Help:** Hours the asset actually ran, not calendar hours.

#### Total repair hours

**Key:** repair_hours

**Type:** number

**Help:** Active repair time from failure to return to service.

#### MTBF (h)

**Key:** mtbf

**Type:** number

**Expr:** op_hours / failures

**Format:** hours

#### MTTR (h)

**Key:** mttr

**Type:** number

**Expr:** repair_hours / failures

**Format:** hours

#### Inherent availability

**Key:** avail

**Type:** number

**Expr:** if(gt(mtbf + mttr, 0), mtbf / (mtbf + mttr) * 100, 0)

**Format:** percent

**Rows:**

**Asset:** CNC mill 04

**Area:** Machining

**Failures:** 6

**Op hours:** 1380

**Repair hours:** 21

**Asset:** CNC lathe 11

**Area:** Machining

**Failures:** 3

**Op hours:** 1420

**Repair hours:** 18

**Asset:** Reflow oven 2

**Area:** Assembly

**Failures:** 2

**Op hours:** 1500

**Repair hours:** 7

**Asset:** Case packer 1

**Area:** Packaging

**Failures:** 14

**Op hours:** 1210

**Repair hours:** 29

**Asset:** Air compressor B

**Area:** Utilities

**Failures:** 1

**Op hours:** 1700

**Repair hours:** 12

**Asset:** Conveyor line 3

**Area:** Material handling

**Failures:** 9

**Op hours:** 1650

**Repair hours:** 16

**Totals:**

#### Total failures

**Key:** failures

**Agg:** sum

**Format:** number

#### Total operating hours

**Key:** op_hours

**Agg:** sum

**Format:** hours

#### Total repair hours

**Key:** repair_hours

**Agg:** sum

**Format:** hours

**Summary:**

#### Fleet MTBF

**Key:** fleet_mtbf

**Expr:** if(gt(sum_failures, 0), sum_op_hours / sum_failures, 0)

**Format:** hours

**Primary:** true

#### Fleet MTTR

**Key:** fleet_mttr

**Expr:** if(gt(sum_failures, 0), sum_repair_hours / sum_failures, 0)

**Format:** hours

**Primary:** true

#### Fleet inherent availability

**Key:** fleet_avail

**Expr:** if(gt(fleet_mtbf + fleet_mttr, 0), fleet_mtbf / (fleet_mtbf + fleet_mttr) * 100, 0)

**Format:** percent

#### Assets tracked

**Key:** worst_count

**Expr:** count

**Format:** integer

**Notes:** Rows with zero failures show MTBF as 0 because the value is undefined; treat them as no failures observed, not as poor reliability. Use a long enough period that every important asset has at least a few failures. Pull failure counts and repair hours from maintenance work orders for the same period.

## Content

**Intro:** MTBF tells you how long an asset runs between failures. MTTR tells you how long it takes to get it running again. This worksheet calculates both for every asset from three simple inputs and combines them into inherent availability, with a fleet total at the bottom.

**Sections:**

#### How to use the worksheet

**Body:** List each asset and enter three numbers for the same period: the count of failures, the hours the asset actually operated and the total active repair hours. MTBF is operating hours divided by failures. MTTR is repair hours divided by failures. Inherent availability is MTBF over MTBF plus MTTR. The totals row computes fleet figures from sums, which is the right way to aggregate because it weights assets by how often they fail. Averaging the individual MTBF values would give the same weight to an asset that failed once and one that failed fifteen times.

#### Definitions that matter

**Body:** Define a failure before you count one. Most sites use an unplanned stop that needs a corrective work order, and exclude planned maintenance, changeovers and operator adjustments. Operating hours should come from run time, not calendar time, so an asset that is idle for lack of orders does not look reliable. MTTR here is active repair time, which is different from downtime. Waiting for parts, waiting for a technician and administrative delay are separate lost time. Splitting them shows whether the answer is a better machine, a faster fix or a better spares policy.

**Bullets:**

- MTBF = operating hours / number of failures.
- MTTR = total repair hours / number of failures.
- Inherent availability = MTBF / (MTBF + MTTR).

#### Reading the example

**Body:** In the sample, the case packer fails 14 times in about 1,200 operating hours, an MTBF near 86 hours, while the air compressor failed once. The packer's MTTR of about two hours looks acceptable, so the problem is frequency, which points to root cause analysis, not faster repair. Another asset might have rare failures but long repairs, where better spares or a trained second technician help more. Sort by MTBF to find the repeat offenders and by MTTR to find slow recoveries, then pick the action that matches.

#### Common mistakes

**Body:** Common errors are using calendar hours instead of operating hours, mixing planned and unplanned work orders, and calculating MTBF on too few failures. With one or two events in the period the number is noise. Extend the window or group similar assets. Also remember that MTBF assumes a roughly constant failure rate, which is a reasonable approximation for many repairable systems but not for parts with wear out. In ERPs such as SAP PM, Infor EAM, Oracle EAM or Epicor, failure codes on notifications and work orders make this data far cleaner.

**Cta:** If failure counts and repair hours already sit in your ERP maintenance module, Netray can build a read-only MTBF and MTTR report over that data. This worksheet works fine on its own.

**Faq:**

#### What is the difference between MTBF and MTTR?

**Answer:** MTBF is the average operating time between failures of a repairable asset. MTTR is the average time to repair it after a failure. Together they determine how often an asset is lost and how long it stays out.

#### How do you calculate availability from MTBF and MTTR?

**Answer:** Inherent availability equals MTBF divided by the sum of MTBF and MTTR. It reflects failures and repairs only, ignoring planned maintenance and logistics delay, so it will be higher than the availability you measure on the floor.

#### Should planned maintenance count as a failure?

**Answer:** No. Count only unplanned events that stop the asset. Planned maintenance is scheduled and does not reflect inherent reliability. Track it separately so you can see how planned work affects availability.

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

**Answer:** More is better. With fewer than about five failures the figure swings widely from one period to the next. Use a longer period, or pool identical assets, before drawing conclusions about reliability.

## Search terms

mtbf mttr worksheet, mtbf calculator excel, mttr calculation template, mean time between failures template, equipment availability formula, reliability metrics spreadsheet, mtbf mttr availability, asset reliability tracker

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json