Verizon implemented a 3-month pilot program to move its Automation Anywhere platform to AWS. This included establishing governance, security, and legal structures for bot development as well as training developers. The migration involved setting up Automation Anywhere instances across multiple AWS availability zones, with control room nodes behind an ELB. Infrastructure is provisioned via ServiceNow and Jenkins to automate the process and ensure resources are utilized efficiently. Key performance metrics are analyzed to validate cost savings targets are met.

1. Verizon RPA Automation
Anywhere Journey to the
Cloud Leveraging AWS

2. How Did We Get Started and More Importantly…GET GOING!
3 Month Multiple Team Bot Building Pilot Program
• This effort led to realizations that this was much more than just getting another
application up and running.
Governance/Security/Legal – Structure around bot ideation (use cases)
and full vetting process.
• Bot Use Case Management - Inventory/ROI calculator/Maintain Digital Org
Structure/Workflow approver & contacts/Legal & Security Questionnaire/Audit
document repository
Training – Ensure bot developers had proper training to get started and be
productive prior to receiving creators
CoE - Established for platform and infa support. Service Now ticketing, issue tracking and
built in work flows.
Confidential and proprietary materials for authorized Verizon personnel and outside agencies only. Use, disclosure or
distribution of this material is not permitted to any unauthorized persons or third parties except by written agreement.

3. Digital Finance–Executive Dashboard (Dummy Data)
Leader Roll-Up
1Q-2Q Progress (as of 4/9/19)
Utilization
Rate
(UR)
Total
Hours
EOY
Trend
Hard
Hours
EOY
Trend
Total
Hours
Target
Hard
Hours
TargetBots
Total
Hours
Hard
Hours
Bots
Total
Hours
Hard
Hours
J. Doe Accounting 196 246,852 170,823 51 120,804 60,454 79% 445,388 222,886 450,000 225,000
K. Smith
R. Palmer
AP 144 126,977 60,154 41 20,437 11,699 81% 75,349 43,133 205,000 110,000
A. White FP&A 84 51,960 12,560 13 18,890 3,409 39% 69,645 12,569 115,000 65,000
T. Wong
P. Harding
M. Ryan
Payroll 260 232,408 140,883 141 116,230 71,412 69% 428,525 263,287 425,000 260,000
O. Salerno Tax 80 180,613 60,412 30 97,564 36,979 46% 360,037 136,337 390,000 150,000
W. Butler Treasury 102 80,656 15,878 47 26,913 5,660 31% 99,225 20,868 165,000 75,000
- Other 56 170,026 79,316 23 80,039 19,840 76% 295,093 73,147 250,000 115,000
922 1,089,492 540,026 346 480,877 209,453 60% 1,773,262 772,227 2,000,000 1,000,000
YTD Hours vs EOY Trend
Over Targets
< 10% Off Trend
> 10% Off Trend
> 25% Off Trend
> 50% Off Trend
1st
Life to Date Values
Year to Date Values
Utilization Rate LTD
End of Year Trends
End of Year Targets
Other Key Metrics to Consider:
- Run Rate (Bot estimated annual value at 100% UR / 12)
- New Value EOY Targets vs Accumulated Value EOY Targets
2nd
3rd
Confidential and proprietary materials for authorized Verizon personnel and outside agencies only. Use, disclosure or
distribution of this material is not permitted to any unauthorized persons or third parties except by written agreement.

4. AWS Services Consumed
Availability Zone #1
https:/ Entry URL
security group
C: drive volume
Data (D: Drive) volume (EBS) Amazon EBS
snapshot
EC2 instance
Control Room App
KMS
encryption
keyApplication
Load Balancer
security group
RDS SQL Server
• Control Room – 3 node
cluster EC2 instance using
Windows 2016 Server AMI
• Database - RDS SQL Server
• Creator/Runner – EC2
Instance using Windows Desktop
Image AMI
• AWS Security Group
• IAM Policy and KMS
Encryption
• EBS Volume and
Snapshot, S3 Bucket
• Elastic Load Balancer –
App LB for Control room
application cluster
S3 Bucket
security group
C: drive
volume Data (D: Drive)
volume (EBS)
EC2 instance
Creator/Runner App
KMS
encryption
key
S3 Bucket
Amazon EBS
snapshot
Confidential and proprietary materials for authorized Verizon personnel and outside agencies only. Use, disclosure or
distribution of this material is not permitted to any unauthorized persons or third parties except by written agreement.

5. AWS Automation Anywhere Instances
AWS Instance layout along with AWS VPC, Availability Zone and Security Groups
Confidential and proprietary materials for authorized Verizon personnel and outside agencies only. Use, disclosure or
distribution of this material is not permitted to any unauthorized persons or third parties except by written agreement.
Availability Zone – us-east-1a
App security group
DB security group
LOBn AA
Runner 1
Virtual Private Cloud
Availability Zone – us-east-1a
LOB2 AA
Runner 1
LOB3 AA
Runner 1
LOB1 AA
Runner 1
. . . .
. LOBn AA
Runner 2
Availability Zone – us-east-1b
LOB2 AA
Runner 2
LOB3 AA
Runner 2
LOB1 AA
Runner 2
. . . .
.
LOBn AA
Creator 1
Availability Zone – us-east-1a
LOB2 AA
Creator 1
LOB3 AA
Creator 1
LOB1 AA
Creator 1
. . . .
. LOBn AA
Creator 2
Availability Zone – us-east-1b
LOB2 AA
Creator 2
LOB3 AA
Creator 2
LOB1 AA
Creator 2
. . . .
.
AA Control
Room Node 2
AA Control
Room Node 3
AA Control
Room Node 1
RDS AA Control Room DB

6. AWS Re-Hydration – Control Room
Confidential and proprietary materials for authorized Verizon personnel and outside agencies only. Use, disclosure or
distribution of this material is not permitted to any unauthorized persons or third parties except by written agreement.
Node 1 - Oct
Node 2 - Nov
Node 3 - Dec
Node 0 – Oct
Node 1 - Nov
Node 2 - Dec
Node 3 - Jan
Node 1 - Nov
Node 2 - Dec
Node 3 - Jan
Node 1 - Nov
Node 2 - Nov
Node 0 - Nov
Node 1 - Nov
Node 2 - Dec
Node 1 - Nov
Node 2 - Dec
Non Prod Prod
January
Node 1 - Nov
Node 2 - Dec
Node 3 - Jan
Node 0 - Nov
Node 1 - Dec
Node 2 - Jan
Node 3 - Feb
Node 1 - Dec
Node 2 - Jan
Node 3 - Feb
Node 1 - Nov
Node 2 - Dec
Node 0 - Nov
Node 1 - Dec
Node 2 - Jan
Node 1 - Dec
Node 2 - Jan
Non Prod Prod
February
1st
15th
30th
1st
15th
30th
Node 1 - Sep
Node 2 - Oct
Node 3 - Nov
Node 0 - Sep
Node 1 - Oct
Node 2 - Nov
Node 3 - Dec
Node 1 - Oct
Node 2 - Nov
Node 3 - Dec
Node 1 - Sep
Node 2 - Oct
Node 0 - Sep
Node 1 - Oct
Node 2 - Nov
Node 1 - Oct
Node 2 - Nov
Non Prod Prod
December
1st
15th
30th
Rehydration of Control Room will be done by removing a node (RED) out of the cluster and introducing a new node (GREEN) with latest AMI.

7. Summary
Confidential and proprietary materials for authorized Verizon personnel and outside agencies only. Use, disclosure or
distribution of this material is not permitted to any unauthorized persons or third parties except by written agreement.
1. Strategic program alignment and governance with enterprise partners
2. Development of deep data analytics and key performance indicators
3. Establishment of streamlined process for federated bot development model
4. Implement security / legal / risk engagement and control
a. Required audit review and documentation along the journey
5. Automate infrastructure provisioning and assignment per request
a. Service Now
b. Jenkins infrastructure builds within AWS
c. Manual control room assignment/provisioning for the time being.
d. Automated usage checks to ensure resource utilization - re-claim unused assets.
6. Validate savings targets are met and adjust accordingly for proper ROI