Before we get into this month's update, make sure you’re registered for the upcoming What’s New in SAP Asset Performance Management 2605 webcast, covering the top features from the releases 2603-2605. Alongside the blogs, it gives you live demos and the chance to ask your questions as you go. We’ll be answering them live via chat during the session. Register here.
See what changed (and why) in your recommendations – New Change Log
When recommendations evolve over time, one critical question often remains unanswered:
What changed, when, and who changed it?
The Challenge
Changes to recommendations used to be either overwritten or require manual duplication. This created a gap:
- No clear audit trail
- Limited transparency into decision-making
- Loss of historical context
For reliability engineers and maintenance planners, this made it difficult to track how and why recommendations have evolved, especially in environments where traceability is essential.
The Solution
We introduced a change log/timeline tab page for Recommendations in Manage Recommendations and Implement Recommendations applications.
All changes to recommendation business objects are automatically documented – independent of versioning – and made visible directly in the UI through a dedicated timeline view.
Behind the scenes, change logging is already captured at database level by the SAP Cloud Application Programming framework. This enhancement brings that data to life by exposing it to users in a clear, accessible way.
The Outcome
With the new change log/timeline:
- Every change is visible
- Every action is traceable
- Every decision has context
This enables:
- Greater transparency across teams
- Improved auditability and compliance
- Better-informed decision-making over time
For more information, refer to View and Export Change Logs .
Revising a Standalone Recommendation
Maintenance strategies don’t stay right forever. Assets change. Conditions change. Insights improve.
But if every change means overwriting the past, you lose the very context that explains why decisions were made.
And that’s a real issue:
Without history, there’s no true learning, no auditability, and no confidence in how your strategy evolves.
The Challenge
Today, updating a recommendation forces a compromise:
- Overwrite it and lose historical context
- Recreate it and break continuity
Over time, this leads to fragmented strategies and limited traceability especially across long asset lifecycles and changing teams.
The Solution
The new Revise button for Standalone Recommendations allows Reliability Engineers to:
- Create a new version of an implemented recommendation
- Carry forward all relevant data automatically
- Track changes between versions with full transparency
Instead of disconnected updates, recommendations now evolve as a continuous, structured history.
The Outcome
- End-to-end traceability of strategy changes
- Clear audit trail across versions
- Confidence to adapt without losing context
- Continuity over decades of asset operation
In a nutshell, change your strategy – without losing your story.
For more information, see Revising a Standalone Recommendation.
Consolidation of Recommendations
The Challenge
As recommendations grow across assets, assessments, and teams, a new challenge emerges:
too many similar recommendations, scattered across the system.
Even when they relate to the same issue, you're left:
- Reviewing and implementing them individually
- Duplicating effort across similar entries
- Losing efficiency in planning and execution
Over time, this doesn't just slow things down – it creates unnecessary complexity in your maintenance processes.
With the Consolidate Recommendations feature, you can now merge multiple standalone recommendations into a single, unified entry.
This allows you to bring together recommendations that share common characteristics – such as the same type, subtype, or failure data profile – and manage them as one.
Instead of handling multiple similar recommendations separately, you streamline them into a single action.
The Solution
When consolidating recommendations, the system ensures consistency by applying a few key rules:
- You can select up to 10 recommendations for consolidation
- Only recommendations in the following statuses can be selected:
- Created
- In Process
- Ready for Release
- In Review
- All selected recommendations must share:
- The same Type and Subtype
- The same Failure Data Profile
- The same Planning Plant and Maintenance Plant
- For assessment-based recommendations:
- The Source Assessment must be identical
These checks ensure that only truly comparable recommendations are merged – maintaining data integrity while reducing duplication.
The Outcome
By consolidating recommendations, you:
- Reduce duplication across similar actions
- Simplify implementation workflows
- Improve clarity for planners and engineers
- Focus effort where it matters most
Instead of managing many similar recommendations, you move forward with one clear, consolidated action. This is a small change with a big impact – helping you keep recommendation management lean, structured, and scalable.
Interacting with Embedded IoT Platform via Command Line Interface
SAP Asset Performance Management now supports the Command Line Interface of the Embedded IoT platform provider. As a Data Integration engineer, you can use this interface to efficiently work with the platform and automate tasks such as device management. This improves operational efficiency and enables scripted automation of routine tasks.
For more information, refer to Interacting with Embedded IoT Platform via Command Line Interface.
