How do I get an automation into UAT and Production?

Once an Automation Developer has built and configured an automation in the development environment it must pass through TCAB, UAT, DCAB and Hypercare before it can be deployed into the production environment for use. The process can be very involved.

Technical Change Approval Board (TCAB) Requirements

Business approved PDD and SDD

UAT Test Plan reviewed and signed off by the Business Area Process Owner

Evidence of a successful operation in the unit test cases in the Test Plan

Release Notes (PRN)

Automation Runsheets

Ai User Guide

Project Implementation Plan (PIP) at least 50% completed

Code package as a snapshot

TCAB Process

BISSO review the automation code and configuration to ensure that it aligns with RPA design principles and RPA best practice guide.

EBPM and BISSO approve the TCAB request based on the automations conformance. The Test plan is also reviewed at the discretion of BISSO.

The automation is deployed into the Testing environment.

The Business Area with the Developer and Process SME conduct UAT.

User Acceptance Testing (UAT) requirements

TCAB approval

UAT Test Plan

Test Plan Speadsheet

UAT test data (happy and unhappy paths)

UAT Process

Process SME with the Developer accept the automation as ready for deployment into production environment based on test reports.

BISSO initiates DCAB assurance checks reviewing the requirement documents to verify the automations readiness.

Development Change Approval Board (DCAB) Requirements

UAT has been completed, business has signed off and test results are recorded.

Production Verification Test Plan has been reviewed and signed-off

Implementation and rollback plan completed

Support Resources identified (SME and Developer available)

Project Implementation Plan 100% completed

Run Sheet

Code package for first deployment into production environment

DCAB Process

BISSO Deploys the automation package into the production environment:

1. BISSO plans the release

2. BISSO schedules the deployment

3. The Business Area provide BISSO with packaged automation

4. BISSO raise a Request for Change

5. BISSO approve the Request for Change

6. BISSO opens a change window

7. BISSO deploys the automation package.

The Business Area, Automation Developer and SME undertakes Production Verification testing IAW the test strategy, test plan and test spreadsheet.

The Business Area approves the automation for Go Live.


BISSO will undertake 2-6 weeks of hypercare if any Severity 1 and 2 defects are identified during this time the automation will be removed and returned to development.

BISSO will sign off an automation if:

system exception rate is less than 5%

All defects have been identified, documented and remediated.

The automation is able to process 100% of live data (minus agreed business exceptions)

able to meet agreed speed-based performance targets.

 SME and Process owner acceptance sign off.

Transition to sustainment

BISSO transitions the automation into sustainment IAW the agreed schedule.