ACI Worldwide Global Payments Hub vs IBM Cloud Pak for Automation comparison

"This solution has a robust cloud model, which it supports, and the pricing is also very competitive in terms of pay-per-use. Right now, it seems like ACI is winning a bit in terms of its pricing model."

"I believe two significant features of IBM Cloud Pak for Automation are the focus on SLA management and the capability to handle parallel instances effectively. Parallel instances, for instance, are valuable when dealing with a large number of users, enabling tasks to be performed concurrently for efficient system operation. The SLA aspect is crucial for tracking and ensuring timely completion of tasks. Additionally, the cloud compatibility of IBM BAW allows for seamless migration from on-premises to the cloud. This version also includes a business rule management system for storing and managing business rules effectively."

"What this product allows us to do is to move from on-prem instances where we are running independent instances of FileNet, Datacap, and ODM. It allows us to leverage container-based resiliency and availability modeling so that we have some visibility across the CP4BA ecosystem. We're now migrating all of our data to be in the Cloud Object Storage, and we can now use some of the features of Azure in terms of how we store and retrieve content for our members and our providers."

"The initial setup of medium complexity. So, there is room for improvement to make it better."

"I believe there is room for improvement in the user interface, particularly in the Process Portal that customers use to view and manage their tasks. The UI of the Process Portal needs enhancement. Additionally, in the next release, I would like to see improved compatibility with Angular, allowing for direct integration with front-end systems. It would be beneficial to have built-in GUI features based on Angular within the system, rather than developing separate applications externally. This, in turn, would provide a more seamless and enhanced front-end experience."

"One of the challenges we're having is finding vendors who have experience in developing on the cloud. We can find developers on the old platform, but it is leading-edge technology. So, we are having some challenges, and IBM is assisting us to find vendor partners. To be able to leverage all the capabilities of the new platform, we have to upgrade our existing ecosystem of FileNet applications. Upgrading to the new platform while trying to modernize is always challenging because it is like you have a moving target."

"I would rate the pricing a two out of ten, where one is cheap, and ten is expensive."

"Its cost is almost the same or comparable to what we pay with FileNet, but I'm not sure what we pay a year. A good part of CP4BA is the CPU-based licensing model. When we're dealing with 50,000 dentists, for example, if we were to use Salesforce, we would be hit with the licensing of 50,000 dentists, whereas when we build out in CP4BA, it is just based on our CPU usage, not on individual licenses."

"IBM Cloud Pak for Automation is relatively expensive, especially considering it is designed for long-living processes, not for normal automation needs. On a scale of one to ten, I would rate the pricing at around 9. There are no additional costs beyond the standard licensing fees, but IBM has multiple pricing models that make it expensive in its own way. Different plans are available, but overall, the experience suggests it is a costly solution."