SAP PM Counter-Based Maintenance Plan Interval Calculator
Performance-based maintenance plans in SAP PM call work when a counter such as running hours reaches a cycle length. Planners still need to know what that means in calendar terms for staffing and budgets, and this calculator does that conversion.
Your numbers
Average counter increase per day, from measurement documents on the measuring point (running hours or cycles).
Cycle length in the maintenance strategy or single-cycle plan, for example 2,000 running hours.
Percent of the cycle after which the call object is created.
Your results
Planning arithmetic only. The actual call dates in SAP depend on measurement documents, the strategy and plan settings; check results in IP10 and IP30.
Calls per year vs daily usage
Sweeps Average usage per calendar day from 2 to 24, holding your other inputs fixed.
Maintenance plan health check
Optional expert review of overdue plans, counter data and call horizons in your SAP PM system.
Optional. The tool and every export work without this. No spam.
How to use it
Read the average daily usage from measurement documents on the measuring point (IK17 or the measuring point's document list). Enter the cycle length from your maintenance strategy or single-cycle plan, the early and late tolerances you have set as shift factors, and the call horizon percentage. The tool gives you the interval in days, earliest and latest windows, order lead time and annual call count.
- Use at least 30 days of usage data for a stable daily rate.
- Recompute when the production schedule changes materially.
- Check whether the plan is a strategy plan or single cycle plan.
How the numbers relate
Cycle days equals the cycle length divided by daily usage. Calls per year equals 365 divided by cycle days. Early and late windows apply the tolerance percentages to the cycle. In SAP, the call horizon is the percentage of the cycle after which the system creates the call, so the lead time is the cycle days times one minus the horizon. For example, a 2,000-hour cycle at 16 hours per day is 125 days, and an 80 percent horizon opens the order 25 days ahead.
Common mistakes
A frequent error is using the nameplate duty cycle rather than measured usage, which can be double the truth. Another is setting the call horizon to 100 percent, which means no lead time to plan materials. Tolerances that are too wide let work drift. Use IP30 to monitor due and overdue calls, and compare planned versus actual counter readings after the first few cycles.
- Counter reading frequency must be enough to reflect real usage.
- Keep a time-based fallback for plans where the counter is unreliable.
- Do not stack both a time and counter plan on the same task.
Frequently Asked Questions
What is a performance-based maintenance plan in SAP?
It schedules maintenance by counter readings, such as running hours or cycles, instead of calendar time. The system forecasts the next due date from the counter's annual estimate and reported readings.
What does the call horizon do?
The call horizon is the percentage of the cycle after which the system creates a call object such as an order. A lower horizon opens the order earlier and gives more time to plan and procure.
What are the shift factors?
They are tolerances. The early shift factor (minus) lets the call occur before the exact due point, and the late factor (plus) allows it to slip. Both are expressed as a percentage of the cycle.
Why compute days from a counter interval?
Budgets, crew plans and shutdown calendars are in calendar time. Converting the counter interval to days shows how often work will land and how many orders you will generate each year.
If you want a review of your maintenance plans and counter data for overdue or drifting schedules, Netray can build a read-only check on your SAP data.
Related Tools
SAP PM Maintenance Backlog Weeks Calculator
Turn the open work hours from your SAP PM order list into backlog in weeks, net burn rate and weeks to clear. Includes a crew-size sweep.
SAPSAP PM MTBF, MTTR and Availability Calculator
Feed in operating hours, failure count and breakdown hours from SAP PM notifications. Get MTBF, MTTR, inherent availability and reliability over a mission time.
SAPSAP PM Equipment Criticality Ranking Worksheet
Score each equipment item for consequence and likelihood, get a weighted criticality percentage, and use it to assign an ABC indicator in SAP PM.
SAPSAP PM Shutdown and Turnaround Readiness Checklist
Check scope freeze, order and network readiness, material availability, permits and contractor setup in SAP PM before a shutdown begins.
More SAP tools
See all- SAP PM Wrench Time Loss Calculator
- SAP PM Spare Parts Reorder Point and Safety Stock Calculator
- SAP PM Repair vs Replace Equipment Calculator
- SAP Movement Types Reference
- SAP Purchasing Document Types Reference
- SAP MIGO Goods Receipt Checklist
- SAP GR/IR Clearing Worksheet
- SAP Release Strategy Design Template
- SAP Source List Upload Template