- SAP Managed Tags:
Preventive maintenance plans are created to ensure that various assets are maintained based on maintenance strategies and program. A meticulous planner may create large number of plans that generates work orders autonomously.
As organization become mature and they move from break fix mode to proactive mode of managing assets, planner needs to evolve maintenance strategies to more optimized inspection, preventive /corrective activities making some of the existing maintenance plans irrelevant in future. There are multiple use cases where planner needs to ensure that system does not propose new preventive activities for plans that would not be relevant in future, e.g. End of warranty related checks, planned improvement / modification project resulting in change of maintenance strategies etc.
Now with SAP EAM, you can effectively stop a preventive maintenance plan based on a date in future or counter value the asset may reach in future.
Fig:1 Time based, counter based plans with end date for scheduling and end counter for scheduling
Once the date or counter value is set, during scheduling run, system ensure that it does not create calls only for the events that is next to end date or end counter.
To get the visibility on how many days are left for a maintenance plans, IP15 and IP16 are enhanced to show remaining number of days or remaining number of counts.
Fig 2: Enhanced IP15 with additional information about remaining days or counters
This enhancement along with enhancements described below would help a maintenance planner to implement proactive management of preventive activities
To enable this feature, you may need to implement Note # 2712672. This note is valid from EhP7 and all the release of SAP S/4HANA. You will need First implement note 2721764 - (LOG_EAM_CI_13) if the Business Function does not exist yet in your system.
You will get further information about this new feature from help document link.
You will find more information in SAP Improvement Finder
Mark master blog as favorite to get information about further improvements that would be released.
As organization become mature and they move from break fix mode to proactive mode of managing assets, planner needs to evolve maintenance strategies to more optimized inspection, preventive /corrective activities making some of the existing maintenance plans irrelevant in future. There are multiple use cases where planner needs to ensure that system does not propose new preventive activities for plans that would not be relevant in future, e.g. End of warranty related checks, planned improvement / modification project resulting in change of maintenance strategies etc.
Now with SAP EAM, you can effectively stop a preventive maintenance plan based on a date in future or counter value the asset may reach in future.
Fig:1 Time based, counter based plans with end date for scheduling and end counter for scheduling
Once the date or counter value is set, during scheduling run, system ensure that it does not create calls only for the events that is next to end date or end counter.
To get the visibility on how many days are left for a maintenance plans, IP15 and IP16 are enhanced to show remaining number of days or remaining number of counts.
Fig 2: Enhanced IP15 with additional information about remaining days or counters
This enhancement along with enhancements described below would help a maintenance planner to implement proactive management of preventive activities
- Attaching Documents, Reason Codes and Cause Codes to Maintenance Item
- Classification of Maintenance Plan
To enable this feature, you may need to implement Note # 2712672. This note is valid from EhP7 and all the release of SAP S/4HANA. You will need First implement note 2721764 - (LOG_EAM_CI_13) if the Business Function does not exist yet in your system.
You will get further information about this new feature from help document link.
You will find more information in SAP Improvement Finder
Mark master blog as favorite to get information about further improvements that would be released.
11 Comments
