Courtesy of Micro Focus's Rai Phakay, below is a transcript of his speaking session on 'Does Robotic Process Automation Take Jobs Away?' to Build a Thriving Enterprise that took place at BTOES RPA & Intelligent Automation Live Virtual Conference.

Hello everyone. Welcome back to RPA and intelligent automation live. I'm sure that pairs the Chairperson, the founder and CEO of excellence and innovation. This session is a really interesting session. We're going to have ... K talking to us about robotic process automation. And the title of the session is, Does Robotic Process automation take jobs away? If a K who is a solutions architect with micro focus specializing in automation orchestration and cloud migration technologies. It has over 16 years of industry experience working. With Fortune 500 companies, it's current stamped and IT operations management focuses on delivering automation solutions for enterprise environments with mission critical infrastructure, helping organizations translate that knowledge to real business value. So, ladies and gentlemen, I'll leave you up with ... in his presentation.

Thank you, Jose.

And, uh, thank you, everyone, for joining us today on this session. I believe this session would be informational, and you enjoy this. If you have any questions, please do write those down in the chat box, and I will definitely be able to answer those later at the end.

So, without any further wait, let's get started with the session. So here's how much the agenda is going to be. For this session, We're going to briefly cover what RPA is. Why do we need RPN? What are the benefits? I'm sure all of you are from the domain, and you know, the benefits already, but it's just a brief setting up. The stage to the main question does RPA, it takes jobs away. We're going to briefly covered the RPM market, how RP is doing. What is, what are the benefits? How we're seeing RPA products in the market. And the services, then, the real question, the impact on jobs that, we're going to look at a few use cases, how organizations are currently using RPA. And then look at a few requirements that, we believe that any ERP solution should have and quick demo for a micro focus RPA solution. Then, at the end, we'll finish it off at the Q and A session.

So, let's get started.

As we know, businesses and organizations around the world are embarking digital transformation, this buyer for continuous improvement and increase automation to become agile and more competitive. They're looking for new ways to increase their productivity, expand their outreach beyond their traditional customers and industries, and looking for new ways to add new revenue revenue streams, implementing new solutions, and cutting out the unnecessary cost by improving the internal processes. But the reality is that the employees spend too much time working on the same mundane, repetitive, error prone task every day, day in and day out.

They're looking to do the same work, same monotonous activities, several hours a day, that opening e-mails and attachments, they're filling out forms. They're moving files and folders, copying and pasting data in and out of apps, preparing the data, manipulating it, merging it, et cetera.

And these everyday manual processes are not just confined to a specific business or an industry.

They actually span different departments and industries from finance to insurance, from medical to telco, or for HR, to e-commerce.

These activity, that range from, for example, month and reconciliation and finance to claims processing and insurance fulfilling service request in a Telco or updating orders for E-commerce. These are just few examples. In fact, you will find that RPA use cases are so rich and diverse. And each, one of them, is based on customers, unique implementations.

And they, these tasks just keep going, like they have been, for many, many years in the same repetitive manual fashion, because they're just used to it. Or they often involve legacy applications, which are difficult to automate. So robot comes to the rescue and offer a solution to these challenges.

How, let's first review what RPA is. in context to this discussion, RPA, or robotic process automation, uses software robots that mimic or stimulate all those human actions performed on any user interface by human beings.

With RPA, you have the ability to record screen actions. And these recordings are nothing but extremely flexible scripts, that you can insert into workflows to create, end to end processes that are truly fully automated.

Now, when do we need RPA? Well, here's a great example. In this screenshot, you can see the reality, which we don't get to see as a customer when we call a bank or a Telco.

We need RPA when we want to automate existing systems and applications without disrupting the way we work with minimal changes, without having to go to expensive inland, the system integrations, RP is not a part of company's core IT infrastructure. Instead, it sits on top of those applications and systems, helping complete to implement automation and technologies quickly and efficiently.

You look at RPI when you don't have a way to easily integrate legacy applications, which have no API, or, very difficult, or, complicated IP.

So RPA, by definition, is all about return on investment, how soon a process can be automated, without changing the way we work, or the process, without changing how these application function. And we are looking to realize the value in terms of increased productivity and hours saved, simply put, is just another computer software deployed by an organization to execute high volume, repetitive tasks.

Now, robots have many benefits, as we all know. The interact with applications and systems, just like humans do, but they're faster, the more accurate, they're highly secure, and they never sleep, potentially can work 24 7.

This means that the quantity of work goes up while the cost of maintaining the processes goes down dramatically, and the robots also free up the employees from their mundane repetitive task so they can focus on more meaningful things and contributing more to the business. All in all business becomes more efficient gained competitiveness, which is what most businesses are aiming for, and in today's world where businesses have cutthroat competition, They're always looking for ways to cut out the cost base to step ahead of their competition and increase their market share and value of the organization.

Let's look at the ARPI market in general.

Forrester predicted that automation would become the tip of the digital transformation spear in 20 19, impacting everything from infrastructure to customers. To business models. Are pure being a subset of the whole automation space. They predict that RPS service market continued to grow and build top $12 billion by 2023.

Enterprises are expected to spend $3 on services for every dollar spent on RPA software, increasing demand for business process automation, through the use of artificial intelligence and machine learning, as well as software robots is anticipated to be the kiko driver. That being said, what does the impact of RPA on job market?

Well, RPA is considered to be a double edged sword. While on one hand, it may take away jobs. It will also create new, high quantity skill jobs.

RPA may lead to some job losses, but more importantly, it will enable employees to be more productive to be able to focus on tasks which require human intervention and intelligence as against working on the same mundane repetitive tasks. RPA is more of an opportunity rather than a threat. It is the opportunity to unleash human creativity to do more meaningful task.

According to a report by McKinsey Global Institute, two third of all jobs could have at least 30% of their activities. Automated by 2030.

It is expected to replace up to 140 million full-time employees worldwide by 2025. However, many of the new, high quality jobs will be created for those who create, maintain, improve RPA, and automation software, and those business processes.

Let's look at some of the industry use cases and how RP has been implemented successfully. This is a multinational investment and financial services company. They use web based legacy application to collect information about distributed disputed transactions.

This application holds huge paginated tables across different screens with thousands of records.

There's no way to filter or sort the data or export it. So everything got to be done manually.

Prior to implementing an RPA solution, a manager would spend up to two hours scrolling through multiple screens, printing out disputed cases from the application screen, and then assigning them to different team members.

Now, interestingly, the current process included printouts, which expose sensitive information as well as the credit card numbers. And the case assignment was driven by various criteria. For example, time to resolution etcetera, and to keep up with compliance with the implementation of RPA solution they observed just like a human would. The robot navigates in the legacy application grabbed thousands of records sorts, and prioritizes the cases by bank and by the team member and then generates an e-mails the report innovate Robot prepares the To-do Report for human employees. each tab in the report lists cases assigned to each team member. In fact, the report also encrypted the credit card numbers, which helped improve the security as the team members were, contractors and not internal employees.

In addition, the robot also generated daily and weekly dashboard showing number of cases received by the bank, number of cases processed by the robot to help manage a review progress, review the outcomes of the process, and prioritize the cases while extracting urgent cases for processing.

In this case, we can see the RPA solution was improving the efficiency of the business process while freeing up manager's time. So he may affect focus on more higher value tasks like improving the business process, taking care of his team and team members, boosting employee morale, etcetera. These are all higher value tasks rather than doing the same monotonous task of creating the report and sending it over.

Now let's change the articles and see a different use case here.

This is a multinational media company that offer customer live streaming services for a wide selection of channels and on demand premium media content.

They use, this media company, offer thousands of products and to make this rich content available the work with various different partners. And now heres here's their challenge.

They use Siebel for internal processes and use Salesforce for managing their customers. They've got 20 full-time worker spending hours copying and pasting the catalog information from Siebel to Salesforce. Now, how do they do that? While they access multiple tabs, copy paste data into an Excel, then use another Excel to map the fields from Siebel to Salesforce. And finally, manually enter the data into Salesforce quite a lengthy daunting and complicated process that we may see.

Just to let you know, one worker completes a catalog entry for one product, in about an hour. So typically, in an eight hours working day, that means about eight catalog updates per worker. And for those 20 workers combined, 160 catalog updates per day depict up this business process to be the pilot for their RPA implementation.

And end results, they observed that the RP solution was able to combine API and UI task in order to move the data from Siebel to Salesforce, including all those different steps. For example, the data mapping, exceptional handling, entering the data into Salesforce, and the product catalog entry for one product was completed in about two minutes.

And the benefits they observed for obvious, in this case, in about an hour, tatty catalog, entry updates, and in eight hours, about 140 catalog entry updates. And that, itself, is a 30 time increasing the efficiency, if we compare it to a single worker.

Now, one may say that the jobs of those 20 workers, or at least some of them, may come at stake now, that the robots are able to perform their activities. And that might very well be true initially. But on the other hand, these workers are subject matter experts for the business process, and these legacy applications didn't know the business process more than anybody else.

They know how to work these applications and act, If there's an exception and eder, which robots may not be capable, are equipped to handle, until being trained or programmed. And they always be needed to improve the business process, create new flows, and automation scripts for RPA to implement.

Let's look at one more different use case, here. Here, we have a telecommunications company and, in this case, we see the customers of this multinational. Telco stopped paying for the services as soon as they submit a request for decommissioning.

However, the company continues to inaccurate charges and fees for third party providers and local operators, until the decommission is fully processed.

The lengthy manual, administrative process behind decommissioning could take up to several weeks with implementation of RPS A they observe.

They could automate the whole business process from initial e-mail notification to pilot PRI validation and classification of data.

RPA was able to run the actual service request fulfillment across all different application. in this case, Salesforce, and Nutcracker, and send automatic decommission e-mails to third party providers so it's able to complete the full loop in a single flow.

They were able to reduce the processing time from several weeks to just few days, thereby eliminating the unnecessary payouts for the services not rendered. Also. It reduced employee efforts tremendously by automating the monotonous process of copying pasting information from one system to another, to create the service requests and send notification e-mails. As a result of the RPA solution, the observed twice the efficiency and could process two hundred and fifty's decommission request as per month, as as against 108.

So they were able to realize the return on investment on their RPA solution instantaneously. And with the successful pilot. The organization was encouraged to implement more processes, and automate more business processes, if possible.

Now, let's look at some of the capabilities that we believe are required in an RPA solution.

A good RPS solution should be a single, scalable, enterprise ready solution that can handle the workload and help you build secure and scale automated business processes from legacy to modern application across the enterprise.

According to us, it should include these three logical components in some form or shape.

A studio, that provides an interface for building and maintaining automated processes, including a recorder for screen actions, so that you can visualize the business process activities and automate those, the orchestrator of it acts like the brain of RPA.

Executing all RPF flows and managers and controls the robot while logging older auctions for added and compliance. And finally, the robot itself, which executes the robotic tasks, interacting with the application and the data.

Building onto those core competence, these are a few key features that we include in an RPA solution.

Our RPA solution comes with easy to use Design Studio in this intuitive visual design interface. You have the ability to launch the Activity Recorder, to record ... and then once the recording is available you can edit pediment tries and debug. All from single screen automating the whole business process. From start to end, combining the APN UI task.

We have Brazilian robots that can keep processing D flows Even when the UI changes. So customer spend a lot less time on maintenance. They don't have to re record the flows or activities. Every time there's an update to the application, or the Page, layout, changes, or a field in the form is relocated. The smart robots able to adapt to those changes, using advanced object recognition capabilities, and keep going and keep performing.

Central robot orchestration that combines UI and API automation steps, while managing and controlling the robot's centrally.

It also provides access to rich library of out of the box EPI content, and co-ordinate the work between multiple robots.

You can also apply advanced workflow logic for decision making, parallel processing, and error handling.

It gives you the ability to orchestrate run, schedule, and monitor your robot from a central dashboard, making it highly capable.

And a user friendly self-service portal is a must for attended bot use cases, so users can initiate and run the flows on demand when needed.

For scalability. Having a worker based to architecture gives the ability to scale the robot's up and down as the workload changes.

This architecture manages a pool of resources, and handoff robotic requests to available robots. Each robot works independently, and it has its own communication in the queue.

As the workload changes, you have the ability to bring additional robots to increase capacity and parallel processing, and once the requirement or the peak is over, you can scale those robots down as needed.

And, at the end, enterprise level Security, to run your business securely, robots have unique IDs and role based credentials that run on lock screens, use encrypted passwords, and automate processes that out exposing sensitive data. So, you, and you also have the ability to track all the actions in detailed logs, all in real time, for any audit or compliance purposes.

Let's see. A quick demo of the solution here, where we can combine the API and UI level tips. This is one of the most common use case for organizations which use Salesforce. In this demo, will be combining your API level, automation steps, as well as your UI level automation, to create sales order, in Salesforce, based on the content received from an e-mail.

The end user can consume this automation on demand using the self-service portal, Or you can have the process running completely automated, with the robots, actively monitor the mailbox, looking for new e-mails for processing.

When a new e-mail is received, the robot then reads the e-mail in Outlook and download the attachment.

Parsis.

The data from Excel creates the Salesforce order in Salesforce, using UI based automation, and at the end, once the order is created, it sends an e-mail report to the end user confirming the order numbers.

So let us see all that inaction.

All right, so what you're looking at right now is the the mailbox, which the robot is actively monitoring, and it would wait for the e-mails to come in. Suppose this was the e-mail that just came in.

It has an Excel file, which it would have the list of all the orders to be created. These are two simple orders that the robot is supposed to create. So as soon as this has received, the robot kicks in, and it goes ahead and start creating those orders. And as you can see here, it's already read the e-mail, it read the orders, files, and now it's process of creating the first order.

Let us see that in action.

Punch is all the information, and then it's saving.

And at the end, it captures the order number, four, output, and then, because we have two entries, it's done the process in loop to and enter the second order. And once the orders completed, it goes ahead and sends the e-mail to the end user. Let's look at that e-mail.

And that's the e-mail that has been sent out to the user. It has the order numbers that had just been created by the robot. Let us see behind the scenes how this has been done combining the API and UI level tasks.

This is the workflow designer, where you could go ahead and create the floes.

So, let's do a recording first, Ford to Salesforce. So, we can teach the robot, or how to do this process.

OK, and as we start recording, it launches the site, which is, let's login for the robot to know.

And it's capturing all our steps.

Let us go and orders.

New water, put in the order details.

It's Steve, And at the end, let's capture disorder number for the output.

All right. So, these are all the steps that we did there. You can see each and every step. Let's go ahead and remove all the hard coded values and put in variables here. So, a user can put in the details, and the robot will be able to use those input values, and create orders pertaining to that.

Let's go ahead and remove these values and replace them with the variables we just created.

OK, and now that recording is ready. Let's go ahead and create the floor to create the entire process, business process, end to end. Now, we just did one. You know, recording, we just taught the robot to do one task, but just to do it in the Salesforce and create an order in the Salesforce. But you do have the ability to use the API level automations and combine that with the UI and do this. So let's get the e-mail message and the attachments, rhett's, read the file, then we use that information in the order to create the Salesforce order, send the e-mail message, and create our workflow.

That's string these tasks together, so they pass along the outputs of each step to the next step.

For the first step, we're going to receive the attachment.

For the next step, we're going to use and parse that attachment.

Third step, we're going to run in loop, because that's the recording, and if there are multiple entries, we want to process that.

Let us see if that information, and deploy that to RPA Central, which is the brain off, the robot orchestration.

And from here, you can run the flows on demand, using the self-service portal, or you can have the robot actively monitor the queue. So as soon as an e-mail is received, it would go ahead and process the order and Completed.

Kate, that's the end of the demo.

And at this time, I'll take any questions, if there are Josey.

Yes, thank you. Thank you very much, Ray.

We do have questions that have come up and I'll be relay those to you and that you feel you Can still type your questions right now, Is just as you have seen the The end of race demo. I'm going to turn my camera, so that you can see me during this, and, and I'll relay the questions to array in real time here. So, so re, going back to the, to the top, to the title of the session, Lydia, is asking, is, knowing business processes enough to keep your job from the robots? Because can't this processes be learned by the robots themselves? What are your thoughts on that?

Well, truly saying lowering the business process is not the, the only thing required to keep your job secure. Obviously, with the advent of any technology, we have to move along, you know, there's a, there's a harsh step or I should say a saying which says, adapt or die. You know. If you don't adapt to the new technology, you're going to dive at the old way. This was, this is how you, you gotta learn. And, as we move along, none of us knew the cloud technologies, you know, a decade ago, we did not know Azure or AWS or Google Cloud existed. We all learn how to use these cloud technologies. Same goes with machine learning and AI. You know, we didn't know these technologies existed. We don't know how to write algorithm and codes.

So, we learned to adapt to these new technologies, and, and made our job secure. And I believe that's the way to move forward. And I'll take a great, you know, illustration from one of the good movies I've seen recently, or actually it's, it's, it's in 20 16 hidden figures. I don't know if anybody else has seen where there are three of women who to contact had a contribution to NASA and and, you know, one of the characters named Dorothy. Juan was the lead of human computers. There were no computers at that time. And although the math calculations were supposed to be done by the human beings, and then NASA implemented the IBM supercomputer.

And, and they were still trying to figure out how, you know, how they think it's going to produce the output has some issues. And ... was able to resolve, learn, to teach herself how to use that computer. And, and, at the same time, no, she taught that thing to the entire team, saw. In a way, she found new jobs for our entire team, because they no longer will be using those whole, you know, human computers, There'll be using the IBM supercomputer to do those complicated, you know, calculations. So, in my eye, you know, you gotta move with the technology. So, you know, you're, it's always good to learn new things and can be being in the technology space where, every six months, there's New software's new products. New solutions that keep coming in and we kind of keep moving along with them.

I believe that should, I believe that answers the question.

Good perspective.

So, Rohit, but is asking about, you've talked about the resilient robot, the, the, the adaptable robots and specifically, on, he's interested on, how does the RPA, our auto detects if there is a UI change in the web page? Tell us a little bit about how that, how, that works.

So I mean, there are some vendors where, which are recording screen positions on, on the screen. So where you click as to, what is on the X axis and what is on the Y axis. But at the end, if it's a webpage, there has to be an object at the backend. So an RPA solution should be tracking the objects. It should know what object Avi. Avi editing or changing are we using in the RPA flow? So even if the object relocates on the page, for example, if it's on the top right hand side of the page and it moves to bottom left or a scrolling down to the end of the page, then the objects still remains the same. And if we know and we can identify those objects uniquely, we would be able to track where it is in the current state on the new layout, and we'll be able to enter that. No problem.

So, the point is to be able to use that, You know, technology, which is able to track the objects and use that object information, instead of just the position of the cursor on the screen.

Yeah. And the question, are, these robots that are able to adapt to these changes are, this is the standard robots offer, or these are special types of robots that have some built-in additional capabilities in them?

So, these this is standard on our solution davina off, obviously, that there are multiple vendors in the market, and I'm sure they're all trying to implement AI and machine learning to track all that changes and process those requests. We obviously want the robots to be able to perform just in case there's a little change, and we know the application have updates, and the web page gets update ever. So often we know in the, in the recent times, so definitely, you know, they didn't, The, robots should be able to track this. And we do have this in our solution, that, that, that is what, you know, I can say.

Very good. So lots of questions coming in, which is great.

So one of the questions is, related to compliance and risk and risks change with RPA being implemented.

Tell me, tell me about your experience with compliance and risk associated with RPA implementations.

Well, compliance, I mean, there's always the risk involved in anything. That is hand it over to robots, because at times, we don't know what is going on, we don't see it. We can't hold the human being responsible for for doing those steps, but a good practice is to have logs and and audits, You know, to be able to check what the robot is doing. So, if a robot, in any process, if, if we have some kind of locked to track, how each and every step has been performed, and if we have detailed logs, which has, you know, the inputs and the outputs of the action, that would give us a good, you know, accountability for the robots as to what it's doing.

So, that gives us the ability to stay compliant and and be able to perform those, those tasks. And at the end of the day, obviously, we need to hit the SLAs or do business objectives that the business is trying to solve, because that's where the dollar value comes in. And I was just there, on Radish session. You know, I mean, you have to convince the business, to, to be able, to able to promote this. Because, again, you know, RPA, you know, as, as the title says, in the beginning, you know, it has a block right there. That, it's going to take away my job, you know. So, you have to, you have to have, you have to convince the business that it's really bringing some tangible business benefits to you. Some values in terms of efficiency, some, some cost reduction or something. So, business is motivated to implement that. And at the same time, you have to communicate better for your team. So, and tell them that there's a next path forward for the team. Which task has been given away to the robots? You know, there's, there's more that these people can do.

That's good, that's good, good, good insights regarding the demo itself. That was, that was interesting, it was nice for you to share that and gives us kind of behind the scenes on the on what's going on there. And Michael Levine was asking, just to confirm what, which RPA tool you use on the demo.

So this was our own RPA solution micro focus. And even though our solution was just released about, you know, a year ago, so might not be available on the analyst reports, but no microphone. This is the seventh largest peer-to-peer software company in the world and it has where it's different technologies that it's developed over these years. ... is one of the testing solutions. That is one of the course of our solution which is doing the recording and those Brazilian robots is the capabilities of ..., a solution by Micro Focus as well as operations orchestration.

one of the most powerful, you know, orchestration solution that we have which has a lot of API level automations out of the box. So you don't have to create those tasks. You can just use, pre created task, which are already provided to you, from our R&D department, or from the user community, which is available on our marketplace, and you can just re-use those, and, as well as any automation can, find, on Cloud Slack, You know, So, you could, you could just download those and, and you have the ability to merge those into other orchestration like C and Siebel or or intelli-j.. So, you could just, you know, merge all those auto orchestration automation tools and and create a flow of those activities where, you know, there's an easier way to do. Things. Not have to record each. And every task. just record the task, which is required only on the US side, but you still have API level access to might as well use those automations technologies that has been developed over these years.

Very good, very good. And following up on that arrow invert dog asked that, based on the demo, it looks like a business analyst or train operational staff would be able to configure the robot for what you did there, which, which was nice. And then he, he asks, in which cases you, you require to have IT developers evolve to setup the RPA.

So, as mentioned, you know, we are combining the API level tasks with UI level. So, you are level task, is obviously the, the subject matter expert for that business process, They know Which application or am I using, at what point? I'm bringing the input from previous step to the next step and fair in what form I am putting that information. But, at the same time, if you're using API level automation, which is, you know, let's say, I want to grab some input from Outlook. How do I do that? So, there's API level automation, where IT has knowledge of or copying pasting a file, that's a function available in, in our flows. So, how do you use those functions to create a path or network share, how to access the network share through the API level? That's where IT would come in and augment these recordings and make them even bigger to complete the end to end orchestration.

Very good. Jonathan Glenny has has a question focused on that API and UI automation that you just refer to when you're looking at API and you in UI automations. Maybe if you back up a little bit. What are the, what are the top considerations that they use? They take into account when you're combining API and UI.

So the first output or the result we're looking for is end to end orchestration or end to end completion of the business flow. So you know, there are possibilities that whatever vendor you're using for RPA may not be able to do a certain process, or they do not have no automation on certain technology. So, you need to find out as to what the solution can do and not do. So, that's, that's one thing you are looking at.

And then, with regards to, you know, at what is, what is your API, when, at one, do use API? So you are looking for the path of least, resistance, know, you're looking to automate your business process as soon as you can as easily as possible without changing any underlying technologies or software's or the process you use. So, with regards to that, you are trying to find the ways, which is the simplest way to automate a particular step. I mean, it is, it could be possible that. I mean, it's easy to use UI instead of API. You know, I don't know how to play around with the API. So, I don't want to even take that route. I just want to use the UI automation, use that as a sub steps, and then move along and use another UI. So, you have to understand what the process is, What's the business process, and what is the path of least resistance, and which is the best?

No. Automation Technology would. You would you would like to use weather?

It would be AI API level automation, or UI level automation.

Very good. Very good, And then let's talk a little bit Megan. Megan Blake has a question about about scaling bots. What are your suggestions for organizations for a scaling and sustaining the bots that they have already created? They created the bots and now they're looking for scaling, and sustain those bots. Any, any practical recommendations for that?

So, I mean, you, you need to first understand, For scaling purpose, you need to understand, you know, what is your normal workload, that the robots, as processing? Is your current robots, OK, To or are they OK to handle the current workload they have. At, at what point there is a rise in the requirement at, Is there a particular pattern that you can, you know, you have that, for example, at X X time, or X hours during the day, you know, I have so many requests, my robot, I need more more processing power at that time. Can you schedule that?

So, in that way, you have the ability to, you know, push more robots for, for parallel processing, or you do have the ability to, you know, leave those robots, you know, in available for grabbing any work, but that's wasting resources. Let's say you only need 10 robots at this time, but you have 20 deployed, because your peak uses 20 robots, but that 10 robots are just sitting there waiting for the tasks to come in. And they're being underutilized. The better way to do is, is to understand when is your peak coming.

And then, just before that, you launch some extra machines, all of which has robots on it, and then you launch those robots for that specific time period, where you have to peak. And then once the peak is over, you shut them down or you take them away from the queue. So, so you save resources there. So, that's the right way to scale robots scale up and down as your workload changes.

Very good. Follow up on rohit's question about the Auto Detect on the RPA. You know, he asked originally about, if there is a UI change in the web page, how does an RPA auto detect. And then, specifically, he was interested if, if there are new or objects, are the bots able to identify or work around those newer objects on the page?

So the question comes, if we are going to use do newer objects. So, if there's a new field that comes in the form, and do you need to fill in that field? Or do you need to enter some new information in that field, or capturing that details? That essentially is adding a new step that the robot needs to do.

So in the previous task, this field did not exist. So Robot did not know about this field. And it didn't knew what it's supposed to do with that.

But in the newer form, I presume what he wrote is trying to say, is, there's a new field. And VR either capturing that information from that field. Or putting some information in that field. That, in turn, adds another step. So you, an RPA solution should be able to either add or remove steps from that existing recordings. So that's minimum level of maintenance, at any point. That would require some maintenance, if you're using that object. So you would either be adding a new step to use the information coming out of that object, or putting the information in that object. So I mean, you could do the whole recording end to end one more time. That's that's where you would add the new object to be used, or you can edit the existing recording and see if that's the way you would like to lead, And that's how you would handle the new new object.

Very good. Very good. I don't know if you have experience with RPA for a sox compliance. Sundar, I was asking about data on how good is RPA forest sox compliance, any, any experience? Do you have, on that area?

I can't recall any cases on that, at this point, for sox compliance.

But what I'm assuming that compliance compliance, right, it's just that the process behind the compliance process is going to be different.

But I would assume that from an RP perspective Drew, imagine it's the same approach. Well, all the complaints would would have a similar approach. You are basically capturing some kind of, you know, inputs from, from something, and then you compare if it's compliant or not, and then if you're not compliant, you push some kind of remediation tasks to to make that compliance, so that remediation tasks can basically be implemented by the robot. So these remediation? Could be installing a patch installing or changing some values, or making some new changes to your to your application or or devices so that task can be Done by the robots without a problem. Yes.

Very good. More of a personal development side, here, personal and professional development side. And thank you, Anna, was asking on, what would be your suggestion for, for someone who is a Quality Professional, Lean, six Sigma practitioner, and they're looking to, to upscale or learn more about RPA? How, you know, what would be a good way of getting started, to stay relevant. We know that, of course, Those individuals, I think it's implicit in the question here, is that, there's professionals have a lot of insights on methodologies and approaches to business process improvement, and, and, as they want to become more conversational, and the news RPA. Any suggestions on how people make that transition from being a process improvement expert to becoming more adaptable to RPA and its applications?

So I would, I would, I would believe, that they already have, you know, half the puzzle, which is, you know, how to price improve the process. Or how to implement these steps. The next step is to implement it or to deploy the, the RPA solution. So they need to understand how each and every step in the improvement process, is implemented. And how they map to the steps within the RPA solution. So knowledge of an RPA solution would definitely be added. plus, it would depend as to what RPA solution they, they plan to implement. I mean, there are various different vendors, but in terms of the terminology and the common platform they use, you know, you need to understand, you know, what is the best practice to convert that process into an actionable steps? That can bring a change, and then, you know, how do you link each and every step to complete the whole business process automation.

And I believe that's the change, not just with any RPA solution, It's, it's about the whole automation space, you know, from, from any previous way of doing things to the new way of doing things. You know, how do you do that in the new automation space?

Very good. So I'll ask one final quick question here. I mean, the RPA is, there are lots of applications right now. I mean the, the field itself is, is evolving, I think the bots are evolving. I mean, you're talking about smart Brazilian bots now and share with us. What do you see coming up? What is there, is there, is there an evolution for RPA here that you see and not, necessarily in the next five years, but next next year, or so what do you see the industry training towards?

So the industry is training about, you know, ah you know, discovering the business process, so, you know, we understand what are you can do for us, but what does the right candidate to, you know, implement RP. What are the business processes, which are, P can implement, where they can realize the business value and give you the efficiencies and the and the results instantaneously. So, that's the hard part, You know, I mean, all businesses have several different, No business processes that they believe, oh, I can automate this, or I can automate another process. But, what are the right candidates? Choosing the right candidate is, is, for RPA is, is the way now, the technology is moving towards, you know, how you can find an uncovered those business processes?

You know, on its own, so first, you know, I mean, the initial step was a business process lead would tell you, OK, this is my business process. How, this is how I do things, This is how I need to automate it. But, but a software that can detect this process automatically, if you run a software. in the environment, that can detect the whole business process, and help you map each and every step in the business process, to actual step within the RPA. That gives you a base, or a layout on, which you can build on. And that's where the technology is heading towards. On that discovery front, We have the capabilities. to do it, we need to find more use cases. That's where the technology is heading. As, well as adding more capabilities in, in the deployment phase, you know, adding machine learning and artificial intelligence, able to handle all those exceptions. Where the pay changes and stuff. So the robots become more and more, you know, independent as well, as they're able to handle all those letters doesn't need more maintenance.

The more they function, the more value vegging out of, out of the whole, you know, RPA solution, ..., thank you so much for sharing your expertise with us today. Very, very helpful to learn all about all this very practical approaches to RPA. Thank you very much, for all of you who are in this session. We're gonna Close. This session right now, is We'll open back up at the top of five minutes to the top of the hour. And As you close the session. Use your control panel. Close button a little window will pop up if you have any questions or feedback and for those in there. And at the top of the hour, we'll have doctor Ashe Power from the California Institute of Technology talking to us about cloud computing for data analytics and application. So should be very interesting last session for today. And I hope to see you back then.