# MTBF and MTTR Reliability Report by Equipment

> 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.

- Type: Report, Custom development, ALV report
- Module: PM
- Estimated effort: M (4–6 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/mtbf-mttr-by-equipment-report/


## 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.

### Closest standard alternatives

- IW29: Lists breakdown notifications; no MTBF, MTTR, availability or repeat failure calculation.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| QMIH | Breakdown flag, malfunction start and downtime (driving table) | Read | - | ECC + S/4 |
| QMEL | Notification type, date and short text | Read | QMEL-QMNUM = QMIH-QMNUM | ECC + S/4 |
| QMFE | Damage codes | Read | QMFE-QMNUM = QMIH-QMNUM | ECC + S/4 |
| QMUR | Cause codes | Read | QMUR-QMNUM = QMFE-QMNUM AND QMUR-FENUM = QMFE-FENUM | ECC + S/4 |
| EQKT | Equipment description | Read | EQKT-EQUNR = QMIH-EQUNR AND EQKT-SPRAS = SY-LANGU | ECC + S/4 |
| ILOA | Functional location | Read | ILOA-ILOAN = QMIH-ILOAN | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_IWERK | Maintenance planning plant | Range / multiple | QMIH-IWERK | Yes |
| S_EQUNR | Equipment | Range / multiple | QMIH-EQUNR | No |
| S_TPLNR | Functional location | Range / multiple | ILOA-TPLNR | No |
| S_QMART | Notification type | Range / multiple | QMEL-QMART | No |
| S_AUSVN | Malfunction start date (period) | Range / multiple | QMIH-AUSVN | Yes |
| P_REPDAY | Repeat window (days) | Single value | - | No |
| P_HRDAY | Operating hours per day (for MTBF) | Single value | - | Yes |
| P_MINBR | Minimum number of breakdowns | Single value | - | No |

## Output columns

| Column | Source |
|---|---|
| Equipment | QMIH-EQUNR |
| Description | EQKT-EQKTX |
| Functional location | ILOA-TPLNR |
| Breakdowns | Calculated: Number of breakdown notifications in the period (N) |
| Total downtime (h) | Calculated: Σ QMIH-AUSZT, converted to hours (D) |
| MTTR (h) | Calculated: D ÷ N |
| MTBF (h) | Calculated: (Period hours − D) ÷ N |
| Availability % | Calculated: (Period hours − D) ÷ period hours × 100 |
| Repeat failures | Calculated: Breakdowns that start within the repeat window after the previous one |
| Last breakdown | Calculated: Largest QMIH-AUSVN |
| Top damage code | Calculated: Most frequent QMFE-FEGRP / QMFE-FECOD |
| Top cause code | Calculated: Most frequent QMUR-URGRP / QMUR-URCOD |

## How does the report work?

1. 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.
2. Downtime = QMIH-AUSZT, converted to hours with unit MAUEH. The number of breakdowns N and total downtime D are calculated per equipment.
3. MTTR = D ÷ N. Period hours = days in period × operating hours per day. MTBF = (period hours − D) ÷ N. Availability % = (period hours − D) ÷ period hours × 100.
4. Repeat failures: breakdowns on the same equipment that start within the repeat window (days) after the start of the previous breakdown are counted.
5. 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.
6. Equipment below the minimum number of breakdowns is skipped; ALV is sorted by MTBF ascending, so the least reliable equipment comes first.

## Authorization objects

- I_QMEL: Display maintenance notifications by notification type
- I_SWERK: Display 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=pm-mtbf-mttr-by-equipment
