RPA is the acronym of Robotics Process Automation. It is used by an organization to automate its tasks that usually an employee takes care of.

• Blue Prism
• UiPath
• Automation Anywhere
• WorkFusion
• OpenSpan

• Improved efficiency of tasks
• Performing the tasks quickly without errors
• Increased productivity
• Cost-saving
• Decreased turnaround time

• Limitations to tasks like decision-making or judgmental tasks
• Not a cognitive computing solution, rather learns through experience
• Might be error-prone when subjected to new environments without experience
• Higher cost of implementation across the industry

There are six steps involves in the process of RPA. These are:

• Identifying the need for automation and the areas where it can be implemented
• Optimizing the processes where there is a need for automation
• Building a business case
• Selecting the right vendor of RPA
• Modeling the development of RPA
• Building expert RPA bots

• Analysis: Identifying the business process for which RPA development is needed
• Development of the Bot: Fulfilling the requirements
• Testing: Performing quality checks
• Deployment and Maintenance: Deploying and maintaining the bot by the team

• Front office bots – Bots whose deployment is in the user’s control and require human intervention. These bots work from the same desktop as that of the user. They can only be triggered by local machines manually and cannot run remotely.
• Back office bots – These bots can run on locked machines from the orchestrator. The user may not be actively involved. These bots can also be triggered remotely by servers.

• Banking and finance
• Human resources
• Insurance agencies
• Marketing and sales

Answer based on experience. List out the Pros and Cons of any two tools. Example, UiPath is developer friendly whereas PEGA not.

In a typical RPA SDD document, following details are captured.

• Process flow diagram
• Scope of the process
• Detailed steps along with screen shots
• Inputs to the process
• Outputs from the process
• Exception details
• Logging Details
• Database configurations
• Other asset details

FTE is calculated based on Manual effort, volume and time taken to complete a process
FTE = (volume * AHT)/ Manual hour per day (8 hours)
AHT is Average Handling Time

Thin client: It is an application that we cannot get the quality properties while spying using any RPA tool .e.g. Any virtual environment.
Thick client: It is an application that we get a pretty handful of attribute features using RPA tool e.g. calculator, Internet Explorer.

Test Automation –For testing purpose we automate the application & getting the result that how many test cases is pass & fail
Process Automation –Automating the process without human intervention is called Process automation.

Recorder
Development Studio
Plugin / Extension
Bot Runner
Control Center

• Solution Design Document
• Process Flow Document
• Production Deployment Checklist
• Support Handover Document