Use ACE as the standard integration framework

I would like to propose that IBM formally elevate IBM App Connect Enterprise (ACE) as the standard and primary integration platform for the Maximo Application Suite (MAS). While ACE is already bundled under restricted use entitlement within MAS (as per license terms), there is very limited enablement or documentation to guide customers and partners in leveraging this powerful tool. By positioning ACE as the go-to integration engine, IBM can significantly simplify how MAS connects with external systems, particularly in hybrid environments.

A key opportunity lies in re-architecting the existing MAS-SAP integration framework to use ACE instead of relying solely on SAP PI/PO or CPI. The current dependency on SAP middleware often creates a bottleneck — requiring specialized skills, additional licenses, and cross-team coordination. By building MAS-SAP integration patterns directly in ACE — through its visual, no-code interface — customers and partners could configure, deploy, and manage integrations more efficiently and autonomously, in line with the cloud-native and OpenShift-native direction of MAS.

To enable this, IBM should invest in creating tight, documented integration patterns between MAS and ACE, including a standard deployment of ACE components alongside MAS on OpenShift, reference flows for common use cases (e.g., MAS ↔ SAP, MAS ↔ ESRI, MAS ↔ Salesforce), and guidance on event-based integration using Maximo’s REST, webhook, and queue capabilities. This would empower MAS solution teams with a more agile, scalable, and maintainable integration option that fully utilizes what’s already in the MAS entitlement. Thank you for considering this improvement for the MAS and automation ecosystem.

I posted a brief discussion about MAS - ACE in the Maximo user community page here:
https://community.ibm.com/community/user/blogs/seno-hardijanto/2025/04/11/mas-appconnect