Type

INPUT TYPES

PROCESS STABILITY

APPLICATIONS STABILITY

OVERALL RESULT

BENEFITS
BENEFITS

PROCESS COMPLEXITY

INPUT DATA

Ease Of Implementation
Benefit/Suitability

Badwidth Freed (man

hours/year)
Error Reduction
Average Handling Time
Reduction (AHT Reduction)
Effort to Implement (man
hours)
Process Name:
Business Unit:
Main Function:

SME Responsible:
Process Owner:
RPA Business Analyst:

Question

How do the majority of your data inputs look like?

How will your process change in the next 6 months?

How will your applications change in the next 6 months?

How many FTEs are currently needed to perform the process?

What is the frequency of the process?
What is the volume of transactions/frequency (number
of times the process is ran/selected frequency)?
What is the average time it takes for the process to
be ran once (average handling time/transaction)?
What is the average number of human errors?
How would you characterize the peaks of the process?
How many steps does the process have?
How difficult are the decisions that you must take to complete the
process?
What is the average number of cases where you are unable to
complete the entire process? (Either because you require input form
a different person or because you end up in a situation that is not
covered by a clear rule)
What is the number of applications that you use for the
process?
Are any of the applications accessed via VDI?
What % of your input data is digital?
Is any of your digital input scanned?

What % of your input data is structured?

Invoice Processing
GBS - EMEA
Finance & Accounting

Charlie Lee
Satoshi Nakamoto
Nick Carver

Explanation

Digital: any data that can be stored on a machine [server, laptop, IOT devices]
Structured data: has a predictable format, exists in fixed fields (e.g. an xls cell or a field in a form)
and is easily detectable via search algorithms. Think about your structured data as: excels, tables
with fixed structure, databases where you can easily extract your information through a search
function.
Unstructured data: may have its own internal structure, but this is not highly predictable.
Examples: web logs, multimedia content, customer service interactions and social media data.

Think about changes of the following type:

- legislative changes that are upcoming and could change the rules/logic of the process.
- organizational changes such as re-distributing bits of the processes between different
roles/departments;
- industry shifts that could change the business model and hence the rules of the process;
Think about not only applications but also interfaces, menus in apps and reports.

Optional field
E.g. If the process happens weekly please then we need to know the volume
that happens on average during a week.
Please quantify the average handling time in minutes e.g. if 4 hours then
insert 240

Structured data: has a predictable format, exists in fixed fields (e.g. an xls cell or
a field in a form) and is easily detectable via search algorithms. Think about
your structured data as: excels, tables with fixed structure, databases where
you can easily extract your information through a search function.
Examples: if your inputs consist of 5 excel files/or ERP reports then 100% of
your data is structured, whereas if your input consists of 4 excel files/ERP
reports and 1 e-mail text then 80% of your data is structured.
Answers Result Computation

Digital and Structured Feasible

Some change 0.4

Medium Change 0.8

0.6

10
Daily
960

5
10%
The process does not have N/A
peaks
10-15 steps 0.2
The process involves complex 0.7
decisions

5%

4-5 aplications 0.6

No 1
100%
Yes 1.2

>= 80% 0

42% Medium Effort

88% High Benefit

18,304
88%
59%

560
ELIMINATORY QUESTIONS

POSTPONEMENT QUESTIONS
SUITABILITY/BENEFIT QUESTIONS

EASE OF IMPLEMENTATION
LIMINATORY QUESTIONS

Rule Based vs Ad-hoc/Judgemental

Possible Answers
Exclusively Rule Based
Mostly Rule Based
Somelevel of subjectivity involved
Mostly subjective
Exclusively Subjective

Type of Input
Possible Answers
Not digital and Unstructured
Non Digital and Structured
Digital and Unstructured
Digital and Structured

OSTPONEMENT QUESTIONS

Process Stability
Possible Answers
No change expected
Very Small Change
Some change
Medium Change
Significant Change

Applications Stability
Possible Answers
No change expected
Very Small Change
 Some change
Medium Change
Significant Change

UITABILITY/BENEFIT QUESTIONS

Frequency of the Process

Possible Answers
Daily
Weekly
Bi-weekly
Monthly
Quarterly
Annualy

Process Peaks
Possible Answers
Regular (e.g. month closing), lasting for several days or weeks in a row and increasing the
utilization of the team capacity by > 20%
Rare but predictable event (e.g. winter holidays/ yearly closing), lasting for the several days or
weeks in a row and increasing the utilization of the team capacity by > 20%
Rare event, hard to predict, of short duration
The process does not have peaks

ASE OF IMPLEMENTATION

Number of Steps - complexity proxy 1

Possible Answers
<=10 steps
10-15 steps
15-25 steps
25-40 steps
>40 steps
 Difficulty of decisions
Possible Answers
The process is linear - there are no decisions to be taken
The process involves simple decisions (yes/no type)
The process involves complex decisions

Number of Applications
Possible Answers
1 application
2-3 applications
4-5 aplications
> 5 applications

Thin Client?
Possible Answers
Yes
No

OCR?
Possible Answers
Yes
No

Structured Data vs Un-Structured

Possible Answers
>= 80%
60%-80%
40%-60%
<40%
mental
Scoring
Feasible
Feasible
Feasible
Low Feasibility
Low Feasibility

Scoring
Low Feasibility
Digitize first
Feasible
Feasible

Scoring
0
0.2
0.4
0.8
Postpone

Scoring
0
0.2
 0.4
0.8
Postpone

s
Scoring
These are control questions that are 260 1 FTE = 260 days
52
not scored. The frequency x AHT x 26
12
Volume/frequency will be used to
4
estimat the number of FTEs 1

Scoring
1

3
N/A

proxy 1
Scoring
0.1
0.2
0.4
0.6
1
 Scoring
0.1
0.2
0.7

Scoring
0.1
0.3
0.6
1

Scoring
1.6
1

Scoring
1.2
1

ured
Scoring
0
0.4
0.7
1
Average Duration (in months)
Average Team Composition for Enablement
 Low Effort Medium Effort High Effort
0.8 1 2
RPA Project Manager 0.1 0.15 0.2
RPA Change Manager 0.05 0.1 0.2
RPA Program Manager 0.05 0.05 0.1
RPA Business Analyst 0.2 0.4 0.6
RPA Infrastructure Engineer 0.1 0.2 0.3
RPA Solution Architect 0.2 0.4 0.6
RPA Developer 1 2 2.5
RPA Technical Support Manager 0.05 0.1 0.15
RPA Operations Support 0.05 0.1 0.15
TOTAL TEAM 1.44 3.5 9.6
230 560 1536
Macro Process Process Name Sub-Process Activity

Invoice to Invoice
Source to Pay Payment Processing
 FEASIBILITY
DECISION TYPE INPUT TYPE

Are the decisions rule-based Score How do the majority of your Score
or subjective/strategic? data inputs look like?

Mostly Rule Based Feasible Digital and Structured Feasible

 AUT
FEASIBILITY
PROCESS STABILITY APPLICATIONS STABILITY

How will your process change in How will your process change in
Score Score
the next 6 months? the next 6 months?

Some change 0.4 Medium Change 0.8

 AUTOMATION POTENTIAL

FEASIBILITY FEASIBILITY
SCORE PROCESS VOLUMETRY

What is the volume of

What is the frequency of transactions/frequency
the process? (number of times the process is
ran/selected frequency)?

Feasible 0.6 Daily 960

Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
Feasible
 SUITABILITY
SS VOLUMETRY ERRORS

What is the average time

it takes for the process What is the average number of
to be ran once (average Equivalent FTEs
human errors?
handling time/transaction)? (in
minutes)

5 10 10%
 PROCESS PEAKS

How would you characterize the peaks of the process? Score

Regular (e.g. month closing), lasting for several days or weeks in a 1

row and increasing the utilization of the team capacity by > 20%
 PROCESS DETAILS
NUMBER OF STEPS DECISION TYPE

How difficult are the

How many steps does SCORE decisions that you must SCORE
the process have? take to complete the
process?

The process involves complex

10-15 steps 0.2 0.7
decisions
 PROCESS COMPLEXITY
PROCESS DETAILS
EXCEPTIONS NUMBER OF APPLICATIONS

What is the average

number of cases where you
are unable to complete the
entire process? (Either What is the number of
because you require input applications that you SCORE
form a different person or use for the process?
because you end up in a
situation that is not
covered by a clear rule)

5% 4-5 aplications 0.6

PROCESS COMPLEXITY
INPUT DATA
THIN CLIENT DIGITAL INPUT

Are any of the applications

SCORE What % of your input
accessed via Citrix/VDI? data is digital?

No 1 100%
 INPUT DATA
SCANNED INPUT STRUCTURED DATA %

Is any of your digital input SCORE What % of your input data SCORE
scanned? is structured?

Yes 1.2 >= 80% 0

28%

ESTIMATED BENEFIT
AUTOMATION
POTENTIAL Man Hours Freed Est. Error Reduction Est. AHT Reduction

Estimated Bandwidth
% Automation Freed expressed as Expressed as % Expressed as %
man hours/year

88% 18,304 88% 59%

FIT ESTIMATED IMPLEMENTATION EFFORT

Peak Priority Man Hours spent

From 3= lowest to 1 = Expressed as man hours

highest

1 560
NTATION EFFORT

IMPLEMENTATION

% effort

42%