Vice President - Digital Automation Services at Techvista Systems
Real User
Top 20
2024-01-04T14:03:00Z
Jan 4, 2024
There are multiple use cases but one notable aspect of IBM Cloud Pak for Automation is its licensing structure. They have consolidated all the products into one pack. Once you acquire the license, you can use each component based on your specific requirements. For instance, if you need to develop a solution, like an approval process for leave requests, the pack allows you to handle various aspects. You can connect to integration layers, design workflows, obtain user approvals, and initiate RPA services. There are numerous use cases, such as tracking requests related to DevOps configurations. You can assign requests to multiple teams, monitor milestones, and ensure compliance with SLAs. IBM Cloud Pak for Automation facilitates tracking process performance and meeting specified timeframes.
Business Architect at a comms service provider with 5,001-10,000 employees
Real User
Top 20
2022-09-07T19:57:27Z
Sep 7, 2022
We got into the migration because CP4BA is an upgraded platform that has FileNet, Datacap, and ODM. It has all of the workflow content management and automation. Applications that used to work independently now work on a new integrated cloud-based containerized platform. We have been working on implementing that probably for the last year. Our use cases are related to end-to-end workflow content. For example, in group life health, we process the claims, and we use the content and workflow engines to be able to build in some auto-adjudication rules. They have a decision manager application. What we're looking to achieve is upgraded capabilities when it comes to cloud-enabling our infrastructure to be able to do end-to-end workflow, also including the end customer. So, by using the access and identity management components of the platform, we will be able to build portals and send secured email links out to the customer to improve our ability to digitally process claims and workflows. We are upgrading existing applications and developing the capacity to leverage the low-code, no-code features of the platform so that we get more of an agile development cadence going with business analysts, systems analysts, developers, and architects. Once we get the platform in a steady state, there are a number of features that we would like to use that we currently can't use, such as having secured email or having a workflow that also includes digitally posting the information in a portal. We would have more tools in our tool set and we won't have to just use Salesforce and all of those licensing implications.
What is process automation? Process automation is the automation of complex business processes. The idea behind process automation is to automate processes, centralize information, and reduce errors by removing human input.
There are multiple use cases but one notable aspect of IBM Cloud Pak for Automation is its licensing structure. They have consolidated all the products into one pack. Once you acquire the license, you can use each component based on your specific requirements. For instance, if you need to develop a solution, like an approval process for leave requests, the pack allows you to handle various aspects. You can connect to integration layers, design workflows, obtain user approvals, and initiate RPA services. There are numerous use cases, such as tracking requests related to DevOps configurations. You can assign requests to multiple teams, monitor milestones, and ensure compliance with SLAs. IBM Cloud Pak for Automation facilitates tracking process performance and meeting specified timeframes.
We got into the migration because CP4BA is an upgraded platform that has FileNet, Datacap, and ODM. It has all of the workflow content management and automation. Applications that used to work independently now work on a new integrated cloud-based containerized platform. We have been working on implementing that probably for the last year. Our use cases are related to end-to-end workflow content. For example, in group life health, we process the claims, and we use the content and workflow engines to be able to build in some auto-adjudication rules. They have a decision manager application. What we're looking to achieve is upgraded capabilities when it comes to cloud-enabling our infrastructure to be able to do end-to-end workflow, also including the end customer. So, by using the access and identity management components of the platform, we will be able to build portals and send secured email links out to the customer to improve our ability to digitally process claims and workflows. We are upgrading existing applications and developing the capacity to leverage the low-code, no-code features of the platform so that we get more of an agile development cadence going with business analysts, systems analysts, developers, and architects. Once we get the platform in a steady state, there are a number of features that we would like to use that we currently can't use, such as having secured email or having a workflow that also includes digitally posting the information in a portal. We would have more tools in our tool set and we won't have to just use Salesforce and all of those licensing implications.