View our schedule of industry leading free to attend virtual conferences. Each a premier gathering of industry thought leaders and experts sharing key solutions to current challenges.View Schedule of Events
The Document is Dead – How to Improve the Design, Delivery and Change Management of RPA using Digital Blueprints
Defining automated processes using manual documentation leads to stalled RPA pipelines, digital workers that break often, high maintenance costs, and siloed implementations.
Digital Blueprints replace manual documentation and eliminate these risks by enhancing collaboration, visibility, context, and governance throughout the RPA lifecycle, enabling you to identify and resolve errors earlier in the design phase of RPA, as well as manage changes across the lifecycle of automation more effectively.
This session introduces the concept of Digital Blueprints and how to use them in tandem with Blue Prism to accelerate and improve the design, delivery and change management of your RPA program.
Thank you for taking the time to join us today. We're excited about the content we're we've prepared today. We'll be talking about how digital blueprints amplify and accelerate your ability to design, deliver and manage RP at scale.
Some housekeeping notes before we jump into the presentation.
You can pop any questions into that question tab on the right and we'll be answering them at the end of the webinar. So, if you have any questions as we're going through, just pop them in there and we'll, we'll, we'll get to them at the end. Please also check out the handouts section of the control panel for a great resource on this topic.
The webinar should run around 45 minutes, and then we'll have some time for questions afterwards and I'd love to now introduce you to our speaker, today, we have Matthew Dodgson. He is the head of Global solution Engineering at Blueprint Software Systems. Matt, I'm gonna hand it over to you.
Thank you very much Brenda, and thank you everyone for joining today.
So, as Bruno mentioned, my name is Matthew .... I head up the solution, the Solution Engineering Group here at Blueprint globally.
That means I support the delivery of Blueprint Blueprint Enterprise automation platform, which is the modern and intuitive solution. We're going to show you guys today for scaling automation initiatives at your enterprise.
And I support these deliveries across our different organizations, the different customers today.
And what we really want to show you is, as an organization, how we're passionate about helping teams rapidly optimize, automate it, digitally transform their organizations.
And I'm really excited today to walk you through, you know, how we can eliminate the antiquated software design practices from your RPA workflow, so you can ultimately design and deliver your digital workers quicker and much easier.
So before we get started, I want to frame everything we're going to talk to, we're going to be talking to you today about.
So I'd like to start, you start by telling you a little bit about Blueprint and what it is that we do.
Then we'll get right into today's topic and explore the current challenges RPA program they're facing.
We'll talk about where those challenges come from, and more importantly, how blueprint is going to remove those barriers to really enable faster, higher quality automation delivery.
And for that, I believing it through a demo on how to import captured processes into Blueprint.
Optimize those processes before converting them into a Digital Blueprint.
How to export and sink your digital blueprint into your RPA tool.
They used to drive your precise, high quality development.
And ultimately and it'll show you how Blueprint is going to provide the change management and governance capabilities that you need to continually add value to your bot ecosystem, increase your Roi at your organization.
So, starting off, I'd like to give you a little bit more context about Blueprint. At a high level, Blueprint is a leading provider of digital process, design and management solutions for Fortune one thousand organizations.
Global leaders from every industry are using our cloud based platform.
The Enterprise Automation Suite, in Tandem with the Global their RPA platforms to help them identify, design, and manage high value automations with the precision and ease they need by creating what we call digital blueprints.
Now, creating a digital blueprint replaces the need to create time consuming error prone documents like the P.v.d., for example.
And it drives both quality and efficiency at numerous points along the automation workflow.
This is exactly what we'll be getting into today.
This enables our customers to spend less time designing, managing or fixing automations and more times on more time on things that directly grow their business.
So let's jump into today's topic.
We're gonna get started by diving into the most pressing challenges RFK programs are facing.
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.
But rolling out and maintaining an army of bots is actually a tremendous challenge. Too often, the industry doesn't acknowledge the realities of this challenge.
Because of these glossed over challenges, over 50% of RPA projects fail to meet their objectives.
While 20 or 25% of companies have them even achieved the breakeven point, or returned enough hours to the company to pay for their initial RPA investment.
But why? What's going wrong?
Why is this happening, OK.
As organizations race to automate more and more processes, they're hitting a wall.
Myths requirements and poorly designed processes are leading to low quality automations that need consistent maintenance.
And these tedious and expensive changes and fixes are highly reactive, which means that the bot downtime is leading to diminishing returns in business value.
Basically, you spend all your time fixing bots and not building bots.
And this is resulting in an inability to really scale your automation initiatives because you're too busy putting out fires all the time.
So before we go any further, we're going to do a quick pulse check to understand where everyone is currently on their RPA journey.
Now, bruna's going to be so generous as to start the poll for everyone and I'd love for you guys to give us your input.
And really, what we want to understand is, you know, where you are in automation.
You know, just, you're piloting RPA, your organization, you know, you have a scale of 1 to 10 bots, where, you know, RPA has been implemented at your organization.
So maybe you're in the 11 to 50 robot or process range, or you've actually begun to scale up our ..., your organization, 50 plus, or, you know, at the end of the day, you're not really sure.
We'll give you guys a minute there to provide us some feedback. Because what we've seen is very interesting.
And in that the industry is, is very hot on how RPA is going to bring tremendous value to organizations.
But the challenge remains that organizations are having a hard time actually getting it in and getting it going.
And so you notice here that a lot of these polls really start at the beginning part of RPA.
And that's, that's telling of, where a lot of organizations are kinda sitting today.
I'm just watching some of the numbers come in here, perfect, So we just took a quick poll, and obviously a large chunk of you aren't really sure, but some of you have started to scale out. Some of you are looking at, you know, actually beginning to scale up.
Automation at your organization, and then as expected, there's, there's a percentage of, you know, the percentage of you piloted RPA, but you're not sure, as well as the RPA, you know, has manipulate the organization.
Let's see that. So you can feel free to look at the poll results there.
Where does this take us?
Well, while RPA is unquestionably helping, many organizations drive digital transformation.
In too many cases, customers are struggling to scale their programs throughout that scaling point and they're trying to really get that scale going and, you know, to achieve ultimately, the value they anticipated.
At Blueprint, we believe the root cause is that today's RPA workflow is fundamentally broken and inefficient due to the industry best practice of using documents, particularly things like PBDEs.
And they're using these to divide, define and design automations.
Know, we've long believed that documents are terrible, medium for software design of any kind.
And when it comes to automation design via document, it invariably, you know, it's invariably time consuming and error prone. It's manual and it just keeps information separate.
Know these errors and gaps ultimately lead to the burrito brought these brittle bots an Endless break fixed cycles.
And that's failed. Roy, that really prevents customers from achieving the value the anticipated and scaling their programs out to what they need and want to what the management in the organization is actually expected.
Quality automation design is much more than just getting the process right.
But perhaps not surprisingly, many folks struggle with this most basic component.
And despite increasing adoption, process, discovery tools haven't proven to be the answer as they really provide the level of accuracy needed.
Even if the discovery tools work perfectly, there are so many dependencies and other mandates that are critical design attributes that really require the engagement of true subject matter expertise. They have to get the humans involved to actually tell us how to put this process in the context of business decisions.
Issues like regulations and compliance requirements, security, data policies, and understanding the layers of technology that every automation is absolutely dependent on, simply aren't discoverable by any tool or technology.
And ironically, in every situation, when you have tooling, throat discovery, and tooling on the RPA, you're still using documents.
So this cascade of dependencies and critical design information is rarely captured in these documents, or in a document, because the documents are not an effective medium for collaboration and communication.
In fact, they provoke, promote the opposite. They silo information and most often reflect just a single point of view, and they simplify things to the point that they're not, they don't have enough detail.
These challenges are made worse by the fact that when these poorly designed bots inevitably break, companies struggle to effectively manage their changes.
They have trouble quickly and effectively identifying which bots are broken, why, and how to resolve the issue, which leads to increased bot downtime.
All these design, all these design issues, resulting companies spending all the time putting out fires and fixing bugs they've already built, resulting installing the automation pipelines and diminishing the business value from their RPA initiatives.
Let's do another quick poll here to see which of the challenges are impacting the people.
Are you your folks here the most?
So, Brian, if you wouldn't mind starting the next poll.
So, what has been the greatest challenge for you in producing high quality automations?
Whether it's collaborating with stakeholders, you know, sufficiently understanding and documenting the process, ensuring you actually have governance over the process.
Whether it's errors due to the real manual approaches for RPA design.
Or, lastly, it's just understanding, responding to the impact of change. After automations go live, you know, how do you maintain them, how do you, how do you manage them?
Give everyone a moment here to weigh in.
All right, Appreciate that. I can see. I can see the Vote's Streaming in here.
So I appreciate you guys Sharing some information.
Know what we're seeing? And feel free to look at the results here. But, obviously, you know, a lot of folks who are in this camp of, you know, really understanding and documenting processes and their dependencies are ensuring the proper governance with you know, some obviously around the collaborations. So, it, it fundamentally falls in this group of just understanding what we do.
So, of, all, all of these design issues, result in companies like yours, having to spend all the time putting out the fires, fixing blocks you've already built are understanding how these bots work so you can maintain them.
And this is what cuts into our ability to deliver more.
So, with all of these challenges that we talked about, in this for a few minutes, what's the solution?
How do we get past this?
This is where Blueprint comes in.
Now, global leaders, as we mentioned, across industries, are increasingly adopting blueprints Enterprise Automation Suite to identify, design, deliver, and manage these automations in order to scale the scope and impact of their RPA programs.
At the heart of the platform is it is what we call a digital blueprint.
And digital blueprints are much more than just process models.
They contain everything you need to efficiently and effectively deliver these automations, including the detailed process flows, all the dependencies, the systems compliance regulations, requirements, user stories', test cases, and specific implementation details. And they're all directly integrated them into your RPA platform.
So using the Blueprint platform and our digital blueprints has many benefits, including having all of this information, all these assets, and stakeholders in one central platform, which ultimately streamlines the workflow and improves alignment.
Think, think, think about what we do today. We work on documents, a unique document, for every single project, every single program.
And as soon as that document is done, somebody starts building. And then when they're done building, the document gets filed away, and it never gets looked at again, it never gets updated. And in most cases, it's basically all of that work went into creating that document and then it was lost.
Blueprint celebrates all this information, and it keeps it centralized so we can re-use it and it becomes something that everyone can access.
And more importantly, Blueprint has built-in intelligence that helps you model future designs off of all this information.
And it integrates with all this really making a faster and easier design and build process to really bring these automations to life, and ultimately, it improves the quality of your processes.
And lastly, the enterprise analytics and dashboarding and Blueprint helps you prioritize and measure what's working and really manage that change proactively to sharpen and scale your strategy across your organization.
Now, building automations with digital blueprints is a state-of-the-art way to achieve RPA success.
The system is purpose built to design automations in an easy, simple, and understandable way.
As you can see here, identifying systems and actions and parameters for any given automation task does exactly.
It doesn't require technical expertise, and is accessible to the business user. So as you enter things here in Blueprint on the left-hand side, all that essentially going to translate directly in VR paid platforms. And that's what makes it so powerful, is the clear superiority of digital design over documents.
Is being able to capture all that once, and then transfer it directly into whatever RPA appropriate market platform you're using today to accelerate your development and reduce the introduction of error and manual, intervention, manual problems, and manual challenges into the equation.
The ease and simplicity of digital blueprints will allow citizen designers to more readily drive your automation pipelines and scale RPA programs, and ultimately, even grow to this citizen developer movement that we start to, that we start to see across the organization, across the industry, should I say.
What makes all this possible is something we call our common object model.
Always, we call it just calm. It provides an ever increasing catalog of services that, on the backend, help us map these common commands and applications across all the different RPA platforms.
All these services and their specific actions and parameters are mapped directly into your automation development environment.
Through our bidirectional connections with AA, or is our automation anywhere, Blue Prism, Power automate and even UI Path.
No other platform in the market has anything like this, and it's going to be a game changer in, how people design and build automations.
Because if your organization is, like many of the ones we talk to you today, you don't just have one RPA platform, you probably have multiple. Or you're looking at multiple.
And so this idea of automation design is something that needs to be generally generic and needs to be, um, common across any RPA approach or any design approach when it comes to automation.
In addition to kameni and create incredible level of detail and precision, it brings the automation design and development.
Digital blueprints are loaded with other capabilities.
They provide a central, centralized repository, of this automation designed information, that can be referenced, and re-use, It's never out of date, either.
Unlike documents, which, as I mentioned, go out of date as soon as they start to get built.
They have a highly configurable review and approval workflow built into Blueprint. So these digital blueprints can be easily consumed by stakeholders and feedback can be gathered in real time.
Another totally differentiating capability is to transform these process models within your digital blueprint into a myriad of other value added types of things.
For example, being able to automatically generate a set of test cases, Ahve Digital Blueprint, or backlog of user stories, for those, for their teams that need to have that backlog consumable, because that's how they track and manage their work.
But digital blueprints aren't just for your initial automation design and development. All the detailed process, information and dependencies that we capture, provides the basis for an ongoing management of an automation across its life cycle, helping you not only to build the bot that help maintain and manage that.
We leverage that information to provide comprehensive analytics and impact analysis reporting, so that you can actively prevent outages when things changed, which they invariably did.
This leads to automations that have increased productivity and substantially reduced total cost of ownership.
Because high quality automation is built, digital blueprints don't result in endless value training, break fix cycles.
Lastly, there's one of the use case for Blueprint that I also want to highlight here.
Due to its connection with these, with the the arcade platforms and these integrations that we've established Blueprint also has unique capability to really support the migration of automations cross-platform.
We can reverse engineer a digital blueprint from any existing automation and then export it to a new target platform, essentially allowing us to extract the automation design from one system and move it to another.
This dramatically lowers the switching costs to enable you to move from one platform of your choice, or just simply consolidate automations. You already have multiple platforms. This is a huge challenge in the industry, because anytime an organization has to do this, they basically have to rebuild these automations from scratch.
But to sum it all up, digital blueprints are substantial leap forward in RPA design and development.
We can radically accelerate bot development. Many customers were helping to deliver their automations in half the time.
Cutting a three month timeline of automation delivering to six weeks, which allows the team to not only build them quicker and less time. It with less effort, but also deliver more automations in a single year in a single quarter. or that timeframe. that they're going for it.
And if you want to make the leap to another platform, we can also dramatically lower that switching cost, as well.
Up to 80% time and cost savings to drive that bot migration, as well as being able to just reduce the break fixed cycle's by at least 50%.
So, these are huge time savings and huge value savings, that organizations to be able to realize and ultimately driving an increase roi and efficiency for their RPA, Centers of Excellence, and the RFA programs at the company.
I'd now like to jump into the product to take you through a detailed overview and a demonstration of how Blueprint Works and specifically, how these digital blueprints are used.
Here we are in Blueprint Blueprint is a web based cloud hosted solution.
So, right out of the gate, you're not working in files, you're not working on your local desktop, saving things and sharing them around, you're working in a web based solution.
What we're going to do is, we're starting in an invoice example here.
And I'm going to actually import Uncaptured process that we use, that we pulled in from Fortress IQ.
So, in this case here, I'm going to reach in wherever, extract invoice process. We pulled in from Fortress like you.
And here, we have a digital blueprint for this extract invoice process that we captured, and we're now automating.
This digital blueprint replaces the PDD, or the large document that folks use today, and it completely digitizes the approach, which will, which will, which will have a direct impact on lowering the costs of development and deploying.
And you'll see why.
Without Blueprint, we would have had to capture all the specifications and the design in a big document before essentially throwing it over the wall to IT for development while the slow unpacked while they slowly unpack all the information needed to start development.
But, Blueprint also gives you the opportunity to easily model these automations model processes and automations directly by creating these digital blueprints.
So, for example, here, if I take this and we actually have a built-in designer.
So, for example, here, if I get quickly create a new process around extracting the invoice.
So, here's our blank canvas.
Now, we can quickly and easily define a new process by adding tasks, adding steps.
We can even toggle, for example, some details, with the System Step button to get more granular, and actually explain how the UI works, so we can add detailed screens and interactions.
But a consideration of time will go back to the process we captured promo, we import it, and of course, if you'd like to see how you can easily build digital blueprints from scratch in detail, by all means please reach out to us for a demo.
We'd love to show you this in it full power of Blueprint over a call.
Now back to this original Digital Blueprint Arad extracting an invoice.
Here's where we can optimize this process with all the capabilities that Digital Blueprints deliver.
Based on previous automations and the production bots we've already cataloged, the system is recommending certain policies, regulations, and rules, and other dependencies that might be missed and apply, and apply for this particular automation.
This is an example of some of the intelligent recommendations that are built-in, and the dependency mapping that you don't get in other automation design solutions on the market.
Ultimately, if you're trying to do this in a document or any other way, you have to just know these things. Here, Blueprint is actually telling you, everything you've already done in Blueprint.
That relates to this extract invoice process, and you might want to re-use it.
This intelligent assistance reinforces a strong tracing strategy to ensure that no dependencies are missed or overlooked, which definitely reduces the bot outages And then the need for maintenance downtime.
All of these dependencies are linked directly to this digital blueprint.
And are used to quickly report and identify the impact of changes that happen when this is live in production.
Which will contribute to the proactive change management approach that blueprint enables, Which will show which will, which we'll also show you here.
Most importantly, we can automate these digital Blueprints by generating a bot package and sending it directly into any of the major RPA platforms. In this case, we're actually going to send it over to Blue Prism.
This allows us to accelerate the transition in handoff to development and really remove this manual need for PBDEs and documents.
Again, reducing the effort of arcade, development, and deployment while producing high quality, resilient automations, because of the precise contexts, digital blueprints deliver.
So here, we're just going to send it over to Blue Prism. It just takes a minute to upload.
Now here, is it generated by package and Blue Prism?
The process flow serves as a baseline bot or a bot skeleton that developers use to get started.
In other words, without blueprint and RPA developer would first have to interpret what exactly needs to be built by digesting a large PDD, recreating all of this, from scratch, by hand.
This is our blueprint provides a head start on development, and not only reduces the time it takes to develop abide by 50%, but it also leads to higher quality development because there's nothing lost in translation.
No one's going to misinterpret what we're doing and what we're working on.
In addition to the process flow, the digital blueprint also sends over all of the links to all the dependencies, rules, regulations, for easy access and transparency.
This ensures that they have precise guidance for the bot, the business wants to, wants to be built.
Without Blueprint, these will be buried in a PDD somewhere, and it'd be very easy to lose, track and miss altogether.
Now, these digital blueprints, while being able to be export it and sent over into the RPA platform in a Bot package.
We can also automate these digital Blueprints into a variety of other places. They can also be used to automatically generate suites of test cases and test scripts, which can then be used for development or u.a.t.
type testing, further reducing the efforts on development and deployment, and really keeping the total cost of ownership for R K, at a minimum.
But digital blueprints can also automate the backlog of user stories that are needed to develop the bot.
Here, we've generated a backlog of user stories for this particular automation and we synchronize it directly with jira.
So as the team now uses Jira to work and deliver those automations and work through the detailed steps as they update those stories, they're going to be updated and reflected back and blueprint as well.
And more importantly, a business analyst or a product owner didn't have to sit down, create a PD, and then recreate all that as a backlog of stories. This is now automate and this is how we streamline and truly digitize the automation process.
Now, if we fast-forward to after this bot has been completed, tested, and deployed to production, Bluford continues to deliver value throughout the life of that new automation.
Helping to streamline changes and ensure continued compliance. And this is where blueprint enables proactiv change management.
Here, for example, you have notifications of the things that have changed, that might affect automations.
So, these notifications are summarized at the top in these different priorities and categories.
And you could use them as filters.
So, for example, let's say you're only interested in certain changes to regulations, and of those, you only care about the ones that are of high severity.
This filters down to maybe a single set of regulations, or in this case, just a single item, we have to look at, and with a click Blueprint, can identify and show you exactly what's going to be impacted or affected through this impact analysis.
This takes you to a live impact analysis view without Blueprint preforming impact analysis, like this, will be a piecemeal practice, where you, essentially, need to manually isolate each bot that might be impacted by the change and then, dig into the code and understand what the implications are.
Here, you can see that a change is part of the regulation, will potentially impact these five automations, including the one that we've been focused on at this point.
Maybe we'd like to alert owners of the automation that they need to take action before the bot fails and it's subject to ours investigation while it sits idly, losing business value that's supposed to be delivering on.
In this case here, we can quickly send an alert and notify the owners or the team of this particular item that's being changed and those automations that are going to be impacted.
This tells them that they have to do something. They have to act on this, again, proactively, instead of waiting for far for a fire to pop up.
We can actually be a lot more proactive around how do we manage these changes, and now that the owners have been alerted.
Blueprint provides the most typical way to co-ordinate this through e-mail. It's, while it's definitely not the most efficient today letting people know, it helps give people notification that these things are being changed, and more importantly, it lets them know that they can quickly come into Blueprint and look at what that change is.
So in this case here, that stakeholder can log into Blueprint based on that notification, see exactly what's being modified, and how it's going to impact their particular automation.
This identifies the regulation that's changed, which automation things to look at, and the associated comments with everything link. They can go explore the regulatory change, and see exactly what it is, and even navigate to the Bot in Blue Prism right to the affected part of that automation.
So, to sum up what we've covered today, paper based, error prone documents like ...
are ultimately leading to low quality automations that need constant maintenance because they produce miss requirements, inevitably lead to more bought outages.
This, that means that our programs are busy putting out fires instead of focusing on building more digital workers to really scale their automation programs.
Digital blueprints effectively replace PDD and deliver higher quality automations because of the level of detail and precision that each digital blooper contains.
They're accelerated and improved development because of the rich context, in each Digital Blueprint, and their ability to be automatically export it into your RPA technology giving, that those developers, all the accuracy and context, that they need, right at their fingertips.
There's increased value throughout the life cycle, and with proactive change management.
This is possible with Blueprints, instant impact analysis that I showed you, Allowing you to predict the impact of a change, with the precision and immediate co-ordination, to prevent that act, prevent that from happening.
And last but not least, there's greater returns from your automation programs and more business value delivered, due to Molest outages, accelerate design, and ultimately higher quality automations.
So for a limited time, we're offering some free customer evaluations and workshops, to really show you specific proof of value for your RPA programs and how digital Blueprints and Blueprints Enterprise Automation Suite, can save you time, cost, and mitigate risk.
If you're interested. Just visit the link on the screen.
Blueprint says dot com slash get started, and we'd love to take you through a deeper understanding.
And with that, I want to thank everyone for hanging out with us today.
And having us go through this, And I want to open it up for any questions or comments at this time, so we can, we can take that on.
Great. Thank you, Matt. As Matt mentioned, we'd like to now open up the floor to audience questions. If you'd like to ask a question, please feel free to pop it into the questions tab in the control panel on the right side of your screen. We have a few that have come in throughout the presentation. So I'll get started with those. The first two questions are from Rebecca.
And the questions are, how many customers use RP for change management builds? And also how many customers use your product for change enablement processes? Great questions, Rebecca. So.
In terms of the number of customers that use RPA for change management builds, um, I haven't, I don't have a direct number on that. Because each of them is kind of a different area. What we see with certain customers is we tend to start with certain RPA programs and like finance or HR, or sometimes IT.
So there, there's definitely obviously different places that are approach. So it's, it's a percentage. I don't know to what extent.
I think more of the IT specific use cases are probably in the 50% range, so that may fall in there.
So, in terms of how many customers use our product for change enablement processes, it's, again, it's, it's the same percentage. So, when it comes to managing change, and, let's say, and I'm not sure if you're referring to a change enablement process you want to automate.
Blueprint has, obviously, a very broad perspective is the designs as a design space for actually designing any automations from you know finance automations to HR to maybe change in a woman processes.
Being able to model is that we design them in Blueprint, is just the same as modeling any type of processes, but blueprint itself.
He's also instrumental in a lot of change management practices.
And that's really more of how do we process change from the business that may impact certain automations that are in production or in some of our customers that are using us in more of an IT specific role.
How do your changes from the business impacts are in IT solutions and technologies?
Hope that helped give some insight on those. And definitely, if you like to understand a little bit more, what we can do around these, these topics for change, enabling change management automations. I encourage you to reach out and we'd love to take you through a deeper demonstration.
Great, thanks, Matt. Um, we have another question here from Joanne.
Um, I see that digital blueprints can be pushed into RPA tools with integrations to those ARPI tools. But does that integration work in reverse as well?
Can I take a bot that I have in My Blue Prism for instance and get it into Blueprint.
So, that is a great question, and yes, you can. So we mentioned it briefly when we talked about migrations, but Blueprint essentially has an important capability.
So you can take Botts, you have from Blue Prism, UI Path, AA, or even Power Automate, for example, and import them into Blueprint, where, you can either re-engineer them, optimize them, convert them to a digital blueprint, to approve that bots life cycle, or even just catalog them.
We see a lot of organizations that use Blueprint, not only to build their new bots, but to catalog their existing automations so they can start to manage and maintain them.
Then, obviously, because those bots are cataloged in Blueprint, they now are able to be used by intelligent recommendations and be able to be re-used. So, those connected bots can be, not only, for those important automations, as well as from Production.
Can not only be managed better because their map to dependencies and be able to be map to the dependencies but they can even be re-used for new automations.
Long winded way to say absolute.
Great. Another one here from Mark. How can RPA programs limit bot errors and RP downtime that's preventing them from scaling and realizing better returns?
So, as I mentioned throughout this presentation, the solution is to find a better way to plan, design and really communicate no automation work, other than using manual paper based document and documentation like PBDEs.
And that's because those are error prone and they lead to brindle bots downstream.
A solution like Blueprints, Enterprise Automation Suite, that slides into the middle of your automation tool chain is the key to really delivering these high quality automations and maximizing your return.
You know, an intuitive collaborative automation design environment like Blueprint that provide, prioritizes things like visibility, it's seamless dependency mapping, for example, even proactive change management is precisely what allows RPA programs too.
Deliver just more robust resilient automations that ultimately drive and maximize the value to enable to scale. So, it's, it is a, it's a multiple, there's multiple layers to it, but it really starts with this idea of information.
And by putting information repository and putting it into a purpose built place, that really helps manage it and cultivate it and curated throughout the life cycle, we're able to ensure that the result of all this information, which is the bot, is a better quality product than what we're doing today.
Manually and Barry in a very error prone and tedious fashion.
Great. We had another question come in from Rebecca. The question is, Can I use it to automate the manual processes?
Process of building an infrastructure implementation documentation, right.
Yes, so here's the automate, the manual process of building it.
Implementation, documentation, so yes, so where blueprint fits in is definitely when it comes to, um, no, taking a manual process and starting to automate it blueprint is definitely part of that equation. Now blueprint itself, just to be clear, it is not an automation.
Um, it's not an automation tool, like an RPA tool, meaning it's not going to run a bot. It's not gonna be able to run an automation.
What it's going to help you do is capture it, design out and capture all the information around that automation that you're trying to build. In some cases, those things you want to automate are going to be delivered with our key technologies. In other cases. You want to automate those with no custom code or scripts, or, you know, even getting the things like low code, no code.
So absolutely, there is definitely a component of what you're doing, that Blueprint can absolutely assist with and bring some, some better speed clarity and efficiency to that process.
Great, We have another question here, this one's from Phillip, can you explain how Blueprint is able to reduce the costs of migration by so much?
Absolutely, so migration has traditionally been so expensive and uncommon as a result because there's no portability in the RP ecosystem.
And, you know, this is, this is to be expected, So you know, automation, anywhere, it doesn't make, it isn't designed the same way UI path is, or Blue Prism, or a power automate, So you can't take a file from one system to another and therefore, you can't really export a bot from one platform to another. And ERP tools aren't really in the market to do that. ...
speaks it's a language, meaning that as long list of incompatible actions commands variables and that means you know that a bot needs to be built again in a new tool if you want it to work.
So essentially, an entire digital workforce needs to be rebuilt from scratch when you want to migrate with Blueprint.
That massive manual effort and expense is removed.
So what we're able to do is reduce the cost so much because of this common object model we've developed and the integration, there's kind of two levels to it.
Um, and, you know, we, we've done these, we've actually created these integrations in this common model by working with the leading RPA vendors.
So when both are ingested into Blueprint, what we do is we re-engineer and convert them into a digital blueprint. So that essentially extracts the design of that bought from the code into a digital blueprint.
And then, we convert those steps into a common object model.
So, we map any step we can into the common model framework that we put together, and because this common model we developed, and these integrations have been created with partnership with those European vendors, those digital blueprints can now be further optimized and then fit into a new technology.
So the whole idea is blueprint becomes this kind of interchange format this way of no translating one technology into another, this common language, if you will.
Hmm, hmm, hmm, hmm, let's see, we have another one here from, from Thomas. Thomas asks, we're currently looking at, migrating to Microsoft Power. Automate, does your migration solution support switching to Power Automate?
Great question, so the true answer here is yes.
Blueprint has a, know bilateral integration with power, automate or Microsoft power automate desktops specifically, and even Cloud, for that matter. So you can ingest your bots from the RP tool you currently use, convert them into digital blueprints and then feed them into power automate.
Awesome, and let's see, we have time for a couple more.
Um, let's see, we have one more here. Since from Francis, you mentioned that Blueprint is able to automatically generate user stories. We use ..., you manage the development, work on our bots, blueprint provide an integration that would enable us to sync those user stories with Jira.
Absolutely, great question. So, we touched on it briefly during the presentation.
Blueprint does indeed, provide an integration with Jira in addition to many more LM or even work management systems, like Azure DevOps, Rally Version one, I think that was called Digital AI.
So the user stories, we automatically generate, can absolutely be sync with jira or any other technology, L M tool, or backlog management tool your organization might use to drive downstream development, so.
And it's a bidirectional integration, so in the same way that we can synchronize, I generate stories and synchronize them from blueprint downstream, but can also synchronize any story updates and changes back upstream and back and forth between those technologies.
Great. Let's see, we'll take two more questions, We have one here from Sophia asking, are sorry. You also mentioned that digital blueprints generate and contain functional tests. Can you elaborate a little?
Absolutely, of course.
So from the process, at the core of your Digital Blueprint, you can actually automatically generate some high quality comprehensive test plans and cases for that automation.
Essentially, blueprint takes the, the process with all the different branches and conditions and different paths and permutations turns them into different test cases or test passes, ways to kind of walk through that process, and then it takes each step and turns it into an input or unexpected result.
That really kind of maps can map very nicely to things like a u.a.t. type of activity where, instead of having someone create those test cases from scratch, you can generate them off digital blueprints.
But secondly, Blueprint also, auto generates things like Gerken feature files, so once automatically generated, things like those who are computer file test cases, can also be seen with test suites, are these are the high level test cases will also be single test suites that, you know, you use with integrations that are available to really accelerate and improve your QA process for automation with your dev teams downstream.
So essentially, think of think of any any times in your process where someone had to sit down and write test cases manually by hand or had to read through requirements, documents, user stories, and Cree tests.
Blueprint automates, that, can help you automate and accelerate, that will handoff from, Again, design into.
Great. And now this is our final question here and it's coming to us from Alex. How long does it take to implement Blueprint in an organization, including the learning curve and what's the time to value?
So the Blueprint Enterprise platform itself is designed to really be intuitive and accessible to all stakeholders.
You know, from the ground up it's it maps very cleanly to what people have done for years in Word, Excel, Visio, PowerPoint, so it's easy to use whether you're a business or a technical user.
There's also built-in onboarding and an interactive, you know, contextual help that guides people through Blueprint and helps accelerate the learning curve.
And we also offer starter packs with unlimited users.
Really designed to get new customers using the enterprise platform, producing digital blueprints and seeing return on their investment very quickly and the first within the first two weeks.
We actually get people onboard and up and running in terms of time to value. As I mentioned, in one of the final slides, my presentation customers on average experience by five X return on their investment, and that's usually within the first six months. So, once they get through a few, you know, automation programs, that they're really serving to actually ramp up and see that increase in the Roi from their overall bought availability, RPA, uptime, and even this the increase with which they can deliver their automations.
Awesome, thank you, Matt. And that was our final question. I want to thank you all for taking the time out of your day to join us. We'll be in touch with a recording of this session in the next few days. In the meantime, please don't hesitate to reach out if you want to learn more about how Blueprint can help you achieve RPA at scale. Thank you so much, everyone.
Head of Global Solution Engineering,
Matthew Dodgson is Head of Global Solution Engineering at Blueprint Software Systems, supporting the delivery of Blueprint’s Enterprise Automation Suite, a modern and intuitive tool for scaling process automation initiatives to enterprise scale. He believes in delivering quality solutions to customers that drive change and value for their organization and is passionate about helping teams rapidly optimize, automate and digitally transform their organizations. Cultivated through a background in customer service, quality assurance, and software engineering, he has seen first-hand that the best solutions require dedication, passion, and support from the whole team.
Search for anything
October 28, 20211
1:00 PM - 2:00 PM ET
November 9, 2021
11:00 AM - 12:00 PM ET
January 13, 2022
1:00 PM - 2:00 PM ET
January 27, 2022
1:00 PM - 2:00 PM ET
View our schedule of industry leading free to attend virtual conferences. Each a premier gathering of industry thought leaders and experts sharing key solutions to current challenges.View Schedule of Events
Watch On-Demand Recording - Access all sessions from progressive thought leaders free of charge from our industry leading virtual conferences.Watch On-Demand Recordings For Free
Courtesy of DC Government's Ernest Chrappah, below is a transcript of his speaking session on 'Going Digital To Enhance The Customer Experience' to ...
Courtesy of 's Anu Senan, below is a transcript of his speaking session on '' to Build a Thriving Enterprise that took place at Enterprise ...
Courtesy of Tasktop's Dr. Mik Kersten, below is a transcript of his speaking session on 'Project to Product: Driving Digital Transformation Insights ...
Courtesy of Nintex Pty's Paul Hsu, below is a transcript of his speaking session on 'Improve employee productivity during and post-COVID by ...
View our schedule of industry leading free to attend virtual conferences. Each a premier gathering of industry thought leaders and experts sharing key solutions to current challenges.View Schedule of Events