Maestro - Just go for it.
Use Cases and Deployment Scope
Our organization transitioned from the SAP APO to Kinaxis Maestro as our strategic Demand Planning Tool. As SAP APO support is ending by 2027, we were planning to migrate the Demand Planning use cases to the next-generation technology. Our global organization believes Maestro over SAP IBP is better due to factors like cost, user-friendliness, and performance.
Pros
- When we plan at the Sales BoM (Bill of Materials) level, the Demand Override option ensures that the base component-level demand plan is also derived.
- Sales History is automatically adjusted when outlier correction is in progress. There are options to exclude the particular Sales Orders partially or fully.
- Statistical forecast available as a basis for project adjustments, and project demand added to the statistical forecast and carried over to future planning cycles.
Cons
- Our ERP environment is from SAP. Integrating the data with SAP is not straightforward. As the Demand Planning requires master data integration from the ERP systems.
- Structured tables are needed to export the data from Maestro to Azure Data Lake. We are using Azure Data Lake as middleware to connect Maestro with SAP. Every time, the full data needs to be extracted.
- Custom and complex logics handling should be better in Maestro.
Return on Investment
- Compared to the previous tools, the demand forecast accuracy is very high. This ensures optimized safety stock levels.
- Reacting to the market fluctuations and supply disruptions are good.
- There is a lot of training required for the planners, as all of them were previously using different tool/environment.
Usability
Alternatives Considered
SAP Integrated Business Planning
Other Software Used
IBM Planning Analytics, SAP Analytics Cloud

