Maintenance KPI dashboard built on SAP PM
PM Run delivers ready-to-use, automated maintenance data, from execution in SAP PM, for you to build the KPI dashboard that makes sense for your operation.
What a maintenance KPI dashboard is
A maintenance KPI dashboard is the set of KPIs that shows the health of the operation: MTTR, MTBF, backlog by criticality, availability, costs and team occupancy. A dashboard is only reliable when the numbers come from execution. PM Run delivers this data ready and automated, from the logging in SAP PM, for you to build your own dashboard.
Free guides to calculate today's maintenance KPIs
If your KPIs are still compiled in a spreadsheet, start here: the MTTR and MTBF formulas, backlog in weeks and OEE step by step.
When the KPI spreadsheet stops working
The formula solves the math. These are the signs that the problem has become the source of the data that goes into it.
- MTTR is calculated with hours typed at the end of the shiftRepair time comes from memory, and the indicator changes depending on who made the entry.
- Machine stops are noted without a start and end timeMTBF depends on who remembered to record the failure, and the number does not match what production saw stop.
- Each technician describes the failure in their own wordsWithout standardized part, symptom and cause, nobody can group failures by equipment or by class.
- Month-end closing takes days of spreadsheet workWhen the number reaches the meeting, the next month has already started and the decision comes late.
With PM Run, the KPI starts where the work is done
The technician opens the notification with Machine Down, and SAP records the start of the breakdown and the end when the order is closed. Hours are booked by operation during the job, and the failure is described with the part, symptom and cause catalogs. The data goes to SAP PM, and PM Run delivers it ready for you to build your dashboard.
What you can build in your dashboard
You choose the indicators and build the dashboard with the data PM Run delivers ready for analysis.
MTTR by equipment and class
Track the mean time to repair by asset and by class, based on the times logged during execution.
MTBF by equipment and class
Measure the mean time between failures by equipment, fed by the Machine Down record.
Backlog by criticality
See the maintenance backlog split by criticality, to prioritize what blocks the operation.
Rescheduling index
See how much of the schedule is rescheduled and where the planning slips during the period.
Cost analysis
Compare actual vs. planned cost and track the maintenance cost by asset and by order.
Team occupancy
Measure occupancy and productivity by work center, based on the hours actually confirmed.
Where your dashboard data is born
This is how the time of each operation is recorded in the app during execution.
- Planned and executed timeEach operation shows the planned time, and the execution timer runs while the technician works.
- Pause mid-jobThe pause button stops the count when the work stops.
- Equipment and location of the operationEach operation carries the equipment and functional location where the time was spent.
- Measurement and material in the orderThe Measurement and Material shortcuts record what was read and used without leaving the operation.
How the data reaches your dashboard ready to use
- 1
The technician records the breakdown
The notification opened with Machine Down marks the start of the breakdown. When the order is closed, SAP records the end and calculates the downtime.
- 2
Logs the hours during execution
The confirmation is made by operation, during the job, automatic or manual.
- 3
Describes the failure with catalogs
Part, symptom and cause come from the SAP PM catalogs, in the same standard for the whole team.
- 4
Everything goes to SAP PM
On sync, the order, the notification and the time logging go to SAP, validated in the Integration Log.
- 5
You build the dashboard
With the data ready, you choose the indicators and how to break them down: by equipment, class, criticality or work center.
Manual spreadsheet vs. a dashboard fed by execution data
| Criterion | Manual spreadsheet | With PM Run |
|---|---|---|
| Source of the data | Typed after the shift | Logging during the job |
| MTTR and MTBF | Estimated, prone to error | Calculated from real times in SAP |
| Backlog | Counted by hand | Split by criticality |
| Costs | Manual closing | Actual vs. planned cost |
| Building the dashboard | Redone every month | Automated data, you build it once |
| Trust in the number | Low, depends on who typed it | High, the data comes from execution |
Reliable execution data in practice
At Rivelli, the team started confirming the order on the tablet during the maintenance itself, and MTBF and MTTR tracking became more precise.
50% reduction in time spent on manual tasks
Rivelli Alimentos
At Citrosuco, technicians started recording notes and photos directly on the order from their phones, with automatic sync to SAP PM.
Order confirmation rate above 95%
Citrosuco
Frequently asked questions
What is a maintenance KPI dashboard?
It is the set of KPIs that shows the health of maintenance: MTTR, MTBF, backlog by criticality, availability, costs and team occupancy. It turns the raw data of the operation into visual information to prioritize resources, plan the preventive maintenance and decide between repairing or replacing an asset.
Does PM Run deliver the dashboard already built?
No. The model is self-service. PM Run delivers the maintenance data ready and automated, from execution in SAP PM, and you build the dashboard that makes sense for your operation, using your own criteria.
Which indicators can you build?
For example: MTTR and MTBF by equipment and by class, maintenance backlog by criticality, rescheduling index, cost analysis and team occupancy. You choose and build the most relevant indicators with the data that PM Run makes available ready for analysis.
Where does the dashboard data come from?
From execution logged in SAP PM. The Machine Down flag marks the start of the breakdown and SAP calculates the downtime when the order is closed, time is confirmed during the job and the part, symptom and cause catalogs standardize the failure record. This data feeds the indicators automatically, without retyping in a spreadsheet.
Do I need a spreadsheet to track the indicators?
No. The whole idea is to take the manual spreadsheet out of the way. The data arrives ready and automated from execution in SAP PM, and you build your dashboard once, instead of redoing the closing and the typing every month.
Is a maintenance KPI dashboard the same as a maintenance dashboard?
Yes. Maintenance dashboard is another name for the KPI dashboard. In the PM Run model, the execution data in SAP PM arrives ready and automated and you build the dashboard for your operation, with MTTR and MTBF by equipment and class, backlog by criticality, costs and team occupancy.
Is there a free guide to calculate MTTR and MTBF?
Yes. PM Run publishes a free guide with the MTTR and MTBF formulas, a worked example, the difference to MTTF and how to build the spreadsheet, plus guides on maintenance backlog and OEE.
Does the PM Run portal show open notifications?
Yes. In the portal, the at-a-glance management panel tracks open notifications by criticality, their status and response time, from the opening of the notification to its resolution, with email escalation when a notification stays pending.
Related content
Book a demo and see where your maintenance KPI dashboard data comes from
We show how the execution data in SAP PM arrives ready for you to build the KPIs of your operation.