SAPFree calculatorPDF, Excel, Word exportSAP ECC / S/4HANAManufacturing

SAP PM Maintenance KPI Calculator: MTBF, MTTR, Availability and Backlog

Four numbers tell most of the story of a maintenance department: how often things fail, how long they take to fix, how much of the work is planned, and how much work is waiting. This calculator computes them from one period's data.

Your numbers

h

30 days at 24 hours is 720.

h

Scheduled maintenance, changeovers excluded if you track them elsewhere.

h

Sum of breakdown durations from notifications.

events
h

From confirmations on planned orders.

h
h

Estimated hours on released orders waiting to be done.

people
h
45 %

Share of the day spent on hands-on work.

Your results

Operational availability
94.7%
Share of available time the asset ran.
Backlog
5.8 weeks
Weeks of work if the crew only worked the backlog.
Operating time
644 hrs
Calendar hours minus all downtime.
MTBF
72 hrs
Mean operating time between failures.
MTTR
4 hrs
Mean time to repair per failure.
Inherent availability
94.7%
MTBF divided by MTBF plus MTTR.
Planned work share
70.5%
Many plants aim for a majority of hours planned.

Definitions differ between plants. Agree on what counts as planned downtime and how failures are counted before comparing numbers over time or between sites.

Save results:

Backlog weeks vs wrench time

Sweeps Wrench time from 20 to 80, holding your other inputs fixed.

KPIs straight from SAP

Optional: we show how these numbers can be read from your SAP PM data without exporting to Excel.

Optional. The tool and every export work without this. No spam.

How to use the calculator

Pick a period, usually a month, and a group of assets, such as a line or a plant. Take calendar hours, planned downtime and unplanned downtime from your records. Count failures from breakdown notifications or malfunction reports in SAP PM, and the hours from order confirmations split by planned and unplanned work. Backlog is the estimated hours on released orders not yet worked. Enter the crew size and a realistic wrench time and read the results.

  • Use the same asset group in every period
  • Count each failure once, not once per order
  • Use estimated hours for backlog, not actuals

The formulas

MTBF is operating time divided by the number of failures. MTTR is repair time divided by the number of failures. Operational availability is operating time divided by the time the asset was supposed to be available. Inherent availability is MTBF divided by the sum of MTBF and MTTR, which ignores planned stops. Planned work share is planned hours divided by total hours. Backlog in weeks is the backlog hours divided by the weekly productive capacity, which is headcount times hours per week times wrench time.

How to read the results

A short MTBF with a short MTTR means many small stops, usually an operating or lubrication problem. A long MTTR means diagnosis, parts or skills delay. A low planned share means the team is mostly reacting. A backlog of several weeks is normal, but a backlog that grows every month means capacity is short or wrench time is low. The chart shows how much a better wrench time cuts backlog, a useful point when asking for planning resources.

  • Zero failures gives MTBF of 0 here because the formula would divide by zero
  • Trend the numbers monthly, do not judge one month
  • Compare against your own history before any benchmark

Frequently Asked Questions

What is a good MTBF?

There is no universal number. It depends on the asset, the duty and the failure definition. Compare your own trend over time and against similar assets in the same plant rather than against a generic figure.

How do I get failures from SAP PM?

Count malfunction notifications with the breakdown indicator set for the assets in scope, or count orders of a corrective type, depending on how your plant works. Be consistent in whichever you use.

What is wrench time?

It is the share of a technician's paid time spent on hands-on work, as opposed to travel, waiting for parts, permits or instructions. Studies at many plants find it well below the full shift, which is why measuring it matters.

Why do two availability figures differ?

Operational availability includes the effect of unplanned downtime during the real period. Inherent availability uses only MTBF and MTTR and ignores logistics and planned stops, so it is usually higher.

Netray can pull these figures from SAP PM notifications and confirmations on your own servers and show them by line, with the query visible, so you stop assembling them in spreadsheets.

Talk to an ExpertExplore More Free Tools

Related Tools

SAP

SAP PM Catalog and Code Group Design Worksheet

Plan code groups and codes for damage, cause, object part and activity, so failure data becomes something you can analyze.

SAP

SAP PM Spare Parts Kitting and Reservation Worksheet

Track which parts each maintenance order needs, what is on hand, what is short and what it costs to buy, before the kit is picked.

SAP

SAP PM Breakdown Notification Request Form Template

A paper-or-PDF form that captures every field a planner needs to key a malfunction report (M2) into SAP PM, so nothing is chased by phone afterwards.

SAP

SAP PM Measuring Point and Counter Readings Worksheet

Log counter readings for running hours or cycles, compute daily usage and the days left until a performance-based service is due.

More SAP tools

See all
Back to All Tools