SAP PM Measuring Point and Counter Readings Worksheet
Performance-based maintenance only works if somebody reads the meters and the numbers reach SAP. This worksheet gives you a clean sheet to plan the measuring points, log readings and see which counter will hit its service threshold first.
| Equipment | Measuring point | Point type | Unit | Previous reading | Current reading | Days between readings | Service interval | Counter at last service | Usage since previous | Usage per day | Remaining to service | Days to service | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
168 | 24 | 1,412 | 59 days | ||||||||||
49,000 | 7,000 | 41,000 | 6 days | ||||||||||
48 | 6.8571 | 82 | 12 days | ||||||||||
52 | 7.4286 | 738 | 99 days | ||||||||||
-4 | -0.5714 | -176 | 0 days |
Counters accumulate and drive performance-based maintenance plans. Measuring points that are not counters (pressure, temperature) record a value, so set the service interval to 0 and ignore the remaining columns. Replace the sample rows with your own.
Connect meters to SAP PM
Optional: we look at where your hours and cycle counts live today and sketch a path to SAP measurement documents.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
List each counter or measuring point you maintain, with the unit and the service interval from the maintenance strategy. Each week enter the previous and current reading and the days between them. The sheet computes usage per day and projects how many days remain until the next service, assuming the current rate holds. Sort by days to service to build the next call-up list. Export to Excel to compare against what SAP shows in its measurement document history.
- One row per measuring point, not per machine
- Counter points are created in IK01, readings entered in IK11
- Use the same unit that is stored on the measuring point
How SAP treats counters
A counter measuring point holds a cumulative total and SAP derives the difference between readings. The counter has an overflow value, so a rollover needs a counter replacement entry, not a negative difference. A performance-based maintenance plan uses the annual estimate or the actual readings to forecast the next call-up date. Poor reading discipline causes the forecast to drift, which is why plans call early or late. The projected date on this sheet is a sanity check, not a replacement for the plan.
Common mistakes
Plants often create the measuring point but never schedule who reads it. Others enter the reading with the wrong date, which wrecks the usage rate. A counter replaced during a rebuild needs a new counter or a documented reset. Finally, copying one annual estimate to every similar machine hides the fact that spare machines run far fewer hours.
- Verify the reading date, not the entry date
- Document counter replacements and rollovers
- Review annual estimates once a year against actual usage
Frequently Asked Questions
What is the difference between a counter and a measuring point?
A counter accumulates, such as running hours or cycles, and SAP uses the difference between readings. A plain measuring point records a value at a moment, such as pressure or temperature, and is compared with limits for alerts.
Which transactions do I use?
IK01 creates a measuring point, IK02 changes it, and IK11 enters a measurement document. Counters can also be read through mobile apps or uploaded in bulk through standard measurement document interfaces.
How accurate is the days-to-service figure?
It is a straight-line projection from the last interval. If usage is seasonal or the machine was idle, the figure is off. Treat it as a planning aid and let the SAP plan do the formal scheduling.
Can I paste this into a SAP upload?
You can reuse the equipment, point and reading columns as a source for your own upload template. Check your system's measurement document upload format and test in a non-production client first.
If readings come from PLCs, historians or MES, Netray can help feed them to SAP measurement documents with an approval step. We only recommend it when manual rounds are a real bottleneck.
Related Tools
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.
SAPSAP PM Maintenance KPI Calculator (MTBF, MTTR, Backlog)
Enter a period's breakdown hours, failures, backlog and crew data to get MTBF, MTTR, availability, planned-work share and weeks of backlog.
SAPSAP 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.
SAPSAP 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.
More SAP tools
See all- SAP QM Inspection Types Reference
- SAP QM Usage Decision Codes Worksheet
- SAP QM Sampling Procedure Design Template
- SAP QM Quality Notification Types Reference
- SAP Master Inspection Characteristic Upload Worksheet
- SAP QM in Procurement Setup Checklist
- SAP QM Inspection Lot Origins Reference
- SAP QM Dynamic Modification Rule Calculator
- SAP PM Maintenance BOM and Spare Parts Cost Worksheet