- At this point, we've been pretty comprehensive
about defining RPA.
But you may have noticed, the type of automation
we've been discussing is described as capable
of taking over the tasks people have been doing.
What about assisting people, by handling specific tasks
in a larger process?
Well, this is also commonly referred to as RPA,
but there's an interesting twist.
For software to react quickly to a person
calling it into action, it most often
needs to reside on the person's desktop.
So as a result, this form of automation is becoming known
as robotic desktop automation, or RDA for short.
Our definition for RDA is as follows.
RDA is configured software that works in real time
with a human operator by presenting a predefined
set of information coming from different systems
to assist the operator with the completion
of operator-generated workflows or tasks.
If you refer back to your notes,
you'll notice the RDA definition shares many similarities
with the definition of RPA, but there were a few
key differences, so let's double click on them.
First, RDA works in realtime with a human operator.
So as mentioned, this is a tool that presents functionality
to a person who is in the act of performing their job.
Second, the definition says RDA delivers a result or service
to assist operator-generated workflows.
This is the key to this form of automation.
A person is an active participant
in the initiation of an RDA automation.
A person uses their judgment and passes work off
to this form of automation, if and when needed.
You'll remember from the RPA definition
that humans got involved there, too,
but it was only when exception management was required.
Humans are always involved in the RDA scenario.
An example of where you might see RDA used
is in a front office or call center environment.
We've all called to check on a credit card balance
or to book a flight with an airline.
RDA are at work making the agents we speak to more efficient
by handling rote tasks at the command of the agent,
so that they may tend to us and our needs
rather than be bogged down with chasing up data
or conducting discrete tasks
that automation can handle instead.
So remember, when you hear people discuss RPA,
there is a good chance that they're referring
to both RPA and RDA.
This distinction is useful to keep in mind.
Unless you're a stickler for absolute nomenclature accuracy,
the RPA term gets the job done,
but it's worthwhile to know the difference.