Before embarking on session 1 of the Business Analyst Series, please remember you are required to complete the prerequisite training. For training links please go to the 👉 series page 👈 Business Analyst Series 2023 - Week 1, Session 1 Topics Covered: RPA BA - Roles & Responsibilities, Skillset & Challenges Traditional Business Analysis Methodology Walkthrough of RPA BA Documents Q&A Please see below the week 1 mandatory UiPath Academy learning assignment (to be completed by Sunday EoD): 1. Automation Business Analyst Fundamentals (3hrs) 2. Introduction to UiPath Business Automation (35 m)

1. Business Analyst
Series 2023
Introduction Slides
By UiPath Community &
The Next Innings

2. 2
About today’s meetings
Enjoy the next 90 minutes packed with expert-led content from our instructors.
Get answers to your questions and challenges. Please use the chat box for Qs during the
presentation. Live Q&A at end of the session.
Please keep yourself on mute during the session unless you are asking a question.
You are encouraged to network and share your Linkedin/Twitter in chat.
If you have questions outside of these sessions, please leverage forum.uipath.com
We will be recording this session, and I will put the url where you can find it the following day in
the chat – so make sure you copy all messages from the chat during the session.
HAVE FUN, Feedback is Welcome!

3. 3
Meet today’s team!
Diana Gray
Community Marketing
Manager AMER
@ UiPath Inc.
Manjula Dharmalingam
Founder The Next Innings
Mukesh Kala
RPA Developer
@Boundaryless Group &
UiPath MVP
Aswathy Suresh
Program Manager,
Academic Alliance
@UiPath, Inc.
Cristina Vidu
Global Manager, Marketing
Community
@ UiPath Inc.

4. 4
Anurag Upadhyay
Digital Tranformation Consultant
PWC
Meet the weekly instructors !
Cristina Avram
Sr. Product Manager
@UiPath Inc.
Dan Fishkin
Solution Architect
@Tapestry & UiPath MVP
Noopur Inani
Product Manager
@UiPath
Tracy Dixon
Operational Excellence & UiPath
Partnership Lead Centric Consulting
& UiPath MVP
Andrei Vintila
Senior Product Manager
@ UiPath Inc.
Week 1 Week 2 Week 3 Week 4
Mukesh Kala
RPA Developer
& UiPath MVP
Devyani Sharma
Senior RPA Business Analyst at Boundaryless
Automation
Christian Ventriglia
Automation Solutions Architect @ FanDuel
& UiPath MVP
Dan Fishkin
Solution Architect
@Tapestry & UiPath MVP
Mukesh Kala
RPA Developer
& UiPath MVP
Mukesh Kala
RPA Developer
& UiPath MVP

5. 5
Business Analyst Curriculum Overview
1. Automation Business Analyst Fundamentals (3hrs)
2. Introduction to UiPath Business Automation (35 m)
Prerequisites
Prior to week one of this series. Please take the following training
Prerequisite Self Study Training – Please take prior to November 13,
2023
1. Automation Business Analyst Foundation Survey
2. Introduction to Automation (1 hr)
3. Automation Implementation Methodology Fundamentals (1h 45m)
Week 1
Week 2
1. Getting Started with UiPath Process Mining (1hr 30m)
2. UiPath Task Mining Overview (2 hr)
Week 3
Week 4 Week 5
1. UiPath Task Capture Overview (30m)
2. UiPath Task Capture Deep Dive (2hr 30m)
1. UiPath Automation Hub Overview (30m) -
2. The Lifecycle of an Automation Idea in UiPath Automation Hub (2hr 20m)
3. Automation Business Analyst Foundation Assessment (30m)
1. BA Certified Professional Live Session (45 m)
2. Demo Day Preparation (45 m)
3. Demo Day (1hr 30m)

6. 6
Date/Time Topic Status
Nov 13,
10 AM EST
Business Analyst Series 2023 - Week 1, Session 1 Happening Now
Nov 15,
10 AM EST
Business Analyst Series 2023 - Week 1, Session 2 Register
Nov 20,
10 AM EST
Business Analyst Series 2023 - Week 2, Session 3 Register
Nov 22,
10 AM EST
Business Analyst Series 2023 - Week 2, Session 4 Register
Register for Events at community.uipath.com

7. 7
Important Links
Business Analyst Series 2003 Website page: https://bit.ly/BA_series_2023 to register for each session.
UiPath Forum Business Analyst Series url: https://forum.uipath.com/t/business-analyst-webinar-series-
2023/651962 to post any questions you have.
Prerequisite Self Study Training
1. Automation Business Analyst Foundation Survey
2. Introduction to Automation (1 hr)
3. Automation Implementation Methodology Fundamentals (1h 45m)
Google Form to update the course completion!
https://forms.gle/nhQtxVV5owgGDk1P6

8. 8
Agenda – Week 1 - November 13 & November 15
Day 1:
Business Analyst Series 2023 - Week 1, Session 1 Topics Covered:
•RPA BA - Roles & Responsibilities, Skillset & Challenges
•Traditional Business Analysis Methodology
•Walkthrough of RPA BA Documents
•Q&A
Please see below the week 1 mandatory UiPath Academy learning assignment (to be completed by Sunday EoD):
1. Automation Business Analyst Fundamentals (3hrs)
2. Introduction to UiPath Business Automation (35 m)
Day 2:
•Business Analyst Series 2023 Week 1, session 2 topics covered:
Challenges in Traditional Discovery
•Traditional Discovery VS Automated Discovery
•UiPath Business Automation Platform
•Exploring UiPath Tools: A Business Analyst's Perspective
•Case Study - How a UK based bank built a pipeline through continuous discovery
•Quiz
•Q & A
Please see below the week 1 mandatory UiPath Academy learning assignment (to be completed by Sunday EoD):
1. Automation Business Analyst Fundamentals (3hrs)
2. Introduction to UiPath Business Automation (35 m)
After UiPath Academy course completion please fill in the week 1 form.
Recording for Day 1 – Can be found at
on series page:
https://bit.ly/BA_series_2023
Or at this url:
https://community.uipath.com/e/mbqm9j/
the day after the session has taken
place in the wrap up tab at top of page
Recording for Day 2 Can be found at on
series page: https://bit.ly/BA_series_2023
Or at this url:
https://community.uipath.com/e/m4g4fq/
the day after the session has taken
place in the wrap up tab at top of page
Make sure you register for next session
here: https://bit.ly/BA_series_2023

9. 9
Business Analyst Series 2023
Demo Project Overview
Atul Trikha
Chief Technologist
@Peraton

10. Business Analyst
Series 2023 Project
Name: First and Last
Name of Project

11. 11
Jane Doe
RPADev @Company
jane.doe@uipath.com
Project Name:
Name:
Title:
Business Analyst Student YES_____ No_____
Business Analyst Career YES_____ No_____
Region:
Linkedin url:

12. 12
Problem Statement & Proposed Solution
Problem Solution
Lorum quis rempore aute nonsed quo conestiae
nis volent, officit iatisit voluptati acest apienda
pero eumque possum inum
vent inus, vende que pro dolut laturerum
explaces destiae repudan dandis mi, que volore,
corehen debitae cupider ibusantio consequias ra
dolorecus, tem aut fugia senit odi que od quat.
Neceptatio odis non cum que molum qui berum
re ea adi dest asimus modit iumet optate vernam
as qui officabores asi od quam ex el id qui des
repe sinvelendion. Andebitiis quae corehent aut
alicimus.
Quam repe odiciist et re nonsedi anditio. Nequi
ipsam hic te recabore commos volut ut ped
quaecus exceati busamus am cum nos mostrum
nosaper ferumqui tempost.

13. 13
Process Overview Example

14. 14
Process Overview Example

15. 15
Process Overview Template
# Item Description
1 Process full name
2 Process Area
3 Department
4 Process short description
(operation, activity, outcome)
5 Role(s) required for performing the process
6 Process schedule and frequency
7 # of items processes /reference period
8 Average handling time per item
9 Peak period (s)
10 Transaction Volume During Peak period
11 Total # of FTEs supporting this activity
12 Expected increase of volume in the next
reference period
13 Level of exception rate
14 Input data
15 Output data
General information about the process selected for RPA prior to automation.
Add more rows to the table to include relevant data for the automation process. No fields should be left empty. Use “n/a” for the items that don`t apply to the selected business process.

17. 17
Problem Statement:
Whether our customers are accelerating life sciences research, solving complex analytical
challenges, improving patient diagnostics and therapies or increasing productivity in their
laboratories, we are here to support them. Whether our customers are accelerating life
sciences research, solving complex analytical challenges, improving patient diagnostics
and therapies or increasing productivity in their laboratories, we are here to support them
Process Name
Business Benefits:
• Standardization: Development split by ERP and Region
• Stability: Manual, repetitive, and time-consuming processing tasks eliminate.
• Scalability: Increase deployment plan by ERP and Workstream.
• Leverage Modules: Intercompany Invoices and Cross Charges.
As-Is vs To-Be
As-Is To-Be
Our global team delivers a combination of
innovative technologies, purchasing
convenience and pharmaceutical services
through our industry-leading brands,
including Thermo Scientific, Applied
Biosystems, Invitrogen, Fisher Scientific,
Unity Lab Services and Patheon.
Whether our customers are accelerating life
sciences research, solving complex
analytical challenges, improving patient
diagnostics and therapies or increasing
productivity in their laboratories, we are here
to support them.
Process Diagram:
Technologies and Applications
List of UiPath Products Used Applications used
Studio , Orchestrator, Integration Services Microsoft Outlook, SAP , Coupa

18. 18
Problem Statement:
The Invoicing process is complex and requires many manual steps to prepare it before the
file can be uploaded. These steps include reading emails, downloading attachments,
extracting invoice details from PDFs, validating & entering details into a downstream ERP.
The Invoice extraction and input process is prone to human errors due to numerous
checks, calculations, and validations, making it difficult to achieve a desired accuracy and
processing rate. As the business grows more people are required to support this process.
Process Name
Business Benefits:
• Standardization: Business rules and activities applied the same across all Regions
• Operational Efficiency: Manual, repetitive, and time-consuming processing tasks
eliminated. Accuracy and quality of outputs improved.
• Scalability: Easier to scale operations and onboard new vendors with minimal effort
• Compliance: Adherence to SLAs and faster turn-around for payments
As-Is vs To-Be
As-Is To-Be
A dedicated finance team performs the
activities to read the invoice attachments,
manually check against the ERP, and
copy/paste data from the invoice into
downstream system. This can result in errors
and long processing times, as well as
duplication of work with multiple team
members reading from the mailbox.
UiPath Unattended Robot(s) will monitor a
dedicated mailbox and identify emails which
contain PDF attachments of invoices. These
invoices are sent through Document
Understanding to classify and extract key
details, perform validations, and input into the
ERP system. Exceptions are sent to Action
Center for manual review and correction
before passed back to the robot(s).
Process Diagram:
Technologies and Applications
List of UiPath Products Used Applications used
Studio, Orchestrator, Unattended Robot(s),
AI Center, Document Understanding, Action
Center, Integration Services
Microsoft Outlook, SAP, Coupa
824,000+
invoices per year
70%
improvement in time
savings
53%
STP without human
involvement

19. 19
Project Summary
Problem Statement:
Analysis / Changes:
Analysis (AS-IS):
Changes (TO-BE):
Results / Benefits:
Category Before After % Improvement
Process Diagram
19
Results / Benefits:
Results / Benefits:

20. Business Analyst
Series 2023
Introduction Slides
By UiPath Community &
The Next Innings

21. 21
This week’s speakers – week 1
Anurag Upadhyay
Program Manager
@Accenture
Mukesh Kala
RPA Developer
@Boundaryless
& UiPath MVP
Dan Fishkin
Solution Architect
@Tapestry & UiPath MVP

22. 22
Who is an RPA Business Analyst ?
• The RPA Business Analyst is characterized by
process experience and analytical thinking and
forms the bridge between the Developers and the
subject matter expert of the company’s automation
journey.
• The BA plays a pivotal and instrumental role in
RPA Projects
• BA is involved from the IPA to Delivery of the
project, BA will be involved in all stages of RPA

23. 23

24. 24
Roles and Responsibilities of RPA BA
Work with the teams in the identification of business
requirements.
Creating Documents (IPA, PDD, Test Cases, Etc.)
Budgeting and forecasting
Departmental planning
Compliance monitoring
Risk management
Profitability analysis
Reporting to stakeholders

25. 25
Who should
become an
RPA BA ?
A good understanding of
the business and
industry he or she is
analysing.
A great level of curiosity
and exceptional
communication skills
To be able to ask good
questions and have the
patience to listen to
complicated
explanations.
Good analytical skills
with the ability to
analyse requirements
from different angles
with clear and logical
thinking.
A “zoom-in zoom-out”
approach in identifying
the best solution, always
ensuring that the steps
taken are coherent with
the program vision.

26. 26
Challenges faced by RPA BA
Process Analysis Issue
Business Case Issue
RPA Development
Mismanagement of Responsibilities
Lack of help from the business team.
Desirable but not Economical
Maintenance of your RPA

27. 27
Career Path for BA
RPA BA
RPA
Senior
BA
RPA
Lead
RPA
Program
Manager
RPA
Delivery
Manager

28. 28
KeyActivities by a BA in Discovery Stage
A framework used to create visual representations of work processes.
o Understand the ecosystem
o Identify Tools
o Define workshop schedule
o Inform Stakeholders
o Set Expectation
o Inform about Limitations
1
o Initiate IPA
o Choose a good RPA use
case
o Collate all information
to build As Is/ To be
Maps and PDD
2
o Build PDD and Maps
o Complexity Analysis
o Sign-off & Client Management
o Pipeline Management*
o Conduct BOT Sizing & Pricing*
o Build Proposal*
3
Set the stage Get an understanding Document your understanding

29. 29
Things to keep in Mind!
o Do not Assume – Ask a lot of questions
o Process Maps are blueprints on which the
automation solution lies
o Deviations from the agreed maps – Affects cost ,
timelines and unhappy clients
o Every information provided by the client must be
documented .
o Most of the process contains very sensitive
information sometimes credentials to access very
sensitive data .
o Never share confidential documents.

30. 30
Process Definition Document(PDD) 1/2
This document is prepared by the Business Analyst, and this is
considered as a Business Requirements Document. This
document contains below items
• Document History - Name Of Author, Approver and
Document Version
• Process key contact - Process Owner, Process Reviewer
and Process SME.
• AS IS process - Like Process map , Process Steps , Process
Required Applications
• TO BE Process - Expected Design of the Business Process
• In/Out Scope for RPA
• Business/Application Exceptions
• Reporting

31. 31
Who all are uses this document and Why?
Process SME/Manager :
To Confirm and Validate Captured Requirement
Tech Lead/Architect :
To Design To Be Process Flow which be executed by the
BOT
Developer:
Use mentioned requirements to create Solution Design
Document and BOT Development
Business Analyst/Tester :
To Create Test Scenarios and Test Cases
Let’s have a look at PDD Sample
Process Definition Document(PDD) 2/2

32. 32
On a lighter note ;)
Streamlining
Standardization
Exploring ERP
Functionalities
Intelligent
Automation