In SAP EAM / PM, a maintenance plan defines recurring maintenance or inspection work for technical objects. It combines maintenance items with scheduling information such as cycles, strategies, counters and call parameters. When scheduled, the plan calculates due dates and can generate call objects such as maintenance orders or maintenance requests according to its category.
Plan, item and task list play different roles
The maintenance plan carries the scheduling logic. A maintenance item identifies what technical object or group of objects is to be maintained and contains planning data. A task list can be assigned to describe the work steps, required parts, tools and planned duration.
Common plan types
SAP documentation distinguishes single-cycle plans, strategy plans and multiple-counter plans. Single-cycle plans use one time- or performance-based cycle. Strategy plans use maintenance packages from a maintenance strategy. Multiple-counter plans can use more than one counter condition.
Scheduling decides when work becomes due
Scheduling parameters control how due dates and calls are calculated. For performance-based plans, counter readings can determine when work is due. The maintenance-plan category determines what kind of call object is created when a maintenance call becomes due.
Consultant checks
Confirm plan category, maintenance item, reference object, task-list assignment, cycle or strategy, counter logic, call horizon, scheduling period, shift factors and how completion history affects future calls. Test both the first call and subsequent calls.
Continue with Maintenance Task Lists, Work Centers in Maintenance, Equipment Master, and the SAP EAM / PM hub.