- SAP Managed Tags:
I. Introduction
In this blog post I will explain Maintenance Plan Scheduling Parameters, by using a real-case scenario, followed by diagrams, which will shed lots of light on every single setting. For this purpose, we will use Single cycle time-based Maintenance Plan, which is part of Preventive Maintenance in SAP Asset Management S/4HANA and older system versions as well.
In this post we purely focus only on scheduling parameters.
II. Business Case
Let's assume, we have the following Business Case/Requirements from one of our Clients:
'In our facility based in Texas we have Technical Assets, which require regular tasks to be performed by our Technician every 1 Month. We want to see this work in our SAP system to document all the insights, time spent for specific activities, used spare parts and more.'
'We want to automatically generate Maintenance Orders in the system, they should be there at least 5 days before maintenance day of each month. The planned dates should be always the same day of each month (1st of Feb, 1st of March, 1st of April and so on) - it means first order should be already visible in the system at the end of January.'
This Maintenance Program should start on 1st of Feb 2024 and should be valid 2 years.
III. Maintenance Plan Scheduling Parameters
Below we see all the scheduling parameters, which are available in SAP system for Maintenance Plans and can be defined during its creation (in this example for single cycle time-based plan). I've assigned numbers to each of them. These numbers correspond the below section in this blog post. We will now go through each of them + with keeping in mind the Business Case from the Texas Client.
1. Cycle & offset
Actually, this is not a scheduling parameter, but it makes sense to start from it, as it defines the interval, at which the tasks should be performed. For single-cycle plan we set it up directly in the Maintenance Plan, for strategy-based plans we do it yeah, via Maintenance Strategies.
“In our facility based in Texas we have Technical Assets, which require regular tasks to be performed by our Technician every 1 Month”
Texas Facility Example:
Cycle/Unit: 1 MON
Effect: Every 1 month a Maintenance Order will be generated in the system
2. 3. Shift Factors
These parameters control what percentage of the late & early completion date is to be transferred to the next planned date. The values are always entered in % and in practice it is either 0% or 100%.
What does it mean? Let’s take the Texas Facility as an example.
Texas Facility Example:
Planned date of maintenance: 01 Feb 2024
Actual completion of maintenance: 05 Feb 2024
1) Shift factor late completion: 100%
Effect: Next planned maintenance date instead of 01 March 2024 -> changed to 05 March 2024.
2) Shift factor late completion: 0%
Effect: Next planned maintenance date 01 March 2024.
The same logic applies to early completion. Moreover, tolerances can be specified, after what amount of days the shift should take place.
4. 5. Cycle Modification Factor & Factory Calendar
You can change the cycle times of a maintenance strategy by entering a value greater/less than 1 individually for each maintenance plan.
In practice, you will just stick to 1, but be aware of such option as well.
Factory Calendar parameter is only relevant for Scheduling indicator Time - factory calendar.
For single-cycle plans - it is derived automatically from the customizing, for strategy plans - it comes directly from strategy settings, and of course - can be changed.
Texas Facility Example:
Factory Calendar: US
Effect: Depends on the other parameters. Check below the ‘Scheduling indicator’ to understand, why calendar does not matter actually in our example.
6. Call Horizon
We enter it in % or number of days. It specifies, when an order should be created in the system for a calculated maintenance date. In other words - how much time should pass between the current and future order, before it is created in the system. By created we mean - just available in the system, the planned dates are something different.
In practice you will use 3 values:
- 0 % - next maintenance order will be immediately created once the previous one is TECO’ed
- 75% - next maintenance order will be created once 75% of cycle time elapsed
- 100% - next maintenance order will be created exactly on the planned date
‘(...) automatically generate Maintenance Orders in the system, they should be there at least 5 days before maintenance day of each month.’
Texas Facility example:
Cycle/Unit: 1 MON (so, about 30 days)
Planned date of an order: 1st Feb 2024
Order finished and technically closed (TECO) on: 1st Feb 2024
Call horizon: 0%
Effect: Next Planned order (with planned date 1st March 2024) available in the system immediately, on 1st Feb 2024.
Call horizon: 75% (in other words 75% of 1 month = around 23 days)
Effect: Next Planned order (with planned date 1st March 2024) available in the system on 24th Feb 2024.
Call horizon: 100%
Effect: Next planned order (with planned date 1st March 2024) available in the system on 1st March 2024.
7. Scheduling Period
Specifies the actual length of time over which scheduling will take place. Once set, it builds a preview of your pending maintenance dates. Entering 5 years means, your maintenance plan lasts 5 years and you will see all the planned dates in the preview.
Texas facility example:
Scheduling period: 365 days
Effect: In the maintenance calls preview, you will see planned dates for the whole year.
But hold a sec - it doesn’t mean you will generate maintenance orders for the whole year.
It is a preview - you will see only dates, which can of course change, for example because of late completion etc.
8. Completion Requirement
If you want the system to generate subsequent order only when the previous one has been technically completed - activate it.
Texas facility example:
Planned date of current order: 1st Feb 2024
Order finished and technically closed (TECO) on: 28 Feb 2024
Completion requirement: activated
Effect: The next order will be created in the system (with planned date 1st March 2024) just on 28 Feb 2024, not earlier.
9. Scheduling indicator
Actually, I should start the explanation with this parameter, since I find It the most important.
It defines the planned dates of your maintenance plan.
We have 3 options
- Time (fixed calculation, a month lasts always 30 days),
- Time - Factory Calendar (like the previous one + only the factory calendar days are counted),
- Time - Key date (effective days of a month).
‘(…) The planned dates should be always the same day of each month (1st of Feb, 1st of March, 1st of April and so on)’
Texas facility example:
Cycle/Unit: 1 MON
Cycle start: 1st Feb 2024
Scheduling indicator: Time - key date
Effect: Planned date of the order 1st of March 2024
Scheduling indicator: Time
Effect: Planned date of the order 30 Feb 2024.
Scheduling indicator: Time - Factory Calendar (US)
Effect: Planned date of the order 9 March 2024.
10. Start of Cycle
As the parameter already says by itself. In reality, we consider this as a date of the last performed maintenance for this asset or group of assets.
This day will form basis for scheduling of your fist preventive orders and the next ones.
‘This Maintenance Program should start on 1st of Feb 2024 (…)’
Texas facility example:
Start of cycle: 1st Jan 2024
Effect: During scheduling, the first scheduled order will be with planned date 1st Feb 2024.
IV. Summary
There is no doubt, there are many scheduling parameters in Maintenance Plan settings, which are confusing for many users and even SAP Consultants.
With proper, step by step understanding of each of the parameters - this won’t be the case anymore.
In this post we went through all of them, with diagrams and what’s even more important - with a proper Business Case.
3 Comments
