PM / EAMadvanced

Scheduling Preventive Maintenance: Call Horizon, Shift Factors and Completion Requirement (Part 3)

Key takeaway

Control preventive-maintenance call timing with call horizon, shift factors/tolerances and completion requirement so late or early execution influences future dates according to maintenance policy.

Explanation

Scheduling parameters determine how the plan reacts to real execution.

Call horizon defines when a call object is generated relative to its planned date. A 0% or 100%-style interpretation depends on plan setting semantics in the target application, so planners should validate actual generated dates rather than rely on informal assumptions.

Shift factors and tolerance windows can move future planned dates when maintenance is completed early or late. This is useful where the next maintenance interval should begin from actual completion, but undesirable where statutory inspections must remain anchored to a fixed calendar.

Completion requirement can prevent the next call from being generated until the previous call is completed, avoiding overlapping maintenance orders when that is the policy.

The design choice is business-specific: fixed-date compliance plans differ from usage/condition maintenance. Always simulate early completion, late completion and missed calls.

Real project scenario

A legally required annual inspection was configured to shift future dates based on late completion. After several years the inspection date drifted materially. The plan was changed to preserve the statutory calendar while other maintenance plans retained shift logic.

Common mistakes

Applying shift factors to every plan.
Confusing generation date with planned maintenance date.
Using completion requirement where overlapping work is valid.
Never testing late-completion behavior.
Letting compliance dates drift unintentionally.

Best practices

Classify fixed-calendar versus rolling plans.
Simulate early/late completion.
Set call horizon for planning lead time.
Monitor overdue calls.
Review compliance plans separately.

Interview angle

Explain call horizon, shift/tolerance and completion requirement with examples of fixed-date versus rolling maintenance.

Practice this lesson

Quick check

1. Scenario — A legally required annual inspection was configured to shift future dates based on late completion. For the lesson "Scheduling Preventive Maintenance: Call Horizon, Shift Factors and Completion Requirement", which response shows the strongest architecture and production judgment?

2. When a maintenance call is confirmed earlier than its planned date, which parameter controls how strongly this early completion shifts the calculation of the next scheduled date?

3. When a maintenance call is confirmed within the defined tolerance (+/-) window around the planned date, how does this typically affect scheduling of the next cycle?

Interview questions

1. You are the senior consultant/architect responsible for Scheduling Preventive Maintenance: Call Horizon, Shift Factors and Completion Requirement. The project situation is: A legally required annual inspection was configured to shift future dates based on late completion. How would you assess the design, identify the highest-risk failure modes, and define the evidence required before approving it for production?

Answer it in your own words first, then compare.

2. Describe the role of the call horizon in the preventive maintenance scheduling process and how it should be set to support realistic workforce planning.

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.