Scheduling maintenance plans means to continuously monitor all maintenance plans performing the following tasks:
- Starting newly created maintenance plans
- Checking existing plan dates if they are due
- Recalculating existing plan dates if scheduling parameters have changed
- Creating call objects for due plan dates (f.ex. creating a maintenance order)
- Shift subsequent plan dates in case of delayed or early completion of the actual plan date
For the monitoring you usually set up a background job - executing a specific ABAP report.
- Deactivate
- You can use this function to block maintenance plans for a certain period of time. The system then sets the status INAK in the maintenance plan. This blocks scheduling, and any planned dates still waiting are displayed as blocked. It isn't possible to make calls in this status. You can deactivate a maintenance plan in the Change and Scheduling modes. You can reactivate blocked maintenance plans at any time.
Cycle Start and Planned Date
When you create a single cycle plan, the cycle unit is assigned. The cycle unit identifies the interval period for the planned dates. Orders are generated based on the planned dates and the call horizon that is identified in the plan.
The call date (the date the order is generated) can be prior to the planned date to allow for a certain lead time (for example, material or external service procurement).
The cycle start defines the date from which the calculation of the planned dates should begin.
Call Horizon
Note
Specifying the call horizon isn't sufficient for the order to be generated; the maintenance plan must also be scheduled for the order to be generated.Upon activating Business Function LOG_EAM_CI_6 ,the call horizon can be specified in days.
You can define a percentage, a number of calendar days, or a number of working days for the call horizon.
If you specify %, the system calculates the times for the maintenance call based on this percentage of the maintenance cycle.
If you specify days (DAY), the system generates the maintenance call objects a certain number of days before the planned date. When scheduling the maintenance call, the system doesn't take weekends, holidays, or your company's vacation shutdowns into account.
If you specify factory calendar days (FKT), the system generates the maintenance call objects a certain number of working days before the planned date. The system bases scheduling on the assigned factory calendar and takes weekends, holidays, and your company's vacation shutdowns into account.
If you've saved a factory calendar in the header data of the maintenance plan, the system uses this calendar for scheduling. If no factory calendar has been entered at header level, the system evaluates the factory calendar of the planning plants at item level. The system considers all the maintenance plan items and defines the earliest possible working day as the maintenance date.
Call Horizon
Total maintenance cycle is f.ex. 3 months = 90 days. If you define a call horizon of 0%, 80% or 100%, the system creates the maintenance order after the number of days shown in the following table:
| Percentage | Days |
|---|---|
| 0% | Immediate call |
| 80% | Call after 72 days (= 80% of 90 days) |
| 100% | The call is made when the planned date is reached |
Note
To use call horizon in days functionality, Business Function LOG_EAM_CI_6 must be activated.
Scheduling Period
Shift Factors and Completion Requirement
The shift factor enables you to react to an early or late completion of a call object. If the shift factor for the late completion is 100%, then the difference (the positive actual variance) between plan date and completion date is added in full to the next plan date.
If completion requirement is activated, the system only generates the next call object once the previous call object has been completed.
When the completion requirement is activated, the next order is only created once the previous order has been technically completed. When the order has been completed, two different times can be specified.
Order Completion Times
Reference time for the maintenance order (relevant for the order history)
Completion date for calling the maintenance plan (relevant for further scheduling in the maintenance plan)
If the call object is a notification, the next notification isn't created until the preceding notification has been completed.
If the call object is a service entry sheet, the next service entry sheet isn't created until the preceding service entry sheet has been accepted.