- You'll remember
that I mentioned at the beginning of this course,
this is not a technical how-to.
Part of the reason is,
over time the RPA vendor landscape has expanded and evolved,
and it would be impossible to pick one,
or even a few tools to highlight here.
Plus, there are tool-specific trainings
and academies for this.
What I do wanna highlight,
is the depth and breadth
of the dynamic RPA-software industry.
The RPA landscape has grown considerably
in the last few years,
and there are now over 20 tools that you may come across,
and many more popping up every year.
I find this both fascinating and encouraging.
The vendor market is a vibrant space,
that's sure to play a significant role
in the future of work for decades.
Now, while I won't be making any tool recommendations,
there are a few key leaders at the moment.
I've provided with comprehensive list in the exercise files.
As the Everest Group PEAK Matrix highlights,
you'll most likely consider Automation Anywhere,
Blue Prism, NICE, Thoughtonomy, and UiPath.
Similar research by other analysts
also places these firms as leaders.
You may also consider other tools, including Kofax,
Kryon Systems, Pegasystems, and Softmotive.
Which software is right for you,
and your organization, however,
isn't as easy as just picking the top of the list.
Each software has different strengths.
There are several characteristics I use
when helping enterprises interpret the differences,
and relevant features of a particular tool.
The first is software architecture.
As our definition stated, RPA is preconfigured software.
This means that the way the tool is designed
influences what sort of tasks
it will be well-suited to handle.
For example, some vendors, like NICE, for instance,
specializes in assisted automation, in the sense that,
their software is built for simultaneous processing,
and listening for user-driven events.
This would be ideal for automating routine tasks,
like those handled by call-center employees.
On the other hand, if you end up needing a tool
that autonomously executes large-scale processes,
you may consider Blue Prism, or the Thoughtonomy platform.
And then, there are some tools that can handle
both assisted and unassisted solutions,
including Automation Anywhere, and UiPath.
I also wouldn't be surprised to see other tools
evolve this dual-state capability in the near future.
Software architecture also determines how well RPA tools
will integrate with certain applications.
For example, UiPath uses the .NET framework,
which makes configuration easier
for more experienced developers.
Thoughtonomy has a modular design,
that easily incorporates cognitive tools with RPA.
And most leading RPA tools now give credence
to an ecosystem approach,
supplementing their capabilities through close partnerships
with firms able to handle character recognition,
workflow management, machine learning, and more.
As with any software tool that's used frequently,
you want an RPA tool that provides a good user experience.
RPA interfaces vary quite a bit,
despite their functional similarities.
Take Blue Prism, for instance.
Its development interface is based on workflow diagrams,
similar to those you might see
in business-process management tools,
making it straightforward for non-programmers.
Then there's Automation Anywhere's interface.
Their workflow studio resembles a list,
where the steps are sequentially ordered.
UiPath's interface works a bit differently.
Its development involves a three-layer design,
in which the bottom layer contains specific action items,
the middle incorporates sequences of actions,
and business rules,
and the top layer controls the process flow
from start to end.
Notice, I don't suggest that one is better than another.
They just happen to be different,
and it will be up to you, perhaps with help,
to identify the right tool for your firm.
You will also wanna consider the available
configuration features that come with an RPA tool.
While most tools use design-based configuration,
some also come with a recorder feature,
that copies the user's steps to simplify configuration.
Other features to consider are version control,
collaborative tools, debugging assistance,
and credential vaults.
As you learn more about the nuances of RPA tools,
you'll come across even more considerations.
For instance, aside from the factors I just described,
subtleties in security, exception handling,
and license structure,
are important topics that you'll wanna have on your list.
One note of caution.
It is easy to get caught up in the numerous features
found in each RPA tool.
I urge you to take a different approach.
I've seen this tool fascination
lead too many firms down the wrong path.
I'll cover this more in a later chapter, but for now,
just know that I think you shouldn't
start your RPA journey by selecting the tool.
Instead, start with a plan.
Focus on the problem you're trying to solve,
or the digital operations vision set for your organization,
and let this vision inform your tool selection.