Item: SAP PPM
Rating: 8
Author: Mohamed Adil Shaikh

Overall Satisfaction with SAP PPM

Use Cases and Deployment Scope

It's a great tool for Maintenance, Asset Management. Optimising Maintenance it's a go to tool for Asset Management and Maintenance.
Here we are handling Maintenance, cutting Maintenance cost, optimizing Maintenance and basically finding out the bottle necks in Maintenance. Understanding MTBR and MRBF finding out whether proper maintenance is done.

Pros and Cons

Pros

Asset Management
Plan Scheduling
Costing of Maintenance

Cons

Major issue while using SAP PPM is it's UI.
Things are way too complicated and difficult to understand.

Return on Investment

It's basically solve the 10000 dollars of Maintenance cost by properly utilising the tools and info.
ROI for this tools is always greater than 3

Usability

It's very detailed oriented but the UI is difficult to use.
It requires proper training and good people to handle day to day activities.
The functionality that SAP provides like, Asset downtime, cost optimization, settling of cost at work order level and the moving it to related cost centre, this defines the actual CMMS system which is very useful.

Alternatives Considered

Oracle JD Edwards EnterpriseOne

Oracle JDE is a basic tools which we can use where implementation cost is not so high and so is the process. It's gives what required and a bit less complicated. Whereas SAP goes in depth of the Maintenance and provide you all the required functionality along with some additional insights

Key Insights

Do you think SAP PPM delivers good value for the price?

Yes

Are you happy with SAP PPM's feature set?

Yes

Did SAP PPM live up to sales and marketing promises?

Yes

Did implementation of SAP PPM go as expected?

Yes

Would you buy SAP PPM again?

Yes

Other Software Used

Oracle JD Edwards EnterpriseOne, IBM Maximo Application Suite, Planon Universe

Likelihood to Recommend

It's has all the functionality a proper CMMS tools required, it's act as a blueprint of what exactly all CMMS tools wants. All the features, costing, optimization, asset management all under one bucket. It's less appropriate for people who required simple UI, only some basic system or people with low budget. Because the cost for implementation is very high.

Comments

Please log in to join the conversation