1 00:00:00,000 --> 00:00:04,900 I'm thrilled to introduce our next speaker. Antique. Karjalainen Antti is 2 00:00:04,900 --> 00:00:08,700 here to talk to us about hyperautomation as we heard from 3 00:00:08,700 --> 00:00:12,800 Jen, some of the challenges of making decisions in 4 00:00:12,800 --> 00:00:16,900 real time our that you're trying to simulate an integrate so much information from so many 5 00:00:16,900 --> 00:00:20,900 sources and then apply context for that to make the organization 6 00:00:20,900 --> 00:00:24,900 more agile, make the organization, more adaptive and optimize many 7 00:00:24,900 --> 00:00:28,800 of the things that are going on on. She's been working on this problem for quite 8 00:00:28,800 --> 00:00:29,300 a while. 9 00:00:30,000 --> 00:00:34,900 And has a lot of interesting insights into how this stuff gets deployed and really how 10 00:00:34,900 --> 00:00:38,800 to how to how to the sausage is made. Kind of it's nice to say, 11 00:00:38,900 --> 00:00:42,800 oh you're going to get a magical decision and it will be right there. Will be optimal but 12 00:00:42,900 --> 00:00:46,600 making that happen. Using modern text acts is a real challenge. 13 00:00:47,800 --> 00:00:51,300 Our next speaker. Hi Auntie. Hey, thank you, 14 00:00:52,100 --> 00:00:56,800 great. So I was I was before getting started. I was looking at 15 00:00:57,300 --> 00:01:01,900 a lot of the attendees here on the session and just trying 16 00:01:01,900 --> 00:01:05,900 to see what kind of backgrounds people have. And, and, you know, 17 00:01:05,900 --> 00:01:09,700 it is, is great to have all the Automation and modern 18 00:01:09,700 --> 00:01:13,600 technology available to us. But but many of you as 19 00:01:13,600 --> 00:01:16,700 attendees will probably know what it means to actually be. 20 00:01:16,800 --> 00:01:20,900 Deploy something in an Enterprise and what kind of struggle 21 00:01:20,900 --> 00:01:24,700 that can be at times. Even the, you know, the best of 22 00:01:24,700 --> 00:01:28,600 Technologies is no use, if you can put it into action. So 23 00:01:28,600 --> 00:01:32,800 so I'm going to be talking about how we actually Master 24 00:01:32,800 --> 00:01:36,100 hyperautomation, with the help of our ba and 25 00:01:36,100 --> 00:01:40,900 an Opa might be familiar to a lot of you and I'm so, but 26 00:01:40,900 --> 00:01:43,800 I'm going to go still briefly over. What is our PA 27 00:01:43,800 --> 00:01:46,800 and where does it come from historically? 28 00:01:46,800 --> 00:01:50,600 And then go into hyperautomation. How hard be a fits 29 00:01:50,600 --> 00:01:54,800 into hyperautomation and then how the next generation of our 30 00:01:54,800 --> 00:01:58,900 PA that we are deploying here at robocorp? For instance is helping you 31 00:01:58,900 --> 00:02:02,200 actually enable hyperautomation in an Enterprise. 32 00:02:04,300 --> 00:02:08,800 So, on the, on the basic level of be a is 33 00:02:09,300 --> 00:02:13,700 all about DT dot workers. So replacing humans. In in it 34 00:02:13,700 --> 00:02:17,900 tasks, doing monitor knows repetitive work, and, 35 00:02:17,900 --> 00:02:21,900 and opa. As you might know, it can interact with any 36 00:02:21,900 --> 00:02:25,500 application that you have, whether it's a desktop, but there's a browser 37 00:02:25,500 --> 00:02:29,800 Vision API just like a human use of wood and even go beyond 38 00:02:29,800 --> 00:02:30,300 that. 39 00:02:31,300 --> 00:02:35,500 And you know, too many of Ip practitioners. RPA 40 00:02:36,000 --> 00:02:40,100 is something that you know, has existed as 41 00:02:40,100 --> 00:02:44,900 scripts for four decades before modern days. But now with 42 00:02:44,900 --> 00:02:48,500 the Advent of local, it have really exploded and and 43 00:02:48,600 --> 00:02:49,900 conquered the Enterprise. 44 00:02:52,200 --> 00:02:56,800 But just to level set on a basic level, I'd 45 00:02:56,800 --> 00:03:00,500 like to do a little little bit of an exercise here before I get into the 46 00:03:00,500 --> 00:03:04,800 topic is type into the chat. Wait 47 00:03:04,800 --> 00:03:08,800 for my cue to hit and and then let's all publish the 48 00:03:10,000 --> 00:03:14,800 results. So I want you to think about what's the first thing that comes to mind. When you 49 00:03:14,800 --> 00:03:18,900 think about our be and how would you describe our PA? I'll give 50 00:03:18,900 --> 00:03:20,900 it a brief moment here. 51 00:03:21,700 --> 00:03:25,800 And just type it into a stepson chat here. And when I 52 00:03:25,800 --> 00:03:29,600 say go, you can hit enter. I hope 53 00:03:30,100 --> 00:03:34,800 hope that'll work out. So so what's the first thing that 54 00:03:34,800 --> 00:03:38,300 comes to your mind when you think about our be a, and 55 00:03:39,100 --> 00:03:41,200 how would you describe our PA? 56 00:03:43,900 --> 00:03:47,700 It's, you know, unless you've been exposed to it, you 57 00:03:47,700 --> 00:03:50,900 might might not kind of get it 58 00:03:51,900 --> 00:03:55,800 intuitively. How does it look like? I have an example for you here after 59 00:03:55,800 --> 00:03:59,500 after we done. So maybe go ahead and press 60 00:03:59,500 --> 00:04:01,000 enter publish your answers. 61 00:04:04,200 --> 00:04:08,900 Glorified Excel macro like it. Automate manual key pressing 62 00:04:09,500 --> 00:04:13,900 routine processing recreating group The workflows requiring. No 63 00:04:13,900 --> 00:04:14,600 thought. 64 00:04:17,500 --> 00:04:21,900 Great. Well, for those benefiting glorified Excel, 65 00:04:21,900 --> 00:04:25,800 macros a good one for those benefit who 66 00:04:25,800 --> 00:04:29,000 haven't seen it in action. I just grabbed really briefly 11 67 00:04:32,000 --> 00:04:36,900 video example of what does that actually look like? So this is a bot 68 00:04:36,900 --> 00:04:40,800 working on a Salesforce interface and this is from a real 69 00:04:41,400 --> 00:04:45,800 proof of concept where the path had to work on an essay Salesforce instance, and then 70 00:04:46,100 --> 00:04:47,100 go into sap, 71 00:04:47,300 --> 00:04:51,900 And and, and do bunch of auditing. Basically comparing data between 72 00:04:51,900 --> 00:04:55,500 these two systems, I think this is Sox compliance thing. 73 00:04:55,700 --> 00:04:59,400 So you see a lot of screens moving really 74 00:04:59,400 --> 00:05:03,900 fast and, and that's typically how our PA looks like. You know, it 75 00:05:03,900 --> 00:05:07,900 really started out with, with this desktop automation, but it has 76 00:05:07,900 --> 00:05:11,600 moved more into the back office nowadays. So, I'll just cover 77 00:05:11,600 --> 00:05:15,800 as a practitioner coming from many, many years spent 78 00:05:15,800 --> 00:05:16,900 in this industry. 79 00:05:17,200 --> 00:05:21,400 How I see the history of our be a and ways coming from 80 00:05:21,400 --> 00:05:24,900 and where it's going from occurring, going to now. 81 00:05:25,600 --> 00:05:29,700 So, so basically, our PA started out as 82 00:05:29,700 --> 00:05:33,700 this well, glorified desktop, or dimensional or Excel 83 00:05:33,700 --> 00:05:37,600 macros, if you want to use that, it started out from, 84 00:05:37,800 --> 00:05:41,500 from Fairly standard technology 85 00:05:41,500 --> 00:05:45,700 that was kind of enhanced with local code and, and it was brought into the 86 00:05:45,700 --> 00:05:46,500 Enterprise 87 00:05:47,400 --> 00:05:51,800 Something where, you know, everyone will have this personal but 88 00:05:51,800 --> 00:05:55,800 as an assistant to help you with this tedious manual tasks on your 89 00:05:56,200 --> 00:06:00,500 up and it was framed as this magical AI. That will just simply learn what you're 90 00:06:00,500 --> 00:06:04,900 doing and watch over you. And then you know automate your routine 91 00:06:04,900 --> 00:06:08,900 work. And and in the in the beginning it was really focusing 92 00:06:08,900 --> 00:06:12,900 on as we called attended use cases so something that you do on 93 00:06:12,900 --> 00:06:16,400 your own desktop and it was sold the line of business 94 00:06:16,400 --> 00:06:17,100 as 95 00:06:17,200 --> 00:06:21,900 Such that was, you know, maybe 2016 96 00:06:21,900 --> 00:06:25,200 starting starting forward from there, and then 97 00:06:25,900 --> 00:06:29,900 after a few years of initial or be a success 98 00:06:29,900 --> 00:06:33,500 in the end, the price, we started seeing a lot of consolidation 99 00:06:33,800 --> 00:06:37,900 obviate had become the fastest growing segments in Enterprise software for 100 00:06:37,900 --> 00:06:41,800 three years. Consecutive we started seeing consolidation in the 101 00:06:41,800 --> 00:06:45,900 vendor space and and you know, people were thinking about what's next in 102 00:06:45,900 --> 00:06:47,000 our be a, is it going to be 103 00:06:47,200 --> 00:06:50,700 You know, or don't know, autonomous, digital workers, 104 00:06:50,700 --> 00:06:54,700 cognitive automation intelligent automation, study, hearing 105 00:06:54,700 --> 00:06:58,500 all these different phrases put together and then you had 106 00:06:58,500 --> 00:07:02,300 Skeptics asking, hey, isn't this just putting a Band-Aid over a broken 107 00:07:02,300 --> 00:07:06,900 process? Shouldn't be fixed underlying systems. Instead of automating 108 00:07:06,900 --> 00:07:10,900 them from from the UI. And we started 109 00:07:10,900 --> 00:07:14,800 seeing this emergence of centers of excellence around RPA. So 110 00:07:14,800 --> 00:07:16,700 there was definitely a need for technology. 111 00:07:17,200 --> 00:07:21,900 That would enable you to well take sap here in the demo video. For 112 00:07:21,900 --> 00:07:25,900 instance, take your existing, it infrastructure and layer on top of that 113 00:07:25,900 --> 00:07:29,700 automation that would kind of patch over missing 114 00:07:29,700 --> 00:07:33,900 integration points and you know, few years forward from that 115 00:07:33,900 --> 00:07:37,500 we are seeing that, you know, happy has been validated as 116 00:07:37,500 --> 00:07:41,600 something. That pretty much, every Enterprise will identify 117 00:07:41,600 --> 00:07:45,800 something that they must have. And, and we have 118 00:07:45,800 --> 00:07:47,100 moved and shifted. 119 00:07:47,200 --> 00:07:51,600 Way from the citizen developer phase where we had bought for every 120 00:07:51,600 --> 00:07:55,400 employee. See your desktop assistant. It will learn into a 121 00:07:55,400 --> 00:07:59,700 space where we are. We are close to a line to it 122 00:08:00,200 --> 00:08:04,900 and and we are seeing that, okay, maybe our PA wasn't the glorified 123 00:08:04,900 --> 00:08:08,600 desktop macro, or Excel macro, but it's 124 00:08:08,600 --> 00:08:12,600 actually something that will work on tedious. High-volume 125 00:08:12,600 --> 00:08:16,800 routine back office. Work loads like working with systems of 126 00:08:16,800 --> 00:08:17,000 record. 127 00:08:17,200 --> 00:08:21,700 Good erps, patient data record systems Etc and and 128 00:08:21,700 --> 00:08:25,900 because we are kind of moving past the hype and into into a 129 00:08:25,900 --> 00:08:29,500 phase where we have Enterprises deploying hundreds, and 130 00:08:29,500 --> 00:08:33,900 thousands of Autobots churning through tens of thousands of 131 00:08:33,900 --> 00:08:37,700 hours of work, every every month, producing immense 132 00:08:37,700 --> 00:08:41,700 value. And it's not seeing as a Band-Aid anymore. 133 00:08:42,300 --> 00:08:46,500 And so, of course, coming from a background of creating an 134 00:08:46,500 --> 00:08:47,000 opa, 135 00:08:47,100 --> 00:08:51,600 Technology and and, and seeing this trend play 136 00:08:51,600 --> 00:08:55,900 out, you know, we are, we are in a space where we want to want to become 137 00:08:55,900 --> 00:08:59,400 something of the next generation of PA. That's what we have, the gen2 138 00:08:59,400 --> 00:09:03,700 RPA here as a title, but the main takeaway here is that 139 00:09:03,700 --> 00:09:07,900 apia isn't that the Band-Aid technology anymore, but it's adopted by 140 00:09:07,900 --> 00:09:11,500 pretty much any every Enterprise out there. And it's more aligned 141 00:09:11,500 --> 00:09:15,800 nowadays with Artie than the line of business. So so 142 00:09:15,800 --> 00:09:17,000 how does this 143 00:09:17,100 --> 00:09:21,600 Whole work with hyperautomation then if you put it into that context 144 00:09:21,600 --> 00:09:25,900 so hyperautomation was already defined in this earlier 145 00:09:25,900 --> 00:09:29,900 talk here. But you know, Gardner definition would be that 146 00:09:29,900 --> 00:09:33,500 it's, you know, business driven approach to 147 00:09:33,500 --> 00:09:37,700 to rapidly identify better than and automate business processes and ID 148 00:09:37,700 --> 00:09:41,800 process and it will include Technologies like AI 149 00:09:41,800 --> 00:09:45,400 am l or PA as one and 150 00:09:45,400 --> 00:09:46,200 and 151 00:09:47,100 --> 00:09:51,200 I based automation but you typically see kind of classical 152 00:09:51,200 --> 00:09:55,800 hyperautomation applications being things like intelligent document processing, 153 00:09:55,800 --> 00:09:59,600 taking, unstructured data, and using OCR 154 00:09:59,600 --> 00:10:03,800 and document understanding to structure eyes and 155 00:10:03,800 --> 00:10:07,400 then putting that into action. Chatbots is a good example of 156 00:10:07,400 --> 00:10:10,900 hyperautomation Technologies. So so 157 00:10:10,900 --> 00:10:14,300 this is sort of an emerging picture that 158 00:10:14,300 --> 00:10:16,400 be as a vendor has 159 00:10:17,100 --> 00:10:21,700 have seen while talking with dozens of customers and and now touching 160 00:10:21,700 --> 00:10:25,500 point is typically a VP in charge of in the price 161 00:10:25,500 --> 00:10:29,800 Automation and and they will have these initiatives 162 00:10:29,800 --> 00:10:32,500 from hyperautomation where they 163 00:10:32,500 --> 00:10:36,800 acquired tools and Technologies and capabilities, but they 164 00:10:36,800 --> 00:10:40,800 actually struggled to put that into action in into into 165 00:10:40,800 --> 00:10:44,900 the existing it landscape. So, this is where our peer really from a 166 00:10:44,900 --> 00:10:46,800 practitioner standpoint comes in 167 00:10:47,500 --> 00:10:51,700 And it can act as the as the central backbone of 168 00:10:51,700 --> 00:10:55,700 hyperautomation where you can take a intelligent document processing 169 00:10:55,700 --> 00:10:59,700 capability and give like we'd like to say give 170 00:10:59,700 --> 00:11:03,200 hands for the AI. So I allow the AI to touch 171 00:11:03,200 --> 00:11:07,500 the existing Enterprise it infrastructure and 172 00:11:07,500 --> 00:11:11,700 Landscape. So you have systems like sap or Oracle 173 00:11:11,700 --> 00:11:15,700 for Erp, you might have, you know, a patient 174 00:11:15,700 --> 00:11:17,200 data record system like it. 175 00:11:17,500 --> 00:11:21,500 And other things that are maybe have 176 00:11:21,500 --> 00:11:25,300 evolved over the last two decades and now you'll start 177 00:11:25,300 --> 00:11:29,400 trying to layer on top of that. This hyperautomation strategy 178 00:11:29,400 --> 00:11:33,800 and an RPA can act as the hands 179 00:11:33,800 --> 00:11:37,900 for that AI to really bring it together and allow you to say 180 00:11:37,900 --> 00:11:41,600 you have a chatbot interacting with your 181 00:11:41,600 --> 00:11:45,900 customer in the front end. You might 182 00:11:45,900 --> 00:11:47,400 this is a real world use. 183 00:11:47,500 --> 00:11:51,800 In case you might need to create a new debit card for that customer, but your core 184 00:11:51,800 --> 00:11:55,900 banking system is is really not meant to play 185 00:11:55,900 --> 00:11:59,700 nice with a chatbot. So you'll take happy about take the initiative 186 00:11:59,700 --> 00:12:03,700 from the chat Bots and then process it and return back to the chat 187 00:12:03,700 --> 00:12:07,900 as you can actually really rapidly deploy these new capabilities into 188 00:12:07,900 --> 00:12:11,800 your existing landscape by by the help of using the help of our PA. 189 00:12:14,100 --> 00:12:18,500 And and so, so how the next generation of our PA comes into play? In this 190 00:12:18,500 --> 00:12:22,700 equation, I already alluded to the Next Generation, but 191 00:12:22,900 --> 00:12:26,700 how we see it is really happy shifting 192 00:12:26,700 --> 00:12:30,500 towards it, coming away from the citizen 193 00:12:30,500 --> 00:12:34,000 developer and line of business. Towards IP it 194 00:12:34,900 --> 00:12:38,800 and and in the second generation of our baby, take a more 195 00:12:38,800 --> 00:12:42,400 automation, develop a focused approach while maintaining the ease of 196 00:12:42,900 --> 00:12:43,000 view. 197 00:12:43,100 --> 00:12:47,800 With low code and as a rope as company robocorp, we 198 00:12:47,800 --> 00:12:51,300 have be aligned with what we are dedicated to to build an 199 00:12:51,300 --> 00:12:55,900 open-source standard for our PA. Maybe that's a, you know, topic 200 00:12:55,900 --> 00:12:59,600 for later talk. But we want to create this open source 201 00:12:59,600 --> 00:13:03,900 standard like technology stack into our p and then 202 00:13:03,900 --> 00:13:07,900 allow it to better shift with sit next to it. 203 00:13:07,900 --> 00:13:09,700 Bit processes like 204 00:13:10,500 --> 00:13:14,900 You know, continuous integration and deployment, and that's something that 205 00:13:14,900 --> 00:13:18,300 we call automation Ops in the industry. So 206 00:13:18,300 --> 00:13:22,900 automation Ops is really Central to being able to operate 207 00:13:22,900 --> 00:13:26,900 a robust function with 208 00:13:26,900 --> 00:13:30,900 the center of excellence with our PA, so that you can actually rely on 209 00:13:30,900 --> 00:13:33,300 these pots. It's not the sort of the brittle, 210 00:13:33,300 --> 00:13:37,900 you know, glued on plaster like 211 00:13:37,900 --> 00:13:40,300 band aid technology, but it's really 212 00:13:40,500 --> 00:13:44,700 A robust way to build Integrations into existing it stack 213 00:13:45,300 --> 00:13:49,800 and so automation Ops in the second generation of RPM. Now enables you to work 214 00:13:49,800 --> 00:13:53,400 with things like get Version Control, full hoarded 215 00:13:53,400 --> 00:13:57,900 ability, full logging of your but actions have devops like 216 00:13:57,900 --> 00:14:01,700 routines for maintaining them and and really 217 00:14:01,700 --> 00:14:05,800 going away from the shadow. It moniker that 218 00:14:05,800 --> 00:14:09,900 had been given to 2R P, NY many it leaders used to 219 00:14:09,900 --> 00:14:10,300 hate it. 220 00:14:10,400 --> 00:14:14,600 And then reusing bought Assets in the form of 221 00:14:14,600 --> 00:14:16,800 code is a big part of this as well. 222 00:14:16,800 --> 00:14:20,200 So so 223 00:14:20,200 --> 00:14:24,700 the first generation of our PA if you contrast it to 224 00:14:24,700 --> 00:14:28,700 that, second generation started off with really, this sort of the 225 00:14:28,700 --> 00:14:32,200 we're going to build a into end hyperautomation 226 00:14:32,200 --> 00:14:36,800 platform and, you know, I think some of 227 00:14:36,800 --> 00:14:39,700 them even even mentioned becoming the next sap. 228 00:14:40,400 --> 00:14:44,800 But the but the way we see in the second generation of obviate the second 229 00:14:44,800 --> 00:14:48,900 emerging technology stack is that rather than trying to build a 230 00:14:48,900 --> 00:14:52,800 into--and wall to wall, covering in the price wide 231 00:14:52,800 --> 00:14:56,800 hyperautomation platform, the next generation is going to be more in the 232 00:14:56,800 --> 00:14:59,400 credible so so you're going to have a new and emerging 233 00:14:59,400 --> 00:15:03,900 hyperautomation technology vendors. Like in this picture we have 234 00:15:03,900 --> 00:15:07,600 Rothstein base64 as good examples of of 235 00:15:07,600 --> 00:15:10,300 fast, moving fast, emerging new technologies. 236 00:15:10,400 --> 00:15:14,900 We want to be able to integrate all of those through the 237 00:15:14,900 --> 00:15:18,800 central backbone of our PA into the Enterprise it landscape. And 238 00:15:18,800 --> 00:15:22,700 thus enable enable kind of faster move woman the into 239 00:15:22,700 --> 00:15:26,900 into hyperautomation. So my view for 240 00:15:26,900 --> 00:15:30,900 sure is that hyperautomation is going to be a multi vendor 241 00:15:30,900 --> 00:15:34,600 approach rather than a single platform 242 00:15:34,600 --> 00:15:38,600 that covers all of this. Just because the that the space is so fast moving 243 00:15:39,100 --> 00:15:43,600 So, wrapping up here 244 00:15:43,600 --> 00:15:47,800 as a summary RPA, while 245 00:15:47,800 --> 00:15:51,800 it's considered as one of the sort of hyperautomation Technologies 246 00:15:51,800 --> 00:15:55,800 next to things like chat Bots and AI am L 247 00:15:55,800 --> 00:15:59,500 capabilities can really act as the as the 248 00:15:59,500 --> 00:16:03,500 central backbone for for hyperautomation and and it should be 249 00:16:03,500 --> 00:16:07,700 considered as such. And then for those 250 00:16:07,700 --> 00:16:09,000 not nice, 251 00:16:09,100 --> 00:16:13,100 He's deep into our PA every day. We've seen that it started out with this 252 00:16:13,100 --> 00:16:17,400 glorified macro but then moved into something that's governed by a 253 00:16:17,400 --> 00:16:21,200 center of excellence. That's aligned with it and actually can 254 00:16:21,200 --> 00:16:25,700 be a fairly robust way to automate business processes across 255 00:16:25,700 --> 00:16:29,800 an Enterprise. And, you know, we see that 256 00:16:29,800 --> 00:16:33,700 hyperautomation is so fast moving space, that 257 00:16:33,700 --> 00:16:37,800 there's not going to be a single vendor that will be able to cover all the 258 00:16:37,800 --> 00:16:39,000 angles, all the needs and 259 00:16:39,200 --> 00:16:43,300 So we're going to see in the next year's many many new vendors, come 260 00:16:44,300 --> 00:16:48,800 Innovative automation capabilities and we want to be able to incorporate them 261 00:16:48,800 --> 00:16:50,100 into a stack. 262 00:16:51,300 --> 00:16:55,600 So, so that's that's my wrap up and I'll 263 00:16:55,600 --> 00:16:59,700 open it up for questions. Thank you so much, talk to you, and 264 00:16:59,700 --> 00:17:03,400 we are about to go into a break here, but if you have a couple of questions we can 265 00:17:03,400 --> 00:17:07,400 feel them here. In looking in the event chat, we've had a few folks 266 00:17:07,400 --> 00:17:10,800 talk about sort of hyperautomation and the contrast between the 267 00:17:10,800 --> 00:17:13,700 Automation and Hyper and what makes it special 268 00:17:13,700 --> 00:17:17,900 and I think you know, really what you were talking about 269 00:17:17,900 --> 00:17:21,000 as a differentiator things like the ability to do auditability. 270 00:17:21,400 --> 00:17:25,500 And to make it more of an operational process, instead of a shadow 80 271 00:17:26,600 --> 00:17:30,900 issue is at the core of this. What do you see 272 00:17:30,900 --> 00:17:34,900 as the big barriers to widespread open source 273 00:17:34,900 --> 00:17:38,600 adoption of this as opposed to sort of Shadow it doing it in the 274 00:17:38,600 --> 00:17:42,300 background with with cans and string? Well I mean 275 00:17:43,800 --> 00:17:47,900 the way apia really exploded in the beginning was that it wasn't a line 276 00:17:47,900 --> 00:17:51,200 with idea. It was this Shadow ID approach for you. 277 00:17:51,300 --> 00:17:55,400 Just you know, popping a few licenses and you're all set and you start 278 00:17:55,400 --> 00:17:59,900 building and then you end up with this Mick mishmash of 279 00:17:59,900 --> 00:18:03,000 processes on automation. That doesn't really scale in any way, 280 00:18:03,500 --> 00:18:07,500 it's harder to maintain every day and week and 281 00:18:07,500 --> 00:18:11,800 so so I think I think that was necessary stage in the growth of our 282 00:18:11,800 --> 00:18:15,700 PA, but as we as we go into this more 283 00:18:15,700 --> 00:18:19,800 scaled up operation, we need to have better governments governance and 284 00:18:19,800 --> 00:18:21,200 and all the controls. 285 00:18:21,200 --> 00:18:25,700 Place. And when we talk about hyperautomation contrast to your sort of 286 00:18:25,700 --> 00:18:29,800 regular day automation, I think it is. The speed of 287 00:18:29,800 --> 00:18:33,800 adoption is what we are we are talking about is not 288 00:18:33,800 --> 00:18:37,700 building a multi-year project to build a, you know, 289 00:18:37,700 --> 00:18:41,700 end-to-end Enterprise automation platform is the speed of being able to adopt 290 00:18:41,700 --> 00:18:45,900 automation Technologies and that's part of where our PA becomes. 291 00:18:45,900 --> 00:18:49,800 The central backbone where it's faster to build Integrations to 292 00:18:49,800 --> 00:18:50,800 our be a than, 293 00:18:51,300 --> 00:18:55,900 That means even you know think about telling to 294 00:18:55,900 --> 00:18:59,800 a CIO that we need an new sap project in terms of integration 295 00:18:59,800 --> 00:19:03,700 c not going to make it most likely but if it's a 296 00:19:03,700 --> 00:19:07,900 digital work or doing the integration, you'll be able to pull it off in a few 297 00:19:07,900 --> 00:19:11,800 months. I'll drink you so much for being with us today. Really fascinating. Look at 298 00:19:11,800 --> 00:19:15,900 how this is kind of gone from Skunk Works to the mainstream and 299 00:19:15,900 --> 00:19:17,900 continues to do. So thank you so much.