Session Information:

RPA, Unlocked - How to Migrate Bots from One RPA Platform to Another to Drive Increased Business Value

Is it time to break up with your RPA vendor?

Due to the large number of RPA projects that fail to meet objectives, more and more companies are looking to switch RPA platforms. However, most have been stuck with whatever tool they initially chose because re-platforming was costly, challenging, and often meant re-building your entire bot portfolio from scratch. Until Now.

Blueprint’s streamlined end-to-end migration process makes moving between any of the leading RPA vendors simple, fast, and affordable, thereby unlocking the entire RPA market.

Attend this session to learn:

• Why 2021 will bring an influx of RPA platform migration and how to know if migration might be right for you
• How to extract existing automation from your current RPA platform into Blueprint, creating a Digital Blueprint of that digital worker
• How to optimize and validate Digital Blueprints before exporting them to a new RPA solution to complete the re-platforming
• How leveraging Blueprint in tandem with your RPA tool enables you to design, build and manage high-value automation with speed and precision to scale the scope and ROI of your RPA initiatives

Session Transcript:

Thank you so much for joining us for today's webinar. We're very excited for the content we prepared for you today, and really happy to have you join us. And we're just going to wait a few more minutes just to let everyone just get logged in and get the audio setup. So, just sit tight for one second, and we will be starting the webinar shortly.

All right. Hey, everyone. Thank you so much for joining us today. We're just going to give everyone just another minute here to jump into the chat, and sorry, to jump into the webinar, and make sure they've got audio, and everything set up here. And so please just hold tight. If anyone's interested, You can pop into the chat section, where you're joining us from, we're located here in Toronto, Ontario, Canada. And we've got a beautiful day outside. So, if you're coming to us from somewhere else in the world, feel free to pop that in the chat, so we can see where everyone is joining us from today.

Oh, I'm sorry, it looks like we actually can't pop that in the chat, but in the Questions tab.

So feel free to pop that in there so we can say hi and know where you're joining us from, and we'll just wait just another minute here to let everyone get getting settled.

All right, we've got ramjets joining us from India, welcome, Ranjith.

You've got orden coming from DCA. Excellent.

All right, well, I think we can, we can get started now, We're just two minutes, past cell.

Thank you so much for everyone for taking the time to join us today, We are incredibly excited about the content that we've prepared, and today we'll be talking about how to unlock the RPA market. And so by that we mean how you can migrate bots from one RP platform to another to drive increased business value.

Just some notes on housekeeping before we get started here. And so you can pop any questions that you have at any point in the webinar, just into that question tab, and we'll be answering all of them at the end of the webinar. Our content here should run around 40, 45 minutes about. So we should have you out before the top of the next hour.

And if you just check out that handouts section of your control panel, you'll see a data sheet in there.

And that's a really great resource, we just wanted to leave behind for everyone, so that you can see a little bit more about our functionality of how we can help migrate bots from any RPA platform to any other platform. So that being said, I'd love to introduce our speaker this afternoon, we have Matt Dodgson, who is our Global Solutions Engineering or head of Global Solution Engineering here at Blueprint. And that will hand it over to you.

Thank you very much, Kate. And I appreciate everyone taking time to join us today. So I want to welcome you all for join us.

and we're going to talk to you about how we can unlock the entire RPA market by simplifying this idea of migration, of these of these digital workforces in digital workers, from one RFK platform, to another.

And this helps us drive greater business value from your automation, for your automation initiatives, and it's a topic that's definitely gaining a lot of steam for reasons that we'll get into in just a moment.

All right, so as Kate mentioned, my name is Matthew .... I head up the global solution engineering team here at Blueprint.

I support the delivery of Blueprints Enterprise Automation Suite, which is this modern, intuitive platform for scaling process automation initiatives to the Enterprise. And a Blueprint, we believe, in delivering quality solutions to customers that drive change and value for the organization.

Or, you know, we're passionate about helping teams to rapidly optimize, automate it, digitally transform their organizations.

Little bit of my background, I actually come from a background of customer service, quality, assurance, software engineering, and even product management. So I've seen firsthand, you know, the best solutions require dedication, passionate support from the whole team.

And ultimately, what supports all the best is platforms and technology to really help empower them and enable effectively.

So before we get started, I want to frame everything.

We're going to be talking about it today.

Let me just start by telling you a little bit about Blueprint and what it is we do.

Then we'll get right into today's topic and explain why there is a fast growing interest of RP platform migration and how to know if migration might be right for you and your organization.

We'll also go over why it's historically been a challenge to switch RPA tools.

Ultimately, how Blueprint is going to remove those challenges while adding value to your bot ecosystem in the process.

So and for that, I'll be leading you through a demo of exactly how to extract the existing automation from your current ERP platform into blueprint creating what we call a digital blueprint of that digital worker.

Then we're going to talk about how we can optimize and validate those digital blueprints before exporting them to a new RPA solution to complete the re platforming. And ultimately, how to leverage how leveraging blueprint in tandem with your RPA tools enables you to design, build, and manage high value automations with speed and precision that you need to really scale and scope out the roi of your RPA initiatives.

So starting off, I'd like to give you a little bit more context about Blueprint.

Today, we're going to be focusing on how Blueprint enables faster simplified RPA platform migrations. That's really just one use case for a solution. At a higher level, Blueprint is a leading provider of digital process design and management solutions to the Fortune one thousand organizations.

Global leaders from every industry are using our cloud based platform, the Enterprise Automation Suite.

In tandem with their RPA platforms to identify design and manage these high value automations with precision and ease by creating what we call digital blueprints.

Now, creating a digital blueprint replaces the need for time consuming error prone documents, like the PDD or STD.

And it drives both quality and efficiency at numerous points along the automation workflow.

So this enables our customers to spend less time designing, managing or fixing automations and more time with things that directly grow their business.

So what do we mean when we say they use it alongside the RPA tool to identify design and manage high value on nations?

Well, at the heart of our platform, it's the digital blueprint.

Digital blueprints are much more than just process models.

They contain everything you need to effectively and efficiently deliver high quality automations, including detailed process flows. All of those dependencies related to the systems, or company or compliance regulations, functional and non functional requirements, user stories, test cases, and specific implementation details that are all directly integrated into your RPA platform.

Using a Blueprint platform in our digital blueprints has many benefits, including having all the assets and stakeholders one centralized platform, which ultimately streamlines workflow and improves alignment. So you can move projects forward with speed and precision.

We have intelligent recommendations and modeling built into the platform, and integrations that really make it faster and easier to design and build automated processes, while also improving the quality of those processes and our Enterprise Analytics dashboard, which really help you prioritize and measure what's working. Managing change proactively and ultimately, sharpen scale your strategy across the organization.

Now, building automations with digital blueprints is the same, is the state-of-the-art way to achieve RPA success.

The system is purpose built to design automations in a simple, easily understandable way.

And as you can see here, identifying things like systems, actions, and parameters for any given automation task doesn't require technical expertise, and is accessible to any business user. Really started to enable something we talked about as citizen designers.

But what makes it really powerful and demonstrates the clear superiority of digital design over documents, is how the information is transferred directly into your RPA platform to accelerate development, and reduce the introduction of error, and translating the design implementation.

These are the ease and simplicity of digital blueprints. And that enables, you know, will allow a truly a lot of things like citizen developer movement.

But in all honesty, it really enables more of the citizen designer where these, in this, this platform is more readily available to drive your automation pipeline and really scale your RFK programs.

Now this is possible because digital blueprints are also loaded with other capabilities. They provide a centralized repass repository of referential automation design.

And this is information that's never out of date.

Unlike documents, they are highly configurable. You know. and they can be tied into a highly configurable review and approval workflow to ensure our stakeholders are engaged on the elements that are most relevant to them.

Another Totaly differentiating capability is to transform the process models within your digital blueprint into a myriad of different value added work products that can accelerate automation implementation.

For example, we can automatically take a digital blueprint, and generate all of the functional tests and user stories for process, so your team can focus their time on high value activities, not sitting there and writing stories and test cases from scratch, based on a PD they just create.

With that, let's dive in. let's dive into today's topic.

So there's no denying. It RPA is undeniably red hot these days and for obvious reasons.

So we won't get into we won't get into that specifically, but there is a stark underside to the cost reduction efficiency and increase quality that ARPI adoption promised.

And here's the rundown.

When RPA first came about, it was positioned as a self contained, solve all for business inefficiencies. And it was so simple.

That companies could even provide a bot for every worker out there.

Rolling out and maintaining an army of bots is actually a tremendous challenge.

And too often, the industry doesn't acknowledge the realities of this challenge, because of these glossed over challenges, over 50% of our key projects fail to meet their objectives. while 25% of companies have not achieved the breakeven point, return enough hours to the company to pay for their initial RPA investment.

But why? What's, what's going wrong? What's causing this?

Now as organizations, race to automate more and more processes, they're hitting a wall.

Mister requirements and poorly designed processes are leading to low quality brattle automations that need constantly make it consistent and constant mittens, and these tedious and expensive changes and fixes are highly reactive.

Reach that with which means that thought downtime is leading to diminishing returns in business value, as well as the inability to scale automation initiatives. Because you're too busy putting out fires, you have no time to actually build the new bots you need to need to prioritize.

To address the underwhelming Roi and challenges RPA programs are encountering, one solution that is becoming more and more common by the day, is migrating to another ARPI platform, to realize the returns that they were promised.

That's the overarching reason, but if we dig a little deeper, there are several reasons that are driving the desire to switch ARPI platforms as well.

At a closer look, what's really fueling R K programs looking to switch platforms can be boiled down to these four reasons.

The first is a failure to get back.

Are paid programs have been unable to scale automation or realize the roi they were promised because they're too busy putting out fires.

They've been burdened with crippling maintenance issues and RPA downtime due to ineffective development and design practices that produce low quality bots.

The result has been negligent returns triggering the question. Did we pick the wrong RPA tool?

Another Sharpie and other strong motivator is unfulfilled promises. RPA vendors have over promise and under delivered on the ease of our ... limitation.

The illusion that citizen developers could drive automation never materialized, and instead, expose, Frei expose, you know, many fragile automations.

Now organizations want to try their luck with a different approach that includes another RPA provider.

Third, we have organizations are looking to eliminate islands of automation.

Some companies have inadvertently set up disconnected independent automation initiatives within different business lines.

The consequences are a lack of quality, different automation design practices, and ultimately inflated costs by unnecessarily doubling down on multiple RPA tools.

In this case, migrating bought into one arcade tool is a way to consolidate all the renovations into a single platform to cut costs and streamline higher quality RRP development.

Lastly, number four, there's also incompatible version upgrades that are frustrating RPA programs. For example, there's a large segment of automation, anywhere customers that are still on version 11, and have faced significant challenges upgrading to the newer ... 2019. are. Now it's permanent, or now it's for.

Now it is known as a 360.

But with the end of maintenance for things like V 11, right around the corner, customers have been forced to rebuild bots from scratch in the a 360 platform or look elsewhere for help or tried their hand at the migration utility.

Even with all these valid reasons, driving the desire to switch RPA vendors, migrating digital workforces, has been nearly impossible because of the effort and costs involved.

Because each RPA platform describes process automations in their own way about built on one platform can't be rather than another, can even be transferred easily. Historically, the only way of switching was to rebuild your boss in the new target platform.

A prospect, so expensive and time consuming. It was shot down before it could even get off the ground.

In an informal poll that we performed on LinkedIn recently, this is exactly what we wanted to verify. We asked respondents what the biggest barriers to switching RFP platforms were by far, as you can see.

The cost of switching was the biggest blocker while we saw significant representation for other barriers like incompatible, bots and the user management effort that would be needed from switching.

Now, historically, that was the case.

But Blueprint has developed a very unique capability that I'm going to demonstrate for you guys today.

Due to the bidirectional integration and the bidirectional connection that we've established with all of the major RP platforms Lucid Blueprint also has a unique capability to support migrating.

These automations are cross-platform.

We can reverse engineer a digital blueprint from an existing automation, and then export that to a new target platform.
16:39
This is a different approach and ultimately, so much more revolutionary approach, excuse me.

It's a much more revolutionary approach, as opposed to looking at things like: I want to migrate code.

This actually focuses on migrating the design.

It ultimately this dramatically loosen.

The dramatically lowers the switching costs to enable you to move to a new platform of your choice, or simply to consolidate your automations if you already have multiple platforms.

Now, before I get into the demo, I wanna give you some, just some context on how Blueprint is able to do this, and what makes this all possible is something we call our common object model framework, Or as we call it.

Com, for sure.

This com provides an increasing catalog of services that form the granular building blocks of automation.

Ultimately, it looks across all of the RPA platforms, and has centralized the common commands and the common sets of commands that are always used.

When you import a bot, from a leaving our platform, Blueprint Convert those process automations, including their services, actions, and parameters into our common object model. There's a whole mapping, sort of, sort of mapping rules that actually facilitate that conversion.

From there, you can then further optimize that process automation in Blueprint by connecting it to any overlooked dependencies or optimizing the process refactoring, redesigning it.

All things that tend to happen as we think about moving automations and migrate.

Then, when you take this Digital Blueprint, and you export that over into a new Target RPA tool that you want to switch to, all of these services, their specific actions and parameters, are mapped directly into your automation development environment.

Through our bidirectional connection, with things like Automation, Anywhere, Blue Prism, Power, Automate, and UI path, Reality is there's no other platform on the market that has anything like this, especially when you consider how it accelerates migration, but most importantly, how, it helps reduce migration cost.

And those switching costs can be quite substantial, as you see from this analysis.

So here we took the the and now we did an analysis with quite a few customers and we broke down the different stages that actually doing the migration.

Without Blueprint migrating, robots is very time intensive.

And it's extremely manual, know, interpreting what has been built on your RFP platform, and how to re implement a digital work or another vendor platform is often a non-trivial exercise with our ability to extract a full digital blueprint from those robots. We can actually reduce the effort by as much as 75%.

When you start looking at the details of how we go through the stages of interpretation, interpreting, designed implementing, and testing. There's significant improvements that are made across the board. And ultimately, this leads to that, you know, 75% reduction of effort, and ultimately, it gets people focused on the true value at hand, which is getting that bot working in the Target RPA system, as opposed to the manual effort today. Which is, a lot of times, just trying to understand what the heck the bot is currently doing.

Again, simplifying and accelerating migrations, while cutting costs is only one use case.

Blueprint can be used to radically improve the entire life cycle of your digital workers. All of that detailed process, information and dependencies that we capture in digital blueprints provides the basis for the ongoing management of an automation across the life cycle.

We leverage that information to provide comprehensive analytics and impact analysis reporting, so you can actually prevent outages when things change, which they invariably do.

This leads to automations that can have increased productivity and substantially reduce total cost of ownership. Because high quality automation is built with digital blueprints, don't result in endless value draining break fix cycles.

That's also what I'll be highlighting as we run through the demo, which we're going to jump into right now.

So, not only will I be showing you how you can easily migrate a bot from one RPA tool to another, but I'll also call it, how you can improve that bot in the process using Blueprint and Drive much greater business value for your RPA efforts.

Yeah, all right, so let's jump into it here.

So, we're going to start with an automation here in UI Path.

This particular automation interacts with native applications like Excel, web, and, and with, you know, an image based or Surface Automation.

So here, for example, we'll look at one of the processes around sap.

Here's an example of an innovation of an image based or surface automation.

If I scroll down, let me just scroll over here.

If someone is migrating this and they didn't create it, for example, it's going to take effort to figure out what it's doing.

Here, for example, is a snippet of some part of a screen, but the screen might have like 100 fields on it, and I can't tell what it is or where it is.

To figure that out, I'll need to look at the various properties on the right and backtracked to find the anchor image, and figure it all out. And that's just for one step.

So you take this, you take this one example, and if we were doing this manually, we would probably be walking through this, and try to reverse engineer this.

This bought into a PDD, so we can actually explain to somebody, and communicate it.

Now, I'll show you the first step of how we would migrate this in Blueprint.

So first thing, we would do is login, here, So here, we are in blueprint again. Blueprint is a web based cloud hosted solution.

So I'm not working with files on my desktop. I'm logging into my environments and log into my workspace, Rama automations, Koa and what I'm going to do next.

It's actually imports that entire project file, that entire project, zip from UI path.

I'm going to grab that one particular Project file, and it's going to import the entire project.

Here on the left, you should recognize that exact same structure that we just saw in UI path.

Blueprint has automatically imported everything, including data and reference documents And even at every ... file has been automatically converted into a digital blueprint.

On Import Blueprint Parse is all the information brought in and provide some key metrics and information that help you make decisions.

For example, if you look at the process at the top of the list, you will see that it has 264 steps.

Right here.

This workflows BPA open invoice Status three, in that 264 steps or 44 decisions.

And it interacts with things like web app, for example, information like this can be help, can really help with decisions as to what to focus on first, for this example.

And here we're gonna jump into one of those things.

We wanna look at things like this, Q two R login.

Here is an example of what a x.a.m.l.

file, or what one of those workflows in UI path would convert into, and specifically, this is what we would refer to as a digital blueprint.

If I click on one of the steps, it takes every, so first of all, the Digital Blueprint takes every step in that automation, and it turns it into a unique step in one of these digital blueprint flows.

Every single step in this flow.

You can see, it's not just the process information, in terms of the overall sequence of steps.

We actually have all the underlying parameter information as well for each step. So all the actual x.a.m.l. code and the parameters that are parsed in are actually brought into Blueprint as well.

Now let's hop over to a different process, for today's example. We're gonna go over to this sap Process. Now, this is that surface based or image based service automation.

Now, we need to activate this blooper to unlock a whole set of powerful features that we can then use.

So what I'm going to do is first things, first is I'm gonna convert imported process to a digital blueprint.

Now, with all the features available, I'm going to use our intelligent process feature.

What this is going to do is this is going to allow me to humanize and make this process a little bit more readable.

So, the first thing that did was to make this process a little more easier to understand.

So, for example, things like, you know, type in an sap code into the highlighted area, no press enter, type in a dark number, so forth.

Blueprint also has the images that are pulled from UI path.

Since this is an image based automation, all those images were attached, these different blue steps, The system steps.

These, of course, go to the responses to help illustrate how the application responds to digital work or doing things.

This makes the process far more understandable for everyone, and if you recall, this allows us to jump directly from a working automation, into something that's easily understood a digestible for all users in a matter of minutes.

Now, if we don't even know what this process might depend on, we need to understand what are the things, you know, what are the things could this impact or effect. This is where we turn to things like intelligent recommendations.

Blueprint is actually going to look through and parse all the different automations and information that has across the different bots. It's cataloged. It starts to suggest and recommend things.

So based on the information in this process, for example, blueprints has found a similar process component right here. This sap PT code enter.

Also, that happens to be a couple of regulations related to that process it found, and if those are related to the similar process, there's a good chance that they should apply to this one.

So, if we find something that we want to use, we can simply click on it.

and then we can select it and actually, just start to link it to this automation at hand.

And this is how Blueprint allows you to not only parse in reverse engineer the designs out of these working bots. but then start to do more with it. And really start to leverage the collective knowledge and the tribal knowledge that's baked into these automations over the many years you've been working on.

But here, under the relationship tab, we can see how this process is now tied to either regulations, policies, rules, requirements, or even other parts of automation, that it may call into.

But finally, Blueprint can take this entire set of blueprints that were improved.

And it can now automatically populate them into the Destination R K platform, meaning, I can take this entire digital blueprint that we've looked at, I can now take it, and I can actually export it over to Blue Prism, in this case.
27:28This will take everything we've looked at and it'll package it up into a BP release file that can then save.

And if I moved from Blueprint over into Blue Prism, I'm going to sign in here and let's open up this particular automation COHE project.

Now blueprint, when it exports and creates this BP release file, it automatically populates that entire digital blueprint, any digital blueprints that you packaged up into this standard Blue Prism template.

Now I'm going to jump into a few of the sub flows that we sent over, what is specifically that to, to our login, and here's what that process looks like.

So for example, we can see all the detailed steps in that process that were in the Digital Blueprint, have now been turned into detailed steps within Blue Prism, which is great, but if we start to look at these individual shapes and these individual parts of this process, we can see some of the additional details.

So, for example, if I click on this one item, you can see that variables have come over, you know, like this particular URL for the web application.

But fractions, Just as a note, if we have actions that we're unable to map, so if in this car model, there was a custom action or set of actions, that we didn't know how to map, that's not a problem.

We still send, over all of the source XML, all the source code from the original RPA platform. So things like this Retry Scope Notes field, is actually where, what, what we'd actually populate. We would create a notes box, will actually all the source information. But for others, things that can be mapped by open up the things like the open browser.

We actually create the needed business objects and map what parameters we're able to.

So in every case, Blueprint is providing all of the source information.

And the kom model that we're talking about, that calm framework, is actually what's facilitating the mapping of these original commands into the command structure and the parameter structure within something like Blue Prism.

Now, if I click on Open Browser, again, I'll actually go into the object Studio here, we can actually go into the business object created in this case, And here it is. If we click through, we can see the different elements, the different tabs, and the actions that are needed to support this particular process.

That was a quick example of a quick overview of really what Blueprint is doing when it comes to migration, but I wanted to give you a bit of context as well.

If we fast forward, and we think about, you know, the migration, or even, you know, building new bots after.

We've completed tests and deployed those automations, the digital blueprints and the information we brought in. It's going to continue to deliver value throughout the life of that automation.

It's really going to help streamline changes and really ensure the continued compliance of these automations.

So here for example, we have the Blueprint dashboard that's going to notify us of things that are changing that, might affect their automations.

These notifications are going to be summarized here at the top. They're broken down by different categories, it's for example, if we wanted to see things like Regulations, we can drill into that.

For those who only want to see things like the high severity, we have one particular regulation we want to look at.

But the key within Blueprint is, whenever you have something that's going to change, whether it's a regulation system, or requirement, or rule, clicking on that item, it's going to actually instantly notify you and show you a live impact analysis view.

And here you can see truly the change and the impact of that change that it'll have across all the different automation. So this one regulation when it changes or is going to be subject to change it can impact and ripple through all of the different automations that we've migrated or actually up and running in Blue, Prism or whatever target RP platform we have moved to.

Blueprint can then go a step further and actually alert and notify these owners to take action.

So, we can then take blueprint and actually click on this little notification window, pop it up, put in a message and actually send it out to the owners, letting them know this of this change, as well as the teams as to what is going to be coming down to what automations are going to be impacted.

Now that, you know, always have been alerted, we could even switch chairs in this case here. I'm going to switch over and login as one of these owners to see my notifications.

Because on the receiving end, whether I own these processes, or I take ownership of them from an ... perspective.

As the owner of this particular sap process, I can see my alert and this whole personal dashboard that identifies a particular regulation that's changing, and which automation will be impacted, that I need to look at, and the associated comments that come along with it.

So, with everything linked, I can now go explore this change, and see exactly what it is, and ultimately, even navigate into Blue Prism, right, to the affected part of this automation.

So, these digital blueprints serve as a means to translate these automations. But, ultimately, they also serve as a catalog and a system of record that we can use to really manage these automations going forward.

So, to sum it all up, if you want to make a leap to another RFK platform, we can dramatically lower the switching costs, so that you can easily and cost, effectively, manage that migration, and, once again, you can leverage the power of these digital blueprints, and this common object model.

Digital blueprints are also a substantial leave for just in general around the RPA design and development that really helps accelerate your bot development while increasing quality.

And this, which usually ultimately it was required, is a tradeoff, but that, the, but you no longer need to do that Blueprint, is able to help you build better bots, manage those bots, and migrate those bots. And this is for our customers, what's been able to drive ROI across the board from whatever part of their business case? Whatever part of the use cases or automation life cycle, where they're currently focused.

So with that, I really appreciate you guys letting me take you through that. I wanna pause, open it up for any questions you may have. As Kate mentioned, I think there's a question tab that everyone has access to, so I encourage you to put any questions in there. And I'll pause it a moment here to take any questions that you guys may or may be curious.

All right, excellent. That we had actually a bunch of questions come in throughout the course of the webinar, so I'll start with those.

And so Roger, she has asked, Can we can export from any of the big four RP providers and convert to any of the others?

Yes, you can.

So we've been actually working through quite an excessive list of mapping rules across Blue Prism, automation, anywhere, UI path, and power automate, We have different levels of, of expertise in each of them. And a lot of that is based on what we've been doing with customers and different partners across the industry. So absolutely.

Great.

And Dan, Harish has a few questions in here.

So they've asked, um, from UI path to Blue Prism, will code ... also be taken care of in the sense of main pages, subpages, exception pages?

Yes, it will. So, one of the key things, when you actually import UI path project, just to give you an example, or in UI path, it will actually bring in all the separate, you know, workflows, frameworks, main flows, exception flows, and it will parse them out as different flows of digital blueprints. And it will link them altogether.

So all of the modular ization that you built into your designs are actually brought into those digital blueprints and ultimately, ultimately, pass through into the new RFP platform.

And that, that, you know, in UI path, that's done through a bunch of different x.a.m.l., and automation, anywhere that's sent across, maybe a bunch of ATM axes where you have a master taskbar that's calling sub tasks bots.

The same mechanism holds true, and that's one of the key things with using digital blueprints.

OK, excellent and a second question here and from here, as well, has asked, What percent of code rework is required post migration based on your experiences? Yeah. So, that's a great point. What we, and this car model that we built, it focuses on, again, the idea of a common object model, is it looks across all the RFP platforms. and it looks for the common commands. What are the things that every platform has? You know, the MS Excel, The words that? The file management. And so, a lot of the main things that get mapped, or all of the common things you do. There's always some custom.

Code. There's always some custom stuff you're doing for an sap here.

Other Applications, that usually has to be reworked. That's where you actually get the source code. So let's say you're going from UI path to Blue Prism. You'll actually see the source UI path XML in Blue Prism.

So what we've seen, know, what a range of rework is within Blue Prism if you're migrating from UI path.

But you'll have anywhere from, like, you know, 20 to 30, 40% rework depending on the complexity and the customization.

Again, that's just a variation, it's usually an 80 20 rule. We see 80, you know, 70% of the commands are always those common commands that get mapped.

There's always 20 or 30% of commands that still need to be reworked.

And that's, you know, to give you our perspective, we're not aiming to do 100% command mapping. I don't think that's a reasonable. I don't think that's realistic for anyone. So if you ever talk somebody, they're like, oh, we can backup map 100% of commands.

You are being light, because it's not ever going to be possible. The goal here is to map the design, bring over all the source, and recognize that there is always somebody work that has to be done. But to minute, minimize that to the customized and bespoke things.

OK, great, and I have a couple questions here from she'd be as welcoming for yourself.

We've got, first question, does it map the control Center data and the work keys Assets, environment session variables?

Great question. Unfortunately, at this time, it does not. So, we focus purely on the, the process object and bought layer. We're not going into the work queue and controls anyway.

And let's see, another question from the same person, or the conversion is largely based on the repository that Blueprint has and will get better as more things are added.

So, it is based on the repository, the Blueprint has. The Blueprint repository starts to improve your ability to centralize all your designs. What I mean by that is, you can start with an empty blueprint repository and migrate your bots.

It will 100% work out of the out of the box, because that's what it's designed to do, it brings in your source bot and helps you convert it over.

However, as you migrate more bots, and you start to get a larger repository of rules, regulations, and policies, every bot you migrate is going to benefit from all that previous knowledge, so that, if that makes sense. So, the whole idea is to think about, every bought you built.

Blueprint helps you just start to leverage and re-use all of that tribal knowledge and subsequent automations, either migrating or even designing new ones.

Great, and last question here from that she had put in, does the code used for customization get migrated as well? How's that interpreted?

It does get migrated. It is not going to be mapped. So, custom code, again, one of the common logic model is not yet to the point is going to pick up custom code. And that's something that we've, again, made a meaningful choice there not to go into. So, we actually bring that over as source code. We will actually send that. Let's say it was a source.

The source of RPA was in UI path.

All the XML that went into those steps that are custom steps they will come over and be note fields over in Blue Prism with all the custom XML so that will be the rework that was asked in a previous question there's going to be focused on.

I've got a couple questions here from a couple of different individuals around electors.

How do you take care of selectors? When you migrate from automation, anywhere to Blue Prism? There's no automated way to handle that today, so you measure the success and 70% of the coding today's mm. Hmm hmm, hmm, selectors are a big, big topic for us?

We've been working tirelessly to standardize a selector.

Was Sarah, the centralized, the selector, storage is quite easy.

With different RPA tools, obviously, we're seeing how they store selectives, definitely. Now we parse them.

So selectors are something that are coming over. They are being parsed in the Common Object model.

What we're seeing is we work with some of our partners, is, we're able to improve how we catch all the different types of selectors, all the different ways that they're parses stored.

So it is something that is being handled.

But it is something that we are learning and discovering more as we start to work more Automation day, whereas one, I know that we still have some, some learning to do, and how to improve that, and make it even better and more robust.

And another question here from ....

Do the companies provide their automation platforms in a standard format like XML or did Blueprint Build some custom parser to read their automations?

So we provide, we build custom parser to read the automations. So we've actually developed a whole discipline, we have different teams that actually have developed skill sets across the entire RPA language. That from, obviously, the main for Blue Prism, a UI path or automate. We have unique, we have a parser that brings those and converts them into digital blueprints so we're able to work with those file formats. We've been partnered with the ...

Platforms, so they've been helping us understand and parse those correctly, but they have not created a standardized XML.

And that's where these digital blueprints are almost kind of standardized, common language across all the RRP platforms.

Because it allows us to actually move information across RPA tools.

Perfect.

Just a couple more questions here, Matt, We've got, uh, says, arrived a little bit late for the webinar. I'm not sure if it was, His question is, why should I consider migrating my RPA tools that are already established from one of my RFPs that are already established from.

one tool to another.

Very good question, so it was something that we did cover a little earlier.

To summarize, if there's the migrating of RPA is something of, I don't say new revelation, but it's something that's happening as the RPA landscape continues to grow, become more commoditized.

So, for example, we have systems like power automate that are coming in and making themselves much more available and widely available to customers.

So, cost, you get organizations where they're looking at the spend, know, their, their yearly license, that they have to pay, or the recurring, no contract paid to each of these RPA vendors. And they're looking at just simply, how we can reduce that, spent, how we can reduce that cost. So that's one factor. We have quite a few companies, in quite a few organizations out there that, by virtue of, you know, mergers and acquisitions, or just how their RPA grew across different lines of business, they have multiple RPA tools. So it's a consolidation effort.

And then in some cases, you have organizations that are just trying to, they believe that they pick the wrong platform to start with, and they want to go to a different platform, be it, because some platforms have recently gone public, or some platforms are doing things like migrating from on premise to a hosted option. So there's a variety of choices in factors. We're by no means saying that you must migrate RPA. It's just a use case and a scenario that's coming up a lot more in the industry.

And it's something that we've been helping customers with for quite some time. And we just wanted to share with you that, so hopefully, answer that within that answers your question, and I definitely encourage you to go back through the presentation as we share this out, because it does touch on some of those things in more detail.

Yes, exactly. So, we will be sharing a copy of this recording, and you'll probably receive it in the next day or so, just so we can get it cleaned up, and make sure we get it sent out to all of you.

A few more questions here, and some around licensing, So is this capability included in the Enterprise Automation Suite, or is it a separate license? And then, and then another individuals have asked, how is the licensing, is it per user?

Very good question. So everything I've shown you today is part of Blueprints, Enterprise Automation Suite.

It has one licensing model, everything is included in there. It is not licensed by user, it's actually licensed by what we would call a digital blueprint. So you probably saw in the demo, I had to convert one of those processes that we wanted to migrate into a Digital Blueprint.

That was actually the Act of me using a license. So essentially, these digital blueprints are going to start mapping to your individual automations or processes.

There is an unlimited user package, meaning you don't, you can have as many people in the system as you want. You can even import as many parts as you want, but when you start migrating those automations or you start building new automations, that's when you start to consume those digital blueprint. So the way blueprint's license is by the digital blueprint. And Blueprint is actually sold similar to the RFA platforms in packages of digital blueprints.

OK, and real questions here and question from ..., how do you migrate a meta by an automation anywhere, which is locked and you can't get to the source code?

Very good question. So, in automation anywhere, in most of these automations, what you're going to be actually doing is importing you know, the source file.

So, for example you the exporting ATX, you'll be important that ATX when it's locks as long as you can open the T max, you can usually import it, that's something that, if, I mean, again, if you have an example or scenario you'd like to go through, I encourage you to reach out to us. I'd love to take that, take you through that example, but in most cases, because it's all file based, you can actually import them as we start to get into more of the systems, like a 360 or power automate. That's where you can get into a bit of the locking situation. But we haven't encountered that as of yet.

So in the scenario of a meta bot in, you know, automation anywhere, you would just be importing the T max file for that matter, but it would bring it in.

Excellent.

Um, we've got here, from Shimmy, do you need to get trained on Blueprint, like any other RPA platform, and do you have a trial version?

So Blueprint does have training. It is, it is not to the same level as an RPA tool, because RPA platforms, again, their development environments. So there's a lot more training. Blueprint is more akin in more in line with what people are used to doing. And things like, Word, Excel, Visio, PowerPoint. So the training and enablement for customers is a, like a two week engagements that we have with teams, we will get them in there, we will get them onboard, It will take them through training. And enablement and they will be off to the races. Very quickly.

And sorry, I forgot the second part of that question, do we have a trial version?

Blueprint does have, does not have a free trial version on our website, but we do do perform validation exercises and provide you exercises with books today. So if you're curious and interested in how we can help you, I encourage you to reach out and we would definitely work with you guys to help set up an engagement. So you could go through and validate that blueprint is the right fit for you.

And she's got a question, could the RPA companies encrypt these files and make it unreadable per blueprint?

They definitely could, There definitely could be some encryption. And that's part of why we partnered with directly with the RP platforms. With many of those are key platforms. Blueprint is filling a gap in there, in that they are having their tool chain. So you look at systems like UI Path that have a whole suite of tools. They have from discovery tools.

They have, you know, obviously the UI path Studio, but they don't have anything in this space of design.

So with every one of these RP platforms, we have, you know, a very healthy partnership at the technical level and the product level that keeps us engaged. And allows us to work with those companies to help us.

Not only improve their customers, but in some cases help them, you know, migrate competitive products and competitive situations over to them and vice versa.

Um, so, yes, there could definitely be encryption that could come along. Part of our partnership and engagement with these customers is to work with them Because, at the end of the day, we're trying to make their customers more successful and ultimately get them to leverage the licenses that they procured and get them working in the digital worker farm. They have set up.

Excellent.

Last call for questions here.

All right. Well, it looks like that's it for today. Well, thank you so much, Matt. That was a fantastic presentation.

And for everyone on the line, I, thank you so much for giving us your time this afternoon, or whatever time it is, where you're coming to us from. We will be sending out a copy of the recording shortly, so keep an eye on your inbox tomorrow and if you have any questions, you can reply directly to that e-mail. We'll put a demo request link in there, or you can reply to info at blueprint ...

dot com and we would be more than happy to know, do you have more in-depth presentation specific to the needs of your organization? So, at the, I guess with that being said, I will wish everyone a wonderful, wonderful day. Stay safe, stay healthy. And we'll see you on the next call. Take care. Take care, everyone.