PM Report Custom development ALV report

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.

TableRoleJoinSystem
QMIHNotification Maintenance DataBreakdown flag, malfunction start and downtime (driving table)—ECC + S/4
QMELNotification HeaderNotification type, date and short textQMEL-QMNUM = QMIH-QMNUMECC + S/4
QMFENotification ItemsDamage codesQMFE-QMNUM = QMIH-QMNUMECC + S/4
QMURNotification CausesCause codesQMUR-QMNUM = QMFE-QMNUM AND QMUR-FENUM = QMFE-FENUMECC + S/4
EQKTEquipment Short TextsEquipment descriptionEQKT-EQUNR = QMIH-EQUNR AND EQKT-SPRAS = SY-LANGUECC + S/4
ILOAPM Object Location and Account AssignmentFunctional locationILOA-ILOAN = QMIH-ILOANECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_IWERKMaintenance planning plantRange / multipleQMIH-IWERKYes1000
S_EQUNREquipmentRange / multipleQMIH-EQUNRNo10000045
S_TPLNRFunctional locationRange / multipleILOA-TPLNRNoTR01-URT-*
S_QMARTNotification typeRange / multipleQMEL-QMARTNoM2
S_AUSVNMalfunction start date (period)Range / multipleQMIH-AUSVNYes01.08.2026 – 31.10.2026
P_REPDAYRepeat window (days)Single value—No90
P_HRDAYOperating hours per day (for MTBF)Single value—Yes24
P_MINBRMinimum number of breakdownsSingle value—No2

Output columns

#ColumnSource
1EquipmentQMIH-EQUNR
2DescriptionEQKT-EQKTX
3Functional locationILOA-TPLNR
4BreakdownsCalculated Number of breakdown notifications in the period (N)
5Total downtime (h)Calculated Σ QMIH-AUSZT, converted to hours (D)
6MTTR (h)Calculated D ÷ N
7MTBF (h)Calculated (Period hours − D) ÷ N
8Availability %Calculated (Period hours − D) ÷ period hours × 100
9Repeat failuresCalculated Breakdowns that start within the repeat window after the previous one
10Last breakdownCalculated Largest QMIH-AUSVN
11Top damage codeCalculated Most frequent QMFE-FEGRP / QMFE-FECOD
12Top cause codeCalculated Most frequent QMUR-URGRP / QMUR-URCOD

Sample output

EquipmentDescriptionFunctional locationBreakdownsTotal downtime (h)MTTR (h)MTBF (h)Availability %Repeat failuresLast breakdownTop damage codeTop cause code
10000045Hydraulic press 400 tTR01-URT-PRS638.506.40361.6098.30210/27/2026HYD/04MEK/12
10000102Belt conveyor line 2TR01-URT-KNV414.503.60548.4099.30110/19/2026ELK/02ELK/07
10000078Screw compressor 75 kWTR01-YRD-KMP294.501,099.5099.60009/14/2026MEK/03MEK/01
A view built with fictional sample data; not real system data.

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.

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

PM Package Custom

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 …

4 components · v1.0

Related reports

PM Report Custom ALV report

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 …

AFIH · AUFK · COEP · QMIH

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.

Related report: MTBF and MTTR Reliability Report by Equipment