PROOF OF CONCEPT GUIDE

Table of Contents
1 Proof of Concept Overview.....................................................................................................................................3
1.1 What Is A POC?..............................................................................................................................................3
1.2 What Options Do I Have For The POC?.........................................................................................................3
1.3 What Do You Need To Prepare In advance of the POC..................................................................................3
1.4 What Will Be The Output................................................................................................................................4
1.5 POC Process....................................................................................................................................................4
1.5.1 Kick-Off..................................................................................................................................................4
1.5.2 Scope.......................................................................................................................................................4
1.5.3 Technical.................................................................................................................................................5
1.5.4 Scope and Technical Readiness...............................................................................................................5
1.5.5 Automation Workshop............................................................................................................................6
1.5.6 Next Steps...............................................................................................................................................6
2 Process Outline........................................................................................................................................................8
2.1 Use Case Overview.........................................................................................................................................8
2.2 Business Process (Process in terms of people and organizations)....................................................................8
2.3 Technical Process (Process in terms of input, output, and processing)............................................................8
2.3.1 Steps........................................................................................................................................................8
2.3.2 Inputs.......................................................................................................................................................8
2.3.3 Outputs....................................................................................................................................................8
1 Proof of Concept Overview
1.1 What Is A POC?
Proof Of Concept – essentially the aim is to test feasibility to automate your systems using Automation Anywhere
client in a short period.
The best type of POC is one that demonstrates the ability to conduct Input and extract actions on your key
systems, if this is possible, anything involving that system is possible, regardless of how complex the logic required.
Where we are building a process as part of the POC this is purely to demonstrate speed of development and system
interactions, we do not provide any official training or ongoing support post POC completion.

1.2 What Options Do I Have for the POC?

We are flexible per each customers requirements and will work with you to identify your ideal solution,
however below is a rough guide of things to think about.
 Development Method:
o Self-driven – Customer conducts POC build themselves with our support as required, we will offer a
maximum of 21 hours support as needed
o AA Drive – We will conduct the POC development, we are happy to have an audience if this is your
preference, however main focus will be building the required use case,
 Presence Needed:
o Onsite – You require the AA resource to be on site with you for the POC (we will come onsite once
for a maximum of 3 consecutive days)
o Remote – You require the AA resource to deliver your POC/Support without coming on site, think
about your apps accessibility outside your network and whether this is an option for you, maximum of
3 consecutive days.
 POC Type:
o Production Ready Process example – available for a single small process only, will include error
handling and variation handling for anything we see in the process, also will include analytics
reporting
o System Integration test – Purely aims to demonstrate read/write access to your key systems from
Automation anywhere – there may also be time to show a quick process build
o Complex/long process – we will build as much of the process as possible within allotted time to give
an indication of speed of development, the output won't be a production ready bot and the solution
shouldn’t be run post POC completion, you will of course have the video for ongoing reference

1.3 What Do You Need To Prepare in advance of the POC

 Identify the processes/systems you want to use for the POC
 Define what success looks like
 Installation of the software – We will provide guidance and support remotely to install as needed, we
suggest a standalone (i.e. single machine) setup for the POC as we aren’t able to provide
Architecture/Infrastructure advice as part of the POC.
 Prepare your process/systems experts to be ready to support the POC & any calls – This ensures the
most productive POC’s
 Ensure relevant sites and systems are accessible from the machine being used for the POC
 Ensure access is available to the meta bot store
 Ensure the user ID being used to conduct the POC has relevant rights to conduct installs and downloads
or that you have someone readily available throughout the POC that has this access.
1.4 What Will Be The Output?
Insight into how the development happens, a video of the automation/s running, we will also leave you with the bot’s
we created, these are for your reference only and they should not be ran post POC and are unsupported.
1.1 POC Process

Preparation
Automation
Kick-Off Scope Next Steps
Workshop
Technical

The POC process includes several steps as shown in the diagram below.

1.1.1 Kick-Off
The kick-off meeting includes discussion of objectives, business processes, POC process, and the logisitics of the
POC. Client should come prepared with a processes or potential processes for automation and possible dates for the
POC. The Sales Engineer will listen to the process and provide consultation on the type and scope of processes to be
included in a proof of concept and will go over the remaining steps to prepare and execute the POC.
Agenda includes the following:

 Objectives
 Process for Automation
 POC Process
 Logistics
o Location
o Date/Time
o Attendees

1.1.2 Scope
Clearly identifying all steps in the use case is important to ensure time spent on automation and not on determining
how the use case is carried out. The following steps may be taken in preparation to ensure sufficient detail is captured
prior to beginning automation.

 Process Selection (Optional) – In some cases multiple processes or no processes have been identified. In
both cases Automation Anywhere can provide consultation on the processes that make good candidates for
Robotic Process Automation and on what portions of those processes may be completed in the time available
for a Proof of Concept.
o Manual and Repetitive – Processes that are performed manually and repeatedly.
o High Volume – High volume processes may generate higher ROI and justify a better business case.
o Rules Based – Processes with an operations manual, training in specific procedures, and/or
compliance regulations may make a good process for automation. In cases where creative decision-
making is required consider if any portion of that process has a small number of common outcomes. If
so, then that portion of the process may make a good RPA candidate.
o Structured Data – RPA generally uses structured data where the format and type of data is known. In
cases where data is unstructured consider if there is a portion of the data that commonly adheres to
 one of several formats. If so, then that portion of the data could be automated with RPA and
consideration may be given for cognitive technologies to automate the remaining data.
o Front End and Back End – Much of the value of RPA comes from front end automation – the
ability to automate a process as-is without changes to underlying systems. Automation Anywhere also
provides back end integration including database, ftp, web services, and API’s.
o Key Systems – Automating a process that interacts with key systems shows Automation Anywhere
can successfully interact with those systems.
 Demo Presentation
o Client presents a demonstration of the process selected for automation.
o Automation Anywhere records this meeting and utilizes it in documenting the process within this
POC Client Guide in cases where client documentation is not available.
 Documentation
o Client provdes detailed documentation OR
o Automation Anywhere creates an outline of process steps based on the recorded demo presentation.
 Scope Verification
o Client and Automation Anywhere agree on the steps to be included in the POC.

1.1.3 Technical
The goal of the installation step is to get Automation Anywhere installed in Client’s environment with access to test
systems. The following steps are to ensure completion of that goal:

 Client Environments
o Client deploys VM’s and VDI’s for Automation Anywhere software
o Client procures a system for the Sales Engineer to use while onsite. (typically, a laptop)
o Client secures bot test accounts on Active Directory and all test systems. This account will be used
when installing Automation Anywhere and when connecting with target systems.
o Client ensures test systems have test data available. Where multiple systems are required please
ensure the test data is consistent across systems.
 Software Download
o Client registers for an account at https://support.automationanywhere.com/
o Client notifies the Sales Engineer of the registered user’s email address.
o The Sales Engineer requests download authorization from support services.
o Client receives email granting download access.
o Client downloads installation files.
 Evaluation License
o The Sales Engineer requests a POC Evaluation license to support the POC timeframe.
 Software Installation
o Client installs the software and communicates with the Sales Engineer for support.
o The Sales Engineer support the software install as needed.
 Technical Verification
o All requirements in the Readiness Checklist have been met including a walkthrough of the target
systems to ensure test data across all systems support the use case.

1.1.4 Scope and Technical Readiness

 Readiness Call – Includes business and technical resources and is typically held 1-2 weeks prior to the
Automation Workshop. The following are verified in this meeting:
o Scope – A final confirmation of the steps to be automated is reviewed. Steps may be documented in
this guide or in Client provided documentation.
 o Technical – The Readiness Checklist at the end of this document is used to verify the following:
 VM’s and laptops are configured
 Test Accounts are setup on test systems
 Test Systems are accessible from the VM or laptop
 Test Systems contain the data needed to complete the use case
 Automation Anywhere is installed, is fully configured, and is able to access and record test
systems

1.1.5 Automation Workshop

The Automation Workshop may be conducted in-person or remote and includes the following:

 Kick-Off and Verification

o Discussion of objectives, success criteria, and the process for automation.
o Verification of the environment to ensure environment functions as expected.
 Bot Creation
o Automation Anywhere and Client work together to create bots that automate part or all of the use
case.
 Demo Recording
o After all bots are complete, Automation Anywhere records a demo of the bots executing the process.
This demo is utilized in the final presentation.
 Final Presentation – The final presentation is an opportunity for additional stakeholders to be informed of
POC results and the Client team’s initial evaluation of Automation Anywhere. The presentation may include
some or all of the following and may be delivered as a formal presentation or conducted as an informal
discussion:
o RPA Overview – Automation Anywhere can present a brief overview of RPA concepts for attendees
not involved in the RPA evaluation process and unfamiliar with RPA.
o Objectives and Success Criteria – Objectives and Success Criteria as defined prior to the workshop
and how those criteria were met.
o Use Case – Review of the use case that was automated.
o Business Impacts – Additional impacts including ROI, staffing, and support may be discussed in the
final presentation.
o Next Steps – Automation Anywhere and Client review open questions and steps to be taken following
the workshop.

1.1.6 Next Steps

Following the Automation Workshop Automation Anywhere may have outstanding questions and other actions for
follow-up.

 Open Questions
o The Sales Engineer researches and responds to Client with answers to open questions including
documentation where appropriate.
 Support
o In some cases, Automation Anywhere may provide additional support to members of the Client team
who continue to build bots after the workshop.
 Evaluation
o Client and the Automation Anywhere Account Manager discuss next steps from a commercial
standpoint.
2 Process Outline
2.1 Use Case Overview
Objective:
Description:

2.2 Business Process (Process in terms of people and organizations)



2.3 Technical Process (Process in terms of input, output, and processing)

2.3.1 Steps


2.3.2 Inputs
 <DOCUMENT INPUT>
 <SYSTEMS INPUT>

2.3.3 Outputs
 <DOCUMENT OUTPUT>
 <SYSTEMS OUTPUT>