UiPath Non-Technical Interview Questions
What is considered a best practice for dealing with large projects?
- Breaking a large process in smaller workflows - Giving descriptive names to variables and workflows - Testing workflows independently
When developing automation projects, it's best to follow what best practices for great automation?
-Reliability: robust workflows that can handle errors and recover gracefully -Efficiency: Maintaining smooth execution while cutting down development time -Maintainability: In an environment where collaboration and handovers are the way things work, it's important that your project is easy to update -Extensibility: The project needs to be as prepared as possible for the addition of new components project organization
Business Analyst Training Traceability Matrix What?
A tool that helps tracking the requirements throughout the cycle, helping to ensure thatthe approved requirements are satisfied by the delivered solution
Business Analyst High Level Process Maps
AS-IS TO-BE Process Steps Step 1 Applications Used Application 1 Application 2 Application 3 AHT 5 mins
Solution Architect Sustain RPA
Analytics through reports Monitoring and robot execution Document changes in the DSD Supporting the RPA Operations team
What is tracing and how do you enable tracing in rpa?
By default, UiPath generates log files that track the activity of Studio and the Robots. These logs can be accessed from the Execute ribbon tab, by clicking the Open Logs button. For complex issues, more details about your automation are needed. To gather them, tracing must be enabled. In UiPath Studio, tracing generates a .etl file. It contains binary log data at the trace level, such as disk accesses or page faults, and is used to log high-frequency events while tracking the performance of an operating system.
RPA Implementation Methodology Environment Setup Robot grouping
By process o Administration ease o Low flexibility o Low robot utilization By used applications Administration difficulty o High robot utilization Mixed approach Optimal choice
Business Analyst Training Change Management
Change Management and Change - Definition Definition of Change Change Management - Steps
RPA Implementation Methodology RPA Development Approach Developer collaboration
Choose the developer collaboration method within the RPA team. Multiple technologies are supported, including TFS and SVN, which are natively integrated with UiPath Studio.
Solution Architect Responsibilities and ownership of the SA
Enable Prepare Design Build Test Sustain
What is the effective process to Log into rpa?
For each activity, there should be a log There should be a trace process to know the operations and to correct the errors.
RPA Implementation Methodology Processes Every Company Should Automate
HR Services Supply Chain Finance and Accounting IT Services
Business Analyst RPA Implementation Strategy
Highly frequent process and (system) environment change No Robotic Automation High Cost Automation Static process and (system) environment Zero touch Automation Semi-Automation
RPA Implementation Methodology What Process Should I Automate?
Highly manual and repetitive processes Processes with standard readable electronic Input Type Changeable Processing Method or System Change Rule-Based Processes High Volumes Automation Savings Low Exception rate Well documented, stable, predictable
Business Analyst Opportunity assessment - The questionnaire
INPUT PROCESS METRICS PROCESS DESCRIPTION IT ENVIRONMENT
RPA Implementation Methodology Implementation Methodology SUSTAIN
Monitor Control Improve Hypercare Platform Support model Quantify the expected benefits Monitoring robots performance Continuous service improvement
RPA Implementation Methodology Reusable Components Approach Shared File Storage
PROS: ✓ Easy to implement ✓ Calling by reference CONS: ▪ In case of network failure, the robots are not able to run ▪ The robots can run more slowly due to network latency (or even trigger exceptions) ▪ Security risk (access to shared folder)
RPA Implementation Methodology Development collaboration tools
SVN native integraton TFS native integration GitHub manual synchronization required
Solution Architect RPA Operations COE
Security Design Operations Design Implementation Design Platform Design Governance Modeling Support Modeling
Which of the following are considered best practices?
Start your new sequence on a short annotation meant to explain the purpose of the workflow. Include a Should Stop activity at the end of the workflow. Think about the exceptions that might occur during the execution of the process
Solution Architect Local File Storage
Store the reusable components in the Source Control System. Sync files in shared location. Add the network path to the Library in Studio.(RECOMMENDED)
RPA Implementation Methodology Authentication of robots In Windows session
The credentials used for authenticating the windows session and starting the workflow will be stored into Orchestrator o The robot does not require administrator privileges to run o Various options for robot accounts: one generic account, multiple technical accounts or user accounts o Analyze the benefits of each approach for the automated applications.
RPA Implementation Methodology Authentication of users Active Directory integration
The login to Orchestrator can also be done using Active Directory integration. This can be achieved by associating AD users to groups and assigning Orchestrator roles to particular groups o The members of the groups would be able to automatically log into Orchestrator
RPA Implementation Methodology Implementation Methodology BUILD
Tracking the progress Please open the Development Specification Document ReFramework benefits
Business Analyst Training Testing
UAT - Lifecycle & BA Role UAT Prerequisites UAT Plan - Structure
RPA Implementation Methodology Implementation Methodology OPPORTUNITY ASSESSMENT
What Process Should I Automate? Processes Every Company Should Automate
Business Analyst Training Traceability Matrix
What? Why? Who? When? How? Tool
activites naming practices?
be explicit and follow guidlines
Solution Architect Sustain
o Change documentation o Monitoring o Support
Business Analyst Training Traceability Matrix When?
➢ Throughout the project cycle, starting with the project approval
Business Analyst Lesson Learned
➢ Update the document, don't start writing it. It should be written from the first stages and structured accordingly ➢ Collect input from all team members, per their activity ➢ Document what triggered issues and how to identify them easier in the future ➢ Describe events and outcomes, not people ➢ Describe what teams were impacted by the change
RPA Awareness RPA Journey & COE Enablement
1 Implementation scenarios 2 A typical 3 step approach 3 Typical project team structure 4 RPA Center Of Excellence types 5 Building a robotic operating team 6 A successful RPA implementation 7 Main inhibitors of RPA implementation
Solution Architect Framework layer
1. Framework layer: High level State Machine using the REFrameWorkwith overall exception handling.
RPA Implementation Methodology
1. Onboarding and COE enablement • IT Onboarding • Business onboarding • Creating a Center of Excellence 2. RPA Preparation • High level architecture • Best practices • Project management methodology 3. Opportunity assessment • Identifying suitable processes • Common processes for automation 4. Design, Build, Test • Design - the PDD • Build - the DSD • Tracking the progress • Robotic Enterprise Framework • Testing steps 5. Sustain RPA • Hypercare period • Quantify benefits • Reporting the results
Solution Architect The Business Process layer
2. Business Process layer: Modeling of the business process rules - a flowchart integrating other components from the other levels
Solution Architect The Services layer
3. Services layer: Additional service components with internal exception handling. State machine template.
Solution Architect The Application Process layer
4. Application Process layer: Components working with applications and implementing process rules. The argument names can be related to the business process. This component will navigate, write and extract
Solution Architect The Application Screen layer - highly reusable
5. Application Screen layer: Generic components where arguments are not related to the business process rules. Separate workflows can be created to navigate, input, and extract data.
Solution Architect The Data layer - reusable
6. Data layer: Interact only with easily accessible (local) data. Orchestrator activities allowed. Not for application interaction.
Business Analyst Defining automation complexity
A HIGH complexity project is one that requires programming skills (.NET programmability) in terms of string manipulation functions, working with arrays, data tables, collections, data formatting, exception handling; complex SAP applications, and/or complex applications running in a Citrix environment, and/or terminal emulators. Development time is 4-6 weeks. MEDIUM complexity automation project could be one that requires the transfer of data between applications or one that involves SAP or applications running in a Citrix environment. It takes around 3-4 weeks to develop. A LOW complexity automation project is in general, one that can be easily created with the recorder and requires small customizations thereafter. This includes desktop applications as well as web applications. It can include scraping (web scraping, screen scraping) and it generally takes 1-2 weeks for Development
RPA Implementation Methodology RPA Development Approach Naming strategy
Adhere to the naming strategy standards suggested by the developers. The entire team should follow this convention to facilitate code understanding, review and maintenance.
RPA Implementation Methodology RPA Development Approach Reusable components
Agree on a strategy for reusing and distributing the developed components. Save time and effort by defining the reusability of components cross-department or crosscompany
Business Analyst Opportunity Assessment
Aim & Approach RPA Implementation Strategy Organization wide assessment Complexity Factors Defining automation complexity Factors driving automation potential Business Benefits Organization wide assessment Opportunity assessment - The questionnaire
RPA Implementation Methodology RPA Project Management Methodology
Analysis Design Development System Integration Testing UAT Warranty
Solution Architect Solution Design
Attended vs. Unattended • Input and Output data • Sub-processes • Number of robots based on business requirements • Process and sub-process scheduling • High level interaction between workflow components Source Control project names • Type and data format - E. g. Queues and queue items specific content • High level diagram of the automated process (will go to DSD). • Additional descriptions
RPA Implementation Methodology Implementation Methodology SECURITY
Authentication of robots Authentication of users Development collaboration tools
Business Analyst Go-Live Preparation
BA Role in GO - live preparation What To whom Preparing GO Live - User Manual & Lessons Learned User Manual Lesson Learned
Business Analyst Role - RPA What is the role of a Business Analyst(BA)?
BUSINESS / PROCESS OWNER TECHNOLOGY TEAM Understands the business requirements & problem Translates the business problem into Technology Problem and provides an high level solution Assists in solution design and Confirms the solution Validates that the solution does what was intended to do A bridge between the stakeholders requesting a solution and the ones delivering the solution
Business Analyst Exception Handling
Business Exception ➢ Mandatory details are missing or incomplete/ unidentifiable ➢ Email attachment is not available Known Previously encountered. A scenario is defined with clear actions/ workarounds for each case. Un-Known New situation never encountered before, which can be caused by external factors and cannot be predicted with precision. However if it occurs, it must be communicated to an authorized person for evaluation System Exception ➢ Application stops responding ➢ System login failure Known Experienced previously, action plan or workaround available for it Un-Known New situation never encountered before, or may happened independent of the applications used in the process.
RPA Awareness RPA Center Of Excellence Types
CENTRALIZED One RPA COE serving all Business Units FEDERATED Independent RPA COEs within each business unit HYBRID One main RPA COE, linked to several smaller RPA COEs dedicated to business units
Business Analyst Training Change Management and Change - Definition
Change Management Definition: Process that guides Business Analysts in preparing, supporting, and adopting process changes Change Definition: Any modification or revision of the requirements in the PDD Example: Newly identified input format
Business Analyst Training Change Management - Steps
Change-Request ➢ A detailed Change-request is created that enlists the Reasons for change, Description and Urgency Assess the Change ➢ Scope of Change ➢ Impact of Change on Business Process and System ➢ Risks related to Change implementation ➢ Estimate the effort required for change implementation Change Management Board ➢ Change Management board will validate the Assessment & information captured ➢ Will Approve, Prioritize or Reject the Change
Solution Architect Test RPA Quality assurance
Code review audit Development Specification Document sign-off Functional testing sign off from Process owners REFrameWork automated test framework Performance tests Load/Stress tests Robustness tests
Business Analyst Organization wide assessment
Complexity ➢ Defined as Low(<30%), Medium(30-60%) and High(>60%) ➢ Derived based Input methods, Application type, Free text, Environment and no of applications involved Potential FTE Savings ➢ Derived from key parameters like % of Rule based steps, Input Methods, Free Text and type ➢ Yields a high level Potential FTE benefits and automation percentage Automation Quadrant ➢ Derived as a matrix based on Process Complexity and potential benefit (High / Medium / Low) ➢ Classified as Quick Win, Low Hanging Fruit, Must Do Improvements and Long Term Improvements
Business Analyst Business Benefits
Cost savings Productivity Gain Business Agility Quality improvements/ Error reduction Customer Satisfaction Flexibility Compliance
Business Analyst Define & Design RPA Solution
Create PDD Gather necessary information and put together a document describing the process Signoff & Maintain PDD Agree both with the business owner and the development team upon the document. Keep the document up to date during development. Unexpected things regarding the process might come to the surface. Solution Design Design RPA Solution in collaboration with Solution Architect & RPA Developer. Assist Solution Architect in documenting the solution. Hand over documents for development
Solution Architect Shared Components Package
Create one package containing shared components and distribute it using the Orchestrator embedded provisioning mechanism.
RPA Implementation Methodology Tracking the progress
Criteria for considering the development done for a process 1 Code produced (completed all 'ToDo' items in code) 2 Code commented according to best practices, checked and ran against current version in source control 3 Peer reviewed (or produced with pair programming) and meeting development standards 4 Passed unit tests 5 Deployed to system test environment 6 Passed System Integration tests and signed off as meeting requirements 7 SDD document filled in and approved 8 Relevant documentation/diagrams produced and/or updated
RPA Awareness A successful RPA implementation
Cultural adoption o Active executive-level RPA sponsor o Strong and operationally efficient Robotics Operating Model o Dedicated Change Management teams IT engagement o Onboard IT function early-on to convey strong governance o IT will ensure requirements for security, scalability, auditability, business recovery and change management are properly met will In house RPA capability o RPA is a strategic capability o RPA aims to evolve, leverage scale and increase business value
Business Analyst Evolution of RPA BA & skills required
Curiosity Wanting to identify all the pieces in the puzzle. Continuous learning Patience Delivering the final output may take time Analytical skills Using clear & logical steps in analyzing a requirement from all angles Vision Zoom-in zoom out approach in identifying the best solution Communication skills Listening, observing and asking the right questions Business & Industry Knowledge Understanding your work environment
What is Project Debugging in rpa?
Debugging is the process of identifying and removing errors from a given project. Coupled with logging, it becomes a powerful functionality that offers you information about your project and step-by-step highlighting, so that you can be sure that it is error-free. Logging enables you to display details about what is happening in your project in the Output panel.
RPA Implementation Methodology RPA Development Approach Environment setup
Decide on the split between the different robotic environments. The advantages offered by the different methods need to be weighted per each project.
Business Analyst User Manual
Describe The New Process Describe final Inputs & outputs Describe process scheduling How to reset and restart the process (for transactions blocked) Describe Reporting and dashboards Error handling Handover User Manual
RPA Implementation Methodology License Features
Development Unattended Attended
RPA Implementation Methodology Environment configuration order
Development environment User Acceptance Testing environment Production environment
Business Analyst Aim & Approach
Devise a strategy to prioritize processes Understand and layout complexity factors Calculate complexity level Calculate automation potential Map business benefits Map the processes into quadrants Prioritize processes
RPA Implementation Methodology UNATTENDED ROBOT
Doesn't require human intervention o Triggered and running remotely o Fit for manual, repetitive, rule-based back office activities NOT requiring human intervention o Communication with the Server is bi-directional (unrestricted) as below: - Robot to Server: Execution logs, automated process upload, robot status - Server to Robot: Automated process version deployment, schedule, start, reset
RPA Implementation Methodology Authentication of users With username and password
Each Orchestrator user can log in with username and password o The associated roles can be fully customized based on granular permissions
Explain About project worked in rpa?
Explain the project description neatly Explain the Test data details, How you are getting the input to the UI and How you will write your output Error Handling methods, how you taking the screenshot during the error SDLC Document Preparation details Explain the Orchestrator mapping details
Solution Architect Stages of an RPA Project
Infrastructure Setup Project Governance Workflow Design Workflow Development Quality Assurance Hypercare
Business Analyst Inputs & Outputs
Inputs ➢ Application type - From which inputs are accessed e.g.:- file, a screen, email, a scanned invoice etc. ➢ Input Structure - Input structure, Templates from which identified inputs needs to be captured ➢ Identify Fields - Unique identifiers to capture the required fields ➢ Input Location - Location from which the input file/ application can be accessed For TO BE, analyze in detail every input and how it is obtain and standardize where possible ➢ Already existing at activity level: i.e. a report that triggers some actions ➢ Specifically created for RPA: i.e. data posted to be used by the robot Outputs Identify if the output already exists or it needs to be generated by the robot: ➢ Output type: a new record in an app, a report, a file etc. ➢ Output type - file/ folder/ report. Attributes to capture: destination, structure, content, trigger
RPA Implementation Methodology Best practices and lessons learned
Interview team: o Composed of 2 members: one asks the questions, one documents the result o Choose the right persons to be interviewed: o The SME is the interviewee- having best knowledge on the detailed process, not the manager o If the process is replicated in more teams (see 100 branches from a bank), the candidates should be chosen by following benchmarks: sample of relevant teams; best SMEs chosen by their managers Others: o The process metrics (FTE, AHT, etc) should be collected separately by the internal Business Analysts o Group the interviews if more processes are performed by the same team
Business Analyst Process Description
Key Stroke Document ➢ Process activities detailed at key stroke level with respective screen shots captured ➢ Capture each and every action by SME on the application layer ➢ Screen shot tools :- Microsoft Screen recorder/ Epiplex to capture screen shots Process Video Recordings ➢ Video recordings of process activities ➢ Best used to capture for complex business rules within a process ➢ Short video recordings (Activities as Modules) with appropriate voice overs are recommended ➢ Index the videos and refer to them as reference in the As-Is process description Business Rules Library Either use the existing business rules library or Document the business rules in a separate file, to ease the PDD Documentation&Development : ➢ Robot can use businessrules directly from the library ➢ In case of future rule changes, Library will be updated directly, with low/ Zero impact on the code ➢ Index the Businessrules and refer to them as reference in the As-Is process description
Solution Architect Reusable Components Approach
Local File Storage Shared File Storage Shared Components Package Custom Packaging Method
Business Analyst Organization wide assessment
Long-term Improvements Must-do Improvements Low hanging fruits Quick Wins
best practices for ui interaction?
Make sure you always choose the right input method that suits your needs The recommended input method is Simulate because it's the fastest. The recommended output method is FullText because it's fast and accurate. You should only use OCR only as a last resort.
RPA Implementation Methodology Sustain
Monitor The Business Processes and Workflows Review reports o Verify outcomes o Measure KPIs Control The Digital Workforce o Review Dashboards o Quick Intervention mechanism o Support model Improve The Attended and Unattended Robots o Correct failures o Integrated automated process o Extend scope o Incorporate CRs
RPA Implementation Methodology UiPath Licensing Models
Named User license dedicated to a single user, number of acquired licenses should match number of employees Concurrent User license not for anyone in particular but the number of them indicates how many can access simultaneously For orchestrator there is a server license for Unattended and NonProduction robots there is concurrent runtime license Attended Robots and developers need named user license
Business Analyst Complexity Factors
Number of screens involved in a process can be taken as a proxy for number of steps Type of Applications - Java Applications, Mainframe applications, SAP, Web based applications, Dotnet applications, MS Office .. Etc Variations/ Scenarios within the process (Number of If Else kind of Rules) Structured Inputs - Machine readable and digital inputs. Scanned PDF Images/ Free flow texts in Emails are considered to be unstructured inputs Standard Inputs - Templated inputs, same format or type of inputs across cases Free Texts - Flow of information as free text (Unstructured informational flow) within the process Image based automation - VDI/ Remote desktops/ Citrix
Solution Architect RPA Deployment considerations
Orchestrator Deployment: Robot Deployment: Package Deployment: Credential Deployment:
Business Analyst Out of Scope
Out of scope ➢ Compliance requests ( Must remain in the human control of team members) ➢ Activities/ source apps under change in the next 3- 6 months ( i.e a source app release announced/) ➢ Templates/ inputs not standardized or involving free text/ poor quality scanned images ➢ Activities that need human input, due to the complexity and human knowledge involved ➢ There is another automation in place ➢ Effort to automate a specific activity bigger than the gain Impact of Out of scope activities For out of scope activities, that mean that either human intervention is still needed, identify dependencies at process level - ➢ will it change the order of performing the steps? ➢ will the robot need to be restarted? ➢ will the robot need to wait for that activity to be processed first? ➢ do the robot need to use the output of that manual activity
RPA Implementation Methodology Custom Packaging Method
PROS: ✓ An alternative to the Shared Components approach CONS: ▪ The most complex approach and the hardest to implement and maintain ▪ Dependent on third party components
RPA Implementation Methodology Shared Components Package
PROS: ✓ Calling by reference ✓ Version control CONS: ▪ Harder to implement ▪ Project path needs configuration
RPA Implementation Methodology Reusable Components Approach Local File Storage
PROS: ✓ Easiest to implement ✓ Most secure CONS: ▪ In case a reusable needs to be changed, manual re-publishing and re-deploying are required
RPA Implementation Methodology Implementation Methodology DESIGN
Please open the Process Design Document available in the Please open the Test Cases Template available in the
Business Analyst Process Deep Dive
Pre-requisite ➢ Gather and understand process related documents - Standard Operating Procedures, process maps, Organizational Chart, user manuals etc Aim ➢ To have a deep understanding of the process ➢ To document and validate with the process owner As-Is process flows and all relevant data for RPA ➢ Design To-Be process flow - High level ➢ Handover a good documentation to the developer to build the RPA solution for that process Approach ➢ Organize a discussion with the process owners & SME ➢ High level description of the process (walk through the process) ➢ Understand the complexity of the process & challenges (from SME point of view and RPA) ➢ Shadow the SME/ Workshop ➢ Capture process metrices (scope, applications involved, no of FTEs, volumes, AHTs, SLAs, Time dependencies, challenges, complexity, stakeholders involved and their role) ➢ Prepare process definition Document with the help of Key stroke level documentation or process recordings ➢ Mark what is in scope and out of scope for RPA from the beginning and continuously validate this classification during the documentation. Log the reasons behind
Business Analyst Opportunity Assessment part 2
Process Deep Dive Actions & Deliverables Requirement Gathering High Level Process Maps Process Mapping - SIPOC Process Mapping - L4 Level Inputs & Outputs Process Description Out of Scope Exception Handling Define & Design RPA Solution
RPA Awareness A typical 3 step approach
Proof of Concept: A quick 30 day PoC on a selected process to validate the applicability of RPA/ IPA. Piloting of additional processes with a parallel set-up of governance & roll-out planning Roll-out of the Robotics Factory for all relevant business processes and handover to the customer.
RPA Implementation Methodology Quantify the expected benefits
RAPID ROI BETTER CUSTOMER EXPERIENCE ENHANCED PROCESS ENHANCED MANAGEMENT ABILITY INSIGHTS AND ANALYTICS INCREASED COMPLIANCE
Solution Architect Preparation - Project Governance
RPA Development Best Practices Enhanced REFramework RPA Feasibility study and Process optimization Development effort estimation - Guidelines
Solution Architect Enable - Prepare RPA
RPA Operations COE RPA Deployment considerations
RPA Awareness Building a robotic operating team
RPA Project Manager RPA Service Support RPA Supervisor RPA Business Analyst RPA Change Manager RPA Developer RPA Solution Architect RPA Infrastructure Engineer
Solution Architect RPA Build - Developing workflows
Review and sign off extra requirement list after PDD sign-off Constant mentoring and increasing the capabilities of the RPA Developers Troubleshooting and debugging Logging and reporting Source control owner of the solution Performance improvements and quality check Managing risk identification and risk mitigation strategies Assisting in Unit and Functional testing
RPA Implementation Methodology Best Practices in Machine Configuration
Robot Machines o Combine Attended and Unattended robots o Design a scalable solution Development Machines Assign machines with enough processing power
Business Analyst Factors driving automation potential
Rule Based • Agent/user doesn't use his/her experience to take any judgement or make decisions while processing a case but on the business rules and pre defined logic Process Type • Manual & Repetitive - A process which is performed • Semi Manual & Repetitive - A process which is • Automated - A process is already automated. Specify • Manual But Not Repetitive - A process which is Standard Input • Input are Standard - Inputs are standard if the content is • Input are NOT standard - Input are considered as not Process or applications used • The process or applications used to process a case going to change within 3 - 6 months. E.g. Major upgrading in ERP systems, Process re-engineering etc Unknown Exceptions % • %age of the total volume received cannot be processed which cannot be processed without an external factor(query/approval.
RPA Awareness Implementation scenarios
TOOL-FOCUSED RPA IMPLEMENTATION o The client purchases a license for the RPA tool o The RPA provider operates as technical support (optionally) o The implementation is led by the client ASSISTED RPA IMPLEMENTATION o The client can involve a consultancy partner to be able to deliver a seamless RPA Implementation o The organizational transition and KT is ensured RPA AS A SERVICE o The client buys the RPA solution as a service o The service provider takes responsibility of the entire implementation o The client focuses only on the business value added
Business Analyst UAT - Lifecycle & BA Role
Test Strategy • Defining the testing approach to achieve the objectives / standards in providing the testing Test Design Preparing: • Test plan • Test Scenario/Cases • Test data Test Execution • Performing testing • Reporting successful and failed tests • Coordinating UAT • Performing test reports Defect Management • Tracking Defects • Debugging Test Closure • Sign-off UAT • Detailed reporting and analysis
Business Analyst BA Role in GO - live preparation To whom
The teams that will be still involved in the operational process ➢ in the guarantee/ post -implementation monitoring ➢ Involved in the business as usual, after handover (attended or unattended bot) CoE Support ➢ in the guarantee/ post -implementation monitoring ➢ Handling exceptions and monitoring bots, after handover Technical Support CoE Support team(with the dev and solutions architect) ➢ Handling errors on applications identified by the bots
RPA Implementation Methodology Authentication of robots In applications
The work done by the robot requires using credentials. o The credentials can be stored locally, in the Windows Credential store or in the Orchestrator Database, encrypted. o Each robot can use its own set of credentials. Since the robot operates as a human operator would, it can use SSO the same way. o Besides the two described methods for storing credentials, a third party solution for credential storing can be used.
RPA Implementation Methodology Server Architecture
Two data centers o Active-active architecture o A NLB and 2 Orchestrator nodes ensure high availability o Round-robin network balancing algorithm o Multiple nodes supported if required o Full redundancy reinforced by: o Shared storage of the NuGet packages o The SQL Server AlwaysOn Availability o Group feature o A load balancer between the 2 Kibana web servers o Reporting: o ElasticSearch o Kibana
Solution Architect Shared File Storage
Use a file share location to store the reusable components and invoke them remotely.
Solution Architect Custom Packaging Method
Use a third party solution to create packages that also provision the reusable components.
RPA Implementation Methodology RPA Project Management Methodology
WATERFALL Project scope defined in advance AGILE Daily developer meetings
Business Analyst UAT Plan - Structure
What? • Test if the robot performs same actions & output as the user does • Test new outputs as described in the PDD When & where? • Define the total time duration, start date & end date • Schedule the tests according to test duration & testers availability • Ideally bring all the testers in the same room Who? • Process owner - SMEs • BA Developer • BA • CoE Support team How? Schedule testing meeting Testers perform same tasks as the robot would in the same environment Log all results as a baseline Run robots and compare results Log and Debug issues Establish reporting metrics Repeat until the results meet success criteria Tools: • Test_Scenariostemplate • Issue_log template
RPA Implementation Methodology UiPath Robot
Windows service that Executes automation instructions
How should an RPA developer address a runtime error?
by logging any exception events by using automatic recovery in a try catch block by using try catch blocks when invoking workflows
What are some limitations of RPA?
developers can not automate creativity or experience based decisions
RPA Implementation Methodology UiPath Licensing Standalone Lincense
if orchestrator is not used, we ave named user and node locked. both are used on a single machine but node locked allows for multiple users. studio and attended use both but unattended has to use node locked license
Solution Architect RPA Workflow Abstraction
o Abstraction is as important in RPA as it is generally in software development. o We suggest six layers of abstraction 1. The Framework layer 2. The Business Process layer 3. The Services layer 4. The Application Process layer 5. The Application Screen layer - highly reusable 6. The Data layer - reusable o The SA identifies the workflow components and assigns them to the appropriate leve
RPA Implementation Methodology ATTENDED ROBOT
o Assists human operators o Triggered manually and running locally o Fit for manual, repetitive, rule-based activities, requires human intervention o Communication with the Server is bi-directional (restricted) as below: - Robot to Server: Execution logs, automated process upload - Server to Robot: Automated process version deployment ONLY
Solution Architect Prepare
o Best Practices agreement o Coding standards o Robotic Enterprise Framework o Collaboration with BA on feasibility and optimization o Development effort estimation o Technical meetings planning
Solution Architect Test
o Code review and audit o DSD sign-off o Functional testing sign-off
Solution Architect Package Deployment:
o Control package propagation
RPA Implementation Methodology UiPath Studio
o Desktop application that enables users to automate with highly intuitive tools, not code o Includes the following: - process recorders - drag & drop widgets - best practices templates
RPA Implementation Methodology UiPath Orchestrator
o Enterprise architecture server platform. Supports the following: - release management - centralized logging - reporting, auditing, monitoring tools - remote control - centralized scheduling - queue/robot management
Solution Architect Build
o Extra requirement list after PDD sign-off o Constant mentoring of Devs o Troubleshooting and debugging o Logging and reporting o Source control solution owner
Solution Architect Orchestrator Deployment:
o High Availability and Scalability, o Disaster Recovery and Automatic Failover strategies, o On-Premise or Cloud-based
Solution Architect Enable
o Infra Initial Setup o Orchestrator deployment options o RPA Deployment Environments
RPA Implementation Methodology Continuous service improvement
o Integrated automated process o Extend scope o Include new business process branches for more advanced features o Simplify and stabilize o Incorporate Change Requests o Apply Change Management o Release new versions o Discontinue obsolete versions
Solution Architect Credential Deployment:
o Maintain credential audit and control
Solution Architect Robot Deployment:
o On-Premise or Cloud-based option o Operating System Environment - Windows Workstation Environment or Windows Server Environment o Operating Infra Environment - VDI or VM o Underlying Sub-System availability and integration o Ease of upscaling during peak loads and offpeak downscaling
Solution Architect Design
o PDD sign-off o Overall solution o Component splitting o Developer appointment o Reusable component identification o Configurations, queues, schedules o Outstanding challenges documentation
RPA Implementation Methodology Hypercare
o The Hypercare period starts after moving the process into production o Various members of the team should monitor the first process run, and intervene if needed o A business and a support representative should be available to supervise the first process run Business representative: o Is able to validate the outcome of the robot's work o Cross checks the input file in case if errors Support representative: o Troubleshoots the technical aspects (application pop-ups, errors, crashes, machine issues or network connectivity problems)
RPA Implementation Methodology UiPath Licensing Reccomended Setup and Distribution
segregatiom between pre production and production environments is recommended heat licensing provides full control for all licenses and allows for centralized license distribution and management
RPA Implementation Methodology Support model Support Level 2
skill • Developer background (.NET or VBA) • UiPath Academy Advanced Learning plan completed • Trained as a developer access • Studio, Orchestrator & Kibana permissions • Can move the workflow in back to development stage • can move to production an improved version of the process
RPA Implementation Methodology Support model Support Level 1
skill • Good technical background • UiPath Academy Foundation learning plan completed • Trained as a support specialist access • Orchestrator & Kibana permissions • Can view, monitor and change assets if requested • Cannot make changes to the code released in production
RPA Implementation Methodology Support model Super users
skill • Part of the business team; an expert of the business processes • Basic technical knowledge • Trained as a Business Administrator access • Orchestrator & Kibana permisssions • First notified if the robot stops running • Makes the necessary changes to correct the robot's behavior
Solution Architect Project Governance
• Agreeing on the project development approach • Reviewing the RPA best practices
Solution Architect Workflow Development
• Building the workflows • Performing Unit and Functional testing • Creating the Development Specification Document (DSD.)
Solution Architect RPA Test - Quality assurance Audit
• Credentials for applications usage • Scope limitation of credentials • Check against exposing sensitive information (send mail, save file, etc.) • Check against modifying configuration parameters
Solution Architect Infrastructure Setup
• Designing the server architecture • Installing and configuring the architecture • Setting up dev, test & production environments
Solution Architect Quality Assurance
• Executing the test cases • Reporting the results • Making the Go/NoGo decision
Solution Architect Workflow Design
• Filling in the Process Design Document (PDD) • Creating test cases and data • Designing the solution
Solution Architect Attended vs Unattended in solution design
• Front office processes can make use of back office processing • Data sync between processes using Orchestrator queues 1 Fast execution for the Attended robot 2 Scalable
Business Analyst INPUT
• Inputs are standard? • Data Inputs Type • Data Inputs Type - Comments • Does this process requires reading of Scanned Images or Handwritten Documents? • Does the process includes reading of Free Text?
Business Analyst PROCESS DESCRIPTION
• Language • High-level description • Quality check? &Quality check (%) • Is the Process Manual &Repetitive? • Rule based process? • Is the process or systemexpected to be changed within next 3-6 months • %age of Unknown Exceptions
Business Analyst PROCESS METRICS
• No. of FTE's • Number of Cases/ Transactions • Process Frequency • AHT • No of steps
Solution Architect Hypercare
• Performing workflow support • Managing Changes and Improvements
Solution Architect Key responsibilities
• RPA Solution Architect definition • Governance of the end-to-end performance of the agreed solution • Automation process optimization • Effort estimation • Code review • Workflow component and reusable definition • PDD and DSD sign-off • Number of robots used, config file, asset, queue, and schedule definition • Logging and Reporting - Dashboards
Business Analyst Training Definition of Change
• Refers to any modification in the initial process requirements as documented and agreed in the signed of Process Definition Documents (PDDs) • Is not a Bug/Defect • Can be triggered by: ➢ Bugs or issues fixing ➢ Business operations as part of the continuous improvement process/process optimization ➢ Business operations following a modification in the steps of the process in scope of the automation. ➢ Gaps in the PDD documentation [e.g exception not captured etc] ➢ External modifications in the IT landscape used in the process • Analyze the propose changes and apply KRAC approach • Identify impact: duration, risks, etc • Use Traceability matrix for logging the approved changes KEEP REMOVE ADD CHANGE
Business Analyst IT ENVIRONMENT
• Technology/ System Constraints • Are there any steps in the process which are already automated using any tool or utility? • Is there a test environment available? • Application Access Via Citrix/Remote Desktop? • No of apps
Solution Architect RPA Test - Quality assurance Code review
• Thorough code review - activity level • Follow the agreed standard and guidelines • Naming strategy • Optimal techniques • Hard coded values vs Config • Assets vs config files • Duplicated code • Scalability and Maintainability • Clean code
Business Analyst BA Role in GO - live preparation What
➢ Delivering Trainings ( along with the SMEs already involved in testing) ➢ Support in updating the existing procedures ➢ User Manuals of the RPA process ➢ Handover all the documents produced (and updated) during the project
Business Analyst Training Traceability Matrix Who?
➢ For documenting: BA with support of the deliverables' responsible
Business Analyst Actions & Deliverables
➢ Gather process information and data ➢ Prepare high level process map with straight through processing scenario and obtain sign-off from process owner ➢ Validate the process map with the process owner and update the document by including more scenarios and business rules ➢ Prepare the detailed L4 level process maps (including all scenarios) using process mapping tools like MS Visio/ Aris , valida te them with the process owner and update the process steps ➢ Prepare PDD and include any support material that would detail the business rules, matrix role, the input & output, reports specifications ➢ Validate The PDD with the process owner and update the PDD with all feedbacks, organize sessions for clarifications-if needed ➢ Obtain the Sign-off
Business Analyst Training Traceability Matrix How?
➢ Identify all deliverables according to the company's implementation methodology and build a template ➢ Split all requirements (process automation) into smaller sub- processes, exceptions and business - rules and map them with the deliverables ➢ Continuously update the status and changes and make sure the deliverables are provided accordingly ➢ Analyze the deviations
Business Analyst Training Traceability Matrix Why?
➢ Maps all requirements with the deliverables, reducing the risk that one requirement/ deliverable is forgotten ➢ Gives the ability to trace the progress from requirement to the test cases & Go-live materials (Procedures, User manuals, etc) ➢ Helps maintaining a versioning of the business requirements, making easier to identify all the tasks that are impacted by the change ➢ Ensures that the scope of the project is not expanded by adding new requirement or use-cases that are not specified in the documented requirements
Business Analyst Requirement Gathering
➢ Process Metrices can be captured with the help of existing workflow/ BPM tool, MI data & Time and Motion study (Provided by operations team) ➢ Volume ➢ AHTs ➢ Total FTE effort involved in the process ➢ Process Information ➢ Open and close times (Time dependencies) & SLA ➢ Expected increase in volume ➢ Stakeholders involved and their role ➢ Inputs & Input Type (Structured/ Unstructured & Standard/ Non-standard) ➢ Output & Output type ➢ Infrastructure requirements ➢ Test environment availability ➢ UiPath hardware/ Software requirements ➢ Applications used ➢ Understand and capture the underlying technology of each application ➢ Capture all applications used in the process ➢ Different instances of one application (Login module) - If applicable (e.g. SAP/ Mainframe) ➢ Thin 'or' Thick client ? ➢ Citrix/ VDI/ Remote desktops - Thin Client ➢ Desktop applications - Thick Clien
Business Analyst Training Traceability Matrix Tool
➢ Sample template and attributes walkthrough: TraceabilityMatrix_ClientOnboarding_v2_041017
Business Analyst UAT Prerequisites
➢ Test scenarios to cover for all the business use-cases, all the exceptions and business rules ➢ Test Data - input for the process (list of transactions/open transactions left to be posted/selected emails/documents for being processed etc) ➢ Test environments: ➢ Robot + Orchestrator test environment ➢ Applications Test environment ➢ Process frequency (daily/bi-weekly/monthly/quarterly) ➢ Check if the environment date needs to be updated ➢ Check if EOD/ EOM needs to be run ➢ Understand the number of times for which the data can be restored, if needed ➢ Dependencies with other projects on the same environment ➢ Receive an estimate of the test duration in one run (how long it would take the robot to perform the expected action) ➢ Clarify with the developer how an intermediary output can be verified
