Free mtbf mttr tracking template
Jump to download form ↓Enter your email below to download this mtbf mttr tracking template as a ready-to-use PDF.
Free MTBF MTTR tracking template. Mean time between failures, mean time to repair, availability per ISO 14224 and IEEE 762 reliability standards.
Commercial Director
Updated 25 May 2026
How to use: download the PDF, print or complete digitally on any device.
- PDF format, ready to print or fill on screen
- Use as-is or customise to suit your operation
- Go digital in MapTrack for photos, alerts and audit trails
Download free PDF template
Trusted by teams across Australia and New Zealand
We respect your privacy. Unsubscribe anytime.
Used by construction, mining and field service teams
What is a mtbf mttr tracking template?
An MTBF MTTR tracking template is a reliability worksheet that calculates Mean Time Between Failures (MTBF) and Mean Time To Repair (MTTR) per asset from the underlying failure events captured against work orders, then rolls the two figures into an availability percentage that operations, reliability and finance read as a single asset performance indicator. It is a different document from a work order or a PM compliance report. A work order captures a single event. A PM compliance report measures whether scheduled work landed on time. An MTBF MTTR tracker measures how reliable the asset actually is and how quickly the maintenance organisation can restore it when it fails. The two metrics together define availability, calculated as MTBF divided by the sum of MTBF and MTTR.
The tracker is built per asset (or per asset class for fleet aggregation) and runs on a rolling window, typically six months or twelve months. Inputs are total operating time in the window, the count of failure events in the window and the total repair time across those events. MTBF is operating time divided by number of failures, expressed in hours or in operating-hours-per-failure. MTTR is total repair time divided by number of failures, expressed in hours per repair. The headline outputs (MTBF, MTTR, availability, six-month trend, failure-mode pareto) feed the reliability programme, the critical spares list, the FMEA worksheet and the capital-versus-maintenance trade-off conversations.
From a standards angle, ISO 14224 provides the reliability data collection framework and the failure-mode taxonomy that makes the data comparable across assets and across organisations, ISO 55001 sets the asset management system requirement for performance reporting against the maintenance plan, and IEEE Std 762 provides the formal definitions of availability and reliability metrics used in process and power industries. A consistent MTBF MTTR tracker is the difference between a reliability function that operates on hard data and one that operates on the loudest opinion in the room.
Learn more about maintenance and work orders in MapTrack.
Benefits of using this mtbf mttr tracking template
- Defensible reliability data: structured MTBF and MTTR calculation against a consistent operating-time and failure-count input produces numbers the team can defend
- Availability as a single indicator: rolling MTBF and MTTR into an availability percentage gives operations and finance a single number to read
- Failure-mode pareto: classifying every failure event against the ISO 14224 taxonomy reveals which two or three modes drive the majority of downtime
- OEM benchmark comparison: holding MTBF against the OEM published benchmark or against historical baseline surfaces drift before it becomes a major issue
- Critical spares feedback: failure-mode pareto data flows directly into the critical spares list so inventory matches the actual failure pattern
- RCM review trigger: assets where MTBF is declining or MTTR is climbing on the trend chart are the first candidates for a Reliability-Centred Maintenance review
- Capital replacement evidence: when MTBF on a specific asset has degraded past the economic threshold, the trend chart is the evidence that supports a replacement business case
Benefits of digitising forms in MapTrack
When you digitise mtbf mttr tracking process documents in MapTrack, you get:
- Field users can easily scan a QR code to complete a form on mobile. Unlimited users.
- Automatically get alerts when faults are identified.
- Link every form digitally as a PDF to the relevant asset, location or person.
- Receive a digital PDF copy with every submission to your email.
- Ability to share forms digitally.
- Build conditional logic (show or hide questions based on answers).
- Take pictures or attach photos. Not possible with a paper-based form.
- Electronic signatures.
- Edit forms later without reprinting.
- Restrict permissions (who can view, complete or approve).
- Build forms with AI (describe what you need and MapTrack suggests the form).
- Trigger work orders automatically when a fault is logged during an inspection.
- Track service intervals by hours, kilometres or calendar date in one place.
- Attach supplier invoices and parts receipts to each maintenance record.
Book a demo to see how MapTrack handles mtbf mttr tracking process documents.
Try MapTrack free for 30 days
Full access to every feature. No credit card required. Per-asset pricing so you scale as your fleet grows.
- No credit card required
- 30 days free trial
- Cancel anytime
1-2 days/week saved
“Bloody amazing! We used to spend 1-2 days a week tracking and managing our generators alone.”
Steve McAllister
Asset Coordinator, Saunders International
What to include in a mtbf mttr tracking template
This mtbf mttr tracking template covers 12 key areas:
- Asset identification: asset ID, name, OEM make and model, serial number, asset criticality from the asset register and link to the FMEA worksheet
- Rolling window definition: the window length (typically six months or twelve months), the start and end dates and the data-source reference (CMMS work-order log)
- Total operating time in window: hours the asset was scheduled to run inside the window, sourced from the operations roster or the SCADA run-time signal, excluding planned shutdown
- Failure event log: every failure event in the window with date, work-order number, failure mode against ISO 14224, severity, downtime hours and the technician sign-off reference
- Number of failures in window: count of failure events in the window, excluding planned shutdown events but including unplanned reactive callouts and failed pre-start inspections
- Total repair time across events: sum of hours from failure event to return-to-service across every event in the window, including diagnosis, parts wait, repair and sign-off
- MTBF calculation: operating time in window divided by number of failures, expressed as operating hours per failure
- MTTR calculation: total repair time divided by number of failures, expressed as hours per repair
- Availability percentage: MTBF divided by the sum of MTBF and MTTR, expressed as a percentage, with the OEM published benchmark or historical baseline noted alongside
- Six-month or twelve-month trend: MTBF, MTTR and availability for each window in the rolling series so the direction of travel is visible
- Failure-mode pareto: count of failures by ISO 14224 mode, sorted descending so the dominant modes are visible at the top
- Sign-off and review trigger: reliability engineer who prepared the worksheet, maintenance manager review, RCM review trigger flag set where MTBF declining or MTTR climbing materially and date of next scheduled review
How to use this mtbf mttr tracking template
- 1. Define the rolling window and the asset scope: agree the window length (typically six months or twelve months) and the start and end dates, agree whether the worksheet runs per asset or per asset class (fleet aggregation is appropriate for identical assets but masks individual outliers), document the scope decision so future windows are consistent
- 2. Pull the operating-time input: source the total operating time in the window from the operations roster, the SCADA run-time signal or a meter reading, exclude planned shutdown hours, document the data source explicitly because operating-time assumption errors are the single biggest distortion in MTBF data
- 3. Pull the failure-event log: pull every failure event in the window from the CMMS work-order log, exclude planned shutdown events but include unplanned reactive callouts and failed pre-start inspections, validate that every event has a date, a work-order number, a failure-mode classification and a recorded downtime in hours
- 4. Classify every failure mode against ISO 14224: walk the failure event list and confirm each event is classified against the ISO 14224 taxonomy (leakage, vibration, sticking, instrument deviation, external damage, breakage, premature wear), correct any free-text-only events so the pareto analysis at the end is defensible
- 5. Sum the total repair time: across every failure event in the window, sum the hours from failure event to return-to-service (diagnosis time plus parts-wait time plus repair time plus sign-off), document the inclusion rule (whether parts-wait time is included) so the MTTR figure is comparable across windows
- 6. Calculate MTBF: operating time in window divided by number of failures, expressed in operating hours per failure, round to a sensible precision (whole hours for high-frequency-failure assets, one decimal for low-frequency-failure assets), record the calculation method as a note for the next analyst
- 7. Calculate MTTR: total repair time divided by number of failures, expressed in hours per repair, round to one decimal place, flag any single event with an exceptionally long repair time so the average is not distorted by an outlier (consider reporting median MTTR alongside mean MTTR if outliers are material)
- 8. Calculate availability and compare to benchmark: divide MTBF by the sum of MTBF and MTTR, multiply by 100 and express as a percentage, compare against the OEM published benchmark and against the same asset historical baseline (six months prior, twelve months prior), call out any material drift
- 9. Produce the failure-mode pareto and trigger RCM review where needed: sort the failure-mode count descending, identify the dominant two or three modes that drive the majority of downtime, raise a Reliability-Centred Maintenance review trigger against any asset where MTBF is declining materially or MTTR is climbing, file the worksheet against the asset record in MapTrack with reliability engineer and maintenance manager sign-off
In MapTrack, you can schedule and track maintenance digitally. Each submission is stored as a timestamped PDF against the asset record.
Get the free templateEnter your email above to download the full mtbf mttr tracking template as a PDF.Back to download formHow often should you complete this process document?
MTBF MTTR tracking runs on a rolling-window cadence rather than a fixed reporting period, but the calculation is refreshed on a monthly schedule so the trend chart updates each month with the most recent thirty days rolled into the rolling six-month or twelve-month window. The fixed monthly refresh is the floor. Beyond the monthly refresh, event-driven recalculations are triggered whenever a significant failure event happens on a critical-criticality asset, a Reliability-Centred Maintenance review is opened on an asset class, a critical spares list review is in progress and needs the latest failure-mode pareto, an OEM service bulletin or modification has been applied and the team wants to track post-modification performance, or a capital replacement business case is being prepared and needs the trend chart as evidence. Operating-time inputs should be reviewed at every monthly refresh because operating-time assumption errors are the single biggest distortion in the data. MapTrack auto-rolls the failure-event log into MTBF and MTTR figures against every asset on a monthly cadence so the tracker is not rebuilt manually each period and the audit trail is preserved.
Frequently asked questions
Applicable regulatory standards
This template aligns with the following regulations and standards:
- ISO 14224 (Reliability data collection)
- ISO 55001 (Asset management systems)
- IEEE Std 762 (Availability and reliability definitions)
- AS/NZS ISO 9001 (Quality management)
Embed this free template on your website
Run an industry blog, trade association site, or training resource? Drop a preview of this free mtbf mttr tracking template straight into your page. The snippet is self-contained, needs no scripts, and links readers back to the full free template.
<div style="max-width:480px;font-family:system-ui,-apple-system,'Segoe UI',Roboto,sans-serif;border:1px solid #E5E7EB;border-radius:12px;padding:20px;background:#ffffff;">
<p style="font-size:12px;font-weight:700;letter-spacing:0.05em;text-transform:uppercase;color:#0E7490;margin:0;">Free template</p>
<p style="font-size:18px;font-weight:700;color:#071D49;margin:6px 0 0;">MTBF MTTR Tracking Template</p>
<ul style="margin:12px 0 0;padding-left:18px;color:#374151;font-size:14px;line-height:1.6;">
<li style="margin:4px 0;">Asset identification: asset ID, name, OEM make and model, serial number, asset criticality from the asset register and link to the FMEA worksheet</li>
<li style="margin:4px 0;">Rolling window definition: the window length (typically six months or twelve months), the start and end dates and the data-source reference (CMMS work-order log)</li>
<li style="margin:4px 0;">Total operating time in window: hours the asset was scheduled to run inside the window, sourced from the operations roster or the SCADA run-time signal, excluding planned shutdown</li>
<li style="margin:4px 0;">Failure event log: every failure event in the window with date, work-order number, failure mode against ISO 14224, severity, downtime hours and the technician sign-off reference</li>
<li style="margin:4px 0;">Number of failures in window: count of failure events in the window, excluding planned shutdown events but including unplanned reactive callouts and failed pre-start inspections</li>
<li style="margin:4px 0;">Total repair time across events: sum of hours from failure event to return-to-service across every event in the window, including diagnosis, parts wait, repair and sign-off</li>
</ul>
<p style="font-size:13px;color:#6B7280;margin:14px 0 0;padding-top:12px;border-top:1px solid #E5E7EB;">Free <a href="https://www.maptrack.com/templates/mtbf-mttr-tracking-template" style="color:#071D49;font-weight:600;text-decoration:none;">MTBF MTTR Tracking Template</a> by MapTrack</p>
</div>Please keep the “by MapTrack” attribution link in the snippet.
Need to schedule and track maintenance digitally?
Register every mtbf mttr tracking in MapTrack, attach digital forms, and get a complete history of every inspection, service and compliance record.
Maintenance and work orders · All templates · Pricing · Book a demo