>> Live from San Francisco, it's theCUBE, covering RSA Conference 2019. Brought to you by Forescout. >> Hey, welcome back everybody, Jeff Frick here with theCUBE, we're at the RSA Conference in downtown San Francisco, it's crazy, 40,000 plus people, we'll get the number later today. We're in the Forescout booth for our first time, we're really excited to be here, and, you know, part of the whole Forescout story is the convergence of IT and OT, operations technology, and those things are coming together, which is such a critical piece of smart things, and smart cities, and smart cars. We're excited to have our next guest, Elisa Costante, on. She is the OT technology and innovation lead at Forescout. Elisa, great to see you. >> Great to see you, thank for having me. >> Absolutely. So you've got a PhD in this space, you picked a field that is pretty hot, so as you think back and look at the convergence of OT and IT, what are some of the top-level things that people are thinking about, but what are some of the top-level things that they're just missing? >> Well, when you speak about OT, typically you refer to critical infrastructure and the technology that operates things. So it's cyber-physical systems, right? And when you think of IT, you think about computer and you think about the web, and you're like, okay, when the two things meet? And then you put in the recipe, you put something like an IoT device, like an IP camera, or a sensor for the number of people in a room. Now these whole things are coming together. And they're coming together because they come with a lot of interesting use cases. You can have all the data and information to configure, for instance, your building, to be as smart as possible, and to have. >> They need smart wheels on that cart, my goodness. >> Of course. And you have a clear picture of how much energy you consume and then you can basically have the energy that is cheaper, because it just arrives in the moment that you need it. Now all of these things are IT and OT convergence. And all of these things make our cities and our world smarter today. >> Right, now one of the interesting things I saw in a talk getting ready for this is, you talked about, there's always been a lot of OT systems, they've been around for a while, >> Yeah. >> But they've always been siloed, you know, they haven't been connected to other OT systems and much less being connected to IT systems. >> Yeah >> So they weren't architected for that from the first point of view. So how does that get implemented? Are they re-architecting 'em? Are you guys overlaying a different kind of control plane? How do you take these siloed applications around, say, elevator operation, and then integrate it in with all these other things? >> So what happens is that those systems are legacy systems. That's why. There are like, 60% of the modern buildings, of the buildings today, they have, they are controlled and managed by system that are 20 years old. So what does it mean? That you make an investment and you don't want to change that investment. You are not going to renew all the backbones of your buildings, or of your manufacturing and operation factories. So what do you do on top of these legacy system that have been developed without security in mind, you put the IT systems, to monitor, to control, to have remote access and remote control. And this is where, like, things can go wrong, because if this is not done properly, and by having in mind, for instance, the threat landscape, that's where you will have the controller for your HVAC exposed to the internet, and can pull down all the air conditioning in a hospital, for instance. And that's why WannaCry can come and heat and put down tons and tons of hospitals. >> Right. It's pretty interesting, you know, I think it's a pretty common concept in security for people that you should only have access, you know, to the information you need around a particular project or particular dataset. But you talked about, in some of your other talks that I saw, about a lot of these devices come out of the box with all kinds of capabilities, right? 'Cause they're built for kind of the Nth degree, the maximum use, but there may be a whole bunch of stuff that's turned on out of the box that you probably need to turn off. >> Yeah, that's actually super interesting. If you look at IP cameras, now IP cameras, they should do one thing, record stuff that they see on the screen. But actually they come with a bunch of protocols indeed, like FTPs, Samba protocols, SSDP, that announce the camera on the network, and reveal a lot of information about those camera on the network that if RPCed by an attacker or by someone with not-good intentions, might actually be leveraged to turn the camera against the owner of the camera itself. >> Right, right. And do weird things that the camera should not. And that's really part of what the Forescout solution is, is making sure that the devices are profiled and acting in the way that they're supposed to act. And not doing stuff that they shouldn't be doing. >> Yeah, Forescout is a leader in device visibility. So what we do is we enter into a network, and we give full visibility of all the IP devices that are there, and that's most of the times is a wow effect, like, the asset owner has no ideas that they had a camera that was directly connected to the internet. Or they'd have a thermostat that communicates with the servers. So all of these things, we bring basically light on the dark sides of the network. >> Right. So excited to talk to you 'cause I think the smart cities and smart buildings is such an interesting concept and going to be so important as we get denser populations and smaller areas that connected to transportation. I wonder if you could share some examples that you see out in the field where the ROI on putting these things in, the good part, is way higher than maybe people expect. That because you're combining, you know, a one plus one equals three kind of an opportunity. >> Right, so actually, one example of a very useful and smart use case is, is happening in Amsterdam right now. The Bijlmer Arena, is basically all the walls are made of solar panels, which means it gets the energy and is able to basically self-sustain the arena. The arena is one of the biggest stadiums in the Netherlands. >> Ajax plays there probably? >> Exactly. >> Alright. >> Now what they do if they have collected more energy than they are able to consume, they provide that same energy to the neighbors. Which means that you have basically a small ecosystem that thanks to the collection of data, knowing what neighbor needs how much light and energy in a certain time, you can actually even improve sustainability and going green initiatives. >> I love the innovation that comes out of the Netherlands. We interviewed a company a long time ago, and they were basically doing segmented data centers, where you would have a piece of the data center in your house and they were selling it as free heating. And I'm like, is it free heating, or is it distributed data center? But I mean, the creativity is terrific. So as you look forward, you know, what are you excited about in 2019? What are some of your top initiatives that you're working on? >> So we are working on a lot of IT and OT convergence, and especially on the IoT part. So we are looking at all those tiny devices that you would not expect to be on your network, and what they can do, and how these old systems that have been conceived to be standalone are now starting to communicate, and what kind of threats this communication can bring, and what we can do to actually defend our customers from the threats that can be arised. >> Going to be a good year. Excited to watch the developments unfold. >> Yeah, thanks. >> All right Elisa, thanks for taking a few minutes of your day, I know you said you had early meetings, you're calling Europe, calling all over the world, so thanks for taking a few. >> Thank you for having me. >> All right, she's Elisa, I'm Jeff, you're watching theCUBE. We're at RSA Conference, RSAC is the hashtag, in the Forescout booth. I'm Jeff Frick, thanks for watching. >> Thank you. (upbeat music)

>>From the Bellagio hotel in Las Vegas, it's the queue covering UI path forward for brought to you by UI path. >>We'll go back to the cubes coverage of UI paths forward for big customer event. You know, this company has always bucked the trend and they're doing it again. They're having a live event, physical event. There are customers here, partners, technologists. I'm here with Lisa Martin, my co-host for the show. And we're going to talk about testing. It's a new market for UI path. If anybody knows anything about testing, it's kind of this mundane, repetitive process ripe for automation geared vice-chairs. Here's the senior vice president of testing products at UI path and Matt Elisa. Who's the product marketing lead at UI path. Gents. Welcome to the cube. Thanks for coming on. Thanks for having us feminists. Explain to us how you guys think about testing both from an internal perspective and how you're going to market. >>Yeah, well, testing has been around for a long time, right? 25 years or so when, when I came to UI pass, the first thing I looked at was like, how do our customers test RPA? And it's quite interesting. We did a survey actually with 1500 people and, uh, 27% said that they wouldn't test at all. And I thought that's really interesting. RPA is a business critical software that runs in your production environment and you probably have to test. So we came up with this idea that we create the test suite we're using, you know, proven technology from UI pass. And, and we built this offering and brought this into the market for RPA testing and for application testing. So we do both. And of course we use it internally as well. I mean, that will be, you know, eat your own dog food or drink your own champagne, I guess. Yeah. >>Well, think about it. If you, if you automate, if you, if there's an ROI to automate a process, there's gotta be an ROI to verify that it's going to work before it goes into production too. And so it's amazing that a lot of companies are not doing this and they're doing it manually, um, today. >>So, so, but so, but parts of testing have been automated, haven't they with regression testing. So can, can you guys take us through kind of the before and after and how you're approaching it versus the traditional way? >>Yeah, absolutely. I mean, like I said, testing is not new, right? Um, but still when you look at the customers, they're not out to meeting more than I would say, 30, 40% of the manual tests. So still a lot of Stan manually, which I think, and we talked about this right manual testing is the, the original RPA. It's a tedious, repetitive tasks that you should not do manually. Right? And so what we are trying to bring in is now we're talking about this new role, it's called a digital tester. The digital tester is an empowered. We could call a manual tester, who's able to build automation and we believe that this will truly increase the automation, even in the existing testing market. And it's going to be, I don't want to use the word game-changer, but it's gonna change. Uh, the way testing is done. Yeah. >>And we're, we're applying, um, all the capabilities of UI path and delivering those testers, just like we would for HR team or a, or a, a finance and accounting team. But testing even has they understand this more, they've been doing this for 20 years. They understand automation and we're going to get them things like process mining so they can figure out what tests they need to run from production data. We're going to give them task mining so they can make more human-like tests test. Exactly. Like I used to be a tester, uh, and I ran a test team. And what I used to do is I have to go out to a warehouse and I'd have to go watch people as they entered orders, to make sure I was testing it the right way. So they would like click. We usually thought they were clicking things, whether you're using hotkeys, that's just an example of what they were doing. But now we can do task, task mining to get that remotely, pull that data in and do tests and make more realistic tests. >>How much of the there's so much potential there? I think you were saying that only 27% are actually doing testing. So there's so much opportunity. I'm curious, where are your conversations within the customer organization? We know that automation is a board level investor topic. Where are you? Where are those discussions with the testing folks, the RPA folks, helping them come together? >>Well, that's interesting. The question we typically, on the IP side, we talked to the cos by the people that are professionally developing those RPAs, but very easily, we get introduced to the test side of the house. And then usually there's a joint meeting where the test people are there, the RPA people are there. And that's why we are talking about this is going to convert somehow, right? They are in different departments today. But if you think about it, if five years down the road, maybe 10 years, they might be an automation discipline for the entire enterprise. So if that answered your question about, >>Yeah, >>Yeah. And we have a customer coming presenting this afternoon, Chipola and they're gonna be talking about how they, both of the teams are using a test teams and the RPA teams. And they built a reusable component library that, so when they built RPA team built their automations, they put them in a reusable library and the test team is able to recreate their tests much faster, reusing about 70% of the components. And so when the, when you think of automation, they're thinking about automating the application, not automating a process or a test so that people can use those like Lego blocks and build it if they're doing so, they could even, even it automation, if they wanted to start doing it, automation, they could pull those components out and use those. >>This is game changing is quality because so often, because in this day and age of agile, it's like move fast and break things. A lot of things break. And when we heard this morning in the keynotes, how you guys are pushing code like a couple of times a week, I mean, it's just a constant. And then you do two big releases. Okay. I get, I get it for the on-prem. But when you're pushing code that fast, you don't have time to test everything. There's a lot of stuff that's unknown. And so to the extent that you can compress all those checkboxes, now I can focus on the really important things that sometimes are architectural. How do you expect applying RPA to testing is going to affect the quality? Or maybe you got some examples. Chipotle. You just mentioned what, >>First of all, I mean, when you say we pushing code like bi-weekly or so, right. We're talking about continuous development. That's what it's called. Right? It's agile. You have sprint cycles, you continue to bring new code, new code, new code, and you test all the increments with it. So it's not that you building up a huge backlog for the testing on the RPA side. What I see is that there will be a transformation about the process, how they develop RPA at the moment. It's still done very much, I would say, in a waterfall issue, which is agree, >>A big bang waterfall. >>Yeah. It will transition. We already have partners that apply agile methodologies to their actually RPA development. And that's going to change that. >>Okay. So it's not so it's quality for those that are in testing obviously, but, but it's, but for the waterfall guys, it's, it's compressing the time to value. Oh yeah. That's going to be the big key. Yeah. That's really where it's coming. >>But he said his Chipotle is, was able to reuse 70% of the automation components. Right. That's huge. I mean, you have to think about it. 70% can be reused from testing to RPA and vice versa. That's a huge acceleration. Also on the IPA side, you can automate more processes faster. If you have components that you can trust. >>So you were a tester. Yeah. So you were a cost center. Yes, exactly. >>Unnecessary. What's the budget. >>So could you think RPA and automation can flip that mindset? Yes, >>Totally. And that's one of the things we want to do is we want to turn testing from a cost center to a value center, give testers a new career paths, even because really testers before all you could do is you could be more technical. Maybe you become a developer or you could be a manager, but you couldn't really become like an automation architect or a senior automation person. And now we're giving them a whole different career path to go down. So it's really exciting >>Because I know when I came out of college, I had a job offer and I wanted to be a developer, a programmer. We call them back then. And the only job I could get was as a tester. And I was like, oh, this is miserable. I'm not doing this, but there's a, there was a growth path there. They were like, Hey, do this for two or three years, maybe five years. I was like, forget it. I'm going into sales and marketing. But so what's the, what's the growth path today for the tester. And how do you see this >>Changing? So you want to go, you want to, I can take that one. No, you take it. I mean, I did it, so really it's, I mean, we're going to be giving these guys, the testing market has been kind of not innovating for years and years and years. And so we're going to be giving these guys some new tools to make them more powerful, make even the cause. Testing is a kind of a practice that is, you know, like, like you said, you didn't like testing. I didn't like testing either. Actually I hate testing. So I automated it. Right. So, um, and so that was the first thing I did. And so I think we're going to give these guys some new tools, some ways to grow their career and some ways to be even better testers, but like, like, like we talked about process mining, test mining, like maybe they're maybe they're testing the wrong things. Maybe they're not testing, you know, maybe, you know, there, cause there's kind of this test, everything mentality where we need to test everything and the whole release instead of like focusing in on what changed. And so I think we'll be able to help them really focus on the testing and the quality to make it more efficient as well. However, >>So T to defend the testers, right test is a very skilled people. Yes. They know their business, they know what to test and how to test in a way that nobody else knows that it's something we sometimes underestimate. They are not developers, so they don't write code or they don't build automations typically. But if we can equip them with tools that they can build out information, you have the brain and the muscle together, you know what I mean? You don't have to delegate the automation to some, whatever team that is maybe outsourced even you can do it. In-house and I think to some extent, that was also the story of Chipotle, right? Yeah. Yeah. They were in sourcing again because they're building their own >>And it saved them time because they have deal is handoffs, you know, to an external third party to do the testing for them. And so they pulled it all in made things much more streamlined and efficient. How >>Is that? It seems like a big cultural shift within any type of organization in any industry we're using as an example here, how does UI path help facilitate that cultural shift? Cause that's big and we're talking about really reducing, um, or speeding time to value. >>Right. Right. And it is a lot of the agile methodology is like, we're starting. So it's kind of like, we're going back in time, you know, and we're teaching these people, you know, the RPA community, all of the things that we learned from software development. Right. And so we're going to bring applying that to this. And so all those agile mindset, the th the agile values, you know, those are the things that are going to help them kind of come together. And that's one of the things that Julie talked about is one of the things is they had a kind of agile mindset, a can-do attitude that pulled them together. >>I think one thing that will really helps with changing the culture is empowering the people. If you give them the tools that they can do, they will do, and that will change the culture. I don't think it can come from top down. It needs to come from within and from the people. And that's what we see also with RPA, by the way, is adopted on department level and D build automations. And then at some point it becomes maybe an enterprise wide initiative, right. But somebody in HR had this idea and started >>The other thing too, is Matt, you mentioned this, you could go to a third party. So what years ago? In the early two thousands, we had a software company. We would use a company called agile on. They were us. I don't know if you ever heard of them. They're basically, we're a job shop. And we would throw our code over the very waterfall, throw the code over the fence. It was a black box and it was very asynchronous. And it would come back, you know, weeks later. And they say, I fix this, fix this, but we didn't have the analytics we didn't have. There was no transparency. Had we had that. We would have maybe come up with new ideas or a way to improve it because we knew the product way better. And so if you can bring that, in-house now you've got much better visibility. So what, what analytics are analytics a piece of this? >>Is that something that is so, I mean, I'll give you an example, SAP systems, right? When you have SAP systems, customers apply transports like five or 10 a day. Every transport can change the system in a way that you might break the automation. We have the possibility to actually not only understand what's going on in this system with process mining, but we also have the possibility to do change, impact, money, and change impact. Mining tells me with every process, every transport I apply, what has changed, and we can pinpoint the test cases that you need to run. So instead of running a thousand test cases, every time we pinpoint 50 of them and you know exactly what has changed. Yeah. >>That's right. Cause a lot of times you don't know what you don't know. And you're saying the machine is basically saying focus on these areas that are going to give you the biggest, that's kind of Amdahl's law, isn't it focus on the areas that are going to get the most return. Yeah. So this is a new business for UI path. You guys are targeting this as a market segment. Can you tell us more about that? >>We joined about two years ago. It takes some time to build something, right. There was a lot of proven technology there. And then we lounged, uh, I think it wasn't July last year, which was more like a, uh, private lounge. We, we didn't make much noise around it and it's gaining a lot of traction. So it's several hundred customers have already jumped on their test bandwagon, if you can call it this way. And yeah, this, this year we were pushing full speed into the testing market as well, because we see the benefits that customers get when they use both like the story from Chipotle. It has other customers like Cisco and, and more, when you hear the stories, what they were able to achieve. I mean, that's a no-brainer I think for any customer who wants to improve the automation. Yeah. >>Well, and also we're taking production grade automation and giving it to the testers and we're giving them this advanced AI so they can automate things. They weren't able to automate before, like Citrix virtual virtualized machines, point of sale systems, like 12 layer, any other business would have, they can automate all those things now that they couldn't do before, as well as everything else. And then they can also the testing tools, they talked about fragmentation this morning. That's another problem is there's a tool for mobile. There's a tool for this. There's a tool for API APIs. You have all these tools, you have to learn all these languages. We're going to give them one. They can learn and use and apply to all their technologies. And it's easy to use and it's easy to use. Yeah. >>That's kind of been the mantra of UI path for very long time, easy to use making, making RPA simple. We've got 8,000 plus customers. You mentioned a few of them. We're going to have some of them on the program this week. How do you expect good question for you that stat that you mentioned from that survey in the very beginning of our conversation, how do you expect that needle to move in the next year? Because we're seeing so much acceleration because of the pandemic. >>That's a really good question because the questions that we had in the, after we had the first hundred, right? The values didn't change that much. So we have now 1500 and you would assume that is pretty stable from the data. It didn't change that much. So we're still at 27% that are not testing. And that's what we see as our mission. We want to change that no customer that has more than, I dunno, five processes in production should not like not test that's crazy and we can help. And that's our mission. So, but the data is not changing. That's the interesting part. >>I know, I know we're out of time, but, but we're how do you price this? Is it a, is it a set? Is it a subscription? Is it a usage based model? How, how do you, >>It's fully included in the UI pass tool suite. So it means it's on the cloud and on-prem the pricing is the same. We are using this. There >>It is. Yeah. >>It's the same components. Like, like we're using studio for automation, we're using orchestrator, but we're using robots. We have cloud test manager on prem test manager. It's just a part of the >>Value, add that you're putting into the platform. Yeah, yeah, >>Exactly. Yeah. There are components that are priced. Yes. But I mean, it's part of the platform, how it is delivered. >>Yeah. So I paid for that module and you turn it on and use it. So it's a subscription. It could be an annual term if I want multi-year term. I can do that. Exactly. Good. Great guys. Thanks so much for coming on the Cuban and good luck with this. Thank you. Great, great innovations. Okay. Keep it right there at Dave Volante for Lisa Martin, we'll be back with our coverage of UI path forward for, from the Bellagio in Las Vegas. Keep it right there.

>>From the Bellagio hotel in Las Vegas, it's the cube covering UI path forward for brought to you by UI path. >>We'll go back to the cubes coverage of UI paths forward for big customer event. You know, this company has always bucked the trend and they're doing it again. They're having a live event, physical event. There are customers here, partners, technologists. I'm here with Lisa Martin, my co-host for the show. And we're going to talk about testing. It's a new market for UI path. If anybody knows anything about testing, it's kind of this mundane, repetitive process ripe for automation geared vice-chairs. Here's the senior vice president of testing products at UI path and Matt Elisa. Who's the product marketing lead at UI path. Gents. Welcome to the cube. Thanks for coming on. Thanks for having a feminist Likert. Explain to us how you guys think about testing both from an internal perspective and how you're going to market. >>Yeah, well, testing has been around for a long time, right? 20 twenty-five years or so when, when I came to UI pass, the first thing I looked at was like, how do our customers test RPA? And it's quite interesting. We did a survey actually with 1500 people and, uh, 27% said that they wouldn't test at all. And I thought that's really interesting. RPA is a business critical software that runs in your production environment and you probably have to test. So we came up with this idea that we create the test suite. We're using, you know, proven technology from UI pass. And, and we built this offering and brought us into market for RPA testing in for application testing. So we do both. And of course we use it internally as well. I mean, that will be, you know, eat your own dog food or drink your own champagne, I guess. So >>I want to think about it. If you, if you automate, if you, if there's an ROI to automate a process, there's gotta be an ROI to verify that it's going to work before it goes into production too. And so it's amazing that a lot of companies are not doing this and they're doing it manually, um, today. >>So, so, but so, but parts of testing have been automated, haven't they with regression testing. So can, can you guys take us through kind of the before and after and how you're approaching it versus the traditional? >>Yeah, absolutely. I mean, like I said, testing is not new, right? Um, but still when you look at the customers, they're not out to meeting more than I would say, 30, 40% of the manual tests. So still a lot of Stan manually, which I think, and we talked about this right manual testing is the, the original RPA. It's a tedious, repetitive tasks that you should not do manually. Right? And so what we are trying to bring in is now we're talking about this new role it's called the digital tester. The digital tester is an empowered. We could call a manual tester, who's able to build automation and we believe that this will truly increase the automation, even in the existing testing market. And it's going to be, I don't want to use the word game changer, but it's going change. Uh, the way testing is done. Yeah. >>And we're, we're applying, um, all the capabilities of UI path and delivering those to testers, just like we would for HR team or a, or a, a finance and accounting team. But testing even has they understand this more, they've been doing this for 20 years. They understand automation and we're going to give them things like process mining so they can figure out what tests they need to run from production data. We're going to give them task mining so they can make more human-like tests test. Exactly. Like I used to be a tester and I ran a test team. And what I used to do is I have to go out to a warehouse and I'd have to go watch people as they entered orders, to make sure I was testing it the right way. So they would like click. We usually thought they were clicking things, but they were using hotkeys. That's just an example of what they were doing. But now we can do task task mining to get that remotely, pull that data in and do tests and make more realistic tests. >>So much of the there's so much potential there. I think you were saying that only 27% are actually doing testing. So there's so much opportunity. I'm curious, where are your conversations within the customer organization? We know that automation is a board level investor topic. Where are you? Where are those discussions with the testing folks, the RPA folks, helping them come together? >>Well, that's interesting. The question, uh, we typically on the IPS, have we talked to the cos, right? The people that are professionally developing those RPAs, but very easily, we get introduced to the test side of the house. And then usually there's a joint meeting where the test people are there, the RPA people are there. And that's why we are talking about this is going to convert somehow, right? The are in different departments today. But if you think about it, five years down the road, maybe 10 years, they might be at an automation discipline for the entire enterprise. So if that answered your question about, >>Yeah. >>Going to require a cultural shift. Yeah. And we have a customer coming presenting this afternoon. and they're gonna be talking about how they, both of the teams are using a test teams and the RPA teams. And they built a reusable component library that, so when they built RPA team built their automations, they put them in a reusable library and the test team is able to recreate their test much faster reusing about 70% of the components. And so when the, when you think of automation, they're thinking about automating the application, not automating a process or a test so that people can use those like Lego blocks and build it if they're doing so, they could even, even it automation, if they wanted to start with an it automation, they could pull those components out and use those. >>I think this is game changing is quality because so often, because in this day and age of agile, it's like move fast and break things. A lot of things break. And when we heard this morning in the keynotes, how you guys are pushing code like a couple of times a week, I mean, it's just a constant. And then you do two big releases. Okay. I get, I get it for the on-prem. But when you're pushing code that fast, you don't have time to test everything. There's a lot of stuff that's unknown. And so to the extent that you can compress all those check boxes, now I can focus on the really important things that sometimes are architectural. How do you expect applying RPA to testing is going to affect the quality? Or maybe you've got some examples. Chipotle, you just mentioned, >>First of all, I mean, when you say we pushing code like bi-weekly or so, right. We're talking about continuous development. That's what it's called. Right? It's agile. You have sprint cycles, you continue to bring new code, new code, new code, and you test all the increments with it. So it's not that you building up a huge backlog for the testing on the IPA side. What I see is that there will be a transformation about the process, how they develop RPA at the moment. It's still done very much, I would say, in a waterfall way, which is agree. A big bang waterfall. Yeah. It will transition. We already have partners that apply agile methodologies to their actually RPA development. And that's going to change that. >>Okay. So it's not so it's quality for those that are in testing obviously, but, but it's, but for the waterfall guys, it's, it's compressing the time to value. Oh yeah. That's going to be the big key. That's really worth. >>I mean, what he said is Chipotle is, was able to reuse 70% of the automation components. Right. That's huge. I mean, you have to think about it. 70% can be reused from testing to RPA and vice versa. That's a huge acceleration. Also on the RPA side, you can automate more processes faster. If you have components that you can trust. >>So you were a tester. Yeah. So you were a cost center. Yes, exactly. >>Unnecessary. What's the budget. >>So could you think RPA and automation can flip that mindset? >>Yeah, totally. And that's one of the things we want to do is we want to turn testing from a cost center to a value center, give testers a new career paths, even because really testers before all you could do is you could be more technical. Maybe you become a developer or you can be a manager, but you couldn't really become like an automation architect or a senior automation person. And now we're giving them a whole different career path to go down. So it's really exciting. >>'cause I know when I came out of college, I had a job offer and I wanted to be a developer, a programmer. We called them back then. And the only job I could get was as a tester. And I was like, oh, this is miserable. I'm not doing this, but there's a, there was, there's a growth path there. They were like, Hey, do this for two or three years, maybe five years. I was like, forget it. I'm going into sales and marketing. But so what's the, what's the growth path today for the tester. And how do you see this changing? >>So you want to go, you want to, I can take that one. No, you take it. So that's a really, yeah. I mean, I did it, so really it's, I mean, we're going to be giving these guys, the testing market has been kind of not innovating for years and years and years. And so we're going to be giving these guys some new tools to make them more powerful, make even the cause. Testing is a kind of a practice that is, you know, like, like you said, you, you didn't like testing. I didn't like testing either. Actually I hate testing. So I automated it. So, um, and so that was the first thing I did. And so I think we're going to give these guys some new tools, some ways to grow their career and some ways to be even better testers, but like, like, like we've talked about process mining, test mining, like maybe they're maybe they're testing the wrong things. Maybe they're not testing, you know, maybe, you know, there, cause there's kind of this test, everything mentality we're we need to test everything and the whole release instead of like focusing in on what changed. And so I think we'll be able to help them really focus on the testing and the quality to make it more efficient as well. >>Go ahead. So do to defend the testers, right? Test is a very skilled people. Yes. They know their business, they know what to test and how to test in a way that nobody else knows that it's something we sometimes underestimate. They are not developers so that they don't write code and they don't build automations typically. But if we can equip them with tools that they can build out information, you have the brain and the muscle together, you know what I mean? You don't have to delegate the automation to some, whatever team that is maybe outsourced even you can do it. In-house and I think to some extent, that was also the story of Portland sourcing again, because they're building their own automation. Yeah. >>And it saved them time because they have deal is handoffs, you know, to an external third party to do the testing for them. And so they pulled it all in made things much more streamlined and efficient. How >>Is that? It seems like a big cultural shift within any type of organization in any industry we're using Chipola as an example here, how does your path help facilitate that cultural shift? Because that's big and we're talking about really reducing, um, or speeding time to value. >>Right. Right. And it is a lot of the agile methodologies like we're starting. So it's kind of like, we're going back in time, you know, and we're teaching these people, you know, the RPA community, all of the things that we learned from software development. Right. And so we're going to be applying that to this. And so all those agile mindset, the th the agile values, you know, those are the things that are going to help them kind of come together. And that's one of the things that Julie talked about is one of the things is they had a, kind of an agile mindset, a can-do attitude that pulled them down. >>And I think one thing that will really helps with changing the culture is empowering the people. If you give them the tools that they can do, they will do, and that will change the culture. I don't think it can come from top down. It needs to come from within and from the people. And that's what we see also with RPA, by the way, is adopted on department level and D build automations. And then at some point it becomes maybe an enterprise wide initiative, right. But somebody in HR had this idea and started >>The other thing too, is Matt, you mentioned this you'd go to a third party. So years ago in the early two thousands, we had a software company. We would use a company called agile on. They were, so I don't know if you ever heard of them. They're basically, we're a job shop. And we would throw our code over the very waterfall, throw the code over the fence. It was a black box and it was very asynchronous. And it would come back, you know, weeks later. And they say, oh, I fixed this, fixed this, but we didn't have the analytics we didn't have. There was no transparency had we had that. We would have maybe come up with new ideas or have way to improve it because we knew the product way better. And so if you can bring that, in-house now you've got much better visibility. So what, what analytics are our analytics a piece of this? And is that something? Yeah. >>Yeah. So, I mean, they'll give you an example, SAP systems, right? When you have SAP systems, customers apply transports like five or 10 a day. Every transport can change the system in a way that you might break the automation. We have the possibility to actually not only understand what's going on in this system with process mining, but we also have the possibility to do change, impact, money, and change impact. Mining tells me with every process, every transport I apply, what has changed, and we can pinpoint the test cases that you need to run. So instead of running a thousand test cases, every time we pinpoint 50 of them and you know exactly what has changed. Yeah. >>That's right. Because a lot of times you don't know what you don't know. And you're saying the machine is basically saying focus on these areas that are going to give you the biggest, that's kind of Amdahl's law. Isn't it focus on the areas that going to get the most return. Yeah. So this is a new business for UI path. You guys are targeting this as a market segment. Can you tell us more about that? >>We joined about two years ago. It takes some time to build something, right. There was a lot of proven technology there. And then we lounged, uh, I think it wasn't July last year, which was more like a private lounge. We, we didn't make much noise around it and it's gaining a lot of traction. So it's several hundred customers have already jumped on that test bandwagon, if you can call it this way. And yeah, this, this year we are pushing full speed into the testing market as well, because we see the benefits that customers get when they use both like the story from Chipotle. It has other customers like Cisco and, and more, when you hear the stories, what they were able to achieve. I mean, that's a no-brainer I think for any customer who wants to improve the automation. Yeah. >>Well, and also we're taking production grade automation and giving it to the testers and we're giving them this advanced AI so they can automate things. They weren't able to automate before, like Citrix virtual virtualized machines, point of sale systems, like 12 layer, any other business would have, they can automate all those things now that they couldn't do before, as well as everything else. And then they can also the testing tools, they talked about fragmentation this morning. That's another problem is there's a tool for mobile. There's a tool for this. There's a tool for API APIs and you have all these tools. You have to learn all these languages. We're going to give them one that they can learn and use and apply to all their technologies. And it's easy to use and it's easy to use. Yeah. >>That's kind of been the mantra of UiPath for very long time, easy to use making, making RPA simple. We've got 8,000 plus customers. You mentioned a few of them. We're going to have some of them on the program this week. How do you expect good question for you that stat that you mentioned from that survey in the very beginning of our conversation, how do you expect that needle to move in the next year? Because we're seeing so much acceleration because of the pandemic. >>A really good question, because the questions that we had in the beginning after we had the first hundred, right? The values didn't change that much. So we have now 1500 and you would assume that is pretty stable from the data. It didn't change that much. So we're still at 27% that are not testing. And that's what we see as our mission. We want to change that no customer that has more than, I dunno, five processes in production should not like not test that's crazy and we can help. And that's our mission. So, but the data is not changing. That's the interesting part. >>And I know, I know we're out of time, but, but we're how do you price this? Is it a, is it a set? Is it a subscription? Is it a usage based model? How >>It's fully included in the UI pass tool suite. So it means it's on the cloud and on-prem the pricing is the same. We are using this. There it is. Yeah. It's the same components. Like, like we're using studio for automation, we're using orchestrator, but we're using robots. We have cloud test manager on prem test manager. It's just a part of the, >>So it's a value add that you're putting into the platform. Yeah, yeah, exactly. >>Yeah. Th there are components that are priced. Yes. But I mean, it's part of the platform, how, >>But it's a module. So I paid for that module and you turn it on and then they can use it. So it's a subscription. It could be an annual term if I want multi-year term, I can do that. Exactly. Good. Great guys. Thanks so much for coming on the Cuban and good luck with this. Thank you. Great, great innovations. Okay. Keep it right there at Dave Volante for Lisa Martin, we'll be back with our coverage of UI path forward for, from the Bellagio in Las Vegas. Keep it right there.

>>long from Las Vegas. It's the Q covering a ws re invent 2019. Brought to you by Amazon Web service is and in along with its ecosystem partners. >>Welcome back to the Cube. We are in Las Vegas, Lisa Martin with John Wall's. I'm very excited that we're kind of color coordinated >>way. Didn't compare notes to begin with, but certainly the pink thing. It's worth it if >>you like. You complete me. >>Oh, thank you. Really, Joe, I don't hear that very often. My wife says that >>you tell that we're at the end of day one of the coverage of A W s three in bed. Good day, though. Yes, it has been very excited. We have a couple of guests joining us for our final segment on this. Please welcome. We have Bill Gerard CTO of Digital Transformation and Scale solutions at Intel Bill, welcome to our show. >>Thank you very much. Happy to be here >>And one of our friends. That's no stranger to the Cube. One of our former host, Bobby Allyn, the CEO of Cloud Generate. Bobby. >>Thank you. Thank you for having us. >>Guys, here we are. This there has not been a lull in the background noise all day. Not reinvent day one. But Bobby want to start with you. Talk to her audience about cloud genera. Who are you guys? What do you do? And what's different about what you're delivering? >>One of the first things is different about Claude Generous where we're located. So we're in Charlotte, which I call Silicon South. So we're kind of representing the East Coast, and we're a company that focuses, focuses on helping with workload, placement and transformation. So where you don't know whether something should go on from off grim. If you put it in Amazon, which service's should have consumed licensing models? Pricing models way help you make data driven decisions, right? So you're not just going based on opinion, you're going based on fact. >>And that's challenging because, you know, in the as, as John Ferrier would say, No Cloud Wanda Otto, which was compute network storage, it was the easy I shouldn't say easy, but the lift and shit applications that enterprises do are these workloads should go to the cloud. Now we have you know what's left over, and that's challenging for organization. Some of the legacy once can't move. How do you help from a Consul Tatum's down point that customers evaluate workloads? What data are they running? What the value that data has and if they are able to move some of those more challenging applications. >>So part of the framework for us, Lisa, is we want to make sure we understand what people are willing and able to change right, because sometimes it's not just about lower costs. Sometimes it's about agility, flexibility, deploying a different region. So what we often start with his wit is better look like you would assist us with life for your organization. And so then, based on that, we analyze the applications with an objective, data driven framework and then make sure the apse land where they're supposed to go. We're not selling any skewer product. We're selling advice to give you inside about what you should do, >>Bobby, I think. And maybe Bill to you could chime in here on this. If you give people a choice, What does this look like? What you know, What do you want? I don't want to do anything right. I want to stay put, right? But that obviously that's not an option, But you I'm sure you do get pushed back quite a bit from these almost the legacy mindset. And we've talked a lot about this whole transformation versus transition. Some people don't want to go, period. So how do you cajole them? Persuade them bring them along on this journey? Because it's gonna be a long trip. Yeah, I think you gotta pack a lunch. >>It's a good point. I think what we've seen, most of them have data experience that this is a tried and elements didn't get the results that they expected. This is where you know, the partnership that we have with call General. Really? You know that data driven, intelligent, based planning is super important, right? We want to really fundamentally health organizations move the right workloads, make sure they get the right results and not have to redo it. Right? And so part of that, you know, move when you're either past scars or not used to what you're doing. Give him the data and the information to be able to do that intelligently and make that as fast as they can. And you know, at the right, you know, experience in performance from a capability perspective. >>So so many businesses these days, if they're not legacy if they're not looking in the rear view mirror, what is the side mirror site? Objects are closer than they appear, even for Amazon. Right? For all of these companies, there are smaller organizations that might be born in a cloud compared to the legacy two words. And if they're not looking at, we have to transform from the top down digitally, truly transform. Their business may not be here in a year or two, so the choice and I think they need to pack a lunch and a hip flask for this because it's quite the journey. But I'm curious with the opportunity that cloud provides. When you have these consultation conversations, what are This? Could be so transformative not just to a business, but to a do an entire industry. Bill talked to us from your perspective about some of the things that you've seen and how this next generation of cloud with a I machine learning, for example, can can really transfer like what's the next industry that you think is prime to be really flipped upside down? >>Well, the good news is I think most of the industries in the segment that we talked to have realized they need to some level of transformation. So doing the business as usual really isn't an option to really grow and drive in the future. But I do think the next evolution really does center on what's happening in a I and analytics. Whether it's, you know, moving manufacturing from video based defect detection, supply chain integrity. You know what's happening from a retail was really the first in that evolution, but we see it in health care in Federal Data Center modernization, and it's really moving at a faster pace and adopting those cloud technologies wherever they needed, both in their data center in the public, cloud out of the edge. And we'll start to see a real shift from really consolidation in tow. Large hyper converts, data centers to distributed computing where everything again. And that's where we're excited about the work we're doing with the Amazon, the work we're doing with Eyes V partners to be at the capability where they need it, but I think it will be really the next. Evolution of service is everywhere. >>Never talk us through an example or use case of a customer that you're working with, a cloud genera with intel and and a W S. What does that trifecta look like for, say, a retailer or financial service is organization >>so that that looks like this? ELISA. When we when we talk about workload placement, we think that most companies look at that as a single question. It's at least a five fold question. Right there is the venue. There's the service. There's the configuration, the licensing model and the pricing model. You need to look at all five of those things. So even if you decided on a DBS is your strategic partner, we're not done yet. So we have a very large financialservices customer that I can't name publicly. But we've collaborated with them to analyze tens of thousands of workloads, some that go best off from some that go best on for him. And they need guidance and coaching on things like, Are you paying for redhead twice your pay for licensing on him? Are you also paying for that in the cloud? There are things that maybe should be running an RT s database as a service. Here's your opportunity to cut down on labor and shift some of the relationships tohave, toe re index and databases is not glamorous or differential to value for your business. Let's take advantage of what a TBS does well and make this better for your company. One of the things that I want to kind of introduce to piggyback on your question. We lean on people process technology as kind of the three, the three legged horse in the Enterprise. I want to change that people process product or people process problem. We're falling in love with the tech and getting lazy. Technology should be almost ubiquitous or under the covers to make a product better or to solve a problem for the customer. >>Well, maybe on that, I mean automation concern to come in and make a big play here because we're taking all these new tasks if you could automate them that you free your people, your developers to do their thing right. So you raise an interesting point on that about being lazy and relying on things. But yet you do want off put our offload some of these nasty not to free up that creativity and free up the people to do what they're supposed to be doing. It's a delicate balance, though, isn't it? It is. It is. This >>is where I think the data driven, you know, informed decisions important. We did a lot of research with Cloud Jenner and our customers, and there's really four key technical characteristics when evaluating workload. The 1st 1 of course, is the size of the data. Where is the created words They use Words that consumed the 2nd 1? Is the performance right? Either performance not only to other systems around it or the end user, but the performance of the infrastructure. What do you need out of the capability? The level of integration with other systems? And then, of course, security. We hear that time and again, right? Regulatory needs. What are we having from top secret data to company sensitive data? Really Getting that type of information to drive those workload placement decision becomes at the forefront of that on getting, you know, using cloud gender to help understand the number of interfaces in and out the sides of the data. The performance utilization of the system's really helps customers understand how to move the right workload. What's involved and then how to put that in the right eight of us instance, and use the right ideas capabilities, >>and you and you both have hit on something here because the complexity of this decision, because it's multi dimensional, you talked about the five points a little bit ago. Now you talked about four other factors. Sue, this is not a static environment, No, and to me that as you're making a decision, that point is what's very difficult for, I would assume for the people that you're interfacing with on the company level. Yes, because it's a moving target for them, right? They just it's it's dynamic and changing your data flows exponentially. Increasing capabilities are changing. How do you keep them from just breaking down? >>I don't want to jump in on that, because again, I'm going to repeat this again. That my thesis is often technology is the easy part. We need to have conversations about what we want to do. And so I had a conversation earlier today. Think of Amazon like a chef. They could make anything I want, but I need to decide what I want to eat. If I'm a vegan and he wants steak. That's not Amazons fault. If they can't cook something, that's a mismatch of a bad conversation. We need to communicate. So what I'm finding is a lot of executives are worried about this. There were Then you're going to give me the right the wrong answer to the right question. The reality is you may have the wrong question. First of all right, the question is usually further upstream, so the worry that you're gonna give me the wrong answer to the right question. But often you need to worry that you're getting your starting with the wrong question. You're gonna get the right answer asked the right question first. And then you got a chance to get to the final destination. But >>and then he in this multi cloud world that many organizations live in, mostly not My strategy could be by Emma A could be bi developer preference for different solutions. A lot of Serios air telling us we've inherited a lot of this multi cloud and technical debt. Exactly. So does not just compound the problem because to your point, I mean you think of one way we hear so many different stats about the number of clouds that on average enterprises using is like 5 to 9. That whole world. That's a reality for organizations. So in terms of how the business can be transformed by what you guys are doing together, it seems like there's a tremendous opportunity there. But to your point, Bobby, where do you start? How do you help them understand what? That right first question is at the executive level so that those four technical points that Bill talked about Tek thee you know, the executive staff is all on board with Yes, this is the question we're asking then will understand it. The technology is right. Sold >>it. It's got to start with, Really? What? The company's business imperatives, right? It can't start with an I t objective. It's it's Are we moving into new markets? Do we need thio deploy capabilities faster? Are we doing a digital customer experience? Transformation? Are we deploying new factories, new products into new regions, and so really the first areas? What's the core company strategy, imperatives of the business objectives? And >>then how >>does I t really help them achieve that? In some cases, it may be we have to shift and reduce our data center footprints way have to move capabilities to where we have a new region. Deployments, right? We've got to get him over to Europe. We don't have capabilities in Europe. We're going to Asia. I've got a mobile sales force now where I need to get that customer, meet the customer where they're doing, you know, in the retail store, and >>that >>really then leads quite simply, too. What are the capabilities that we have in house that we're using? >>How are >>they being utilized? And he's using them, and then how do we get them to where they need to be? Some cases accost, imperative. Some cases and agility, Time to market and another's and we're seeing this more often is really what are the new sets of technologies? A. I service is training in forgetting that we're not experience to do and set up, and we don't want to spend the time to go train our infrastructure teams on the technology. So we'll put our data scientists in there figuring out the right set of workloads, the right set of technology, that we can then transform and move our applications to utilize it really starts, I think with the business conversation, or what's the key inflection point that they're experiencing? >>And have you seen that change in the last few years that now it's where you know, cloud not cloud. What goes on Cloud was an I t conversation to your point, Bill. And then the CEO got involved in a little bit later. But now we're we're seeing and hearing the CEO has got to be involved from a business imperative perspective. >>Share some data, right? Uh, so, you know, a couple of years ago, everybody was pursuing cloud largely for cost. Agility started to become primary, and that's still very important. A lot of the internal enterprise data modernizations were essentially stalled a bit because they were trying to figure how much do we move to the the public cloud, right. We want to take advantage of those modern service is at that time, we did a lot of research with our partners. He was roughly 56% of enterprise workload for in their own data center. You know, the rest of them Republic Cloud. And then we saw really the work, the intelligent workload discussion that says we've had some false starts. Organizations now really consistently realize they need both, you know, their own infrastructure and public cloud, and we've actually seen on increase of infrastructure modernization. While they're moving more and more stuff to the cloud, they're actually growing there on centre. It's now roughly 59% on Prem today for that same business, and that's largely because they're using more. Cloud service is that they're also even using Maur on premise, and they're realizing it's a balance and not stalling one or starving one and then committing to the other the committing to both and really just growing the business where it needs to go. >>Strategic reasons. All right? >>Yes, well, there should be four strategic reasons. There aren't always back to your question about which question asked. One of the questions I often ask is, What do you think the benefits will be if you go to cloud? And part of what happens is is not a cloud capability? Problem is an expectation problem. You're not gonna put your GOP system in the cloud and dropped 30% costs in a month, and so that's where we need to have a conversation on, You know, let's iterating on what this is actually gonna look like. Let's evolve the organization. Let's change our thinking. And then the other part of this and this were clouded or an intel come in. Let's model with simulation looks like. So we're gonna take those legacy work clothes unless model containers. Let's model Micro Service is so before you have to invest in transformation to may not make sense. Let's see what the outcome's look like through simulation through a through M l and understand. Where does it make sense to apply? The resource is, you know, to double click on that solution that will help the business. >>I was gonna finish my last question, Bobby, with you saying, Why, Cloud General? But I think you just answered that. So last question for you, though, from from an expectation perspective, give me one of your favorite examples of customer whatever kind of industry there and that you've come in and helped them really level, set their expectations and kick that door wide open. >>That's tough, many >>to choose from. >>Yeah, let me let me try to tackle that one quickly. Store's computer databases. Those are all things that people look at I think what people are struggling with the most in terms of kind of expectations is what they're willing and able to change. So this is kind of what I leave on. Bill and I talked about this earlier today. A product is good, a plan is better. A partnership is best. Because with the enterprises of saying is, we're overwhelmed. Either fix it for me or get in there with me and do it right. Be in this together. So what we've learned is it's not about were close applications. It's all kind of the same. We need help. We're overwhelmed. I want a partner in telling Claude Juncker the get in this thing with me. Help me figure this out because I told you this cloud is at best a teenager. They just learned how to drive is very capable, but it needs some guard rails. >>I love that. Thanks you guys So much for explaining with Johnny what you guys are doing together and how you're really flipping the model for what customers need to be evaluated and what they need to be asking. We appreciate your time. >>Thank you for having us >>our pleasure. Thank you. for John Wall's I'm Lisa Martin. You've been watching the Cube at Reinvent 19 from Vegas. Wants to go tomorrow.

>> live from Mountain View, California It's the queue covering definite create twenty nineteen. Brought to You by Cisco >> Welcome back to the Cube. Elisa Martin with Set Cisco Definite Create twenty nineteen at the Computer History Museum, but here all day, talking with some really great innovative folks excited to welcome to the Cube. Marty Jane, senior director of this Cisco Global Partnership and Video. Marty, It's great to have you here. >> Thank you. Good to be here. >> So I always love talking about partnerships Where what Day One of Dev. Net. Tomorrow's day to. There's been a lot of a lot of community spirit is here, so I just kind of in the spirit of partnerships, lot of collaboration that community is is really strong. Uh, before we get into kind of the details of this Cisco in video partnership first kind of thing, I wonder is all right. This is the developer community. Why the developer community within video? >> That's a great question. So if you think about way, make GP use, which is a piece of silicon graphics processing unit, and it is really only a piece of silicon until a developer comes along and develops a cool app on it. So if you think about how we go to market our large conferences called GTC, it's really developer. Focus. We have a little over a million developers in our ecosystem, and I find it very synergistic with Cisco. If you think about Suzy, we's vision. I think it's the same idea. You look at over half a million developers in their ecosystem and they want to develop collapse, and that's how your platform becomes relevant. So if you think of all the modern innovation that's coming from developers, so these are the folks that we should be talking to on a daily basis. I see a lot of commonality, a lot of synergies. In fact, we had Sisko definite come over to our conference GTC, and they they appeal to our developers. And now we're here talking to their developers and also developing some joint platforms which the the folks can use for. Like I said, the more modern *** with all the new data that's coming, whether the coyote with a machine learning automotive, smart cities, you name it, we need to be able to provide the platform to the developers >> and a number of those topics came up today, even during the keynote, Smart cities being able to utilize and accelerate work leads with a I and machine learning. They gave some great examples during the keynote of how developers can build networks. They give this cool example of I think it right off the hills of Coachella of designing a secure network for an indoor concert, designing it for an outdoor festival, Coachella and then designing it for a massive stadium like a big football game like the Super Bowl, for example. And they showed it that higher end. They showed how they're using machine, learning to zoom in on. For example, they had this little red box and you see people and what's actually in there than the machines detected was a fight and in real time, analysing this data and thence, dispatching the appropriate security to come and obviously probably take the drinks out of their hands first. But it was a really interesting, great real world example. So you guys have been partners a long time. Our you've been actually working at various companies with Cisco for a long time, but I think of Cisco and video coming together. How are you great? Something to accelerate these? Aye. Aye. And machine weren't were machine learning workloads that we're starting to see in every industry. >> You bet. Great question. So let me first comment on what you said about smart cities. I like to think of it as smart and safe cities. So actually, the first set of application will be around public safety. What the example you were giving his spot on? If you have large crowds gathering, it makes sense for us to be able to look at those clouds. Crowds? We call it intelligent video analytics or idea. In fact, we have a platform here. The Sisko i R eleven o one with a GPU added to it. So now I can wash the crowds. And if there's a fight breaking out or somebody's carrying in a weapon, you want to know somebody walks in carrying a backpack and drops it and moves on. You want to know one? Inform somebody. So what is happening is way of these millions and millions of bites of video data, >> and >> that data is not being really used today. So what we're doing is saying you know what? Let's find those pieces of intelligence and the video data and do something with it. And public safety is absolutely the highest priority. So smartest, safe city makes a lot of sense. So what we're doing is we're going to market with partners at Cisco. So what we're doing is we're saying Okay, let's design these GPS into the servers, which are connected to cameras and think about how many cameras are deployed today, probably a billion. And a lot of the video data can now be used for public safety purposes, and we basically go out and talk to large companies. We talked to governments. We talked to cities along with Sisko to go even open their eyes to what is possible today. >> Right? Because of that data is dark for so long, they don't know what they don't know. >> While most cases, what happens is you record four days of video and until something happens, nobody goes back and takes a look at it. But now we have the ability to look at the real time and cities and government's desire that very much so, >> sir example, that's such a relevant topic. I mean, they know. There's also the issue of privacy. But to your point about not just a smart city but a smart, safe city. I like that. I think it's absolutely imperative. How do you have this conversations with cities with governments about All right, this is what we want. Do we want to actually apply machine learning? So the machines are taught What that line is with privacy with those boundaries are so that a person, I'd say a lay person not in technology. Maybe is a city government official who doesn't understand the technology or need Teo will go. I get it. >> Yes. So our conversations are really about what we call you cases. So think of enterprise. A good use case would be. In fact, we work with Cisco on developing use case. You know, you always badge in into an enterprise. You have your badge, you walk in. But you also have some cases. People follow you, following you in what stops you from following me into a building. And usually people are too polite to say no, you can walk in, but we've >> all had the video training or read the manual. We know we're not >> we're not supposed to bite, but >> then you're like, I >> don't just cultural, exactly. We just can't you know that. So now we have the ability. So we trained a in a network to say, Look, if Marty's badging in, only he's allowed to walk in. And if there's a second person walks in, I want to take put Little Red Square on that face and inform security that we have had more than one person walking. So these are some of the ways. So we talk about use cases. This is one use case crowd behavior. Analytics is another use case. You know, people were walking in the backpack, dropping it. Other use case would be something like Bar to Bart loses millions of dollars year because people jumped the turnstiles and Bart didn't really have a good way of of monitoring, measuring the losses until we put a camera and captured the number of people that were jumping. The turnstiles are going in through the handicap access, okay? They were losing ten times the dollar value of what we had thought. Wow. So this is how we start the conversation with use cases, you know? And what would you like to do? Being able to count the number of cars in intersection begin with counter number of pedestrians, so you could do traffic management better. That's the language we would use with cities and governments. And then we go deeper as you go through the implementation process. >> Well, that makes perfect sense going in the use case route, because you can clearly see in that example that you mentioned with Bart a massive business outcome and an opportunity to regain a tremendous amount of resource is that they could redeploy for whether it it's new trains, new trucks, etcetera than them, not realizing we're losing how much money. I think anybody when you could put the useless in that context of this is what you can expect as an outcome. They get it >> Absolutely. That's the really the only way to start the conversation than starting from bits and bytes. And this is the This is usually the case across industries. If you think about retail, for example, you know you go to a safe way to start talking about GPS and servers. That's not the great way to start, but they do have issues with shoplifting, for example. So how do you know a person is walking in, you know, through the checkout. And they have one item. Then there's a small item right here and they walk out with this. How do you monitor that? So now you can do that with the right kind of cameras that can capture. Look there Two items, not one. How do you know where shop are stopping Which aisle is the most popular? I'Ll How do you know that? Well, now you can have cameras would say, Look, we have red zones and Green Zone so you could do those kinds of things with modern ways of doing. I >> so interesting because it's so. I mean, the examples that you gave are so disparate, but yet they make so much sense was how how you're describing it rather than going into, you know, a grocery store in talking about GPS, which they might fall over with their eyes. Doing this >> right. >> You're actually putting in the context of a real world problem they've been experiencing since the beginning of time. Don't you understand? Only goodness and this is how we can use technology. It's the safe way becomes a technology company. They don't know it. What actually started packing their bottom line. >> That's right, And so even now, you know. So I have to take that and you extend that into How do you go to market? And it's something you wanted Teo Touch on. How do you go to market with Cisco's? How does ingredients is? Could do it together, right? So think of Cisco's sales teams who are talking to all these customers every day where their retailers, financial services, federal government, health care, you name it. So what we've done is we basically sort of taking all these industries and created the top three or four use cases we know are relevant to that industry, either for safety or for saving money's. For variety of their operational reason, we have narrowed it down to three or four five use cases and each of those target industries. So what we do now with Cisco teams that we would bring them into our facility or go to them and really talkto all those use cases and train them on Hey, look, this is what we do jointly, and that makes the conversation much easier. Then they will go and present to the customer and what's the customer gets an idea far this all possible. Now that starts a deeper level technology and server and GPU engagement. So this is one way we go up and talk to different customers. What's the school's >> second? About a bit. Marcus. Cisco is so enormous, they have a billion different. I'm slightly exaggerating products with but a lot of different technologies that form many different solutions. So I imagine your Cisco expertise over many years of working with Cisco's a partner for other companies. How do you once you get to that deeper level conversation, how do you bring this different groups within Cisco together? So that that solution conversation is one that really aligns to that use case and the customer doesn't get it? >> Yeah, that's a difficult question to answer. That's like, you know your work. It's just cause a large company. But I think I also think they're also very cells driven, and that's what drives the different groups to come together. In fact, some people called me the Connector because I've been working. Cisco's so long. I know people and definite I know people in sales. I know people in the server. BU, in fact, if you think about the The platform was talking about the i r eleven o one with the jets and GPU that came as a result. I was talking to the i o t bu result talking to Dev net our situation the definite he said. You know what? This is cool are gonna do this. Then we take that to the IOC Guys is Oh, this is cool. We can take that. Put it in this platform, and then I'm next. Actually, next week I'm talking to a sale. Seaman Cisco. They cover utilities. And this platform was profit for utilities. Even think about fire monitoring in a forest. How do you do, boy thousand? The people to just watch what happens. We can take a platform like that now and really deploy it in hundreds of places which could monitor fires or the starting off a fire. But yes, bringing them together. It is no easy task. It's fun >> where you are smiling. I like that. Marty the connector. Jane, thank you >> so much for >> joining me on the kid this afternoon. Fun conversation. I enjoyed it. >> Ofcourse. Thank you. Likewise. Thank >> you, Lisa Martin for the Cube. you're watching us live, Francisco Definite. Create twenty nineteen. This is the end of day one. Stick around, John. Failure on I will be back tomorrow to cover day too. Thanks for watching.