Your Architecture Setup for Automation

Best practices to follow for an on-premises robotics deployment.

Do you know that globally 30 to 50% of all robotics projects fail? A significant reason for this is poor architecture set-up. Don’t fall into this trap.

Read this guide to two Blue Prism and UiPath, discover their functions and merits, and find out what not to do.

Blue Prism Setup

Your Architecture Setup for Automation 2
Figure 1: A typical Blue Prism architectural setup. Coloured swim lanes represent an independent virtual machine. Red = PROD and green = DEV

The Blue Prism architectural setup can be complicated. Fortunately, here at Synpulse, we’ll help guide you through it.

Figure 1 above shows the six virtual machines (VMs) that are required in an ideal solution and how they interact with one another. There are three core environments. One of the most vital things to keep in mind is that each environment is divided into test and production environments, with the former dedicated to the initial building and testing, and the latter committed to running the process live.

The interactive client on the right-hand side of Figure 1 is where the main bulk of the configuration is performed and where the developer will spend most of their time. There should be no reason to interact with either of the two other environments while in the development stage of the project.

The run-time resource on the left-hand side of Figure 1 is where the process will run in live mode.We suggest keeping access to the run-time resource as limited as possible. There are technical means available to avoid this

The application server VM in the middle of Figure 1 is the environment that usually hosts the SQL database and essentially moulds the three different environments together and directs the flow of information from the databases to the other elements of the architecture. Although you could theoretically develop in this environment, usually no configuration is to be done here.

The main benefits of splitting the architecture into several environments include ensuring the confidentiality, reliability, and scalability of your RPA solution going forward. It will also enable you to get your RPA project off to a swift start.

Avoid pitfalls & read the full version of this article, available as a whitepaper.

UiPath Setup

Your Architecture Setup for Automation 3
Figure 2: A typical UiPath unattended architectural setup. Coloured swim lanes represent an independent virtual machine. Red = PROD and green = DEV

We’ve talked about Blue Prism, the first RPA tool of its kind. Now let’s move on to UiPath, the most popular RPA tool by revenue. There are similarities and differences with the two RPA tools. Figure 2 above depicts a typical setup that Synpulse usually encounters on the client site.

Similar to Blue Prism, an on-premises set-up will have an SQL database at its core. Here, all of the information needed to build and deploy automated solutions is stored and called upon when executing commands. Here it’s advisable to split, with a test/UAT SQL database mirrored by a PROD SQL database running in production guise. This design makes sure that you only have production-approved processes communicating with live applications on the client site and that once processes have been built and successfully tested on the non-production servers, they can be released to the production database to run in production. It also guarantees reliability and scalability.

The orchestrator plays a pivotal role in the overall sequencing of processes. It communicates with the databases to pull out desired information needed to run automations. It then directs the recovered information to other elements in the architectural system. There’s typically a production and non-production orchestrator.

UiPath Studio is where you perform the main development. Typically, there will be a production and non-production instance of this module. Conversely, there will be no studio on the production VM; only what is known as a UiPath robot. Like Blue Prism, the UiPath orchestrator can accommodate multiple attended and unattended robots. The UiPath robot can be thought of as an executor of unattended processes. It communicates with the production orchestrator and will run processes with no human intervention via a trigger or schedule.

The final element of the “best of breed” UiPath architectural setup is the production-level VM that houses applications such as Tableau or Indexer. It’s optional but highly recommended. It can be very useful for an organisation to have access to logs for trouble-shooting and dashboarding for management information to help guide a business to make informed decisions. It can also be vital for an organisation when conducting audits to have this data, so for most clients this is a must-have.

This setup is widely regarded as the most scalable deployment at a commercial client, as it allows solutions to be controlled in a contained environment, monitored as accurately as possible, and developed safely without affecting business-critical applications and processes.

If you’d like to find out more, contact us or download the PDF with a more comprehensive version of this article

Alternative Designs and Their Drawbacks

The other potential deployment method that UiPath offers is an attended solution. This is where the solution is launched, managed, and located on the local PC of the subject matter expert (SME). A disadvantage of this setup is the fact that it requires human intervention and can be ineffective at scaling an automated process whose goal is to take work off SME hands. In our experience, choosing the unattended solution simply because it’s cheaper can end up being a costly mistake. Time and money can be saved if you consider the long-term scalability of the setup.

Your Architecture Setup for Automation 4
Figure 3: The main benefits of the “best of breed” robotics structures and the impact they have on your architectural landscape.

Closing Remarks

A superior architectural setup is crucial when preparing for an automated solution within your business. One of the main reasons RPA initiations are delayed is poor architectural setup. To ensure you avoid this pitfall, it’s a good idea to understand and follow the steps we’re described in this article.

Our experts in this topic