>>The Cube Presents UI Path Forward five. Brought to you by UI Path. >>Hi everybody. We're back. David Ante with David Nicholson. This is UiPath Forward five from Las Vegas. We're live, you know, the customers here, they're automating all the time, sucking work and the cube. We're sucking all the information out of the experts and the customers. A bar Toban is here. He's the global business, Shared services, leading automation and AI at PepsiCo. And Para Colan is back is the chief, He's the chief product officer, UiPath longtime Cube alum. Great to see you guys. Thanks for coming on. Great to see us all day. So you guys keynote today, you know, excited to have PepsiCo on. I'm not sure I've ever interviewed PepsiCo in the Cube, but tell us about your role there. >>Absolutely. So I'm part of a PepsiCo global business shared services team. I lead automation and AI capabilities. GBS has, you know, we started GBS portfolio back about three and a half years ago, and we have a six hubs across PepsiCo. And as, as a part of my role, we deliver transformational capability across the PepsiCo. >>When did it all start? >>About three and a half years ago, 2019. So >>Prior to the pandemic. Yeah. You know, versus the pandemic was a catalyst for this. Yeah. But it was at the catalyst, but maybe it sped it up a bit. Yeah. >>PepsiCo journey started with, if, if you look at the PepsiCo, you know, the automation journey, it started back in 2017, but the GBS portfolio took shape back in 2019. So prior to that, you know, PepsiCo was definitely, you know, working on lot of, you know, the automation capabilities and automation product across, you know, PepsiCo. But with the introduction of PepsiCo global business shared services team, we are, you know, centralizing a lot of transformation capability, you know, across the functions that, that we support within the >>PepsiCo and, and UI path. Was going to part of that journey all along? Or was there sort of other activities beforehand or how >>No, no, absolutely. Starting from 2017, if I, you know, remembered, you know, with the vision of our, you know, some of our senior leadership team and recognizing the value of, you know, automation in the core, you know, capability as a transformation at that time, you know, we started with just like anybody else, right? We started with, you know, proof of concept, showed some, you know, early wins and the value back to the business, start setting up some, you know, business processes and capabilities, stood up the platform, build a complete, you know, ecosystem around that, you know, platform and partnership with, you know, UI bot team. And you know, from there, here we are five years. I mean, it's, it's a, it's a, it's a, it's a very critical component to our digital transformation capability and, and yes, leverage across >>Let's talk platform. So you, you guys have made some announcements this week. You talk about the business automation platform. I remember our first forward was, you know, RPA tool. Okay. Yeah. And then you guys made acquisitions. I was there for that. So the process process cold and then people started to really expand it and it's really come in amazingly long way in a short time. So what did you guys announce today? What'd you talk about on stage 20, 22, 10? Tell us more about it. >>Absolutely, Dave. So you've seen the journey, you've been with us since the early days. You know, we were in 2017 and RPA tool that could automate a representative task that happened over and over again in the environment. And then three years ago you were here when we announced the automation platform, we said, it's not just about a task, it's about involving humans in bots to manage end to end processes. It's about discovering what automation opportunities exist. It's about using ai. Pepsi Co was actually the pioneer of using AI along with automation. You know, we were in stage together with them in, in 2019. And where we are now is we're essentially seeing people want to take the next step with automation. They're saying that it's no longer just an automation tool, It's the way we operate. It's the way we innovate in the organization. So they're really making sure that it becomes a part of their digital transformation journey that they're on. >>And they're saying that we can do the digital transformation by consolidating multiple DRP systems and CRM systems. And that'll take us seven years to do, or we can go with UI path and we can leverage the core that we can leverage the GL system that exists today. We can leverage inventory tracking system that exists today and start to build processes on top of that that can adapt to what customers are trying to do in this digital age. And that's where, you know, we've made announcements today is, is really pivot the platform to be a business automation platform. And there's sort of three layers, you know, unique but you know, connected layers of the platform. The first one is discover. And Discover is all about finding your processes, identifying the opportunities, making sure that you are managing the return on investment. What is the process? You know, how are you getting ROI on it? >>The second one is automated, and that is really where we're applying semantic automation to identify the digital building blocks of an enterprise, which is your data, your document, your screens and communication. Like putting all of that together and saying you can automate our processes, leveraging a lot of intelligence that exist in how business processes are done. And the last one is operate, which is if you're trying to execute a business process at scale, you're processing not just, you know, a task thousand times, but you are fulfilling millions of transactions. You're, you know, you're looking at trillions of records to identify what processes you need. A scalable enterprise platform that's able to ingest a lot of data, report on metrics, reporting efficiency. So that's what we've announced today is an automation platform that companies can use to put at the center of the digital transformation >>Journey. So I about the interesting thing about PepsiCo, you guys started in 2017. Yeah. So kind of early, early on. Yeah. Yeah. And you kind of been there with the progression platform. So my question to you is end up, it was, you know, we've seen the e from primarily on-prem, now it's cloud first. Yeah. How disruptive or non disruptive was that for you? Did you have to rip and replace? Did you have to sort of retool or migrate? What was that like? >>No, I mean, significant disruption, right? I mean, I mean, as, as we started our journey back in 2017, just like, you know, PRM mentioned, right? With simple rule based, you know, the automation from then now to our journey where our continue to, you know, infuse, you know, AI capability, document understanding, conversation ai, right? As a part of our end to end portfolio. At the same time, I think the cloud is providing a fantastic opportunity for us to continue to scale, right? You know, scale at, at a large. So that I think is a fantastic, you know, fantastic platform and fantastic, you know, the opportunity that we are looking forward >>To know. So how do you affect adoption inside of the organization? Can you talk about that? What's working? What's, >>It's always value driven as you know, right? I mean, the business business has to see the value. It it, it was, I mean, I would, you know, admit it was not as easy as before, but as the mindsets have started to shift, right? As the people have started to realize the value that, you know, the automation brings to, you know, the, I mean, you know, not just the, the value for the business, but actually transforming the entire portfolio, right? And, and people have started to see now that not every automation project is going to be transformation product, but for every transformation project you will find the automation at the heart and the core of it. So I, I, I think that's what has started to shift the mindset of, of uniforms. >>So how do you know when you have end to end? What are you wake up one day and say, Wow, we've achieved it. You know, is it pieces that come together? Yeah. What do you say? >>Yeah, You know, we wanna look at customers from, you know, from an end to end perspective. It's not just about piecemealing mealing finding a problem, solving it, really what does it deliver from, from an end to end perspective. Did you actually, you know, because a lot of times companies will say, we wanna automate X number of processes, and, and they do that and they're like, Well, we've automated a lot of processes. We're not sure what value we're getting out of it. It's the ability to measure like, what impact is this automation having on your business from an operational metric, but from a business metric as built. But then going back and saying, Well, where is the biggest pain point? Where do we have the largest value that we can give to the business back? So one of the things we actually announced today is the ability to take at an look at an idea and look at what was the estimated benefits of that idea, and then map it all the way through execution to say, what are we getting? >>We estimated we were gonna save a million dollars by doing those automation, or what have we achieved till now? Have we achieved a million dollars? Have we achieved half a million dollars by having achieved? That's true. That never happens. That, and, and, and, and it's hard to do that, like the data existed, but it's really hard for people to pull that data out. So we build out the box dashboards that give you the ROI bag, and that's why it's really important to, to make sure that, you know, you look at it not just as a technology project, but more as a investment from a business side. And so you can making a business more efficient. Yeah, >>That's, I just, I know you were jumping in, but that's super important. Cause you know, you run a lot of projects. Yeah, absolutely. And each of those projects has zone roi, then you jam it into the application portfolio. Exactly. And then everybody sort of forgets about it. You can't really track what impact it had because there's always, you know, some things that are benefit, some things are sometimes a negative. And so it's that holistic picture that you >>Trying to achieve, extremely critical point, what you hit on, right? From it's measuring the benefit and measuring the continuous benefit across, and not just from start and end, Okay, what I promised I delivered or not, but, but you have to have this continuous mindset. And so I think Yeah, definitely that that's a very, very critical to our finance team and our cfo, >>They organic mechanisms. It's constantly >>Evidence. Absolutely. Yeah. So abar, yeah. Global business shared services. Yeah. When you think of PepsiCo, yeah, of course people immediately think of Sure, Pepsi. But PepsiCo is a multi tentacled absolutely beast of a company. Absolutely. In a good way. Yeah. For organizations that are in that same category, holding companies, companies that have all sorts of different entities that are working together under one umbrella, how shareable is this idea of automation and business automation process moving forward? How, how shareable is that on the share oter? Yeah. Yeah. As far as, as far as, as far as you're concerned, are you, are you talking to some people where you're saying, Hey, I'm here, I'm here from GBS and I'm here to help, and they look at you like you're crazy because you don't understand their business? Or is this something that relatively easily applies across businesses >>That No, to your point, I mean, very valid point, right? I mean, it's, that's, that's the gbs, global business shared services mindset, right? As you move the functional areas into the Pepsi, into the Pepsi, gbs, like hr, procurement, commercial sales, supply chain, right? That's where you wanna start to find those, you know, the optimization, you know, opportunity. You wanna start to ize your processes, and that's where you will, you know, as you transition this processes within the gbs, that's what create those, you know, opportunities for you. So >>What, >>What about automation opportunities? Not in the sh I know you're in the shared arena. Yeah, yeah. But each of those business units has processes that could probably be optimized and automated. Sure. Is that something that's under your purview? We've heard, we've heard a lot about citizen developers. Yeah. I don't know if that, if that >>Applies to No, that definitely. I mean, you cannot just have focus on end to end, you know, automation. I mean, that's, that's a huge portfolio for gps at the same time supporting, you know, automation through the citizen development capability. That that's where, once again, you know, you have not provided a lot of capability and solution tools that we use, right? To continue to empower the folks who are part of our, you know, GBS team inside or outside gbs, right? It, it, it's, I think it's very, very critical. It, it, it helps people transform their career even in one ways, right? And, and, and, and you have that muscle, you have that resource, and you have the power. You definitely want to utilize that. >>So let's talk about metrics for a minute. So more data, the better. Usually I like data. Yeah. But, but if you're trying to optimize for 15 metrics, I feel like you're not gonna optimize on any, So how do you deal with that from both, as par was saying, an operational standpoint and a business standpoint? What are the things about how do you sort of get the, the teams focused on the right things? >>B business, functional leadership team drive those alignment for us as a part of a global business, shared services, we, we are hip to have connected with our business, you know, functions, right? They, they have to help us prioritize those. And to your point, I mean, yeah, you cannot attack 15 metrics at once. You have to prioritize, you have to make sure that you bring the focus to the product, you know, project, right? So, so definitely, I mean, it's, it's, it's not often 15 metrics, but top three metrics, let's, let's focus, let's zoom in and ensure we are driving it. But, >>And if you think about the system, I mean, at the end of the day, the p and l manager, he or she cares about ebit, let's say. Sure, okay. But there are so many factors, you know, in that complicated organization that are gonna affect ebitda and they're gonna be different. But somebody's gotta figure out, okay, how do they fit together in a system? And can, can UiPath help me understand that, those relationships and those dependencies? >>Absolutely. I mean, I think there's a, there's an aspect of human relationships and, and making sure that you get the right level of sponsorship from the business and, and there's a business stakeholder and, and looking at every investment and, and outcomes that you're driving based on that. But, but that is something that we, from a tools perspective, we're trying to make sure that you can measure the value throughout the entire value chain. But then getting the business sponsorship, like where we've seen automation scale is always because there's a business sponsor that's essentially saying, Here's what I'm trying to achieve and here's the, here's my goal, here's a North star and go get it and let me know how you're tracking against it. And, and our job is to make sure that we can provide the visibility, the people that are operating the, the programs to make sure they get that level of visibility. >>What's the scope of automations in your, you know, organization? Is it dozens, hundreds, >>Huge. >>That is thousands. >>We are getting there. Okay. No, definitely. I mean, we have definitely, you know, realized that it's, it's a core component to our digital transformation, right? So, so there is no, there's no stopping on it. There, there, there, there's plenty of support from top down and you know, it's a fantastic time to be at PepsiCo. Right? Especially at the PepsiCo gbs. Right, >>Right. Thanks for sharing your story. Congratulations on all the progress you guys have made. It's actually quite remarkable to see where you guys have come from. So I really appreciate it. Thank you, Dave. Thanks. Thank you Dave. Okay. Thank you for watching. This is Dave Ante for Dave Nicholson. We are right middle of day two at forward five from Las Vegas. We're live, we're right back.

(upbeat music) >> TheCUBE presents UiPath Forward 5. Brought to you by UiPath. >> Hello and welcome back to TheCUBE's coverage of UiPath Forward 5. We're here in Las Vegas at the Venetian Convention Center. This is day two. We're wrapping up Dave Nicholson and Dave Vellante. This is the fourth time theCUBE has been at UiPath Forward. And we've seen the transformation of the company from, essentially, what was a really interesting and easy to adopt point product to now one through acquisitions, IPO, has made a number of enhancements to its platform. David Cardenas is here. Deputy Director of Operations for County of Los Angeles, the Department of Public Health. David, good to see you. Thanks for coming on theCUBE. >> Thanks for having me on guys. Appreciate it. >> So what is your role? What does it have to do with automation? >> So I had been, actually started off in the IT space within the public health. Had served as a CIO previously, but now been moving into broader operations. And I basically manage all of the back office operations for the department, HR, IT, finance, all that. >> So you've had a wild ride in the last couple of years. >> Yeah, I think, like I've been talking earlier, it's just been, the last two years have just been horrendous. It's been a really difficult experience for us. >> Yeah, and I mean, the scars are there, and maybe permanently. But it also had major effects on organizations, on operations that, again, seem to be permanent. How would you describe the situation in your organization? >> So I think it, the urgency that came along with the pandemic response, kind of required us to look at things, you know, differently. We had to be, realize we had to be a lot more nimble than when we were and try to figure out how to enhance our operations. But really look at the core of what we're doing and figure out how it is to be more efficient. So I think we've kind of seen it as an opportunity to really examine ourselves a little bit more deeply and see what things we need to do to kind of, to fix our operations and get things on a better path. >> You know, I think a lot of organizations we talked to say that. But I want to understand how you handle this is, you didn't have time to sit back in the middle of the pandemic. >> Yeah. >> And then as you exit, what I call the isolation economy, people are so burned out, you know? So how do you deal with that organizational trauma? Say, okay now, let's sit back and think about this. Do people, are they eager to do so? Do they have the appetite for it? What's that dynamic like? >> So I think certainly there's a level of exhaustion inside the organization. I can't say that there isn't because it's just been, you know, two years of 24/7/365 kind of work. And that's tough on any organization. But I think what we realize is that there's, you know, we need to move into action quickly 'cause we don't know what's going to come next, right? And we're expecting that this is just a sign of what's to come and that we're just at the start of that stage of, we're just going to see a lot more outbreaks, we're going to see a lot more conditions kind of hitting us. And if we're not prepared for that, we're not going to be able to respond for the, and preserve the health and safety of our citizens, right? So I think we're taking a very active, like, look at these opportunities and see what we've done and say how do we now make the changes that we made in response to the pandemic permanent so that the next time this comes at us, we won't have to be struggling the way that we were to try to figure things out because we'll have such a better foundation in place to be able to move things forward. >> I mean, I've never served in the military, but I imagine that when you're in the military, you're always prepared for some kind of, you know, in your world, code red, right? >> Yeah. >> So it's like this code red culture. And that seems to have carried through, right? People are, you know, constantly aware that, wow. We got caught off guard and we don't want that to happen again. Because that was a big part of the trauma was just the unknown- >> Right. >> and the lack of preparedness. So thinking about technology and its role in helping you to prepare for that type of uncertainty. Can you describe how you're applying technology to prepare for the next unknown? >> So I think, so that first part of what you said, I think the difficulty we've always had in the public health side is that there's the, generally the approach to healthcare is very reactionary, right? Your first interface with the healthcare system is, "I'm going to go see my doctor; I'm going to go to the hospital." The work that we do in public health is to try to do everything we can to keep you out of that, right? So it's broad-based messaging, social media now is going to put us out there. But also, to be able to surveil disease in a different way. And so the holy grail for us in healthcare has always been, at least on the public health side, has been to try to see how can we tap in more actively that when you go see the doctor or when you go to the hospital, how can I get access to that information very, very quickly so that I know, and can see, and surveil my entire county in my jurisdiction and know, oh, there's an outbreak of disease happening in this section of the county. We're 10 million people with, you know, hundreds of square miles inside of LA. There are places where we can see very, you know, specific targets that we know we have to hit. But the data's a little stale and we find out several months after. We need to figure out a way to do that more actively. Technology's going to be our path to be able to capture that information more actively and come up on something a little bit, so we can track things faster and be able to respond more quickly. So that's our focus for all our technology implementations, automation like UiPath has offered us and other things, is around how to gather that information more quickly and put that into action so we can do quick interventions. >> People have notoriously short memories. Please tell me (chuckles) any of the friction that you may have experienced in years past before the pandemic. That those friction points where people are thinking, "Eh, what are the odds?" >> Yeah. "Eh, I've got finite budget, I think I'm going to spend it on this thing over here." Do you, are you able to still ride sort of the wave of mind share at this point when putting programs together for the future? >> So whatever friction was there during the pandemic wiped away. I mean, we had amazing collaboration with the medical provider community, our hospital partners. The healthcare system in LA was working very closely with us to make sure that we were responding. And there is that wave that we are trying to make sure that we use this as an opportunity to kind of ride it so that we can implement all the things that we want. 'Cause we don't know how long that's going to last us. The last time that I saw anything this large was after the anthrax attacks and the bioterrorism attacks that we had after 9/11. >> How interesting. >> Public health was really in lens at that point. And we had a huge infusion of funding, a lot of support from stakeholders, both politically and within the healthcare system. And we were able to make some large steps in movement at that point. This feels the same but in a larger scale because now it touched every part of the infrastructure. And we saw how society really had to react to what was going on in a different way than anyone has ever prepared for. And so now is we think is a time where we know that people are making more investments. And our success is going to be their success in the longterm. >> And you have to know that expectations are now set- >> Extremely high. >> at a completely different level, right? >> Yes, absolutely. >> There is no, "Oh, we don't have enough PPE." >> Correct. >> Right? >> David: Correct. >> The the expectation level is, hey, you should have learned from all of- >> We should have it; we can deliver it, We'll have it at the ready when we need to provide it. Yes, absolutely. >> Okay, so I sort of mentioned, we're, David cubed on theCUBE (all laughing). So three Daves. You spoke today at the conference? >> Actually I'm speaking later actually in the session in an hour or so. >> Oh Okay. My understanding is that you've got this concept of putting humans at the center of the automation. What does that mean? Why is that important? Help us understand that. >> So I think what we found in the crisis is that the high demand for information was something we hadn't seen before, right? We're one of the largest media markets in the United States. And what we really had trouble with is trying to figure out how to serve the residents, to provide them the information that we needed to provide to them. And so what we had traditionally done is press releases, you know, just general marketing campaigns, billboards, trying to send our message out. And when you're talking about a pandemic where on a daily basis, hour-by-hour people wanted to know what was going on in their local communities. Like, we had to change the way that we focused on. So we started thinking about, what is the information that the residents of our county need? And how can we set up an infrastructure to sustain the feeding of that? Because if we can provide more information, people will make their own personal decisions around their personal risk, their personal safety measures they need to take, and do so more actively. More so than, you know, one of us going on camera to say, "This is what you should do." They can look for themselves and look at the data that's in front of them and be able to make those choices for themselves, right? And so we needed to make sure that everything that we were doing wasn't built around feeding it to our political stakeholders, which are important stakeholders. We needed to make sure that they're aware and are messaging out, and our leadership are aware. But it's what could we give the public to be able to make them have access to information that we were collecting on an every single day basis to be able to make the decisions for their lives. And so the automation was key to that. We were at the beginning of the pandemic just had tons and tons of resources that we were throwing at the problem that was, our systems were slow, we didn't have good ability to move data back and forth between our systems, and we needed a stop-gap solution to really fill that need and be able to make the data cycles to meet the data cycles. We had basically every day had to deliver reports and analytics and dashboards by like 10 o'clock in the morning because we knew that the 12 an hour and the five-hour news cycles were going to hit and the press were going to then take those and message out. And the public started to kind of come in at that same time and look at 10 and 11 o'clock and 12 o'clock. >> Yeah. >> We could see it from how many hits were hitting our website, looking for that information. So when we failed and had a cycle where that data cycle didn't work and we couldn't deliver, the public would let us know, the press would let us know, the stakeholders would let us know. We had never experienced anything like that before, right. Where people had like this voracious appetite for the information. So we needed to have a very bulletproof process to make sure that every single 24 hours we were delivering that data, making it available at the ready. >> Software robots enabled that. >> Exactly. >> Okay. And so how were you able to implement that so quickly within such a traumatic environment? >> So I think, I guess necessity is always the mother of invention. It kind of drove us to go real quickly to look at what we had. We had data entry operations set up where we had dozens and dozens of people whose sole job in life on a 24-hour cycle was to receive medical reports that we we're getting, interview data that's coming from our case interviews, hospitalization data that was coming in through all these different channels. And it was all coming in in various forms. And they were entering that into our systems of record. And that's what we were using, extracts from that system of record, what was using to generate the data analyses in our systems and our dashboards. And so we couldn't rely on those after a while because the data was coming in at such high volume. There wasn't enough data entry staff to be able to fit the need, right? And so we needed to replace those humans and take them out of that data entry cycle, pop in the bots. And so what we started to look at is, let's pick off the, where it is that that data entry cycle starts and see what we could do to kind of replace that cycle. And we started off with a very discreet workload that was focused on some of our case interview data that was being turned into PDFs that somebody was using to enter into our systems. And we said, "Well before you do that," since we can't import into the systems 'cause it wasn't working, the import utilities weren't working. We got 'em into simple Excel spreadsheets, mapped those to the fields in our systems and let the bots do that over and over again. And we just started off with that one-use case and just tuned it and went cycle after cycle. The bots just got better and better to the point where we had almost like 95% success rates on each submission of data transactions that we did every day. >> Okay, and you applied that automation, I don't know, how many bots was it roughly? >> We're now at like 30; we started with about five. >> Okay, oh, interesting. So you started with five and you applied 'em to this specific use case to handle the velocity and volume of data- >> Correct. >> that was coming in. But that's obviously dynamic and it's changed. >> Absolutely. >> I presume it's shifted to other areas now. So how did you take what you learned there and then apply it to other use cases in other parts of the organization? >> So, fortunately for us, the process that was being used to capture the information to generate the dashboards and the analyses for the case interview data, which is what we started with- >> Yeah. >> Was essentially being used the same for the hospitalization data that we were getting and for tracking deaths as they were coming in as well. And so the bots essentially were just, we just took one process, take the same bots, copy them over essentially, and had them follow the very same process. We didn't try to introduce any different workflow than what was being done for the first one so we could replicate quickly. So I think it was lucky for us a lot- >> Dave V.: I was going to say, was that luck or by design? >> It was the same people doing the same analyses, right? So in the end they were thinking about how to be efficient themselves. So they kind of had coalesced around a similar process. And so it was kind of like fortunate, but it was by design in terms of how they- >> Dave V.: It was logical to them. >> Logical to them to make it. >> Interesting. >> So for us to be able to insert the bots became pretty easy on the front end. It's just now as we're trying to now expand to other areas that were now encountering like unique processes that we just can't replicate that quickly. We're having to like now dig into. >> So how are you handling that? First of all, how are you determining which processes? Is it sort of process driven? Is it data driven? How do you determine that? >> So obviously right now the focus still is COVID. So the the priorities scale that we've set internally for analyzing those opportunities really is centered around, you know, which things are really going to help our pandemic response, right? We're expecting another surge that's going to happen probably in the next couple of weeks. That'll probably take us through December. Hopefully, at that point, things start to calm down. But that means high-data volume again; these same process. So we're looking at optimizing the processes that we have, what can we do to make those cycles better, faster, you know, what else can we add? The data teams haven't stopped to try to figure out how else can they turn out new data reports, new data analysis, to give us a different perspective on the new variants and the new different outbreaks and hotspots that are popping up. And so we also have to kind of keep up with where they're going on these data dashboards. So they're adding more data into these reports so we know we have to optimize that. And then there's these kind of tangential work. So for example, COVID brought about, unfortunately, a lot of domestic violence reports. And so we have a lot of domestic violence agencies that we work with and that we have interactions with and to monitor their work, we have certain processes. So that's kind of like COVID-adjacent. But it's because it's such a very critical task, we're looking at how we can kind of help in those processes and areas. Same thing in like in our substance abuse area. We have substance use disorder treatment services that we provide. And we're delivering those at a higher rate because COVID kind of created more of a crisis than we would've liked. And so that's how we're prioritizing. It's really about what is the social need, what does the community need, and how can we put the technology work in those areas? >> So how do you envision the future of automation in your organization and the future of your organization? What does that look like? Paint a picture for us. >> So I'm hoping that it really does, you know, so we're going to take everything that's COVID related in the disease control areas, both in terms of our laboratory operations, in terms of our clinic operations, the way we respond, vaccination campaigns, things of that nature. And we're going to look at it to see what can efficiencies can we do there because it's a natural outgrowth of everything we've done on COVID up to this point. So, you know, it's almost like it's as simple as you're just replicating it with another disease. The disease might have different characteristics, but the work process that we follow is very similar. It's not like we're going to change everything and do something completely different for a respiratory condition as we would for some other type of foodborne condition or something else that might happen. So we certainly see very easy opportunities to just to grow out what we've already done in terms of the processes is to do that. So that's wave one, is really focus on that grow out. The second piece I think is to look at these kind of other general kind of community-based type of operations and see what operations we can do there to kind of implement some improvements there. And then I'm certainly in my new role of, in Deputy Director of Operation, I'm a CIO before. Now that I'm in this operations role, I have access to the full administrative apparatus for the department. And believe me, there's enough to keep me busy there. (Dave V. Laughing) And so that's going to be kind of my third prong is to kind of look at the implement there. >> Awesome. Go ahead, Dave. >> Yeah, so, this is going to be taking a step back, kind of a higher level view. If we could direct the same level of rigor and attention towards some other thing that we've directed towards COVID, if you could snap your fingers and make that happen, what would that thing be in the arena of public health in LA County in particular, or if you want California, United States. What is something that you feel maybe needs more attention that it's getting right now? >> So I think I touched on it a little bit earlier, but I think it's the thing we've been always been trying to get to is how to really become just very intentional about how we share data more actively, right? I don't have to know everything about you, but there are certain things I care about when you go to the doctor for that doctor and that physician to tell me. Our physicians, our healthcare system as you know, is always under a lot of pressure. Doctors don't have the time to sit down and write a form out for me and tell me everything that's going on. During COVID they did because they were, they cared about their patients so much and knew, I need to know what's going on at every single moment. And if I don't tell you what's going on in my office, you'll never know and can't tell us what's going on in the community. So they had a vested interest in telling us. But on a normal day-to-day, they don't have the time for that. I got to replace that. We got to make sure that when we get to, not me only, but everyone in this public health community has to be focused and working with our healthcare partners to automate the dissemination and the distribution of information so that I have the information at my fingers, that I can then tell you, "Here's what's going on in your local community," down to your neighborhood, down to your zip code, your census tracked, down to your neighbors' homes. We'll be able to tell you, "This is your risk. Here are the things that are going on. This is what you have to watch out for." And the more that we can be more that focused and laser-focused on meeting that goal, we will be able to do our job more effectively. >> And you can do that while preserving people's privacy. >> Privacy, absolutely. >> Yeah, absolutely. But if people are informed then they can make their own decisions. >> Correct. >> And they're not frustrated at the systems. David, we got to wrap. >> Sure. >> But maybe you can help us. What's your impression of the, first of all, is this your first Forward? You've been to others? >> This is my first time. >> Okay. >> My first time. >> What's your sort of takeaway when you go back to the office or home and people say, "Hey, how was the show? What, what'd you learn?" What are you going to say? >> Well, from just seeing all the partners here and kind of seeing all the different events I've been able to go to and the sessions there's, you don't know many times I've gone to and say, "We've got to be doing that." And so there's certainly these opportunities for, you know, more AI, more automation opportunities that we have not, we just haven't even touched on really. I think that we really need to do that. I have to be able to, as a public institution at some point our budgets get capped. We only have so much that we're going to receive. Even riding this wave, there's only so much we're going to be able to get. So we have to be very efficient and use our resources more. There's a lot more that we can do with AI, a lot more with the tools that we saw, some of the work product that are coming out at this conference that we think we can directly apply to kind of take the humans out of that, their traditional roles, get them doing higher level work so I can get the most out of them and have this other more mundane type of work, just have the systems just do it. I don't need anybody doing that necessarily, that work. I need to be able to leverage them for other higher level capabilities. >> Well thank you for that. Thanks for coming on theCUBE and really appreciate. Dave- >> It's been great talking to you guys, thank you. >> Dave, you know, I love software shows because the business impact is so enormous and I especially love cool software shows. You know, this first of all, the venue. 3,500 people here. Very cool venue. I like the fact that it's not like booth in your face, booth competition. I mean I love VMware, VMworld, VMware Explore. But it's like, "My booth is bigger than your booth." This is really nice and clean, and it's all about the experience. >> A lot of steak, not as much sizzle. >> Yeah, definitely. >> A lot of steak. >> And the customer content at the UiPath events is always outstanding. But we are entering a new era for UiPath, and we're talking. We heard a lot about the Enterprise platform. You know, the big thing is this company's been in this quarterly shock-lock since last April when it went public. And it hasn't all been pretty. And so new co-CEO comes in, they've got, you know, resetting priorities around financials, go to market, they've got to have profitable growth. So watching that that closely. But also product innovation so the co-CEOs will be able to split that up, split their duties up. Daniel Dines the product visionary, product guru. Rob Enslin, you know- making the operations work. >> Operations execution business, yeah. >> We heard that Carl Eschenbach did the introduction. Carl's a major operator, wanted that DNA into the company. 'Cause they got to keep product innovation. And I want to, I want to see R&D spending, stay relatively high. >> Product innovation, but under the heading of platform. And that's the key thing is just not being that tool set. The positioning has been, I think, accurate that, you know, over history, we started with these RPA tools and now we've moved into business process automation and now we're moving into new frontiers where, where truly, AI and ML are being leveraged. I love the re-infer story about going in and using natural national (chuckles) national, natural language processing. I can't even say it, to go through messaging. That's sort of a next-level of intelligence to be able to automate things that couldn't be automated before. So that whole platform story is key. And they seem to have made a pretty good case for their journey into platform as far as I'm concerned. >> Well, yeah, to me again. So it's always about the customers, want to come to an event like this, you listen to what they say in the keynotes and then you listen to what the customers say. And there's a very strong alignment in the UiPath community between, you know, the marketing and the actual implementation. You know, marketing's always going to be ahead. But, we saw this a couple of years ago with platform. And now we're seeing it, you know, throughout the customer base, 10,000+ customers. I think this company could have, you know, easily double, tripled, maybe even 10x that. All right, we got to wrap. Dave Nicholson, thank you. Two weeks in a row. Good job. And let's see. Check out siliconangle.com for all the news. Check out thecube.net; wikibon.com has the research. We'll be on the road as usual. theCUBE, you can follow us. UiPath Forward 5, Dave Vellante for Dave Nicholson. We're out and we'll see you next time. Thanks for watching. (gentle music)

>>The Cube Presents UI Path Forward five. Brought to you by UI Path. >>Hi everybody. We're back. David Ante with David Nicholson. This is UiPath Forward five from Las Vegas. We're live, you know, the customers here, they're automating all the time, sucking work and the cube. We're sucking all the information out of the experts and the customers. A bar Toban is here. He's the global business, Shared services, leading automation and AI at PepsiCo. And Para Colan is back is the chief. He's the Chief product officer at UiPath, longtime Cube alum. Great to see you guys. Thanks for coming on. Great to see us all day. So you guys keynote today, you know, excited to have PepsiCo on. I'm not sure I've ever interviewed PepsiCo in the Cube, but tell us about your role there. >>Absolutely. So I'm part of a PepsiCo global business shared services team. I lead automation and AI capabilities. GBS has, you know, we started GBS portfolio back about three and a half years ago, and we have a six hubs across PepsiCo. And as, as a part of my role, we deliver transformational capability across the PepsiCo. >>When did it all start? >>About three and a half years ago, 2019. So >>Prior to the pandemic. Yeah. You know, versus the pandemic was the catalyst for this. Yeah. But it was at the catalyst, but maybe it sped it up a bit. >>Yeah. PepsiCo journey started with, if, if you look at the PepsiCo, you know, the automation journey, it started back in 2017, but the GBS portfolio took shape back in 2019. So prior to that, you know, PepsiCo was definitely, you know, working a lot of, you know, the automation capabilities and automation product across, you know, PepsiCo. But with the introduction of PepsiCo global business shared services team, we are, you know, centralizing a lot of transformation capability, you know, across the functions that, that we support within the >>PepsiCo and, and UI path was kind of part of that journey all along? Or was there sort of other activities beforehand or how did that >>No, no, absolutely. Starting from 2017, if I, you know, remembered, you know, with the vision of our, you know, some of our senior leadership team and recognizing the value of, you know, automation in the core, you know, capability as a transformation at that time, you know, we started with just like anybody else, right? We started with, you know, proof of concept, showed some, you know, early wins and the value back to the business, start setting up some, you know, business processes and capabilities, stood up the platform, build a complete, you know, ecosystem around that, you know, platform partnership with, you know, UI bot team. And you know, from there, here we are five years. I mean, it's, it's a, it's a, it's a, it's a very critical component to our digital transformation capability and, and yes, leverage across >>Let's talk platform probably. So you, you guys have made some announcements this week. You talk about the business automation platform. I remember our first forward was, you know, RPA tool. Okay. Yeah. And then you guys made acquisitions. I was there for that. So the process process cold and then people started to really expand it, and it's really come in amazingly long away in a short time. So what did you guys announce today? What'd you talk about on stage 2022 dot 10? Tell us more about it. >>Absolutely, Dave. So you've seen the journey, you've been with us since the early days. You know, we were in 2017 and RPA tool that could automate a representative task that happened over and over again in the environment. And then three years ago you were here when we announced the automation platform, we said, it's not just about a task, it's about involving humans in bots to manage end to end processes. It's about discovering what automation opportunities exist. It's about using ai. Pepsi Co was actually the pioneer of using AI along with automation. You know, we were in stage together with them in, in 2019. And where we are now is we're essentially seeing people want to take the next step with automation. They're saying that it's no longer just an automation tool, It's the way we operate. It's the way we innovate in the organization. So they're really making sure that it becomes a part of their digital transformation journey that they're on. >>And they're saying that we can to the digital transformation by consolidating multiple RP systems and CRM systems. And that'll take us seven years to do, or we can go with UI path and we can leverage the core that we can leverage the GL system that exists today. We can leverage the inventory tracking system that exists today and start to build processes on top of that that can adapt to what customers are trying to do in this digital age. And that's where, you know, we've made announcements today is, is really pivot the platform to be a business automation platform. And there's sort of three layers, you know, unique but you know, connected layers of the platform. The first one is discover. And Discover is all about finding your processes, identifying the opportunities, making sure that you are managing the return on investment. What is the process? >>You know, how are you getting ROI on it? The second one is automated, and that is really where we're applying semantic automation to identify the digital building blocks of an enterprise, which is your data, your document, your screens and communication. Like putting all of that together and saying you can automate in our processes, leveraging a lot of intelligence that exist in how business processes are done. And the last one is operate, which is if you're trying to execute a business process at scale, you're processing not just, you know, a task thousand times, but you are fulfilling millions of transactions. You're, you know, you're looking at trillions of records to identify what processes you need, a scalable enterprise platform that's able to ingest a lot of data report on metrics report and efficiency. So that's what we've announced today is an automation platform that companies can use to put at the center of the digital transformation journey. >>So like about the interesting thing about PepsiCo, you guys started in 2017. Yeah. So kind of early, early on. Yeah. Yeah. And you kind of been there with the progression of platform. So my question to you is, and it was, you know, Yeah, we've seen the e from primarily on-prem now it's cloud first. Yeah. How disruptive or non disruptive was that for you? Did you have to rip and replace? Did you have to sort of retool or migrate? What was that like? >>No, I mean, significant disruption, right? I mean, I mean, as, as we started our journey back in 2017, just like, you know, PRM mentioned, right? With simple rule based, you know, the automation from then now to our journey where our continue to, you know, infuse, you know, AI capability, document understanding, conversation ai, right? As a part of our end to end profile. At the same time, I think the cloud is providing a fantastic opportunity for us to continue to scale, right? You know, scale at, at large. So that I think is a fantastic op, you know, fantastic platform and fantastic, you know, the opportunity that we are looking forward >>To. So how do you affect adoption inside of the organization? Can you talk about that? What's working? What's, >>It's always value driven as you know, right? I mean, the business business has to see the value. It it, it was, I mean, I would, you know, admit it was not as easy as before, but as the mindsets have started to shift, right? As the people have started to realize the value that, you know, the automation brings to, you know, the, I mean, you know, not just the, the value for the business, but actually transforming the entire portfolio, right? And, and people have started to see now that not every automation project is going to be transformation product, but for every transformation project you will find the automation at the heart and the core of it. So I, I, I think that's what has started to shift the mindset of, of uniforms. >>So how do you know when you have end to end? What are you still wake up one day and say, Wow, we've achieved it. You know, is it pieces that come together? Yeah. What do you say? >>Yeah, You know, we wanna look at customers from, you know, from an end to end perspective. It's not just about piecemealing finding a problem, solving it, really what does it deliver from, from an end to end perspective. Did you actually, you know, because a lot of times companies will say, we wanna automate X number of processes, and, and they do that and they're like, Well, we've automated a lot of processes. We're not sure what value we're getting out of it. It's the ability to measure like, what impact is this automation having on your business from an operational metric, but from a business metric as well. But then going back and saying, Well, where is the biggest pain point? Where do we have the largest value that we can give to the business back? So one of the things we actually announced today is the ability to take at an look at an idea and look at what was the estimated benefits of an idea, and then map it all the way through execution to say, what are we getting? >>We estimated we were gonna save a million dollars by doing those automation, or what have we achieved till now? Have we achieved a million dollars? Have we achieved half a million dollars by having achieved? That's, that never happens. That, and, and, and, and it's hard to do that, like the data existed, but it's really hard for people to pull that data out. So we build out the box dashboards that give you the ROI bag. And that's why it's really important to, to make sure that, you know, you look at it not just as a technology project, but more as a investment from a business side. And so you can, making a business more efficient. You >>Know, that's, I just, I know you were jumping in, but that's super important. Cause you know, you run a lot of projects Absolutely. And each of those projects has zone roi, then you jam it into the application portfolio. Exactly. And then everybody sort of forgets about it. You can't really track what impact it had because there's always, you know, some things that are benefit, some things are sometimes a negative. And so it's that holistic picture that >>You trying >>To achieve, extremely critical point, what you hit on, right? From it's measuring the benefit and measuring the continuous benefit across, and not just from start and end, Okay, what I promised I delivered or not, but, but you have to have this continuous mindset. And, and so I think yeah, definitely that, that's a very, very critical to our finance team in our cfo, >>Organiza, they're organic mechanisms and it's constantly >>Absolutely. Yeah. So abar, yeah. Global business shared services. Yeah. When you think of PepsiCo, yeah, of course people immediately think of Sure, Pepsi. But PepsiCo is a multi tentacled absolutely beast of a company. Absolutely. In a good way. Yeah. For organizations that are in that same category, holding companies, companies that have all sorts of different entities that are working together under one umbrella, How shareable is this idea of automation and business automation process moving forward? How, how shareable is that on the share oter? Yeah. Yeah. >>As >>Far as, as far as, as far as you're concerned, are you, are you talking to some people where you're saying, Hey, I'm here, I'm here from gvs and I'm here to help, and they look at you like you're crazy because you don't understand their business? Or is this something that relatively easily applies across >>Businesses that No, to your point, I mean, very valid point, right? I mean, it's, that's, that's the gbs, global business shared services mindset, right? As you move the functional areas into the Pepsi, in, into the PepsiCo gbs like hr, procurement, commercial sales, supply chain, right? That's where you gonna start to find those, you know, the optimization, you know, opportunity. You wanna start to standardize your processes, and that's where you will, you know, as you transition this processes within the gbs, that's what create those, you know, opportunities for you. >>What, >>What, what about automation opportunities? Not in the, I know you're in the sharing arena. Yeah, yeah. But each of those business units has processes that could probably be optimized and automated. Sure. Is that something that's under your purview? We've heard, we've heard a lot about citizen developers. Yeah. I don't know if that, if that >>Applies to No, that definitely. I mean, you cannot just have focus on end to end, you know, automation. I mean, that's, that's a huge portfolio for gps at the same time supporting, you know, automation through the citizen development capability. That that's where, once again, you know, you have had, provides a lot of capability and solution tools that we use, right? To continue to empower the folks who are part of our, you know, GBS team inside or outside gbs, right? It, it's, I think it's very, very critical. It, it, it helps people transform their career even in one ways, right? And, and, and, and you have that muscle, you have that resource, and you have that power. You definitely want to utilize that. >>So let's talk about metrics for a minute. So more data the better. Usually I like data. Yeah. But, but if you're trying to optimize for 15 metrics, I feel like you're not gonna optimize on any, So how do you deal with that from both as Paramo saying an operational standpoint and a business standpoint? What are the things about how do you sort of get the, the teams focused on the right things, >>Bi business, functional leadership team drive those alignment for us as a part of a global business, shared services, we, we are hip to have connected with our business, you know, functions, right? They, they have to help us prioritize those. And to your point, I mean, yeah, you cannot attack 15 metrics at once. You have to prioritize, you have to make sure that you bring the focus to the product. You have a project, right? So, so definitely, I mean, it's, it's, it's not often 15 metrics, but top three metrics, let's, let's focus, let's zoom in and ensure we are driving it. But then >>If you think about the system, I mean, at the end of the day, the p and l manager, he or she cares about ebit, let's say. Sure, okay. But there are so many factors, you know, in that complicated organization that are gonna affect ebitda. Yeah. And they're gonna be different. Yeah. But somebody's gotta figure out, okay, how do they fit together in a system? And, and can, can UiPath help me understand that, those relationships and those dependencies? >>Absolutely. I mean, I think there's a, there's an aspect of human relationships and, and making sure that you get the right level of sponsorship from the business and, and there's a business stakeholder and, and looking at every investment and, and outcomes that you're driving based on that. But, but that is something that we, from a tools perspective, we're trying to make sure that you can measure the value throughout the entire value chain. But then getting the business sponsorship, like where we've seen automation scale is always because there's a business sponsor that's essentially saying, Here's what I'm trying to achieve and here's the, here's my goal, here's the North star and go get it and let me know how you're tracking against it. And, and our job is to make sure that we can provide the visibility, the people that are operating the, the programs to make sure they get that level of visibility. >>What's the scope of automations in your, you know, organization? Is it dozens, hundreds, huge. That is thousands. >>We are getting there. >>Okay. >>No, definitely. I mean, we have definitely, you know, realized that it's, it's a core component to our digital transformation, right? So, so there is no, there's no stopping. I mean there, there, there, there's plenty of support from top down and you know, it's a fantastic time to be at PepsiCo. Right? Especially at the PepsiCo ubs, Right. >>So, Right. Thanks for sharing your story, Pam. Congratulations on all the progress you guys have made. It's actually quite remarkable to see where you guys have come from. So I really appreciate it. Thank you Dave. Thank you Dave. Okay. Thank you for watching. This is Dave Ante for Dave Nicholson. We are right middle of day two at forward five from Las Vegas. We're live, we're right back.

>>The Cube presents UI Path Forward five. Brought to you by UI Path. >>We're back the cube's coverage of UI path forward. Five. And we're live. Dave Velante with Dave Nicholson. AJ Gupta is here. He's the Chief Digital Transformation Officer at the Motor Vehicles of California dmv. Welcome Jay. Good to see you. >>Thank you. >>Good to see you. Wow, you, you have an interesting job. I would just say, you know, I've been to going to conferences for a long time. I remember early last decade, Frank Sluman put up a slide. People ho hanging out, waiting outside the California dmv. You were the butt of many jokes, but we have a happy customer here, so we're gonna get it to your taste >>Of it. Yeah, very happy >>Customer, obviously transform the organization. I think it's pretty clear from our conversations that that automation has played a role in that. But first of all, tell us about yourself, your role and what's going on at the dmv. >>Sure. Myself, a j Gupta, I am the Chief Digital Transformation Officer at the dmv. Somewhat of i, one would say a made up title, but Governor's office asked me, Okay, we need help. And that's what >>Your title though? >>Yeah, yeah. So I'm like, well we are doing business and technology transformation. So that's, that's what I've been doing for the last three years at the dmv. Before that I was in private sector for 25 years, decided first time to give back cuz I was mostly doing public sector consulting. So here I am. >>Okay. So you knew the industry and that's cool that you wanted to give back because I mean obviously you just, in talking off camera, you're smart, you're very cogent and you know, a lot of times people in the private sector, they don't want to go work in the, in the public sector unless they're, unless they're power crazy, you know? Anyway, so speaking with David Nicholson, the experience has gone from really crappy to really great. I mean, take >>It from here. Yeah. Well, am I gonna be, I'm, because I'm from California, I was just, I was just, you know, we >>Got a dual case study >>Eloquently about, about the, the, the change that's happened just in, just in terms of simple things like a registration renewal. It used to be go online and pray and weed through things and now it's very simple, very, very fast. Tell us more about, about some of the things that you've done in the area of automation that have increased the percentage of things that could be done online without visiting a field office. Just as an >>Example. Yeah, what's the story? >>Yeah, so first of all, thank you for saying nice things about dmv, you as a customer. It means a lot because we have been very deliberately working towards solving all customer po pain points, whether it's in person experiences, online call centers, kiosks, so all across the channels. So we started our journey, myself and director Steve Gordon about three years ago, almost at the same time with the goal of making Department of Mo no motor vehicles in California as the best retail experience in the nation across industries. So that's our goal, right? Not there yet, but we are working towards it. So for, for our in person channels, which is what you may be familiar with, first of all, we wanna make sure brick and click and call all the customer journeys can be done across the channels. You can decide to start journey at one place, finish at another place. >>All that is very deliberate. We are also trying to make sure you don't have to come to field office at all. We would welcome you to come, we love you, but we don't want you to be there. You have better things to do for the economy. We want you to do that instead of showing up in the field office, being in the weight line. So that's number one. Creating more digital channels has been the key. We have created virtual field office. That's something that you would become familiar with if you are not as a DMV customer. During Covid, the goal was we provide almost all the services. We connect our technicians to the customer who are in need of a live conversation or a email or a text or a, or a SMS conversation or chat conversation in multiple languages or a video call, right? >>So we were able to accomplish that while Covid was going on, while the riots were going on. Those of your, you know about that, we, our offices were shut down. We created this channel, which we are continuing because it's a great disaster recovery business continuity channel, but also it can help keep people away from field office during peak hours. So that's been very deliberate. We have also added additional online services using bots. So we have created these web and process bots that actually let you do the intake, right? You, we could set up a new service in less than four weeks, a brand new service online. We have set up a brand new IVR service on call centers in less than a month for our seniors who didn't want to come to the field office and they were required certain pieces of information and we were able to provide that for our customers by creating this channel in less than less than four. >>And the pandemic was an accelerant to this was, was it the catalyst really? And then you guys compressed it? Or were, had you already started on the >>Well, we were >>Ready. I mean you, but you came on right? Just about just before the pandemic. >>Yeah. Yeah. So I came on in 2019, pandemic started in 2020 early. So we got lucky a little bit because we had a head start at, I was already working with u UI paths and we had come up with design patterns that we gonna take this journey for all DMV channels with using UiPath. So it was about timing that when it happened, it accelerated the need and it accelerated the actual work. I was thinking, I'll have a one year plan. I executed all of the one year plan items in less than two months out of necessity. So it accelerated definitely the execution of my plan. >>So when you talk about the chat channel, is that bots, is that humans or a combination? Yeah, >>It's a, it's a combination of it. I would say more AI than bots. Bots to the service fulfillment. So there is the user interaction where you have, you're saying something, the, the chat answers those questions, but then if you want something, hey, I want my, my registration renewed, right? It would take you to the right channel. And this is something we do today on our IVR channel. If you call in the DMV number in California, you'll see that your registration renewal is all automatic. You also have a AI listening to it. But also when you are saying, Yep, I wanna do it, then bot triggers certain aspects of the service fulfillment because our legacy is still sitting about 60 years old and we are able to still provide this modern facade for our customers with no gap and as quickly as possible within a month's time. How >>Many DMVs are in the state? >>Okay, so we have 230 different field locations out of which 180 are available for general public services. >>Okay. So and then you're, you're creating a digital overlay that's right >>To all of >>That, right? >>Yeah, it's digital and virtual overlay, right? Digital is fully self-service. Bots can do all your processing automation, can do all the processing. AI can do all the processing, but then you have virtual channels where you have customer interacting with the technicians or technicians virtually. But once a technician is done solving the problem, they click a button and bot does rest of the work for the technician. So that's where we are able to get some back office efficiency and transaction reduction. >>When was the last time you walked into a bank? >>Oh man. >>I mean, is that where we're going here where you just don't have to >>Go into the branch and that is the goal. In fact, we already have a starting point. I mean, just like you have ATM machines, we have kiosks already that do some of this automation work for us today. The goal is to not have to have to, unless you really want to, We actually set up these personas. One of them was high touch Henry. He likes to go to the field office and talk to people. We are there for them. But for the millennials, for the people who are like, I don't have time. I wanna like quickly finish this work off hours 24 by seven, which is where bots come in. They do not have weekends, HR complaint, they don't have overtime. They're able to solve these problems for me, 24 >>By seven. And what's the scope of your, like how many automations, how many bots? Can you give us a sense? >>Sure. So right now we are sitting at 36 different use cases. We have collected six point of eight point, well, we have saved 8.8 million just using the bots overall savings. If you were to look at virtual field office, which bots are part of, we have collected 388 million so far in that particular channel bots. I've also saved paper. I've saved a million sheets of paper through the bot, which I'm trying to remember how many trees it equates to, but it's a whole lot of trees that I've saved. And >>How many bots are we talking about? >>So it's 36 different use cases. So 36 >>Bots? >>Well, no, there's more bots I wanna say. So we are running at 85% efficiency, 50 bots. Oh wow. Yeah. >>Wow. Okay. So you, you asked the question about, you know, when was the last time someone was in a bank? The last time I was in a bank it was to deposit, you know, more than $10,000 in cash because of a cash transaction. Someone bought a car from me. It was more of a nuisance. I felt like I was being treated like a criminal. I was very clear what I was doing. I had just paid off a loan with that bank and I was giving them the cash for that transaction as opposed to the DMV transaction transferring title. That was easy. The DMV part was easier than the bank. And you're trying to make it even easier and it shouldn't, it shouldn't be that way. Yes. Right. But, but I, I have a, I have a question for you on, on that bot implementation. Can you give us, you've sort of give it us examples of how they interact. Yeah. But as your kind of prototypical California driver's license holder, how has that improved a specific transaction that I would be involved with? Can >>You, so well you as a Californian and you as a taxpayer, you as a Californian getting services and you as a taxpayer getting the most out of the money Okay. That the DMV spending on providing services, Right. Both are benefits to you. Sure. So bots have benefited in both of those areas. If you were used to the DMV three years ago, there was a whole lot of paper involved. You gotta fill this form out, you gotta fill this other form out and you gotta go to dmv. Oh by the way, your form, you didn't bring this thing with you. Your form has issues. We are calculated that about 30% of paper workloads are wasted because they just have bad data, right? There is no control. There's nobody telling you, hey, do this. Right. Even dates could be wrong, names could be wrong fields, maybe incomplete and such. >>So we were able to automate a whole lot of that by creating self-service channels, which are accelerated by bot. So we have these web acceleration platforms that collect the data, bots do the validation, they also verify the information, give you real time feedback or near real time feedback that hey, this is what you need to change. This is when you need to verify. So all the business rules are in the bot. And then once you're done, it'll commit the information to our legacy systems, which wouldn't have been possible unless a technician was punching it in manually. So there is a third cohort of Californians, which is our employees. We have 10,000 of those. They, I don't want them to get carpal tunnel. I want them to make sure they're spending more time thinking and helping our customers, looking at the customers rather than typing things. And that's what we are able to accomplish with the bots where you press that one button, which will have required maybe 50 more keystrokes and that's gone. And now you're saving time, you're also saving the effort and the attention loss of serving the best. >>Jay, what does it take to get a new process on board? So I'm thinking about real id, I just went through that in Massachusetts. I took, it was gonna be months to get to the dmv. So I ended up going through a aaa, had to get all these documents, I uploaded all the documents. Of course when I showed up, none were there. Thankfully I had backup copies. But it was really a pleasant experience. Are you, describe what you're doing with real ID and what role bots play? >>Yeah, sure. So with real id, what we are doing today and what I, what we'll be doing in the future, so I can talk about both. What we are doing today is that we are aligning most of the work to be done upfront by the customer. Because real ID is a complex transaction. You've gotta have four different pieces of documentation. You need to provide your information, it needs to match our records. And then you show up to the field office. And by the way, oh man, I did not upload this information. We are getting about 15 to 17% returns customers. And that's a whole lot of time. Every single mile our customer travels to the DMV office, which averages to about 13 miles. In my calculation for average customer, it's a dollar spent in carbon footprint in the time lost in the technician time trying to triage out some other things. So you're talking $26 per visit to the economy. >>Yeah. An amazing frustration, Yes. >>That has to come back and, and our customer satisfaction scores, which we really like to track, goes down right away. So in general, for real, id, what we have been, what we have done is created bunch of self-service channels, which are accelerated by workflow engines, by AI and by bots to collect the documentation, verify the documentation against external systems because we actually connect with Department of Homeland Security verify, you know, what's your passport about? We look at your picture and we verify that yep, it is truly a passport and yours and not your wives. Right? Or not a picture of a dog. And it's actually truly you, right? I mean, people do all kind of fun stuff by mistake or intentionally. So we wanna make sure we save time for our customer, we save time for our, for our employees, and we have zero returns required when employees, where customer shows up, which by the way is requirement right now. But the Department of Homeland Security is in a rule making process. And we are hopeful, very hopeful at this point in time that we'll be able to take the entire experience and get it done from home. And that'll give us a whole lot more efficiency, as you can imagine. And bots are at the tail end of it, committing all the data and transactions into our systems faster and with more accuracy. >>That's a great story. I mean, really congratulations and, and I guess I'll leave it. Last question is, where do you want to take this? What's the, what's your roadmap look like? What's your runway look like? Is it, is there endless opportunities to automate at the state or do you see a sort of light at the end of the tunnel? >>Sure. So there is a thing I shared in the previous session that I was in, which is be modern while we modernize. So that's been the goal with the bot. They are integral part of my transition architecture as I modernize the entire dmv, bring them from 90 60, bringing us from 1960 to 2022 or even 2025 and do it now, right? So bots are able to get me to a place where customers expectations are managed. They are getting their online, they're getting their mobile experience, they are avoiding making field off his trips and avoiding any kind of paper based processing right? For our employees and customers as well. So bots are serving that need today as part of the transition strategy going from 1960 to 2022 in the future. They're continue gonna continue to service. I think it's one thing that was talked about by the previous sessions today that we, they, they're looking at empowering the employees to do their own work back office work also in a full automation way and self-power them to automate their own processes. So that's one of the strategies we're gonna look for. But also we'll continue to have a strategy where we need to remain nimble with upcoming needs and have a faster go to market market plan using the bot. >>Outstanding. Well thanks so much for sharing your, your story and, and thanks for helping Dave. >>Real life testimony. I never, never thought I'd be coming on to praise the California dmv. Here I am and it's legit. Yeah, >>Well done. Can I, can I make an introduction to our Massachusetts colleagues? >>Good to, well actually we have, we have been working with state of New York, Massachusetts, Nevara, Arizona. So goal is to share but also learn from >>That. Help us out, help us out. >>But nice to be here, >>Great >>To have you and looking for feedback next time you was at dmv. >>All right. Oh, absolutely. Yeah. Get that, fill out that NPS score. All right. Thank you for watching. This is Dave Valante for Dave Nicholson. Forward five UI customer conference from the Venetian in Las Vegas. We'll be right back.

>>The Cube Presents UI Path Forward five. Brought to you by UI Path. >>Hi everybody. Welcome back to UI Path Forward at five. You're watching the Cubes coverage. Everybody here is automating everything. Mundane tasks, Enterprisewide Automation Platform Beats product. Dave Nicholson. Dave Ante, Garish Pie is here. He is the Global head of Intelligent Enterprise Automation at Cognizant Global. Si, good to see you. Thanks for coming to the queue. Thank you for having me. Tell us about your role. What are you focused on? So, >>So I lead the enterprise automation practice at Cognizant, and we are focused on three broad segments, right? So we help customers anchor to business outcomes in, in looking at the business outcomes, what we look to do is help them drive transformation at a process level, looking at it from a technology standpoint, and then helping them look at how they're trying to drive change across their entire enterprise and bringing that together, you know, and helping them harmonize both at a technology and at a process level in terms of, you know, the outcomes they're trying to achieve. So >>You guys are a partner, I see your booth over there, and you're also a customer, right? Yes, we are. So are you involved in the both sides? One side, what, what, what's your purpose? >>So we do, so we, we sort of work, So we have a full 360 degree relationship with the i p. So we work with them, you know, in a professional services capacity. They, they support us as a partnership in the marketplace where we go into a number of our customers jointly to drive turnkey transformational engagements from an automation standpoint and second from a, as a, as a, as a customer to UiPath, they've been supporting us, you know, drive a number of automation initiatives across our operations book over the course of the last two years. >>Okay. So tell us more about that. So you started your internal journey, we had you guys on last year. Yep. It were just getting started I think, I think I think you, your head count is what, 60,000 somewhere around? Yeah. 70,000. Yeah, $70,000 growing. I think at the time it was maybe less than 10% of the workforce was kind of automated and the goal was to automate everybody. How are you guys doing along >>The, I think it's starting to in industrialize quite significantly. So over the course of the last year since we last spoke to you, probably, you know, we've doubled the head count in terms of the number of people that are now, you know, officially what we call quote unquote citizen developers. And you know, how they are driving automation at a personal level, we've probably gone about 2.5 x in terms of the number of RS we've saved. So we've done about, I think 450,000 rs, you know, in terms of actual saves at a personal automation level. And look, it's, it's been a great, you know, last 12 months too, right? Because, you know, as we've sort of started to get the message percolated more and more, our teams have started to get energized. They are happy that they are, you know, getting a release in terms of what they're doing on a day to day basis, which is largely repetitive at times, very mundane. And now they have the ability to bring in technology to be able to embrace that and drive that, that you know, much more efficiently. >>Are you talking dozens of bots? Thousands of bots? What's the scope of? >>So I think we've, we've scaled to about 3,500 today in terms of the bots and, and it's, it's a journey that continues to evolve. For me, the number is probably something which I wouldn't anchor to because it's, look, it's end of the day what you end up releasing and what you end up freeing and what the teams are doing. And I think, you know, that's the way we are >>Leading. So you're saying like, we always talk about number of boss, but you're saying it's largely in a relevant metric? Well, and not if it's five versus a thousand. Okay. That's meaningful, right? But, but >>Yeah, I think look a number for me, I think it's not about the number, right? It's about the outcome and it's about what impact you're having in, in terms of, you know, what you're trying to get done at the end of the day, right? Because ultimately you're trying to better, you know, what you do on a day to day basis and you know, whether it's done through 10 or whether that's done through 10,000. >>Yeah. But you pay >>Form, >>Right? Exactly. So, so you better get some value out. Exactly. It's about the value. >>But is there, is there a, is there a curve in terms, you know, an s-curve in terms of scalability though? I mean we, we, we've heard organizations doing, from organizations doing an amazing amount of modernization and automation and they say they've got 15 bots running, you have 3,500. Is there a number where it becomes harder to manage or, or is there scalability involved? >>So look, for me, so let me answer it this way, right? I think, I think there are two aspects to it. I think the, the, the, the more you have, you know, the bigger the challenge in terms of how you run the controls, the governance and the residency in terms of, you know, how you manage the, you know, the, the setup of the bots itself. So I think, yeah, I mean we want to have it to a manageable number, but for us, in the way we've looked at the number of bots, one of the things that we've done is we also look at, you know, what's foundational versus what's nuanced in terms of the kind of use cases that you're trying to deliver. So, so any program of this nature, you need to have a setup, which is, you know, which allows you to sort of orchestrate it in the right manner so that as you sort of scale and you bring more people into that equation, you, it's, you're not just creating bots for the sake of it, but you're actually, you know, trying to look at what you can reuse, what you can orchestrate better. >>And then in the context of that, figuring out where you have the gaps and then hence, you know, sort of taking the delta approach of what else and what more you need to build it. >>So you guys have a big observation space. You work with a lot of customers and, and so what are you seeing as the trends when you look out there? How are you applying it to your own business and your customer's businesses? >>So look, for me, I think the last two years, if anything, the one thing I've taken away is that transformation is now extremely, extremely compressed, right? So, so it's almost, you know, what's true today is probably irrelevant tomorrow. So, which means you have to continually evolve in terms of what needs to be done, right? Second is experiences have become extremely, extremely crucial and critical and experiences of, in, in my mind, you know, two or three kinds, right? One the end customer second from an employee standpoint, and third, in terms of the partner ecosystem that you will have as an enterprise that you have to cater to, right? The other element that you know, which becomes true will always remain true is the whole outcome story in terms of, you know, how we have an anchor to why you're trying to do what you're trying to do. >>And that is, you know, core to what you need to get done. So in the way we've looked at it, as we've said, you know, as you sort of look at how transformation is now evolving and how compressed it's starting to become, the more you are able to orchestrate for what the enterprise is trying to get done in terms of modernization, in terms of digitization, in terms of end goals and end outcomes that they're trying to achieve. And the more you're able to sweat what sits within, you know, the enterprise bring that together as you think about automation is, you know, where the true value lies in terms of being able to create an agile enterprise. >>When you think about digital transformation, digital experiences, if it's, if it's a layer cake, where is automation in that, in that layer? Is it, is it sort of the bottom of the stack? Is it, is it the whole stack? >>So for me it's, I mean it's, it's evolved. If you take today's view, I think what's emerging is a very pervasive view of how you think about automation. It sits across, you know, the entire enterprise. It, it, it, it takes a people process, technology dimension, which is age old. It has to cover, you know, all forms of transformation. You know, whether you're looking at end, how do I say, impact in terms of how you're dealing with customers, whether you're looking at the infrastructure, whether you're looking at the data layer in between, it has to be embedded across the base, right? It, it, you have to take a pervasive approach. And for me, I think automation increasingly in the days ahead is gonna be an enterprise capability. You know, it has to be, you know, all pervasive in the way it needs to be set up. >>The key, the operative word there is pervasive. And that seems to be, you know, the era that we're entering, I don't know what you call it, call it the metaverse, I mean, you know, it's more than cloud and cloud is basically just the infrastructure, right? You're building on top of that, whether it's natural language processing or cryptography or virtual, I mean, there's so many different, you know, technology dimensions, right? But it, but the point about pervasive, okay, it's everywhere. It's sensing, it's anticipatory, it feels like there's this new, you know, construct, emerging of platform that is the basis for digital business, right? And I, and I feel like every 15 years our industry goes through some big transformation. How, how do you see it? You know, do you agree that you, it feels like, okay, something new is happening. It's, it's not gonna be the social media, you know, Facebook's not gonna continue to dominate the world as it does. You already seen some cracks in that armor. We saw Microsoft after the pc, and then of course it came back with cloud Amazon looks, you know, indestructible. But that, that's never the end story, right? In our, in our world, how do you see that? >>No, I think all of what you said, I, I would sort of tend to agree with, for me, look, I don't have a crystal ball to say, you know, what's gonna happen with Facebook or Amazon or >>Otherwise. Yeah. But that's what makes this fun. But >>I, Yeah, but, but I think for me, the, the core is I think you're dictated by, you know, us as end consumers, if you're a B2B or a b2b, b2c, you know, depending upon what business you're in, I think the end customer value dictates, you know, what evolves in terms of, you know, the, the manifestation of, you know, how you will two minutes sort of deliver services, the products that you'll get into. And in that context then, you know, whether you take a, a TikTok view to it or whether you take an Amazon view to it, or whether YouTube becomes relevant in the days ahead, I think it's gonna be dictated by, >>By customer, but it tends to be a technology that's the disruptor, it's the microprocessor or it's the social capability or, or maybe it's ai that, that is the catalyst for that. And then the customer adoption dictates, oh, you're right about that. But there, but the, the match is usually technology. Is that fair or not necessarily? Yeah, >>I still look, I mean you talked about metaverse earlier, right? I think we are, I think we are, it's probably hype more than it is reality right now, at least in my view. And it's, I think we are significantly out in terms of, you know, large scale adoption in terms of what needs to be done. You talk about blockchain, blockchains been around, you know, for at least a decade if not more in, in, right. The way it's being talked about, the adoption, you know, in terms of the, the, the applicability of the, you know, of what is that technology I think is understood, but the actual use cases in terms of how it can be taken into the market and how you can scale it across industries, I think is, you know, is still because >>The economics determine ultimately exactly the outcome. So, Okay, that makes sense. >>Yeah. Now you said you don't have a crystal ball. I, I have one, but when I look into it, it's sort of murky when I try to figure out the answer to the question, Is a platform necessary for this, for automation? I mean, this is really the direction, the question, the existential question in terms of the trajectory of UI path. It seems obvious that automation is critical. It's not as obvious where that automation is going to end up eventually because it's so critical. It feels like it's almost the same as, okay, there's an interface between my keystrokes and filling in a box with text. Well, of course there has to be, there has to be that interface, right? So why wouldn't everyone deliver that by default? So as you gaze into my crystal ball with me, tell me about the things that only a platform can do from your perspective. >>So, >>So, so, so think of it this way, right? I mean, any enterprise probably has hundreds of technologies that they've invested in some platform, some applications that you would've built and evolved over time, which are bespoke custom in nature. So for me, I think when you think about automation, I think it's the balance between the two. What a platform allows you to do is to be able to orchestrate, given the complexity and the, the spa that is any enterprise, you know, that's probably got the burden of, you know, what they've done over the course of the, the previous years. And then in that context then, you know, how do you sort of help get the, the best value out of that in terms of what you want to deliver as the end, end outcomes, if I can call it that, right? So for me, I don't think you can say it's, it's her platform versus the rest. >>I think it's gonna be, it's always gonna be a balance and to the question that you asked earlier. And in terms of saying where does an automation end up at? I think if it's gonna be a pervasive view, look, you know, if, if clients are trying to modernize and get onto the cloud, you can do automation at a cloud level too. Now, you know, do I say then, you know, is it, is it sort of inclusive or it's native to what the cloud providers offer? Or do I then go and say automation needs to be something which I will, you know, sort of overlay on top of what the cloud providers offer. So I think it depends upon what dimension that you come at it. So I don't think you can say it's one or the other. You have a platform, I think it helps you orchestrate quite significantly. But there are gonna be aspects within any enterprise, given the complexity that exists that you will have to balance out, you know, platform versus, you know, how you have to address it maybe in a more individual capacity. >>Garris, gotta go. Thank you so much. Appreciate your perspectives. Good conversation. All right, keep it right there. But trains will back it up. We'll be right back right after this short break. The cube live at UI path forward, five from Las Vegas.

(upbeat music) >> Announcer: theCUBE presents UiPath Forward5. Brought to you by UiPath. >> Hi everybody, we're back in Las Vegas. We're live with Cube's coverage of Forward 5 2022. Dave Vellante with Dave Nicholson Ted Kumer this year is the Executive Vice President, product and engineering at UiPath. Brought on to do a lot of the integration and bring on new capabilities for the platform and we've seen that over the last several years. And he's joined by Dr. Edward Challis, who's the co-founder of the recent acquisition that UiPath made, company called Re:infer. We're going to learn about those guys. Gents, welcome to theCUBE. Ted, good to see you again. Ed, welcome. >> Good to be here. >> First time. >> Thank you. >> Yeah, great to be here with you. >> Yeah, so we have seen, as I said, this platform expanding. I think you used the term business automation platform. It's kind of a new term you guys introduced at the conference. Where'd that come from? What is that? What are the characteristics that are salient to the platform? >> Well, I see the, the evolution of our platform in three chapters. You understand the first chapter, we call that the RPA chapter. And that's where we saw the power of UI automation applied to the old problems of how do I integrate apps? How do I automate processes? That was chapter one. You know, chapter two gets us to Forward3 in 2019, and the definition of this end-to-end automation platform you know, with the capabilities from discover to measure, and building out that core platform. And as the platform's progressed, what we've seen happen with our customers is the use of it goes from being very heavy in automating the repetitive and routine to being more balanced, to now where they're implementing new brought business process, new capability for their organization. So that's where the name, Business Automation Platform, came from. Reflecting now that it's got this central role, as a strategic tool, sitting between their application landscape, their processes, their people, helping that move forward at the rate that it needs to. >> And process mining and task mining, that was sort of the enabler of chapter two, is that right? >> Well, I'd say chapter two was, you know, first the robots got bigger in terms of what they could cover and do. API integration, long running workflows, AI and ML skills integrated document processing, citizen development in addition to professional development, engaging end users with things like user interfaces built with UiPath apps. And then the discovery. >> So, more robustness of the? Yeah, okay. >> Yeah. Just an expansion of the whole surface area which opened up a lot of things for our customers to do. That went much broader than where core RPA started. And so, and the other thing about this progression to the business automation platform is, you know, we see customers now talking more about outcomes. Early on they talk a lot about hours saved and that's great, but then what about the business outcomes it's enabling? The transformations in their business. And the other thing we're doing in the platform is thinking about, well, where can we land with solutions capabilities that more directly land on business, measurable business outcomes? And so we had started, for example, offering an email automation solution, big business problem for a lot of our customers last year. And we'd started encountering this company Re:infer as we were working with customers. And then, and we encountered Re:infer being used with our platform together. And we saw we can accelerate this. And what that is giving us now is a solution now that aligns with a very defined business outcome. And this way, you know, we can help you process communications and do it efficiently and provide better service for your customers. And that's beginning of another important progression for us in our platform. >> So that's a nice segue, Ed. Tell about Re:infer. Why did you start the company? >> Right, yeah, so my whole career has been in machine learning and AI and I finished my PhD around 2013, it was a very exciting time in AI. And me and my co-founders come from UCL, this university in London, and Deep Mind, this company which Google acquired a few years later, came from our same university. So very exciting time amongst the people that really knew about machine learning and AI. And everyone was thinking, you know, how do we, these are just really big breakthroughs. And you could just see there was going to be a whole bunch of subsequent breakthroughs and we thought NLP would be the next breakthrough. So we were really focused on machine reading problems. And, but we also knew as people that had like built machine learning production systems. 'Cause I'd also worked in industry that built that journey from having a hypothesis that machine learning can solve a problem to getting machine learning into production. That journey is of painful, painful journey and that, you know, you can see that you've got these advances, but getting into broad is just way too hard. >> So where do you fit in the platform? >> Yeah, so I think when you look in the enterprise just so many processes start with a message start with a no, start with a case ticket or, you know, some other kind of request from a colleague or a customer. And so it's super exciting to be able to, you know, take automation one step higher in that process chain. So, you could automatically read that request, interpret it, get all the structured data you need to drive that process forward. So it's about bringing automation into these human channels. >> So I want to give the audience a sense here. So we do a lot of events at the Venetian Conference Center, and it's usually very booth heavy, you know, brands and big giant booths. And here the booths are all very small. They're like kiosks, and they're all pretty much the same size. So it's not like one vendor trying to compete with the other. And there are all these elements, you know I feel like there's clouds and there's, you know, of course orange is the color here. And one of the spots is, it has this really kind of cool sitting area around customer stories. And I was in there last night reading about Deutsche Bank. Deutsche Bank was also up on stage. Deutsche Bank, you guys were talking about a Re:infer. So share with our audience what Deutsche Bank are doing with UiPath and Re:infer. >> Yeah, so I mean, you know, before we automate something, we often like to do what we call communications mining. Which is really understanding what all of these messages are about that might be hitting a part of the business. And at Deutsche Bank and in many, you know, like many large financial services businesses, huge volumes of messages coming in from the clients. We analyze those, interpret the high volume query types and then it's about automating against those to free up capacity. Which ultimately means you can provide faster, higher quality service because you've got more time to do it. And you're not dealing with all of those mundane tasks. So it's that whole journey of mining to automation of the coms that come into the corporate bank. >> So how do I invoke the service? So is it mother module or what's the customer onboarding experience like? >> So, I think the first thing that we do is we generate some understanding of actually the communications data they want to observe, right? And we call it mining, but you know, what we're trying to understand is like what are these communications about? What's the intent? What are they trying to accomplish? Tone can be interesting, like what's the sentiment of this customer? And once you understand that, you essentially then understand categories of conversations you're having and then you apply automations to that. And so then essentially those individual automations can be pointed to sets of emails for them to automate the processing of. And so what we've seen is customers go from things they're handling a hundred percent manual to now 95% of them are handled basically with completely automated processing. The other thing I think is super interesting here and why communications mining and automation are so powerful together is communications about your business can be very, very dynamic. So like, new conversations can emerge, something happens right in your business, you have an outage, whatever, and the automation platform, being a very rapid development platform, can help you adapt quickly to that in an automated way. Which is another reason why this is such a powerful thing to put the two things together. >> So, you can build that event into the automation very quickly you're saying? >> Speaker 1: Yeah. >> Speaker 2: That's totally right. >> Cool. >> So Ed, on the subject of natural language processing and machine learning versus machine teaching. If I text my wife and ask her would you like to go to an Italian restaurant tonight? And she replies, fine. Okay, how smart is your machine? And, of course, context usually literally denotes things within the text, and a short response like that's very difficult to do this. But how do you go through this process? Let's say you're implementing this for a given customer. And we were just talking about, you know, the specific customer requirements that they might have. What does that process look like? Do you have an auditor that goes through? And I mean do you get like 20% accuracy, and then you do a pass, and now you're at 80% accuracy, and you do a pass? What does that look? >> Yeah, so I mean, you know when I was talking about the pain of getting a machine learning model into production one of the principle drivers of that is this process of training the machine learning model. And so what we use is a technique called active learning which is effectively where the AI and ML model queries the user to say, teach me about this data point, teach me about this sentence. And that's a dynamic iterative process. And by doing it in that way you make that training process much, much faster. But critically that means that the user has, when you train the model the user defines how you want to encode that interpretation. So when you were training it you would say fine from my wife is not good, right? >> Sure, so it might be fine, do you have a better suggestion? >> Yeah, but that's actually a very serious point because one of the things we do is track the quality of service. Our customers use us to attract the quality of service they deliver to their clients. And in many industries people don't use flowery language, like, thank you so much, or you know, I'm upset with you, you know. What they might say is fine, and you know, the person that manages that client, that is not good, right? Or they might say I'd like to remind you that we've been late the last three times, you know. >> This is urgent. >> Yeah, you know, so it's important that the client, our client, the user of Re:infer, can encode what their notions of good and bad are. >> Sorry, quick follow up on that. Differences between British English and American English. In the U.K., if you're thinking about becoming an elected politician, you stand for office, right? Here in the U.S., you run for office. That's just the beginning of the vagaries and differences. >> Yeah, well, I've now got a lot more American colleagues and I realize my English phrasing often goes amiss. So I'm really aware of the problem. We have customers that have contact centers, some of them are in the U.K., some of them are in America, and they see big differences in the way that the customers get treated based on where the customer is based. So we've actually done analysis in Re:infer to look at how agents and customers interact and how you should route customers to the contact centers to be culturally matched. Because sometimes there can be a little bit of friction just for that cultural mapping. >> Ted, what's the what's the general philosophy when you make an acquisition like this and you bring in new features? Do you just wake up one day and all of a sudden there's this new capability? Is it a separate sort of for pay module? Does it depend? >> I think it depends. You know, in this case we were really led here by customers. We saw a very high value opportunity and the beginnings of a strategy and really being able to mine all forms of communication and drive automated processing of all forms of communication. And in this case we found a fantastic team and a fantastic piece of software that we can move very quickly to get in the hands of our customer's via UiPath. We're in private preview now, we're going to be GA in the cloud right after the first of the year and it's going to continue forward from there. But it's definitely not one size fits all. Every single one of 'em is different and it's important to approach 'em that way. >> Right, right. So some announcements, StudioWeb was one that I think you could. So I think it came out today. Can't remember what was today. I think we talked about it yesterday on the keynotes anyway. Why is that important? What is it all about? >> Well we talked, you know, at a very top level. I think every development platform thinks about two things for developers. They think, how do I make it more expressive so you can do other things, richer scenarios. And how do I make it simpler? 'Cause fast is always better, and lower learning curves is always better, and those sorts of things. So, Re:infer's a great example of look the runtime is becoming more and more expressive and now you can buy in communications state as part of your automation, which is super cool. And then, you know StudioWeb is about kind of that second point and Studios and Studio X are already low code visual, but they're desktop. And part of our strategy here is to elevate all of that experience into the web. Now we didn't elevate all of studio there, it's a subset. It is API integration and web based application automation, Which is a great foundation for a lot of apps. It's a complete reimagining of the studio user interface and most importantly it's our first cross-platform developer strategy. And so that's been another piece of our strategy, is to say to the customers we want to be everywhere you need us to be. We did cross-platform deployment with the automation suite. We got cross-platform robots with linear robots, serverless robots, Mac support and now we got a cross-platform devs story. So we're starting out with a subset of capabilities maybe oriented toward what you would associate with citizen scenarios. But you're going to see more roadmap, bringing more and more of that. But it's pretty exciting for us. We've been working on this thing for a couple years now and like this is a huge milestone for the team to get to this, this point. >> I think my first conversation on theCUBE with a customer was six years ago maybe at one of the earlier Forwards, I think Forward2. And the pattern that I saw was basically people taking existing processes and making them better, you know taking the mundane away. I remember asking customers, yeah, aren't you kind of paving the cow path? Aren't there sort of new things that you can do, new process? And they're like, yeah, that's sort of the next wave. So what are you seeing in terms of automating existing processes versus new processes? I would see Re:infer is going to open up a whole new vector of new processes. How should we think about that? >> Yeah, I think, you know, I mean in some ways RPA has this reputation because there's so much value that's been provided in the automating of the repetitive and routine. But I'd say in my whole time, I've been at the company now for two and a half years, I've seen lots of new novel stuff stood up. I mean just in Covid we saw the platform being used in PPP loan processing. We saw it in new clinical workflows for COVID testing. We see it and we've just seen more and more progression and it's been exciting that the conference, to see customers now talking about things they built with UiPath apps. So app experiences they've been delivering, you know. I talked about one in healthcare yesterday and basically how they've improved their patient intake processing and that sort of thing. And I think this is just the front end. I truly believe that we are seeing the convergence happen and it's happening already of categories we've talked about separately, iPass, BPM, low-code, RPA. It's happening and it's good for customers 'cause they want one thing to cover more stuff and you know, I think it just creates more opportunity for developers to do more things. >> Your background at Microsoft probably well prepared you for a company that you know, was born on-prem and then went all in on the cloud and had, you know, multiple code bases to deal with. UiPath has gone through a similar transformation and we talked to Daniel last night about this and you're now cloud first. So how is that going just in terms of managing multiple code bases? >> Well it's actually not multiple Code bases. >> Oh, it's the same one, Right, deployment models I should say. >> Is the first thing, Yeah, the deployment models. Another thing we did along the way was basically replatform at an infrastructure level. So we now can deploy into a Kubernetes Docker world, what you'd call the cloud native platform. And that allows us to have much more of a shared infrastructure layer as we look to deliver to the automation cloud. The same workload to the automation cloud that we now deliver in the automation suite for deployment on-prem or deploying a public cloud for a customer to manage. Interesting and enough, that's how Re:infer was built, which is it was built also in the cloud native platform. So it's going to be pretty easy. Well, pretty easy, there's some work to do, but it's going to be pretty easy for us to then bring that into the platform 'cause they're already working on that same platform and provide those same services both on premises and in the cloud without having your developers have to think too much about both. >> Okay, I got to ask you, so I could wrap my stack in a container and put it into AWS or Azure or Google and it'll run great. As well, I could tap some of the underlying primitives of those respective clouds, which are different and I could run them just fine. Or/and I could create an abstraction layer that could hide those underlying primitives and then take the best of each and create an automation cloud, my own cloud. Does that resonate? Is that what you're doing architecturally? Is that a roadmap, or? >> Certainly going forward, you know, in the automation cloud. The automation cloud, we announced a great partnership or a continued partnership with Microsoft. And just Azure and our platform. We obviously take advantage of anything we can to make that great and native capabilities. And I think you're going to see in the Automation Suite us doing more and more to be in a deployment model on Azure, be more and more optimized to using those infrastructure services. So if you deploy automation suite on-prem we'll use our embedded distro then when we deploy it say on Azure, we'll use some of their higher level managed services instead of our embedded distro. And that will just give customers a better optimized experience. >> Interesting to see how that'll develop. Last question is, you know what should we expect going forward? Can you show us a little leg on on the future? >> Well, we've talked about a number of directions. This idea of semantic automation is a place where you know, you're going to, I think, continue to see things, shoots, green shoots, come up in our platform. And you know, it's somewhat of an abstract idea but the idea that the platform is just going to become semantically smarter. You know, I had to serve Re:infer as a way, we're semantically smarter now about communications data and forms of communications data. We're getting semantically smarter about documents, screens you know, so developers aren't dealing with, like, this low level stuff. They can focus on business problem and get out of having to deal with all this lower level mechanism. That is one of many areas I'm excited about, but I think that's an area you're going to see a lot from us in the next coming years. >> All right guys, hey, thanks so much for coming to theCUBE. Really appreciate you taking us through this. Awesome >> Yeah Always a pleasure. >> Platform extension. Ed. All right, keep it right there, everybody. Dave Nicholson, I will be back right after this short break from UiPath Forward5, Las Vegas. (upbeat music)

>>The Cube presents UI Path Forward five. Brought to you by UI Path. >>Hi everybody. We're winding down. Day two, a forward five UI Path customer conference. This is the fourth time the Cube has been at a forward. Dave Nicholson, Dave Ante. Maureen Fleming is here. This is a program Vice President idc. She's got the data fresh survey data. We'd love to have the analyst on. And Kevin CRO is back on the cube. He's a partner for intelligent automation and digital. Upscaling is the operative word. Kevin, good to see you again, pwc. Good to see you. Thanks for coming on you guys. Yep. All right. We, we love idc. We love the data. You guys are all about it. So you've just completed a recent study. Tell us all about it. Who'd you survey? What was the objective? What'd you learn? >>Yeah, what we wanted to do was try to learn more about people who are adopting robotic process automation. So mainly large, you know, larger to midsize, enter midsize, large enterprises. And we wanted to figure out how many of them had a citizen developer program. And then we wanted to compare the difference between people who do not have that program and people who do, and what the difference is in terms of how, what kind of reach they have inside the enterprise, and also the different ways that, that they valued it. So the difference, so we asked the same questions of the, of these people without them knowing that we were actually looking for a citizen developer. And then we compared the results of that to see is it more valuable to have citizen developer and enterprise, or is it more valuable to have enterprise only? So what was the impact >>Global survey? >>It was North America. >>North America. Was it, was it we any kind of slice and dice in terms of industry or targets or you, >>We, we kept it across industry, cross industry. We're finding that RPA is adopting cross >>Industry way. Was it, was it UI path specific or more Any tech, Any automation, >>Any rpa. >>Okay. And top two or three findings. >>So one thing was, first off, the rapid growth rate in citizen, citizen developer programs grew 47% over a two year period. And so now for people who've adopted rpa, it's the majority there. They're, you know, it's a pervasive trend to >>See you're taking over, >>You know, right now the conclusion from that, and some other studies that I did that have similar conclusions is that we have to start learning to live with this idea that business users can learn how to develop. They are developing their driving value. And so now we just need to figure out how to build these sorts of programs accurately. And the other, the really key finding of it was that, that there was much more significant reach for people that were doing citizen developer plus enterprise automation, more reach, more processes touched, more employees impacted by it. And then on top of it, the, they rated the value, the people who had the combination rated the programs at a higher value across different measures. So effectively the, the combination is working out better than standalone top down automation. >>So Kevin, from what, what's your takeaway here? What does this mean to you and your customers? >>So I guess a, a couple things and just anecdotally, you know, building on what Marine found in the, in the survey, the concept of citizen development is a real concept and it's something that organizations are applying and trying to figure out how to apply at scale. The reason why they're doing it is twofold. One, early automation efforts struggled to get scale and they struggled to deliver value from a scale perspective. There were two major problems. The ability to identify the right opportunities and the ability to tackle a wide range of, from the little to the very large, often teams focus on the very large, but don't focus on the little, the little is important. The second part is thinking about how you create a better culture of innovation and actually drive identifying opportunities for the, the more, I'll call it technology professionals to focus on. And so, you know, there's been, you know, based on that big drive to say, okay, not how do we replace automation professionals with business users, you know, the random accountant, the random operations analyst. It's more around how do you actually engage them in innovation. And that in, in that engagement may involve actual hands on building of bots and technologies like UiPath or it might just involve generating ideas to get further engaged. >>So 47% growth. What's the catalyst for that kind of growth? Where's that come from? >>I scarcity? So, well there are a couple things. One is, you know, we all know about developer scarcity and it's strive to automate. You know, if you have an automation strategy in place, you wanna do this quickly and aggressively. But if you've got a shortage of, of people, you know, developers don't have enough, they're turning over. Then you go to, you go and figure out, well this is low code. And so why can't we train our business users who are the subject matter experts to do automation for themselves or their teams? So sort of think about this as the long tail, the things that that top down like enterprise, I think UiPath is calling it enterprise automation versus people automation. So, you know, so there's just different things that they work on as well. And there's also, you know, fearlessness on the part of a lot of people on the business side, they're not afraid of technology, they're not afraid of getting trained. >>And the other piece to me that made, like, I've covered this topic for a long time, and what I found originally when people started talking about citizen developers is that they, they were calling me and having inquiry about why these programs were failing. And when we would decompose the failure was because the ma their managers didn't give them any, they didn't put 'em in trading but wouldn't get, give 'em time to develop. And so they just could not, you know, they just were running into problems. And so with things that, things like PWC and what they're doing, they're sort of saying, here's the, here are the features of a program that matter, including being given time to develop and do that as part of your job. So >>Maureen, is there a minimum level size of organization that you find taking advantage of this? I mean, you know, where's the sweet spot for the value delivered from this kind of automation? >>Do you have an idea? Right. So we, we tended in some of the surveys, we tended to do like thousand employees up. So we were screening for that. But I also met with the, our, our analysts who covered smb, small midsize. She said that they've had that for a long time because they don't have these clear distinctions between IT and business. So then the question is, who are adopters of rpa, for example? And you know that that's still a little bit at, at, you know, the enterprise level, but, but citizen developer at it, it, it is SB is just a given concept. So, >>But is it, is there, is there an economy of scale that kicks in at a certain point? Have we been able to figure that out? I'm thinking of, I'm thinking of business process automation being such a competitive advantage that there becomes almost a divide because of smaller organization. Yes, they could go out and they can buy, they have access to the same software packages, but you have to build all of those processes. Yes. You have to develop those processes over time. So is there any sense for a divide possibly happening or what the, >>It's a really good question because they, you know, in a way people have to understand what a business process is, you know, and they need to understand what the technology can do. And so from that perspective, people who have thought leaders inside their organization and maybe have a chance to get out and look at broader topics might be more inclined to try this out and also identify directly as a problem. SMB also tends to try to buy package solutions. And you see larger enterprises say, well, you know, what we do is unique and so we should just sort of use horizontal technology and apply it at will where it's needed. And so for me that's kind of why we organize toward higher, you know, higher si, larger sizes. As it gets simplified, it's gonna go down into the SMB market though. >>So Kevin, when it comes to you guys, your client engagements, upscaling keeps, keep coming back to that word low code. Is it fundamental component of upscaling? Is it, is it, I don't say synonymous, but is it a prerequisite to have low code capabilities to scale? >>You know, from our perspective, I think the two biggest challenges with making this work, one is learning and development. How do you actually teach the skills in a way that allows people to apply them very quickly and give them the time to actually function right to the finding about managers not necessarily being supportive. And so you have to figure out, you know, what, you know, how do you actually create that right environment and give people the right tools? It's an area that we invested really heavily in from the PWC side with the, with the launch of our pro edge platform and really thinking about how to solve that. But then the problem that you're ultimately getting at once you solve the people equation is how do you get scale and how do you move quicker? And so the, you know, the, the, the, the biggest challenge is not should you let a, a business user build a bot. It's, you know, how do we actually build many bots, generate many ideas for the professional developers and actually create an ecosystem to move faster. Every client that we work with, it's all about, you know, how we're not moving fast enough. A COE cannot, you know, by itself automate an entire organization. And so, you know, the, you know, the, the this theme of scale really becomes, you know, the critical aspect of this >>Is the former other words, the the teaching and individual how to build a bot. Is that trivial or, or is that really not the big gate is what you're saying? It's, >>We don't think it's a big gate. I think the, you know, to the original question, I think the, the, the low code space is a ripe spot for this, you know, upskilling construct because you're not, you're not, you're, you're gauging with employees who don't have an undergraduate degree in computer science who are not IT professionals. And so giving someone, you know, a book on job and saying, go build an application's, probably not gonna be very productive. But with, with tools in the, in the low code space, be it RPA or be it other forms of lower code technology, you get people opportunity where they need to learn some technical concepts. You need to understand how the technology works and how basic programming techniques work, but you don't need to understand everything. And again, going back to the, the simple versus the complex, the goal here is not to turn people into professional developers. The goal is to get them engaged and, and create, you know, make them part of that company's digital transformation. >>But from what you just described, that's, to me it's basic logic skills. I mean you don't have to be, like I say, a assembly language programmer. Yeah. But you gotta understand and you gotta know the business process, right? I mean you have to be a domain expert. Yeah. >>But that, but that's the, that's the biggest advantage of this. You're engaging the people closest to the business process, right? You look at how most big IT projects failed was the same reason a lot of early automation efforts failed. You're creating, you know, a function that essentially lives in an ivory tower that's focused on, you know, where can I go out and find opportunities and automate. But you're not, those aren't the people that run the process day to day. Yeah, okay. You, you put it, you make those people that run the process day to day accountable, you're gonna get a different outcome >>And they'll lean in and get excited. Exactly. >>So where, where, where is that transition? I know it's easy to say, oh, you know, it's logic and people can do it, but what about having a bot whisperer in your, in your organization who's who, who literally says, you know, Maureen, I'm gonna come and sit with you on Friday and you're going to explain your frustrations to me and I'm gonna sit right next to you and I'm gonna code this bot for you and we're gonna test it and you're gonna tell me if it does what you want it to do. And Maureen doesn't need to understand how to move the widgets around and do anything. >>It's, you know, it's a great question cuz I think it's changing the nature of how you accelerate these efforts, right? I think you know, the, and if I go into early RPA days, the initial kind of thought process was let's just get a factory in here and build as many bots as possible. A lot of our client engagement today isn't always around our bot development services. It's around can you bring in coaches? Can you hold office hours? Exactly. We have an office hour construct, which I've never really had in my consulting career where we put, you know, I mean this obviously post covid when when people are in their offices, we put someone in a room and people can come by and get help. And I think having that, that coaching and mentoring construct is very helpful. What we've also seen, and I think it's a really critical success factor for clients to make this work, is thinking about how they pick a subset of their population and making them, you know, digital accelerators, digital champions, pick your word, not it professionals, peers who will actually get realtime dedicated. Right. And maybe a full time or a halftime job where that's exactly what they do. >>Maureen, we're out of time, but my last question for you is, when you do a survey like this, you know you have open ended sometimes and you analyze a survey, you take a bath in the data, write it up. There's always something that you wish you'd asked, which is great cuz then you could do it on the next one. What, was there anything in there that you wish you'd asked that you're gonna ask in the next one? Are you gonna explore in the next survey? >>Yeah. One of the things that I asked, one thing that I was glad I asked was, I, I, we, we spent time finding what were considered business side product champions or RPA champions and then we ask 'em what they did, how often they did, how much time they spent. But what I want, what I really, really wanna ask of my next survey, and I will, I've got a planned, is to find out how, how what percentage of population is involved with, with big a citizen developer and what activities are common and what are less common and you know, what their challenges are. So we'll be looking at a different kind of audience with this next >>Survey. Well, we'd love to have you back to talk about that. Just invite, Thank you very much. Come queue. Really appreciate it Kevin. Good to see you again. >>Good to see you. >>All right. And thank you for watching. Keep it right there. Dave Nicholson and Dave Ante. We're here wrapping up day two of UI path forward. Five live from the Venetian, all Las Vegas. Super right back.

>>The Cube presents UI Path Forward five. Brought to you by UI Path. >>Welcome back to The Cube's, continuous coverage with day two of UI Path forward. Five. My name is Dave Ante. I'm here with my co-host Dave Nicholson. And you are watching The Cube. It's all about the robots, the automations, the transformations and beyond. Audi Gana is here. She's group executive at Vodacom and Niva is back. She's senior director of telecommunications industry for UiPath. Ladies, welcome to the Cube. >>I thank you very much. >>So Vodacom a leading telco in in Africa across the continent. Tell us more about the company. >>The company is a traditionally telecommunications company, but our vision 2025 is first to transition from being a telco to a technology company. So you'll find that a lot of the use cases that we've actually started embarking on, combined the combination of telco and FinTech. And we've got a lot of RPA bot also supporting the FinTech platform, which is quite a major step in our strategy. >>So, you know, it's interesting Mark Andreessen's famous comment, Every company's a software company. I like to think every company's a technology company, technology driven. So what does that actually mean for you? Is it like a split brain between FinTech? Cuz it's pretty clear that FinTech is always a highly, you know, technology oriented and telecom. Are they sort of together driving a, a technology business? How does that >>Work? It's, it's a, it's a converge use of the technology to add value to the customer. So what we wanna do is to get to the point where we have converged services where the Telecommunicate, cuz at the end of the day in the African market, you'll find that there's a lot of markets that are unbanked. So you find that a cell phone is a means of communication and a a mobile platform for the users. So it's a natural progression for our company to actually play in both spaces. And I think one of the things I find quite interesting is the levels of trust that a lot of citizens have in our financial platform. In that even some of the governments are paying social grants using the platform. And so it almost becomes, without the phones a lot of people cannot function type of scenario. >>Nevas is your role a global role? >>Yes, it is a global role. >>Okay. So it's interesting cause you're I think based down under, right? I am. Is that true? Okay. Obviously spent some time in, in, in the African continent. How are you, what are you seeing in terms of the, the trends in, in telecommunications that, and are you noticing there's gotta be differences across different regions? You know, a lot of times you hear, oh no, there's really kind of a global world out and I know it is, but telco seems to be one of the industries that has some uniqueness within the different breaches. What are you seeing? >>Look, we are privileged to work with more than 200 telecoms around the world. But clearly from a technology perspective, there are some regions that have embraced technology sooner than the others, particularly when it comes to automation. Now we do have use cases with all of them that we are, you know, the 200 we are working with. But the extent to which they become strategic partners, Varie is, you know, what I find is in, in the US we are doing a lot in the customer experience space with the telecoms in aj it's more back of house. And with telecoms like Vodacom, it's really strategic. You know, automation is being applied practically in every facet of work. And you know, sometimes that could be because the demand is just so great for connectivity, you know, at times there's a skills gap, but it does vary. But what's reassuring is that there is a journey and you know, at this event what I have seen is telecoms wanting to learn from other telecoms. And I must say Artie has been in huge demand. We did about 22 meetings yesterday with others wanting to know, which again is that strategic trend. >>Artie, my understanding is you've been at this for a while, this automation journey for quite some time and p i pass. Interesting. I mean it's a company that's founded in 2005 and kind of did sort of its own thing for a long time and then realized it had lightning in a bottle Yeah. For a mid last decade. But my understanding is you've seen it all. You've seen the, the legacy platforms. And so tell me about your personal journey with automation and then the companies. >>Okay, so there's the automation pre rpa, which was strangely enough, I come from banking, got a finance degree, did automated ations in one of the bigger banks. And somehow I transitioned. And I mean from a history perspective, the one of the previous platforms, which was the biggest one at the time, that's where I got to learn about rpa. And then there's another vendor that we then use in another company. So this is almost my third vendor that I'm experiencing in the RPA space. Having joined RPA space in 2015, apparently I'm kind of a veteran, >>So, So what are you seeing is what's the difference between, I mean let's call UI path, that was sort of a modern focus on simple to deploy. That's really how they get started when I first found them. How do you compare what UiPath has? And there are others, there are other modern platforms to sort of the legacy platforms. What's the >>Difference? I think it's the diversity and the applicability of the technology across multiple industries is something that still amazes me up until today. Because the kind of customers I've been meeting today, I, I would not, I met a guy who owns an ice cream company and I'm like, where would automation come in here? But he's actually quite a big customer of, of UiPath, you know. So I think that's one thing I appreciate. I think the ease of use, it has actually allowed for a lot of people to be part of the digital transformation. I think in the his, in the past technology has been seen as something that was a bit elite and that you needed to have X amount of skills and level of education. Whereas the RPA industry has almost bridged that gap in actually bringing along as many people in the journey in terms of digital transformation. And the fourth industrial revolution is now starting to become more inclusive >>Horizontal across industries. >>Yeah. >>So Vodacom headquartered in South Africa. Okay. But presence throughout the continent. Yes. I imagine that various geographies have various twists and quirks to them and different needs. But as a general premise, the African continent has led the rest of the world in terms of embracing these little mobile devices for the most mission. Critical from a personal perspective things, right? Yeah. So if you, if you're already trusting all of your finances and even interaction with your government from a financial perspective. Yeah. When you say technology platform technology is moving forward, what's more critical from that? Or how do you, how do you, how do you branch off from that? What are some of the other things that you can share with us that you're looking towards in the future that may, that that may trickle over here eventually? >>So I think what one of the things we started playing around with quite well is actually the convergence of machine learning, AI and rpa. You would find that a lot of research will tell you that this is the future of the automation and for us, we are actually living the future in that we have civil use cases that are actually extracting a lot of business value. Where we've realized that RPA in of itself, and this is obviously oversimplifying the technology is almost the unlimited hands on keyboards that you could ever have, right? And then machine learning and AI almost the becomes the unlimited brains. So when you then combine the tool, you almost have this strong technology that can revolutionize how we operate and service our customers. >>Well how do, how does that translate? Can you translate that into a user experience at this point? So I mean, we're talking about people who they, they have a motor license, they don't have a desktop computer at home. Yeah. This is their portal into the world. >>So you find that if you're speaking pure telco, and I'm obviously over simplifying there some nowhere an engineer, right? But I think at, at a very simplified level, there's a lot of legacy technology that is used in the telco space and you'll find that because of that, there's a lot of lack of integration. And you'll find that the reasons why a lot of customers call corners is because there's poor integration in a lot of instances. And it's, it's, it's, it's ad hoc. So it's not as if the system is failed completely. So what we've now done is to try and see how do we use machine learning to pick up on those anomalies on the network, right? And because each time something breaks, right, it's almost a fixed way to fix it and therefore the machine learning picking up there normally almost the hands over to the RPA bot to fix the problem within the network element. But that means is that from a customer experience perspective, instead of you actually realizing there's a problem, we've fixed it before you even know that there's a problem. And therefore, and as you can imagine, it means that you then call the course into less because now you don't have the reason to complain because we've proactively identified the problem and we proactively use RPA then to fix it. So we almost have the almost like a self-healing element in within the, the, the RPA AI space. >>You know, I think of, we don't talk about the data, we haven't talked about the data much this week. I think in many respects this industry is, is data industry. Our automation is all about what you can do with the data. You said unlimited hands, unlimited brains. Cuz to me you have unlimited data and a lot of times you just can't handle it. Yeah. So what's the data angle on all this? >>So firstly, I know a lot of people will say data is the new oil. No, >>Right? So I would never >>Say that. I always though, I think I always ask people if I give you a bucket of brain crude oil, right? What are you gonna do with it? Right? Right. And similar to data, right? So I want to almost equate data to that crude oil element, but if you don't know how to refine it, process it, get it to be reliable, it's very useless in of its natural sense. So I think one of the things we've realized is that leveraging of the analogy of the, the machine learning in the brain, if you are in the sales space, you forever trying to push new sales, right? And then chances are when a customer leaves you, you are almost in a reactor state. So, and I imagine a world where you could proactively identify a customer with the propensity to leave your company because a lot of customers don't just, they are situations where they'll be walking down the street competitor calls them, they leave, not because they were unhappy, but a lot of customers actually had several engagements with us that were not pleasant, whatever the definition is. >>So we then saw there was almost five types of attributes that resulted in customers leaving us. So what then that said was imagine if you are an account manager, right? And you got told UiPath P two I limited has experienced 1, 2, 3, 4. Right? Actually, please go engage with them because something is happening. It means that as an account manager, you are then equipped to have a meaningful engagement with the customer because you're saying, hi UiPath, I see you've had X amount of job calls and you've had x amount of complaints in our call center. What is happening is it could be, could be your network, maybe the tower where you are, do you, And then the conversation becomes so meaningful. And I think even during covid what we found is lot of customers started using less of our data, not because they were unhappy, but it became an affordability thing, right? >>Because this is a thousands and thousands of, of data elements and pieces around Yeah. About customer transactions. There's no way one human would be able to go through all of the data and make me meaningful decisions out of it. So we then found that some customers were complaining about affordability. So we then built another model that says if an account manager is talking to a customer and they're struggling from an affordability perspective, what's the next best offer you can make to your customer while you're engaging? And then if in, if, if now your UiPath takes up that offer, then you'd find that the bot does the post engagement provisioning on the system. Because now if you then said, I've only, I can only afford 10 lines, but only pay 10 gigs, but not 10 lines and 20 gigs, that is at least better than us losing the customer. >>Yeah. Right? And we offering them almost a downward migration type of situation. Then the bot does that on the system. So you would find that we almost playing in the space of a human, human centered, intelligent automation where machine learning becomes the brain, the person is amplified in how they operate at the customer. And then the RPA bot becomes the hands that executes on that. And as the account manager you focusing on engagement and convincing, which is really what people are great and selling as opposed to going through all of the pro cause VOCA is a lot of products. So as opposed to having a person going through the products and trying to find the best product for you, you know, so we, we are using machine learning to assist the >>Humans. I I mean in every, every interaction is consistent in that case. I know I sometimes have to call three or four times to find a professional that knows enough that can help me. Yes. Such a frustrating thing as a consumer. So you are, are you, you're attacking churn with automation. So we haven't even talked about how you guys are working together, your journey and all that stuff, but, but how are you guys working here? What are you, what are you doing? You know, in addition to what you just described with with ui. iPad? >>So I think my portfolio's quite wide. So I am, my team is in every single vertical in the organization from customer care to the consumer enterprise business units to finance technology, network compliance. And we do all of this in about six countries, right? So one of the things we've actually realized is that if we are looking at customer service, we wanted to understand why do customers call us? And I think I came from a point of ignorance because I'm not from telco, so I actually realized that if we're talking billing and finance revenue assurance, customers call us because we build them arly. But technically speaking it's our systems that there's something that resulted in the customer calling us. So why do we not know about our own systems? Why are we waiting for the customers to call us? And literally those are the questions I was asking cuz I felt like why are we, why are we waiting for the customers to call us? >>So we then then found a way to try and see within the billing systems where do the breakages happen, right? So that we fix them before the customer has to call us again. So then again from a billing perspective, it means that cuz it the billing element can come in two ways where we are giving you a service and not charging you for it. We then have revenue leakage or we, you are consuming something and we are overcharging you. Then you call us and say, Whatcom is stealing my data. Yeah, you're right out there. I promise you nobody wakes up in the morning and wants to take one gig of your data. So it almost becomes a day integrity initiative that results in good customer service but then result in eradication of course. As opposed to us waiting for customers to tell us what the problem is and trying to help them fast. Cuz that's generally always been what I've picked up the energy around customer service. How do we help you fast? I'm saying why must you call us when our systems had fail that? So we almost trying to see how do we use the technology internally to give customers a better experience and then also have the financial benefits that we are now starting to see happening in the, >>What's the scope of, of your like how many automations, how many bots? Can you give us a sense >>Of this? So right now I think we over on with all of the four, five countries that we are in, we over 400 bots. Wow. Okay. So we started in 2004 years ago, this is my fourth year in Voca. We, and we are not using just one product with UiPath. It became a platform because as we became across more kinds of problems, I think what I've appreciated about part is how we've actually created a partnership. Instead of them trying to sell me products for the sake of consuming products, it became a, this is my problem, right? And then somehow they would whip out the product that solves my problem type of thing. So it became a ecosystem of solutions that >>You must love hanging out with Artie. >>I absolutely do and love, you know, I've spent a career in telecommunications myself and you know, the best days were when you could deliver an outstanding customer experience. And as you can see from what Artie has achieved when you were more proactive and predictive, you can serve your customers so much more effectively and that just lift the morale of the team because we all, you know, have this purpose in doing our jobs. But this is automation and AI built into every part of that customer journey. So end to end, you know, the customer's much happier. You know there's a problem before the customer knows you can solve the problem in most cases before they even know. And that's just what we are all in business to do to make things better. >>Great story. Thank you so much for sharing. Appreciate coming back >>In the queue. Thank you very much. Thank >>You. Thank you for watching. Keep it right there. Don't forget, go to silicon angle.com, all the news, go to the cube.net. You'll see me all these videos are available on demand as well as the other events that we do. Dave VTE for Dave Nicholson. Keep it right there. Right back at forward five UI.

>> Presenter: theCUBE presents UiPath FORWARD5 brought to you by UiPath. >> Back to theCUBE's coverage of UiPath FORWARD5, 2022. This is theCUBE's 4th UiPath FORWARD. They're mining automation gold here at the conference and in the customer base and we're creating Cube Gold, Dave Vellante and Dave Nicholson. Cheryln Chin is here. She's the vice president of Global Alliances at UIPATH. Sameer Bohra, who's the director of Information Technology at Deloitte. Good to see you guys. >> Great. >> Thank you. >> Now normally we would be talking about, how Deloitte's out, doing its thing with its customers, but this is actually a case study on Deloitte's use of automation and UiPath, so that's cool. You not only partner with the GSIs you actually sell to them as well. Okay. What's that all about? What's your relationship like? Why don't you start there? >> Absolutely. So we're thrilled to be here. Thanks for having us. And really appreciate Sameer being here with us. Deloitte was an early adopter of UiPath not just as a partner, driving innovations and investing in getting skilled and building the capability. They were the first to become the US and certified partner network investing in thousands and thousands of skilling up their consultants and resources to help us address our customer needs together. But it's not just about being a great partner it's being a customer with what they've done and built their own business around UiPath and the automations. We've got an amazing story to tell you about today that we'd love to share. >> All right, Sameer, let's hear it. What's the story? What was the catalyst to bring in automation, UiPath? Where are you applying it? Where'd you start? >> Fantastic, well first of all, thanks for having me here. >> You're welcome. >> I'll start this journey with the predictions that we were making at some point. So, Deloitte, as a company, we are in the business of predicting the technology trends. We have been tracking automation as a trend for quite some time, and we have been following how this industries going to come along. And we then started placing our bets not just on the technology, but on the vendor as well in this case. Right around 2017, 18 is when we started kind of implementing automation with UiPath for our internal purposes. And as it happens, different constituents in our member firms started doing it at the same time without kind of consulting with each other. But the surprising thing is that we all ended up with the same results. We all ended up with UiPath. We all ended up using the same technology set and it was good that we all made the same choice because we would then all get along with it together. So we started our journey kind of disintegrated in a way and then we came along quickly all together. We then have COEs in each of our member firms, or at least the big member firms. And around January last year is when we signed an enterprise license agreement with UiPath that really brought some of our mature COEs together. And now we are kind of utilizing the product quite well. We are exploring the benefits of that ELA brings to us. So that has been our journey so far. Just in terms of some numbers, we are more than 400 millionaires saved for our member firm. We have hundreds of processes that we have automated. I'm kind of losing count of that already. And we have a good 70, 80 member team members across our three mature COEs that are constantly automating day in and day out. So there's a lot in terms of the history and there's a lot that we are looking forward to. >> Can you paint a picture of sort of where you're applying these automations in your business and maybe double click on that a little bit? >> Absolutely. So when we started our journey, there were some candidates right off the bat there were some of our enabling areas where we were looking at for instance, finance our talent which we also called as HR. Those were some of our preliminary areas that we started doing automations for. But another surprising thing is that our first automation use cases were actually contingent solutions that we built to help some of the other big deployments that were happening in the firm. And in absence of any good solution, we said, "Let's bring in RP and let's bridge the gap." And that basically opened the door for us to use automation at a bigger scale. So it's enabling area, talent, finance, business operations. Those are the prominent areas, marketing, chief culture, those are the areas that we are applying it. And then our services on the other hand are using automation as well because we need our services people to be armed with the valuable time to be able to invest on our clients rather than, being stuck in repetitive mundane tasks. So we are pretty much applying it all over the board now. >> So as director of IT at Deloitte, I'm curious about how this process works for you. You've heard the term drinking one's own champagne. >> Yeah. >> When you are looking... >> 'or jog fooding, but okay. >> I was trying to be polite, right? One throat to choke one bat to pat, back to pat. Are you immediately and at all times under a microscope when you're deploying something internally because someone else in Deloitte is thinking, "Okay, let's see how this works for us. Because if it works well, if we gain expertise, we can turn this into a line of business to help our clients." Is that something that starts day one? Or do people come to you six months into a project and say, "Hey, I hear you have something going on. That's cool." What's that look like? >> Very interesting question. The way I would like to describe it is we have a symbiotic relationship between our internal COE and our client facing teams that are out in the market selling automation along with UiPath. And the way that symbiotic relationship work for us is when we are doing anything interesting in terms of an automation use case, and we have many that I can talk about, we do have this constant connect with our client facing folks where we tell them about the use case. We tell them about the problem that we are solving and the way in which we are solving that problem. And in many cases, it generates interest. And then we get into conversations where we see, okay is it an asset that we can build out of it? Or is it simply a client use case that we could burn and implement and apply somewhere? So that's one side of the symbolic relationship. The other side is what our client service folks are seeing in the market. So when they see it, they come to us and they tell us, "Look, we see such and such client doing this and we did it for them. We should think about doing this in Deloitte and for ourselves." And then we say, "Fantastic, let's do it." So it's both ways. >> Dave: Both ways. And the fact that it is both ways. There is not that sense of pressure or you know that I'm under a microscope. It's all one big family. >> How do you measure success? >> It's a pretty interesting question again, success is subjective, right? When it comes to automation the typical metrics that people use to define and describe success is how many hours you have saved or how many hours, at least the way we use it how many hours you have reinvested, right? So we started with that as our measure and for some time that was really our measure of success. But lately we are seeing a change in that we are now shifting more over to other matrix like cost avoidance. So for instance, your firm is growing at a certain pace. Do all your enabling areas need to grow at that pace? Maybe not. Maybe we can avoid that cost and maybe we bring in more automation to support that. So cost avoidance is kind of emerging as a bigger matrix for us now, especially given that all low hanging automation fruits have been plucked. That's a big one we are looking at. I think the other matrix which is a bit difficult to measure directly is the employee satisfaction. There's somewhere I read that if you want happy clients you need to have happy employees first, right? And one way of making your employees happy is to give them the task that they really value that they really like to do. Now, again, being a professional services firm are ours are people's, our is our currency, right? So we want to give them as much of their valuable time back so they can invest it in their client facing activities as opposed to, you know doing mundane and ones. So those are some of the matrix and measures we are looking at. >> So I'd like to dig into that a little bit. If I could Sameer. So, aren't hours saved sort of related to cost avoidance? Is that an input to the cost avoidance calculation, if you will? >> So yeah, so yes and no. And the reason I say that is because yes, if you do the math, yes, it makes sense, >> 'not that it's direct. I understand it's not a direct relationship but it's somewhere related. Is it not? >> It is related in the sense that our saved is an immediate measure of automation, right? So if me as a practitioner, if I can hand over a task to the bar, which can take off five hours out of my week, that's an hour saved right away. But cost avoidance is more like, "Hey, I have these 10 engagements that are coming up. Do I need to amp up to meet boost end engagement or I simply amp up my automation, right?" So that's more around the cost avoidance piece. >> Okay. So there's an algorithm there. >> Yeah. >> Which makes sense. Do you find, so in other words, when you save hours at some point it's going to translate it to headcount avoidance. Okay, are you finding that when you run a project if you can automate that project, that the proportion of savings is greater on that automation of the project than it is for those sort of hours saved? I'm just sort of curious as to what the balance looks like. Is it like overwhelmingly speeding up the project? Is the real benefit there? I'm just kind of curious. >> There's absolutely a benefit there. With automation, you can obviously speed up your projects, you can do more with the staff and the team that you have. So that's definitely something that helps us a lot both internally and I believe on the client facing side as well. >> Okay. And just put my CFO hat on. Let's, so are those internal resources or are there sort of out of pocket expenses? In other words, it's the hard dollars that I don't spend or is it resources that I can deploy on another project or both? Or both. >> For the most part it's the resources right? >> So it's okay. >> Yeah, it's the resources that you can now have them do more value work with more clients as opposed to have them do many task at one place. >> Okay, I'm going to just keep going. So that's a productivity measure in my mind anyway, so I just like to keep peeling the onion on the metrics. So I would at some point, so the two things the cost avoidance and the employee satisfaction I would ultimately as the CFO want to see that show up in terms of productivity increases and decreases in turnover. And you probably don't have enough experience yet to measure that. But ultimately, isn't that where you want to go? >> I think that's essentially where it's going and I think that's the way it'll probably go for pretty much everyone who is in this journey of automation at your CFO will eventually want to look at, okay what after this investment, where is it leading us? So that's definitely the direction we are also heading. >> Yeah and so productivity revenue per employee, is that a good starting point? Maybe you get more sophisticated than that, but... >> Yeah, that's probably a good starting point. >> UiPath revenue employees about 250,000, which is pretty average for software companies. Now, maybe it's because they're investing more, but at some point I'd like to see that tick to 350,000 anyway. >> Yeah. >> I Digress. >> And we are on that journey where we are essentially looking to arm everyone with a bot right? There's a philosophy and UiPath around a bot for everyone. We are pretty close to getting to that stage where everybody should be able to leverage the technology. We shouldn't be limited to a certain business unit or certain pockets within a business unit. >> I want a bot. I do, I want a bot, I'm getting a bot. >> I wish I have a bot. >> I would, yeah, I want to a bot and I want to give that bot a very clever name. That's like you're thinking of naming bots. So are your activities evaluated in completely independently as sort of your own P and L or do you get credit for some of that symbiotic relationship that's developed? Because I can imagine a situation where you deploy something intelligent automation and you get a yield that translates into a practice for your firm that brings in a bunch of revenue with a bunch of satisfied customers. Do you get credit for that? Or is it like, no, no, no, no. I wouldn't >> I would love to get credit for that. But again, it's all in the family. It's all one big family. At this time we are simply focused on bringing the right use cases forward for our client facing folks and the other way around. So we haven't got into that stage as left. >> But you need to deliver standalone value. You're evaluated that way. >> And this COE. That's what we are evaluated upon. The matrix that I talked about earlier around cost avoidance, number of our saved employee satisfaction. Those are some of area that we are being rated upon. And that's across all our COEs. >> Oh, surely congratulations on landing Deloitte as a customer and of course a partner. And I'm sure there's big things in the future. We'll give you the last word, bring it home. >> You know, the takeaway here is we are leveraging partners like this who are going way beyond just automating processes for the sake of process and our save the using this to build their business make their consultants more productive and really driving profitability for the business. So really the automation flywheel going beyond that's really trying to fuel digital transformation by taking this, they make it go faster, more profitable, more agile, and they become an amazing customer and an amazing good market partner. >> Yeah, you guys take this pretty seriously behind us there's this, I don't know what you call it but this clouds floating above it. If you walk through there, there's some really inspiring commentary. And so I encourage you to do that if you're here at the show. All right, thanks guys, appreciate it. >> Thank you. >> Thank you. >> You're welcome. All keep it right there Dave Vellante and Dave Nicholson will be back at FORWARD5 UiPath customer event from Las Vegas. We're live right back. (soft music)

>>The Cube presents UI Path Forward five. Brought to you by UI Path. >>Hi everybody. Welcome back to Las Vegas. You're watching the Cube's coverage of UI Path Forward. Five. We reach cruising altitude on day two. Christina Seacrest is here. She's the process Artificial intelligence and automation GPS automation leader at ey. And Bob PCIs, executive director for Intelligent Automation for the state of Tennessee. Folks, welcome to the cube. Thank you for Adam. >>Good >>To have you. Okay, I don't know if I messed up that title, Christina, but it's kind of interesting. You got process, you got ai, you got automation, you got gps. What's your role? >>I have a lot of rules, so thank you for that. Yeah, so my focus is first and foremost automation. So how do you get things like UI path into our clients, but also I focus specifically in our government and public sector clients. So sled specifically. So state local education. So that's why I'm here with the state of Tennessee. And then we also like to take it beyond automation. So how do you bring an artificial intelligence and all the technologies that come with that. So really full end to end spectrum of >>Automation. So Bob, when you think about the sort of the, the factors that are driving your organization of, how did you describe that, Those sort of external factors that inform your strategy. What, what's, what are the catalysts for how you determine to deploy technology? >>Well, it was primarily that we know tendency has a tendency to provide good customer service, but we want to get to a great status best in class, if you will. And we had an external advisory review where it said, Hey, you know, we could make automation to improve our customer experience. And so that was like a directive of the, the state leaders to go across the board and automate all processes statewide, starting with the 23 executive agencies. >>So where's the focus from that standpoint? Is it on just providing better interfaces to your constituents, your customers? Is it cutting costs or you actually have more budget to invest? Kind of a combination of >>Those? Yeah, so it's, it's really both qualitative and quantitative, right? So quantitative is where we're able to reduce hours and therefore we can redirect people to more less mundane work, if you will. And then qualitative is where we're able to reduce the errors, improve data quality, reduce cycle time for our citizens, you know, when they're making requests, et cetera. So it's, I think it's a combination of both of those quantitative and qualitative metrics that we are mandated in, in micromanaged, quite frankly to, to bring, make those >>Numbers. So I'm from Massachusetts, when I go to a a mass.gov website, I say, all this was done in the 1990s and you could just see where the different stovepipes were, were. But then every now and then you'll hit one and you'll say, Wow, okay, this is up to, it's such a great experience. And then the flip side of that is you want your employees to be happy and not have to do all this mundane work so you can retain the best people. You don't have to. So you're living that in, in state and, and local. So where did you start your automation journey? What role did EY play? Let's go. Yeah, >>Sure. So I, I, I think the thought for process automation was probably three or four years ago, but then we started the program about 18 months ago and there was a lot of, let's say behind the scenes work before we could bring EY in, you know, like what resources was I gonna have in, in the state that were gonna help me address all of the agency simultaneously, right? Cuz normally you'll see a project that'll do be more siloed across the state and say, we're gonna do this agency, we're gonna do this division. Well, you have 40 other agencies that are, you know, the momentum is it's just gonna fall, it wayside. So how we looked at it was let's blanket it and go across all 23 agencies at the same time, you know, identify common processes that are used across 40 divisions, for example, right? >>So, so what we basically did is we procured the software, you know, did the contracts, and then it was really about, I designed, I'm gonna say a multistream approach where they were, we could run multiple work streams, independent define all the architectures, required dev tests, production, the disaster recovery at the same time in parallel developed the center of excellence, the operation model, the processes, methodologies. And the third one was, let's go out to a few divisions, business administration, health, you know, health, human resources, and be able to do a process inventory to see what was there. And then based on that, there's all this theory of well let's do a proof of concept. Let's do a proof of technology, let's do apply. Well, the bottom line is rpa technology's been around for a long time. It's proven there's nothing to prove. But really what was important to prove before we decided to go, you know, full tilt was, you know, develop a proof of perceived business value. >>Are we gonna bring in the, the business value, the hours and the qu qualitative metrics that is expected by our ex executive team, The leadership, we were able to do that, you know, with the help of help of ey, we built out the prototypes and we got the green light to go forward, got ey to start, and then we just basically went pedal to the metal. We had our foundation already defined. We built up the architecture in less than one to two months. Now, in, in a public sector or private sector, it's just not heard of, right? But we have a tendency with EYs technical team, myself, we look around the, the road around the rock instead, the rock in the road, right? So we ended up coming up with a very unique, very easy to easy to handle architecture that was very scalable. And then were able to hit the ground running and deploy in production by December where head of >>Was EY involved in the whole, you know, dev test production, dr. Center of excellence, the, the process inventory or did you bring them in? Did you kind of do that internally then bring EY in for the proof of >>Value? EY was actually awarded the contract for soup to nuts, basically the first phase, which was those four work streams I told you about. And they worked with myself and the state of Tennessee infrastructure architecture teams. We needed to get these things defined and signed off the architecture so we could expedite getting them built out. And then they, and they basically ran all four work streams, you know, the process, inventory, the prototype, the, the proof of perceived business value, the building out the center of excellence, working with myself. And, and this wasn't just us in a, a vacuum, we ended up having to, I mean, I could do the strategy, I could do the technology and I could said the roadmap and all the good stuff, but we had to actually meet with a lot of the state or tendency organizations on change management. How do we end up putting this process or an automation in the middle of the, the normal traditional process, right? So there was a lot of interaction there and getting their feedback and then tweaking our operational model based on feedback from the state of Tennessee. So it was all very collective collaborative. I think that would be the keyword is collaborative and then building out everything. So then, and then we ended up going to the next way where they knew so much and we were, we had such a tight timeframe that we continued with ey. >>So Christina, Bob mentioned center of excellence a couple of times in the state of Tennessee, but then beyond state of Tennessee, other organizations you've worked with in this space, what's the relationship between center of excellence and this thing we've been hearing about over the last couple of days, the citizen developer has that been, has, has, has that been leveraged in the state of Tennessee? Bob, have you seen that leveraged in other places? Christina? What's that relationship look like? >>Yeah, so we don't leverage that, that model yet we have centralized model and there's reasons for that. So we don't end up having maverick's, runoff runoffs have one off, have, you know, have a a UI path version or down this division or have another RPA tool in another division, right? So then all of a sudden we're, we have a maintenance nightmare. Manageability nightmare. So we basically, you know, I I I negotiate an ELA with UI path, so therefore if anyone wants to go do another automation on another division, or they would basically follow our model, our design, our coe, our quality gates. We we're the gatekeepers to bring into production. >>Got it. Now, yeah. Now Christina, what's your perspective? Because I can imagine Nashville and Memphis might have very different ideas about a lot of things. Yeah. Little Tennessee reference there, but what, what, what about what, what about other places are you, are you seeing the citizen developer leveraged in, in some kinds of places more than others or >>What? Yeah. Yeah. And that's part of, because of the foundation we're building. Yeah. So we laid, you know, when, when Bob talks about the first phase of eight weeks, that was amazingly fast, even in that's ridiculous. Spoke about it to say you're gonna lay these four foundations. I was excited, like, I was like, wow, this, this is a very serious client. They wanna go fast and they wanna get that momentum, but the AUM was laid out so we could propel ourselves. So we are at 40 automations right now. We're in the works of creating 80 more automations in this next year. We'll be at 120 really quickly. The AUM is critical. And I will say at a client, I've, I've worked with over 50 clients on automation programs. The way state of Tennessee treats the aom and they abide by it, it is the living document of how you go and go fast. Got it. And the one thing I would say is it's also allowed us to have such immense quality. So I always talk about you put in forward, you put in another 80, we're at 98% uptime on all our automations, meaning they don't go down. And that's because of the AOM we set up. And the natural progression is going to be how do you take it to citizen developer? How do you take it to, we call, you know, process automation plus, >>But methodically, methodically, not just throwing it out at the beginning and, and hoping the chaos >>Works. Exactly. Exactly. And >>The ratio of of bots to automations, is that one to one or you have automation? Oh no, the single bot is doing multiple. So how many bots are you talking about? >>We're doing, Bob, you're gonna answer this better than I will, but the efficiency is amazing. We've been pushing that. >>So our ratio now, cause we have a high density architecture we put in is four bots, excuse me, four processes. The one bot and four bots, The one virtual machine EC two server. Right? So it's four to one, four to one. Now what we're going to get by next summer, we'll do more analysis. We'll probably get the six to one, six to one that's made serious shrinkage of our footprint from a machine, you know, management perspective from 60 down to seven right now we're gonna add the next chunk. We add another 80 automations in FIS gear 24. We're only gonna add two more bot, two more servers. Right? So that's only 10 running like close to 200 bucks. >>And, and is doing this on prem in the cloud? >>No, our, the architecture's fully >>Oh, cloud based >>Ct. Yeah. So we use UiPath SAS model. Yeah. Right. So that handles the orchestrator, the attended bots, all the other tooling you need automation hub, process minor et etc. Etc. Cetera. And then on the state side in aws we have, we use unattended bots, cert bots that have to go down into the legacy systems, et cetera. And they're sitting on EC two instances. >>Was there, was there a security not hole that you had to get through internally? What was that like? >>No, actually we, we, we were lock and step with the security team on this. I mean, there are some standards and templates and you know, what we had to follow, you know, but they're doing an assessment every single release, they do assessments on little bots, what systems it's activating or are accessing, et cetera. The data, because you have fedra data of FTI data, you know, in the public sector to make sure we're not touching it. >>Do you guys golf? >>I do, yeah. Not Well, yes, >>If you mean I I like golf but not don't golf well, but so you know what, what a mulligan is. If you had a Mulligan right, for the state of Tennessee, what'd you learn? What would you do differently? You know, what are some of the gotchas you see maybe Christina in, in other customers and then maybe specifically state of Tennessee, >>Right? I would say, you know, it is the intangibles. So when we talk about our clients that go fast and go big, like state of Tennessee, it's because that, that we call it phase zero that gets done that Bob did. It's about making sure you've got the sponsorship. So we've got executive sponsorship all the way up. You've got amazing stakeholder engagement. So you're communicating the value of what we're trying to do. And you're, you're showing them the value. We have been really focused on the return on investment and we'll talk a little bit about that, but it's how do you make sure that when you do, you know, states are different with those agencies, you have such an opportunity to maximize return on investment if you do it right, because you're not talking about automation in one agency, you're talking it across multiple agencies. We call that the multiplier effect. And that's huge. And if you understand that and how to actually apply that, the value you get is amazing. So I, I don't, I can't say there's a mulligan here, Bob, you may think of some, I know on other clients, if you don't line up your stakeholders and you don't set the expectations early on, you meander and you may get five, six automations in over the year. You know, when I go to clients and say, we're doing 40, we're doing 80, they're like, >>Wow, that's the, but that's the bottom line. Gotcha. Is if you, if you want to have an operational impact and have multiple zeros, you gotta go through that process that you said up front. >>Exactly. A >>Anything you do differently, Bob? >>Well, I I what I do differently, I mean, I think, I mean we, we did get executive sponsorship, you know, and in one area, but we still have to go out to all the 23 agencies and get, and bring awareness and kind of like set the hook to bring 'em in, right? Bring 'em to the, to the, to the lake. Right. And, and I think if, if it was more of a blanket top down, getting every agency to agree to, you know, in investigate automation, it would've been a lot easier. So we're, we're, we're getting it done. We've gone through 13 agencies already and less than a year, all of our releases are sprinkling across multiple agencies. So it's not like a silo. I'll look at that. Everyone at every agency is being impacted. So I think that's great. But I, I think our, our Mueller now is just trying to make sure we have enough backlog to do the next sprints. >>Is it, you know, the ROI on these initiatives is, is, is so clear and so fast. Is it self-funding? Is there gain sharing or do you just give business, give money back to the state and have to scramble for more? Do you get to, you know, get a lick off that cone? >>Unfortunately we don't, but I, I, I try to see if we could get some property like, nah, we don't do that. It's all cost, cost based. But, but our ROI is very attractive, I think for, for doing a whole state, you know, transformation. I think our ROI is three and a half to four years. Right. And that's pretty mind blowing. Even if you look at private sector or, I, I think some of the, the key things which people are noticing, even though we're in public sector, we're we are very nimble. This project is extremely nimble. We've had people come in, exactly, we need this, so we're gonna get penalized. Okay, knock it out in four hours, four days. Right? So it's that nimbleness that you just don't hear of even in private sector or public sector. And we're just able to do that for all the collaboration we do across ey, across myself and across all the other organizations that I, that I kind of drag along or what have, >>What do you, what do you, do you see any limits to the opportunities here? I mean, is this a decade long opportunity? Is you have that much runway >>Or that's just not my dna, so we're gonna, we're gonna probably do it like in four years, but Well, when >>You say do it, I mean, will you be done at that point? Or do you see the weight, >>Look at, you know, we could boil the ocean and I think this is one of the reasons why we're successful is we could boil the ocean and and be, it will be 10 attended 20 year program. Yeah. Okay. Or we looked at it, we had some of EY guys look at it and say, I said, what's the 25 80 rule? Meaning, you know, give me, So if we had 500 processes, tell me how many processes will gimme 80% of the hours. And it was 125, it was a 25 80 rule. I said, that's what we're doing it, we're doing, we're gonna do the 80% of the hours quantifiably. Now when we're done with that pass, then we'll have those other ones that are bringing 20% of the hours, that's when we might be bringing citizens in. That's what we're bringing state workers in. But at that same time, we will be going back in the wave and doing advanced ai. Right. Or advance ia, in other words. So right now we do rpa, ocr, icr, but you know, there's NL ml nps, there's virtual agents and stuff. So that's like the wave we're gonna do through the ones we've already gone through. Got it. Right. So it'll probably be a two or three wave or iterations. >>Cool. Guys, thanks so much for coming into the cube. Great story. Really appreciate you taking us through it. Thank you so much for having us. You're very welcome. All right, keep it right there. Dave Nicholson. The Dave ante. We back at UI path forward five from the Venetian in Las Vegas. Keep it right there.

(intro upbeat music) >> TheCUBE presents UiPath Forward5, Brought to you by UiPath. >> Welcome to day two of Forward5 UiPath Customer Conference. You're watching theCUBE. My name is Dave Vellante. My co-host is David Nicholson. Yesterday, Dave, we heard about the extension into an enterprise platform. We heard about, from the two CEOs, a new go-to-market strategy. We heard from a lot of customers how they're implementing UiPath generally and automation, specifically, scaling, hyper-automation, and all the buzzwords you hear. Todd Foley is the CDO and CSO of Lydonia Technologies and Devika Saharya is the director of ERP and RPA at MongoDB. Folks, welcome to theCUBE. Thanks for taking time out of your busy day and coming on. >> Thank you Dave. >> Thank you so much. >> So let's start with the roles. So Devika, ERP and RPA. >> Yes. >> It's like peanut butter and jelly, or how do those things relate? What's your, what's your role? >> Absolutely. So I started at Mongo as an ERP manager, and you know, as we were growing, the one thing that came out of, you know, the every year goals for the company, one big goal that came out was how we have to scale. There are so many barriers to scale. How can we become a billion dollar company? What do we need to do? And when we started drilling down into, you know, different areas, we figured it out that people do a lot of stuff manually. It's like comparing sheets, you know, copying data from one place to the other, and so on and so forth. So one thing that we realized was we definitely need some kind of automation. At that time, we didn't know about automation, but we did our own market research and here we are. >> Let's automate. Yeah, right. (Devika laughs) Sounds easy. All right, thank you. Todd, CDO, Chief Data or Chief Dig, and CSO, I'm assuming Chief Data? >> Chief Data. >> And the Chief Information Security Officer. Tell us about Lydonia and also your role. >> Sure, Lydonia, we started just over three years ago. We looked at the RPA market. We saw great opportunity, but we also saw a challenge. We saw that a lot of people had deployed RPA but weren't getting the promised, you know, immediate ROI, rapid deployment that was out there. And when we looked at it, we saw that it really wasn't a technical challenge. Sometimes it was how technology was applied, but there were a lot of things that people were doing in their process and how they were treating RPA, often as if it were traditional technology that slowed them down. So we built our practice, our company, around the idea of being able to help people scale very quickly and drive that faster. And we're finding now with the RPA being pretty ubiquitous, that it's the one thing that's in the greatest demand among our clients. >> Okay, so you're the implementation partner for Mongo, is that right? >> We are. >> Okay, so relatively new. Very new actually, but a specialist. Why'd you choose Lydonia? >> So, that's an interesting question. When we came last year to UiPath Forward, we were looking for, you know, the right kind of people who can, you know, put us on track. We had the technology, we had everything in place, we did the POC, everybody liked it, but we didn't know how to, you know, basically go in that direction. We were missing that direction. And then we, you know, we were doing our homework here, we found, we accidentally stumbled with Lydonia, and I had follow up conversations with Todd, and they were just so tapered. I knew exactly what Todd was explaining me, and we knew we are, we are in safe hands. >> So, where did you start? >> So we, the first thing that we did was a POC for the finance side of business. And right after that POC, we realized that, you know, how much time people were actually investing manually, like things that were done in three to four days was turning into a 30 minute process. And that gave us, you know, the idea that we should start drilling down into different departments and try to find where there are, you know, areas where we can improve. And we did all of that. And then we met with Todd, and Todd explained that how his Reignite process works. So we took Reignite as our first step and, you know, took it from there. We chose one department, we worked with them. We had about 10 processes highlighted, thanks to Todd, he worked with them, and he literally drilled and nailed it down that what we need to do. And as of today, all those 10 are automated. >> Wow. Okay. >> Todd, does this interaction between Lydonia and MongoDB, as a customer, apply equally in the field when you're going out and talking to clients that might be running MongoDB, they might be customers of MongoDB, they may have financial applications that are backended with MongoDB, is there a synergy there that you've been able to gain? >> I think there is. I think there's one thing that's kind of unique about RPA, and that the traditional questions around integration and applicability aren't as important when you have a platform that can work with anything that people can use. I think also, you know, when we look at what we typically do with people, some of the things we see at Mongo are very common use cases you know, across all of our clients. So I, there's definitely the ability for us to take things we've done and have clients get leverage out of them. At the same time, the platform itself is, makes it different than a traditional model where, you know if somebody has worked in a particular area or built an automation for a particular application, there's some kind of utility to do it faster for another client. What we find is that that's not really the case. And that oftentimes we'll compete with people who use different tool sets than UiPath who have that kind of value story around having done it before, we come in and we do it twice as fast as they could. >> So you've, you're a veteran of complex integrations. >> Oh yeah. (Todd laughs) >> I know that from our paths have crossed in the past. So you're saying that in this world of RPA, that this tool set like UiPath as a platform, we've been talking a lot about the difference between being a tool set and being a platform. >> Right. >> That this platform can sort of hover above things without that same layer of complexity, or level of complexity, that you've experienced in the past. Because that speaks to the idea that UiPath, as a platform, is going to work moving forward in a big way. >> Exactly, right. I think we've seen for years and years that regardless of the type of development environment you're using, a developer's value sometimes is based on what reusable libraries they've created, what they have to cut and paste from their old code to be able to do things faster. The challenge with that is it has to be maintained, when things change, they've got to update those libraries. It's a value prop that's very high touch. With UiPath, they've created the ultimate in reusability. The platform, especially since they acquired cloud elements and built all of those API integrations into their platform. The platform maintains the reusability and the libraries in such a way where they're drag and drop from a development standpoint and you don't have to maintain them. It's the ultimate expression of reusability as a platform. >> Yeah, cloud elements, API automation, obviously a key pick by UiPath. Devika, what's the scale of your operation today? Like how many bots and where do you see it going? >> Yes. So we, we started with one bot. Last year we experimented a lot that, you know, we were just trying to make our footprint in the company, trying to understand that, you know, people understand what RPA is, what UiPath is. Initially we got a lot of pushback. We got a pushback from our security team as well, because they could not understand, you know, that what UiPath is and how secure it is. And we had to explain them that how we would host it over AWS, how we will work, how we will not save passwords, et cetera. When we did all of that and they got comfort, we started picking, you know, very small processes around to show, you know, people the capability of RPA and UiPath per se. When we did that, people started just coming with bigger processes, and one specific team that I can think of came that we do, you know, fuzzy logic in Excel, and we do it twice a week, but it takes a lot of time. We automated it, they run it daily, every single day, two times now. And the exponential growth that we saw just with that one automation was mind boggling. I couldn't believe that, you know. We were tracking our insights and we were like, oh my God, what happened? It just blew out of proportion. >> Okay. So then did you need more bots? Are you still running one bot, or? >> Nope. Now at the moment we have nine. >> Okay. >> And we are still looking to grow. >> Okay. So the initial friction, you said there was some, you know, concern, it was primarily security or were there others, people afraid they're going to lose their jobs? Was there any of that? >> There was no risk of losing the job. The major, you know, pushback was, one was from security, the other one was from different system owners because a lot of people were not sure why we want UI access, or why we want API access, and why are we accessing their systems? What type of information we are trying to gather out of their systems. Are we writing into their system? Because a lot of people have issues when we start saying that we will write or override data. So most of the processes that we are working around are either writing, comparing, and reading and comparing, and if it is writing, we take special permission that this is what we are going to do. >> So what did you have to do to get through the security mottle, a AWS SOC 2 report, did you have to show them the UiPath pen test? >> Absolutely. >> Did you have to change any of your processes? What was that sort of punch list like? >> Everything. >> Yeah. >> So we had to start from pen test. We had to start, we had to explain that UiPath is in the process of, you know, acquiring SOC. We also explained that how things are hosted on AWS. We had to, you know, bring our consultants in who explained that how on, on AWS, this will be a very secured way of doing things. And when we did our first process, which was actually for the auditors, which is, you know, interesting. >> Yeah. >> What we did was we did segregation of duties, which I think is very important in every field and every sphere we work in. So for example, the the writeup that we were building for auditors, we made sure that it is approved by a physical or a human, you know, and not everything is done by the bot. The biggest piece of the puzzle was writing, you know, because it was taking a lot of time. People were going into different systems, gathering information, putting it on Excel, and then you know, comparing and submitting it to PWC. >> When you say write, you mean any update to a system of record? >> Correct. >> Required some scrutiny? >> Some scrutiny, yes, yes. >> Okay, initially by a human until there was comfort level and then it's like these bots know what they're doing. >> Correct, correct. >> Okay. And now you're a NetSuite customer, correct? >> Yes. >> That's your ERP? >> That's right. >> Now we were talking about Oracle is going to acquire OCR capabilities. Will that, and we've been talking, Dave and I, a week about, okay well ServiceNow has, you know, RPA, and Salesforce, and SAP, et cetera. How will that affect your thinking about adopting UiPath? >> I don't think it should matter because I think all these systems kind of coexist in a bigger ecosystem, you know, and I also feel that all these systems have their own plus points and minus points. Not one system in, per se, can do everything within a company. So it could be that, for example, NetSuite might be very strong for financials in the space we are in, but not extremely good around sales and marketing. So for that company chose Salesforce. So you know, you have those smaller smaller multiple systems that build into a bigger ecosystem, right. And I think the other piece of the puzzle is that UiPath helps bridge that gap between these systems. You know, it could happen that certain things can get integrated, certain things cannot because of the nature of business, the nature of work that the teams are trying to do. And I think UiPath is leveraging that gap, you know, and putting, you know, those strings together. >> As you scale - >> Mm hmm. >> How will, and Todd I presume you're going to assist in this process, but how will you decide what processes to prioritize, and is that a process driven decision? Is it data led? Both? If so, what kind of data? Can you describe how you guys are going to approach that? >> Yep. Todd, would you like to take that first before I start? >> Sure, yeah. >> Maybe some best practices and then we can maybe get specific to Mongo. >> Absolutely. Our guidance is always that it should be a business decision, right? And it should be data driven, based on a business defined metric around the business case for that particular automation. Our guidance to customers is don't automate it unless you know why you're automating it, and what the value is. We see sometimes there are challenges with people being able to articulate the business case for an automation, and it can almost always be resolved by having that business case be the first step, and qualifying and identifying an automation candidate. >> And how does that apply to Mongo? Do you, where are you thinking about scaling, in your opinion? >> It's interesting because, you know, initially we thought that we will, you know, explore one area in MongoDB. And the other thing that we did was we did road shows. So because we had to create some awareness in the company that we have UiPath there's something called bots. There's something called, you know, automation that we can do, so we created a presentation with small demos inside it and, you know, circulated it within the company. Different departments tried to explain what we can achieve. And based off of that, you know, we came up with a laundry list of all the automations that different departments needed. And out of that, you know, we started doing the business case, the value, you know, trying to come up with complexity, effort. We did a full estimation matrix and based off of that we came, okay, these are the top 20 that we should build first. And as soon as we built those top 20, we saw a skyrocket, you know, growth and - >> And you're looking for hard dollars, right? >> Yes, yes. Absolutely. >> Okay, just to be clear. >> Devika, I think Mongo also is great at taking a data driven approach to looking at their program. Do you want to share how you do that? >> Yes, absolutely. So one thing that we were very sure was we have to talk in terms of numbers because that's the only solid way to see growth. And what we did was, you know, we got insights, we started doing full metrics in terms of dollar saved, hour saved, and we are trying to track how every process is impacting, you know, in the grand scheme of things. Like say for example, for finance, are we shortening the close cycle in any shape or form by doing these two or three automations that we are doing? And I'm happy to report that we have really shortened our close cycle from where we started. >> Your quarter end or month end close. >> Correct, yes. >> Daily? You at the daily close yet, (all laugh) or the "John Chambers"? >> Drive everyone nuts. First I have to say, I could feel the audience sort of smiling as they see, as they hear from MongoDB, disruptor of legacy databases being cautious in their internal approach to change. As everyone else is. >> Exactly, yeah. >> But Todd, just sort of, double clicking on this idea of kind of stove pipes of capabilities in the RPA space. I mean OCR, being added to NetSuite, I'm not sure if that's the greatest example, but the point is Lydonia will work with all of those technologies to synthesize something. Is that correct? Or are you a UiPath only? >> Both. So we exclusively use UiPath with our customers. We don't use other RPA platforms. >> Okay. >> And we don't because, not because we can't, but because we don't believe that anything else is going to be as quick or as effective. Also, it's the only platform that is as broad and comprehensive as it needs to be to deliver outcomes to our customers. We have partnerships with other companies that have gaps where UiPath isn't currently playing, but the number of companies and the number of gaps has shrunk down to almost nothing these days. And we're well placed as UiPath continues to grow their platform to take advantage of that and leverage that to deliver outcomes to customers. >> It was a great story of starting small, being careful. >> Yes. >> And prudent, from a security standpoint, especially as a public company. And then it sounds like there's virtually unlimited opportunity. >> Yes, absolutely, absolutely. >> For you guys. Great story, thank you very much for sharing it. Appreciate it. >> Thank you. >> All right, good luck. All right, thank you for watching. Keep it right there. Dave Nicholson and Dave Vellante will be back from UiPath Forward5 from the Venetian in Las Vegas. Be right back. (upbeat music playing)

>> Male: TheCUBE presents, UIPATH, Forward 5 brought to you by, UIPATH. >> Okay the party has started here at forward 5 UIPATH big customer event if you're watching the cube. We're wrapping up day one with the co-CE0 segment. Daniel Dines is here. He's the founder and Co-CEO of UIPATH and Rob Enslin, is co-CEO. Gents, great to see you. Thanks for spending some time with us. I know you're super busy. >> Thanks Dave. >> So I've been looking forward to this. Daniel you know I've followed the company for a long time. The really interesting path you took, to get to where you are today. How did you guys meet? And why did you decide to hire Rob? >> Male: (laughs) >> Rob: Well let me start. I uh, I was looking for a partner. Actually, in our work to your stand here, we are talking about how, how you feel in this job. You feel so alone. Because you are the center of all pressure points. And having a partner, having someone that has your back, it's kind of awesome. So I was looking for a partner. And our current friend, Carl Escenbach, he introduced us to each other, and we instantly clicked. And this is the type of job where it's uh either work well or it doesn't. It cannot be anything in the middle. >> Right, okay with Carl, we know Carl well. Awesome operator. Knows the business super well. So Rob, what attracted you to UIPATH? You had a great situation at google. You guys were growing like crazy. Why did you decide to come here? What did you see that attracted you? >> Yeah you know when I, when I went to google, I went to google because I really believed that data and AI was necessary for companies. And business is to be competitive in the future. And we did some great stuff at google cloud in the 3 years. But I knew UIPATH from a couple of years ago when they were mainly a RPA space. And I just felt that there was a place in time when automation was going expand. And as I sat down with Carl a couple of times, spoke to carl. And then I sat down with Daniel, I knew that there was something special with UIPATH, that could be a generational opportunity. Not any for myself but for the company in the future. And then I, you know I got to know Daniel. And at this stage of my career I was like, I'm pretty fussy about what I want to do and what I want and where I want to go. First of all, I want to go to a company that had great product, had a great culture, and I wanted to work with somebody that we could shake the future together and you know, Daniel and I just hit it off from the very first time we met. He got to meet my family, my dogs and we did the whole, we did the whole courting thing before we actually decided this was going to be a good thing for both of us. >> Dave: That's good. >> Rob: Yeah. >> Dave: You got to meet the family. That's very good. >> We just had, John Furrier and I just had, Mohit Aron and Sanjay Poonen into out studio. Cause Mohit, you know, formal google. Long time. And they decided to kind of split duties. Mohit's going into product, he didn't keep his CEO title. He walked. How are you guys splitting you time? What are each of you going to, responsible for? >> Daniel: Well its, its kind of similar. On a day by day operation I, I rely heavily on Rob. We do it together. Strategic decisions about the company's destiny. I'm doing mostly the product these days. Which is a big relief for me. And I think we also split a bit of customers visit. Which is great. I still enjoy meeting customers. I need, customers are food for my cause. >> Dave: (laughs) yeah and your awesome product visionary. You've been there since day one. Now Rob, you said in the key note today that you've seen around about a hundred customers. You've transverse the world. What did you learn from them that informed you? That gave you confidence that the the move to the internet platform, even though you had already started that. >> Male: Yeah. >> But you're really doubling down on that >> Rob: You know when I... >> from a stand point. >> Rob: You know Dave, when you think about it, like I was, I was so impressed that Daniel had the vision to create a platform 3 years ago. >> Dave: Yeah. >> All right. And as we went around the world. As I went around the world, and it was one of the very first things I've seen. I've got to understand how customers see UIPATH, from their advantage point. What are they looking for from us? Why is this company, why doe customers like this company so much? And as I went around the world. I went to Asia a couple, I went to Asia, Australia, Singapore, Japan. I was in Europe twice. We did the trip together. We went to visit customers. And it was very much the same thing. Helps us expand automation faster. And we are so surprise, at the break of your platform. We never knew that. And so it kind of just had, for me, it was conviction. It's like, this walls is the right decision you've made. There's so much opportunity there. And that's, you know that's kind of what I've learned through the last four five months. >> Dave: Now as you know Daniel, I've written a lot about your company. One of the things I've said is that, that start ups, if I can call you that back pre-IPO, typically don't have as much international exposure as UIPATH had. I mean you sort of, you sort of started as an international company and became more US centric. You said, in the, in the key note today, you're talking to Ray Wong about people may don't understand that challenges of FX. Point being, when you convert international dollars into US dollars there are less of them cause the dollars stronger. But still, I've always felt like that international footprint is an advantage. Rob you came from SAP, you know, again European based company. I don't, (stutters), do you regret that? Now? I mean I know it's technical, I'm sure you don't, but talk about that sort of international exposure? Why that's a long term benefit. >> Well, you, first of all, you expand faster. I think we expanded faster than our competition because our global footprint was larger. And we had the courage. Go in Japan, for instance. Everybody told me, it's impossible to make for such a small starter. It's impossible to make a business in Japan. But we didn't believe it. We're just crazy and we went there, and be built a very sizable business in Japan. Fifty-five percent of our revenue, even today, it's outside U.S. Now of course that has a down side. When uh, When the local currencies, you know, are losing the value compared to the dollars, we're impacted. As we go to... to investors, until now, so we are seeing like a (indistinct) in terms of ARI. It's huge. Only because (indistinct) and losing the business in Russia. But it still, it's the strength of our company. Things will come back. And then, you know, the growth engine will re-accelerate again. >> Dave: Yeah but when the dollars weakens that'll be in your favor. Rob I want to pick up on something you said today in your keynote. You went back and started, you know the cycles of ERP and you know, internet, et cetera. I kind of have a love hate with ERP. I have to be honest. >> Male: (laughing) >> But it, but but (chuckles) but if I go back to that. Late eighties nineties, you wouldn't have be able to pick SAP as the winner. And then SAP emerged. You know, very clearly. But the more interesting thing, is that the customers who are implementing ERP well. The practitioners did better than their peers, and dominated their industries. And their stocks went up. Their evaluations went up. Different worlds obviously but, do you see the same thing happening with RPA and automation? What gives you confidence that that's the case? >> I absolutely do see the same thing happening with automation and RPA being a part of, in being a part of that. The reason, the reason I believe that is speed is so critical. (stutters) And if you think about how hard it is for a CIO or a c level executive to consume the technology coming at them, plus all the changes in the world being thrown at them. It's compiling and compiling and compiling. We have an incredible solution, that can help companies. And there comes certain times, the love outcomes to the business. Like no one else gets. And when I see that, I view that as just like the beginning of what's going to happen in the future so, in many ways, and I've said this to many of my friends, it feels like 1992, 1993 to me. And it's interesting because no one really understood then why SAP would be great in 1992 and 93. And they got a couple of things right. They got the eco system right. Their new partners were important. And the knew they needed to drive business outcome for companies, in which they did. And so I feel like we are in a very similar place. Very different technology obviously. And the speed of change now is so dramatic, compared to what it was. And there's very few technology that can provide that level of speed and accomodation to their customers. >> All right, let's talk about priorities. You guys got a lot of work to do and you've, you've laid it out to the financial community. You've got to have profitable growth, because of FX, it part, you've lowered your forecast. But I think there's some conservative in their as well. Um, but you got to do that balance. You've given some guidance on gross margins. Cloud maybe brings that down a little bit. RnD I saw wide range. Thirteen to seventeen percent. I hope you keep spending on RnD. Big fan of that. You know stock buybacks and, RnD if in your position are going to be better. And the product priorities, continue to build that out. But question, let's start with the product. So you've got an on-prem stack and you've got a cloud stack that's emerging, how do you balance those out? How do you do the integration? You've done a great job with the integration. Does it, are you concerned about your ability to continue to work at that speed with two code bases? I wonder if you could address that? >> Daniel: We've become a cloud first company. We deliver all of our products first in the cloud. We've deliver on the two week (indistinct) in the cloud. So that helps us integrate quite fast. I think we made a very good business decision to build our cloud team in Seattle. In Bellevue to be specific. And we have access to great talent that knows how to build serious cloud service. Which is hard to find dollar. And uh, so, and also we, we have, we benef- one of our only benefits was, we have the really good architecture. We have an architecture that work easily on-prem and on the cloud. And even today, our work flow foundation, our local designers, were easy to modernize. So right now we are launching studio weapon. But behind the scene, it's the same workflow engine. Our customers don't have to rewrite anything. It just works. And it does the same to take our own brand product and brand it in the multicloud. So, it's, there is no friction at all. Actually cloud is just helping us accelerate. But we benefit then again of a really solid architectural foundation. >> Daniel: Architecture matters. We've seen that in this industry. We got the B52s rocking out in the background, I love it, but I've got so many questions for you guys. I want to talk about the go to market. Because Rob, it's obviously a strength of yours. You've come in. You've communicated to the street, that you're reshaping the sales floors. Are they lowering the ratios of sales? People, the customers at the high end, mid range as well, using digital. I mean the numbers are one to ten now. At the top. One to maybe fifty at the mid range. Where are you in terms of that journey? You've got to find people, you got to train them, how do you get the productivity out of those guys? Take us through your thinking there? >> Rob: Yeah firstly, I think we have enough resources. Having resources is not an issue. Um, we have an incredible vehicle to acquire customers inside the company. Our digital sales motion, it's probably the best I've seen. And so we have the ability to acquire customers really fast. And we get the first workload in really fast. The challenge is we need to, we need to be able to drive a (indistinct) model and we graduate customs when we acquire them into the direct sales floors. And then direct sales floors, we're not going to go one to thirty, we're talking one to ten for the direct sales floor. And even the high up in the pyramid, we want to have an even denser model than that. And the whole purpose is to drive the time to consumption much quicker, much faster. So we know exactly if we acquire a customer, will they spend? Do they have a (indistinct) spend? On what level do they have a (indistinct) spend? And therefore when we capture them, we can immediately surround them, and put the right resources so we can grow faster. We think this will have a significant impact on the organization. We'll start to implement certain pieces in the next quarter. Um, things like packaging solutions. Putting them in, enabling the sales organization. And buy the beginning of next year, we'll be ready to actually go full board, globally. We already put some pieces in place when I joined. Chris Weber, my chief business officer, did a great job doing some of those pieces. So we're on the journey already. >> Dave: Yeah and even before you guys were public and you weren't publishing your NRR numbers. Our ETR survey partner, we, we always thought you had very low churn. And I think you broke out just yesterday. The, the NRR for overseas vs U.S, U.S I think was 140 plus percent. >> Male: Yeah >> Very very strong. A little, a little less overseas but the churn is still very low. >> Male: Yep. >> Okay so that's super positive. Customer affinity, I was wanted to code these events. I listen to the key notes very carefully, and then interview customers on the cube, and I try to identify, is there alignment there? And I see very strong alignment, I have to say, and strong customer affinity. So that's in your favor. I have, Daniel, I got another question for you on product. What is Symantec automation? What the heck is that? Can you explain that? I don't understand >> Dave, have you seen the demo in my (indistinct)? >> Dave: You know, I had to leave and do interviews, so I, uh, I missed it. >> I think, I think that demo answer complete your question. So in the s-, you know there saying that great, you can not distinguish great technology by magic. I think technology should be simple. And we, we show today, one of the simplest demo that you can imagine. But it's so, such a complex technology behind the scene, that you also can not imagine. So what was demo? We show how one business user, without any technical skills, can build any type of document. Can be a passport, can be an invoice, can be a legal (indistinct), and just go, "I want to copy data from here, and I want to paste data there". Can be a spreadsheet, can be another obligation, and like a human user, without understanding, without having prior knowledge about data, document layout, about screens, screens layouts, nothing, we analyze real time. Document. We discover, we discover the meaning of the information. We analyze the screen. We understand the screen but we understand the meaning of the screen. And we understand how the information in one side relate to the other side. And we just connects the dots and we copy the information and we paste it. A job that you'll do as a human user, maybe three minutes, is done in ten seconds. This is powerful. >> Yeah that is powerful. Thank you for that. I mean, and you take the date, whether it's transaction data or unstructured data and and and bring meaning out of it. That's powerful. Last question and I'll let you guys go. Rob, you got traders, and you've got long term investors. All right traders going to be defensive, today. I get that. Make the case for UIPATH, for long term investors. >> Rob: I think we're going to be a multi-gern- multi-billion company and we're going to be a generational company of our time. And we will define enterprise automation. And it's going to be a long term game and we feel like really strong that we'll be the lead in that game. >> Dave: Guys, thanks so much for coming to the cube. Great show. Always fun at UiPath Forward. Really appreciate your time. Thank you. >> Thanks dave. >> Appreciate it as well. >> Okay wrap it up, day one, we're here tomorrow, first thing, Dave Vellante and Dave Nicholson. Thanks for watching, forward 5, Uipath big customer event, we'll see you tomorrow. (music)

(upbeat music) >> theCUBE presents UiPath FORWARD5 brought to you by UiPath. >> Welcome back to Las Vegas, everybody you're watching theCUBE's coverage of UiPath FORWARD5. We're here at the Venetian Convention Center Dave Vellante with Dave Nicholson this morning. Dave, we heard these boomers, these thunder boomers. We thought it was the sound system. (Dave laughing) >> Thought it was something fake. >> But it was actually some crazy weather out here in Vegas. It's rare to see that kind of nuttiness out here. John Morrison is the director of Product and Technology at T-Mobile and Naga Chakravarthy is the Chief Digital Officer at iOpex. Guys, welcome. >> Thanks for having us. >> Next, so John, (commentator booming) so okay, we're serving automation. I don't know if you guys can hear that S0 let's just give him a second here. >> (Commentator) Three different tracks >> I think it's pretty loud. Probably coming through. Usually we don't get that. >> It's live. >> But, it is live. So John, we, we've interviewed a lot of customers that have automation in their title. Your title's, Director of product and technology. Obviously you're here 'cause you have an affinity to automation. But talk about your role and how automation fits into it. >> Sure. Well, I'm the director of product and technology and I oversee what we call the communication, collaboration and productivity applications and services for T-Mobile. Reason I'm here is we took over the automation program and automation is falling within to our productivity portfolio. So I'm here to learn about, from these experts and all these leaders within the UiPath and from our vendors as well. >> Okay. Now tell us about iOpex. So kind of an interesting name. Where'd that come from? I think cloud. When I think opex, but, get rid of my cap. Where's the name come from and what do you guys do? >> Actually we thought hard about what to name about 13 years back. You know, I think all of us, the whole team comes from a service background and then I think we believe that you need to have people and as a lot of operational activities were increasing, you know the dependency on people was also increasing. And we thought that there has to be an angle for us to be very unique in the market. So we thought, you know, I would say iOpex is currently at 3.0 and if you look at what 1.0 was, it's all about driving innovation in operation excellence, right? And the medium was technology. And today, if you ask me from operation excellence that is the base, we are actually looking at how do you drive innovation in operating experiences. That's where automation and all these things becomes very native to us. >> So the market just went right, right to you guys you were ahead of the game. And then, wow, now, >> I have to brag that we fortunately named it Opex, which can be interchangeably used for operation excellence or operating experience. >> Got it. >> So, so John, where did, where did it start? What was the catalyst for your automation journey? How did, was it the, was it the, the merger? Take us through that. >> Sure. So I look at our automation journey, like a crawl, walk, run journey for sure. It started with the partnership of UiPath and iOpex. We had an innovation lab. They came, they set up a proof of concept. Proof of concept was successful. I was then asked to build out an automation program for the T-mobile enterprise. Not having any experience within automation as we had discussed before usually you have automation within the title. We leaned heavily on our partners iOpex being main critical partner in that evolution. And so iOpex came in and helped us build that center of excellence and really helped us put that support team together so that we could be successful as we moved forward. Now, when we had both of those in place, we were able to go to the businesses and find opportunities and showcase what automation was all about. The problem is we were so green is that, you know, we'd go and we'd look at an opportunity, but that opportunity we'd deliver and then our pipeline would be empty and we'd have to go look for other opportunities. So we really had to present and get that executive sponsorship of automation for the enterprise. And I'm going to do a few shoutouts here. Giao Duong, John Lowe and our CIO Brian King, were critical in giving us what we needed to be successful. They gave us the expertise, the funds to do what we needed to, to build out this program. We utilized iOpex, UiPath to really get that expertise in place. And today, our pipeline, we have about 300,000 manual hours of labor savings that we'll deploy by the end of the year. That's a huge success. And that's where we're at right now. The run part of it is going to be, I'll wait. >> Wait. No, it's okay. So you went, you went from hunting to fishing in a barrel? >> Absolutely. Absolutely. So the, our next is focused on citizen development, building out that citizen development program, where we will be partnering with UiPath and iOpex to get that in place. And once we have that in place I feel like we're going to be ready to run and we'll see that program just kick off. But like I said before, 300,000 hours of savings in the first year of that program. That's incredible. And we're a large company and we'll, I mean we're just starting so it's going to be fun. >> So many questions. So Naga, is the COE where people typically start or is it sometimes a grassroot effort and then the COE comes later? How do you typically recommend approaching it? >> I think the fact that we started very small there was a clear mandate that we have to take a very strategic approach while we are solving a tactical problem to show that automation is the future and you need to solve using automation, right? And we not only looked at it just from a task automation standpoint, we were starting to look at it from a process, entire end to end process automation. And when we started looking at it, though we were tactically automating it, COE naturally fell in place. So, which means you need to evangelize this across multiple departments. So when you have to have, when you have to have evangelize across multiple departments, what is very important is you need to have the pod leaders identified let's say if you have to go to different departments it is somebody from John's team who's very capable of navigating through different departments' problem statements and how when you, when you navigate it you can rightly evangelize what is the benefit. And when it comes to benefit, right? You need to look at it from both the angles of operation excellence and what is it going to do from a growth standpoint of solving a future problem. So somebody internally within T-Mobile we were able to use very nice, you know John's team, you know, the COE naturally fell in place. All of them were at some point in time doing automation. And slowly it was a path that they took to evangelize and we were able to piggyback and scale it bigger. >> So in the world we're in, whether you're talking about cloud services that are created by hyper scale cloud providers or automation platforms from UiPath, between those shiny toys and what we want to accomplish with them in the world of business and everything else there are organizations like iOpex and you and John are working together to figure out which projects need to be done in a strategic, from a strategic viewpoint but you're also addressing them tactically. I'm curious, >> Yeah. >> How does that business model from an iOpex perspective work do you have people embedded at T-Mobile that are working with John and his folks to identify the next things to automate? Is it a, is it, where is the push and where is the pull coming from in terms of, okay now what do we do next? Because look, let's be frank, in the, from a business perspective, iOpex wants to do as much as it can a value for T-mobile because that's what, that's the business they're in. But, so tell me about that push pull between the two of you. Does that make sense? Yeah, So I'll say real fast that, yeah iOpex is actually part of the T-mobile team. They are embedded. >> Nicholson: Okay. >> We work with them daily. >> Nicholson: Okay. >> Right. They had the expertise they're passing along the expertise to our full-time employees. And so it's like we're all one team. So that should answer that one for sure there. >> Absolutely. Let me add one more point to it. See if, you know, I think with respect to T-Mobile I would say it's a little bit of a special case for us. Why I say that is, when we started the whole conversation of we need to drive automation with you there was a natural way to get embedded, you know as part of their team. Normally what happens is a team, a COE team works and say I will do the discovery and you guys can come and do the solution design. That was not the case, right? I think it was such a strategic investment that T-Mobile made on us, right? We were part of the discovery team. So, which means that we were able to take all the best practices that we learned from outside and openness to accept and start looking at it what's in it for us for the larger good that made us to get to what we call it as building a solution factory for T-Mobile. >> Vellante: I got a lot of questions. >> John: Yeah. >> John, you mentioned your CIO and a couple of other constituents. >> Yes. >> What part of the organization were they from? They helped you with funding, >> Yep. >> And maybe sort of gave you a catalyst. How did this all get funded? If I, if you could, Cause a lot of people ask me well how do I fund this thing? Does it fund itself? Do I do, is it an IT driven initiative line of business? >> So those executives were from the IT team. >> Vellante: Okay. For sure. But a lot of our programs start from grassroots ground up and you know a lot of vendors say, hey, you need it from the top down. This was a perfect example of getting it from the top down. We were working it, it was fine, but it wouldn't have taken off if we didn't have, you know, Brian King and John Lowe providing us that executive sponsorship, going to their peers and telling them about the program and giving us the opportunity to showcase what automation can do. >> How do you choose, I got so many questions I'm going to go rapid fire. How do you choose your automation priorities? Is it process driven? Is it data led? What's the right approach? >> I think it's a combination, right? One fundamentally guiding principle that we always look at is let it not be a task automation, right? Task automation solves a particular problem, but maybe you know, if you start looking at it from a bigger, you need to start looking at it from process angle. And when it comes to process, right? There are a lot of things that gets executed in the systems of record, in the form of workflow. And there's a lot of things that gets executed outside the systems of record, which is in people's mind. That's when data comes in, right? So let's say you use process mining tool of UiPath, you will get to know that there is a bottleneck in a particular process because it's cluttered somewhere. But you also have to look at why is this clutter happening, and you need to start collecting data. So a combination of a data science as well as a process science blends together. And that's when you'll start deciding, hey this is repetitive in nature, this is going to scale, this is an optimization problem. And then you build a scorecard and that scorecard naturally drives the, you know decision making process. Hey, it's going to drive operation excellence problem for me or is it going to be a true business benefit of driving growth? >> So I was going to ask you how you visualize it. You visualize it through, I guess, understanding of the organization, anecdotal comments, research digging, peeling the onion, and then you do some kind of scorecard like approach and say, okay these are the high, high opportunity areas. Okay. So combination. Got it. How about change management? Because Dave, you and I were talking about this before, big organizations that I know they have IT, they got an application portfolio. That application portfolio the applications have dependencies on each other. And then they have a process portfolio that is also related. So any change in process ripples through the applications. Any change in application affects other applications and affects processes. So how do you handle change management? >> So we actually have a change management team and we make sure that before we go forward with anything it's communicated what changes would be in place. And this change management team also does communications broadly for any of our applications, not just automation. So they partner close with iOpex, with our development teams on opportunities that are going out. You want to add anything? >> Yeah. So when it comes to change management, right? Well, John is front-ending all the changes relating to apps and stuff like that by having a steering committee, what really is the proactive thing that we end up doing is right when a bot goes live, there is a life support that we provide for the entire bot that's gone live. And the fundamentally core principle for that entire support to work good is you start looking at what's the benefit that the bot is giving more than that when a bot fails. Right? Why is the bot failing? Is it because the systems of records on which the bot is running? Is it that is failing? Or the inputs that is coming to the systems of record the data format, is it changing or the bot logic is failed? And once we set up a constant monitoring about that we were able to throw insights into the change management team saying that the bot failed because of various reasons. And that kind of compliments the whole change management process. And we get earlier notifications saying, hey there's going to be changes. So which means we go proactively look at, hey, okay fair enough, this systems of records, this data is going to change. Can we test this out in staging before you hit the production? So that way the change becomes a smoother process. >> And how quickly can you diagnose that? Is it hours, minutes, days, weeks, months? >> So, >> Vellante: Depends. >> It's a very subjective question. Right. If we know the pattern early then the SWAT team quickly gets into it and figure out how we could stop something, you know, stop the bot from failing. The moment the bot fails, you know, you need to basically look at how the business is going to going to get affected. But we try to do as much as we could. >> So Naga, I'm going to put you on the spot here. >> Please. >> As a partner of UiPath, this question of platform versus product. In order to scale and survive and thrive into the future UiPath needs to be able to demonstrate that it's more than a tool set, but instead a platform. What's your view on that in general? What differentiates a platform from a product? Does it matter to your organization whether UiPath moves in the direction of platform or not? >> I think, it is, it's undoubtedly platform, right? And a platform in my mind will constantly evolve. And once you think about it as a platform you will end up having a lot of plug and place. If you look at the way UiPath is evolving it is evolving as a platform. It used to be attended bot and unattended bot and plugged with Orchestrator. And if you look at it, the problem of solving the up chain and the down chain naturally came in process mining, task capture, made it up chain, a platform that solves the up chain. And then it slowly evolved into, hey I'm actually doing business process automation. Why could I not do test automation with the same skillset? So a platform will try to look at what is that, you know I've got in myself and how can I reuse across the enterprise? I think that is deeply embedded in the UiPath culture. And that's the kind of platform that, you know anybody like a system integrator like us, we do not have to multi-skill people. You just have to skill in one and you can interchange. That I would say is a good approach. >> So John, what's the future look like? What's the organization's appetite for automation? You know, is there an all you could eat kind of enterprise license approach? >> John: Yeah, so we are enterprise license. >> You are? Okay. >> So, and iOpex helped us move to the cloud so we can move quickly. That was definitely a benefit. The future of it, I would say citizen development is going to be key. Like I want citizen development within every business organization. I want them to be able to discover, deploy, you know, and and just use us, the center of excellence as support as needed. The appetite's there. Every group has automation within their goals or KPIs right? So it's there. We just need to be able to get in front of 'em. It's a large company. So I'm, '23 is going to be huge for us. >> Another fantastic story. I love that UiPath brings the customers to theCUBE. So thank you guys for telling your story. Congratulations on all your success. Good luck in the future. >> Yeah. Thank you. >> All right. Okay. Thank you for watching. This is Dave Vellante for Dave Nicholson UiPath FORWARD5. The bots are running around Dave. We're going to have to get one of the bots to come up here and show people a lot of fun at FORWARD. We're here in Vegas, right back, right after this short break.

>>The Cube Presents UI Path Forward five. Brought to you by UI Path, >>Everybody. We're back in Las Vegas. The cube's coverage we're day one at UI Path forward. Five. Pascal Borne is here. He's an expert and bestselling author in the topic of AI and automation and the book Intelligent Automation. Welcome to the world of Hyper Automation, the first book on the topic. And of course, Ray Wong is back on the cube. He's the founder, chairman and principal analyst, Constellation Reese, also bestselling author of Everybody Wants To Rule the World. Guys, thanks so much for coming on The Cubes. Always a pleasure. Ray Pascal, First time on the Cube, I believe. >>Yes, thank you. Thanks for the invitation. Thank you. >>So what is artificial about artificial intelligence, >>For sure, not people. >>So, okay, so you guys are both speaking at the conference, Ray today. I think you're interviewing the co CEOs. What do you make of that? What's, what are you gonna, what are you gonna probe with these guys? Like, how they're gonna divide their divide and conquer, and why do you think the, the company Danielle in particular, decided to bring in Rob Sland? >>Well, you know what I mean, Like, you know, these companies are now at a different stage of growth, right? There's that early battle between RPA vendors. Now we're actually talking something different, right? We're talking about where does automation go? How do we get the decisioning? What's the next best action? That's gonna be the next step. And to take where UI path is today to somewhere else, You really want someone with that enterprise cred and experience the sales motions, the packages, the partnership capabilities, and who else better than Roblin? He, that's, he's done, he can do that in his sleep, but now he's gotta do that in a new space, taking whole category to another level. Now, Daniel on the other hand, right, I mean, he's the visionary founder. He put this thing from nothing to where he is today, right? I mean, at that point you want your founder thinking about the next set of ideas, right? So you get this interesting dynamic that we've seen for a while with co CEOs, those that are doing the operations, getting the stuff out the door, and then letting the founders get a chance to go back and rethink, take a look at the perspective, and hopefully get a chance to build the next idea or take the next idea back into the organization. >>Right? Very well said. Pascal, why did you write your book on intelligent automation and, and hyper automation, and what's changed since you've written that book? >>So, I, I wrote this book, An Intelligent Automation, two years ago. At that time, it was really a new topic. It was really about the key, the, the key, the key content of the, of the book is really about combining different technologies to automate the most complex end to end business processes in companies. And when I say capabilities, it's, we, we hear a lot about up here, especially here, robotic process automation. But up here alone, if you just trying to transform a company with only up here, you just fall short. Okay? A lot of those processes need more than execution. They need language, they need the capacity to view, to see, they need the capacity to understand and to, and to create insights. So by combining process automation with ai, natural language processing, computer vision, you give this capability to create impact by automating end to end processes in companies. >>I, I like the test, what I hear in the keynote with independent experts like yourself. So we're hearing that that intelligent automation or automation is a fundamental component of digital transformation. Is it? Or is it more sort of a back office sort of hidden in inside plumbing Ray? What do you think? >>Well, you start by understanding what's going on in the process phase. And that's where you see discover become very important in that keynote, right? And that's where process mining's playing a role. Then you gotta automate stuff. But when you get to operations, that's really where the change is going to happen, right? We actually think that, you know, when you're doing the digital transformation pieces, right? Analytics, automation and AI are coming together to create a concept we call decision velocity. You and I make a quick decision, boom, how long does it take to get out? Management committee could free forever, right? A week, two months, never. But if you're thinking about competing with the automation, right? These decisions are actually being done a hundred times per second by machine, even a thousand times per second. That asymmetry is really what people are facing at the moment. >>And the companies that are gonna be able to do that and start automating decisions are gonna be operating at another level. Back to what Pascal's book talking about, right? And there are four questions everyone has to ask you, like, when do you fully intelligently automate? And that happens right in the background when you augment the machine with a human. So we can find why did you make an exception? Why did you break a roll? Why didn't you follow this protocol so we can get it down to a higher level confidence? When do you augment the human with the machine so we can give you the information so you can act quickly. And the last one is, when do you wanna insert a human in the process? That's gonna be the biggest question. Order to cash, incident or resolution, Hire to retire, procure to pay. It doesn't matter. When do you want to put a human in the process? When do you want a man in the middle, person in the middle? And more importantly, when do you want insert friction? >>So Pascal, you wrote your book in the middle of the, the pandemic. Yes. And, and so, you know, pre pandemic digital transformation was kind of a buzzword. A lot of people gave it lip service, eh, not on my watch, I don't have to worry about that. But then it became sort of, you're not a digital business, you're out of business. So, so what have you seen as the catalyst for adoption of automation? Was it the, the pandemic? Was it sort of good runway before that? What's changed? You know, pre isolation, post isolation economy. >>You, you make me think about a joke. Who, who did your best digital transformation over the last years? The ceo, C H R O, the Covid. >>It's a big record ball, right? Yeah. >>Right. And that's exactly true. You know, before pandemic digital transformation was a competitive advantage. >>Companies that went into it had an opportunity to get a bit better than their, their competitors during the pandemic. Things have changed completely. Companies that were not digitalized and automated could not survive. And we've seen so many companies just burning out and, and, and those companies that have been able to capitalize on intelligent automation, digital transformations during the pandemic have been able not only to survive, but to, to thrive, to really create their place on the market. So that's, that has been a catalyst, definitely a catalyst for that. That explains the success of the book, basically. Yeah. >>Okay. Okay. >>So you're familiar with the concept of Stew the food, right? So Stew by definition is something that's delicious to eat. Stew isn't simply taking one of every ingredient from the pantry and throwing it in the pot and stirring it around. When we start talking about intelligent automation, artificial intelligence, augmented intelligence, it starts getting a bit overwhelming. My spy sense goes off and I start thinking, this sounds like mush. It doesn't sound like Stew. So I wanna hear from each of you, what is the methodical process that, that people need to go through when they're going through digital trans transmission, digital transformation, so that you get delicious stew instead of a mush that's just confused everything in your business. So you, Ray, you want, you want to, you wanna answer that first? >>Yeah. You know, I mean, we've been talking about digital transformation since 2010, right? And part of it was really getting the business model, right? What are you trying to achieve? Is that a new type of offering? Are you changing the way you monetize something? Are you taking existing process and applying it to a new set of technologies? And what do you wanna accomplish, right? Once you start there, then it becomes a whole lot of operational stuff. And it's more than st right? I mean, it, it could be like, well, I can't use those words there. But the point being is it could be a complete like, operational exercise. It could be a complete revenue exercise, it could be a regulatory exercise, it could be something about where you want to take growth into the next level. And each one of those processes, some of it is automation, right? There's a big component of it today. But most of it is really rethinking about what you want things to do, right? How do you actually make things to be successful, right? Do I reorganize a process? Do I insert a place to do monetization? Where do I put engagement in place? How do I collect data along the way so I can build better feedback loop? What can I do to build the business graph so that I have that knowledge for the future so I can go forward doing that so I can be successful. >>The Pascal should, should, should the directive be first ia, then ai? Or are these, are these things going to happen in parallel naturally? What's your position on that? Is it first, >>So it, so, >>So AI is part of IA because that's, it's, it's part of the big umbrella. And very often I got the question. So how do you differentiate AI in, I a, I like to say that AI is only the brain. So think of ai cuz I'm consider, I consider AI as machine learning, Okay? Think of AI in a, like a brain near jar that only can think, create, insight, learn, but doesn't do anything, doesn't have any arms, doesn't have any eyes, doesn't not have any mouth and ears can't talk, can't understand with ia, you, you give those capabilities to ai. You, you basically, you create a cap, the capability, technological capability that is able to do more than just thinking, learning and, and create insight, but also acting, speaking, understanding the environment, viewing it, interacting with it. So basically performing these, those end to end processes that are performed currently by people in companies. >>Yeah, we're gonna get to a point where we get to what we call a dynamic scenario generation. You're talking to me, you get excited, well, I changed the story because something else shows up, or you're talking to me and you're really upset. We're gonna have to actually ch, you know, address that issue right away. Well, we want the ability to have that sense and respond capability so that the next best action is served. So your data, your process, the journey, all the analytics on the top end, that's all gonna be served up and changed along the way. As we go from 2D journeys to 3D scenarios in the metaverse, if we think about what happens from a decentralized world to decentralized, and we think about what's happening from web two to web three, we're gonna make those types of shifts so that things are moving along. Everything's a choose your end venture journey. >>So I hope I remember this correctly from your book. You talked about disruption scenarios within industries and within companies. And I go back to the early days of, of our industry and East coast Prime, Wang, dg, they're all gone. And then, but, but you look at companies like Microsoft, you know, they were, they were able to, you know, get through that novel. Yeah. Ibm, you know, I call it survived. Intel is now going through their, you know, their challenge. So, so maybe it's inevitable, but how do you see the future in terms of disruption with an industry, Forget our industry for a second, all industry across, whether it's healthcare, financial services, manufacturing, automobiles, et cetera. How do you see the disruption scenario? I'm pretty sure you talked about this in your book, it's been a while since I read it, but I wonder if you could talk about that disruption scenario and, and the role that automation is going to play, either as the disruptor or as the protector of the incumbents. >>Let's take healthcare and auto as an example. Healthcare is a great example. If we think about what's going on, not enough nurses, massive shortage, right? What are we doing at the moment? We're setting five foot nine robots to do non-patient care. We're trying to capture enough information off, you know, patient analytics like this watch is gonna capture vitals from a going forward. We're doing a lot what we can do in the ambient level so that information and data is automatically captured and decisions are being rendered against that. Maybe you're gonna change your diet along the way, maybe you're gonna walk an extra 10 minutes. All those things are gonna be provided in that level of automation. Take the car business. It's not about selling cars. Tesla's a great example. We talk about this all the time. What Tesla's doing, they're basically gonna be an insurance company with all the data they have. They have better data than the insurance companies. They can do better underwriting, they've got better mapping information and insights they can actually suggest next best action do collision avoidance, right? Those are all the things that are actually happening today. And automation plays a big role, not just in the collection of that, that information insight, but also in the ability to make recommendations, to do predictions and to help you prevent things from going wrong. >>So, you know, it's interesting. It's like you talk about Tesla as the, the disrupting the insurance companies. It's almost like the over the top vendors have all the data relative to the telcos and mopped them up for lunch. Pascal, I wanna ask you, you know, the topic of future of work kind of was a bromide before, but, but now I feel like, you know, post pandemic, it, it actually has substance. How do you see the future of work? Can you even summarize what it's gonna look like? It's, it's, Or are we here? >>It's, yeah, it's, and definitely it's, it's more and more important topic currently. And you, you all heard about the great resignation and how employee experience is more and more important for companies according to have a business review. The companies that take care of their employee experience are four times more profitable that those that don't. So it's a, it's a, it's an issue for CEOs and, and shareholders. Now, how do we get there? How, how do we, how do we improve the, the quality of the employee experience, understanding the people, getting information from them, educating them. I'm talking about educating them on those new technologies and how they can benefit from those empowering them. And, and I think we've talked a lot about this, about the democratization local type of, of technologies that democratize the access to those technologies. Everyone can be empowered today to change their work, improve their work, and finally, incentivization. I think it's a very important point where companies that, yeah, I >>Give that. What's gonna be the key message of your talk tomorrow. Give us the bumper sticker, >>If you will. Oh, I'm gonna talk, It's a little bit different. I'm gonna talk for the IT community in this, in the context of the IT summit. And I'm gonna talk about the future of intelligent automation. So basically how new technologies will impact beyond what we see today, The future of work. >>Well, I always love having you on the cube, so articulate and, and and crisp. What's, what's exciting you these days, you know, in your world, I know you're traveling around a lot, but what's, what's hot? >>Yeah, I think one of the coolest thing that's going on right now is the fact that we're trying to figure out do we go to work or do we not go to work? Back to your other point, I mean, I don't know, work, work is, I mean, for me, work has been everywhere, right? And we're starting to figure out what that means. I think the second thing though is this notion around mission and purpose. And everyone's trying to figure out what does that mean for themselves? And that's really, I don't know if it's a great, great resignation. We call it great refactoring, right? Where you work, when you work, how we work, why you work, that's changing. But more importantly, the business models are changing. The monetization models are changing macro dynamics that are happening. Us versus China, G seven versus bricks, right? War on the dollar. All these things are happening around us at this moment and, and I think it's gonna really reshape us the way that we came out of the seventies into the eighties. >>Guys, always a pleasure having folks like yourself on, Thank you, Pascal. Been great to see you again. All right, Dave Nicholson, Dave Ante, keep it right there. Forward five from Las Vegas. You're watching the cue.