RPA automates the tasks other IT projects can’t reach. Why? Consider the pyramid below which shows RPA use cases increasing as available IT resources decrease:
Why do use cases increase as the available IT resources go down? It's simply down to cost. Let us examine each section of the pyramid:
Top Tier - Many IT Resources Available
Well-resourced automation projects are likely to have a team of experienced developers who know how to build APIs and how to orchestrate these APIs into a process flow. Let’s face it, these developers can build complex systems with their eyes closed and don’t consider RPA as a technology of choice unless they have a particularly difficult system for which they can’t build an API.
Middle Tier - Limited IT Resources Available
Mid-budget projects may not have the resources to build new APIs or have a large software budget. Instead, they build RPA bots to access their legacy system and turn that two-year project into six months. It may not be as slick, but it works, and it delivers on time and on budget.
Bottom Tier- Very limited/No IT Resources Available
Most IT vendors shy away from these projects, but not RPA. RPA is designed to automate mundane and seemingly trivial tasks on a very low budget. For example, filling in an invoice. An RPA bot could take a day or two to write and yet could save hundreds of days per annum doing tedious work.
The lower your IT resources, the more attractive becomes RPA. With a small IT team working with business users, RPA bots can be built to automate tasks that other IT projects cannot reach.
For more information on IBM RPA and its many uses, see my introductory videos below: