MTBF and MTTR Reliability Report by Equipment
Short answer: A custom ALV report that calculates, from breakdown notifications, the number of breakdowns, total downtime, mean time to repair (MTTR), mean time between failures (MTBF), availability percentage and repeat failures for each equipment. The most frequent damage and cause codes appear on the same line.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 6
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
MTBF and MTTR analyses in the maintenance information system (MCI7, MCJB) depend on statistics updates and do not give flexible filters for damage and cause codes, repeat failures or the company's own operating time. IW29 lists notifications but does not calculate the ratios. Reliability teams export the notification list to Excel every month and calculate these metrics by hand.
Who uses it? Reliability engineers, maintenance managers, production managers and TPM teams.
Closest standard alternatives
- IW29 Display Notifications (List). Lists breakdown notifications; no MTBF, MTTR, availability or repeat failure calculation.
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| QMIHNotification Maintenance Data | Breakdown flag, malfunction start and downtime (driving table) | — | ECC + S/4 |
| QMELNotification Header | Notification type, date and short text | QMEL-QMNUM = QMIH-QMNUM | ECC + S/4 |
| QMFENotification Items | Damage codes | QMFE-QMNUM = QMIH-QMNUM | ECC + S/4 |
| QMURNotification Causes | Cause codes | QMUR-QMNUM = QMFE-QMNUM AND QMUR-FENUM = QMFE-FENUM | ECC + S/4 |
| EQKTEquipment Short Texts | Equipment description | EQKT-EQUNR = QMIH-EQUNR AND EQKT-SPRAS = SY-LANGU | ECC + S/4 |
| ILOAPM Object Location and Account Assignment | Functional location | ILOA-ILOAN = QMIH-ILOAN | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_IWERK | Maintenance planning plant | Range / multiple | QMIH-IWERK | Yes | 1000 |
| S_EQUNR | Equipment | Range / multiple | QMIH-EQUNR | No | 10000045 |
| S_TPLNR | Functional location | Range / multiple | ILOA-TPLNR | No | TR01-URT-* |
| S_QMART | Notification type | Range / multiple | QMEL-QMART | No | M2 |
| S_AUSVN | Malfunction start date (period) | Range / multiple | QMIH-AUSVN | Yes | 01.08.2026 – 31.10.2026 |
| P_REPDAY | Repeat window (days) | Single value | — | No | 90 |
| P_HRDAY | Operating hours per day (for MTBF) | Single value | — | Yes | 24 |
| P_MINBR | Minimum number of breakdowns | Single value | — | No | 2 |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Equipment | QMIH-EQUNR |
| 2 | Description | EQKT-EQKTX |
| 3 | Functional location | ILOA-TPLNR |
| 4 | Breakdowns | Calculated Number of breakdown notifications in the period (N) |
| 5 | Total downtime (h) | Calculated Σ QMIH-AUSZT, converted to hours (D) |
| 6 | MTTR (h) | Calculated D ÷ N |
| 7 | MTBF (h) | Calculated (Period hours − D) ÷ N |
| 8 | Availability % | Calculated (Period hours − D) ÷ period hours × 100 |
| 9 | Repeat failures | Calculated Breakdowns that start within the repeat window after the previous one |
| 10 | Last breakdown | Calculated Largest QMIH-AUSVN |
| 11 | Top damage code | Calculated Most frequent QMFE-FEGRP / QMFE-FECOD |
| 12 | Top cause code | Calculated Most frequent QMUR-URGRP / QMUR-URCOD |
Sample output
| Equipment | Description | Functional location | Breakdowns | Total downtime (h) | MTTR (h) | MTBF (h) | Availability % | Repeat failures | Last breakdown | Top damage code | Top cause code |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 10000045 | Hydraulic press 400 t | TR01-URT-PRS | 6 | 38.50 | 6.40 | 361.60 | 98.30 | 2 | 10/27/2026 | HYD/04 | MEK/12 |
| 10000102 | Belt conveyor line 2 | TR01-URT-KNV | 4 | 14.50 | 3.60 | 548.40 | 99.30 | 1 | 10/19/2026 | ELK/02 | ELK/07 |
| 10000078 | Screw compressor 75 kW | TR01-YRD-KMP | 2 | 9 | 4.50 | 1,099.50 | 99.60 | 0 | 09/14/2026 | MEK/03 | MEK/01 |
How does the report work?
- Maintenance notifications with the breakdown flag (MSAUS) set and a malfunction start (AUSVN) inside the selected period are read from QMIH; notification type (QMART) and date are added from QMEL and deleted notifications are skipped.
- Downtime = QMIH-AUSZT, converted to hours with unit MAUEH. The number of breakdowns N and total downtime D are calculated per equipment.
- MTTR = D ÷ N. Period hours = days in period × operating hours per day. MTBF = (period hours − D) ÷ N. Availability % = (period hours − D) ÷ period hours × 100.
- Repeat failures: breakdowns on the same equipment that start within the repeat window (days) after the start of the previous breakdown are counted.
- The damage code (FEGRP/FECOD) from QMFE and the cause code (URGRP/URCOD) from QMUR are added as the most frequent value. The functional location comes through QMIH-ILOAN → ILOA-TPLNR and the equipment description from EQKT.
- Equipment below the minimum number of breakdowns is skipped; ALV is sorted by MTBF ascending, so the least reliable equipment comes first.
Performance notes
Narrow QMIH by planning plant and malfunction start date. Read QMFE and QMUR with FOR ALL ENTRIES only for the selected notifications. The report can run in the background before the monthly reliability meeting.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document An equipment line lists the breakdown notifications of the period; a notification opens IW23.
- Export to Excel
- Runs as a background job
- Send the result by email A monthly reliability summary can be sent to managers.
Authorization objects
- I_QMELDisplay maintenance notifications by notification type
- I_SWERKDisplay by maintenance plant
Frequently asked questions
Is MTBF based on calendar time or operating time?
It is set by the operating hours per day parameter: 24 gives calendar time, the shift length gives operating time. For equipment with counters, the real operating hours can also be read from measurement documents.
What happens to notifications without downtime?
They are counted as breakdowns, but add zero downtime and are flagged in a separate warning column, so the data quality issue becomes visible.
Does it work on S/4HANA?
Yes. QMEL, QMIH, QMFE and QMUR keep the same structure in S/4HANA. For a clean core approach, I_MaintenanceNotification and related CDS views can be used.
Packages that include this solution
Maintenance KPI Pack
A pack that delivers the four core indicators of the monthly maintenance review with one plant, work center and equipment selection: maintenance …
Related reports
Maintenance Cost and Downtime by Equipment Report
A custom ALV report that splits the actual cost of maintenance orders per equipment in a period into labor, material, external services and other, and …
Open Maintenance Notifications Without Order Aging Report
A custom ALV report that lists open notifications not yet converted to a maintenance order by age, priority and how far they are past the required end …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.