Example use cases

IBM® Cloud Pak for Business Automation as a Service provides a set of well-established capabilities that have reliable use cases.

Cloud Pak for Business Automation as a Service is a deployment option of IBM Cloud Pak® for Business Automation. You can design, build, and run automation applications and services on your cloud subscription by using pre-integrated automation technologies. For demos and videos, visit the IBM Cloud Pak for Business Automation web site External link opens a new window or tab.

The following examples provide implemented use cases of the Cloud Pak for Business Automation as a Service capabilities:

Example 1. Core business operations of loan companies

Core business is the primary area that a company focuses on with its business operations. Core business operations encompass the set of functions, processes, and capabilities that produce the most, or all of, the value created by a company.
Note: Mandatory functions such as human resources and accounting are considered non-core.
The following operations are common in any loan company, all of which can be automated:
  • New clients and processing.
  • Claims and processing.
  • Selling, including cross-sell and up-sell.
  • Business decisions to manage rapidly growing workloads.
Business problem

A loan company hardcoded its rules and policies into Java™ and Microsoft .NET programs, which make them difficult to modify. Internal business units or lines of business (LOB) want agility and flexibility to develop, test, and maintain their rules. So the company needs to look at more robust and flexible business rules capabilities. It deems that its loan process automation also needs policy management.

Business solution

By combining workflow and decisions capabilities, companies can automate their business processes across multiple LOBs and put millions of automated business rules in production. The solution can help any business refine and improve its processes. Transactions can be checked for risk of fraud. Suspected fraudulent transactions are routed for resolution.

Fraud detection
Companies that use these solutions show desirable outcomes:
  • 80 – 90% fewer loan applications reviewed manually.
  • Supports increased work volumes without adding staff.
  • Simplifies compliance reporting.

Example 2. Issue resolution

Businesses being able to automate how they resolve an issue is a problem the whole world over. Issues can range from a customer issue, such as a billing dispute or complaint, or it can be an internal issue such as a compliance or risk issue. Companies need to first detect that an issue occurred, and then take the necessary action when the issue is recognized to resolve it (or choose not to resolve it). Tasks that are part of the use case include:
  • Billing dispute.
  • Invoice exception.
  • Inventory exception.
  • Risk event.
  • Compliance issue.
  • New claim.
  • Service request.
  • Quality issue or complaint.
Business problem

Tapping into mountains of data to find insights about a business might feel like looking for a needle in a haystack. Searching through all of the data that businesses collect and identifying the key pieces with traditional methods is time-consuming and costly.

Business solution

With Cloud Pak for Business Automation as a Service capabilities, a company can unify and analyze data from multiple sources to a centralized repository, helping unearth crucial information that is hidden in the data. It integrates business intelligence and analytics applications with digital platforms, opening up more ways for companies to harness data.

Companies who use a combination of workflow, content, and decisions capabilities to resolve issues show desirable outcomes:
  • Faster decisions.
  • Reveals hidden insights.
  • Uses real-time intelligence.

Example 3. Employee onboarding

To establish employee benefits and payrolls, a benefits coordinator enters employee information and collects completed documents. Rules guide document requirements, benefits eligibility, and payroll settings.

Business problem

Onboarding of an employee is traditionally a stand-alone human task, which takes time from both the employee who joins the company and the employee who is tasked with the onboarding.

To establish an employee onboarding training plan, the hiring manager puts together requirements and a proposed plan. It is routed to the second-line manager and peers for feedback and approval. After it is approved, a checklist is routed to the appropriate team for implementation and monitoring of the training plan.

Business solution

Companies can build applications quickly to automate some, or all, of these tasks by using low-code application authoring and other capabilities in Cloud Pak for Business Automation as a Service.

The low-code Application Designer empowers business users to create business applications, and the capability toolkits and templates are created by developers for business users to assemble the applications.

Business users can also use Workstream Services to quickly and easily automate under-served "long tail" workstreams, such as requests, approvals, and collaborating with co-workers. It can reduce dependency on technical skills with tools to configure, save, and share productivity services. New automations can be deployed faster, and IT can govern the entire process with guardrails to prevent compliance missteps.

Example 4. Vendor onboarding

Business problem

Vendor onboarding requires numerous manual steps to collect information and vet a vendor. Steps include reviewing supplier's service track record to checking their sustainability credentials. It might involve evaluating their ownership and credit history and assessing their compliance with regulations and governance.

Business solution
Cloud Pak for Business Automation as a Service offers a range of capabilities that can be used to automate the manual steps of onboarding.
Workflow
New vendors can be vetted through workflows and collaboration. Smart user interfaces provide task interfaces, which allow participants to quickly and efficiently get their work done.
Decisions
Can be used to determine eligibility and risk.
Content
Can be used to curate and manage new vendor documents.
Insights
Can be used to get insight and visibility into the vendor onboarding process, from business stakeholders to participants.
Application Designer
Can be used to build applications that use the platform capabilities.