In SAP EAM / PM, a measuring point is a place on a technical object where a condition or reading is recorded, such as temperature, pressure or vibration. A counter is a particular type of measuring point used for values that accumulate over time, such as operating hours, distance or production quantity. Measurement documents preserve the actual readings and can support condition- or performance-based maintenance.
Why maintenance teams record readings
Not all maintenance should be triggered only by calendar dates. A pump may need attention when vibration rises, a vehicle after a distance threshold, or a machine after a defined number of operating hours. Measuring points give those observations a stable definition tied to equipment or a functional location.
Measuring point versus counter
A normal measuring point can capture a current condition value. A counter is designed for cumulative usage and is therefore useful when maintenance frequency depends on performance rather than simply elapsed time. The distinction matters because scheduling logic depends on what the reading represents.
How readings enter maintenance planning
When a reading is recorded, SAP creates a measurement document for the relevant measuring point or counter. Regular counter readings can influence when a performance-based maintenance call becomes due. Condition readings can also provide evidence for inspection, diagnosis and maintenance decisions.
Consultant checks
Confirm the technical object, characteristic and unit of measure; define whether the value is a condition or cumulative counter; agree who records readings and how frequently; and test implausible, missing or reset values. A counter history is only trustworthy when rollover, replacement and corrections are handled consistently.
Continue with Equipment Master, Maintenance Plans, Maintenance Strategies and the SAP EAM / PM hub.