Bot Development and Deployment Model

1.Demand Management Team

 Identify automation opportunities

 Process prioritization automation pipeline management

2.Risk and Control Team

 Check bots operational risks and control method

 Handle password management policies

3. Research Team

 Identify new technologies(AI,IQ-Bot,Analytics,Meta-bots)

 Manage internal demos and Proof of Concepts(POCs)

4. Bot Framework and Library Management Team

 Develop reusable bots and scripts

 Develop best practices, common framework, and reusable fast Meta-bots

5. RPA Scripting Team

 Write scripts (Core Scripting Team: Developers and Solution Architect)

 Deliver Bots

6. Production Support and Monitoring Team

 Maintain runbooks
 Resolve common infrastructure issues and root cause analysis of bot production issues
Business Excellence Team

 Team looks into Process assessment and prioritization (as to how the process is in general with
the knowledge of the applications that are involved and the complexity of the process )
 Prioritizing the process based upon rank
 BRD Documents
 UAT Application(Mainframe,Web Applications, Windows Applications) access for developers
 Process flow documents
 Solution mapping with process flow
 Effort estimation in bot development
 Application test against Automation Anywhere

Scripting Team

 Modulation of bots as independent deliverable entities

 Development in UAT Applications
 Parameterize parameters which will change from development to production in configurations
 Continuous communication with demand management to discuss the changes and demo of
progressed bot

Scripting and Operations Team

 Bug Fixing
 Test enviroment’s test acceptance approval
 Bot performance assessment
 Bot machines count estimations
 Robotics ID access raised for production application involved in automation process
 Process owner training (Education on how to run bots, raise issues, password change)
 Configuration file changes and standardization
 Bug fixing which appeared because of bot migration into production environment
 Bot production deployment and execute production parallel phase

Deployment planning?

 Define and agree deployment plans with customer

 Ensure all deployment packages can be tracked, installed, verified, and/or uninstalled or backed
out, if appropriate
 Ensure that change is managed during the deployment activities
 Ensure that there is knowledge transfer to enable the customers and users to optimize their use
of the service to support their business activites.
Handover documents

 High level design

 Low level design
 Deployment machine details
 Deployment task package in control room
 Release notes

Prerequisites

 Installation of product and its dependencies

 DEV license on development machines
 Run Time(RT) license on other machines
 Respective generic automation profiles created
 Credentials of applications/servers required for execution of bots

Deployment Machine’s Details

 Number of machines
 Category of machines
 Names of the machines
 Location of the machines

Deployment Package Details

 Number of bots
 Integrated bots

UAT folder,Prod Folder, Dev folder?

Scenario Test , Result , Timestamp

Bugs Categories

 Minor bugs – category 1

 Manual resolution available – category 2
 Show stoppers - category 3

Bot Release

 Task files
 New Configuration files
 Automation schedule

Workload Management

Device pool is a collection of unattended bot runner

Device pool In device pooler dedicataed to running task bot associataed with queues in processing their
work item , multiple queue can be serviced by single device pool or round robin scheduling algorithm or
prioritiz based

WLM Roles

Custom roles as Participants or Consumers.