(upbeat music) >> Hey, everyone, welcome back to Las Vegas, "theCube" is on our fourth day of covering AWS re:Invent, live from the Venetian Expo Center. This week has been amazing. We've created a ton of content, as you know, 'cause you've been watching. But, there's been north of 55,000 people here, hundreds of thousands online. We've had amazing conversations across the AWS ecosystem. Lisa Martin, Paul Gillan. Paul, what's your, kind of, take on day four of the conference? It's still highly packed. >> Oh, there's lots of people here. (laughs) >> Yep. Unusual for the final day of a conference. I think Werner Vogels, if I'm pronouncing it right kicked things off today when he talked about asymmetry and how the world is, you know, asymmetric. We build symmetric software, because it's convenient to do so, but asymmetric software actually scales and evolves much better. And I think that that was a conversation starter for a lot of what people are talking about here today, which is how the cloud changes the way we think about building software. >> Absolutely does. >> Our next guest, Holger Mueller, that's one of his key areas of focus. And Holger, welcome, thanks for joining us on the "theCube". >> Thanks for having me. >> What did you take away from the keynote this morning? >> Well, how do you feel on the final day of the marathon, right? We're like 23, 24 miles. Hit the ball yesterday, right? >> We are going strong Holger. And, of course, >> Yeah. >> you guys, we can either talk about business transformation with cloud or the World Cup. >> Or we can do both. >> The World Cup, hands down. World Cup. (Lisa laughs) Germany's out, I'm unbiased now. They just got eliminated. >> Spain is out now. >> What will the U.S. do against Netherlands tomorrow? >> They're going to win. What's your forecast? U.S. will win? >> They're going to win 2 to 1. >> What do you say, 2:1? >> I'm optimistic, but realistic. >> 3? >> I think Netherlands. >> Netherlands will win? >> 2 to nothing. >> Okay, I'll vote for the U.S.. >> Okay, okay >> 3:1 for the U.S.. >> Be optimistic. >> Root for the U.S.. >> Okay, I like that. >> Hope for the best wherever you work. >> Tomorrow you'll see how much soccer experts we are. >> If your prediction was right. (laughs) >> (laughs) Ja, ja. Or yours was right, right, so. Cool, no, but the event, I think the event is great to have 50,000 people. Biggest event of the year again, right? Not yet the 70,000 we had in 2019. But it's great to have the energy. I've never seen the show floor going all the way down like this, right? >> I haven't either. >> I've never seen that. I think it's a record. Often vendors get the space here and they have the keynote area, and the entertainment area, >> Yeah. >> and the food area, and then there's an exposition, right? This is packed. >> It's packed. >> Maybe it'll pay off. >> You don't see the big empty booths that you often see. >> Oh no. >> Exactly, exactly. You know, the white spaces and so on. >> No. >> Right. >> Which is a good thing. >> There's lots of energy, which is great. And today's, of course, the developer day, like you said before, right now Vogels' a rockstar in the developer community, right. Revered visionary on what has been built, right? And he's becoming a little professorial is my feeling, right. He had these moments before too, when it was justifying how AWS moved off the Oracle database about the importance of data warehouses and structures and why DynamoDB is better and so on. But, he had a large part of this too, and this coming right across the keynotes, right? Adam Selipsky talking about Antarctica, right? Scott against almonds and what went wrong. He didn't tell us, by the way, which often the tech winners forget. Scott banked on technology. He had motorized sleds, which failed after three miles. So, that's not the story to tell the technology. Let everything down. Everybody went back to ponies and horses and dogs. >> Maybe goes back to these asynchronous behavior. >> Yeah. >> The way of nature. >> And, yesterday, Swami talking about the bridges, right? The root bridges, right? >> Right. >> So, how could Werner pick up with his video at the beginning. >> Yeah. >> And then talk about space and other things? So I think it's important to educate about event-based architecture, right? And we see this massive transformation. Modern software has to be event based, right? Because, that's how things work and we didn't think like this before. I see this massive transformation in my other research area in other platforms about the HR space, where payrolls are being rebuilt completely. And payroll used to be one of the three peaks of ERP, right? You would size your ERP machine before the cloud to financial close, to run the payroll, and to do an MRP manufacturing run if you're manufacturing. God forbid you run those three at the same time. Your machine wouldn't be able to do that, right? So it was like start the engine, start the boosters, we are running payroll. And now the modern payroll designs like you see from ADP or from Ceridian, they're taking every payroll relevant event. You check in time wise, right? You go overtime, you take a day of vacation and right away they trigger and run the payroll, so it's up to date for you, up to date for you, which, in this economy, is super important, because we have more gig workers, we have more contractors, we have employees who are leaving suddenly, right? The great resignation, which is happening. So, from that perspective, it's the modern way of building software. So it's great to see Werner showing that. The dirty little secrets though is that is more efficient software for the cloud platform vendor too. Takes less resources, gets less committed things, so it's a much more scalable architecture. You can move the events, you can work asynchronously much better. And the biggest showcase, right? What's the biggest transactional showcase for an eventually consistent asynchronous transactional application? I know it's a mouthful, but we at Amazon, AWS, Amazon, right? You buy something on Amazon they tell you it's going to come tomorrow. >> Yep. >> They don't know it's going to come tomorrow by that time, because it's not transactionally consistent, right? We're just making every ERP vendor, who lives in transactional work, having nightmares of course, (Lisa laughs) but for them it's like, yes we have the delivery to promise, a promise to do that, right? But they come back to you and say, "Sorry, we couldn't make it, delivery didn't work and so on. It's going to be a new date. We are out of the product.", right? So these kind of event base asynchronous things are more and more what's going to scale around the world. It's going to be efficient for everybody, it's going to be better customer experience, better employee experience, ultimately better user experience, it's going to be better for the enterprise to build, but we have to learn to build it. So big announcement was to build our environment to build better eventful applications from today. >> Talk about... This is the first re:Invent... Well, actually, I'm sorry, it's the second re:Invent under Adam Selipsky. >> Right. Adam Selipsky, yep. >> But his first year. >> Right >> We're hearing a lot of momentum. What's your takeaway with what he delivered with the direction Amazon is going, their vision? >> Ja, I think compared to the Jassy times, right, we didn't see the hockey stick slide, right? With a number of innovations and releases. That was done in 2019 too, right? So I think it's a more pedestrian pace, which, ultimately, is good for everybody, because it means that when software vendors go slower, they do less width, but more depth. >> Yeah. >> And depth is what customers need. So Amazon's building more on the depth side, which is good news. I also think, and that's not official, right, but Adam Selipsky came from Tableau, right? >> Yeah. So he is a BI analytics guy. So it's no surprise we have three data lake offerings, right? Security data lake, we have a healthcare data lake and we have a supply chain data lake, right? Where all, again, the epigonos mentioned them I was like, "Oh, my god, Amazon's coming to supply chain.", but it's actually data lakes, which is an interesting part. But, I think it's not a surprise that someone who comes heavily out of the analytics BI world, it's off ringside, if I was pitching internally to him maybe I'd do something which he's is familiar with and I think that's what we see in the major announcement of his keynote on Tuesday. >> I mean, speaking of analytics, one of the big announcements early on was Amazon is trying to bridge the gap between Aurora. >> Yep. >> And Redshift. >> Right. >> And setting up for continuous pipelines, continuous integration. >> Right. >> Seems to be a trend that is common to all database players. I mean, Oracle is doing the same thing. SAP is doing the same thing. MariaDB. Do you see the distinction between transactional and analytical databases going away? >> It's coming together, right? Certainly coming together, from that perspective, but there's a fundamental different starting point, right? And with the big idea part, right? The universal database, which does everything for you in one system, whereas the suite of specialized databases, right? Oracle is in the classic Oracle database in the universal database camp. On the other side you have Amazon, which built a database. This is one of the first few Amazon re:Invents. It's my 10th where there was no new database announced. Right? >> No. >> So it was always add another one specially- >> I think they have enough. >> It's a great approach. They have enough, right? So it's a great approach to build something quick, which Amazon is all about. It's not so great when customers want to leverage things. And, ultimately, which I think with Selipsky, AWS is waking up to the enterprise saying, "I have all this different database and what is in them matters to me." >> Yeah. >> "So how can I get this better?" So no surprise between the two most popular database, Aurora and RDS. They're bring together the data with some out of the box parts. I think it's kind of, like, silly when Swami's saying, "Hey, no ETL.". (chuckles) Right? >> Yeah. >> There shouldn't be an ETL from the same vendor, right? There should be data pipes from that perspective anyway. So it looks like, on the overall value proposition database side, AWS is moving closer to the universal database on the Oracle side, right? Because, if you lift, of course, the universal database, under the hood, you see, well, there's different database there, different part there, you do something there, you have to configure stuff, which is also the case but it's one part of it, right, so. >> With that shift, talk about the value that's going to be in it for customers regardless of industry. >> Well, the value for customers is great, because when software vendors, or platform vendors, go in depth, you get more functionality, you get more maturity you get easier ways of setting up the whole things. You get ways of maintaining things. And you, ultimately, get lower TCO to build them, which is super important for enterprise. Because, here, this is the developer cloud, right? Developers love AWS. Developers are scarce, expensive. Might not be want to work for you, right? So developer velocity getting more done with same amount of developers, getting less done, less developers getting more done, is super crucial, super important. So this is all good news for enterprise banking on AWS and then providing them more efficiency, more automation, out of the box. >> Some of your customer conversations this week, talk to us about some of the feedback. What's the common denominator amongst customers right now? >> Customers are excited. First of all, like, first event, again in person, large, right? >> Yeah. >> People can travel, people meet each other, meet in person. They have a good handle around the complexity, which used to be a huge challenge in the past, because people say, "Do I do this?" I know so many CXOs saying, "Yeah, I want to build, say, something in IoT with AWS. The first reference built it like this, the next reference built it completely different. The third one built it completely different again. So now I'm doubting if my team has the skills to build things successfully, because will they be smart enough, like your teams, because there's no repetitiveness and that repetitiveness is going to be very important for AWS to come up with some higher packaging and version numbers.", right? But customers like that message. They like that things are working better together. They're not missing the big announcement, right? One of the traditional things of AWS would be, and they made it even proud, as a system, Jassy was saying, "If we look at the IT spend and we see something which is, like, high margin for us and not served well and we announced something there, right?" So Quick Start, Workspaces, where all liaisons where AWS went after traditional IT spend and had an offering. We haven't had this in 2019, we don't have them in 2020. Last year and didn't have it now. So something is changing on the AWS side. It's a little bit too early to figure out what, but they're not chewing off as many big things as they used in the past. >> Right. >> Yep. >> Did you get the sense that... Keith Townsend, from "The CTO Advisor", was on earlier. >> Yep. >> And he said he's been to many re:Invents, as you have, and he said that he got the sense that this is Amazon's chance to do a victory lap, as he called it. That this is a way for Amazon to reinforce the leadership cloud. >> Ja. >> And really, kind of, establish that nobody can come close to them, nobody can compete with them. >> You don't think that- >> I don't think that's at all... I mean, love Keith, he's a great guy, but I don't think that's the mindset at all, right? So, I mean, Jassy was always saying, "It's still the morning of the day in the cloud.", right? They're far away from being done. They're obsessed over being right. They do more work with the analysts. We think we got something right. And I like the passion, from that perspective. So I think Amazon's far from being complacent and the area, which is the biggest bit, right, the biggest. The only thing where Amazon truly has floundered, always floundered, is the AI space, right? So, 2018, Werner Vogels was doing more technical stuff that "Oh, this is all about linear regression.", right? And Amazon didn't start to put algorithms on silicon, right? And they have a three four trail and they didn't announce anything new here, behind Google who's been doing this for much, much longer than TPU platform, so. >> But they have now. >> They're keen aware. >> Yep. >> They now have three, or they own two of their own hardware platforms for AI. >> Right. >> They support the Intel platform. They seem to be catching up in that area. >> It's very hard to catch up on hardware, right? Because, there's release cycles, right? And just the volume that, just talking about the largest models that we have right now, to do with the language models, and Google is just doing a side note of saying, "Oh, we supported 50 less or 30 less, not little spoken languages, which I've never even heard of, because they're under banked and under supported and here's the language model, right? And I think it's all about little bit the organizational DNA of a company. I'm a strong believer in that. And, you have to remember AWS comes from the retail side, right? >> Yeah. >> Their roll out of data centers follows their retail strategy. Open secret, right? But, the same thing as the scale of the AI is very very different than if you take a look over at Google where it makes sense of the internet, right? The scale right away >> Right. >> is a solution, which is a good solution for some of the DNA of AWS. Also, Microsoft Azure is good. There has no chance to even get off the ship of that at Google, right? And these leaders with Google and it's not getting smaller, right? We didn't hear anything. I mean so much focused on data. Why do they focus so much on data? Because, data is the first step for AI. If AWS was doing a victory lap, data would've been done. They would own data, right? They would have a competitor to BigQuery Omni from the Google side to get data from the different clouds. There's crickets on that topic, right? So I think they know that they're catching up on the AI side, but it's really, really hard. It's not like in software where you can't acquire someone they could acquire in video. >> Not at Core Donovan. >> Might play a game, but that's not a good idea, right? So you can't, there's no shortcuts on the hardware side. As much as I'm a software guy and love software and don't like hardware, it's always a pain, right? There's no shortcuts there and there's nothing, which I think, has a new Artanium instance, of course, certainly, but they're not catching up. The distance is the same, yep. >> One of the things is funny, one of our guests, I think it was Tuesday, it was, it was right after Adam's keynote. >> Sure. >> Said that Adam Selipsky stood up on stage and talked about data for 52 minutes. >> Yeah. Right. >> It was timed, 52 minutes. >> Right. >> Huge emphasis on that. One of the things that Adam said to John Furrier when they were able to sit down >> Yeah >> a week or so ago at an event preview, was that CIOs and CEOs are not coming to Adam to talk about technology. They want to talk about transformation. They want to talk about business transformation. >> Sure, yes, yes. >> Talk to me in our last couple of minutes about what CEOs and CIOs are coming to you saying, "Holger, help us figure this out. We have to transform the business." >> Right. So we advise, I'm going quote our friends at Gartner, once the type A company. So we'll use technology aggressively, right? So take everything in the audience with a grain of salt, followers are the laggards, and so on. So for them, it's really the cusp of doing AI, right? Getting that data together. It has to be in the cloud. We live in the air of infinite computing. The cloud makes computing infinite, both from a storage, from a compute perspective, from an AI perspective, and then define new business models and create new best practices on top of that. Because, in the past, everything was fine out on premise, right? We talked about the (indistinct) size. Now in the cloud, it's just the business model to say, "Do I want to have a little more AI? Do I want a to run a little more? Will it give me the insight in the business?". So, that's the transformation that is happening, really. So, bringing your data together, this live conversation data, but not for bringing the data together. There's often the big win for the business for the first time to see the data. AWS is banking on that. The supply chain product, as an example. So many disparate systems, bring them them together. Big win for the business. But, the win for the business, ultimately, is when you change the paradigm from the user showing up to do something, to software doing stuff for us, right? >> Right. >> We have too much in this operator paradigm. If the user doesn't show up, doesn't find the click, doesn't find where to go, nothing happens. It can't be done in the 21st century, right? Software has to look over your shoulder. >> Good point. >> Understand one for you, autonomous self-driving systems. That's what CXOs, who're future looking, will be talked to come to AWS and all the other cloud vendors. >> Got it, last question for you. We're making a sizzle reel on Instagram. >> Yeah. >> If you had, like, a phrase, like, or a 30 second pitch that would describe re:Invent 2022 in the direction the company's going. What would that elevator pitch say? >> 30 second pitch? >> Yeah. >> All right, just timing. AWS is doing well. It's providing more depth, less breadth. Making things work together. It's catching up in some areas, has some interesting offerings, like the healthcare offering, the security data lake offering, which might change some things in the industry. It's staying the course and it's going strong. >> Ah, beautifully said, Holger. Thank you so much for joining Paul and me. >> Might have been too short. I don't know. (laughs) >> About 10 seconds left over. >> It was perfect, absolutely perfect. >> Thanks for having me. >> Perfect sizzle reel. >> Appreciate it. >> We appreciate your insights, what you're seeing this week, and the direction the company is going. We can't wait to see what happens in the next year. And, yeah. >> Thanks for having me. >> And of course, we've been on so many times. We know we're going to have you back. (laughs) >> Looking forward to it, thank you. >> All right, for Holger Mueller and Paul Gillan, I'm Lisa Martin. You're watching "theCube", the leader in live enterprise and emerging tech coverage. (upbeat music)

(upbeat music) >> Hello, beautiful cloud community, and welcome back to AWS reInvent. It is day four here in fabulous Las Vegas, Nevada. My voice can feel it, clearly. I'm Savannah Peterson with my co-host Paul Gillin. Paul, how you doing? >> Doing fine, Savannah. >> Are your feet about where my voice is? >> Well, getting little rest here as we have back to back segments. >> Yeah, yeah, we'll keep you off those. Very excited about this next segment. We get to have a chat with one of our very favorite analysts, Keith Townsend. Welcome back to theCUBE. >> Savannah Page. I'm going to use your south names, Savannah Page. Thank you for having me, Paul. Good to see you again. It's been been too long since CubeCon Valencia. >> Valencia. >> Valencia. >> Well at that beautiful lisp, love that. Keith, how's the show been for you so far? >> It has been great. I tweeted it a couple of days ago. Amazon reInvent is back. >> Savannah: Whoo! Love that. >> 50, 60 thousand people, you know? After 40 thousand, I stop countin'. It has been an amazing show. I don't know if it's just the assignment of returning, but easily the best reInvent of the four that I've attended. >> Savannah: Love that. >> Paul: I love that we have you here because, you know, we tend to get anchored to these desks, and we don't really get a sense of what's going on out there. You've been spending the last four days traversing the floor and talking to people. What are you hearing? Are there any mega themes that are emerging? >> Keith: So, a couple of mega themes is... We were in the Allen session with Adam, and Adam bought up the idea of hybrid cloud. At the 2019 show, that would be unheard of. There's only one cloud, and that's the AWS cloud, when you're at the Amazon show. Booths, folks, I was at the VMware booth and there's a hybrid cloud sign session. People are talking about multicloud. Yes, we're at the AWS show, but the reality that most customers' environments are complex. Adam mentioned that it's hybrid today and more than likely to be hybrid in the future in Amazon, and the ecosystem has adjusted to that reality. >> Paul: Now, is that because they want sell more outposts? >> You know, outpost is definitely a part of the story, but it's a tactile realization that outposts alone won't get it. So, you know, from Todd Consulting, to Capgemini, to PWC, to many of the integrations on the show floor... I even saw company that's doing HP-UX in the cloud or on-prem. The reality is these, well, we've deemed these legacy systems aren't going anywhere. AWS announced the mainframe service last year for converting mainframe code into cloud workloads, and it's just not taking on the, I think, the way that the Amazon would like, and that's a reality that is too complex for all of it to run in the cloud. >> Paul: So it sounds like the strategy is to envelop and consume then if you have mainframe conversion services and HP-UX in the cloud, I mean, you're talking about serious legacy stuff there. >> Keith: You're talking about serious legacy stuff. They haven't de-emphasized their relationship with VMware. You know, hybrid is not a place, it is a operating model. So VMware cloud on AWS allows you to do both models concurrently if you have those applications that need layer two. You have these workloads that just don't... SAP just doesn't... Sorry, AWS, SAP in the cloud and EC2 just doesn't make financial sense. It's a reality. It's accepting of that and meeting customers where they're at. >> And all the collaboration, I mean, you've mentioned so many companies in that answer, and I think it's very interesting to see how much we're all going to have to work together to make the cloud its own operating system. Cloud as an OS came up on our last conversation here and I think it's absolutely fascinating. >> Keith: Yeah, cloud is the OS I think is a thing. This idea that I'm going to use the cloud as my base layer of abstraction. I've talked to a really interesting startup... Well actually it's a open source project cross plane of where they're taking that cloud model and now I can put my VMware vsphere, my AWS, GCP, et cetera, behind that and use that operating model to manage my overall infrastructure. So, the maturity of the market has fascinated me over the past year, year and a half. >> It really feels like we're at a new inflection point. I totally agree. I want to talk about something completely different. >> Keith: Okay. >> Because I know that we both did this challenge. So one of the things that's really inspiring quite frankly about being here at AWS reInvent, and I know you all at home don't have an opportunity to walk the floor and get the experience and get as many steps as Paul gets in, but there's a real emphasis on giving back. This community cares about giving back and AWS is doing a variety of different activations to donate to a variety of different charities. And there's a DJ booth. I've been joking. It kind of feels like you're arriving at a rave when you get to reInvent. And right next to that, there is a hydrate and help station with these reusable water bottles. This is actually firm. It's not one of those plastic ones that's going to end up in the recycled bin or the landfill. And every single time that you fill up your water bottle, AWS will donate $3 to help women in Kenya get access to water. One of the things that I found really fascinating about the activation is women in sub-Saharan Africa spend 16 million hours carrying water a day, which is a wild concept to think about, and water is heavy. Keith, my man, I know that you did the activation. They had you carrying two 20 pound jugs of water. >> Keith: For about 15 feet. It's not the... >> (laughs) >> 20 pound jugs of water, 20 gallons, whatever the amount is. It was extremely heavy. I'm a fairly sizeable guy. Six four, six five. >> You're in good shape, yeah. >> Keith: Couple of a hundred pounds. >> Yeah. >> Keith: And I could not imagine spending that many hours simply getting fresh water. We take it for granted. Every time I run the water in the sink, my family gets on me because I get on them when they leave the sink water. It's like my dad's left the light on. If you leave the water on in my house, you are going to hear it from me because, you know, things like this tickle in my mind like, wow, people walk that far. >> Savannah: That's your whole day. >> Just water, and that's probably not even enough water for the day. >> Paul: Yeah. We think of that as being, like, an 18th century phenomenon, but it's very much today in parts of Sub-Saharan Africa. >> I know, and we're so privileged. For me, it was just, we work in technology. Everyone here is pretty blessed, and to do that activation really got my head in the right space to think, wow I'm so lucky. The team here, the fabulous production team, can go refill my water bottle. I mean, so simple. They've also got a fitness activation going on. You can jump on a bike, a treadmill, and if you work out for five minutes, they donate $5 to Fred Hutch up in Seattle. And that was nice. I did a little cross-training in between segments yesterday and I just, I really love seeing that emphasis. None of this matters if we're not taking care of community. >> Yeah, I'm going to go out and google Fred Hutch, and just donate the five bucks. 'Cause I'm not, I'm not. >> (laughs) >> I'll run forever, but I'm not getting on a bike. >> This from a guy who did 100 5Ks in a row last year. >> Yeah. I did 100 5Ks in a row, and I'm not doing five minutes on a bike. That's it. That's crazy, right? >> I mean there is a treadmill And they have the little hands workout thing too if you want. >> About five minutes though. >> Savannah: I know. >> Like five minutes is way longer than what you think it is. >> I mean, it's true. I was up there in a dress in sequence. Hopefully, I didn't scar any anyone on the show floor yesterday. It's still toss up. >> I'm going to take us back to back. >> Take us back Paul. >> Back to what we were talking about. I want to know what you're hearing. So we've had a lot of people on this show, a lot of vendors on the show who have said AWS is our most important cloud partner, which would imply that AWS's lead is solidifying its lead and pulling away from the pack as the number one. Do you hear that as well? Or is that lip service? >> Keith: So I always think about AWS reInvent as the Amazon victory lap. This is where they come and just thumb their noses at all the other cloud providers and just show how far ahead they're are. Werner Vogels, CTO at Amazon's keynotes, so I hadn't watched it yet, but at that keynote, this is where they literally take the victory lap and say that we're going to expose what we did four or five years ago on stage, and what we did four or five years ago is ahead of every cloud provider with maybe the exception of GCP and they're maybe three years behind. So customers are overwhelmingly choosing Amazon for these reasons. Don't get me wrong, Corey Quinn, Gardner folks, really went at Adam yesterday about Amazon had three majors outages in December last year. AWS has way too many services that are disconnected, but from the pure capability, I talked to a born in the cloud data protection company who could repatriate their data protection and storage on-prem private data center, save money. Instead, they double down on Amazon. They're using, they modernize their application and they're reduced their cost by 60 to 70%. >> Massive. >> This is massive. AWS is keeping up with customers no matter where they're at on the spectrum. >> Savannah: I love that you use the term victory lap. We've had a lot of folks from AWS here up on the show this week, and a couple of them have said they live for this. I mean, and it's got to be pretty cool. You've got 70 thousand plus people obsessed with your product and so many different partners doing so many different things from the edge to hospital to the largest companies on earth to the Israeli Ministry of Defense we were just talking about earlier, so everybody needs the cloud. I feel like that's where we're at. >> Keith: Yeah, and the next step, I think the next level opportunity for AWS is to get to that analyst or that citizen developer, being able to enable the end user to use a lambda, use these data services to create new applications, and the meanwhile, there's folks on the show floor filling that gap that enable develop... the piece of owner, the piece of parlor owner, to create a web portal that compares his prices and solutions to other vendors in his area and adjust dynamically. You go into a restaurant now and there is no price menu. There's a QR code that Amazon is powering much of that dynamic relationship between the restaurateur, the customer, and even the menu and availability. It's just a wonderful time. >> I always ask for the print menu. I'm sorry. >> Yeah. You want the printed menu. >> Look down, my phone doesn't work. >> Gimme something I could shine my light on. >> I know you didn't have have a chance to look at Vogel's keynote yet, but I mean you mentioned citizen developer. One of the things they announced this morning was essentially a low code lambda interface. So you can plug, take your lamb dysfunctions and do drag and drop a connection between them. So they are going after that market. >> Keith: So I guess I'll take my victory lap because that was my prediction. That's where Amazon's next... >> Well done, Keith. >> Because Lambda is that thing when you look at what server list was and the name of the concept of being, not having to have to worry about servers in your application development, the logical next step, I won't take too much of a leap. That logical first step is, well, code less code. This is something that Kelsey Hightower has talked about a lot. Low code, no code, the ability to empower people without having these artificial barriers, learning how to code in a different language. This is the time where I can go to Valencia, it's pronounced, where I can go to Valencia and not speak Spanish and just have my phone. Why can't we do, at business value, for people who have amazing ideas and enable those amazing ideas before I have to stick a developer in between them and the system. >> Paul: Low-code market is growing 35% a year. It's not surprising, given the potential that's out there. >> And as a non-technical person, who works in technology, I've been waiting for this moment. So keep predicting this kind of thing, Keith. 'Cause hopefully it'll keep happening. Keith, I'm going to give you the challenge we've been giving all of our guests this week. >> Keith: Okay. >> And I know you're going to absolutely crush this. So we are looking for your 32nd Instagram real, sizzle hot take, biggest takeaway from this year's show. >> So 32nd Instagram, I'll even put it on TikTok. >> Savannah: Heck yeah. >> Hybrid cloud, hybrid infrastructure. This is way bigger than Amazon. Whether we're talking about Amazon, AWS, I mean AWS's solutions, Google Cloud, Azure, OCI, on-prem. Customers want it all. They want a way to manage it all, and they need the skill and tools to enable their not-so-growing work force to do it. That is, that's AWS reInvent 2019 to 2022. >> Absolutely nailed it. Keith Townsend, it is always such a joy to have you here on theCUBE. Thank you for joining us >> Savannah Page. Great to have you. Paul, you too. You're always a great co-host. >> (laughs) We co-hosted for three days. >> We've got a lot of love for each other here. And we have even more love for all of you tuning into our fabulous livestream from AWS reInvent Las Vegas, Nevada, with Paul Gillin. I'm Savannah Peterson. You're watching theCUBE, the leader in high tech coverage. (upbeat music)

>>Okay, welcome back everyone. Day three of the cube coverage here at VMware VMware Explorer, not world 12 years. The Cube's been covering VMware is end user conference this year. It's called explore previously world. We got two great guests, friends of the cube friend, cube, alumni and cloud rod, Keith Townson, principal CTO advisor, air streaming his way into world this year in a big way. Congratulations. And course James Erhard principal technology, a at tan zoo cloud ARA. He's been in cloud game for a long time. We've known each other for a long, long time, even before cloud was cloud. So great to see you guys. Thanks for coming on. >>Ah, it's a pleasure, always happy to >>Be here. So day threes are kind of like riff. I'll throw out super cloud. You guys will, will trash it. We'll debate. It'll be controversial and say this damage done by the over rotation of developer experience. We'll defend Tansu, but really the end of the game is, is that guys, we have been on the cloud thing for a long time. We're we're totally into it. And we've been saying infrastructure is code as the end state. We want to get there. Right? DevOps and infrastructure is code has always been the, the, the underlying fire burning in, in all the innovation, but it's now getting legitimately enterprised it's adopted in, in, in large scale, Amazon web services. We saw that rise. It feels we're in another level right now. And I think we're looking at this new wave coming. And I gotta say, you know, the Broadcom thing has put like an electric shock syndrome into this ecosystem cuz they don't know what's gonna happen next. So as a result, everyone's kind of gotta spring in their step a little, whether it's nervous, energy or excitement around something happening, it's all cloud native. So, you know, as VMware's got such a great investment in cloud native, but yet multi cloud's the story. Right? So, so messaging's okay. So what's happening here? Like guys let's, let's break it down. You're on the show floor of the Airstream you're on the inside, but with the seeing the industry, James will start with you what's happening this year with cloud next level and VMware's future. >>Yeah, I think the big thing that is happening is that we are beginning to see the true separation of capacity delivery from capacity consumption in computing. And what I mean by that is the, the abstractions that sort of bled between the idea of a server and the idea of an application have sort of become separated much better. And I think Kubernetes is, is the strong evidence of that. But also all of the public cloud APIs are strong evidence of that. And VMware's APIs, frankly, before that we're strong evidence of that. So I think what's, what's starting to happen now then is, is developers have really kind of pulled very far away from, from anything other than saying, I need compute, I need network. I need storage. And so now you're seeing the technologies that say, well, we've figured out how to do that at a team level, like one team can automate an application to an environment, but another team will, you know, other teams, if I have hundreds of teams or, or thousands of applications, how do I handle that? And that's what the excitement I think is right >>Now. I mean the, the developer we talking, we're going on camera before you came on camera Keith around, you know, your contr statement around the developer experience. Now we, I mean, I believe that the cloud native development environment is doing extremely well right now. You talk to, you know, look around the industry. It's, it's at an all time high and relative to euphoria, you know, sit on the beach with sunglasses. You couldn't be better if you were a developer open source, booming, everything's driving to their doorstep, self service. They're at the center of the security conversation, which shift left. Yeah. There's some things there, but it's, it's a good time. If you're a developer now is VMware gonna be changing that and, and you know, are they gonna meet the developers where they are? Are they gonna try to bring something new? So these are conversations that are super important. Now VMware has a great install base and there's developers there too. So I think I see their point, but, but you have a take on this, Keith, what's your, what's your position on this? How do the developer experience core and tangential played? >>Yeah, we're I think we're doing a disservice to the industry and I think it's hurting and, or D I think I'm gonna stand by my statement. It's damaging the in industry to, to an extent VMware >>What's damaging to the >>Industry. The focusing over focusing on developer experience developer experience is super important, but we're focusing on developer experience the, the detriment of infrastructure, the infrastructure to deliver that developer experience across the industry isn't there. So we're asking VMware, who's a infrastructure company at core to meet the developer where the developer, the developer is at today with an infrastructure that's not ready to deliver on the promise. So when we're, when NetApp is coming out with cool innovations, like adding block storage to VMC on AWS, we collectively yawn. It's an amazing innovation, but we're focused on, well, what does that mean for the developer down the road? >>It should mean nothing because if it's infrastructure's code, it should just work, right. >>It should just work, but it doesn't. Okay. >>I see the damage there. The, >>The, when you're thinking, oh, well I should be able to just simply provide Dr. Service for my on-prem service to this new block level stores, because I can do that in a enterprise today. Non-cloud, we're not there. We're not at a point where we can just write code infrastructure code and that happens. VMware needs the latitude to do that work while doing stuff like innovating on tap and we're, you know, and then I think we, we, when buyers look at what we say, and we, we say VMware, isn't meeting developers where they're at, but they're doing the hard work of normalizing across clouds. I got off a conversation with a multi-cloud customer, John, the, the, the, the unicorn we all talk about. And at the end I tried to wrap up and he said, no, no, no way. I gotta talk about vRealize. Whoa, you're the first customer I heard here talk about vRealize and, and the importance of normalizing that underlay. And we just don't give these companies in this space, the right >>Latitude. So I'm trying to, I'm trying to rock a little bit what you're saying. So from my standpoint, generically speaking, okay. If I'm a, if the developers are key to the, to the cloud native role, which I, I would say they are, then if I'm a developer and I want, and I want infrastructure as code, I'm not under the hood, I'm not getting the weeds in which some lot people love to do. I wanna just make things work. So meet me where I'm at, which means self-service, I don't care about locking someone else should figure that problem out, but I'm gonna just accelerate my velocity, making sure it's secure. And I'm moving on being creative and doing my thing, building apps. Okay. That's the kind of the generic, generic statement. So what has to happen in your mind to >>Get there? Yeah. Someone, someone has to do the dirty work of making the world move as 400, still propagate the data center. They're still H P X running SAP, E there's still, you know, 75% of the world's transactions happen through SAP. And most of that happens on bare metal. Someone needs to do the plumbing to give that infrastructure's cold world. Yeah. Someone needs to say, okay, when I want to do Dr. Between my on premises edge solution and the public cloud, someone needs to make it invisible to the Kubernetes, the, the Kubernetes consuming that, that work isn't done. Yeah. It >>Is. It's an >>Opportunity. It's on paper. >>It's an opportunity though. It's not, I mean, we're not in a bad spot. So I mean, I think what you're getting at is that there's a lot of fix a lot of gaps. All right. I want Jay, I wanna bring you in, because we had a panel at super cloud event. Chris Hoff, you know, beaker was on here. Yeah. He's always snarky, but he's building, he's been building clouds lately. So he's been getting his, his hands dirty, rolling up his sleeves. The title of panel was originally called the innovators dilemma with a question, mark, you know, haha you know, innovators, dilemma, little goof on that. Cuz you know, there's challenges and trade offs like, like he's talking about, he says we should call it the integrator's dilemma because I think a lot of people are talking about, okay, it's not as seamless as it can be or should be in the Nirvana state. >>But there's a lot of integration going on. A lot of APIs are, are key to this API security. One of the most talked about things. I mean I interviewed six companies on API security in the past couple months. So yeah. I mean I never talked to anybody about API security before this year. Yeah. APIs are critical. So these key things of cloud are being attacked. And so there's more complexity as we're getting more successful. And so, so I think this is mucking up some of the conversations, what's your read on this to make the complexity go away. You guys have the, the chaos rain here, which I actually like that Dave does too, but you know, Andy Grove once said let chaos rain and then rain in the chaos. So we're in that reign in the chaos mode. Now what's your take on what Keith was saying around. Yeah. >>So I think that the one piece of the puzzle that's missing a little bit from Keith's narrative that I think is important is it's really not just infrastructure and developers. Right? It's it's there's in fact, and, and I, I wrote a blog post about this a long time ago, right? There's there's really sort of three layers of operations that come out of the cloud model in long term and that's applications and infrastructure at the bottom and in the middle is platform and services. And so I think one of the, this is where VMware is making its play right now is in terms of providing the platform and service capability that does that integration at a lower level works with VMs works with bare metal, works with the public cloud services that are available, makes it easy to access things like database services and messaging services and things along those lines. >>It makes it easy to turn code that you write into a service that can be consumed by other applications, but ultimately creates an in environment that begins to pull away from having to know, to write code about infrastructure. Right. And so infrastructure's, code's great. But if you have a right platform, you don't have to write code about infrastructure. You can actually D declare what basic needs of the application are. And then that platform will say, okay, well I will interpret that. And that's really, that's what Kubernetes strength is. Yeah. And that's what VMware's taking advantage of with what we're doing >>With. Yeah. I remember when we first Lou Tucker and I, and I think you might have been in the room during those OpenStack days and when Kubernetes was just starting and literally just happened, the paper was written, gonna go out and a couple companies formed around it. We said that could be the interoperability layer between clouds and our, our dream at that time was Hey. And, and we, we mentioned and Stratus in our, our super cloud, but the days of spanning clouds, a dream, we thought that now look at Kubernetes. Now it's kind of become that defacto rallying moment for, I won't say middleware, but this abstraction that we've been talking about allows for right once run anywhere. I think to me, that's not nowhere in the market today. Nobody has that. Nobody has anything that could write once, read one, write once and then run on multiple clouds. >>It's more true than ever. We had one customer that just was, was using AKs for a while and then decided to try the application on EKS. And they said it took them a couple of hours to, to get through the few issues they ran into. >>Yeah. I talked to a customer who who's going from, who went from VMC on AWS to Oracle cloud on Oracle cloud's VMware solution. And he raved about now he has a inherent backup Dr. For his O CVS solution because there's a shim between the two. And >>How did he do >>That? The, there there's a solution. And this is where the white space is. James talked about in the past exists. When, when I go to a conference like Cuban, the cube will be there in, in Detroit, in, in, in about 45 days or so. I talk to platform group at the platform group. That's doing the work that VMware red had hash Corp all should be doing. I shouldn't have to build that shim while we rave and, and talk about the power Kubernetes. That's great, but Kubernetes might get me 60 to 65% of their, for the platform right now there's groups of developers within that sit in between infrastructure and sit in between application development that all they do is build platforms. There's a lot of opportunity to build that platform. VMware announced tap one, 1.3. And the thing that I'm surprised, the one on Twitter is talking about is this API discovery piece. If you've ever had to use an API and you don't know how to integrate with it or whatever, and now it, it just magically happens. The marketing at the end of developing the application. Think if you're in you're, you're in a shop that develops hundreds of applications, there's thousands or tens of thousands of APIs that have to be documented. That's beating the developer where it's at and it's also infrastructure. >>Well guys, thanks for coming on the cube. I really appreciate we're on a time deadline, which we're gonna do more. We'll follow up on a power panel after VMware Explorer. Thanks for coming on the cube. Appreciate it. No problem. See you pleasure. Yeah. Okay. We'll be back with more live coverage. You, after this short break, stay with us.

[Music] welcome to the great super cloud debate a power panel of three top technology industry analysts maribel lopez is here she's the founder and principal analyst at lopez research keith townsend is ceo and founder of the cto advisor and sanjeev mohan is principal at sanjmo super cloud is a term that we've used to describe the future of cloud architectures the idea is that super clouds are built on top of hyperscaler capex infrastructure and the idea is it goes beyond multi-cloud the premise being that multi-cloud is primarily a symptom of multi-vendor or m a or both and results in more stove we're going to talk about that super cloud's meant to connote a new architecture that leverages the underlying primitives of hyperscale clouds but hides and abstracts that complexity of each of their respective clouds and adds new value on top of that with services and a continuous experience a similar or identical experience across more than one cloud people may say hey that's multi-cloud we're going to talk about that as well so with that as brief background um i'd like to first welcome our painless guys thanks so much for coming on thecube it's great to see you all again great to be here thank you to be here so i'm going to start with maribel you know what i just described what's your reaction to that is it just like what like cloud is supposed to be is that really what multi-cloud is do you agree with the premise that multi-cloud has really been you know what like chuck whitten from dell calls it it's been multi-cloud by default i call it a symptom of multi-vendor what's your take on on what this is oh wow dave another term here we go right more more to define for people but okay the reality is i agree that it's time for something new something evolved right whether we call that super cloud or something else i you know i don't want to really debate the term but we need to move beyond where we are today in multi-cloud and into if we want to call it cloud 5 multi-cloud 2 whatever we want to call it i believe that we're at the next generation that we have to define what that next generation is but if you think about it we went from public to private to hybrid to multi and every time you have a discussion with somebody about cloud you spend 10 minutes defining what you're talking about so this doesn't seem any different to me so let's just go with super cloud for the moment and see where we go and you know if you're interested after everybody else makes their comments i got a few thoughts about what super cloud might mean as well yeah great so i and i agree with you when we like i said in a recent post you could call it cl cloud you know multi-cloud 2.0 but it's something different is happening and sanjeev i know you're not a you're not a big fan of buzz words either but i wonder if you could weigh in on this topic uh you mean by the way sanjeev is at the mit cdo iq conference a great conference uh in boston uh and so he's it's a public place so we're going to have i think you viewed his line when he's not speaking please go ahead yeah so you know i come from a pedigree of uh being an analyst of uh firms that love inventing new terms i am not a big fan of inventing new terms i feel that when we come up with a new term i spend all my time standing on a stage trying to define what it is it takes me away from trying to solve the problem so so i'm you know i find these terms to be uh words of convenience like for example big data you know big data to me may not mean anything but big data connotes some of this modern way of handling vast volumes of data that traditional systems could not handle so from that point of view i'm i'm completely okay with super cloud but just inventing a new term is what i have called in my previous sessions tyranny of jargons where we have just too many jargons and uh and they resonate with i.t people they do not resonate with the business people business people care about the problem they don't care about what we and i t called them yeah and i think this is a really important point that you make and by the way we're not trying to create a new industry category per se yeah we leave that to gartner that's why actually i like super cloud because nobody's going to use that no vendor's going to use the term super cloud it's just too buzzy so so but but but it brings up the point about practitioners and so keith i want to bring you in so the what we've talked about and i'll just sort of share some some thoughts on the problems that we see and and get keith get your practitioner view most clouds most companies use multiple clouds we all kind of agree on that i think and largely these clouds operate in silos and they have their own development environment their own operating environment different apis different primitives and the functionality of a particular cloud doesn't necessarily extend to other clouds so the problem is that increases friction for customers increases cost increases security risk and so there's this promise maribel multi-cloud 2.0 that's going to solve that problem so keith my question to you is is is that an accurate description of the problem that practitioners face today do what did i miss and i wonder if you could elaborate so i think we'll get into some of the detail later on why this is a problem specifically around technologies but if we think about it in the abstract most customers have their hands full dealing with one cloud like we'll you know through m a and such and you zoom in and you look at companies that have multiple clouds or multi-cloud from result of mma mna m a activity you'll see that most of that is in silos so organizationally the customer may have multiple clouds but sub orchid silos they're generally a single silo in a single cloud so as you think about being able to take advantage of of tooling across the multicloud of what dave you guys are calling the super cloud this becomes a serious problem it's just a skill problem it's too much capability uh across too many things that look completely different than another okay so dave can i pick up on that please i'd love i was gonna just go to you maribel please chime in here okay so if we think about what we're talking about with super cloud and what keith just mentioned remember when we went to see tcp ip and the whole idea was like how do we get computers to talk to each other in a more standardized way how do we get data to move in a more standardized way i think that the problem we have with multi-cloud right now is that we don't have that so i think that's sort of a ground level of getting us to your super cloud premise is that and and you know google's tried it with anthony's like everybody every hyperscaler has tried their like right one to run anywhere but that abstraction layer you talk about what whatever we want to call it is super necessary and it's sort of the foundation so if you really think about it we've spent like 15 years or so building out all the various components of cloud and now's the time to take it so that cloud is actually more of an operating model versus a place there's at least a base level of it that is vendor neutral and then to your point the value that's going to be built on top of that you know people been trying to commoditize the basic infrastructure for a while now and i think that's what you're seeing in your super cloud multi-cloud whatever you want to call it the infrastructure is the infrastructure and then what would have been traditionally that past layer and above is where we're going to start to see some real innovation but we still haven't gotten to that point where you can do visibility observability manageability across that really complex cloud stack that we have the reason i the reason i love that tcpip example hm is because it changed the industry and it had an ecosystem effect in sanjiv the the the example that i first example that i used was snowflake a company that you're very familiar with that is sort of hiding all that complexity and right and so we're not there yet but please chime in on this topic uh you gotta you gotta view it again uh after you building upon what maribel said you know to me uh this sounds like a multi-cloud operating system where uh you know you need that kind of a common uh set of primitives and layers because if you go in in the typical multi-cloud process you've got multiple identities and you can't have that you how can you govern if i'm if i have multiple identities i don't have observability i don't know what's going on across my different stacks so to me super cloud is that call it single pane of glass or or one way through which i'm unifying my experience my my technology interfaces my integration and uh and i as an end user don't even care which uh which cloud i'm in it makes no difference to me it makes a difference to the vendor the vendor may say this is coming from aws and this is coming from gcp or azure but to the end user it is a consistent experience with consistent id and and observability and governance so that to me makes it a big difference and so one of floyer's contribution conversation was in order to have a super cloud you got to have a super pass i'm like oh boy people are going to love that but the point being that that allows a consistent developer experience and to maribel's earlier point about tcp it explodes the ecosystem because the ecosystem can now write to that super pass if you will those apis so keith do you do do you buy that number one and number two do you see that industries financial services and healthcare are actually going to be on clouds or what we call super clouds so sanjeev hit on a really key aspect of this is identity let's make this real they you love talk about data collaboration i love senji's point on the business user kind of doesn't care if this is aws versus super cloud versus etc i was collaborating with the client and he wanted to send video file and the video file uh his organization's access control policy didn't allow him to upload or share the file from their preferred platform so he had to go out to another cloud provider and create yet another identity for that data on the cloud same data different identity a proper super cloud will enable me to simply say as a end user here's a set of data or data sets and i want to share a collaboration a collaborator and that requires cross identity across multiple clouds so even before we get to the past layer and the apis we have to solve the most basic problem which is data how do we stop data scientists from shipping snowballs to a location because we can't figure out the identity the we're duplicating the same data within the same cloud because we can't share identity across customer accounts or etc we we have to solve these basic thoughts before we get to supercloud otherwise we get to us a turtles all the way down thing so we'll get into snowflake and what snowflake can do but that's what happens when i want to share my snowflake data across multiple clouds to a different platform yeah you have to go inside the snowflake cloud which leads right so i would say to keith's question sanjeev snowflake i think is solving that problem but then he brings up the other problem which is what if i want to share share data outside the snowflake cloud so that gets to the point of visit open is it closed and so sanji chime in on the sort of snowflake example and in maribel i wonder if there are networking examples because that's that's keith's saying you got to fix the plumbing before you get these higher level abstractions but sanji first yeah so i so i actually want to go and talk a little bit about network but from a data and analytics point of view so i never built upon what what keith said so i i want to give an example let's say i am getting fantastic web logs i and i know who uh uh how much time they're spending on my web pages and which pages they're looking at so i have all of that now all of that is going into cloud a now it turns out that i use google analytics or maybe i use adobe's you know analytics uh suite now that is giving me the business view and i'm trying to do customer journey analytics and guess what i now have two separate identities two separate products two separate clouds if i and i as an id person no problem i can solve any problem by writing tons of code but why would i do that if i can have that super pass or a multi-cloud layout where i've got like a single way of looking at my network traffic my customer metrics and i can do my customer journey analytics it solves a huge problem and then i can share that data with my with my partners so they can see data about their products which is a combination of data from different uh clouds great thank you uh maribel please i think we're having a lord of the rings moment here with the run one room to rule them all concept and i'm not sure that anybody's actually incented to do that right so i think there's two levels of the stack i think in the basic we're talking a lot about we don't have the basic fundamentals of how do you move data authenticate data secure data do data lineage all that stuff across different clouds right we haven't even spoken right now i feel like we're really just talking about the public cloud venue and we haven't even pulled in the fact that people are doing hybrid cloud right so hybrid cloud you know then you're talking about you've got hardware vendors and you've got hyperscaler vendors and there's two or three different ways of doing things so i honestly think that something will emerge like if we think about where we are in technology today it's almost like we need back to that operating system that sanji was talking about like we need a next generation operating system like nobody wants to build the cloud mouse driver of the 21st century over and over again right we need something like that as a foundation layer but then on top of it you know there's obviously a lot of opportunity to build differentiation like when i think back on what happened with cloud amazon remained aws remained very powerful and popular because people invested in building things on amazon right they created a platform and it took a while for anybody else to catch up to that or to have that kind of presence and i still feel that way when i talk to companies but having said that i talked to retail the other day and they were like hey we spent a long time building an abstraction layer on top of the clouds so that our developers could basically write once and run anywhere but they were a massive global presence retailer that's not something that everybody can do so i think that we are still missing a gap i don't know if that exactly answers your question but i i do feel like we're kind of in this chicken and egg thing which comes first and nobody wants to necessarily invest in like oh well you know amazon has built a way to do this so we're all just going to do it the amazon way right it seems like that's not going to work either but i think you bring up a really important point which there is going to be no one ring to rule them all you're going to have you know vmware is going to solve its multi-cloud problem snowflake's going to do a very has a very specific you know purpose-built system for it itself databricks is going to do its thing and it's going to be you know more open source i would companies like aviatrix i would say cisco even is going to go out and solve this problem dell showed at uh at dell tech world a thing called uh project alpine which is basically storage across clouds they're going to be many super clouds we're going to get maybe super cloud stove pipes but but the point is however for a specific problem in a set of use cases they will be addressing those and solving incremental value so keith maybe we won't have that single cloud operating you know system but we'll have multiple ones what are your thoughts on that yeah we're definitely going to have multiple ones uh the there is no um there is no community large enough or influential enough to push a design take maribel's example of the mega retailer they've solved it but they're not going to that's that's competitive that's their competitive advantage they're not going to share that with the rest of us and open source that and force that upon the industry via just agreement from everyone else so we're not going to get uh the level of collaboration either originated by the cloud provider originated from user groups that solves this problem big for us we will get silos in which this problem is solved we'll get groups working together inside of maybe uh industry or subgroups within the industry to say that hey we're going to share or federate identity across our three or four or five or a dozen organizations we'll be able to share data we're going to solve that data problem but in the same individual organizations in another part of the super cloud problem are going to again just be silos i can't uh i can't run machine learning against my web assets for the community group that i run because that's not part of the working group that solved a different data science problem so yes we're going to have these uh bifurcations and forks within the super cloud the question is where is the focus for each individual organization where do i point my smart people and what problems they solve okay i want to throw out a premise and get you guys reaction to it because i think this again i go back to the maribel's tcpip example it changed the industry it opened up an ecosystem and to me this is what digital transformation is all about you've got now industry participants marc andreessen says every company is a software company you've now got industry participants and here's some examples it's not i wouldn't call them true super clouds yet but walmart's doing their hybrid thing with azure you got goldman sachs announced at the last reinvent and it's going to take its tools its software its data and which is on-prem and connect that to the aws cloud and actually deliver a service capital one we saw sanjiv at the snowflake summit is is taking their tooling and doing it now granted just within snowflake and aws but i fully expect them to expand that across other clouds these are industry examples capital one software is the name of the division that are now it's to the re reason why i don't get so worried that we're not solving the lord of the rings problem that maribel mentioned is because it opens up tremendous opportunities for companies we got like just under five minutes left i want to throw that out there and see what you guys think yeah i would just i want to build upon what maribel said i love what she said you're not going to build a mouse driver so if multi-cloud supercloud is a multi-cloud os the mouse driver would be identity or maybe it's data quality and to teach point that data quality is not going to come from a single vendor that is going to come from a different vendor whose job is to to harmonize data because there might be data might be for the same identity but it may be a different granularity level so you cannot just mix and match so you need to have some sort of like resolution and that is is an example of a driver for multi-cloud interesting okay so you know octa might be the identity cloud or z scaler might be the security cloud or calibre has its cloud etc any thoughts on that keith or maribel yeah so let's talk about where the practical challenges run into this we did some really great research that was sponsored by one of the large cloud providers in which we took all we looked at all the vmware cloud solutions when i say vmware cloud vmware has a lot of products across multi-cloud now in the rock broadcloud portfolio but we're talking about the og solution vmware vsphere it would seem like on paper if i put vmware vsphere in each cloud that is therefore a super cloud i think we would all agree to that in principle what we found in our research was that when we put hands on keyboard the differences of the clouds show themselves in the training gap and that skills gap between the clouds show themselves if i needed to expose less our favorite friend a friend a tc pip address to the public internet that is a different process on each one of the clouds that needs to be done on each one of the clouds and not abstracted in vmware vsphere so as we look at the nuance yes we can give the big controls but where the capital ones the uh jp morgan chase just spent two billion dollars on this type of capability where the spin effort is done is taking it from that 80 percent to that 90 95 experience and that's where the effort and money is spent on that last mile maribel we're out of time but please you know bring us home give us your closing thoughts hey i think we're still going to be working on what the multi-cloud thing is for a while and you know super cloud i think is a direction of the future of cloud computing but we got some real problems to solve around authentication uh identity data lineage data security so i think those are going to be sort of the tactical things that we're working on for the next couple years right guys always a pleasure having you on the cube i hope we see you around keith i understand you're you're bringing your airstream to vmworld or vmware explorer putting it on the on the floor i can't wait to see that and uh mrs cto advisor i'm sure we'll be uh by your side so looking forward to that hopefully sanjeev and maribel we'll see you uh on the circuit as well yes hope to see you there right looking forward to hopefully even doing some content with you guys at vmware explorer too awesome looking forward all right keep it right there for more content from super cloud 22 right back [Music] you

(upbeat music) >> The ascendancy of cloud and SAS has shown new light on how organizations think about, pay for, and value hardware. Once sought after skills for practitioners with expertise in hardware troubleshooting, configuring ports, tuning storage arrays, and maximizing server utilization has been superseded by demand for cloud architects, DevOps pros, developers with expertise in microservices, container, application development, and like. Even a company like Dell, the largest hardware company in enterprise tech touts that it has more software engineers than those working in hardware. Begs the question, is hardware going the way of Coball? Well, not likely. Software has to run on something, but the labor needed to deploy, and troubleshoot, and manage hardware infrastructure is shifting. At the same time, we've seen the value flow also shifting in hardware. Once a world dominated by X86 processors value is flowing to alternatives like Nvidia and arm based designs. Moreover, other componentry like NICs, accelerators, and storage controllers are becoming more advanced, integrated, and increasingly important. The question is, does it matter? And if so, why does it matter and to whom? What does it mean to customers, workloads, OEMs, and the broader society? Hello and welcome to this week's Wikibon theCUBE Insights powered by ETR. In this breaking analysis, we've organized a special power panel of industry analysts and experts to address the question, does hardware still matter? Allow me to introduce the panel. Bob O'Donnell is president and chief analyst at TECHnalysis Research. Zeus Kerravala is the founder and principal analyst at ZK Research. David Nicholson is a CTO and tech expert. Keith Townson is CEO and founder of CTO Advisor. And Marc Staimer is the chief dragon slayer at Dragon Slayer Consulting and oftentimes a Wikibon contributor. Guys, welcome to theCUBE. Thanks so much for spending some time here. >> Good to be here. >> Thanks. >> Thanks for having us. >> Okay before we get into it, I just want to bring up some data from ETR. This is a survey that ETR does every quarter. It's a survey of about 1200 to 1500 CIOs and IT buyers and I'm showing a subset of the taxonomy here. This XY axis and the vertical axis is something called net score. That's a measure of spending momentum. It's essentially the percentage of customers that are spending more on a particular area than those spending less. You subtract the lesses from the mores and you get a net score. Anything the horizontal axis is pervasion in the data set. Sometimes they call it market share. It's not like IDC market share. It's just the percentage of activity in the data set as a percentage of the total. That red 40% line, anything over that is considered highly elevated. And for the past, I don't know, eight to 12 quarters, the big four have been AI and machine learning, containers, RPA and cloud and cloud of course is very impressive because not only is it elevated in the vertical access, but you know it's very highly pervasive on the horizontal. So what I've done is highlighted in red that historical hardware sector. The server, the storage, the networking, and even PCs despite the work from home are depressed in relative terms. And of course, data center collocation services. Okay so you're seeing obviously hardware is not... People don't have the spending momentum today that they used to. They've got other priorities, et cetera, but I want to start and go kind of around the horn with each of you, what is the number one trend that each of you sees in hardware and why does it matter? Bob O'Donnell, can you please start us off? >> Sure Dave, so look, I mean, hardware is incredibly important and one comment first I'll make on that slide is let's not forget that hardware, even though it may not be growing, the amount of money spent on hardware continues to be very, very high. It's just a little bit more stable. It's not as subject to big jumps as we see certainly in other software areas. But look, the important thing that's happening in hardware is the diversification of the types of chip architectures we're seeing and how and where they're being deployed, right? You refer to this in your opening. We've moved from a world of x86 CPUs from Intel and AMD to things like obviously GPUs, DPUs. We've got VPU for, you know, computer vision processing. We've got AI-dedicated accelerators, we've got all kinds of other network acceleration tools and AI-powered tools. There's an incredible diversification of these chip architectures and that's been happening for a while but now we're seeing them more widely deployed and it's being done that way because workloads are evolving. The kinds of workloads that we're seeing in some of these software areas require different types of compute engines than traditionally we've had. The other thing is (coughs), excuse me, the power requirements based on where geographically that compute happens is also evolving. This whole notion of the edge, which I'm sure we'll get into a little bit more detail later is driven by the fact that where the compute actually sits closer to in theory the edge and where edge devices are, depending on your definition, changes the power requirements. It changes the kind of connectivity that connects the applications to those edge devices and those applications. So all of those things are being impacted by this growing diversity in chip architectures. And that's a very long-term trend that I think we're going to continue to see play out through this decade and well into the 2030s as well. >> Excellent, great, great points. Thank you, Bob. Zeus up next, please. >> Yeah, and I think the other thing when you look at this chart to remember too is, you know, through the pandemic and the work from home period a lot of companies did put their office modernization projects on hold and you heard that echoed, you know, from really all the network manufacturers anyways. They always had projects underway to upgrade networks. They put 'em on hold. Now that people are starting to come back to the office, they're looking at that now. So we might see some change there, but Bob's right. The size of those market are quite a bit different. I think the other big trend here is the hardware companies, at least in the areas that I look at networking are understanding now that it's a combination of hardware and software and silicon that works together that creates that optimum type of performance and experience, right? So some things are best done in silicon. Some like data forwarding and things like that. Historically when you look at the way network devices were built, you did everything in hardware. You configured in hardware, they did all the data for you, and did all the management. And that's been decoupled now. So more and more of the control element has been placed in software. A lot of the high-performance things, encryption, and as I mentioned, data forwarding, packet analysis, stuff like that is still done in hardware, but not everything is done in hardware. And so it's a combination of the two. I think, for the people that work with the equipment as well, there's been more shift to understanding how to work with software. And this is a mistake I think the industry made for a while is we had everybody convinced they had to become a programmer. It's really more a software power user. Can you pull things out of software? Can you through API calls and things like that. But I think the big frame here is, David, it's a combination of hardware, software working together that really make a difference. And you know how much you invest in hardware versus software kind of depends on the performance requirements you have. And I'll talk about that later but that's really the big shift that's happened here. It's the vendors that figured out how to optimize performance by leveraging the best of all of those. >> Excellent. You guys both brought up some really good themes that we can tap into Dave Nicholson, please. >> Yeah, so just kind of picking up where Bob started off. Not only are we seeing the rise of a variety of CPU designs, but I think increasingly the connectivity that's involved from a hardware perspective, from a kind of a server or service design perspective has become increasingly important. I think we'll get a chance to look at this in more depth a little bit later but when you look at what happens on the motherboard, you know we're not in so much a CPU-centric world anymore. Various application environments have various demands and you can meet them by using a variety of components. And it's extremely significant when you start looking down at the component level. It's really important that you optimize around those components. So I guess my summary would be, I think we are moving out of the CPU-centric hardware model into more of a connectivity-centric model. We can talk more about that later. >> Yeah, great. And thank you, David, and Keith Townsend I really interested in your perspectives on this. I mean, for years you worked in a data center surrounded by hardware. Now that we have the software defined data center, please chime in here. >> Well, you know, I'm going to dig deeper into that software-defined data center nature of what's happening with hardware. Hardware is meeting software infrastructure as code is a thing. What does that code look like? We're still trying to figure out but servicing up these capabilities that the previous analysts have brought up, how do I ensure that I can get the level of services needed for the applications that I need? Whether they're legacy, traditional data center, workloads, AI ML, workloads, workloads at the edge. How do I codify that and consume that as a service? And hardware vendors are figuring this out. HPE, the big push into GreenLake as a service. Dale now with Apex taking what we need, these bare bone components, moving it forward with DDR five, six CXL, et cetera, and surfacing that as cold or as services. This is a very tough problem. As we transition from consuming a hardware-based configuration to this infrastructure as cold paradigm shift. >> Yeah, programmable infrastructure, really attacking that sort of labor discussion that we were having earlier, okay. Last but not least Marc Staimer, please. >> Thanks, Dave. My peers raised really good points. I agree with most of them, but I'm going to disagree with the title of this session, which is, does hardware matter? It absolutely matters. You can't run software on the air. You can't run it in an ephemeral cloud, although there's the technical cloud and that's a different issue. The cloud is kind of changed everything. And from a market perspective in the 40 plus years I've been in this business, I've seen this perception that hardware has to go down in price every year. And part of that was driven by Moore's law. And we're coming to, let's say a lag or an end, depending on who you talk to Moore's law. So we're not doubling our transistors every 18 to 24 months in a chip and as a result of that, there's been a higher emphasis on software. From a market perception, there's no penalty. They don't put the same pressure on software from the market to reduce the cost every year that they do on hardware, which kind of bass ackwards when you think about it. Hardware costs are fixed. Software costs tend to be very low. It's kind of a weird thing that we do in the market. And what's changing is we're now starting to treat hardware like software from an OPEX versus CapEx perspective. So yes, hardware matters. And we'll talk about that more in length. >> You know, I want to follow up on that. And I wonder if you guys have a thought on this, Bob O'Donnell, you and I have talked about this a little bit. Marc, you just pointed out that Moore's laws could have waning. Pat Gelsinger recently at their investor meeting said that he promised that Moore's law is alive and well. And the point I made in breaking analysis was okay, great. You know, Pat said, doubling transistors every 18 to 24 months, let's say that Intel can do that. Even though we know it's waning somewhat. Look at the M1 Ultra from Apple (chuckles). In about 15 months increased transistor density on their package by 6X. So to your earlier point, Bob, we have this sort of these alternative processors that are really changing things. And to Dave Nicholson's point, there's a whole lot of supporting components as well. Do you have a comment on that, Bob? >> Yeah, I mean, it's a great point, Dave. And one thing to bear in mind as well, not only are we seeing a diversity of these different chip architectures and different types of components as a number of us have raised the other big point and I think it was Keith that mentioned it. CXL and interconnect on the chip itself is dramatically changing it. And a lot of the more interesting advances that are going to continue to drive Moore's law forward in terms of the way we think about performance, if perhaps not number of transistors per se, is the interconnects that become available. You're seeing the development of chiplets or tiles, people use different names, but the idea is you can have different components being put together eventually in sort of a Lego block style. And what that's also going to allow, not only is that going to give interesting performance possibilities 'cause of the faster interconnect. So you can share, have shared memory between things which for big workloads like AI, huge data sets can make a huge difference in terms of how you talk to memory over a network connection, for example, but not only that you're going to see more diversity in the types of solutions that can be built. So we're going to see even more choices in hardware from a silicon perspective because you'll be able to piece together different elements. And oh, by the way, the other benefit of that is we've reached a point in chip architectures where not everything benefits from being smaller. We've been so focused and so obsessed when it comes to Moore's law, to the size of each individual transistor and yes, for certain architecture types, CPUs and GPUs in particular, that's absolutely true, but we've already hit the point where things like RF for 5g and wifi and other wireless technologies and a whole bunch of other things actually don't get any better with a smaller transistor size. They actually get worse. So the beauty of these chiplet architectures is you could actually combine different chip manufacturing sizes. You know you hear about four nanometer and five nanometer along with 14 nanometer on a single chip, each one optimized for its specific application yet together, they can give you the best of all worlds. And so we're just at the very beginning of that era, which I think is going to drive a ton of innovation. Again, gets back to my comment about different types of devices located geographically different places at the edge, in the data center, you know, in a private cloud versus a public cloud. All of those things are going to be impacted and there'll be a lot more options because of this silicon diversity and this interconnect diversity that we're just starting to see. >> Yeah, David. David Nicholson's got a graphic on that. They're going to show later. Before we do that, I want to introduce some data. I actually want to ask Keith to comment on this before we, you know, go on. This next slide is some data from ETR that shows the percent of customers that cited difficulty procuring hardware. And you can see the red is they had significant issues and it's most pronounced in laptops and networking hardware on the far right-hand side, but virtually all categories, firewalls, peripheral servers, storage are having moderately difficult procurement issues. That's the sort of pinkish or significant challenges. So Keith, I mean, what are you seeing with your customers in the hardware supply chains and bottlenecks? And you know we're seeing it with automobiles and appliances but so it goes beyond IT. The semiconductor, you know, challenges. What's been the impact on the buyer community and society and do you have any sense as to when it will subside? >> You know, I was just asked this question yesterday and I'm feeling the pain. People question, kind of a side project within the CTO advisor, we built a hybrid infrastructure, traditional IT data center that we're walking with the traditional customer and modernizing that data center. So it was, you know, kind of a snapshot of time in 2016, 2017, 10 gigabit, ARISTA switches, some older Dell's 730 XD switches, you know, speeds and feeds. And we said we would modern that with the latest Intel stack and connected to the public cloud and then the pandemic hit and we are experiencing a lot of the same challenges. I thought we'd easily migrate from 10 gig networking to 25 gig networking path that customers are going on. The 10 gig network switches that I bought used are now double the price because you can't get legacy 10 gig network switches because all of the manufacturers are focusing on the more profitable 25 gig for capacity, even the 25 gig switches. And we're focused on networking right now. It's hard to procure. We're talking about nine to 12 months or more lead time. So we're seeing customers adjust by adopting cloud. But if you remember early on in the pandemic, Microsoft Azure kind of gated customers that didn't have a capacity agreement. So customers are keeping an eye on that. There's a desire to abstract away from the underlying vendor to be able to control or provision your IT services in a way that we do with VMware VP or some other virtualization technology where it doesn't matter who can get me the hardware, they can just get me the hardware because it's critically impacting projects and timelines. >> So that's a great setup Zeus for you with Keith mentioned the earlier the software-defined data center with software-defined networking and cloud. Do you see a day where networking hardware is monetized and it's all about the software, or are we there already? >> No, we're not there already. And I don't see that really happening any time in the near future. I do think it's changed though. And just to be clear, I mean, when you look at that data, this is saying customers have had problems procuring the equipment, right? And there's not a network vendor out there. I've talked to Norman Rice at Extreme, and I've talked to the folks at Cisco and ARISTA about this. They all said they could have had blowout quarters had they had the inventory to ship. So it's not like customers aren't buying this anymore. Right? I do think though, when it comes to networking network has certainly changed some because there's a lot more controls as I mentioned before that you can do in software. And I think the customers need to start thinking about the types of hardware they buy and you know, where they're going to use it and, you know, what its purpose is. Because I've talked to customers that have tried to run software and commodity hardware and where the performance requirements are very high and it's bogged down, right? It just doesn't have the horsepower to run it. And, you know, even when you do that, you have to start thinking of the components you use. The NICs you buy. And I've talked to customers that have simply just gone through the process replacing a NIC card and a commodity box and had some performance problems and, you know, things like that. So if agility is more important than performance, then by all means try running software on commodity hardware. I think that works in some cases. If performance though is more important, that's when you need that kind of turnkey hardware system. And I've actually seen more and more customers reverting back to that model. In fact, when you talk to even some startups I think today about when they come to market, they're delivering things more on appliances because that's what customers want. And so there's this kind of app pivot this pendulum of agility and performance. And if performance absolutely matters, that's when you do need to buy these kind of turnkey, prebuilt hardware systems. If agility matters more, that's when you can go more to software, but the underlying hardware still does matter. So I think, you know, will we ever have a day where you can just run it on whatever hardware? Maybe but I'll long be retired by that point. So I don't care. >> Well, you bring up a good point Zeus. And I remember the early days of cloud, the narrative was, oh, the cloud vendors. They don't use EMC storage, they just run on commodity storage. And then of course, low and behold, you know, they've trot out James Hamilton to talk about all the custom hardware that they were building. And you saw Google and Microsoft follow suit. >> Well, (indistinct) been falling for this forever. Right? And I mean, all the way back to the turn of the century, we were calling for the commodity of hardware. And it's never really happened because you can still drive. As long as you can drive innovation into it, customers will always lean towards the innovation cycles 'cause they get more features faster and things. And so the vendors have done a good job of keeping that cycle up but it'll be a long time before. >> Yeah, and that's why you see companies like Pure Storage. A storage company has 69% gross margins. All right. I want to go jump ahead. We're going to bring up the slide four. I want to go back to something that Bob O'Donnell was talking about, the sort of supporting act. The diversity of silicon and we've marched to the cadence of Moore's law for decades. You know, we asked, you know, is Moore's law dead? We say it's moderating. Dave Nicholson. You want to talk about those supporting components. And you shared with us a slide that shift. You call it a shift from a processor-centric world to a connect-centric world. What do you mean by that? And let's bring up slide four and you can talk to that. >> Yeah, yeah. So first, I want to echo this sentiment that the question does hardware matter is sort of the answer is of course it matters. Maybe the real question should be, should you care about it? And the answer to that is it depends who you are. If you're an end user using an application on your mobile device, maybe you don't care how the architecture is put together. You just care that the service is delivered but as you back away from that and you get closer and closer to the source, someone needs to care about the hardware and it should matter. Why? Because essentially what hardware is doing is it's consuming electricity and dollars and the more efficiently you can configure hardware, the more bang you're going to get for your buck. So it's not only a quantitative question in terms of how much can you deliver? But it also ends up being a qualitative change as capabilities allow for things we couldn't do before, because we just didn't have the aggregate horsepower to do it. So this chart actually comes out of some performance tests that were done. So it happens to be Dell servers with Broadcom components. And the point here was to peel back, you know, peel off the top of the server and look at what's in that server, starting with, you know, the PCI interconnect. So PCIE gen three, gen four, moving forward. What are the effects on from an interconnect versus on performance application performance, translating into new orders per minute, processed per dollar, et cetera, et cetera? If you look at the advances in CPU architecture mapped against the advances in interconnect and storage subsystem performance, you can see that CPU architecture is sort of lagging behind in a way. And Bob mentioned this idea of tiling and all of the different ways to get around that. When we do performance testing, we can actually peg CPUs, just running the performance tests without any actual database environments working. So right now we're at this sort of imbalance point where you have to make sure you design things properly to get the most bang per kilowatt hour of power per dollar input. So the key thing here what this is highlighting is just as a very specific example, you take a card that's designed as a gen three PCIE device, and you plug it into a gen four slot. Now the card is the bottleneck. You plug a gen four card into a gen four slot. Now the gen four slot is the bottleneck. So we're constantly chasing these bottlenecks. Someone has to be focused on that from an architectural perspective, it's critically important. So there's no question that it matters. But of course, various people in this food chain won't care where it comes from. I guess a good analogy might be, where does our food come from? If I get a steak, it's a pink thing wrapped in plastic, right? Well, there are a lot of inputs that a lot of people have to care about to get that to me. Do I care about all of those things? No. Are they important? They're critically important. >> So, okay. So all I want to get to the, okay. So what does this all mean to customers? And so what I'm hearing from you is to balance a system it's becoming, you know, more complicated. And I kind of been waiting for this day for a long time, because as we all know the bottleneck was always the spinning disc, the last mechanical. So people who wrote software knew that when they were doing it right, the disc had to go and do stuff. And so they were doing other things in the software. And now with all these new interconnects and flash and things like you could do atomic rights. And so that opens up new software possibilities and combine that with alternative processes. But what's the so what on this to the customer and the application impact? Can anybody address that? >> Yeah, let me address that for a moment. I want to leverage some of the things that Bob said, Keith said, Zeus said, and David said, yeah. So I'm a bit of a contrarian in some of this. For example, on the chip side. As the chips get smaller, 14 nanometer, 10 nanometer, five nanometer, soon three nanometer, we talk about more cores, but the biggest problem on the chip is the interconnect from the chip 'cause the wires get smaller. People don't realize in 2004 the latency on those wires in the chips was 80 picoseconds. Today it's 1300 picoseconds. That's on the chip. This is why they're not getting faster. So we maybe getting a little bit slowing down in Moore's law. But even as we kind of conquer that you still have the interconnect problem and the interconnect problem goes beyond the chip. It goes within the system, composable architectures. It goes to the point where Keith made, ultimately you need a hybrid because what we're seeing, what I'm seeing and I'm talking to customers, the biggest issue they have is moving data. Whether it be in a chip, in a system, in a data center, between data centers, moving data is now the biggest gating item in performance. So if you want to move it from, let's say your transactional database to your machine learning, it's the bottleneck, it's moving the data. And so when you look at it from a distributed environment, now you've got to move the compute to the data. The only way to get around these bottlenecks today is to spend less time in trying to move the data and more time in taking the compute, the software, running on hardware closer to the data. Go ahead. >> So is this what you mean when Nicholson was talking about a shift from a processor centric world to a connectivity centric world? You're talking about moving the bits across all the different components, not having the processor you're saying is essentially becoming the bottleneck or the memory, I guess. >> Well, that's one of them and there's a lot of different bottlenecks, but it's the data movement itself. It's moving away from, wait, why do we need to move the data? Can we move the compute, the processing closer to the data? Because if we keep them separate and this has been a trend now where people are moving processing away from it. It's like the edge. I think it was Zeus or David. You were talking about the edge earlier. As you look at the edge, who defines the edge, right? Is the edge a closet or is it a sensor? If it's a sensor, how do you do AI at the edge? When you don't have enough power, you don't have enough computable. People were inventing chips to do that. To do all that at the edge, to do AI within the sensor, instead of moving the data to a data center or a cloud to do the processing. Because the lag in latency is always limited by speed of light. How fast can you move the electrons? And all this interconnecting, all the processing, and all the improvement we're seeing in the PCIE bus from three, to four, to five, to CXL, to a higher bandwidth on the network. And that's all great but none of that deals with the speed of light latency. And that's an-- Go ahead. >> You know Marc, no, I just want to just because what you're referring to could be looked at at a macro level, which I think is what you're describing. You can also look at it at a more micro level from a systems design perspective, right? I'm going to be the resident knuckle dragging hardware guy on the panel today. But it's exactly right. You moving compute closer to data includes concepts like peripheral cards that have built in intelligence, right? So again, in some of this testing that I'm referring to, we saw dramatic improvements when you basically took the horsepower instead of using the CPU horsepower for the like IO. Now you have essentially offload engines in the form of storage controllers, rate controllers, of course, for ethernet NICs, smart NICs. And so when you can have these sort of offload engines and we've gone through these waves over time. People think, well, wait a minute, raid controller and NVMe? You know, flash storage devices. Does that make sense? It turns out it does. Why? Because you're actually at a micro level doing exactly what you're referring to. You're bringing compute closer to the data. Now, closer to the data meaning closer to the data storage subsystem. It doesn't solve the macro issue that you're referring to but it is important. Again, going back to this idea of system design optimization, always chasing the bottleneck, plugging the holes. Someone needs to do that in this value chain in order to get the best value for every kilowatt hour of power and every dollar. >> Yeah. >> Well this whole drive performance has created some really interesting architectural designs, right? Like Nickelson, the rise of the DPU right? Brings more processing power into systems that already had a lot of processing power. There's also been some really interesting, you know, kind of innovation in the area of systems architecture too. If you look at the way Nvidia goes to market, their drive kit is a prebuilt piece of hardware, you know, optimized for self-driving cars, right? They partnered with Pure Storage and ARISTA to build that AI-ready infrastructure. I remember when I talked to Charlie Giancarlo, the CEO of Pure about when the three companies rolled that out. He said, "Look, if you're going to do AI, "you need good store. "You need fast storage, fast processor and fast network." And so for customers to be able to put that together themselves was very, very difficult. There's a lot of software that needs tuning as well. So the three companies partner together to create a fully integrated turnkey hardware system with a bunch of optimized software that runs on it. And so in that case, in some ways the hardware was leading the software innovation. And so, the variety of different architectures we have today around hardware has really exploded. And I think it, part of the what Bob brought up at the beginning about the different chip design. >> Yeah, Bob talked about that earlier. Bob, I mean, most AI today is modeling, you know, and a lot of that's done in the cloud and it looks from my standpoint anyway that the future is going to be a lot of AI inferencing at the edge. And that's a radically different architecture, Bob, isn't it? >> It is, it's a completely different architecture. And just to follow up on a couple points, excellent conversation guys. Dave talked about system architecture and really this that's what this boils down to, right? But it's looking at architecture at every level. I was talking about the individual different components the new interconnect methods. There's this new thing called UCIE universal connection. I forget what it stands answer for, but it's a mechanism for doing chiplet architectures, but then again, you have to take it up to the system level, 'cause it's all fine and good. If you have this SOC that's tuned and optimized, but it has to talk to the rest of the system. And that's where you see other issues. And you've seen things like CXL and other interconnect standards, you know, and nobody likes to talk about interconnect 'cause it's really wonky and really technical and not that sexy, but at the end of the day it's incredibly important exactly. To the other points that were being raised like mark raised, for example, about getting that compute closer to where the data is and that's where again, a diversity of chip architectures help and exactly to your last comment there Dave, putting that ability in an edge device is really at the cutting edge of what we're seeing on a semiconductor design and the ability to, for example, maybe it's an FPGA, maybe it's a dedicated AI chip. It's another kind of chip architecture that's being created to do that inferencing on the edge. Because again, it's that the cost and the challenges of moving lots of data, whether it be from say a smartphone to a cloud-based application or whether it be from a private network to a cloud or any other kinds of permutations we can think of really matters. And the other thing is we're tackling bigger problems. So architecturally, not even just architecturally within a system, but when we think about DPUs and the sort of the east west data center movement conversation that we hear Nvidia and others talk about, it's about combining multiple sets of these systems to function together more efficiently again with even bigger sets of data. So really is about tackling where the processing is needed, having the interconnect and the ability to get where the data you need to the right place at the right time. And because those needs are diversifying, we're just going to continue to see an explosion of different choices and options, which is going to make hardware even more essential I would argue than it is today. And so I think what we're going to see not only does hardware matter, it's going to matter even more in the future than it does now. >> Great, yeah. Great discussion, guys. I want to bring Keith back into the conversation here. Keith, if your main expertise in tech is provisioning LUNs, you probably you want to look for another job. So maybe clearly hardware matters, but with software defined everything, do people with hardware expertise matter outside of for instance, component manufacturers or cloud companies? I mean, VMware certainly changed the dynamic in servers. Dell just spun off its most profitable asset and VMware. So it obviously thinks hardware can stand alone. How does an enterprise architect view the shift to software defined hyperscale cloud and how do you see the shifting demand for skills in enterprise IT? >> So I love the question and I'll take a different view of it. If you're a data analyst and your primary value add is that you do ETL transformation, talk to a CDO, a chief data officer over midsize bank a little bit ago. He said 80% of his data scientists' time is done on ETL. Super not value ad. He wants his data scientists to do data science work. Chances are if your only value is that you do LUN provisioning, then you probably don't have a job now. The technologies have gotten much more intelligent. As infrastructure pros, we want to give infrastructure pros the opportunities to shine and I think the software defined nature and the automation that we're seeing vendors undertake, whether it's Dell, HP, Lenovo take your pick that Pure Storage, NetApp that are doing the automation and the ML needed so that these practitioners don't spend 80% of their time doing LUN provisioning and focusing on their true expertise, which is ensuring that data is stored. Data is retrievable, data's protected, et cetera. I think the shift is to focus on that part of the job that you're ensuring no matter where the data's at, because as my data is spread across the enterprise hybrid different types, you know, Dave, you talk about the super cloud a lot. If my data is in the super cloud, protecting that data and securing that data becomes much more complicated when than when it was me just procuring or provisioning LUNs. So when you say, where should the shift be, or look be, you know, focusing on the real value, which is making sure that customers can access data, can recover data, can get data at performance levels that they need within the price point. They need to get at those datasets and where they need it. We talked a lot about where they need out. One last point about this interconnecting. I have this vision and I think we all do of composable infrastructure. This idea that scaled out does not solve every problem. The cloud can give me infinite scale out. Sometimes I just need a single OS with 64 terabytes of RAM and 204 GPUs or GPU instances that single OS does not exist today. And the opportunity is to create composable infrastructure so that we solve a lot of these problems that just simply don't scale out. >> You know, wow. So many interesting points there. I had just interviewed Zhamak Dehghani, who's the founder of Data Mesh last week. And she made a really interesting point. She said, "Think about, we have separate stacks. "We have an application stack and we have "a data pipeline stack and the transaction systems, "the transaction database, we extract data from that," to your point, "We ETL it in, you know, it takes forever. "And then we have this separate sort of data stack." If we're going to inject more intelligence and data and AI into applications, those two stacks, her contention is they have to come together. And when you think about, you know, super cloud bringing compute to data, that was what Haduck was supposed to be. It ended up all sort of going into a central location, but it's almost a rhetorical question. I mean, it seems that that necessitates new thinking around hardware architectures as it kind of everything's the edge. And the other point is to your point, Keith, it's really hard to secure that. So when you can think about offloads, right, you've heard the stats, you know, Nvidia talks about it. Broadcom talks about it that, you know, that 30%, 25 to 30% of the CPU cycles are wasted on doing things like storage offloads, or networking or security. It seems like maybe Zeus you have a comment on this. It seems like new architectures need to come other to support, you know, all of that stuff that Keith and I just dispute. >> Yeah, and by the way, I do want to Keith, the question you just asked. Keith, it's the point I made at the beginning too about engineers do need to be more software-centric, right? They do need to have better software skills. In fact, I remember talking to Cisco about this last year when they surveyed their engineer base, only about a third of 'em had ever made an API call, which you know that that kind of shows this big skillset change, you know, that has to come. But on the point of architectures, I think the big change here is edge because it brings in distributed compute models. Historically, when you think about compute, even with multi-cloud, we never really had multi-cloud. We'd use multiple centralized clouds, but compute was always centralized, right? It was in a branch office, in a data center, in a cloud. With edge what we creates is the rise of distributed computing where we'll have an application that actually accesses different resources and at different edge locations. And I think Marc, you were talking about this, like the edge could be in your IoT device. It could be your campus edge. It could be cellular edge, it could be your car, right? And so we need to start thinkin' about how our applications interact with all those different parts of that edge ecosystem, you know, to create a single experience. The consumer apps, a lot of consumer apps largely works that way. If you think of like app like Uber, right? It pulls in information from all kinds of different edge application, edge services. And, you know, it creates pretty cool experience. We're just starting to get to that point in the business world now. There's a lot of security implications and things like that, but I do think it drives more architectural decisions to be made about how I deploy what data where and where I do my processing, where I do my AI and things like that. It actually makes the world more complicated. In some ways we can do so much more with it, but I think it does drive us more towards turnkey systems, at least initially in order to, you know, ensure performance and security. >> Right. Marc, I wanted to go to you. You had indicated to me that you wanted to chat about this a little bit. You've written quite a bit about the integration of hardware and software. You know, we've watched Oracle's move from, you know, buying Sun and then basically using that in a highly differentiated approach. Engineered systems. What's your take on all that? I know you also have some thoughts on the shift from CapEx to OPEX chime in on that. >> Sure. When you look at it, there are advantages to having one vendor who has the software and hardware. They can synergistically make them work together that you can't do in a commodity basis. If you own the software and somebody else has the hardware, I'll give you an example would be Oracle. As you talked about with their exit data platform, they literally are leveraging microcode in the Intel chips. And now in AMD chips and all the way down to Optane, they make basically AMD database servers work with Optane memory PMM in their storage systems, not MVME, SSD PMM. I'm talking about the cards itself. So there are advantages you can take advantage of if you own the stack, as you were putting out earlier, Dave, of both the software and the hardware. Okay, that's great. But on the other side of that, that tends to give you better performance, but it tends to cost a little more. On the commodity side it costs less but you get less performance. What Zeus had said earlier, it depends where you're running your application. How much performance do you need? What kind of performance do you need? One of the things about moving to the edge and I'll get to the OPEX CapEx in a second. One of the issues about moving to the edge is what kind of processing do you need? If you're running in a CCTV camera on top of a traffic light, how much power do you have? How much cooling do you have that you can run this? And more importantly, do you have to take the data you're getting and move it somewhere else and get processed and the information is sent back? I mean, there are companies out there like Brain Chip that have developed AI chips that can run on the sensor without a CPU. Without any additional memory. So, I mean, there's innovation going on to deal with this question of data movement. There's companies out there like Tachyon that are combining GPUs, CPUs, and DPUs in a single chip. Think of it as super composable architecture. They're looking at being able to do more in less. On the OPEX and CapEx issue. >> Hold that thought, hold that thought on the OPEX CapEx, 'cause we're running out of time and maybe you can wrap on that. I just wanted to pick up on something you said about the integrated hardware software. I mean, other than the fact that, you know, Michael Dell unlocked whatever $40 billion for himself and Silverlake, I was always a fan of a spin in with VMware basically become the Oracle of hardware. Now I know it would've been a nightmare for the ecosystem and culturally, they probably would've had a VMware brain drain, but what does anybody have any thoughts on that as a sort of a thought exercise? I was always a fan of that on paper. >> I got to eat a little crow. I did not like the Dale VMware acquisition for the industry in general. And I think it hurt the industry in general, HPE, Cisco walked away a little bit from that VMware relationship. But when I talked to customers, they loved it. You know, I got to be honest. They absolutely loved the integration. The VxRail, VxRack solution exploded. Nutanix became kind of a afterthought when it came to competing. So that spin in, when we talk about the ability to innovate and the ability to create solutions that you just simply can't create because you don't have the full stack. Dell was well positioned to do that with a potential span in of VMware. >> Yeah, we're going to be-- Go ahead please. >> Yeah, in fact, I think you're right, Keith, it was terrible for the industry. Great for Dell. And I remember talking to Chad Sakac when he was running, you know, VCE, which became Rack and Rail, their ability to stay in lockstep with what VMware was doing. What was the number one workload running on hyperconverged forever? It was VMware. So their ability to remain in lockstep with VMware gave them a huge competitive advantage. And Dell came out of nowhere in, you know, the hyper-converged market and just started taking share because of that relationship. So, you know, this sort I guess it's, you know, from a Dell perspective I thought it gave them a pretty big advantage that they didn't really exploit across their other properties, right? Networking and service and things like they could have given the dominance that VMware had. From an industry perspective though, I do think it's better to have them be coupled. So. >> I agree. I mean, they could. I think they could have dominated in super cloud and maybe they would become the next Oracle where everybody hates 'em, but they kick ass. But guys. We got to wrap up here. And so what I'm going to ask you is I'm going to go and reverse the order this time, you know, big takeaways from this conversation today, which guys by the way, I can't thank you enough phenomenal insights, but big takeaways, any final thoughts, any research that you're working on that you want highlight or you know, what you look for in the future? Try to keep it brief. We'll go in reverse order. Maybe Marc, you could start us off please. >> Sure, on the research front, I'm working on a total cost of ownership of an integrated database analytics machine learning versus separate services. On the other aspect that I would wanted to chat about real quickly, OPEX versus CapEx, the cloud changed the market perception of hardware in the sense that you can use hardware or buy hardware like you do software. As you use it, pay for what you use in arrears. The good thing about that is you're only paying for what you use, period. You're not for what you don't use. I mean, it's compute time, everything else. The bad side about that is you have no predictability in your bill. It's elastic, but every user I've talked to says every month it's different. And from a budgeting perspective, it's very hard to set up your budget year to year and it's causing a lot of nightmares. So it's just something to be aware of. From a CapEx perspective, you have no more CapEx if you're using that kind of base system but you lose a certain amount of control as well. So ultimately that's some of the issues. But my biggest point, my biggest takeaway from this is the biggest issue right now that everybody I talk to in some shape or form it comes down to data movement whether it be ETLs that you talked about Keith or other aspects moving it between hybrid locations, moving it within a system, moving it within a chip. All those are key issues. >> Great, thank you. Okay, CTO advisor, give us your final thoughts. >> All right. Really, really great commentary. Again, I'm going to point back to us taking the walk that our customers are taking, which is trying to do this conversion of all primary data center to a hybrid of which I have this hard earned philosophy that enterprise IT is additive. When we add a service, we rarely subtract a service. So the landscape and service area what we support has to grow. So our research focuses on taking that walk. We are taking a monolithic application, decomposing that to containers, and putting that in a public cloud, and connecting that back private data center and telling that story and walking that walk with our customers. This has been a super enlightening panel. >> Yeah, thank you. Real, real different world coming. David Nicholson, please. >> You know, it really hearkens back to the beginning of the conversation. You talked about momentum in the direction of cloud. I'm sort of spending my time under the hood, getting grease under my fingernails, focusing on where still the lions share of spend will be in coming years, which is OnPrem. And then of course, obviously data center infrastructure for cloud but really diving under the covers and helping folks understand the ramifications of movement between generations of CPU architecture. I know we all know Sapphire Rapids pushed into the future. When's the next Intel release coming? Who knows? We think, you know, in 2023. There have been a lot of people standing by from a practitioner's standpoint asking, well, what do I do between now and then? Does it make sense to upgrade bits and pieces of hardware or go from a last generation to a current generation when we know the next generation is coming? And so I've been very, very focused on looking at how these connectivity components like rate controllers and NICs. I know it's not as sexy as talking about cloud but just how these opponents completely change the game and actually can justify movement from say a 14th-generation architecture to a 15th-generation architecture today, even though gen 16 is coming, let's say 12 months from now. So that's where I am. Keep my phone number in the Rolodex. I literally reference Rolodex intentionally because like I said, I'm in there under the hood and it's not as sexy. But yeah, so that's what I'm focused on Dave. >> Well, you know, to paraphrase it, maybe derivative paraphrase of, you know, Larry Ellison's rant on what is cloud? It's operating systems and databases, et cetera. Rate controllers and NICs live inside of clouds. All right. You know, one of the reasons I love working with you guys is 'cause have such a wide observation space and Zeus Kerravala you, of all people, you know you have your fingers in a lot of pies. So give us your final thoughts. >> Yeah, I'm not a propeller heady as my chip counterparts here. (all laugh) So, you know, I look at the world a little differently and a lot of my research I'm doing now is the impact that distributed computing has on customer employee experiences, right? You talk to every business and how the experiences they deliver to their customers is really differentiating how they go to market. And so they're looking at these different ways of feeding up data and analytics and things like that in different places. And I think this is going to have a really profound impact on enterprise IT architecture. We're putting more data, more compute in more places all the way down to like little micro edges and retailers and things like that. And so we need the variety. Historically, if you think back to when I was in IT you know, pre-Y2K, we didn't have a lot of choice in things, right? We had a server that was rack mount or standup, right? And there wasn't a whole lot of, you know, differences in choice. But today we can deploy, you know, these really high-performance compute systems on little blades inside servers or inside, you know, autonomous vehicles and things. I think the world from here gets... You know, just the choice of what we have and the way hardware and software works together is really going to, I think, change the world the way we do things. We're already seeing that, like I said, in the consumer world, right? There's so many things you can do from, you know, smart home perspective, you know, natural language processing, stuff like that. And it's starting to hit businesses now. So just wait and watch the next five years. >> Yeah, totally. The computing power at the edge is just going to be mind blowing. >> It's unbelievable what you can do at the edge. >> Yeah, yeah. Hey Z, I just want to say that we know you're not a propeller head and I for one would like to thank you for having your master's thesis hanging on the wall behind you 'cause we know that you studied basket weaving. >> I was actually a physics math major, so. >> Good man. Another math major. All right, Bob O'Donnell, you're going to bring us home. I mean, we've seen the importance of semiconductors and silicon in our everyday lives, but your last thoughts please. >> Sure and just to clarify, by the way I was a great books major and this was actually for my final paper. And so I was like philosophy and all that kind of stuff and literature but I still somehow got into tech. Look, it's been a great conversation and I want to pick up a little bit on a comment Zeus made, which is this it's the combination of the hardware and the software and coming together and the manner with which that needs to happen, I think is critically important. And the other thing is because of the diversity of the chip architectures and all those different pieces and elements, it's going to be how software tools evolve to adapt to that new world. So I look at things like what Intel's trying to do with oneAPI. You know, what Nvidia has done with CUDA. What other platform companies are trying to create tools that allow them to leverage the hardware, but also embrace the variety of hardware that is there. And so as those software development environments and software development tools evolve to take advantage of these new capabilities, that's going to open up a lot of interesting opportunities that can leverage all these new chip architectures. That can leverage all these new interconnects. That can leverage all these new system architectures and figure out ways to make that all happen, I think is going to be critically important. And then finally, I'll mention the research I'm actually currently working on is on private 5g and how companies are thinking about deploying private 5g and the potential for edge applications for that. So I'm doing a survey of several hundred us companies as we speak and really looking forward to getting that done in the next couple of weeks. >> Yeah, look forward to that. Guys, again, thank you so much. Outstanding conversation. Anybody going to be at Dell tech world in a couple of weeks? Bob's going to be there. Dave Nicholson. Well drinks on me and guys I really can't thank you enough for the insights and your participation today. Really appreciate it. Okay, and thank you for watching this special power panel episode of theCube Insights powered by ETR. Remember we publish each week on Siliconangle.com and wikibon.com. All these episodes they're available as podcasts. DM me or any of these guys. I'm at DVellante. You can email me at David.Vellante@siliconangle.com. Check out etr.ai for all the data. This is Dave Vellante. We'll see you next time. (upbeat music)

>>From around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome to cube three 60 fives coverage of the Accenture executive summit. Part of AWS reinvent. I'm your host Rebecca Knight. Today we are joined by a cube alum Karthik NurAin. He is Accenture senior managing director and lead Accenture cloud. First, welcome back to the show Karthik. >>Thank you. Thanks for having me here. >>Always a pleasure. So I want to talk to you. You are an industry veteran, you've been in Silicon Valley for decades. Um, I want to hear from your perspective what the impact of the COVID-19 pandemic has been, what are you hearing from clients? What are they struggling with? What are their challenges that they're facing day to day? >>I think, um, COVID-19 is being a eye-opener from, you know, various facets, you know, um, first and foremost, it's a, it's a head, um, situation that everybody's facing, which is not just, uh, highest economic bearings to it. It has enterprise, um, an organization with bedding to it. And most importantly, it's very personal to people, um, because they themselves and their friends, family near and dear ones are going to this challenge, uh, from various different dimension. But putting that aside, when you come to it from an organization enterprise standpoint, it has changed everything well, the behavior of organizations coming together, working in their campuses, working with each other as friends, family, and, uh, um, near and dear colleagues, all of them are operating differently. So that's what big change to get things done in a completely different way, from how they used to get things done. >>Number two, a lot of things that were planned for normal scenarios, like their global supply chain, how they interact with their client customers, how they coordinate with their partners on how that employees contribute to the success of an organization at all changed. And there are no data models that give them a hint of something like this for them to be prepared for this. So we are seeing organizations, um, that have adapted to this reasonably okay, and are, you know, launching to innovate faster in this. And there are organizations that have started with struggling, but are continuing to struggle. And the gap, uh, between the leaders and legs are widening. So this is creating opportunities in a different way for the leaders, um, with a lot of pivot their business, but it's also creating significant challenge for the lag guides, uh, as we defined in our future systems research that we did a year ago, uh, and those organizations are struggling further. So the gap is actually whitening. >>So you've just talked about the widening gap. I've talked about the tremendous uncertainty that so many companies, even the ones who have adapted reasonably well, uh, in this, in this time, talk a little bit about Accenture cloud first and why, why now? >>I think it's a great question. Um, we believe that for many of our clients COVID-19 has turned, uh, cloud from an experimentation aspiration to an origin mandate. What I mean by that is everybody has been doing something on the other end cloud. There's no company that says we don't believe in cloud. Uh, our, we don't want to do cloud. It was how much they did in cloud. And they were experimenting. They were doing the new things in cloud. Um, but they were operating a lot of their core business outside the cloud or not in the cloud. Those organizations have struggled to operate in this new normal, in a remote fashion as with us, uh, that ability to pivot to all the changes the pandemic has brought to them. But on the other hand, the organizations that had a solid foundation in cloud were able to collect faster and not actually gone into the stage of innovating faster and driving a new behavior in the market, new behavior within their organization. >>So we are seeing that spend to make is actually fast-forwarded something that we always believed was going to happen. This, uh, uh, moving to cloud over the next decade is fast, forwarded it to, uh, happen in the next three to five years. And it's created this moment where it's a once in an era, really replatforming of businesses in the cloud that we are going to see. And we see this moment as a cloud first moment where organizations will use cloud as the, the canvas and the foundation with which they're going to reimagine their business after they were born in the cloud. Uh, and this requires a whole new strategy. Uh, and as Accenture, we are getting a lot in cloud, but we thought that this is the moment where we bring all of that capabilities together because we need a strategy for addressing, moving to cloud are embracing cloud in a holistic fashion. And that's what Accenture cloud first brings together a holistic strategy, a team that's 70,000 plus people that's coming together with rich cloud skills, but investing to tie in all the various capabilities of cloud to Delaware, that holistic strategy to our clients. So I want you to >>Delve into a little bit more about what this strategy actually entails. I mean, it's clearly about embracing change and being willing to experiment and, and having capabilities to innovate. Can you tell us a little bit more about what this strategy entails? >>Yeah. The reason why we say that there's a need for the strategy is, like I said, COVID is not new. There's almost every customer client is doing something with the cloud, but all of them have taken different approaches to cloud and different boundaries to cloud. Some organizations say, I just need to consolidate my multiple data centers to a small data center footprint and move the nest to cloud. Certain other organizations say that well, I'm going to move certain workloads to cloud. Certain other organizations said, well, I'm going to build this Greenfield application or workload in cloud. Certain other said, um, I'm going to use the power of AI ML in the cloud to analyze my data and drive insights. But a cloud first strategy is all of this tied with the corporate strategy of the organization with an industry specific cloud journey to say, if in this current industry, if I were to be reborn in the cloud, would I do it in the exact same passion that I did in the past, which means that the products and services that they offer need to be the matching, how they interact with that customers and partners need to be revisited, how they bird and operate their IP systems need to be the, imagine how they unearthed the data from all the systems under which they attract need to be liberated so that you could drive insights of cloud. >>First strategy. Hans is a corporate wide strategy, and it's a C-suite responsibility. It doesn't take the ownership away from the CIO or CIO, but the CIO is, and CDI was felt that it was just their problem and they were to solve it. And everyone as being a customer, now, the center of gravity is elevated to it becoming a C-suite agenda on everybody's agenda, where probably the CDI is the instrument to execute that that's a holistic cloud-first strategy >>And it, and it's a strategy, but the way you're describing it, it sounds like it's also a mindset and an approach, as you were saying, this idea of being reborn in the cloud. So now how do I think about things? How do I communicate? How do I collaborate? How do I get done? What I need to get done. Talk a little bit about how this has changed, the way you support your clients and how Accenture cloud first is changing your approach to cloud services. >>Wonderful. Um, you know, I did not color one very important aspect in my previous question, but that's exactly what you just asked me now, which is to do all of this. I talked about all of the vehicles, uh, an organization or an enterprise is going to go to, but the good part is they have one constant. And what is that? That is their employees, uh, because you do, the employees are able to embrace this change. If they are able to, uh, change them, says, pivot them says retool and train themselves to be able to operate in this new cloud. First one, the ability to reimagine every function of the business would be happening at speed. And cloud first approach is to do all of this at speed, because innovation is deadly proposed there, do the rate of probability on experimentation. You need to experiment a lot for any kind of experimentation. >>There's a probability of success. Organizations need to have an ability and a mechanism for them to be able to innovate faster for which they need to experiment a lot. The more the experiment and the lower cost at which they experiment is going to help them experiment a lot and experiment demic speed, fail fast, succeed more. And hence, they're going to be able to operate this at speed. So the cloud-first mindset is all about speed. I'm helping the clients fast track that innovation journey, and this is going to happen. Like I said, across the enterprise and every function across every department, I'm the agent of this change is going to be the employee's weapon, race, this change through new skills and new grueling and new mindset that they need to adapt to. >>So Karthik what you're describing it, it sounds so exciting. And yet for a pandemic wary workforce, that's been working remotely that may be dealing with uncertainty if for their kid's school and for so many other aspects of their life, it sounds hard. So how are you helping your clients, employees get onboard with this? And because the change management is, is often the hardest part. >>Yeah, I think it's, again, a great question. A bottle has only so much capacity. Something got to come off for something else to go in. That's what you're saying is absolutely right. And that is again, the power of cloud. The reason why cloud is such a fundamental breakthrough technology and capability for us to succeed in this era, because it helps in various forms. What we talked so far is the power of innovation that could create, but cloud can also simplify the life of the employees in an enterprise. There are several activities and tasks that people do in managing their complex infrastructure, complex ID landscape. They used to do certain jobs and activities in a very difficult, uh, underground about with cloud has simplified. And democratised a lot of these activities. So that things which had to be done in the past, like managing the complexity of the infrastructure, keeping them up all the time, managing the, um, the obsolescence of the capabilities and technologies and infrastructure, all of that could be offloaded to the cloud. >>So that the time that is available for all of these employees can be used to further innovate. Every organization is good to spend almost the same amount of money, but rather than spending activities, by looking at the rear view mirror on keeping the lights on, they're going to spend more money, more time, more energy, and spend their skills on things that are going to add value to their organization. Because you, every innovation that an enterprise can give to their end customer need not come from that enterprise. The word of platform economy is about democratising innovation. And the power of cloud is to get all of these capabilities from outside the four walls of the enterprise, >>It will add value to the organization, but I would imagine also add value to that employee's life because that employee, the employee will be more engaged in his or her job and therefore bring more excitement and energy into her, his or her day-to-day activities too. >>Absolutely. Absolutely. And this is, this is a normal evolution we would have seen everybody would have seen in their lives, that they keep moving up the value chain of what activities that, uh, gets performed buying by those individuals. And there's this, um, you know, no more true than how the United States, uh, as an economy has operated where, um, this is the power of a powerhouse of innovation, where the work that's done inside the country keeps moving up to that. You change. And, um, us leverages the global economy for a lot of things that is required to power the United States and that global economic, uh, phenomenon is very proof for an enterprise as well. There are things that an enterprise needs to do them soon. There are things an employee needs to do themselves. Um, but there are things that they could leverage from the external innovation and the power of innovation that is coming from technologies like cloud. >>So at Accenture, you have long, long, deep Stan, sorry, you have deep and long standing relationships with many cloud service providers, including AWS. How does the Accenture cloud first strategy, how does it affect your relationships with those providers? >>Yeah, we have great relationships with cloud providers like AWS. And in fact, in the cloud world, it was one of the first, um, capability that we started about years ago, uh, when we started developing these capabilities. But five years ago, we hit a very important milestone where the two organizations came together and said that we are forging a pharma partnership with joint investments to build this partnership. And we named that as a Accenture, AWS business group ABG, uh, where we co-invest and brought skills together and develop solutions. And we will continue to do that. And through that investment, we've also made several acquisitions that you would have seen in the recent times, like, uh, an invoice and gecko that we made acquisitions in in Europe. But now we're taking this to the next level. What we are saying is two cloud first and the $3 billion investment that we are bringing in, uh, through cloud first, we are going to make specific investment to create unique joint solution and landing zones foundation, um, cloud packs with which clients can accelerate their innovation or their journey to cloud first. >>And one great example is what we are doing with Takeda, uh, billable, pharmaceutical giant, um, between we've signed a five-year partnership. And it was out in the media just a month ago or so, where we are, the two organizations are coming together. We have created a partnership as a power of three partnership where the three organizations are jointly hoarding hats and taking responsibility for the innovation and the leadership position that Decatur wants to get to with this. We are going to simplify their operating model and organization by providing it flexibility. We're going to provide a lot more insights. Tequila has a 230 year old organization. Imagine the amount of trapped data and intelligence that is there. How about bringing all of that together with the power of AWS and Accenture and Takeda to drive more customer insights, um, come up with breakthrough, uh, R and D uh, accelerate clinical trials and improve the patient experience using AI ML and edge technologies. So all of these things that we will do through this partnership with joint investment from Accenture cloud first, as well as partner like AWS, so that Takeda can realize their gain. And, uh, they're seeing you actually made a statement that five years from now, every ticket an employee will have an AI assistant. That's going to make that beginner employee move up the value chain on how they contribute and add value to the future of tequila with the AI assistant, making them even more equipped and smarter than what they could be otherwise. >>So, one last question to close this out here. What is your future vision for, for Accenture cloud first? What are we going to be talking about at next year's Accenture executive summit? Yeah, the future >>Is going to be, um, evolving, but the part that is exciting to me, and this is, uh, uh, a fundamental belief that we are entering a new era of industrial revolution from industry first, second, and third industry. The third happened probably 20 years ago with the advent of Silicon and computers and all of that stuff that happened here in the Silicon Valley. I think the fourth industrial revolution is going to be in the cross section of, uh, physical, digital and biological boundaries. And there's a great article, um, in what economic forum that, that people, uh, your audience can Google and read about it. Uh, but the reason why this is very, very important is we are seeing a disturbing phenomenon that over the last 10 years, they are seeing a Blackwing of the, um, labor productivity and innovation, which has dropped to about 2.1%. When you see that kind of phenomenon over that longer period of time, there has to be breakthrough innovation that needs to happen to come out of this barrier and get to the next base camp, as I would call it to further this productivity, um, lack that we are seeing, and that is going to happen in the intersection of the physical, digital and biological boundaries. >>And I think cloud is going to be the connective tissue between all of these three, to be able to provide that where it's the edge, especially is going to come closer to the human lives. It's going to come from cloud pick totally in your mind, you can think about cloud as central, either in a private cloud, in a data center or in a public cloud, you know, everywhere. But when you think about edge, it's going to be far reaching and coming close to where we live and maybe work and very, um, get entertained and so on and so forth. And there's going to be, uh, intervention in a positive way in the field of medicine, in the field of entertainment, in the field of, um, manufacturing in the field of, um, uh, you know, mobility. When I say mobility, human mobility, people, transportation, and so on and so forth with all of this stuff, cloud is going to be the connective tissue and the vision of cloud first is going to be, uh, you know, blowing through this big change that is going to happen. And the evolution that is going to happen where, you know, the human grace of mankind, um, our person kind of being very gender neutral in today's world. Um, go first needs to be that beacon of, uh, creating the next generation vision for enterprises to take advantage of that kind of an exciting future. And that's why it, Accenture. We say, let there be change as our, as a purpose. >>I genuinely believe that cloud first is going to be in the forefront of that change agenda, both for Accenture as well as for the rest of the world. Excellent. Let there be change, indeed. Thank you so much for joining us Karthik. A pleasure I'm Rebecca night's stay tuned for more of Q3 60 fives coverage of the Accenture executive summit >>From around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS >>Welcome everyone to the Q virtual and our coverage of the Accenture executive summit, which is part of AWS reinvent 2020. I'm your host Rebecca Knight. Today, we are talking about the green, the cloud and joining me is Kishor Dirk. He is Accenture senior managing director cloud first global services lead. Thank you so much for coming on the show. Kishor nice to meet you. So I want to start by asking you what it is that we mean when we say green cloud, we know that sustainability is a business imperative. So many organizations around the world are committing to responsible innovation, lowering carbon emissions, but what's this, what is it? What does it mean when they talk about cloud from a sustainability perspective? I think it's about responsible innovation being cloud is a cloud first approach that has profits and benefit the clients by helping reduce carbon emissions. >>Think about it this way. You have a large number of data centers. Each of these data centers are increasing by 14% every year. And this double digit growth. What you're seeing is these data centers and the consumption is nearly coolant to the kind of them should have a country like Spain. So the magnitude of the problem that is out there and how do we pursue a green approach. If you look at this, our Accenture analysis, in terms of the migration to public cloud, we've seen that we can reduce that by 59 million tons of CO2 per year with just the 5.9% reduction in total ID emissions and equates this to 22 million cars off the road. And the magnitude of reduction can go a long way in meeting climate change commitments, particularly for data sensitive. >>Wow, that's incredible. What the numbers that you're putting forward are, are absolutely mind blowing. So how does it work? Is it a simple cloud migration? So, you know, when companies begin their cloud journey and then they confront, uh, with them a lot of questions, the decision to make, uh, this particular, uh, element sustainable in the solution and benefits they drive and they have to make wise choices, and then they will be unprecedented level of innovation leading to both a greener planet, as well as, uh, a greener balance sheet, I would say, uh, so effectively it's all about ambition data, the ambition, greater the reduction in carbon emissions. So from a cloud migration perspective, we look at it as a, as a simple solution with approaches and sustainability benefits, uh, that vary based on things it's about selecting the right cloud provider, a very carbon thoughtful provider and the first step towards a sustainable cloud journey. >>And here we're looking at cloud operators, obviously they have different corporate commitments towards sustainability, and that determines how they plan, how they build, uh, their, uh, uh, the data centers, how they are consumed and assumptions that operate there and how they, or they retire their data centers. Then, uh, the next element that you want to do is how do you build it ambition, you know, for some of the companies, uh, and average on-prem, uh, drives about 65% energy reduction and the carbon emissions and reduction number was 84%, which is kind of good, I would say. But then if you could go up to 98% by configuring applications to the cloud, that is significant benefit for, uh, for the board. And obviously it's a, a greener cloud that we're talking about. And then the question is, how far can you go? And, uh, you know, the, obviously the companies have to unlock greater financial societal environmental benefits, and Accenture has this cloud based circular operations and sustainable products and services that we bring into play. So it's a, it's a very thoughtful, broader approach that w bringing in, in terms of, uh, just a simple concept of cloud migration, >>We know that in the COVID era, shifting to the cloud has really become a business imperative. How is Accenture working with its clients at a time when all of this movement has been accelerated? How do you partner and what is your approach in terms of helping them with their migration? >>Yeah, I mean, let, let me talk a little bit about the pandemic and the crisis that is there today. And if you really look at that in terms of how we partnered with a lot of our clients in terms of the cloud first approach, I'll give you a couple of examples. We worked with rolls Royce, McLaren, DHL, and others, as part of the ventilator challenge consortium, again, to, uh, coordinate production of medical ventilator surgically needed for the UK health service. Many of these farms I've taken similar initiatives in, in terms of, uh, you know, from a few manufacturers hand sanitizers and to hand sanitizers, and again, leading passionate labels, making PPE, and again, at the UN general assembly, we launched the end-to-end integration guide that helps company essentially to have a sustainable development goals. And that's how we have parking at a very large scale. >>Uh, and, and if you really look at how we work with our clients and what is Accenture's role there, uh, you know, from, in terms of our clients, you know, there are multiple steps that we look at. One is about, uh, planning, building, deploying, and managing an optimal green cloud solution. And Accenture has this concept of, uh, helping clients with a platform to kind of achieve that goal. And here we are having, we are having a platform or a mine app, which has a module called BGR advisor. And this is a capability that helps you provide optimal green cloud, uh, you know, a business case, and obviously a blueprint for each of our clients and right from the start in terms of how do we complete cloud migration recommendation to an improved solution, accurate accuracy to obviously bringing in the end to end perspective, uh, you know, with this green card advisor capability, we're helping our clients capture what we call as a carbon footprint for existing data centers and provide, uh, I would say the current cloud CO2 emission score that, you know, obviously helps them, uh, with carbon credits that can further that green agenda. >>So essentially this is about recommending a green index score, reducing carbon footprint for migration migrating for green cloud. And if we look at how Accenture itself is practicing what we preach, 95% of our applications are in the cloud. And this migration has helped us, uh, to lead to about $14.5 million in benefit. And in the third year and another 3 million analytics costs that are saved through right-sizing a service consumption. So it's a very broad umbrella and a footprint in terms of how we engage societaly with the UN or our clients. And what is it that we exactly bring to our clients in solving a specific problem? >>Accenture isn't is walking the walk, as you say yes. >>So that's that instead of it, we practice what we preach, and that is something that we take it to heart. We want to have a responsible business and we want to practice it. And we want to advise our clients around that >>You are your own use case. And so they can, they know they can take your advice. So talk a little bit about, um, the global, the cooperation that's needed. We know that conquering this pandemic is going to take a coordinated global effort and talk a little bit about the great reset initiative. First of all, what is that? Why don't we, why don't we start there and then we can delve into it a little bit more. >>Okay. So before we get to how we are cooperating, the great reset, uh, initiative is about improving the state of the world. And it's about a group of global stakeholders cooperating to simultaneously manage the direct consequences of their COVID-19 crisis. Uh, and in spirit of this cooperation that we're seeing during COVID-19, uh, which will obviously either to post pandemic, to tackle the world's pressing issues. As I say, uh, we are increasing companies to realize a combined potential of technology and sustainable impact to use enterprise solutions, to address with urgency and scale, and, um, obviously, uh, multiple challenges that are facing our world. One of the ways that you're increasing, uh, companies to reach their readiness cloud with Accenture's cloud core strategy is to build a solid foundation that is resilient and will be able to faster to the current, as well as future times. Now, when you think of cloud as the foundation, uh, that drives the digital transformation, it's about scale speed, streamlining your operations, and obviously reducing costs. >>And as these businesses seize the construct of cloud first, they must remain obviously responsible and trusted. Now think about this, right, as part of our analysis, uh, that profitability can co-exist with responsible and sustainable practices. Let's say that all the data centers, uh, migrated from on-prem to cloud based, we estimate that would reduce carbon emissions globally by 60 million tons per year. Uh, and think about it this way, right? Easier metric would be taking out 22 million cars off the road. Um, the other examples that you've seen, right, in terms of the NHS work that they're doing, uh, in, in UK to build, uh, uh, you know, uh, Microsoft teams in based integration. And, uh, the platform rolled out for 1.2 million in interest users, uh, and got 16,000 users that we were able to secure, uh, instant messages, obviously complete audio video calls and host virtual meetings across India. So, uh, this, this work that we did with NHS is something that we have are collaborating with a lot of tools and powering businesses. >>Well, you're vividly describing the business case for sustainability. What do you see as the future of cloud when thinking about it from this lens of sustainability, and also going back to what you were talking about in terms of how you are helping your, your fostering cooperation within these organizations. >>Yeah, that's a very good question. So if you look at today, right, businesses are obviously environmentally aware and they are expanding efforts to decrease power consumption, carbon emissions, and they want to run a sustainable operational efficiency across all elements of their business. And this is an increasing trend, and there is that option of energy efficient infrastructure in the global market. And this trend is the cloud first thinking. And with the right cloud migration that we've been discussing is about unlocking new opportunity, like clean energy foundations enable enabled by cloud based geographic analysis, material, waste reductions, and better data insights. And this is something that, uh, uh, we'll we'll drive, uh, with obviously faster analytics platform that is out there. Now, the sustainability is actually the future of business, which is companies that are historically different, the financial security or agility benefits to cloud. Now sustainability becomes an imperative for them. And I would on expedience Accenture's experience with cloud migrations, we have seen 30 to 40% total cost of ownership savings. And it's driving a greater workload, flexibility, better service, your obligation, and obviously more energy efficient, uh, public clouds that cost we'll see that, that drive a lot of these enterprise own data centers. So in our view, what we are seeing is that this, this, uh, sustainable cloud position helps, uh, helps companies to, uh, drive a lot of the goals in addition to their financial and other goods. >>So what should organizations who are, who are watching this interview and saying, Hey, I need to know more, what, what do you recommend to them? And what, where should they go to get more information on Greenplum? >>No, if you you're, if you are a business leader and you're thinking about which cloud provider is good, or how, how should applications be modernized to meet our day-to-day needs, which cloud driven innovations should be priorities. Uh, you know, that's why Accenture, uh, formed up the cloud first organization and essentially to provide the full stack of cloud services to help our clients become a cloud first business. Um, you know, it's all about excavation, uh, the digital transformation innovating faster, creating differentiated, uh, and sustainable value for our clients. And we're powering it up at 70,000 cloud professionals, $3 billion investment, and, uh, bringing together and services for our clients in terms of cloud solutions. And obviously the ecosystem partnership that we have that we are seeing today, uh, and the assets that help our clients realize their goals. Um, and again, to do reach out to us, uh, we can help them determine obviously, an optimal, sustainable cloud for solution that meets the business needs and being unprecedented levels of innovation. Our experience will be our advantage. And now more than ever, Rebecca, >>Just closing us out here. Do you have any advice for these companies who are navigating a great deal of uncertainty? We, what, what do you think the next 12 to 24 months? What do you think that should be on the minds of CEOs as they go through? >>So, as CEO's are thinking about rapidly leveraging cloud, migrating to cloud, uh, one of the elements that we want them to be thoughtful about is can they do that, uh, with unprecedent level of innovation, but also build a greener planet and a greener balance sheet, if we can achieve this balance and kind of, uh, have a, have a world which is greener, I think the world will win. And we all along with Accenture clients will win. That's what I would say, uh, >>Optimistic outlook. And I will take it. Thank you so much. Kishor for coming on the show >>That was >>Accenture's Kishor Dirk, I'm Rebecca Knight stay tuned for more of the cube virtuals coverage of the Accenture executive summit >>Around the globe. >>It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome everyone to the cube virtual and our coverage of the Accenture executive summit. Part of AWS reinvent 2020. I'm your host Rebecca Knight. Today, we are talking about the power of three. And what happens when you bring together the scientific know-how of a global bias biopharmaceutical powerhouse in Takeda, a leading cloud services provider in AWS, and Accenture's ability to innovate, execute, and deliver innovation. Joining me to talk about these things. We have Aaron, sorry, Arjun, baby. He is the senior managing director and chairman of Accenture's diamond leadership council. Welcome Arjun Karl hick. He is the chief digital and information officer at Takeda. >>What is your bigger, thank you, Rebecca >>And Brian bowhead, global director, and head of the Accenture AWS business group at Amazon web services. Thanks so much for coming on. Thank you. So, as I said, we're talking today about this relationship between, uh, your three organizations. Carl, I want to talk with you. I know you're at the beginning of your cloud journey. What was the compelling reason? What, what, why, why move to the cloud and why now? >>Yeah, no, thank you for the question. So, you know, as a biopharmaceutical leader, we're committed to bringing better health and a brighter future to our patients. We're doing that by translating science into some really innovative and life transporting therapies, but throughout, you know, we believe that there's a responsible use of technology, of data and of innovation. And those three ingredients are really key to helping us deliver on that promise. And so, you know, while I think, uh, I'll call it, this cloud journey is already always been a part of our strategy. Um, and we've made some pretty steady progress over the last years with a number of I'll call it diverse approaches to the digital and AI. We just weren't seeing the impact at scale that we wanted to see. Um, and I think that, you know, there's a, there's a need ultimately to, you know, accelerate and, uh, broaden that shift. >>And, you know, we were commenting on this earlier, but there's, you know, it's been highlighted by a number of factors. One of those has been certainly a number of the large acquisitions we've made Shire, uh, being the most pressing example, uh, but also the global pandemic, both of those highlight the need for us to move faster, um, at the speed of cloud, ultimately. Uh, and so we started thinking outside of the box because it was taking us too long and we decided to leverage this strategic partner model. Uh, and it's giving us a chance to think about our challenges very differently. We call this the power of three, uh, and ultimately our focus is singularly on our patients. I mean, they're waiting for us. We need to get there faster. It can take years. And so I think that there is a focus on innovation, um, at a rapid speed, so we can move ultimately from treating conditions to keeping people healthy. >>So as you are embarking on this journey, what are some of the insights you want to share about, about what you're seeing so far? >>Yeah, no, it's a great question. So, I mean, look, maybe right before I highlight some of the key insights, uh, I would say that, you know, with cloud now as the, as the launchpad for innovation, you know, our vision all along has been that in less than 10 years, we want every single to kid, uh, associate we're employed to be empowered by an AI assistant. And I think that, you know, that's going to help us make faster, better decisions. That'll help us, uh, fundamentally deliver transformative therapies and better experiences to, to that ecosystem, to our patients, to physicians, to payers, et cetera, much faster than we previously thought possible. Um, and I think that technologies like cloud and edge computing together with a very powerful I'll call it data fabric is going to help us to create this, this real-time, uh, I'll call it the digital ecosystem. >>The data has to flow ultimately seamlessly between our patients and providers or partners or researchers, et cetera. Uh, and so we've been thinking about this, uh, I'll call it legal, hold up, sort of this pyramid, um, that helps us describe our vision. Uh, and a lot of it has to do with ultimately modernizing the foundation, modernizing and rearchitecting, the platforms that drive the company, uh, heightening our focus on data, which means that there's an accelerated shift towards enterprise data platforms and digital products. And then ultimately, uh, uh, P you know, really an engine for innovation sitting at the very top. Um, and so I think with that, you know, there's a few different, uh, I'll call it insights that, you know, are quickly kind of come zooming into focus. I would say one is this need to collaborate very differently. Um, you know, not only internally, but you know, how do we define ultimately, and build a connected digital ecosystem with the right partners and technologies externally? >>I think the second, uh, component that maybe people don't think as much about, but, you know, I find critically important is for us to find ways of really transforming our culture. We have to unlock talent and shift the culture certainly as a large biopharmaceutical very differently. And then lastly, you've touched on it already, which is, you know, innovation at the speed of cloud. How do we re-imagine that, you know, how do ideas go from getting tested and months to kind of getting tested in days? You know, how do we collaborate very differently? Uh, and so I think those are three, uh, perhaps of the larger I'll call it, uh, insights that, you know, the three of us are spending a lot of time thinking about right now. >>So Arjun, I want to bring you into this conversation a little bit. Let's, let's delve into those a bit. Talk first about the collaboration, uh, that Carl was referencing there. How, how have you seen that it is enabling, uh, colleagues and teams to communicate differently and interact in new and different ways? Uh, both internally and externally, as Carl said, >>No, th thank you for that. And, um, I've got to give call a lot of credit, because as we started to think about this journey, it was clear, it was a bold ambition. It was, uh, something that, you know, we had all to do differently. And so the, the concept of the power of three that Carl has constructed has become a label for us as a way to think about what are we going to do to collectively drive this journey forward. And to me, the unique ways of collaboration means three things. The first one is that, um, what is expected is that the three parties are going to come together and it's more than just the sum of our resources. And by that, I mean that we have to bring all of ourselves, all of our collective capabilities, as an example, Amazon has amazing supply chain capabilities. >>They're one of the best at supply chain. So in addition to resources, when we have supply chain innovations, uh, that's something that they're bringing in addition to just, uh, talent and assets, similarly for Accenture, right? We do a lot, uh, in the talent space. So how do we bring our thinking as to how we apply best practices for talent to this partnership? So, um, as we think about this, so that's, that's the first one, the second one is about shared success very early on in this partnership, we started to build some foundations and actually develop seven principles that all of us would look at as the basis for this success shared success model. And we continue to hold that sort of in the forefront, as we think about this collaboration. And maybe the third thing I would say is this one team mindset. So whether it's the three of our CEOs that get together every couple of months to think about, uh, this partnership, or it is the governance model that Carl has put together, which has all three parties in the governance and every level of leadership, we always think about this as a collective group, so that we can keep that front and center. >>And what I think ultimately has enabled us to do is it allowed us to move at speed, be more flexible. And ultimately all we're looking at the target the same way, the North side, the same way. >>Brian, what about you? What have you observed and what are you thinking about in terms of how this is helping teams collaborate differently? >>Yeah, absolutely. And RJ made some, some great points there. And I think if you really think about what he's talking about, it's that, that diversity of talent, diversity of skill and viewpoint and even culture, right? And so we see that in the power of three. And then I think if we drill down into what we see at Takeda, and frankly, Takeda was, was really, I think, pretty visionary and on their way here, right. And taking this kind of cross-functional approach and applying it to how they operate day to day. So moving from a more functional view of the world to more of a product oriented view of the world, right? So when you think about we're going to be organized around a product or a service or a capability that we're going to provide to our customers or our patients or donors in this case, it implies a different structure, although altogether, and a different way of thinking, right? >>Because now you've got technical people and business experts and marketing experts, all working together in this is sort of cross collaboration. And what's great about that is it's really the only way to succeed with cloud, right? Because the old ways of thinking where you've got application people and infrastructure, people in business, people is suboptimal, right? Because we can all access this tool was, and these capabilities and the best way to do that, isn't across kind of a cross collaborative way. And so this is product oriented mindset. It's a keto was already on. I think it's allowed us to move faster in those areas. >>Carl, I want to go back to this idea of unlocking talent and culture. And this is something that both Brian and Arjun have talked about too. People are, are an essential part of their, at the heart of your organization. How will their experience of work change and how are you helping re-imagine and reinforce a strong organizational culture, particularly at this time when so many people are working remotely. >>Yeah. It's a great question. And it's something that, you know, I think we all have to think a lot about, I mean, I think, um, you know, driving this, this call it, this, this digital and data kind of capability building, uh, takes a lot of, a lot of thinking. So, I mean, there's a few different elements in terms of how we're tackling this one is we're recognizing, and it's not just for the technology organization or for those actors that, that we're innovating with, but it's really across all of the Cato where we're working through ways of raising what I'll call the overall digital leaders literacy of the organization, you know, what are the, you know, what are the skills that are needed almost at a baseline level, even for a global bio-pharmaceutical company and how do we deploy, I'll call it those learning resources very broadly. >>And then secondly, I think that, you know, we're, we're very clear that there's a number of areas where there are very specialized skills that are needed. Uh, my organization is one of those. And so, you know, we're fostering ways in which, you know, we're very kind of quickly kind of creating, uh, avenues excitement for, for associates in that space. So one example specifically, as we use, you know, during these very much sort of remote, uh, sort of days, we, we use what we call global it days, and we set a day aside every single month and this last Friday, um, you know, we, we create during that time, it's time for personal development. Um, and we provide active seminars and training on things like, you know, robotic process automation, data analytics cloud, uh, in this last month we've been doing this for months and months now, but in his last month, more than 50% of my organization participated, and there's this huge positive shift, both in terms of access and excitement about really harnessing those new skills and being able to apply them. >>Uh, and so I think that that's, you know, one, one element that, uh, can be considered. And then thirdly, um, of course, every organization to work on, how do you prioritize talent, acquisition and management and competencies that you can't rescale? I mean, there are just some new capabilities that we don't have. And so there's a large focus that I have with our executive team and our CEO and thinking through those critical roles that we need to activate in order to kind of, to, to build on this, uh, this business led cloud transformation. And lastly, probably the hardest one, but the one that I'm most jazzed about is really this focus on changing the mindsets and behaviors. Um, and I think there, you know, this is where the power of three is, is really, uh, kind of coming together nicely. I mean, we're working on things like, you know, how do we create this patient obsessed curiosity, um, and really kind of unlock innovation with a real, kind of a growth mindset. >>Uh, and the level of curiosity that's needed, not to just continue to do the same things, but to really challenge the status quo. So that's one big area of focus we're having the agility to act just faster. I mean, to worry less, I guess I would say about kind of the standard chain of command, but how do you make more speedy, more courageous decisions? And this is places where we can emulate the way that a partner like AWS works, or how do we collaborate across the number of boundaries, you know, and I think, uh, Arjun spoke eloquently to a number of partnerships that we can build. So we can break down some of these barriers and use these networks, um, whether it's within our own internal ecosystem or externally to help, to create value faster. So a lot of energy around ways of working and we'll have to check back in, but I mean, we're early in on this mindset and behavioral shift, um, but a lot of good early momentum. >>Carl you've given me a good segue to talk to Brian about innovation, because you said a lot of the things that I was the customer obsession and this idea of innovating much more quickly. Obviously now the world has its eyes on drug development, and we've all learned a lot about it, uh, in the past few months and accelerating drug development is all, uh, is of great interest to all of us. Brian, how does a transformation like this help a company's, uh, ability to become more agile and more innovative and at a quicker speed to, >>Yeah, no, absolutely. And I think some of the things that Carl talked about just now are critical to that, right? I think where sometimes folks fall short is they think, you know, we're going to roll out the technology and the technology is going to be the silver bullet where we're, in fact it is the culture. It is, is the talent. And it's the focus on that. That's going to be, you know, the determinant of success. And I will say, you know, in this power of three arrangement and Carl talked a little bit about the pyramid, um, talent and culture and that change, and the kind of thinking about that has been a first-class citizen since the very beginning, right. That absolutely is critical for, for being there. Um, and, and so that's been, that's been key. And so we think about innovation at Amazon and AWS, and Carl mentioned some of the things that, you know, partner like AWS can bring to the table is we talk a lot about builders, right? >>So kind of obsessive about builders. Um, and, and we meet what we mean by that is we at Amazon, we hire for builders, we cultivate builders and we like to talk to our customers about it as well. And it also implies a different mindset, right? When you're a builder, you have that, that curiosity, you have that ownership, you have that stake in whatever I'm creating, I'm going to be a co-owner of this product or this service, right. Getting back to that kind of product oriented mindset. And it's not just the technical people or the it people who are builders. It is also the business people as, as Carl talked about. Right. So when we start thinking about, um, innovation again, where we see folks kind of get into a little bit of a innovation pilot paralysis, is that you can focus on the technology, but if you're not focusing on the talent and the culture and the processes and the mechanisms, you're going to be putting out technology, but you're not going to have an organization that's ready to take it and scale it and accelerate it. >>Right. And so that's, that's been absolutely critical. So just a couple of things we've been doing with, with Takeda and Decatur has really been leading the way is, think about a mechanism and a process. And it's really been working backward from the customer, right? In this case, again, the patient and the donor. And that was an easy one because the key value of Decatur is to be a patient focused bio-pharmaceutical right. So that was embedded in their DNA. So that working back from that, that patient, that donor was a key part of that process. And that's really deep in our DNA as well. And Accenture's, and so we were able to bring that together. The other one is, is, is getting used to experimenting and even perhaps failing, right. And being able to iterate and fail fast and experiment and understanding that, you know, some decisions, what we call it at Amazon or two-way doors, meaning you can go through that door, not like what you see and turn around and go back. And cloud really helps there because the costs of experimenting and the cost of failure is so much lower than it's ever been. You can do it much faster and the implications are so much less. So just a couple of things that we've been really driving, uh, with the cadence around innovation, that's been really critical. Carl, where are you already seeing signs of success? >>Yeah, no, it's a great question. And so we chose, you know, uh, with our focus on innovation to try to unleash maybe the power of data digital in, uh, in focusing on what I call sort of a Maven. And so we chose our, our, our plasma derived therapy business, um, and you know, the plasma-derived therapy business unit, it develops critical life-saving therapies for patients with rare and complex diseases. Um, but what we're doing is by bringing kind of our energy together, we're focusing on creating, I'll call it state of the art digitally connected donation centers. And we're really modernizing, you know, the, the, the donor experience right now, we're trying to, uh, improve also I'll call it the overall plasma collection process. And so we've, uh, selected a number of alcohol at a very high speed pilots that we're working through right now, specifically in this, in this area. And we're seeing >>Really great results already. Um, and so that's, that's one specific area of focus are Jen, I want you to close this out here. Any ideas, any best practices advice you would have for other pharmaceutical companies that are, that are at the early stage of their cloud journey? Yes. Sorry. Arjun. >>Yeah, no, I was breaking up a bit. No, I think they, um, the key is what what's sort of been great for me to see is that when people think about cloud, you know, you always think about infrastructure technology. The reality is that the cloud is really the true enabler for innovation and innovating at scale. And, and if you think about that, right, in all the components that you need, uh, ultimately that's where the value is for the company, right? Because yes, you're going to get some cost synergies and that's great, but the true value is in how do we transform the organization in the case of the Qaeda and the life sciences clients, right. We're trying to take a 14 year process of research and development that takes billions of dollars and compress that right. Tremendous amounts of innovation opportunity. You think about the commercial aspect, lots of innovation can come there. The plasma derived therapy is a great example of how we're going to really innovate to change the trajectory of that business. So I think innovation is at the heart of what most organizations need to do. And the formula, the cocktail that Takeda has constructed with this Fuji program really has all the ingredients, um, that are required for that success. >>Great. Well, thank you so much. Arjun, Brian and Carl was really an enlightening conversation. >>Thank you. Yeah, it's been fun. Thanks Rebecca. >>And thank you for tuning into the cube. Virtual is coverage of the Accenture executive summit >>From around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome everyone to the cubes coverage of Accenture executive summit here at AWS reinvent. I'm your host Rebecca Knight for this segment? We have two guests. First. We have Helen Davis. She is the senior director of cloud platform services, assistant director for it and digital for the West Midlands police. Thanks so much for coming on the show, Helen, and we also have Matthew lb. He is Accenture health and public service associate director and West Midlands police account lead. Thanks so much for coming on the show. Matthew, thank you for joining us. So we are going to be talking about delivering data-driven insights to the West Midlands police force. Helen, I want to start with >>You. Can you tell us a little bit about the West Midlands police force? How big is the force and also what were some of the challenges that you were grappling with prior to this initiative? >>Yeah, certainly. So Westerners police is the second largest police force in the UK, outside of the metropolitan police in London. Um, we have an excessive, um, 11,000 people work at Westman ins police serving communities, um, through, across the Midlands region. So geographically, we're quite a big area as well, as well as, um, being population, um, density, having that as a, at a high level. Um, so the reason we sort of embarked on the data-driven insights platform and it, which was a huge change for us was for a number of reasons. Um, namely we had a lot of disparate data, um, which was spread across a range of legacy systems that were many, many years old, um, with some duplication of what was being captured and no single view for offices or, um, support staff. Um, some of the access was limited. You have to be in a, in an actual police building on a desktop computer to access it. Um, other information could only reach the offices on the front line, through a telephone call back to one of our enabling services where they would do a manual checkup, um, look at the information, then call the offices back, um, and tell them what they needed to know. So it was a very long laborious, um, process and not very efficient. Um, and we certainly weren't exploiting the data that we had in a very productive way. >>So it sounds like as you're describing, and I'm old clunky system that needed a technological, uh, reimagination. So what was the main motivation for, for doing, for making this shift? >>It was really, um, about making us more efficient and more effective in how we do how we do business. So, um, you know, certainly as a, as an it leader and some of my operational colleagues, we recognize the benefits, um, that data analytics could bring in, uh, in a policing environment, not something that was, um, really done in the UK at the time. You know, we have a lot of data, so we're very data rich and the information that we have, but we needed to turn it into information that was actionable. So that's where we started looking for, um, technology partners and suppliers to help us and sort of help us really with what's the art of the possible, you know, this hasn't been done before. So what could we do in this space? That's appropriate, >>Helen. I love that idea. What is the art of the possible, can you tell us a little bit about why you chose AWS? >>I think really, you know, as with all things and when we're procuring a partner in the public sector that, you know, there are many rules and regulations quite rightly as you would expect that to be because we're spending public money. So we have to be very, very careful and, um, it's, it's a long process and we have to be open to public scrutiny. So, um, we sort of look to everything, everything that was available as part of that process, but we recognize the benefits that Clyde would provide in this space because, you know, we're like moving to a cloud environment. We would literally be replacing something that was legacy with something that was a bit more modern. Um, that's not what we wanted to do. Our ambition was far greater than that. So I think, um, in terms of AWS, really, it was around scalability, interoperability, you know, just us things like the disaster recovery service, the fact that we can scale up and down quickly, we call it dialing up and dialing back. Um, you know, it's it's page go. So it just sort of ticked all the boxes for us. And then we went through the full procurement process, fortunately, um, it came out on top for us. So we were, we were able to move forward, but it just sort of had everything that we were looking for in that space. >>Matthew, I want to bring you into the conversation a little bit here. How are you working with a wet with the West Midlands police, sorry. And helping them implement this cloud-first >>Yeah, so I guess, um, by January the West Midlands police started, um, favorite five years ago now. So, um, we set up a partnership with the fools. I wanted to operate in a way that was very different to a traditional supplier relationship. Um, secretary that the data difference insights program is, is one of many that we've been working with last on, um, over the last five years, um, as having said already, um, cloud gave a number of, uh, advantages certainly from a big data perspective and things that, that enabled us today. Um, I'm from an Accenture perspective that allowed us to bring in a number of the different teams that we have say, cloud teams, security teams, um, and drafted from an insurance perspective, as well as the more traditional services that people would associate with the country. >>I mean, so much of this is about embracing comprehensive change to experiment and innovate and try different things. Matthew, how, how do you help, uh, an entity like West Midlands police think differently when they are, there are these ways of doing things that people are used to, how do you help them think about what is the art of the possible, as Helen said, >>There's a few things to that enable those being critical is trying to co-create solutions together. Yeah. There's no point just turning up with, um, what we think is the right answer, try and say, um, collectively work three, um, the issues that the fullest is seeing and the outcomes they're looking to achieve rather than simply focusing on a long list of requirements, I think was critical and then being really open to working together to create the right solution. Um, rather than just, you know, trying to pick something off the shelf that maybe doesn't fit the forces requirements in the way that it should too, >>Right. It's not always a one size fits all. >>Obviously, you know, today what we believe is critical is making sure that we're creating something that met the forces needs, um, in terms of the outcomes they're looking to achieve the financial envelopes that were available, um, and how we can deliver those in a, uh, iterative agile way, um, rather than spending years and years, um, working towards an outcome, um, that is gonna update before you even get that. >>So Helen, how, how are things different? What kinds of business functions and processes have been re-imagined in, in light of this change and this shift >>It's, it's actually unrecognizable now, um, in certain areas of the business as it was before. So to give you a little bit of, of context, when we, um, started working with essentially an AWS on the data driven insights program, it was very much around providing, um, what was called locally, a wizzy tool for our intelligence analyst to interrogate data, look at data, you know, decide whether they could do anything predictive with it. And it was very much sort of a back office function to sort of tidy things up for us and make us a bit better in that, in that area or a lot better in that area. And it was rolled out to a number of offices, a small number on the front line. Um, and really it was, um, in line with a mobility strategy that we, hardware officers were getting new smartphones for the first time, um, to do sort of a lot of things on, on, um, policing apps and things like that to again, to avoid them, having to keep driving back to police stations, et cetera. >>And the pilot was so successful. Every officer now has access to this data, um, on their mobile devices. So it literally went from a handful of people in an office somewhere using it to do sort of clever whizzbang things to, um, every officer in the force, being able to access that level of data at their fingertips. Literally. So what they were touched we've done before is if they needed to check and address or check details of an individual, um, just as one example, they would either have to, in many cases, go back to a police station to look it up themselves on a desktop computer. Well, they would have to make a call back to a centralized function and speak to an operator, relay the questions, either, wait for the answer or wait for a call back with the answer when those people are doing the data interrogation manually. >>So the biggest change for us is the self-service nature of the data we now have available. So officers can do it themselves on their phone, wherever they might be. So the efficiency savings from that point of view are immense. And I think just parallel to that is the quality of our, because we had a lot of data, but just because you've got a lot of data and a lot of information doesn't mean it's big data and it's valuable necessarily. Um, so again, it was having the single source of truth as we, as we call it. So you know that when you are completing those safe searches and getting the responses back, that it is the most accurate information we hold. And also you're getting it back within minutes, as opposed to, you know, half an hour, an hour or a drive back to a station. So it's making officers more efficient and it's also making them safer. The more efficient they are, the more time they have to spend out with the public doing what they, you know, we all should be doing, >>Seen that kind of return on investment, because what you were just describing with all the steps that we needed to be taken in prior to this, to verify an address say, and those are precious seconds when someone's life is on the line in, in sort of in the course of everyday police work. >>Absolutely. Yeah, absolutely. It's difficult to put a price on it. It's difficult to quantify. Um, but all the, you know, the minutes here and that certainly add up to a significant amount of efficiency savings, and we've certainly been able to demonstrate the officers are spending less time up police stations as a result or more time out on the front frontline also they're safer because they can get information about what may or may not be and address what may or may not have occurred in an area before very, very quickly without having to wait. >>Thank you. I want to hear your observations of working so closely with this West Midlands police. Have you noticed anything about changes in its culture and its operating model in how police officers interact with one another? Have you seen any changes since this technology change? >>What's unique about the Western new misplaces, the buy-in from the top down, the chief and his exact team and Helen as the leader from an IOT perspective, um, the entire force is bought in. So what is a significant change program? Uh, I'm not trickles three. Um, everyone in the organization, um, change is difficult. Um, and there's a lot of time effort. That's been put into both the technical delivery and the business change and adoption aspects around each of the projects. Um, but you can see the step change that is making in each aspect to the organization, uh, and where that's putting West Midlands police as a leader in, um, technology I'm policing in the UK. And I think globally, >>And this is a question for both of you because Matthew, as you said, change is difficult and there is always a certain intransigence in workplaces about this is just the way we've always done things and we're used to this and don't try us to get us. Don't try to get us to do anything new here. It works. How do you get the buy-in that you need to do this kind of digital transformation? >>I think it, it would be wrong to say it was easy. Um, um, we also have to bear in mind that this was one program in a five-year program. So there was a lot of change going on, um, both internally for some of our back office functions, as well as front Tai, uh, frontline offices. So with DDI in particular, I think the stat change occurred when people could see what it could do for them. You know, we had lots of workshops and seminars where we all talk about, you know, big data and it's going to be great and it's data analytics and it's transformational, you know, and quite rightly people that are very busy doing a day job that not necessarily technologists in the main and, you know, are particularly interested quite rightly so in what we are not dealing with the cloud, you know? >>And it was like, yeah, okay. It's one more thing. And then when they started to see on that, on their phones and what teams could do, that's when it started to sell itself. And I think that's when we started to see, you know, to see the stat change, you know, and, and if we, if we have any issues now it's literally, you know, our help desks in meltdown. Cause everyone's like, well, we call it manage without this anymore. And I think that speaks for itself. So it doesn't happen overnight. It's sort of incremental changes and then that's a step change in attitude. And when they see it working and they see the benefits, they want to use it more. And that's how it's become fundamental to all policing by itself, really, without much selling >>You, Helen just made a compelling case for how to get buy in. Have you discovered any other best practices when you are trying to get everyone on board for this kind of thing? >>We've um, we've used a lot of the traditional techniques, things around comms and engagement. We've also used things like, um, the 30 day challenge and nudge theory around how can we gradually encourage people to use things? Um, I think there's a point where all of this around, how do we just keep it simple and keep it user centric from an end user perspective? I think DDI is a great example of where the, the technology is incredibly complex. The solution itself is, um, you know, extremely large and, um, has been very difficult to, um, get delivered. But at the heart of it is a very simple front end for the user to encourage it and take that complexity away from them. Uh, I think that's been critical through the whole piece of DDR. >>One final word from Helen. I want to hear, where do you go from here? What is the longterm vision? I know that this has made productivity, um, productivity savings equivalent to 154 full-time officers. Uh, what's next, >>I think really it's around, um, exploiting what we've got. Um, I use the phrase quite a lot, dialing it up, which drives my technical architects crazy. But so, because it's apparently not that simple, but, um, you know, we've, we've been through significant change in the last five years and we are still continuing to batch all of those changes into everyday, um, operational policing. But what we need to see is we need to exploit and build on the investments that we've made in terms of data and claims specifically, the next step really is about expanding our pool of data and our functions. Um, so that, you know, we keep getting better and better at this. And the more we do, the more data we have, the more refined we can be, the more precise we are with all of our actions. Um, you know, we're always being expected to, again, look after the public purse and do more for less. >>And I think this is certainly an and our cloud journey and, and cloud first by design, which is where we are now, um, is helping us to be future-proofed. So for us, it's very much an investment. And I see now that we have good at embedded in operational policing for me, this is the start of our journey, not the end. So it's really exciting to see where we can go from here. Exciting times. Indeed. Thank you so much. Lily, Helen and Matthew for joining us. I really appreciate it. Thank you. And you are watching the cube stay tuned for more of the cubes coverage of the AWS reinvent Accenture executive summit. I'm Rebecca Knight from around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome to the cube virtual coverage of the executive summit at AWS reinvent 2020 virtual. This is the cube virtual. We can't be there in person like we are every year we have to be remote. This executive summit is with special programming supported by Accenture where the cube virtual I'm your host John for a year, we had a great panel here called uncloud first digital transformation from some experts, Stuart driver, the director of it and infrastructure and operates at lion Australia, Douglas Regan, managing director, client account lead at lion for Accenture as a deep Islam associate director application development lead for Centure gentlemen, thanks for coming on the cube virtual that's a mouthful, all that digital, but the bottom line it's cloud transformation. This is a journey that you guys have been on together for over 10 years to be really a digital company. Now, some things have happened in the past year that kind of brings all this together. This is about the next generation organization. So I want to ask Stuart you first, if you can talk about this transformation at lion has undertaken some of the challenges and opportunities and how this year in particular has brought it together because you know, COVID has been the accelerant of digital transformation. Well, if you're 10 years in, I'm sure you're there. You're in the, uh, on that wave right now. Take a minute to explain this transformation journey. >>Yeah, sure. So a number of years back, we, we looked at kind of our infrastructure in our landscape trying to figure out where we >>Wanted to go next. And we were very analog based and stuck in the old it groove of, you know, Capitol reef rash, um, struggling to transform, struggling to get to a digital platform and we needed to change it up so that we could become very different business to the one that we were back then obviously cloud is an accelerant to that. And we had a number of initiatives that needed a platform to build on. And a cloud infrastructure was the way that we started to do that. So we went through a number of transformation programs that we didn't want to do that in the old world. We wanted to do it in a new world. So for us, it was partnering up with a dried organizations that can take you on the journey and, uh, you know, start to deliver bit by bit incremental progress, uh, to get to the, uh, I guess the promise land. >>Um, we're not, not all the way there, but to where we're on the way along. And then when you get to some of the challenges like we've had this year, um, it makes all of the hard work worthwhile because you can actually change pretty quickly, um, provide capacity and, uh, and increase your environments and, you know, do the things that you need to do in a much more dynamic way than we would have been able to previously where we might've been waiting for the hardware vendors, et cetera, to deliver capacity. So for us this year, it's been a pretty strong year from an it perspective and delivering for the business needs >>Before I hit the Douglas. I want to just real quick, a redirect to you and say, you know, if all the people said, Oh yeah, you got to jump on cloud, get in early, you know, a lot of naysayers like, well, wait till to mature a little bit, really, if you got in early and you, you know, paying your dues, if you will taking that medicine with the cloud, you're really kind of peaking at the right time. Is that true? Is that one of the benefits that comes out of this getting in the cloud? Yeah, >>John, this has been an unprecedented year, right. And, um, you know, Australia, we had to live through Bush fires and then we had covert and, and then we actually had to deliver a, um, a project on very nice transformational project, completely remote. And then we also had had some, some cyber challenges, which is public as well. And I don't think if we weren't moved into and enabled through the cloud, we would have been able to achieve that this year. It would have been much different and would have been very difficult to do the backing. We're able to work and partner with Amazon through this year, which is unprecedented and actually come out the other end and we've delivered a brand new digital capability across the entire business. Um, in many, you know, wouldn't have been impossible if we could, I guess, stayed in the old world. The fact that we were moved into the new Naval by the new allowed us to work in this unprecedented year. >>Just quilt. What's your personal view on this? Because I've been saying on the Cuban reporting necessity is the mother of all invention and the word agility has been kicked around as kind of a cliche, Oh, it'd be agile. You know, we're going to get the city, you get a minute on specifically, but from your perspective, uh, Douglas, what does that mean to you? Because there is benefits there for being agile. And >>I mean, I think as Stuart mentioned, right, in a lot of these things we try to do and, you know, typically, you know, hardware and, uh, the last >>To be told and, and, and always on the critical path to be done, we really didn't have that in this case, what we were doing with our projects in our deployments, right. We were able to move quickly able to make decisions in line with the business and really get things going. Right. So you see a lot of times in a traditional world, you have these inhibitors, you have these critical path, it takes weeks and months to get things done as opposed to hours and days, and, and truly allowed us to, we had to, you know, VJ things, move things. And, you know, we were able to do that in this environment with AWS to support and the fact that they can kind of turn things off and on as quickly as we needed. >>Yeah. Cloud-scale is great for speed. So DECA, Gardez get your thoughts on this cloud first mission, you know, it, you know, the dev ops world, they saw this early, that jumping in there, they saw the, the, the agility. Now the theme this year is modern applications with the COVID pandemic pressure, there's real business pressure to make that happen. How did you guys learn to get there fast? And what specifically did you guys do at Accenture and how did it all come together? Can you take us inside kind of how it played out? >>Right. So, yeah, we started off with, as we do in most cases with a much more bigger group, and we worked with lions functional experts and, uh, the lost knowledge that allowed the infrastructure had. Um, we then applied our journey to cloud strategy, which basically revolves around the seminars and, and, uh, you know, the deep three steps from our perspective, uh, assessing the current and bottom and setting up the new cloud environment. And as we go modernizing and, and migrating these applications to the cloud now, you know, one of the key things that, uh, you know, we learned along this journey was that, you know, you can have the best plans, but bottom line that we were dealing with, we often than not have to make changes, uh, what a lot of agility and also work with a lot of collaboration with the, uh, lion team, as well as, uh, uh, AWS. I think the key thing for me was being able to really bring it all together. It's not just, uh, you know, we want to hear it's all of us working together to make this happen. >>What were some of the learnings real quick journey there? >>So I think perspective, the key learnings were that, you know, uh, you know, work, when you look back at, uh, the, the infrastructure that was that we were trying to migrate over to the cloud. A lot of the documentation, et cetera, was not, uh, available. We were having to, uh, figure out a lot of things on the fly. Now that really required us to have, uh, uh, people with deep expertise who could go into those environments and, and work out, uh, you know, the best ways to, to migrate the workloads to the cloud. Uh, I think, you know, the, the biggest thing for me was making sure all the had on that real SMEs across the board globally, that we could leverage across the various technologies, uh, uh, and, and, and, you know, that would really work in our collaborative and agile environment with line. >>Let's do what I got to ask you. How did you address your approach to the cloud and what was your experience? >>Yeah, for me, it's around getting the foundations right. To start with and then building on them. Um, so, you know, you've got to have your, your, your process and you've got to have your, your kind of your infrastructure there and your blueprints ready. Um, AWS do a great job of that, right. Getting the foundations right. And then building upon it, and then, you know, partnering with Accenture allows you to do that very successfully. Um, I think, um, you know, the one thing that was probably surprising to us when we started down this journey and kind of after we got a long way down the track and looking backwards is actually how much you can just turn off. Right? So a lot of stuff that you, uh, you get electric with a legacy in your environment, and when you start to work through it with the types of people that civic just mentioned, you know, the technical expertise working with the business, um, you can really rationalize your environment and, uh, you know, cloud is a good opportunity to do that, to drive that legacy out. >>Um, so you know, a few things there, the other thing is, um, you've got to try and figure out the benefits that you're going to get out of moving here. So there's no point in just taking something that is not delivering a huge amount of value in the traditional world, moving it into the cloud, and guess what is going to deliver the same limited amount of value. So you've got to transform it, and you've got to make sure that you build it for the future and understand exactly what you're trying to gain out of it. So again, you need a strong collaboration. You need a good partners to work with, and you need good engagement from the business as well, because the kind of, uh, you know, digital transformation, cloud transformation, isn't really an it project, I guess, fundamentally it is at the core, but it's a business project that you've got to get the whole business aligned on. You've got to make sure that your investment streams are appropriate and that's, uh, you're able to understand the benefits and the value that say, you're going to drive back towards the business. >>Let's do it. If you don't mind me asking, what was some of the obstacles you encountered or learnings, um, that might different from the expectation we all been there, Hey, you know, we're going to change the world. Here's the sales pitch, here's the outcome. And then obviously things happen, you know, you learn legacy, okay. Let's put some containerization around that cloud native, um, all that rational. You're talking about what are, and you're going to have obstacles. That's how you learn. That's how perfection has developed. How, what obstacles did you come up with and how are they different from your expectations going in? >>Yeah, they're probably no different from other people that have gone down the same journey. If I'm totally honest, the, you know, 70 or 80% of what you do is relatively easy of the known quantity. It's relatively modern architectures and infrastructures, and you can upgrade, migrate, move them into the cloud, whatever it is, rehost, replatform, rearchitect, whatever it is you want to do, it's the other stuff, right? It's the stuff that always gets left behind. And that's the challenge. It's, it's getting that last bit over the line and making sure that you haven't been invested in the future while still carrying all of your legacy costs and complexity within your environment. So, um, to be quite honest, that's probably taken longer and has been more of a challenge than we thought it would be. Um, the other piece I touched on earlier on in terms of what was surprising was actually how much of, uh, your environment is actually not needed anymore. >>When you start to put a critical eye across it and understand, um, uh, ask the tough questions and start to understand exactly what, what it is you're trying to achieve. So if you ask a part of a business, do they still need this application or this service a hundred percent of the time, they will say yes until you start to lay out to them, okay, now I'm going to cost you this to migrate it or this, to run it in the future. And, you know, here's your ongoing costs and, you know, et cetera, et cetera. And then, uh, for a significant amount of those answers, you get a different response when you start to layer on the true value of it. So you start to flush out those hidden costs within the business, and you start to make some critical decisions as a company based on, uh, based on that. So that was a little tougher than we first thought and probably broader than we thought there was more of that than we anticipated, um, which actually results in a much cleaner environment, post post migration, >>You know, the old expression, if it moves automated, you know, it's kind of a joke on government, how they want to tax everything, you know, you want to automate, that's a key thing in cloud, and you've got to discover those opportunities to create value Stuart and Siddique. Mainly if you can weigh in on this love to know the percentage of total cloud that you have now, versus when you started, because as you start to uncover whether it's by design for purpose, or you discover opportunity to innovate, like you guys have, I'm sure it kind of, you took on some territory inside Lyon, what percentage of cloud now versus start? >>Yeah. And at the start it was minimal, right. You know, close to zero, right. Single and single digits. Right. It was mainly SAS environments that we had, uh, sitting in clouds when we, uh, when we started, um, Doug mentioned earlier on a really significant transformation project, um, that we've undertaken and recently gone live on a multi-year one. Um, you know, that's all stood up on AWS and is a significant portion of our environment, um, in terms of what we can move to cloud. Uh, we're probably at about 80 or 90% now. And the balance bit is, um, legacy infrastructure that is just going to retire as we go through the cycle rather than migrate to the cloud. Um, so we are significantly cloud-based and, uh, you know, we're reaping the benefits of it in a year, like 2020, and makes you glad that you did all of the hard yards in the previous years when you started that business challenges thrown out as, >>So do you any common reaction still the cloud percentage penetration? >>Sorry, I didn't, I didn't guys don't, but I, I was going to say it was, I think it's like the 80 20 rule, right? We, we, we worked really hard in the, you know, I think 2018, 19 to get any person off, uh, after getting onto the cloud and, or the last year is the 20% that we have been migrating. And Stuart said like a non-athlete that is also, that's going to be the diet. And I think our next big step is going to be obviously, you know, the icing on the cake, which is to decommission all these apps as well. Right. So, you know, to get the real benefits out of, uh, the whole conservation program from a, uh, from a >>Douglas and Stewart, can you guys talk about the decision around the cloud because you guys have had success with AWS, why AWS how's that decision made? Can you guys give some insight into some of those thoughts? >>I can, I can start, start off. I think back when the decision was made and it was, Oh, it was a while back, um, you know, there's some clear advantages of moving relay, Ws, a lot of alignment with some of the significant projects and, uh, the trend, that particular one big transformation project that we've alluded to as well. Um, you know, we needed some, um, some very robust and, um, just future proof and, um, proven technology. And AWS gave that to us. We needed a lot of those blueprints to help us move down the path. We didn't want to reinvent everything. So, um, you know, having a lot of that legwork done for us and an AWS gives you that, right. And particularly when you partner up with, uh, with a company like Accenture as well, you get combinations of the technology and the skills and the knowledge to, to move you forward in that direction. >>So, um, you know, for us, it was a, uh, uh, it was a decision based on, you know, best of breed, um, you know, looking forward and, and trying to predict the future needs and, and, and kind of the environmental that we might need. Um, and, you know, partnering up with organizations that can take you on the journey. Yeah. And just to build on it. So obviously, you know, lion's like an NWS, but, you know, we knew it was a very good choice given that, um, uh, the skills and the capability that we had, as well as the assets and tools we had to get the most out of, um, out of AWS. And obviously our, our CEO globally is just spending, you know, announcement about a huge investment that we're making in cloud. Um, but you know, we've, we've worked very well. AWS, we've done some joint workshops and joint investments, um, some joint POC. So yeah, w we have a very good working relationship, AWS, and I think, um, one incident to reflect upon whether it's cyber it's and again, where we actually jointly, you know, dove in with, um, with Amazon and some of their security experts and our experts. And we're able to actually work through that with mine quite successful. So, um, you know, really good behaviors as an organization, but also really good capabilities. >>Yeah. As you guys, you're essential cloud outcomes, research shown, it's the cycle of innovation with the cloud. That's creating a lot of benefits, knowing what you guys know now, looking back certainly COVID is impacted a lot of people kind of going through the same process, knowing what you guys know now, would you advocate people to jump on this transformation journey? If so, how, and what tweaks they make, which changes, what would you advise? >>Uh, I might take that one to start with. Um, I hate to think where we would have been when, uh, COVID kicked off here in Australia and, you know, we were all sent home, literally were at work on the Friday, and then over the weekend. And then Monday, we were told not to come back into the office and all of a sudden, um, our capacity in terms of remote access and I quadrupled, or more four, five X, what we had on the Friday we needed on the Monday. And we were able to stand that up during the day Monday into Tuesday, because we were cloud-based and, uh, you know, we just spun up your instances and, uh, you know, sort of our licensing, et cetera. And we had all of our people working remotely, um, within, uh, you know, effectively one business day. Um, I know peers of mine in other organizations and industries that are relying on kind of a traditional wise and getting hardware, et cetera, that were weeks and months before they could get there the right hardware to be able to deliver to their user base. >>So, um, you know, one example where you're able to scale and, uh, um, get, uh, get value out of this platform beyond probably what was anticipated at the time you talk about, um, you know, less the, in all of these kinds of things. And you can also think of a few scenarios, but real world ones where you're getting your business back up and running in that period of time is, is just phenomenal. There's other stuff, right? There's these programs that we've rolled out, you do your sizing, um, and in the traditional world, you would just go out and buy more servers than you need. And, you know, probably never realize the full value of those, you know, the capability of those servers over the life cycle of them. Whereas, you know, in a cloud world, you put in what you think is right. And if it's not right, you pump it up a little bit when, when all of your metrics and so on, tell you that you need to bump it up. And conversely you scale it down at the same rate. So for us, with the types of challenges and programs and, uh, uh, and just business need, that's come at as this year, uh, we wouldn't have been able to do it without a strong cloud base, uh, to, uh, to move forward. >>You know, Douglas, one of the things I talked to, a lot of people on the right side of history who have been on the right wave with cloud, with the pandemic, and they're happy, they're like, and they're humble. Like, well, we're just lucky, you know, luck is preparation meets opportunity. And this is really about you guys getting in early and being prepared and readiness. This is kind of important as people realize, then you gotta be ready. I mean, it's not just, you don't get lucky by being in the right place, the right time. And there were a lot of companies were on the wrong side of history here who might get washed away. This is a super important, I think, >>To echo and kind of building on what Stewart said. I think that the reason that we've had success and I guess the momentum is we didn't just do it in isolation within it and technology. It was actually linked to broader business changes, you know, creating basically a digital platform for the entire business, moving the business, where are they going to be able to come back stronger after COVID, when they're actually set up for growth, um, and actually allows, you know, a line to achievements growth objectives, and also its ambitions as far as what it wants to do, uh, with growth in whatever they make, do with acquiring other companies and moving into different markets and launching new products. So we've actually done it in a way that is, you know, real and direct business benefit, uh, that actually enables line to grow >>General. I really appreciate you coming. I have one final question. If you can wrap up here, uh, Stuart and Douglas, you don't mind weighing in what's the priorities for the future. What's next for lion in a century >>Christmas holidays, I'll start Christmas holidays. I spent a good year and then a, and then a reset, obviously, right? So, um, you know, it's, it's figuring out, uh, transform what we've already transformed, if that makes sense. So God, a huge proportion of our services sitting in the cloud. Um, but we know we're not done even with the stuff that is in there. We need to take those next steps. We need more and more automation and orchestration. We need to, um, our environment is more future proof. We need to be able to work with the business and understand what's coming at them so that we can, um, you know, build that into, into our environment. So again, it's really transformation on top of transformation is the way that I'll describe it. And it's really an open book, right? Once you get it in and you've got the capabilities and the evolving tool sets that AWS continue to bring to the market based, um, you know, working with the partners to, to figure out how we unlock that value, um, you know, drive our costs down efficiency, uh, all of those kind of, you know, standard metrics. >>Um, but you know, we're looking for the next things to transform and showed value back out to our customer base, um, that, uh, that we continue to, you know, sell our products to and work with and understand how we can better meet their needs. Yeah, I think just to echo that, I think it's really leveraging this and then did you capability they have and getting the most out of that investment. And then I think it's also moving to, uh, and adopting more new ways of working as far as, you know, the speed of the business, um, is getting up to speed in the market is changing. So being able to launch and do things quickly and also, um, competitive and efficient operating costs, uh, now that they're in the cloud, right? So I think it's really leveraging the most out of the platform and then, you know, being efficient in launching things. So putting them with >>Siddique, any word from you on your priorities by you see this year in folding, >>There's got to say like e-learning squares, right, for me around, you know, just journey. This is a journey to the cloud, right? >>And, uh, you know, as well dug into sort of Saturday, it's getting all, you know, different parts of the organization along the journey business to it, to your, uh, product lenders, et cetera. Right. And it takes time. It is tough, but, uh, uh, you know, you got to get started on it. And, you know, once we, once we finish off, uh, it's the realization of the benefits now that, you know, looking forward, I think for, from Alliance perspective, it is, uh, you know, once we migrate all the workloads to the cloud, it is leveraging, uh, all stack drive. And as I think Stewart said earlier, uh, with, uh, you know, the latest and greatest stuff that AWS it's basically working to see how we can really, uh, achieve more better operational excellence, uh, from a, uh, from a cloud perspective. >>Well, Stewart, thanks for coming on with a and sharing your environment and what's going on and your journey you're on the right wave. Did the work you're in, it's all coming together with faster, congratulations for your success, and, uh, really appreciate Douglas with Steve for coming on as well from essential. Thank you for coming on. Thanks, John. Okay. Just the cubes coverage of executive summit at AWS reinvent. This is where all the thought leaders share their best practices, their journeys, and of course, special programming with Accenture and the cube. I'm Sean ferry, your host, thanks for watching from around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome everyone to the cube virtuals coverage of the Accenture executive summit. Part of AWS reinvent 2020. I'm your host Rebecca Knight. We are talking today about reinventing the energy data platform. We have two guests joining us. First. We have Johan Krebbers. He is the GM digital emerging technologies and VP of it. Innovation at shell. Thank you so much for coming on the show, Johan you're welcome. And next we have Liz Dennett. She is the lead solution architect for O S D U on AWS. Thank you so much, Liz, maybe here. So I want to start our conversation by talking about OSD. You like so many great innovations. It started with a problem. Johann, what was the problem you were trying to solve at shell? We go back a couple of years, we started summer 2017, where we had a meeting with the guys from exploration in shell, and the main problem they had, of course, they got lots of lots of data, but are unable to find the right data. They need to work from all over the place and told him >>To, and we'll probably try to solve is how that person working exploration could find their proper date, not just a day, but also the date you really needed that we did probably talked about is summer 2017. And we said, okay, the only way ABC is moving forward is to start pulling that data into a single data platform. And that, that was at the time that we called it as the, you, the subsurface data universe in there was about the shell name was so in, in January, 2018, we started a project with Amazon to start grating a co fricking that building, that Stu environment, that the, the universe, so that single data level to put all your exploration and Wells data into that single environment that was intent. And every cent, um, already in March of that same year, we said, well, from Michele point of view, we will be far better off if we could make this an industry solution and not just a shelf solution, because Shelby, Shelby, if you can make an industry solution, but people are developing applications for it. >>It also is far better than for shell to say we haven't shell special solution because we don't make money out of how we start a day that we can make money out of it. We have access to the data, we can explore the data. So storing the data we should do as efficiently possibly can. So we monitor, we reach out to about eight or nine other last, uh, or I guess operators like the economics, like the tutorials, like the shepherds of this world and say, Hey, we inshallah doing this. Do you want to join this effort? And to our surprise, they all said, yes. And then in September, 2018, we had our kickoff meeting with your open group where we said, we said, okay, if you want to work together and lots of other companies, we also need to look at, okay, how, how we organize that. >>Or if you started working with lots of large companies, you need to have some legal framework around some framework around it. So that's why we went to the open group and say, okay, let's, let's form the old forum as we call it at the time. So it's September, 2080, where I did a Galleria in Houston, but the kickoff meeting for the OT four with about 10 members at the time. So that's just over two years ago, we started an exercise for me called ODU. They kicked it off. Uh, and so that's really them will be coming from and how we've got there. Also >>The origin story. Um, what, so what digging a little deeper there? What were some of the things you were trying to achieve with the OSU? >>Well, a couple of things we've tried to achieve with you, um, first is really separating data from applications for what is, what is the biggest problem we have in the subsurface space that the data and applications are all interlinked or tied together. And if, if you have them and a new company coming along and say, I have this new application and he's access to the data that is not possible because the data often interlinked with the application. So the first thing we did is really breaking the link between the application, the data as those levels, the first thing we did, secondly, put all the data to a single data platform, take the silos out what was happening in the sub-service space. They got all the data in what we call silos in small little islands out there. So what we're trying to do is first break the link to great, great. >>They put the data single day, the bathroom, and the third part, put a standard layer on top of that, it's an API layer on top to equate a platform. So we could create an ecosystem out of companies to start a valving Schoff application on top of dev data platform across you might have a data platform, but you're only successful if have a rich ecosystem of people start developing applications on top of that. And then you can export the data like small companies, last company, university, you name it, we're getting after create an ecosystem out here. So the three things were first break the link between application data, just break it and put data at the center and also make sure that data, this data structure would not be managed by one company, but it would only be met. It would be managed the data structures by the ODI forum. Secondly, then put a, the data, a single data platform certainly then has an API layer on top and then create an ecosystem. Really go for people, say, please start developing applications, because now you had access to the data. I've got the data no longer linked to somebody whose application was all freely available, but an API layer that was, that was all September, 2018, more or less. >>And hear a little bit. Can you talk a little bit about some of the imperatives from the AWS standpoint in terms of what you were trying to achieve with this? Yeah, absolutely. And this whole thing is Johann said started with a challenge that was really brought out at shell. The challenges that geoscientists spend up to 70% of their time looking for data. I'm a geologist I've spent more than 70% of my time trying to find data in these silos. And from there, instead of just figuring out how we could address that one problem, we worked together to really understand the root cause of these challenges and working backwards from that use case OSU and OSU on AWS has really enabled customers to create solutions that span, not just this in particular problem, but can really scale to be inclusive of the entire energy value chain and deliver value from these use cases to the energy industry and beyond. Thank you, Lee, uh, Johann. So talk a little bit about Accenture's cloud first approach and how it has, uh, helped shell work faster and better with speed. >>Well, of course, access a cloud first approach only works together. It's been an Amazon environment, AWS environment. So we're really looking at, uh, at, at Accenture and others altogether helping shell in this space. Now the combination of the two is what we're really looking at, uh, where access of course can be recent knowledge student to that environment operates support knowledge, do an environment. And of course, Amazon will be doing that to today's environment that underpinning their services, et cetera. So, uh, we would expect a combination, a lot of goods when we started rolling out and put in production, the old you are three and bug because we are anus. Then when the release feed comes to the market in Q1, next year of ODU have already started going to Audi production inside shell. But as the first release, which is ready for prime time production across an enterprise will be released just before Christmas, last year when he's still in may of this year. But really three is the first release we want to use for full scale production deployment inside shell, and also the operators around the world. And there is one Amazon, sorry, at that one. Um, extensive can play a role in the ongoing, in the, in deployment building up, but also support environment. >>So one of the other things that we talk a lot about here on the cube is sustainability. And this is a big imperative at so many organizations around the world in particular energy companies. How does this move to OSD you, uh, help organizations become, how is this a greener solution for companies? >>Well, first we make it's a greatest solution because you start making a much more efficient use of your resources, which is already an important one. The second thing we're doing is also, we started ODU in framers, in the oil and gas space in the expert development space. We've grown, uh, OTU in our strategy of growth. I was, you know, also do an alternative energy sociology. We'll all start supporting next year. Things like solar farms, wind farms, uh, the, the dermatomal environment hydration. So it becomes an and an open energy data platform, not just what I want to get into sleep. That's what new industry, any type of energy industry. So our focus is to create, bring the data of all those various energy data sources to get me to a single data platform you can to use AI and other technologies on top of that, to exploit the data, to meet again into a single data platform. >>Liz, I want to ask you about security because security is, is, is such a big concern when it comes to data. How secure is the data on OSD? You, um, actually, can I talk, can I do a follow up on this sustainability talking? Oh, absolutely. By all means. I mean, I want to interject though security is absolutely our top priority. I don't mean to move away from that, but with sustainability, in addition to the benefits of the OSU data platform, when a company moves from on-prem to the cloud, they're also able to leverage the benefits of scale. Now, AWS is committed to running our business in the most environmentally friendly way possible. And our scale allows us to achieve higher resource utilization and energy efficiency than a typical data center. >>Now, a recent study by four 51 research found that AWS is infrastructure is 3.6 times more energy efficient than the median of surveyed enterprise data centers. Two thirds of that advantage is due to higher, um, server utilization and a more energy efficient server population. But when you factor in the carbon intensity of consumed electricity and renewable energy purchases for 51 found that AWS performs the same task with an 88% lower carbon footprint. Now that's just another way that AWS and OSU are working to support our customers is they seek to better understand their workflows and make their legacy businesses less carbon intensive. >>That's that's incorrect. Those are those statistics are incredible. Do you want to talk a little bit now about security? Absolutely. And security will always be AWS is top priority. In fact, AWS has been architected to be the most flexible and secure cloud computing environment available today. Our core infrastructure is built to satisfy. There are the security requirements for the military, local banks and other high sensitivity organizations. And in fact, AWS uses the same secure hardware and software to build and operate each of our regions. So that customers benefit from the only commercial cloud that's hat hits service offerings and associated supply chain vetted and deemed secure enough for top secret workloads. That's backed by a deep set of cloud security tools with more than 200 security compliance and governmental service and key features as well as an ecosystem of partners like Accenture, that can really help our customers to make sure that their environments for their data meet and or exceed their security requirements. Johann, I want you to talk a little bit about how OSD you can be used today. Does it only handle subsurface data? >>Uh, today it's Honda's subserves or Wells data, we go to add to that production around the middle of next year. That means that the whole upstate business. So we've got goes from exploration all the way to production. You've made it together into a single data platform. So production will be added around Q3 of next year. Then a principal. We have a difficult, the elder data that single environment, and we want to extend them to other data sources or energy sources like solar farms, wind farms, uh, hydrogen, hydro, et cetera. So we're going to add a whore, a whole list of audit day energy source to them and be all the data together into a single data club. So we move from a falling guest data platform to an aniseed data platform. That's really what our objective is because the whole industry, if you look it over, look at our companies are all moving in. That same two acts of quantity of course, are very strong in oil and gas, but also increased the, got into the other energy sources like, like solar, like wind, like th like highly attended, et cetera. So we would be moving exactly. But that same method that, that, that the whole OSU can't really support at home. And as a spectrum of energy sources, >>Of course, and Liz and Johan. I want you to close us out here by just giving us a look into your crystal balls and talking about the five and 10 year plan for OSD. You we'll start with you, Liz. What do you, what do you see as the future holding for this platform? Um, honestly, the incredibly cool thing about working at AWS is you never know where the innovation and the journey is going to take you. I personally am looking forward to work with our customers, wherever their OSU journeys, take them, whether it's enabling new energy solutions or continuing to expand, to support use cases throughout the energy value chain and beyond, but really looking forward to continuing to partner as we innovate to slay tomorrow's challenges, Johann first, nobody can look at any more nowadays, especially 10 years own objective is really in the next five years, you will become the key backbone for energy companies for storing your data. You are efficient intelligence and optimize the whole supply energy supply chain in this world down here, you'll uncovers Liz Dennett. Thank you so much for coming on the cube virtual I'm Rebecca Knight stay tuned for more of our coverage of the Accenture executive summit >>From around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome everyone to the cubes coverage of the Accenture executive summit. Part of AWS reinvent. I'm your host Rebecca Knight today we're welcoming back to Kubila. We have Kishor Dirk. He is the Accenture senior managing director cloud first global services lead. Welcome back to the show Kishore. Thank you very much. Nice to meet again. And, uh, Tristan moral horse set. He is the managing director, Accenture cloud first North America growth. Welcome back to you to trust and great to be back in grapes here again, Rebecca. Exactly. Even in this virtual format, it is good to see your faces. Um, today we're going to be talking about my nav and green cloud advisor capability. Kishor I want to start with you. So my nav is a platform that is really celebrating its first year in existence. Uh, November, 2019 is when Accenture introduced it. Uh, but it's, it has new relevance in light of this global pandemic that we are all enduring and suffering through. Tell us a little bit about the lineup platform, what it is that cloud platform to help our clients navigate the complexity of cloud and cloud decisions to make it faster. And obviously, you know, we have in the cloud, uh, you know, with >>The increased relevance and all the, especially over the last few months with the impact of COVID crisis and exhibition of digital transformation, you know, we are seeing the transformation or the acceleration to cloud much faster. This platform that you're talking about has enabled and 40 clients globally across different industries. You identify the right cloud solution, navigate the complexity, provide a cloud specific solution simulate for our clients to meet the strategy business needs, and the clients are loving it. >>I want to go to you now trust and tell us a little bit about how mine nav works and how it helps companies make good cloud choice. >>Yeah, so Rebecca, we we've talked about cloud is, is more than just infrastructure and that's what mine app tries to solve for it. It really looks at a variety of variables, including infrastructure operating model and fundamentally what client's business outcomes, um, uh, our clients are, are looking for and, and identifies the optimal solution for what they need. And we assign this to accelerate and we mentioned the pandemic. One of the big focus now is to accelerate. And so we worked through a three-step process. The first is scanning and assessing our client's infrastructure, their data landscape, their application. Second, we use our automated artificial intelligence engine to interact with. We have a wide variety and library of a collective plot expertise. And we look to recommend what is the enterprise architecture and solution. And then third, before we aligned with our clients, we look to simulate and test this scaled up model. And the simulation gives our clients a way to see what cloud is going to look like, feel like and how it's going to transform their business before they go there. >>Tell us a little bit about that in real life. Now as a company, so many of people are working remotely having to collaborate, uh, not in real life. How is that helping them right now? >>So, um, the, the pandemic has put a tremendous strain on systems, uh, because of the demand on those systems. And so we talk about resiliency. We also now need to collaborate across data across people. Um, I think all of us are calling from a variety of different places where our last year we were all at the VA cube itself. Um, and, and cloud technologies such as teams, zoom that we're we're leveraging now has fundamentally accelerated and clients are looking to onboard this for their capabilities. They're trying to accelerate their journey. They realize that now the cloud is what is going to become important for them to differentiate. Once we come out of the pandemic and the ability to collaborate with their employees, their partners, and their clients through these systems is becoming a true business differentiator for our clients. >>Keisha, I want to talk with you now about my navs multiple capabilities, um, and helping clients design and navigate their cloud journeys. Tell us a little bit about the green cloud advisor capability and its significance, particularly as so many companies are thinking more deeply and thoughtfully about sustainability. >>Yes. So since the launch of my lab, we continue to enhance, uh, capabilities for our clients. One of the significant, uh, capabilities that we have enabled is the being taught advisor today. You know, Rebecca, a lot of the businesses are more environmentally aware and are expanding efforts to decrease power consumption, uh, and obviously carbon emissions and, uh, and run a sustainable operations across every aspect of the enterprise. Uh, as a result, you're seeing an increasing trend in adoption of energy, efficient infrastructure in the global market. And one of the things that we did a lot of research we found out is that there's an ability to influence our client's carbon footprint through a better cloud solution. And that's what the internet brings to us, uh, in, in terms of a lot of the client connotation that you're seeing in Europe, North America and others, lot of our clients are accelerating to a green cloud strategy to unlock beta financial, societal and environmental benefit, uh, through obviously cloud-based circular, operational, sustainable products and services. That is something that we are enhancing my now, and we are having active client discussions at this point of time. >>So Tristan, tell us a little bit about how this capability helps clients make greener decisions. >>Yeah. Um, well, let's start about the investments from the cloud providers in renewable and sustainable energy. Um, they have most of the hyperscalers today, um, have been investing significantly on data centers that are run on renewable energy, some incredibly creative constructs on the how to do that. And sustainability is there for a key, um, key item of importance for the hyperscalers and also for our clients who now are looking for sustainable energy. And it turns out this marriage is now possible. I can, we marry the, the green capabilities of the comm providers with a sustainability agenda of our clients. And so what we look into the way the mine EF works is it looks at industry benchmarks and evaluates our current clients, um, capabilities and carpet footprint leveraging their existing data centers. We then look to model from an end-to-end perspective, how the, their journey to the cloud leveraging sustainable and, um, and data centers with renewable energy. We look at how their solution will look like and, and quantify carbon tax credits, um, improve a green index score and provide quantifiable, um, green cloud capabilities and measurable outcomes to our clients, shareholders, stakeholders, clients, and customers. Um, and our green plot advisers sustainability solutions already been implemented at three clients. And in many cases in two cases has helped them reduce the carbon footprint by up to 400% through migration from their existing data center to green cloud. Very, very, >>That is remarkable. Now tell us a little bit about the kinds of clients. Is this, is this more interesting to clients in Europe? Would you say that it's catching on in the United States? Where, what is the breakdown that you're seeing right now? >>Sustainability is becoming such a global agenda and we're seeing our clients, um, uh, tie this and put this at board level, um, uh, agenda and requirements across the globe. Um, Europe has specific constraints around data sovereignty, right, where they need their data in country, but from a green, a sustainability agenda, we see clients across all our markets, North America, Europe, and our growth markets adopt this. And we have seen case studies and all three months. >>Keisha, I want to bring you back into the conversation. Talk a little bit about how MindUP ties into Accenture's cloud first strategy, your Accenture's CEO, Julie Sweet has talked about post COVID leadership requiring every business to become a cloud first business. Tell us a little bit about how this ethos is in Accenture and how you're sort of looking outward with it too. >>So Rebecca mine is the launch pad, uh, to a cloud first transformation for our clients. Uh, Accenture, see your jewelry suite, uh, you know, shared the Accenture cloud first and our substantial investment demonstrate our commitment and is delivering greater value for our clients when they need it the most. And with the digital transformation requiring cloud at scale, you know, we're seeing that in the post COVID leadership, it requires that every business should become a cloud business. And my nap helps them get there by evaluating the cloud landscape, navigating the complexity, modeling architecting and simulating an optimal cloud solution for our clients. And as Justin was sharing a greener cloud. >>So Tristan, talk a little bit more about some of the real life use cases in terms of what are we, what are clients seeing? What are the results that they're having? >>Yes. Thank you, Rebecca. I would say two key things right around my neck. The first is the iterative process. Clients don't want to wait, um, until they get started, they want to get started and see what their journey is going to look like. And the second is fundamental acceleration, dependent make, as we talked about, has accelerated the need to move to cloud very quickly. And my nav is there to do that. So how do we do that? First is generating the business cases. Clients need to know in many cases that they have a business case by business case, we talk about the financial benefits, as well as the business outcomes, the green, green clot impact sustainability impacts with minus. We can build initial recommendations using a basic understanding of their environment and benchmarks in weeks versus months with indicative value savings in the millions of dollars arranges. >>So for example, very recently, we worked with a global oil and gas company, and in only two weeks, we're able to provide an indicative savings for $27 million over five years. This enabled the client to get started, knowing that there is a business case benefit and then iterate on it. And this iteration is, I would say the second point that is particularly important with my nav that we've seen in bank, the clients, which is, um, any journey starts with an understanding of what is the application landscape and what are we trying to do with those, these initial assessments that used to take six to eight weeks are now taking anywhere from two to four weeks. So we're seeing a 40 to 50% reduction in the initial assessment, which gets clients started in their journey. And then finally we've had discussions with all of the hyperscalers to help partner with Accenture and leverage mine after prepared their detailed business case module as they're going to clients. And as they're accelerating the client's journey, so real results, real acceleration. And is there a journey? Do I have a business case and furthermore accelerating the journey once we are by giving the ability to work in iterative approach. >>I mean, it sounds as though that the company that clients and and employees are sort of saying, this is an amazing time savings look at what I can do here in, in so much in a condensed amount of time, but in terms of getting everyone on board, one of the things we talked about last time we met, uh, Tristan was just how much, uh, how one of the obstacles is getting people to sign on and the new technologies and new platforms. Those are often the obstacles and struggles that companies face. Have you found that at all? Or what is sort of the feedback that you're getting from employers? >>Sorry. Yes. We clearly, there are always obstacles to a cloud journey. If there were an obstacles, all our clients would be, uh, already fully in the cloud. What man I gives the ability is to navigate through those, to start quickly. And then as we identify obstacles, we can simulate what things are going to look like. We can continue with certain parts of the journey while we deal with that obstacle. And it's a fundamental accelerator. Whereas in the past one, obstacle would prevent a class from starting. We can now start to address the obstacles one at a time while continuing and accelerating the contrary. That is the fundamental difference. >>Kishor I want to give you the final word here. Tell us a little bit about what is next for Accenture might have and what we'll be discussing next year at the Accenture executive summit >>Sort of echo, we are continuously evolving with our client needs and reinventing, reinventing for the future. For mine, as I've been taught advisor, our plan is to help our clients reduce carbon footprint and again, migrate to a green cloud. Uh, and additionally, we're looking at, you know, two capabilities, uh, which include sovereign cloud advisor, uh, with clients, especially in, in Europe and others are under pressure to meet, uh, stringent data norms that Kristen was talking about. And the sovereign cloud advisor health organization to create an architecture cloud architecture that complies with the green. Uh, I would say the data sovereignty norms that is out there. The other element is around data to cloud. We are seeing massive migration, uh, for, uh, for a lot of the data to cloud. And there's a lot of migration hurdles that come within that. Uh, we have expanded mine app to support assessment capabilities, uh, for, uh, assessing applications, infrastructure, but also covering the entire state, including data and the code level to determine the right cloud solution. So we are, we are pushing the boundaries on what mine app can do with mine. Have you created the ability to take the guesswork out of cloud navigate the complexity? We are roaring risks costs, and we are, you know, achieving client's static business objectives while building a sustainable alerts with being cloud >>Any platform that can take some of the guesswork out of the future. I'm I'm onboard with. Thank you so much, Tristin and Kishore. This has been a great conversation. >>Thank you. >>Stay tuned for more of the cubes coverage of the Accenture executive summit. I'm Rebecca Knight from around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Hey, welcome back to the cubes coverage of 80 us reinvent 2020 virtual centric executive summit. The two great guests here to break down the analysis of the relationship with cloud and essential Brian bowhead director ahead of a century 80. It was business group at Amazon web services. And Andy T a B G the M is essentially Amazon business group lead managing director at Accenture. Uh, I'm sure you're super busy and dealing with all the action, Brian. Great to see you. Thanks for coming on. So thank you. You guys essentially has been in the spotlight this week and all through the conference around this whole digital transformation, essentially as business group is celebrating its fifth anniversary. What's new, obviously the emphasis of next gen post COVID generation, highly digital transformation, a lot happening. You got your five-year anniversary, what's new. >>Yeah, it, you know, so if you look back, it's exciting. Um, you know, so it was five years ago. Uh, it was actually October where we, where we launched the Accenture AWS business group. And if we think back five years, I think we're still at the point where a lot of customers were making that transition from, you know, should I move to cloud to how do I move to cloud? Right? And so that was one of the reasons why we launched the business group. And since, since then, certainly we've seen that transition, right? Our conversations today are very much around how do I move to cloud, help me move, help me figure out the business case and then pull together all the different pieces so I can move more quickly, uh, you know, with less risk and really achieve my business outcomes. And I would say, you know, one of the things too, that's, that's really changed over the five years. >>And what we're seeing now is when we started, right, we were focused on migration data and IOT as the big three pillars that we launched with. And those are still incredibly important to us, but just the breadth of capability and frankly, the, the, the breadth of need that we're seeing from customers. And obviously as AWS has matured over the years and launched our new capabilities, we're Eva with Accenture and in the business group, we've broadened our capabilities and deepened our capabilities over the, over the last five years as well. For instance, this year with, with COVID, especially, it's really forced our customers to think differently about their own customers or their citizens, and how do they service those citizens? So we've seen a huge acceleration around customer engagement, right? And we powered that with Accenture customer engagement platform powered by ADA, Amazon connect. And so that's been a really big trend this year. And then, you know, that broadens our capability from just a technical discussion to one where we're now really reaching out and, and, um, and helping transform and modernize that customer and citizen experience as well, which has been exciting to see. >>Yeah, Andy, I want to get your thoughts here. We've been reporting and covering essentially for years. It's not like it's new to you guys. I mean, five years is a great anniversary. You know, check is good relationship, but you guys have been doing the work you've been on the trend line. And then this hits and Andy said on his keynote and I thought he said it beautifully. And he even said it to me in my one-on-one interview with them was it's on full display right now, the whole digital transformation, everything about it is on full display and you're either were prepared for it or you kind of word, and you can see who's there. You guys have been prepared. This is not new. So give us the update from your perspective, how you're taking advantage of this, of this massive shift, highly accelerated digital transformation. >>Well, I think, I think you can be prepared, but you've also got to be prepared to always sort of, I think what we're seeing in, in, um, in, in, in, in recent times and particularly 20 w what is it I think today there are, um, full sense of the enterprise workloads, the cloud, um, you know, that leaves 96 percentile now for him. Um, and I, over the next four to >>Five years, um, we're going to see that sort of, uh, acceleration to the, to the cloud pick up, um, this year is, as Andy touched on, I think, uh, uh, on Tuesday in his, I think the pandemic is a forcing function, uh, for companies to, to really pause and think about everything from, from, you know, how they, um, manage that technology to infrastructure, to just to carotenoids where the data sets to what insights and intelligence that getting from that data. And then eventually even to, to the talent, the talent they have in the organization and how they can be competitive, um, their culture, their culture of innovation, of invention and reinvention. And so I think, I think, you know, when you, when you think of companies out there faced with these challenges, it, it forces us, it forces AWS, it forces AEG to come together and think through how can we help create value for them? How can we help help them move from sort of just causing and rethinking to having real plans in an action and that taking them, uh, into, into implementation. And so that's, that's what we're working on. Um, I think over the next five years, we're looking to just continue to come together and help these, these companies get to the cloud and get the value from the cloud because it's beyond just getting to the cloud attached to them and living in the cloud and, and getting the value from it. >>It's interesting. Andy was saying, don't just put your toe in the water. You got to go beyond the toe in the water kind of approach. Um, I want to get to that large scale cause that's the big pickup this week that I kind of walked away with was it's large scale. Acceleration's not just toe in the water experimentation. Can you guys share, what's causing this large scale end to end enterprise transformation? And what are some of the success criteria have you seen for the folks who have done that? >>Yeah. And I'll, I'll, I'll start. And at the end you can buy a lawn. So, you know, it's interesting if I look back a year ago at re-invent and when I did the cube interview, then we were talking about how the ABG, we were starting to see this shift of customers. You know, we've been working with customers for years on a single of what I'll call a single-threaded programs, right. We can do a migration, we could do SAP, we can do a data program. And then even last year, we were really starting to see customers ask. The question is like, what kind of synergies and what kind of economies of scale do I get when I start bringing these different threads together, and also realizing that it's, you know, to innovate for the business and build new applications, new capabilities. Well, that then is going to inform what data you need to, to hydrate those applications, right? Which then informs your data strategy while a lot of that data is then also embedded in your underlying applications that sit on premises. So you should be thinking through how do you get those applications into the cloud? So you need to draw that line through all of those layers. And that was already starting last year. And so last year we launched the joint transformation program with AEG. And then, so we were ready when this year happened and then it was just an acceleration. So things have been happening faster than we anticipated, >>But we knew this was going to be happening. And luckily we've been in a really good position to help some of our customers really think through all those different layers of kind of pyramid as we've been calling it along with the talent and change pieces, which are also so important as you make this transformation to cloud >>Andy, what's the success factors. Andy Jassy came on stage during the partner day, a surprise fireside chat with Doug Hume and talking about this is really an opportunity for partners to, to change the business landscape with enablement from Amazon. You guys are in a pole position to do that in the marketplace. What's the success factors that you see, >>Um, really from three, three fronts, I'd say, um, w one is the people. Um, and, and I, I, again, I think Andy touched on sort of eight, uh, success factors, uh, early in the week. And for me, it's these three areas that it sort of boils down to these three areas. Um, one is the, the, the, the people, uh, from the leaders that it's really important to set those big, bold visions point the way. And then, and then, you know, set top down goals. How are we going to measure Z almost do get what you measure, um, to be, you know, beyond the leaders, to, to the right people in the right position across the company. We we're finding a key success factor for these end to end transformations is not just the leaders, but you haven't poached across the company, working in a, in a collaborative, shared, shared success model, um, and people who are not afraid to, to invent and fail. >>And so that takes me to perhaps the second point, which is the culture, um, it's important, uh, with finding for the right conditions to be set in the company that enabled, uh, people to move at pace, move at speed, be able to fail fast, um, keep things very, very simple and just keep iterating and that sort of culture of iteration and improvement versus seeking perfection is, is super important for, for success. And then the third part of maybe touch on is, is partners. Um, I think, you know, as we move forward over the next five years, we're going to see an increasing number of players in the ecosystem in the enterprise and state. Um, you're going to see more and more SAS providers. And so it's important for companies and our joint clients out there to pick partners like, um, like AWS or, or Accenture or others, but to pick partners who have all worked together and you have built solutions together, and that allows them to get speed to value quicker. It allows them to bring in pre-assembled solutions, um, and really just drive that transformation in a quicker, it sorts of manner. >>Yeah, that's a great point worth calling out, having that partnership model that's additive and has synergy in the cloud, because one of the things that came out of this this week, this year is reinvented, is there's new things going on in the public cloud, even though hybrid is an operating model, outpost and super relevant. There, there are benefits for being in the cloud and you've got partners API, for instance, and have microservices working together. This is all new, but I got, I got to ask that on that thread, Andy, where did you see your customers going? Because I think, you know, as you work backwards from the customers, you guys do, what's their needs, how do you see them? W you know, where's the puck going? Where can they skate where the puck's going, because you can almost look forward and say, okay, I've got to build modern apps. I got to do the digital transformation. Everything is a service. I get that, but what are they, what solutions are you building for them right now to get there? >>Yeah. And, and of course, with, with, you know, industries blurring and multiple companies, it's always hard to boil down to the exact situations, but you could probably look at it from a sort of a thematic lens. And what we're seeing is as the cloud transformation journey picks up, um, from us perspective, we've seen a material shift in the solutions and problems that we're trying to address with clients that they are asking for us, uh, to, to help, uh, address is no longer just the back office, where you're sort of looking at cost and efficiency and, um, uh, driving gains from that perspective. It's beyond that, it's now materially the top line. It's, how'd you get the driving to the, you know, speed to insights, how'd you get them decomposing, uh, their application set in order to derive those insights. Um, how'd you get them, um, to, to, um, uh, sort of adopt leading edge industry solutions that give them that jump start, uh, and that accelerant to winning the customers, winning the eyeballs. >>Um, and then, and then how'd, you help drive the customer experience. We're seeing a lot of push from clients, um, or ask for help on how do I optimize my customer experience in order to retain my eyeballs. And then how do I make sure I've got a soft self-learning ecosystem of play, um, where, uh, you know, it's not just a practical experience that I can sort of keep learning and iterating, um, how I treat my, my customers, um, and a lot of that, um, that still self-learning, that comes from, you know, putting in intelligence into your, into your systems, getting an AI and ML in there. And so, as a result of that work, we're seeing a lot of push and a lot of what we're doing, uh, is pouring investment into those areas. And then finally, maybe beyond the bottom line, and the top line is how do you harden that and protect that with, um, security and resilience? So I'll probably say those are the three areas. John, >>You know, the business model side, obviously the enablement is what Amazon has. Um, we see things like SAS factory coming on board and the partner network, obviously a century is a big, huge partner of you guys. Um, the business models there, you've got I, as, as doing great with chips, you have this data modeling this data opportunity to enable these modern apps. We heard about the partner strategy for me and D um, talking to me now about how can partners within even Accenture, w w what's the business model, um, side on your side that you're enabling this. Can you just share your thoughts on that? >>Yeah, yeah. And so it's, it's interesting. I think I'm going to build it and then build a little bit on some of the things that Andy really talked about there, right? And that we, if you think of that from the partnership, we are absolutely helping our customers with kind of that it modernization piece. And we're investing a lot and there's hard work that needs to get done there. And we're investing a lot as a partnership around the tools, the assets and the methodology. So in AWS and Accenture show up together as AEG, we are executing office single blueprint with a single set of assets, so we can move fast. So we're going to continue to do that with all the hybrid announcements from this past week, those get baked into that, that migration modernization theme, but the other really important piece here as we go up the stack, Andy mentioned it, right? >>The data piece, like so much of what we're talking about here is around data and insights. Right? I did a cube interview last week with, uh, Carl hick. Um, who's the CIO from Takeda. And if you hear Christophe Weber from Takeda talk, he talks about Takeda being a data company, data and insights company. So how do we, as a partnership, again, build the capabilities and the platforms like with Accenture's applied insights platform so that we can bootstrap and really accelerate our client's journey. And then finally, on the innovation on the business front, and Andy was touching on some of these, we are investing in industry solutions and accelerators, right? Because we know that at the end of the day, a lot of these are very similar. We're talking about ingesting data, using machine learning to provide insights and then taking action. So for instance, the cognitive insurance platform that we're working together on with Accenture, if they give out property and casualty claims and think about how do we enable touchless claims using machine learning and computer vision that can assess based on an image damage, and then be able to triage that and process it accordingly, right? >>Using all the latest machine learning capabilities from AWS with that deep, um, AI machine learning data science capability from Accenture, who knows all those algorithms that need to get built and build that library by doing that, we can really help these insurance companies accelerate their transformation around how they think about claims and how they can speed those claims on behalf of their policy holder. So that's an example of a, kind of like a bottom to top, uh, view of what we're doing in the partnership to address these new needs. >>That's awesome. Andy, I want to get back to your point about culture. You mentioned it twice now. Um, talent is a big part of the game here. Andy Jassy referenced Lambda. The next generation developers were using Lambda. He talked about CIO stories around, they didn't move fast enough. They lost three years. A new person came in and made it go faster. This is a new, this is a time for a certain kind of, um, uh, professional and individual, um, to, to be part of, um, this next generation. What's the talent strategy you guys have to attract and attain the best and retain the people. How do you do it? >>Um, you know, it's, it's, um, it's an interesting one. It's, it's, it's oftentimes a, it's, it's a significant point and often overlooked. Um, you know, people, people really matter and getting the right people, um, in not just in AWS or it, but then in our customers is super important. We often find that much of our discussions with, with our clients is centered around that. And it's really a key ingredient. As you touched on, you need people who are willing to embrace change, but also people who are willing to create new, um, to invent new, to reinvent, um, and to, to keep it very simple. Um, w we're we're we're seeing increasingly that you need people that have a sort of deep learning and a deep, uh, or deep desire to keep learning and to be very curious as, as they go along. Most of all, though, I find that, um, having people who are not willing or not afraid to fail is critical, absolutely critical. Um, and I think that that's, that's, uh, a necessary ingredient that we're seeing, um, our clients needing more off, um, because if you can't start and, and, and you can't iterate, um, you know, for fear of failure, you're in trouble. And, and I think Andy touched on that you, you know, where that CIO, that you referred to last three years, um, and so you really do need people who are willing to start not afraid to start, uh, and, uh, and not afraid to lead >>Was a gut check there. I just say, you guys have a great team over there. Everyone at the center I've interviewed strong, talented, and not afraid to lean in and, and into the trends. Um, I got to ask on that front cloud first was something that was a big strategic focus for Accenture. How does that fit into your business group? That's an Amazon focused, obviously they're cloud, and now hybrid everywhere, as I say, um, how does that all work it out? >>We're super excited about our cloud first initiative, and I think it fits it, um, really, uh, perfectly it's it's, it's what we needed. It's, it's, it's a, it's another accelerant. Um, if you think of count first, what we're doing is we're, we're putting together, um, uh, you know, capability set that will help enable him to and transformations as Brian touched on, you know, help companies move from just, you know, migrating to, to, to modernizing, to driving insights, to bringing in change, um, and, and, and helping on that, on that talent side. So that's sort of component number one is how does Accenture bring the best, uh, end to end transformation capabilities to our clients? Number two is perhaps, you know, how do we, um, uh, bring together pre-assembled as Brian touched on pre-assembled industry offerings to help as an accelerant, uh, for our, for our customers three years, as we touched on earlier is, is that sort of partnership with the ecosystem. >>We're going to see an increasing number of SAS providers in an estate, in the enterprise of snakes out there. And so, you know, panto wild cloud first, and our ABG strategy is to increase our touch points in our integrations and our solutions and our offerings with the ecosystem partners out there, the ISP partners out, then the SAS providers out there. And then number four is really about, you know, how do we, um, extend the definition of the cloud? I think oftentimes people thought of the cloud just as sort of on-prem and prem. Um, but, but as Andy touched on earlier this week, you know, you've, you've got this concept of hybrid cloud and that in itself, um, uh, is, is, is, you know, being redefined as well. You know, when you've got the intelligent edge and you've got various forms of the edge. Um, so that's the fourth part of, of, uh, of occupied for strategy. And for us was super excited because all of that is highly relevant for ABG, as we look to build those capabilities as industry solutions and others, and as when to enable our customers, but also how we, you know, as we, as we look to extend how we go to market, I'll join tele PS, uh, in, uh, in our respective skews and products. >>Well, what's clear now is that people now realize that if you contain that complexity, the upside is massive. And that's great opportunity for you guys. We got to get to the final question for you guys to weigh in on, as we wrap up next five years, Brian, Andy weigh in, how do you see that playing out? What do you see this exciting, um, for the partnership and the cloud first cloud, everywhere cloud opportunities share some perspective. >>Yeah, I, I think, you know, just kinda building on that cloud first, right? What cloud first, and we were super excited when cloud first was announced and you know, what it signals to the market and what we're seeing in our customers, which has cloud really permeates everything that we're doing now. Um, and so all aspects of the business will get infused with cloud in some ways, you know, it, it touches on, on all pieces. And I think what we're going to see is just a continued acceleration and getting much more efficient about pulling together the disparate, what had been disparate pieces of these transformations, and then using automation using machine learning to go faster. Right? And so, as we started thinking about the stack, right, well, we're going to get, I know we are, as a partnership is we're already investing there and getting better and more efficient every day as the migration pieces and the moving the assets to the cloud are just going to continue to get more automated, more efficient. And those will become the economic engines that allow us to fund the differentiated, innovative activities up the stack. So I'm excited to see us kind of invest to make those, those, um, those bets accelerated for customers so that we can free up capital and resources to invest where it's going to drive the most outcome for their end customers. And I think that's going to be a big focus and that's going to have the industry, um, you know, focus. It's going to be making sure that we can >>Consume the latest and greatest of AWS as capabilities and, you know, in the areas of machine learning and analytics, but then Andy's also touched on it bringing in ecosystem partners, right? I mean, one of the most exciting wins we had this year, and this year of COVID is looking at the universe, looking at Massachusetts, the COVID track and trace solution that we put in place is a partnership between Accenture, AWS, and Salesforce, right? So again, bringing together three really leading partners who can deliver value for our customers. I think we're going to see a lot more of that as customers look to partnerships like this, to help them figure out how to bring together the best of the ecosystem to drive solutions. So I think we're going to see more of that as well. >>All right, Andy final word, your take >>Thinks of innovation is, is picking up, um, dismiss things are just going faster and faster. I'm just super excited and looking forward to the next five years as, as you know, the technology invention, um, comes out and continues to sort of set new standards from AWS. Um, and as we, as Accenture wringing, our industry capabilities, we marry the two. We, we go and help our customers super exciting time. >>Well, congratulations on the partnership. I want to say thank you to you guys, because I've reported a few times some stories around real successes around this COVID pandemic that you guys worked together on with Amazon that really changed people's lives. Uh, so congratulations on that too as well. I want to call that out. Thanks for coming >>Up. Thank you. Thanks for coming on. >>Okay. This is the cubes coverage, essentially. AWS partnership, part of a century executive summit at Atrius reinvent 2020 I'm John for your host. Thanks. >>You're watching from around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Hello, and welcome back to the cubes coverage of AWS reinvent 2020. This is special programming for the century executive summit, where all the thought leaders going to extract the signal from the nose to share with you their perspective of this year's reinvent conference, as it respects the customers' digital transformation. Brian Bohan is the director and head of a center. ADA was business group at Amazon web services. Brian, great to see you. And Chris Wegman is the, uh, center, uh, Amazon business group technology lead at Accenture. Um, guys, this is about technology vision, this, this conversation, um, Chris, I want to start with you because you, Andy Jackson's keynote, you heard about the strategy of digital transformation, how you gotta lean into it. You gotta have the guts to go for it, and you got to decompose. He went everywhere. So what, what did you hear? What was striking about the keynote? Because he covered a lot of topics. Yeah. You know, it >>Was Epic, uh, as always for Mandy, a lot of topics, a lot to cover in the three hours. Uh, there was a couple of things that stood out for me, first of all, hybrid, uh, the concept, the new concept of hybrid and how Andy talked about it, you know, uh, bringing the compute and the power to all parts of the enterprise, uh, whether it be at the edge or are in the big public cloud, uh, whether it be in an outpost or wherever it might be right with containerization now, uh, you know, being able to do, uh, Amazon containerization in my data center and that that's, that's awesome. I think that's gonna make a big difference, all that being underneath the Amazon, uh, console and billing and things like that, which is great. Uh, I'll also say the, the chips, right. And I know compute is always something that, you know, we always kind of take for granted, but I think again, this year, uh, Amazon and Andy really focused on what they're doing with the chips and PR and compute, and the compute is still at the heart of everything in cloud. And that continued advancement is, is making an impact and will make a continue to make a big impact. >>Yeah, I would agree. I think one of the things that really, I mean, the container thing was, I think really kind of a nuanced point when you got Deepak sing on the opening day with Andy Jassy and he's, he runs a container group over there, you know, small little team he's on the front and front stage. That really is the key to the hybrid. And I think this showcases this new layer and taking advantage of the graviton two chips that, which I thought was huge. Brian, this is really a key part of the platform change, not change, but the continuation of AWS higher level servers building blocks that provide more capabilities, heavy lifting as they say, but the new services that are coming on top really speaks to hybrid and speaks to the edge. >>It does. Yeah. And it, it, you know, I think like Andy talks about, and we talk about, I, you know, we really want to provide choice to our customers, uh, first and foremost, and you can see that and they re uh, services. We have, we can see it in the, the hybrid options that Chris talked about, being able to run your containers through ECS or EKS anywhere I just get to the customer's choice. And one of the things that I'm excited about as you talk about going up the stack and on the edge are things will certainly outpost. Um, right. So now I'll post those launched last year, but then with the new form factors, uh, and then you look at services like Panorama, right? Being able to take computer vision and embed machine learning and computer vision, and do that as a managed capability at the edge, um, for customers. >>And so we see this across a number of industries. And so what we're really thinking about is customers no longer have to make trade-offs and have to think about those, those choices that they can really deploy, uh, natively in the cloud. And then they can take those capabilities, train those models, and then deploy them where they need to, whether that's on premises or at the edge, you know, whether it be in a factory or retail environment. When we start, I think we're really well positioned when, um, you know, hopefully next year we started seeing the travel industry rebound, um, and the, the need, you know, more than ever really to, uh, to kind of rethink about how we kind of monitor and make those environments safe. Having this kind of capability at the edge is really going to help our customers as, as we come out of this year and hopefully rebound next year. >>Yeah. Chris, I want to go back to you for a second. It's hard to hard to pick your favorite innovation from the keynote, because, you know, just reminded me that Brian just reminded me of some things I forgot happened. It was like a buffet of innovation. Some keynotes have one or two, it was like 20, you got the industrial piece that was huge. Computer vision machine learning. That's just a game changer. The connect thing came out of nowhere, in my opinion, I mean, it's a call center technology. This is boring as hell. What are you gonna do with that? It turns out it's a game changer. It's not about the calls with the contact and that's discern intermediating, um, in the stack as well. So again, a feature that looks old is actually new and relevant. What's your, what was your favorite, um, innovation? >>Uh, it it's, it's, it's hard to say. I will say my personal favorite was the, the maca last. I, I just, I think that is a phenomenal, um, uh, just addition, right? And the fact that AWS is, has worked with Apple to integrate the Nitra chip into, into, uh, you know, the iMac and offer that out. Um, you know, a lot of people are doing development, uh, on for ILS and that stuff. And that there's just gonna be a huge benefit, uh, for the development teams. But, you know, I will say, I'll come back to connect you. You mentioned it. Um, you know, but you're right. It was a, it's a boring area, but it's an area that we've seen huge success with since, since connect was launched and the additional features and the Amazon continues to bring, you know, um, obviously with, with the pandemic and now that, you know, customer engagement through the phone, uh, through omni-channel has just been critical for companies, right. >>And to be able to have those agents at home, working from home versus being in the office, it was a huge, huge advantage for, for several customers that are using connect. You know, we, we did some great stuff with some different customers, but the continue technology, like you said, the, you know, the call translation and during a call to be able to pop up those key words and have a, have a supervisor, listen is awesome. And a lot of that was some of that was already being done, but we were stitching multiple services together. Now that's right out of the box. Um, and that Google's location is only going to make that go faster and make us to be able to innovate faster for that piece of the business. >>It's interesting, you know, not to get all nerdy and, and business school life, but you've got systems of records, systems of engagement. If you look at the call center and the connect thing, what got my attention was not only the model of disintermediating, that part of the engagement in the stack, but what actually cloud does to something that's a feature or something that could be an element, like say, call center, you old days of, you know, calling an 800 number, getting some support you got in chip, you have machine learning, you actually have stuff in the, in the stack that actually makes that different now. So you w you know, the thing that impressed me was Andy was saying, you could have machine learning, detect pauses, voice inflections. So now you have technology making that more relevant and better and different. So a lot going on, this is just one example of many things that are happening from a disruption innovation standpoint. W what do you guys, what do you guys think about that? And is that like getting it right? Can you share it? >>I think, I think, I think you are right. And I think what's implied there and what you're saying, and even in the, you know, the macro S example is the ability if we're talking about features, right. Which by themselves, you're saying, Oh, wow, what's, what's so unique about that, but because it's on AWS and now, because whether you're a developer working on, you know, w with Mac iOS and you have access to the 175 plus services, that you can then weave into your new applications, talk about the connect scenario. Now we're embedding that kind of inference and machine learning to do what you say, but then your data Lake is also most likely running in AWS, right? And then the other channels, whether they be mobile channels or web channels, or in store physical channels, that data can be captured in that same machine learning could be applied there to get that full picture across the spectrum. Right? So that's the, that's the power of bringing together on AWS to access to all those different capabilities of services, and then also the where the data is, and pulling all that together, that for that end to end view, okay, >>You guys give some examples of work you've done together. I know this stuff we've reported on. Um, in the last session we talked about some of the connect stuff, but that kind of encapsulates where this, where this is all going with respect to the tech. >>Yeah. I think one of the, you know, it was called out on Doug's partner summit was, you know, is there a, uh, an SAP data Lake accelerator, right? Almost every enterprise has SAP, right. And SAP getting data out of SAP has always been a challenge, right. Um, whether it be through, you know, data warehouses and AWS, sorry, SAP BW, you know, what we've focused on is, is getting that data when you're on have SAP on AWS getting that data into the data Lake, right. And getting it into, into a model that you can pull the value out of the customers can pull the value out, use those AI models. Um, so that was one thing we worked on in the last 12 months, super excited about seeing great success with customers. Um, you know, a lot of customers had ideas. They want to do this. They had different models. What we've done is, is made it very, uh, simplified, uh, framework that allows customers to do it very quickly, get the data out there and start getting value out of it and iterating on that data. Um, we saw customers are spending way too much time trying to stitch it all together and trying to get it to work technically. Uh, and we've now cut all that out and they can immediately start getting down to, to the data and taking advantage of those, those different, um, services are out there by AWS. >>Brian, you want to weigh in as things you see as relevant, um, builds that you guys done together that kind of tease out the future and connect the dots to what's coming. >>Uh, I, you know, I'm going to use a customer example. Uh, we worked with, um, and it just came out with, with Unilever around their blue air connected, smart air purifier. And what I think is interesting about that, I think it touches on some of the themes we're talking about, as well as some of the themes we talked about in the last session, which is we started that program before the pandemic. Um, and, but, you know, Unilever recognized that they needed to differentiate their product in the marketplace, move to more of a services oriented business, which we're seeing as a trend. We, uh, we enabled this capability. So now it's a smart air purifier that can be remote manage. And now in the pandemic head, they are in a really good position, obviously with a very relevant product and capability, um, to be used. And so that data then, as we were talking about is going to reside on the cloud. And so the learning that can now happen about usage and about, you know, filter changes, et cetera, can find its way back into future iterations of that valve, that product. And I think that's, that's keeping with, you know, uh, Chris was talking about where we might be systems of record, like in SAP, how do we bring those in and then start learning from that data so that we can get better on our future iterations? >>Hey, Chris, on the last segment we did on the business mission, um, session, Andy Taylor from your team, uh, talked about partnerships within a century and working with other folks. I want to take that now on the technical side, because one of the things that we heard from, um, Doug's, um, keynote and that during the partner day was integrations and data were two big themes. When you're in the cloud, technically the integrations are different. You're going to get unique things in the public cloud that you're just not going to get on premise access to other cloud native technologies and companies. How has that, how do you see the partnering of Accenture with people within your ecosystem and how the data and the integration play together? What's your vision? >>Yeah, I think there's two parts of it. You know, one there's from a commercial standpoint, right? So marketplace, you know, you, you heard Dave talk about that in the, in the partner summit, right? That marketplace is now bringing together this ecosystem, uh, in a very easy way to consume by the customers, uh, and by the users and bringing multiple partners together. And we're working with our ecosystem to put more products out in the marketplace that are integrated together, uh, already. Um, you know, I think one from a technical perspective though, you know, if you look at Salesforce, you know, we talked a little earlier about connect another good example, technically underneath the covers, how we've integrated connect and Salesforce, some of it being prebuilt by AWS and Salesforce, other things that we've added on top of it, um, I think are good examples. And I think as these ecosystems, these IFCs put their products out there and start exposing more and more API APIs, uh, on the Amazon platform, make opening it up, having those, those prebuilt network connections there between, you know, the different VPCs and the different areas within, within a customer's network. >>Um, and having them, having that all opened up and connected and having all that networking done underneath the covers. You know, it's one thing to call the API APIs. It's one thing to have access to those. And that's been a big focus of a lot of, you know, ISBNs and customers to build those API APIs and expose them, but having that network infrastructure and being able to stay within the cloud within AWS to make those connections, the past that data, we always talk about scale, right? It's one thing if I just need to pass like a, you know, a simple user ID back and forth, right? That's, that's fine. We're not talking massive data sets, whether it be seismic data or whatever it be passing those of those large, those large data sets between customers across the Amazon network is going to, is going to open up the world. >>Yeah. I see huge possibilities there and love to keep on this story. I think it's going to be important and something to keep track of. I'm sure you guys will be on top of it. You know, one of the things I want to, um, dig into with you guys now is Andy had kind of this philosophy philosophical thing in his keynote, talk about societal change and how tough the pandemic is. Everything's on full display. Um, and this kind of brings out kind of like where we are and the truth. You look at the truth, it's a virtual event. I mean, it's a website and you got some sessions out there with doing remote best weekend. Um, and you've got software and you've got technology and, you know, the concept of a mechanism it's software, it does something, it does a purpose. Essentially. You guys have a concept called living systems where growth strategy powered by technology. How do you take the concept of a, of a living organism or a system and replace the mechanism, staleness of computing and software. And this is kind of an interesting, because we're on the cusp of a, of a major inflection point post COVID. I get the digital transformation being slow that's yes, that's happening. There's other things going on in society. What do you guys think about this living systems concept? >>Yeah, so I, you know, I'll start, but, you know, I think the living system concept, um, you know, it started out very much thinking about how do you rapidly change the system, right? And, and because of cloud, because of, of dev ops, because of, you know, all these software technologies and processes that we've created, you know, that's where it started it, making it much easier to make it a much faster being able to change rapidly, but you're right. I think as you now bring in more technologies, the AI technology self-healing technologies, again, you're hurting Indian in his keynote, talk about, you know, the, the systems and services they're building to the tech problems and, and, and, and give, uh, resolve those problems. Right. Obviously automation is a big part of that living systems, you know, being able to bring that all together and to be able to react in real time to either what a customer, you know, asks, um, you know, either through the AI models that have been generated and turning those AI models around much faster, um, and being able to get all the information that came came in in the last 20 minutes, right. >>You know, society's moving fast and changing fast. And, you know, even in one part of the world, if, um, something, you know, in 10 minutes can change and being able to have systems to react to that, learn from that and be able to pass that on to the next country, especially in this world with COVID and, you know, things changing very quickly with quickly and, and, and, um, diagnosis and, and, um, medical response, all that so quickly to be able to react to that and have systems pass that information learned from that information is going to be critical. >>That's awesome. Brian, one of the things that comes up every year is, Oh, the cloud scalable this year. I think, you know, we've, we've talked on the cube before, uh, years ago, certainly with the censure and Amazon, I think it was like three or four years ago. Yeah. The clouds horizontally scalable, but vertically specialized at the application layer. But if you look at the data Lake stuff that you guys have been doing, where you have machine learning, the data's horizontally scalable, and then you got the specialization in the app changes that changes the whole vertical thing. Like you don't need to have a whole vertical solution or do you, so how has this year's um, cloud news impacted vertical industries because it used to be, Oh, the oil and gas financial services. They've got a team for that. We've got a stack for that. Not anymore. Is it going away? What's changing. Wow. >>I, you know, I think it's a really good question. And I don't think, I think what we're saying, and I was just on a call this morning talking about banking and capital markets. And I do think the, you know, the, the challenges are still pretty sector specific. Um, but what we do see is the, the kind of commonality, when we start looking at the, and we talked about it as the industry solutions that we're building as a partnership, most of them follow the pattern of ingesting data, analyzing that data, and then being able to, uh, provide insights and an actions. Right. So if you think about creating that yeah. That kind of common chassis of that ingest the data Lake and then the machine learning, can you talk about, you know, the announces around SageMaker and being able to manage these models, what changes then really are the very specific industries algorithms that you're, you're, you're writing right within that framework. And so we're doing a lot in connect is a good example of this too, where you look at it. Yeah. Customer service is a horizontal capability that we're building out, but then when you stop it into insurance or retail banking or utilities, there are nuances then that we then extend and build so that we meet the unique needs of those, those industries. And that's usually around those, those models. >>Yeah. And I think this year was the first reinvented. I saw real products coming out that actually solve that problem. And that was their last year SageMaker was kinda moving up the stack, but now you have apps embedding machine learning directly in, and users don't even know it's in there. I mean, Christmas is kind of where it's going. Right. I mean, >>Yeah. Announcements. Right. How many, how many announcements where machine learning is just embedded in? I mean, so, you know, code guru, uh, dev ops guru Panorama, we talked about, it's just, it's just there. >>Yeah. I mean, having that knowledge about the linguistics and the metadata, knowing the, the business logic, those are important specific use cases for the vertical and you can get to it faster. Right. Chris, how is this changing on the tech side, your perspective? Yeah. >>You know, I keep coming back to, you know, AWS and cloud makes it easier, right? None of this stuff, you know, all of this stuff can be done, uh, and has some of it has been, but you know, what Amazon continues to do is make it easier to consume by the developer, by the, by the customer and to actually embedded into applications much easier than it would be if I had to go set up the stack and build it all on that and, and, and, uh, embed it. Right. So it's, shortcutting that process. And again, as these products continue to mature, right. And some of the stuff is embedded, um, it makes that process so much faster. Uh, it makes it reduces the amount of work required by the developers, uh, the engineers to get there. So I I'm expecting, you're going to see more of this. >>Right. I think you're going to see more and more of these multi connected services by AWS that has a lot of the AIML, um, pre-configured data lakes, all that kind of stuff embedded in those services. So you don't have to do it yourself and continue to go up the stack. And we was talking about, Amazon's built for builders, right. But, you know, builders, you know, um, have been super specialized in, or we're becoming, you know, as engineers, we're being asked to be bigger and bigger and to be, you know, uh, be able to do more stuff. And I think, you know, these kinds of integrated services are gonna help us do that >>And certainly needed more. Now, when you have hybrid edge that are going to be operating with microservices on a cloud model, and with all those advantages that are going to come around the corner for being in the cloud, I mean, there's going to be, I think there's going to be a whole clarity around benefits in the cloud with all these capabilities and benefits cloud guru. Thanks my favorite this year, because it just points to why that could happen. I mean, that happens because of the cloud data. If you're on premise, you may not have a little cloud guru, you got to got to get more data. So, but they're all different edge certainly will come into your vision on the edge. Chris, how do you see that evolving for customers? Because that could be complex new stuff. How is it going to get easier? >>Yeah. It's super complex now, right? I mean, you gotta design for, you know, all the different, uh, edge 5g, uh, protocols are out there and, and, and solutions. Right. You know, Amazon's simplifying that again, to come back to simplification. Right. I can, I can build an app that, that works on any 5g network that's been integrated with AWS. Right. I don't have to set up all the different layers to get back to my cloud or back to my, my bigger data side. And I was kind of choking. I don't even know where to call the cloud anymore, big cloud, which is a central and I go down and then I've got a cloud at the edge. Right. So what do I call that? >>Exactly. So, you know, again, I think it is this next generation of technology with the edge comes, right. And we put more and more data at the edge. We're asking for more and more compute at the edge, right? Whether it be industrial or, you know, for personal use or consumer use, um, you know, that processing is gonna get more and more intense, uh, to be able to manage and under a single console, under a single platform and be able to move the code that I develop across that entire platform, whether I have to go all the way down to the, you know, to the very edge, uh, at the, at the 5g level, right? Or all the way into the bigger cloud and how that process, isn't there be able to do that. Seamlessly is going to be allow the speed of development that's needed. >>Well, you guys done a great job and no better time to be a techie or interested in technology or computer science or social science for that matter. This is a really perfect storm, a lot of problems to solve a lot of things, a lot of change happening, positive change opportunities, a lot of great stuff. Uh, final question guys, five years working together now on this partnership with AWS and Accenture, um, congratulations, you guys are in pole position for the next wave coming. Um, what's exciting. You guys, Chris, what's on your mind, Brian. What's, what's getting you guys pumped up >>Again. I come back to G you know, Andy mentioned it in his keynote, right? We're seeing customers move now, right. We're seeing, you know, five years ago we knew customers were going to get a new, this. We built a partnership to enable these enterprise customers to make that, that journey. Right. But now, you know, even more, we're seeing them move at such great speed. Right. Which is super excites me. Right. Because I can see, you know, being in this for a long time, now I can see the value on the other end. And I really, we've been wanting to push our customers as fast as they can through the journey. And now they're moving out of, they're getting, they're getting the religion, they're getting there. They see, they need to do it to change your business. So that's what excites me is just the excites me. >>It's just the speed at which we're, we're in a single movement. Yeah, yeah. I'd agree with, yeah, I'd agree with that. I mean, so, you know, obviously getting, getting customers to the cloud is super important work, and we're obviously doing that and helping accelerate that, it's it, it's what we've been talking about when we're there, all the possibilities that become available right. Through the common data capabilities, the access to the 175 some-odd AWS services. And I also think, and this is, this is kind of permeated through this week at re-invent is the opportunity, especially in those industries that do have an industrial aspect, a manufacturing aspect, or a really strong physical aspect of bringing together it and operational technology and the business with all these capabilities, then I think edge and pushing machine learning down to the edge and analytics at the edge is really going to help us do that. And so I'm super excited by all that possibility is I feel like we're just scratching the surface there, >>Great time to be building out. And you know, this is the time for re reconstruction. Re-invention big themes. So many storylines in the keynote, in the events. It's going to keep us busy here. It's looking at angle in the cube for the next year. Gentlemen, thank you for coming out. I really appreciate it. Thanks. Thank you. All right. Great conversation. You're getting technical. We could've go on another 30 minutes. Lot to talk about a lot of storylines here at AWS. Reinvent 2020 at the Centure executive summit. I'm John furrier. Thanks for watching.

>>from around the globe. It's the Cube with digital coverage of AWS reinvent 2020 sponsored by Intel AWS and our community partners. Welcome everyone to the Cube virtual and our coverage of the Accenture Executive Summit, which is part of AWS reinvent 2020. I'm your host Rebecca Knight. Today we're talking about the green Cloud and joining me is Kishore Dirk. He is Accenture Senior Managing director Cloud First Global Services lead. Thank you so much for coming on the show Key Shore. >>Nice to meet you, Rebecca. >>Great to have you. Yeah. So I want to start by asking you what it is that we mean when we say green cloud. We know the sustainability is a business imperative. So many organizations around the world are committing to responsible innovation lowering carbon emissions. But what does this? What does it? What does it mean when they talk about cloud from a sustainability perspective? >>E think it's about responsible innovation. Green Cloud is a thoughtful cloud first approach that helps boost profits and benefit the clients for helping reduce carbon emissions. Think about it this way. And you have a large number of data centers and each of these data centers are increasing by 14% every year, and this double digit growth comes with the price of Becca. What you're seeing is these global data centers consume a lot of power on the consumption is nearly pull into the consumption of a country like Spain. So the magnitude off the problem that is out there and and how do we pursue a green approach if you look at this hour? Accenture Analysis In terms of the migrations to public crowd, we have seen that we can reduce that by 59 million tons of CO two per year and with just the 5.9% reduction in top lighting emissions. And he creates this toe 22 million cars off the road. And the magnitude of reduction can go a long way. Meeting climate change commitments, particularly poor data sensitive businesses. >>Wow, that's incredible. What you're the numbers that you're putting forward are absolutely mind blowing. So how does it work? Is it a simple cloud migration? So, you know, >>when companies begin their cloud journey and and then they confront off with them a lot of questions. The decision to make uh, in this particular element sustainable in their solution and benefits. They drive and they had to make vice choices. And then they will gain unprecedented level of innovation, leading to both greener planet as well as a a green of balance sheet. I would say eso effectively. It's all about ambition. Greater the ambition, greater the reduction in carbon emissions. So from a cloud migration perspective, we look at it as a simple solution with approaches and sustainability. Benefits are that very based on things. It's about selecting the right cloud provider, very carbon thoughtful provider and the first step towards a sustainable cloud journey. And here we're looking at clown operators. You know, obviously they have different corporate commitments towards sustainability and that determines how they plan, how they build their the data centers, how they our and consume connections that operate there and how they retire their data centers. Then, uh, the next element that you want to do is how do you build it? Ambition, You know, for some of the companies, on average on Prem drives about 65% energy reduction and the carbon emission reduction of about 84% which is kind of OK and good I would say, But then, if you could go up to 98% by configuring applications to the cloud, that is significant benefit for for the world. And obviously it's a greener cloud that we're talking about. And then the question is, How far can you go? And, you know, obviously the companies have to unlock greater financial, societal environmental benefits. And essential has this cloud based circular operations and sustainable products and services that that you bring into play. So it's a It's a very thoughtful, broader approach that we're bringing and in terms off just a simple concept off migration s. >>So we know that in the covert era, shifting to the cloud has really become a business imperative. How is Accenture working with its clients at a time when all of this movement has been accelerated? How do you partner and what is your approach in terms of helping them with their migrations? >>Yeah, I mean, let me talk a little bit about the pandemic and the crisis that is there today, and and if you really look at that in terms of how your partner with a lot of our clients in terms of the cloud first approach. I'll give you a couple of examples. We've worked with Rolls Royce, McClaren, DHL and others as part of the ventilator UK Charon Consortium again to, uh, coordinate production of medical ventilators urgently needed for the UK Health Service. Many of these firms have taken similar initiatives in terms off, you know, from perfume manufacturers hand sanitizers. And to answer it is, is and again leading passion levels, making BP and again at the U. N. General Assembly. We launched the end to end integration Guy that helps company essentially to have a sustainable development goes. And that's how we're parting at a very large scale. Andi, if you really look at how we work with our clients and what's Accenture's role there? Uh, you know, from in terms of our clients, you know there are multiple steps that we look at. One is about planning, building, deploying and managing an optimal green color solution. And Accenture has this concept off helping clients for the platform to kind of achieve that goal. And here we're having. We're having a platform called Minor, which has a model called Green Clad Advisor, and this is the capability that helps you provide optimal green cloud, you know, a business case and obviously blueprint for each of our clients. And right from the start in terms off, how do we complete lower migration recommendation toe on improve solution accuracy to obviously bringing in the end to end perspective? You know, with this green clad adviser capability, we're helping our clients capture what we call it the carbon footprint for existing data centers and provide, uh, I would say the current cloud C 02 emissions core that you know, obviously helps them with carbon credits that can further their green agenda. So essentially, this is about recommending a green index score reducing carbon footprint for migration, migrating for green a cloud. And it really look at how accentuate itself is practicing. What we preached. 95% of the applications are in the cloud, and this migration has helped us. Uh, toe lied to about $42.5 million in benefit and in the third year, and and another three million analyzed costs that are saved through rightsizing service consumption. So it's a very broad umbrella and a footprint in terms of having engage societally with the U. N our clients. And what is it that we exactly bring to our clients in solving a specific problem? >>Accenture isn't is walking the walk as you say? >>Yes, So that that is that we we practice what we preach, and that is something that we take it to heart. We want toe have a responsible business and we want to practice it. And we want to advise our clients around that >>you are your own use case, and so they they know they can take your advice. So talk a little bit about the global, the cooperation that's needed. We know that conquering this pandemic is going to take a coordinated global effort and talk a little bit about the great reset initiative. First of all, what is that? Why don't we? Why don't we start there? And then we could delve into it a little bit more. >>Okay, so before we get to how we're cooperating, the great recent initiative is about improving the state of the world, and it's about a group of global stakeholders cooperating to simultaneously manage the direct consequences of their Cohen 19 prices andan spirit of this cooperation that you're seeing during Court 19 which will obviously either toe post pandemic project will the worth pressing issues. As I say, we're increasing companies to realize combined potential of technology and sustainable impact, to use enterprise solutions to address with urgency and scale and obviously multiple challenges that are facing our world. One of the ways that you're increasing, uh, companies to reach their Venus cloud with extensions cloud strategy is to build a solid foundation that is resilient. I would prefer to faster to the current as well as future times. Now, when you think of Cloud as the foundation that drives the digital transformation, it's about scale, speed, streamlining your operations and obviously reducing costs. And and as these businesses sees the construct of cloud first, they must remain obviously responsible and trusted. Now think about this right as part of our analysis that profitability can co exist with responsible and sustainable practices. Let's say that on the data centers migrated from on from the cloud based, we estimate, you know, that would reduce carbon emissions globally by 60 million tons for years. Andi, think about it this way, right? Easier Metric will be taking out 22 million cars off the road Thea Other examples that you've seen right in terms off the NHS work that they're doing in UK to build, uh, you know, a Microsoft teams were in based integration and the platform he rolled out for 1.2 million in it. Just users Onda. About 16,000 users there were able to secure instant messages, you know, obviously complete audio video calls and host working meetings across England. So this this work that we did with NHS is is something that we're collaborating with a lot of fools and powering businesses, not marriage. >>Well, you're vividly describing the business case for sustainability. What do you see as the future of cloud when thinking about it through this lens of sustainability and also going back to what you were talking about in terms of how you are helping your fostering cooperation within these organizations? >>That's a very good question, because so if you look at today, right, businesses are obviously environmentally aware, and they are expanding efforts to decrease power consumption, carbon emissions, and they want to run a sustainable operational efficiency across all elements of the business. And this is an increasing trend. And there is that option off energy efficient infrastructure in the global market. And this trend is the cloud. First thinking and with the right cloud migration that we've been discussing is what unlocking new opportunity, like clean energy transitions enabled, enabled by cloud based geographic analysis, material based reductions and better data insights. And this is something that, well, we'll drive with obviously faster analytics platform that is out there now. The sustainability is actually the future of business, which is companies that have historically different the financial security or agility benefits to cloud. Now sustainability becomes an imperative for them and our own experience. Accenture's experience with cloud migrations We have seen 30 to 40% total cost of ownership savings on its driving. Ah, greater workloads, flexibility, better service, somebody utilization and obviously more energy efficient public clouds that cost obviously well, that that drive a lot of these enterprise own data centers. So in our view, what we're seeing is that this this, uh, sustainable cloud position helps helps companies to a drive a lot of the goals, in addition to their financial and other goals. >>So what should organizations who are who are watching this interview and saying, Hey, I need to know more. What do you recommend to them and what? Where should they go to get more information on Green Cloud. >>You know, if you're if you're a business leader and you're thinking about which cloud provider is good, how should applications be modernized to meet our day to day needs Which cloud driven innovation should be priorities? Uh, you know, that's why Accenture, uh, from the Cloud First organization and essentially to provide the whole stack of cloud services to help our clients become a cloud first business. You know, it's all about exhibition. The digital transformation innovating faster, creating differentiated and sustainable value for our clients. And we're powering it up with 70,000 cloud professionals, $3 billion investment and bringing together unmasked depth and breadth of cloud services for our clients in terms of plant solutions and obviously the ecosystem partnership that we have that we're seeing today, Andi assets that help our clients realize that goes on and again toe do reach out to us way can help them to two men, obviously an optimal, sustainable cloud for solution that meets the business needs and being unprecedented levels of innovation. Our experience will be an advantage. And now more than ever, Rebecca. >>So just closing us out here, Do you have any advice for these companies who are navigating a great deal of uncertainty? We What? What do you think? The next 12 to 24 months. What do you think that should be on the minds of CEOs as they go >>forward. So as CEOs are thinking about rapidly leveraging cloud migrating to cloud off, one of the elements that we want them to be thoughtful about is can they do that with unprecedented level of innovation, but also build a greener planet and a greener balance sheet? If we can achieve this balance and and kind off have, ah, have, ah, world, which is greener. I think the world will win and we all along with extension of clients, will win. That's what I will say, Rebecca. >>That is an optimistic outlook, and I will take it. Thank you so much. Key shore for coming on the show. >>Thank you so much. >>That was Accenture's Key Shore. Dirk Rebecca. Night. Stay tuned for more of the Cube virtual coverage of the Accenture Executive Summit

>>From around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome to cube three 60 fives coverage of the Accenture executive summit. Part of AWS reinvent. I'm your host Rebecca Knight. Today we are joined by a cube alum, Karthik, Lorraine. He is Accenture senior managing director and lead Accenture cloud. First, welcome back to the show Karthik. >>Thank you. Thanks for having me here. >>Always a pleasure. So I want to talk to you. You are an industry veteran, you've been in Silicon Valley for decades. Um, I want to hear from your perspective what the impact of the COVID-19 pandemic has been, what are you hearing from clients? What are they struggling with? What are their challenges that they're facing day to day? >>I think, um, COVID-19 is being a eye-opener from, you know, various facets, you know, um, first and foremost, it's a, it's a hell, um, situation that everybody's facing, which is not just, uh, highest economic bearings to it. It has enterprise, um, an organization with bedding to it. And most importantly, it's very personal to people, um, because they themselves and their friends, family near and dear ones are going through this challenge, uh, from various different dimension. But putting that aside, when you come to it from an organization enterprise standpoint, it has changed everything well, the behavior of organizations coming together, working in their campuses, working with each other as friends, family, and, uh, um, near and dear colleagues, all of them are operating differently. So that's what big change to get things done in a completely different way, from how they used to get things done. >>Number two, a lot of things that were planned for normal scenarios, like their global supply chain, how they interact with their client customers, how they go innovate with their partners on how that employees contribute to the success of an organization at all changed. And there are no data models that give them a hint of something like this for them to be prepared for this. So we are seeing organizations, um, that have adapted to this reasonably okay, and are, you know, launching to innovate faster in this. And there are organizations that have started with struggling, but are continuing to struggle. And the gap between the leaders and legs are widening. So this is creating opportunities in a different way for the leaders, um, with a lot of pivot their business, but it's also creating significant challenge for the lag guides, uh, as we defined in our future systems research that we did a year ago, uh, and those organizations are struggling further. So the gap is actually widening. >>So you just talked about the widening gap. I've talked about the tremendous uncertainty that so many companies, even the ones who have adapted reasonably well, uh, in this, in this time, talk a little bit about Accenture cloud first and why, why now? >>I think it's a great question. Um, we believe that for many of our clients COVID-19 has turned, uh, cloud from an experimentation aspiration to an origin mandate. What I mean by that is everybody has been doing something on the other end cloud. There's no company that says we don't believe in cloud are, we don't want to do cloud. It was how much they did in cloud. And they were experimenting. They were doing the new things in cloud, but they were operating a lot of their core business outside the cloud or not in the cloud. Those organizations have struggled to operate in this new normal, in a remote fashion, as well as, uh, their ability to pivot to all the changes the pandemic has brought to them. But on the other hand, the organizations that had a solid foundation in cloud were able to collect faster and not actually gone into the stage of innovating faster and driving a new behavior in the market, new behavior within their organization. >>So we are seeing that spend to make is actually fast-forwarded something that we always believed was going to happen. This, uh, uh, moving to cloud over the next decade is fast forward it to happen in the next three to five years. And it's created this moment where it's a once in an era, really replatforming of businesses in the cloud that we are going to see. And we see this moment as a cloud first moment where organizations will use cloud as the, the, the canvas and the foundation with which they're going to reimagine their business after they were born in the cloud. Uh, and this requires a whole new strategy. Uh, and as Accenture, we are getting a lot in cloud, but we thought that this is the moment where we bring all of that, gave him a piece together because we need a strategy for addressing, moving to cloud are embracing cloud in a holistic fashion. And that's what Accenture cloud first brings together a holistic strategy, a team that's 70,000 plus people that's coming together with rich cloud skills, but investing to tie in all the various capabilities of cloud to Delaware, that holistic strategy to our clients. So I want you to >>Delve into a little bit more about what this strategy actually entails. I mean, it's clearly about embracing change and being willing to experiment and having capabilities to innovate. Can you tell us a little bit more about what this strategy entails? >>Yeah. The reason why we say that as a need for strategy is like I said, cloud is not new. There's almost every customer client is doing something with the cloud, but all of them have taken different approaches to cloud and different boundaries to cloud. Some organizations say, I just need to consolidate my multiple data centers to a small data center footprint and move the nest to cloud. Certain other organizations say that well, I'm going to move certain workloads to cloud. Certain other organizations said, well, I'm going to build this Greenfield application or workload in cloud. Certain other said, um, I'm going to use the power of AI ML in the cloud to analyze my data and drive insights. But a cloud first strategy is all of this tied with the corporate strategy of the organization with an industry specific cloud journey to say, if in this current industry, if I were to be reborn in the cloud, would I do it in the exact same passion that I did in the past, which means that the products and services that they offer need to be the matching, how they interact with that customers and partners need to be revisited, how they bird and operate their IP systems need to be the, imagine how they unearthed the data from all of the systems under which they attract need to be liberated so that you could drive insights of cloud. >>First strategy hands is a corporate wide strategy, and it's a C-suite responsibility. It doesn't take the ownership away from the CIO or CIO, but the CIO is, and CDI was felt that it was just their problem and they were to solve it. And everyone as being a customer, now, the center of gravity is elevated to it becoming a C-suite agenda on everybody's agenda, where probably the CDI is the instrument to execute that that's a holistic cloud-first strategy >>And it, and it's a strategy, but the way you're describing it, it sounds like it's also a mindset and an approach, as you were saying, this idea of being reborn in the cloud. So now how do I think about things? How do I communicate? How do I collaborate? How do I get done? What I need to get done. Talk a little bit about how this has changed, the way you support your clients and how Accenture cloud first is changing your approach to cloud services. >>Wonderful. Um, you know, I did not color one very important aspect in my previous question, but that's exactly what you just asked me now, which is to do all of this. I talked about all of the variables, uh, an organization or an enterprise is going to go through, but the good part is they have one constant. And what is that? That is their employees, uh, because you do, the employees are able to embrace this change. If they are able to, uh, change them, says, pivot them says retool and train themselves to be able to operate in this new cloud. First one, the ability to reimagine every function of the business would be happening at speed. And cloud first approach is to do all of this at speed, because innovation is deadly proposed there, do the rate of probability on experimentation. You need to experiment a lot for any kind of experimentation. >>There's a probability of success. Organizations need to have an ability and a mechanism for them to be able to innovate faster for which they need to experiment a lot, the more the experiment and the lower cost at which they experiment is going to help them experiment a lot. And they experiment demic speed, fail fast, succeed more. And hence, they're going to be able to operate this at speed. So the cloud-first mindset is all about speed. I'm helping the clients fast track that innovation journey, and this is going to happen. Like I said, across the enterprise and every function across every department, I'm the agent of this change is going to be the employees or weapon, race, this change through new skills and new grueling and new mindset that they need to adapt to. >>So Karthik what you're describing it, it sounds so exciting. And yet for a pandemic wary workforce, that's been working remotely that may be dealing with uncertainty if for their kid's school and for so many other aspects of their life, it sounds hard. So how are you helping your clients, employees get onboard with this? And because the change management is, is often the hardest part. >>Yeah, I think it's, again, a great question. A bottle has only so much capacity. Something got to come off for something else to go in. That's what you're saying is absolutely right. And that is again, the power of cloud. The reason why cloud is such a fundamental breakthrough technology and capability for us to succeed in this era, because it helps in various forms. What we talked so far is the power of innovation that can create, but cloud can also simplify the life of the employees in an enterprise. There are several activities and tasks that people do in managing that complex infrastructure, complex ID landscape. They used to do certain jobs and activities in a very difficult underground about with cloud has simplified. And democratised a lot of these activities. So that things which had to be done in the past, like managing the complexity of the infrastructure, keeping them up all the time, managing the, um, the obsolescence of the capabilities and technologies and infrastructure, all of that could be offloaded to the cloud. >>So that the time that is available for all of these employees can be used to further innovate. Every organization is going to spend almost the same amount of money, but rather than spending activities, by looking at the rear view mirror on keeping the lights on, they're going to spend more money, more time, more energy, and spend their skills on things that are going to add value to their organization. Because you, every innovation that an enterprise can give to their end customer need not come from that enterprise. The word of platform economy is about democratising innovation. And the power of cloud is to get all of these capabilities from outside the four walls of the enterprise, >>It will add value to the organization, but I would imagine also add value to that employee's life because that employee, the employee will be more engaged in his or her job and therefore bring more excitement and energy into her, his or her day-to-day activities too. >>Absolutely. Absolutely. And this is, this is a normal evolution we would have seen everybody would have seen in their lives, that they keep moving up the value chain of what activities that, uh, gets performed buying by those individuals. And this is, um, you know, no more true than how the United States, uh, as an economy has operated where, um, this is the power of a powerhouse of innovation, where the work that's done inside the country keeps moving up to value chain. And, um, us leverage is the global economy for a lot of things that is required to power the United States and that global economic, uh, phenomenon is very proof for an enterprise as well. There are things that an enterprise needs to do them soon. There are things an employee needs to do themselves. Um, but there are things that they could leverage from the external innovation and the power of innovation that is coming from technologies like cloud. >>So at Accenture, you have long, long, deep Stan, sorry, you have deep and long-standing relationships with many cloud service providers, including AWS. How does the Accenture cloud first strategy, how does it affect your relationships with those providers? >>Yeah, we have great relationships with cloud providers like AWS. And in fact, in the cloud world, it was one of the first, um, capability that we started about years ago, uh, when we started developing these capabilities. But five years ago, we hit a very important milestone where the two organizations came together and said that we are forging a pharma partnership with joint investments to build this partnership. And we named that as a Accenture, AWS business group ABG, uh, where we co-invest and brought skills together and develop solutions. And we will continue to do that. And through that investment, we've also made several acquisitions that you would have seen in the recent times, like, uh, an invoice and gecko that we made acquisitions in in Europe. But now we're taking this to the next level. What we are saying is two cloud first and the $3 billion investment that we are bringing in, uh, through cloud-first. >>We are going to make specific investment to create unique joint solution and landing zones foundation, um, cloud packs with which clients can accelerate their innovation or their journey to cloud first. And one great example is what we are doing with Takeda, uh, billable, pharmaceutical giant, um, between we've signed a five-year partnership. And it was out in the media just a month ago or so, where we are, the two organizations are coming together. We have created a partnership as a power of three partnership, where the three organizations are jointly hoarding hats and taking responsibility for the innovation and the leadership position that Takeda wants to get to with this. We are going to simplify their operating model and organization by providing and flexibility. We're going to provide a lot more insights. Tequila has a 230 year old organization. Imagine the amount of trapped data and intelligence that is there. >>How about bringing all of that together with the power of AWS and Accenture and Takeda to drive more customer insights, um, come up with breakthrough R and D uh, accelerate clinical trials and improve the patient experience using AI ML and edge technologies. So all of these things that we will do through this partnership with joined investment from Accenture cloud first, as well as partner like AWS, so that Takeda can realize their gain. And, uh, their senior actually made a statement that five years from now, every ticket an employee will have an AI assistant. That's going to make that beginner employee move up the value chain on how they contribute and add value to the future of tequila with the AI assistant, making them even more equipped and smarter than what they could be otherwise. >>So, one last question to close this out here. What is your future vision for, for Accenture cloud first? What are we going to be talking about at next year's Accenture executive summit? Yeah, the future >>Is going to be, um, evolving, but the part that is exciting to me, and this is, uh, uh, a fundamental belief that we are entering a new era of industrial revolution from industry first, second, and third industry. The third happened probably 20 years ago with the advent of Silicon and computers and all of that stuff that happened here in the Silicon Valley. I think the fourth industrial revolution is going to be in the cross section of, uh, physical, digital and biological boundaries. And there's a great article, um, in one economic forum that people, uh, your audience can Google and read about it. Uh, but the reason why this is very, very important is we are seeing a disturbing phenomenon that over the last 10 years are seeing a Blackwing of the, um, labor productivity and innovation, which has dropped to about 2.1%. When you see that kind of phenomenon over that longer period of time, there has to be breakthrough innovation that needs to happen to come out of this barrier and get to the next, you know, base camp, as I would call it to further this productivity, um, lack that we are seeing, and that is going to happen in the intersection of the physical, digital and biological boundaries. >>And I think cloud is going to be the connective tissue between all of these three, to be able to provide that where it's the edge, especially is good to come closer to the human lives. It's going to come from cloud. Yeah. Pick totally in your mind, you can think about cloud as central, either in a private cloud, in a data center or in a public cloud, you know, everywhere. But when you think about edge, it's going to be far reaching and coming close to where we live and maybe work and very, um, get entertained and so on and so forth. And there's good to be, uh, intervention in a positive way in the field of medicine, in the field of entertainment, in the field of, um, manufacturing in the field of, um, you know, mobility. When I say mobility, human mobility, people, transportation, and so on and so forth with all of this stuff, cloud is going to be the connective tissue and the vision of cloud first is going to be, uh, you know, blowing through this big change that is going to happen. And the evolution that is going to happen where, you know, the human grace of mankind, um, our person kind of being very gender neutral in today's world. Um, go first needs to be that beacon of, uh, creating the next generation vision for enterprises to take advantage of that kind of an exciting future. And that's why it, Accenture, are we saying that there'll be change as our, as our purpose? >>I genuinely believe that cloud first is going to be in the forefront of that change agenda, both for Accenture as well as for the rest of the work. Excellent. Let there be change, indeed. Thank you so much for joining us Karthik. A pleasure I'm Rebecca nights stay tuned for more of Q3 60 fives coverage of the Accenture executive summit >>From around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS >>Welcome everyone to the Q virtual and our coverage of the Accenture executive summit, which is part of AWS reinvent 2020. I'm your host Rebecca Knight. Today, we are talking about the green cloud and joining me is Kishor Dirk. He is Accenture senior managing director cloud first global services lead. Thank you so much for coming on the show. Kishor nice to meet you. So I want to start by asking you what it is that we mean when we say green cloud, we know the sustainability is a business imperative. So many organizations around the world are committing to responsible innovation, lowering carbon emissions. But what is this? What is it? What does it mean when they talk about cloud from a sustainability perspective? I think it's about responsible innovation being cloud is a cloud first approach that has benefit the clients by helping reduce carbon emissions. Think about it this way. >>You have a large number of data centers. Each of these data centers are increasing by 14% every year. And this double digit growth. What you're seeing is these data centers and the consumption is nearly coolant to the kind of them should have a country like Spain. So the magnitude of the problem that is out there and how do we pursue a green approach. If you look at this, our Accenture analysis, in terms of the migration to public cloud, we've seen that we can reduce that by 59 million tons of CO2 per year with just the 5.9% reduction in total emissions and equates this to 22 million cars off the road. And the magnitude of reduction can go a long way in meeting climate change commitments, particularly for data sensitive. Wow, that's incredible. The numbers that you're putting forward are, are absolutely mind blowing. So how does it work? Is it a simple cloud migration? So, you know, when companies begin their cloud journey and then they confront, uh, with >>Them a lot of questions, the decision to make, uh, this particular, uh, element sustainable in the solution and benefits they drive and they have to make wise choices, and then they will gain unprecedented level of innovation leading to both a greener planet, as well as, uh, a greener balance sheet, I would say, uh, so effectively it's all about ambition, data ambition, greater the reduction in carbon emissions. So from a cloud migration perspective, we look at it as a, as a simple solution with approaches and sustainability benefits, uh, that vary based on things it's about selecting the right cloud provider, a very carbon thoughtful provider and the first step towards a sustainable cloud journey. And here we're looking at cloud operators know, obviously they have different corporate commitments towards sustainability, and that determines how they plan, how they build, uh, their, uh, uh, the data centers, how they are consumed and assumptions that operate there and how they, or they retire their data centers. >>Then, uh, the next element that you want to do is how do you build it ambition, you know, for some of the companies, uh, and average on-prem, uh, drives about 65% energy reduction and the carbon emission reduction number was 84%, which is kind of good, I would say. But then if you could go up to 98% by configuring applications to the cloud, that is significant benefit for, uh, for the board. And obviously it's a, a greener cloud that we're talking about. And then the question is, how far can you go? And, uh, you know, the, obviously the companies have to unlock greater financial societal environmental benefits, and Accenture has this cloud based circular operations and sustainable products and services that we bring into play. So it's a, it's a very thoughtful, broader approach that w bringing in, in terms of, uh, just a simple concept of cloud migration. >>So we know that in the COVID era, shifting to the cloud has really become a business imperative. How is Accenture working with its clients at a time when all of this movement has been accelerated? How do you partner and what is your approach in terms of helping them with their migrations? >>Yeah, I mean, let, let me talk a little bit about the pandemic and the crisis that is that today. And if you really look at that in terms of how we partnered with a lot of our clients in terms of the cloud first approach, I'll give you a couple of examples. We worked with rolls, Royce, MacLaren, DHL, and others, as part of the ventilator, a UK challenge consortium, again, to, uh, coordinate production of medical ventilator surgically needed for the UK health service. Many of these farms I've taken similar initiatives in, in terms of, uh, you know, from a few manufacturers hand sanitizers, and to answer it as us and again, leading passionate labels, making PPE, and again, at the UN general assembly, we launched the end-to-end integration guide that helps company is essentially to have a sustainable development goals. And that's how we are parking at a very large scale. >>Uh, and, and if you really look at how we work with our clients and what is Accenture's role there, uh, you know, from, in terms of our clients, you know, there are multiple steps that we look at. One is about planning, building, deploying, and managing an optimal green cloud solution. And Accenture has this concept of, uh, helping clients with a platform to kind of achieve that goal. And here we are having, we are having a platform or a mine app, which has a module called BGR advisor. And this is a capability that helps you provide optimal green cloud, uh, you know, a business case, and obviously a blueprint for each of our clients and right from the start in terms of how do we complete cloud migration recommendation to an improved solution, accurate accuracy to obviously bringing in the end to end perspective, uh, you know, with this green card advisor capability, we're helping our clients capture what we call as a carbon footprint for existing data centers and provide, uh, I would say the current cloud CO2 emission score that, you know, obviously helps them, uh, with carbon credits that can further that green agenda. >>So essentially this is about recommending a green index score, reducing carbon footprint for migration migrating for green cloud. And if we look at how Accenture itself is practicing what we preach, 95% of our applications are in the cloud. And this migration has helped us, uh, to lead to about $14.5 million in benefit. And in the third year and another 3 million analytics costs that are saved through right-sizing a service consumption. So it's a very broad umbrella and a footprint in terms of how we engage societaly with the UN or our clients. And what is it that we exactly bring to our clients in solving a specific problem? >>Accenture isn't is walking the walk, as you say, >>Instead of it, we practice what we preach, and that is something that we take it to heart. We want to have a responsible business and we want to practice it. And we want to advise our clients around that >>You are your own use case. And so they can, they know they can take your advice. So talk a little bit about, um, the global, the cooperation that's needed. We know that conquering this pandemic is going to take a coordinated global effort and talk a little bit about the great reset initiative. First of all, what is that? Why don't we, why don't we start there and then we can delve into it a little bit more. >>Okay. So before we get to how we are cooperating, the great reset, uh, initiative is about improving the state of the world. And it's about a group of global stakeholders cooperating to simultaneously manage the direct consequences of their COVID-19 crisis. Uh, and in spirit of this cooperation that we're seeing during COVID-19, uh, which will obviously either to post pandemic, to tackle the world's pressing issues. As I say, uh, we are increasing companies to realize a combined potential of technology and sustainable impact to use enterprise solutions, to address with urgency and scale, and, um, obviously, uh, multiple challenges that are facing our world. One of the ways that are increasing, uh, companies to reach their readiness cloud with Accenture's cloud strategy is to build a solid foundation that is resilient and will be able to faster to the current, as well as future times. Now, when you think of cloud as the foundation, uh, that drives the digital transformation, it's about scale speed, streamlining your operations, and obviously reducing costs. >>And as these businesses seize the construct of cloud first, they must remain obviously responsible and trusted. Now think about this, right, as part of our analysis, uh, that profitability can co-exist with responsible and sustainable practices. Let's say that all the data centers, uh, migrated from on-prem to cloud based, we estimate that would reduce carbon emissions globally by 60 million tons per year. Uh, and think about it this way, right? Easier metric would be taking out 22 million cars off the road. Um, the other examples that you've seen, right, in terms of the NHS work that they're doing, uh, in, in UK to build, uh, uh, you know, uh, Microsoft teams in based integration. And, uh, the platform rolled out for 1.2 million users, uh, and got 16,000 users that we were able to secure, uh, instant messages, obviously complete audio video calls and host virtual meetings across India. So, uh, this, this work that we did with NHS is, is something that we have, we are collaborating with a lot of tools and powering businesses. >>Well, you're vividly describing the business case for sustainability. What do you see as the future of cloud when thinking about it from this lens of sustainability, and also going back to what you were talking about in terms of how you are helping your, your fostering cooperation within these organizations. >>Yeah, that's a very good question. So if you look at today, right, businesses are obviously environmentally aware and they are expanding efforts to decrease power consumption, carbon emissions, and they want to run a sustainable operational efficiency across all elements of their business. And this is an increasing trend, and there is that option of energy efficient infrastructure in the global market. And this trend is the cloud first thinking. And with the right cloud migration that we've been discussing is about unlocking new opportunity, like clean energy foundations enable enabled by cloud based geographic analysis, material, waste reductions, and better data insights. And this is something that, uh, uh, will drive, uh, with obviously faster analytics platform that is out there. Now, the sustainability is actually the future of business, which is companies that are historically different, the financial security or agility benefits to cloud. Now sustainability becomes an imperative for them. And I would own experience Accenture's experience with cloud migrations. We have seen 30 to 40% total cost of ownership savings, and it's driving a greater workload, flexibility, better service, your obligation, and obviously more energy efficient, uh, public clouds that cost, uh, we'll see that, that drive a lot of these enterprise own data centers. So in our view, what we are seeing is that this, this, uh, sustainable cloud position helps, uh, helps companies to, uh, drive a lot of the goals in addition to their financial and other goods. >>So what should organizations who are, who are watching this interview and saying, Hey, I need to know more, what, what do you recommend to them? And what, where should they go to get more information on Greenplum? >>Yeah. If you wanna, if you are a business leader and you're thinking about which cloud provider is good, or how, how should applications be modernized to meet our day-to-day needs, which cloud driven innovations should be priorities. Uh, you know, that's why Accenture, uh, formed up the cloud first organization and essentially to provide the full stack of cloud services to help our clients become a cloud first business. Um, you know, it's all about excavation, uh, the digital transformation innovating faster, creating differentiated, uh, and sustainable value for our clients. And we are powering it up at 70,000 cloud professionals, $3 billion investment, and, uh, bringing together and services for our clients in terms of cloud solutions. And obviously the ecosystem partnership that we have that we are seeing today, uh, and, and the assets that help our clients realize their goals. Um, and again, to do reach out to us, uh, we can help them determine obviously, an optimal, sustainable cloud for solution that meets the business needs and being unprecedented levels of innovation. Our experience, uh, will be our advantage. And, uh, now more than ever Rebecca, >>Just closing us out here. Do you have any advice for these companies who are navigating a great deal of uncertainty? We, what, what do you think the next 12 to 24 months? What do you think that should be on the minds of CEOs as they go through? >>So, as CEO's are thinking about rapidly leveraging cloud, migrating to cloud, uh, one of the elements that we want them to be thoughtful about is can they do that, uh, with unprecedent level of innovation, but also build a greener planet and a greener balance sheet, if we can achieve this balance and kind of, uh, have a, have a world which is greener, I think the world will win. And we all along with Accenture clients will win. That's what I would say, uh, >>Optimistic outlook, and I will take it. Thank you so much. Kishor for coming on the show >>That was >>Accenture's Kishor Dirk, I'm Rebecca Knight stay tuned for more of the cube virtuals coverage of the Accenture executive summit >>Around the globe. >>It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome everyone to the cube virtual and our coverage of the Accenture executive summit. Part of AWS reinvent 2020. I'm your host Rebecca Knight. Today, we are talking about the power of three. And what happens when you bring together the scientific know-how of a global bias biopharmaceutical powerhouse in Takeda, a leading cloud services provider in AWS, and Accenture's ability to innovate, execute, and deliver innovation. Joining me to talk about these things. We have Aaron, sorry, Arjun, baby. He is the senior managing director and chairman of Accenture's diamond leadership council. Welcome Arjun, Karl hick. He is the chief digital and information officer at Takeda. What is your bigger, thank you, Rebecca and Brian bowhead, global director, and head of the Accenture AWS business group at Amazon web services. Thanks so much for coming up. So, as I said, we're talking today about this relationship between, uh, your three organizations. Carl, I want to talk with you. I know you're at the beginning of your cloud journey. What was the compelling reason? What w why, why move to the cloud and why now? >>Yeah, no, thank you for the question. So, you know, as a biopharmaceutical leader, we're committed to bringing better health and a brighter future to our patients. We're doing that by translating science into some really innovative and life transporting therapies, but throughout, you know, we believe that there's a responsible use of technology, of data and of innovation. And those three ingredients are really key to helping us deliver on that promise. And so, you know, while I think, uh, I'll call it, this cloud journey is already always been a part of our strategy. Um, and we've made some pretty steady progress over the last years with a number of I'll call it diverse approaches to the digital and AI. We just weren't seeing the impact at scale that we wanted to see. Um, and I think that, you know, there's a, there's a need ultimately to, you know, accelerate and, uh, broaden that shift. >>And, you know, we were commenting on this earlier, but there's, you know, it's been highlighted by a number of factors. One of those has been certainly a number of the large acquisitions we've made Shire, uh, being the most pressing example, uh, but also the global pandemic, both of those highlight the need for us to move faster, um, at the speed of cloud, ultimately. Uh, and so we started thinking outside of the box because it was taking us too long and we decided to leverage the strategic partner model. Uh, and it's giving us a chance to think about our challenges very differently. We call this the power of three, uh, and ultimately our focus is singularly on our patients. I mean, they're waiting for us. We need to get there faster. It can take years. And so I think that there is a focus on innovation, um, at a rapid speed, so we can move ultimately from treating conditions to keeping people healthy. >>So, as you are embarking on this journey, what are some of the insights you want to share about, about what you're seeing so far? >>Yeah, no, it's a great question. So, I mean, look, maybe right before I highlight some of the key insights, uh, I would say that, you know, with cloud now as the, as the launchpad for innovation, you know, our vision all along has been that in less than 10 years, we want every single to kid, uh, associate we're employed to be empowered by an AI assistant. And I think that, you know, that's going to help us make faster, better decisions. It'll help us, uh, fundamentally deliver transformative therapies and better experiences to, to that ecosystem, to our patients, to physicians, to payers, et cetera, much faster than we previously thought possible. Um, and I think that technologies like cloud and edge computing together with a very powerful I'll call it data fabric is going to help us to create this, this real-time, uh, I'll call it the digital ecosystem. >>The data has to flow ultimately seamlessly between our patients and providers or partners or researchers, et cetera. Uh, and so we've been thinking about this, uh, I'll call it, we call it sort of this pyramid, um, that helps us describe our vision. Uh, and a lot of it has to do with ultimately modernizing the foundation, modernizing and rearchitecting, the platforms that drive the company, uh, heightening our focus on data, which means that there's an accelerated shift towards, uh, enterprise data platforms and digital products. And then ultimately, uh, uh, P you know, really an engine for innovation sitting at the very top. Um, and so I think with that, you know, there's a few different, I'll call it insights that, you know, are quickly kind of come zooming into focus. I would say one is this need to collaborate very differently. Um, you know, not only internally, but you know, how do we define ultimately, and build a connected digital ecosystem with the right partners and technologies externally? >>I think the second component that maybe people don't think as much about, but, you know, I find critically important is for us to find ways of really transforming our culture. We have to unlock talent and shift the culture certainly as a large biopharmaceutical very differently. And then lastly, you've touched on it already, which is, you know, innovation at the speed of cloud. How do we re-imagine that, you know, how do ideas go from getting tested and months to kind of getting tested in days? You know, how do we collaborate very differently? Uh, and so I think those are three, uh, perhaps of the larger I'll call it, uh, insights that, you know, the three of us are spending a lot of time thinking about right now. >>So Arjun, I want to bring you into this conversation a little bit, let let's delve into those a bit. Talk first about the collaboration, uh, that Carl was referencing there. How, how have you seen that? It is enabling, uh, colleagues and teams to communicate differently and interact in new and different ways? Uh, both internally and externally, as Carl said, >>No, th thank you for that. And, um, I've got to give call a lot of credit, because as we started to think about this journey, it was clear, it was a bold ambition. It was, uh, something that, you know, we had all to do differently. And so the, the concept of the power of three that Carl has constructed has become a label for us as a way to think about what are we going to do to collectively drive this journey forward. And to me, the unique ways of collaboration means three things. The first one is that, um, what is expected is that the three parties are going to come together and it's more than just the sum of our resources. And by that, I mean that we have to bring all of ourselves, all of our collective capabilities, as an example, Amazon has amazing supply chain capabilities. >>They're one of the best at supply chain. So in addition to resources, when we have supply chain innovations, uh, that's something that they're bringing in addition to just, uh, talent and assets, similarly for Accenture, right? We do a lot, uh, in the talent space. So how do we bring our thinking as to how we apply best practices for talent to this partnership? So, um, as we think about this, so that's, that's the first one, the second one is about shared success very early on in this partnership, we started to build some foundations and actually develop seven principles that all of us would look at as the basis for this success shared success model. And we continue to hold that sort of in the forefront, as we think about this collaboration. And maybe the third thing I would say is this one team mindset. So whether it's the three of our CEOs that get together every couple of months to think about, uh, this partnership, or it is the governance model that Carl has put together, which has all three parties in the governance and every level of leadership. We always think about this as a collective group, so that we can keep that front and center. And what I think ultimately has enabled us to do is it allowed us to move at speed, be more flexible. And ultimately all we're looking at the target the same way, the North side, the same way. >>Brian, what about you? What have you observed? And are you thinking about in terms of how this is helping teams collaborate differently, >>Lillian and Arjun made some, some great points there. And I think if you really think about what he's talking about, it's that, that diversity of talent, diversity of scale and viewpoint and even culture, right? And so we see that in the power of three. And then I think if we drill down into what we see at Takeda, and frankly, Takeda was, was really, I think, pretty visionary and on their way here, right? And taking this kind of cross functional approach and applying it to how they operate day to day. So moving from a more functional view of the world to more of a product oriented view of the world, right? So when you think about we're going to be organized around a product or a service or a capability that we're going to provide to our customers or our patients or donors in this case, it implies a different structure, although altogether, and a different way of thinking, right? >>Because now you've got technical people and business experts and marketing experts, all working together in this is sort of cross collaboration. And what's great about that is it's really the only way to succeed with cloud, right? Because the old ways of thinking where you've got application people and infrastructure, people in business, people is suboptimal, right? Because we can all access this tool as these capabilities and the best way to do that. Isn't across kind of a cross-collaborative way. And so this is product oriented mindset. It's a keto was already on. I think it's allowed us to move faster in those areas. >>Carl, I want to go back to this idea of unlocking talent and culture. And this is something that both Brian and Arjun have talked about too. People are an essential part of their, at the heart of your organization. How will their experience of work change and how are you helping re-imagine and reinforce a strong organizational culture, particularly at this time when so many people are working remotely. >>Yeah. It's a great question. And it's something that, you know, I think we all have to think a lot about, I mean, I think, um, you know, driving this, this call it, this, this digital and data kind of capability building, uh, takes a lot of, a lot of thinking. So, I mean, there's a few different elements in terms of how we're tackling this one is we're recognizing, and it's not just for the technology organization or for those actors that, that we're innovating with, but it's really across all of the Cato where we're working through ways of raising what I'll call the overall digital leaders literacy of the organization, you know, what are the, you know, what are the skills that are needed almost at a baseline level, even for a global bio-pharmaceutical company and how do we deploy, I'll call it those learning resources very broadly. >>And then secondly, I think that, you know, we're, we're very clear that there's a number of areas where there are very specialized skills that are needed. Uh, my organization is one of those. And so, you know, we're fostering ways in which, you know, we're very kind of quickly kind of creating, uh, avenues excitement for, for associates in that space. So one example specifically, as we use, you know, during these very much sort of remote, uh, sort of days, we, we use what we call global it meet days, and we set a day aside every single month and this last Friday, um, you know, we, we create during that time, it's time for personal development. Um, and we provide active seminars and training on things like, you know, robotic process automation, data analytics cloud, uh, in this last month we've been doing this for months and months now, but in his last month, more than 50% of my organization participated, and there's this huge positive shift, both in terms of access and excitement about really harnessing those new skills and being able to apply them. >>Uh, and so I think that that's, you know, one, one element that, uh, can be considered. And then thirdly, um, of course, every organization to work on, how do you prioritize talent, acquisition and management and competencies that you can't rescale? I mean, there are just some new capabilities that we don't have. And so there's a large focus that I have with our executive team and our CEO and thinking through those critical roles that we need to activate in order to kind of, to, to build on this, uh, this business led cloud transformation. And lastly, probably the hardest one, but the one that I'm most jazzed about is really this focus on changing the mindsets and behaviors. Um, and I think there, you know, this is where the power of three is, is really, uh, kind of coming together nicely. I mean, we're working on things like, you know, how do we create this patient obsessed curiosity, um, and really kind of unlock innovation with a real, kind of a growth mindset. >>Uh, and the level of curiosity that's needed, not to just continue to do the same things, but to really challenge the status quo. So that's one big area of focus we're having the agility to act just faster. I mean, to worry less, I guess I would say about kind of the standard chain of command, but how do you make more speedy, more courageous decisions? And this is places where we can emulate the way that a partner like AWS works, or how do we collaborate across the number of boundaries, you know, and I think, uh, Arjun spoke eloquently to a number of partnerships that we can build. So we can break down some of these barriers and use these networks, um, whether it's within our own internal ecosystem or externally to help, to create value faster. So a lot of energy around ways of working and we'll have to check back in, but I mean, we're early in on this mindset and behavioral shift, um, but a lot of good early momentum. >>Carl you've given me a good segue to talk to Brian about innovation, because you said a lot of the things that I was the customer obsession and this idea of innovating much more quickly. Obviously now the world has its eyes on drug development, and we've all learned a lot about it, uh, in the past few months and accelerating drug development is all, uh, is of great interest to all of us. Brian, how does a transformation like this help a company's, uh, ability to become more agile and more innovative and add a quicker speed to, >>Yeah, no, absolutely. And I think some of the things that Carl talked about just now are critical to that, right? I think where sometimes folks fall short is they think, you know, we're going to roll out the technology and the technology is going to be the silver bullet where in fact it is the culture, it is, is the talent. And it's the focus on that. That's going to be, you know, the determinant of success. And I will say, you know, in this power of three arrangement and Carl talked a little bit about the pyramid, um, talent and culture and that change, and that kind of thinking about that has been a first-class citizen since the very beginning, right. That absolutely is critical for, for being there. Um, and, and so that's been, that's been key. And so we think about innovation at Amazon and AWS, and Carl mentioned some of the things that, you know, partner like AWS can bring to the table is we talk a lot about builders, right? >>So kind of obsessive about builders. Um, and, and we meet what we mean by that is we at Amazon, we hire for builders, we cultivate builders and we like to talk to our customers about it as well. And it also implies a different mindset, right? When you're a builder, you have that, that curiosity, you have that ownership, you have that stake and whatever I'm creating, I'm going to be a co-owner of this product or this service, right. Getting back to that kind of product oriented mindset. And it's not just the technical people or the it people who are builders. It is also the business people as, as Carl talked about. Right. So when we start thinking about, um, innovation again, where we see folks kind of get into a little bit of a innovation pilot paralysis, is that you can focus on the technology, but if you're not focusing on the talent and the culture and the processes and the mechanisms, you're going to be putting out technology, but you're not going to have an organization that's ready to take it and scale it and accelerate it. >>Right. And so that's, that's been absolutely critical. So just a couple of things we've been doing with, with Takeda and Decatur has really been leading the way is, think about a mechanism and a process. And it's really been working backward from the customer, right? In this case, again, the patient and the donor. And that was an easy one because the key value of Decatur is to be a patient focused bio-pharmaceutical right. So that was embedded in their DNA. So that working back from that, that patient, that donor was a key part of that process. And that's really deep in our DNA as well. And Accenture's, and so we were able to bring that together. The other one is, is, is getting used to experimenting and even perhaps failing, right. And being able to iterate and fail fast and experiment and understanding that, you know, some decisions, what we call it at Amazon are two two-way doors, meaning you can go through that door, not like what you see and turn around and go back. And cloud really helps there because the costs of experimenting and the cost of failure is so much lower than it's ever been. You can do it much faster and the implications are so much less. So just a couple of things that we've been really driving, uh, with the cadence around innovation, that's been really critical. Carl, where are you already seeing signs of success? >>Yeah, no, it's a great question. And so we chose, you know, uh, with our focus on innovation to try to unleash maybe the power of data digital in, uh, in focusing on what I call sort of a nave. And so we chose our, our, our plasma derived therapy business, um, and you know, the plasma-derived therapy business unit, it develops critical life-saving therapies for patients with rare and complex diseases. Um, but what we're doing is by bringing kind of our energy together, we're focusing on creating, I'll call it state of the art digitally connected donation centers. And we're really modernizing, you know, the, the, the donor experience right now, we're trying to, uh, improve also I'll call it the overall plasma collection process. And so we've, uh, selected a number of alcohol at a very high speed pilots that we're working through right now, specifically in this, in this area. And we're seeing >>Really great results already. Um, and so that's, that's one specific area of focus are Jen, I want you to close this out here. Any ideas, any best practices advice you would have for other pharmaceutical companies that are, that are at the early stage of their cloud journey? Sorry. Was that for me? Yes. Sorry. Origin. Yeah, no, I was breaking up a bit. No, I think they, um, the key is what's sort of been great for me to see is that when people think about cloud, you know, you always think about infrastructure technology. The reality is that the cloud is really the true enabler for innovation and innovating at scale. And, and if you think about that, right, and all the components that you need, ultimately, that's where the value is for the company, right? Because yes, you're going to get some cost synergies and that's great, but the true value is in how do we transform the organization in the case of the Qaeda and our life sciences clients, right. >>We're trying to take a 14 year process of research and development that takes billions of dollars and compress that right. Tremendous amounts of innovation opportunity. You think about the commercial aspect, lots of innovation can come there. The plasma derived therapy is a great example of how we're going to really innovate to change the trajectory of that business. So I think innovation is at the heart of what most organizations need to do. And the formula, the cocktail that the Qaeda has constructed with this footie program really has all the ingredients, um, that are required for that success. Great. Well, thank you so much. Arjun, Brian and Carl was really an enlightening conversation. Thank you. It's been a lot of, thank you. Yeah, it's been fun. Thanks Rebecca. And thank you for tuning into the cube. Virtual has coverage of the Accenture executive summit >>From around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome everyone to the cubes coverage of Accenture executive summit here at AWS reinvent. I'm your host Rebecca Knight for this segment? We have two guests. First. We have Helen Davis. She is the senior director of cloud platform services, assistant director for it and digital for the West Midlands police. Thanks so much for coming on the show, Helen, and we also have Matthew pound. He is Accenture health and public service associate director and West Midlands police account lead. Thanks so much for coming on the show. Matthew, thank you for having us. So we are going to be talking about delivering data-driven insights to the West Midlands police force. Helen, I want to start with >>You. Can you tell us a little bit about the West Midlands police force? How big is the force and also what were some of the challenges that you were grappling with prior to this initiative? >>Yeah, certainly. So Westerners police is the second largest police force in the UK, outside of the metropolitan police in London. Um, we have an excessive, um, 11,000 people work at Westman ins police serving communities, um, through, across the Midlands region. So geographically, we're quite a big area as well, as well as, um, being population, um, density, having that as a, at a high level. Um, so the reason we sort of embarked on the data-driven insights platform and it, which was a huge change for us was for a number of reasons. Um, namely we had a lot of disparate data, um, which was spread across a range of legacy systems that were many, many years old, um, with some duplication of what was being captured and no single view for offices or, um, support staff. Um, some of the access was limited. You have to be in a, in an actual police building on a desktop computer to access it. Um, other information could only reach the offices on the frontline through a telephone call back to one of our enabling services where they would do a manual checkup, um, look at the information, then call the offices back, um, and tell them what they needed to know. So it was a very long laborious, um, process and not very efficient. Um, and we certainly weren't exploiting the data that we had in a very productive way. >>So it sounds like as you're describing and an old clunky system that needed a technological, uh, reimagination, so what was the main motivation for, for doing, for making this shift? >>It was really, um, about making us more efficient and more effective in how we do how we do business. So, um, you know, certainly as a, as an it leader and sort of my operational colleagues, we recognize the benefits, um, that data and analytics could bring in, uh, in a policing environment, not something that was, um, really done in the UK at the time. You know, we have a lot of data, so we're very data rich and the information that we have, but we needed to turn it into information that was actionable. So that's where we started looking for, um, technology partners and suppliers to help us and sort of help us really with what's the art of the possible, you know, this hasn't been done before. So what could we do in this space that's appropriate for policing? >>I love that idea. What is the art of the possible, can you tell us a little bit about why you chose AWS? >>I think really, you know, as with all things and when we're procuring a partner in the public sector that, you know, there are many rules and regulations, uh, quite rightly as you would expect that to be because we're spending public money. So we have to be very, very careful and, um, it's, it's a long process and we have to be open to public scrutiny. So, um, we sort of look to everything, everything that was available as part of that process, but we recognize the benefits that Clyde would provide in this space because, you know, without moving to a cloud environment, we would literally be replacing something that was legacy with something that was a bit more modern. Um, that's not what we wanted to do. Our ambition was far greater than that. So I think, um, in terms of AWS, really, it was around the scalability, interoperability, you know, disaster things like the disaster recovery service, the fact that we can scale up and down quickly, we call it dialing up and dialing back. Um, you know, it's it's page go. So it just sort of ticked all the boxes for us. And then we went through the full procurement process, fortunately, um, it came out on top for us. So we were, we were able to move forward, but it just sort of had everything that we were looking for in that space. >>Matthew, I want to bring you into the conversation a little bit here. How are you working with a wet with the West Midlands police, sorry. And helping them implement this cloud-first journey? >>Yeah, so I guess, um, by January the West Midlands police started, um, favorite five years ago now. So, um, we set up a partnership with the force. I wanted to operate in a way that it was very different to a traditional supplier relationship. Um, secretary that the data difference insights program is, is one of many that we've been working with last nights on, um, over the last five years. Um, as having said already, um, cloud gave a number of, uh, advantages certainly from a big data perspective and the things that that enabled us today, um, I'm from an Accenture perspective that allowed us to bring in a number of the different themes that we have say, cloud teams, security teams, um, and drafted from an insurance perspective, as well as more traditional services that people would associate with the country. >>I mean, so much of this is about embracing comprehensive change to experiment and innovate and try different things. Matthew, how, how do you help, uh, an entity like West Midlands police think differently when they are, there are these ways of doing things that people are used to, how do you help them think about what is the art of the possible, as Helen said, >>There's a few things to that enable those being critical is trying to co-create solutions together. Yeah. There's no point just turning up with, um, what we think is the right answer, try and say, um, collectively work three, um, the issues that the fullest is seeing and the outcomes they're looking to achieve rather than simply focusing on a long list of requirements, I think was critical and then being really open to working together to create the right solution. Um, rather than just, you know, trying to pick something off the shelf that maybe doesn't fit the forces requirements in the way that it should too, >>Right. It's not always a one size fits all. >>Absolutely not. You know, what we believe is critical is making sure that we're creating something that met the forces needs, um, in terms of the outcomes they're looking to achieve the financial envelopes that were available, um, and how we can deliver those in a, uh, iterative agile way, um, rather than spending years and years, um, working towards an outcome, um, that is gonna update before you even get that. >>So Helen, how, how are things different? What kinds of business functions and processes have been re-imagined in, in light of this change and this shift >>It's, it's actually unrecognizable now, um, in certain areas of the business as it was before. So to give you a little bit of, of context, when we, um, started working with essentially in AWS on the data driven insights program, it was very much around providing, um, what was called locally, a wizzy tool for our intelligence analysts to interrogate data, look at data, you know, decide whether they could do anything predictive with it. And it was very much sort of a back office function to sort of tidy things up for us and make us a bit better in that, in that area or a lot better in that area. And it was rolled out to a number of offices, a small number on the front line. Um, I'm really, it was, um, in line with a mobility strategy that we, hardware officers were getting new smartphones for the first time, um, to do sort of a lot of things on, on, um, policing apps and things like that to again, to avoid them, having to keep driving back to police stations, et cetera. >>And the pilot was so successful. Every officer now has access to this data, um, on their mobile devices. So it literally went from a handful of people in an office somewhere using it to do sort of clever bang things to, um, every officer in the force, being able to access that level of data at their fingertips. Literally. So what they were touched with done before is if they needed to check and address or check details of an individual, um, just as one example, they would either have to, in many cases, go back to a police station to look it up themselves on a desktop computer. Well, they would have to make a call back to a centralized function and speak to an operator, relay the questions, either, wait for the answer or wait for a call back with the answer when those people are doing the data interrogation manually. >>So the biggest change for us is the self-service nature of the data we now have available. So officers can do it themselves on their phone, wherever they might be. So the efficiency savings from that point of view are immense. And I think just parallel to that is the quality of our, because we had a lot of data, but just because you've got a lot of data and a lot of information doesn't mean it's big data and it's valuable necessarily. Um, so again, it was having the single source of truth as we, as we call it. So you know that when you are completing those safe searches and getting the responses back, that it is the most accurate information we hold. And also you're getting it back within minutes, as opposed to, you know, half an hour, an hour or a drive back to a station. So it's making officers more efficient and it's also making them safer. The more efficient they are, the more time they have to spend out with the public doing what they, you know, we all should be doing >>That kind of return on investment because what you were just describing with all the steps that we needed to be taken in prior to this, to verify an address say, and those are precious seconds when someone's life is on the line in, in sort of in the course of everyday police work. >>Absolutely. Yeah, absolutely. It's difficult to put a price on it. It's difficult to quantify. Um, but all the, you know, the minutes here and there certainly add up to a significant amount of efficiency savings, and we've certainly been able to demonstrate the officers are spending less time up police stations as a result or more time out on the front line. Also they're safer because they can get information about what may or may not be and address what may or may not have occurred in an area before very, very quickly without having to wait. >>I do, I want to hear your observations of working so closely with this West Midlands police. Have you noticed anything about changes in its culture and its operating model in how police officers interact with one another? Have you seen any changes since this technology change? >>What's unique about the Western displaces, the buy-in from the top down, the chief and his exact team and Helen as the leader from an IOT perspective, um, the entire force is bought in. So what is a significant change program? Uh, I'm not trickles three. Um, everyone in the organization, um, change is difficult. Um, and there's a lot of time effort that's been put in to bake the technical delivery and the business change and adoption aspects around each of the projects. Um, but you can see the step change that is making in each aspect to the organization, uh, and where that's putting West Midlands police as a leader in, um, technology I'm policing in the UK. And I think globally, >>And this is a question for both of you because Matthew, as you said, change is difficult and there is always a certain intransigence in workplaces about this is just the way we've always done things and we're used to this and don't try us to get us. Don't try to get us to do anything new here. It works. How do you get the buy-in that you need to do this kind of digital transformation? >>I think it would be wrong to say it was easy. Um, um, we also have to bear in mind that this was one program in a five-year program. So there was a lot of change going on, um, both internally for some of our back office functions, as well as front tie, uh, frontline offices. So with DDI in particular, I think the stack change occurred when people could see what it could do for them. You know, we had lots of workshops and seminars where we all talk about, you know, big data and it's going to be great and it's data analytics and it's transformational, you know, and quite rightly people that are very busy doing a day job, but not necessarily technologists in the main and, you know, are particularly interested quite rightly so in what we are not dealing with the cloud, you know? And it was like, yeah, okay. >>It's one more thing. And then when they started to see on that, on their phones and what teams could do, that's when it started to sell itself. And I think that's when we started to see, you know, to see the stat change, you know, and, and if we, if we have any issues now it's literally, you know, our help desks in meltdown. Cause everyone's like, well, we call it manage without this anymore. And I think that speaks for itself. So it doesn't happen overnight. It's sort of incremental changes and then that's a step change in attitude. And when they see it working and they see the benefits, they want to use it more. And that's how it's become fundamental to all policing by itself, really, without much selling >>You, Helen just made a compelling case for how to get buy in. Have you discovered any other best practices when you are trying to get everyone on board for this kind of thing? >>We've um, we've used a lot of the traditional techniques, things around comms and engagement. We've also used things like, um, the 30 day challenge and nudge theory around how can we gradually encourage people to use things? Um, I think there's a point where all of this around, how do we just keep it simple and keep it user centric from an end user perspective? I think DDI is a great example of where the, the technology is incredibly complex. The solution itself is, um, you know, extremely large and, um, has been very difficult to, um, get delivered. But at the heart of it is a very simple front end for the user to encourage it and take that complexity away from them. Uh, I think that's been critical through the whole piece of DDR. >>One final word from Helen. I want to hear, where do you go from here? What is the longterm vision? I know that this has made productivity, um, productivity savings equivalent to 154 full-time officers. Uh, what's next, >>I think really it's around, um, exploiting what we've got. Um, I use the phrase quite a lot, dialing it up, which drives my technical architects crazy, but because it's apparently not that simple, but, um, you know, we've, we've been through significant change in the last five years and we are still continuing to batch all of those changes into everyday, um, operational policing. But what we need to see is we need to exploit and build on the investments that we've made in terms of data and claims specifically, the next step really is about expanding our pool of data and our functions. Um, so that, you know, we keep getting better and better at this. Um, the more we do, the more data we have, the more refined we can be, the more precise we are with all of our actions. Um, you know, we're always being expected to, again, look after the public purse and do more for less. And I think this is certainly an and our cloud journey and cloud first by design, which is where we are now, um, is helping us to be future-proofed. So for us, it's very much an investment. And I see now that we have good at embedded in operational policing for me, this is the start of our journey, not the end. So it's really exciting to see where we can go from here. >>Exciting times. Indeed. Thank you so much. Lily, Helen and Matthew for joining us. I really appreciate it. Thank you. And you are watching the cube stay tuned for more of the cubes coverage of the AWS reinvent Accenture executive summit. I'm Rebecca Knight from around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Hi, everyone. Welcome to the cube virtual coverage of the executive summit at AWS reinvent 2020 virtual. This is the cube virtual. We can't be there in person like we are every year we have to be remote. This executive summit is with special programming supported by Accenture where the cube virtual I'm your host John for a year, we had a great panel here called uncloud first digital transformation from some experts, Stuart driver, the director of it and infrastructure and operates at lion Australia, Douglas Regan, managing director, client account lead at lion for Accenture as a deep Islam associate director application development lead for Accenture gentlemen, thanks for coming on the cube virtual that's a mouthful, all that digital, but the bottom line it's cloud transformation. This is a journey that you guys have been on together for over 10 years to be really a digital company. Now, some things have happened in the past year that kind of brings all this together. This is about the next generation organization. So I want to ask Stuart you first, if you can talk about this transformation at lion has undertaken some of the challenges and opportunities and how this year in particular has brought it together because you know, COVID has been the accelerant of digital transformation. Well, if you're 10 years in, I'm sure you're there. You're in the, uh, on that wave right now. Take a minute to explain this transformation journey. >>Yeah, sure. So number of years back, we looked at kind of our infrastructure and our landscape trying to figure out where we >>Wanted to go next. And we were very analog based and stuck in the old it groove of, you know, Capitol reef rash, um, struggling to transform, struggling to get to a digital platform and we needed to change it up so that we could become very different business to the one that we were back then obviously cloud is an accelerant to that. And we had a number of initiatives that needed a platform to build on. And a cloud infrastructure was the way that we started to do that. So we went through a number of transformation programs that we didn't want to do that in the old world. We wanted to do it in a new world. So for us, it was partnering up with a dried organizations that can take you on the journey and, uh, you know, start to deliver bit by bit incremental progress, uh, to get to the, uh, I guess the promise land. >>Um, we're not, not all the way there, but to where we're on the way along. And then when you get to some of the challenges like we've had this year, um, it makes all of the hard work worthwhile because you can actually change pretty quickly, um, provide capacity and, uh, and increase your environments and, you know, do the things that you need to do in a much more dynamic way than we would have been able to previously where we might've been waiting for the hardware vendors, et cetera, to deliver capacity. So for us this year, it's been a pretty strong year from an it perspective and delivering for the business needs >>Before I hit the Douglas. I want to just real quick, a redirect to you and say, you know, if all the people said, Oh yeah, you got to jump on cloud, get in early, you know, a lot of naysayers like, well, wait till to mature a little bit, really, if you got in early and you, you know, paying your dues, if you will taking that medicine with the cloud, you're really kind of peaking at the right time. Is that true? Is that one of the benefits that comes out of this getting in the cloud? Yeah, >>John, this has been an unprecedented year, right. And, um, you know, Australia, we had to live through Bush fires and then we had covert and, and then we actually had to deliver a, um, a project on very large transformational project, completely remote. And then we also had had some, some cyber challenges, which is public as well. And I don't think if we weren't moved into and enabled through the cloud, we would have been able to achieve that this year. It would have been much different, would have been very difficult to do the backing. We're able to work and partner with Amazon through this year, which is unprecedented and actually come out the other end. Then we've delivered a brand new digital capability across the entire business. Um, in many, you know, wouldn't have been impossible if we could, I guess, state in the old world, the fact that we were moved into the new Naval by the new allowed us to work in this unprecedented year. >>Just quick, what's your personal view on this? Because I've been saying on the Cuban reporting necessity is the mother of all invention and the word agility has been kicked around as kind of a cliche, Oh, it'd be agile. You know, we're going to get the city, you get a minute on specifically, but from your perspective, uh, Douglas, what does that mean to you? Because there is benefits there for being agile. And >>I mean, I think as Stuart mentioned, right, in a lot of these things we try to do and, you know, typically, you know, hardware and of the last >>To be told and, and, and always on the critical path to be done, we really didn't have that in this case, what we were doing with our projects in our deployments, right. We were able to move quickly able to make decisions in line with the business and really get things going. Right. So you see a lot of times in a traditional world, you have these inhibitors, you have these critical path, it takes weeks and months to get things done as opposed to hours and days, and truly allowed us to, we had to, you know, VJ things, move things. And, you know, we were able to do that in this environment with AWS support and the fact that we can kind of turn things off and on as quickly as we need it. >>Yeah. Cloud-scale is great for speed. So DECA, Gardez get your thoughts on this cloud first mission, you know, it, you know, the dev ops world, they saw this early that jumping in there, they saw the, the, the agility. Now the theme this year is modern applications with the COVID pandemic pressure, there's real business pressure to make that happen. How did you guys learn to get there fast? And what specifically did you guys do at Accenture and how did it all come together? Can you take us inside kind of how it played out? >>Oh, right. So yeah, we started off with, as we do in most cases with a much more bigger group, and we worked with lions functional experts and, uh, the lost knowledge that allowed the infrastructure being had. Um, we then applied our journey to cloud strategy, which basically revolves around the seminars and, and, uh, you know, the deep three steps from our perspective, uh, assessing the current environment, setting up the new cloud environment. And as we go modernizing and, and migrating these applications to the cloud now, you know, one of the key things that, uh, you know, we learned along this journey was that, you know, you can have the best plans, but bottom line that we were dealing with, we often than not have to make changes. Uh, what a lot of agility and also work with a lot of collaboration with the, uh, Lyon team, as well as, uh, uh, AWS. I think the key thing for me was being able to really bring it all together. It's not just, uh, you know, essentially mobilize it's all of us working together to make this happen. >>What were some of the learnings real quick journeys? >>So I think so the perspective of the key learnings that, you know, uh, you know, when you look back at, uh, the, the infrastructure that was that we were trying to migrate over to the cloud, a lot of the documentation, et cetera, was not available. We were having to, uh, figure out a lot of things on the fly. Now that really required us to have, uh, uh, people with deep expertise who could go into those environments and, and work out, uh, you know, the best ways to, to migrate the workloads to the cloud. Uh, I think, you know, the, the biggest thing for me was making sure all the had on that real SMEs across the board globally, that we could leverage across the various technologies, uh, uh, and, and, and, you know, that would really work in our collaborative and agile environment with line. >>Let's do what I got to ask you. How did you address your approach to the cloud and what was your experience? >>Yeah, for me, it's around getting the foundations right. To start with and then building on them. Um, so, you know, you've gotta have your, your, your process and you've got to have your, your kind of your infrastructure there and your blueprints ready. Um, AWS do a great job of that, right. Getting the foundations right. And then building upon it, and then, you know, partnering with Accenture allows you to do that very successfully. Um, I think, um, you know, the one thing that was probably surprising to us when we started down this journey and kind of after we got a long way down the track and looking backwards is actually how much you can just turn off. Right? So a lot of stuff that you, uh, you get left with a legacy in your environment, and when you start to work through it with the types of people that civic just mentioned, you know, the technical expertise working with the business, um, you can really rationalize your environment and, uh, you know, cloud is a good opportunity to do that, to drive that legacy out. >>Um, so you know, a few things there, the other thing is, um, you've got to try and figure out the benefits that you're going to get out of moving here. So there's no point just taking something that is not delivering a huge amount of value in the traditional world, moving it into the cloud, and guess what is going to deliver the same limited amount of value. So you've got to transform it, and you've got to make sure that you build it for the future and understand exactly what you're trying to gain out of it. So again, you need a strong collaboration. You need a good partners to work with, and you need good engagement from the business as well, because the kind of, uh, you know, digital transformation, cloud transformation, isn't really an it project, I guess, fundamentally it is at the core, but it's a business project that you've got to get the whole business aligned on. You've got to make sure that your investment streams are appropriate and that you're able to understand the benefits and the value that, so you're going to drive back towards the business. >>Let's do it. If you don't mind me asking, what was some of the obstacles you encountered or learnings, um, that might different from the expectation we all been there, Hey, you know, we're going to change the world. Here's the sales pitch, here's the outcome. And then obviously things happen, you know, you learn legacy, okay. Let's put some containerization around that cloud native, um, all that rational. You're talking about what are, and you're going to have obstacles. That's how you learn. That's how perfection has developed. How, what obstacles did you come up with and how are they different from your expectations going in? >>Yeah, they're probably no different from other people that have gone down the same journey. If I'm totally honest, the, you know, 70 or 80% of what you do is relatively easy of the known quantity. It's relatively modern architectures and infrastructures, and you can upgrade, migrate, move them into the cloud, whatever it is, rehost, replatform, rearchitect, whatever it is you want to do, it's the other stuff, right? It's the stuff that always gets left behind. And that's the challenge. It's, it's getting that last bit over the line and making sure that you haven't invested in the future while still carrying all of your legacy costs and complexity within your environment. So, um, to be quite honest, that's probably taken longer and has been more of a challenge than we thought it would be. Um, the other piece I touched on earlier on in terms of what was surprising was actually how much of, uh, your environment is actually not needed anymore. >>When you start to put a critical eye across it and understand, um, uh, ask the tough questions and start to understand exactly what, what it is you're trying to achieve. So if you ask a part of a business, do they still need this application or this service a hundred percent of the time, they will say yes until you start to lay out to them, okay, now I'm going to cost you this to migrate it or this, to run it in the future. And, you know, here's your ongoing costs and, you know, et cetera, et cetera. And then, uh, for a significant amount of those answers, you get a different response when you start to layer on the true value of it. So you start to flush out those hidden costs within the business, and you start to make some critical decisions as a company based on, uh, based on that. So that was a little tougher than we first thought and probably broader than we thought there was more of that than we anticipated, um, which actually results in a much cleaner environment post and post migration. >>You know, the old expression, if it moves automated, you know, it's kind of a joke on government, how they want to tax everything, you know, you want to automate, that's a key thing in cloud, and you've got to discover those opportunities to create value Stuart and Sadiq. Mainly if you can weigh in on this love to know the percentage of total cloud that you have now, versus when you started, because as you start to uncover whether it's by design for purpose, or you discover opportunities to innovate, like you guys have, I'm sure it kind of, you took on some territory inside Lyon, what percentage of cloud now versus stark? >>Yeah. At the start, it was minimal, right. You know, close to zero, right. Single and single digits. Right. It was mainly SAS environments that we had, uh, sitting in clouds when we, uh, when we started, um, Doug mentioned earlier on a really significant transformation project, um, that we've undertaken and recently gone live on a multi-year one. Um, you know, that's all stood up on AWS and is a significant portion of our environment, um, in terms of what we can move to cloud. Uh, we're probably at about 80 or 90% now. And the balanced bit is, um, legacy infrastructure that is just gonna retire as we go through the cycle rather than migrate to the cloud. Um, so we are significantly cloud-based and, uh, you know, we're reaping the benefits of it. I know you like 20, 20, I'm actually glad that you did all the hard yards in the previous years when you started that business challenges thrown out as, >>So do you any common reaction to the cloud percentage penetration? >>I mean, guys don't, but I was going to say was, I think it's like the 80 20 rule, right? We, we, we worked really hard in the, you know, I think 2018, 19 to get any person off, uh, after getting a loan, the cloud and, or the last year is the 20% that we have been migrating. And Stuart said like, uh, not that is also, that's going to be a good diet. And I think our next big step is going to be obviously, you know, the icing on the tape, which is to decommission all these apps as well. Right. So, you know, to get the real benefits out of, uh, the whole conservation program from a, uh, from a >>Douglas and Stewart, can you guys talk about the decision around the cloud because you guys have had success with AWS, why AWS how's that decision made? Can you guys give some insight into some of those thoughts? >>I can stop, start off. I think back when the decision was made and it was, it was a while back, um, you know, there's some clear advantages of moving relay, Ws, a lot of alignment with some of the significant projects and, uh, the trend, that particular one big transformation project that we've alluded to as well. Um, you know, we needed some, uh, some very robust and, um, just future proof and, um, proven technology. And they Ws gave that to us. We needed a lot of those blueprints to help us move down the path. We didn't want to reinvent everything. So, um, you know, having a lot of that legwork done for us and AWS gives you that, right. And, and particularly when you partner up with, uh, with a company like Accenture as well, you get combinations of the technology and the skills and the knowledge to, to move you forward in that direction. >>So, um, you know, for us, it was a, uh, uh, it was a decision based on, you know, best of breed, um, you know, looking forward and, and trying to predict the future needs and, and, and kind of the environmental that we might need. Um, and, you know, partnering up with organizations that can then take you on the journey. Yeah. And just to build on it. So obviously, you know, lion's like an AWS, but, you know, we knew it was a very good choice given that, um, uh, the skills and the capability that we had, as well as the assets and tools we had to get the most out of, um, AWS and obviously our, our CEO globally, you know, announcement about a huge investment that we're making in cloud. Um, but you know, we've, we've worked very well DWS, we've done some joint workshops and joint investments, um, some joint POC. So yeah, w we have a very good working relationship, AWS, and I think, um, one incident to reflect upon whether it's cyber it's and again, where we actually jointly, you know, dove in with, um, with Amazon and some of their security experts and our experts. And we're able to actually work through that with mine quite successfully. So, um, you know, really good behaviors as an organization, but also really good capabilities. >>Yeah. As you guys, you're essential cloud outcomes, research shown, it's the cycle of innovation with the cloud. That's creating a lot of benefits, knowing what you guys know now, looking back certainly COVID is impacted a lot of people kind of going through the same process, knowing what you guys know now, would you advocate people to jump on this transformation journey? If so, how, and what tweaks they make, which changes, what would you advise? >>Uh, I might take that one to start with. Um, I hate to think where we would have been when, uh, COVID kicked off here in Australia and, you know, we were all sent home, literally were at work on the Friday, and then over the weekend. And then Monday, we were told not to come back into the office and all of a sudden, um, our capacity in terms of remote access and I quadrupled, or more four, five X, uh, what we had on the Friday we needed on the Monday. And we were able to stand that up during the day Monday and into Tuesday, because we were cloud-based. And, uh, you know, we just found up your instances and, uh, you know, sort of our licensing, et cetera. And we had all of our people working remotely, um, within, uh, you know, effectively one business day. >>Um, I know peers of mine in other organizations and industries that are relying on kind of a traditional wise and getting hardware, et cetera, that were weeks and months before they could get their, the right hardware to be able to deliver to their user base. So, um, you know, one example where you're able to scale and, uh, uh, get, uh, get value out of this platform beyond probably what was anticipated at the time you talk about, um, you know, less the, in all of these kinds of things. And you can also think of a few scenarios, but real world ones where you're getting your business back up and running in that period of time is, is just phenomenal. There's other stuff, right? There's these programs that we've rolled out, you do your sizing, um, and in the traditional world, you would just go out and buy more servers than you need. >>And, you know, probably never realize the full value of those, you know, the capability of those servers over the life cycle of them. Whereas you're in a cloud world, you put in what you think is right. And if it's not right, you pump it up a little bit when, when all of your metrics and so on, tell you that you need to bump it up. And conversely you scale it down at the same rate. So for us, with the types of challenges and programs and, uh, uh, and just business need, that's come at as this year, uh, we wouldn't have been able to do it without a strong cloud base, uh, to, uh, to move forward >>Know Douglas. One of the things that I talked to, a lot of people on the right side of history who have been on the right wave with cloud, with the pandemic, and they're happy, they're like, and they're humble. Like, well, we're just lucky, you know, luck is preparation meets opportunity. And this is really about you guys getting in early and being prepared and readiness. This is kind of important as people realize, then you gotta be ready. I mean, it's not just, you don't get lucky by being in the right place, the right time. And there were a lot of companies were on the wrong side of history here who might get washed away. This is a super important, I think, >>To echo and kind of build on what Stewart said. I think that the reason that we've had success and I guess the momentum is we, we didn't just do it in isolation within it and technology. It was actually linked to broader business changes, you know, creating basically a digital platform for the entire business, moving the business, where are they going to be able to come back stronger after COVID, when they're actually set up for growth, um, and actually allows, you know, lying to achievements growth objectives, and also its ambitions as far as what it wants to do, uh, with growth in whatever they make, do with acquiring other companies and moving into different markets and launching new products. So we've actually done it in a way that is, you know, real and direct business benefit, uh, that actually enables line to grow >>General. I really appreciate you coming. I have one final question. If you can wrap up here, uh, Stuart and Douglas, you don't mind weighing in what's the priorities for the future. What's next for lion in a century >>Christmas holidays, I'll start Christmas holidays been a big deal and then a, and then a reset, obviously, right? So, um, you know, it's, it's figuring out, uh, transform what we've already transformed, if that makes sense. So God, a huge proportion of our services sitting in the cloud. Um, but we know we're not done even with the stuff that is in there. We need to take those next steps. We need more and more automation and orchestration. We need to, um, our environment, there's more future growth. We need to be able to work with the business and understand what's coming at them so that we can, um, you know, build that into, into our environment. So again, it's really transformation on top of transformation is the way that I'll describe it. And it's really an open book, right? Once you get it in and you've got the capabilities and the evolving tool sets that, uh, AWS continue to bring to the market, um, you know, working with the partners to, to figure out how we unlock that value, um, you know, drive our costs down efficiency, uh, all of those kind of, you know, standard metrics. >>Um, but you know, we're looking for the next things to transform and show value back out to our customer base, um, that, uh, that we continue to, you know, sell our products to and work with and understand how we can better meet their needs. Yeah, I think just to echo that, I think it's really leveraging this and then did you capability they have and getting the most out of that investment. And then I think it's also moving to, uh, and adopting more new ways of working as far as, you know, the speed of the business, um, is getting up the speed of the market is changing. So being able to launch and do things quickly and also, um, competitive and efficient operating costs, uh, now that they're in the cloud, right? So I think it's really leveraging the most out of the platform and then, you know, being efficient in launching things. So putting them with the business, >>Any word from you on your priorities by you see this year in folding, >>There's got to say like e-learning squares, right, for me around, you know, just journey. This is a journey to the cloud, right. >>And, uh, you know, as well, the sort of Saturday, it's getting all, you know, different parts of the organization along the journey business to it, to your, uh, product lenders, et cetera. Right. And it takes time. It is tough, but, uh, uh, you know, you got to get started on it. And, you know, once we, once we finish off, uh, it's the realization of the benefits now that, you know, looking forward, I think for, from Alliance perspective, it is, uh, you know, once we migrate all the workloads to the cloud, it is leveraging, uh, all staff, right. And as I think students said earlier, uh, with, uh, you know, the latest and greatest stuff that AWS is basically working to see how we can really, uh, achieve more better operational excellence, uh, from a, uh, from a cloud perspective. >>Well, Stewart, thanks for coming on with a and sharing your environment and what's going on and your journey you're on the right wave. Did the work you're in, it's all coming together with faster, congratulations for your success, and, uh, really appreciate Douglas with Steve for coming on as well from Accenture. Thank you for coming on. Thanks, John. Okay. Just the cubes coverage of executive summit at AWS reinvent. This is where all the thought leaders share their best practices, their journeys, and of course, special programming with Accenture and the cube. I'm Sean ferry, your host, thanks for watching from around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome everyone to the cube virtuals coverage of the Accenture executive summit. Part of AWS reinvent 2020. I'm your host Rebecca Knight. We are talking today about reinventing the energy data platform. We have two guests joining us. First. We have Johan Krebbers. He is the GM digital emerging technologies and VP of it. Innovation at shell. Thank you so much for coming on the show, Johan you're welcome. And next we have Liz Dennett. She is the lead solution architect for O S D U on AWS. Thank you so much Liz to be here. So I want to start our conversation by talking about OSD. You like so many great innovations. It started with a problem Johan. What was the problem you were trying to solve at shell? >>Yeah, the ethical back a couple of years, we started shoving 2017 where we had a meeting with the deg, the gas exploration in shell, and the main problem they had. Of course, they got lots of lots of data, but are unable to find the right data. They need to work from all over the place. And totally >>Went to real, probably tried to solve is how that person working exploration could find their proper date, not just a day, but also the date you really needed that we did probably talked about his summer 2017. And we said, okay, they don't maybe see this moving forward is to start pulling that data into a single data platform. And that, that was at the time that we called it as the, you, the subsurface data universe in there was about the shell name was so in, in January, 2018, we started a project with Amazon to start grating a co fricking that building, that Stu environment that subserve the universe, so that single data level to put all your exploration and Wells data into that single environment that was intent. And every cent, um, already in March of that same year, we said, well, from Michelle point of view, we will be far better off if we could make this an industry solution and not just a shelf sluice, because Shelby, Shelby, if you can make an industry solution where people are developing applications for it, it also is far better than for shell to say we haven't shell special solution because we don't make money out of how we start a day that we can make money out of it. >>We have access to the data, we can explore the data. So storing the data we should do as efficiently possibly can. So we monitor, we reach out to about eight or nine other large, uh, or I guess operators like the economics, like the tutorials, like the chefs of this world and say, Hey, we inshallah doing this. Do you want to join this effort? And to our surprise, they all said, yes. And then in September, 2018, we had our kickoff meeting with your open group where we said, we said, okay, if you want to work together with lots of other companies, we also need to look at okay, how, how we organize that. Or if you started working with lots of large companies, you need to have some legal framework around some framework around it. So that's why we went to the open group and say, okay, let's, let's form the old forum as we call it at the time. So it's September, 2080, where I did a Galleria in Houston, but the kickoff meeting for the OT four with about 10 members at the time. So there's just over two years ago, we started an exercise for me called ODU, uh, kicked it off. Uh, and so that's really them will be coming from and how we've got there. Also >>The origin story. Um, what, so what digging a little deeper there? What were some of the things you were trying to achieve with the OSU? >>Well, a couple of things we've tried to achieve with you, um, first is really separating data from applications for what is, what is the biggest problem we have in the subsurface space that the data and applications are all interlinked tied together. And if, if you have them and a new company coming along and say, I have this new application and is access to the data that is not possible because the data often interlinked with the application. So the first thing we did is really breaking the link between the application, the data out as those levels, the first thing we did, secondly, put all the data to a single data platform, take the silos out what was happening in the sub-service space and know they got all the data in what we call silos in small little islands out there. So what we're trying to do is first break the link to great, great. >>They put the data single day, the bathroom, and the third part, put a standard layer on top of that, it's an API layer on top to create a platform. So we could create an ecosystem out of companies to start a valving shop application on top of dev data platform across you might have a data platform, but you're only successful. If you have a rich ecosystem of people start developing applications on top of that. And then you can export the data like small companies, last company, university, you name it, we're getting after create an ecosystem out there. So the three things were as was first break, the link between application data, just break it and put data at the center and also make sure that data, this data structure would not be managed by one company. It would only be met. It will be managed the data structures by the ODI forum. Secondly, then put a data, a single data platform certainly then has an API layer on top and then create an ecosystem. Really go for people, say, please start developing applications because now you have access to the data or the data no longer linked to somebody whose application was all freely available, but an API layer that was, that was all September, 2018, more or less >>To hear a little bit. Can you talk a little bit about some of the imperatives from the AWS standpoint in terms of what you were trying to achieve with this? Yeah, absolutely. And this whole thing is Johann said started with a challenge that was really brought out at shell. The challenges that geoscientists spend up to 70% of their time looking for data. I'm a geologist I've spent more than 70% of my time trying to find data in these silos. And from there, instead of just figuring out how we could address that one problem, we worked together to really understand the root cause of these challenges and working backwards from that use case OSU and OSU on AWS has really enabled customers to create solutions that span, not just this in particular problem, but can really scale to be inclusive of the entire energy value chain and deliver value from these use cases to the energy industry and beyond. >>Thank you, Lee, >>Uh, Johann. So talk a little bit about Accenture's cloud first approach and how it has, uh, helped shell work faster and better with it. >>Well, of course, access a cloud first approach only works together. It's been an Amazon environment, AWS environment. So we really look at, uh, at, at Accenture and others up together helping shell in this space. Now the combination of the two is where we're really looking at, uh, where access of course can be increased knowledge student to that environment operates support knowledge to do an environment. And of course, Amazon will be doing that to this environment that underpinning their services, et cetera. So, uh, we would expect a combination, a lot of goods when we started rolling out and put in production, the old you are three and four because we are anus. Then when release feed comes to the market in Q1 next year of ODU, when he started going to Audi production inside shell, but as the first release, which is ready for prime time production across an enterprise will be released just before Christmas, last year when he's still in may of this year. But really three is the first release we want to use for full scale production deployment inside shell, and also all the operators around the world. And there is one Amazon, sorry, at that one. Um, extensive can play a role in the ongoing, in the, in deployment building up, but also support environment. >>So one of the other things that we talk a lot about here on the cube is sustainability. And this is a big imperative at so many organizations around the world in particular energy companies. How does this move to OSD you, uh, help organizations become, how is this a greener solution for companies? >>Well, first he make it's a greatest solution because you start making a much more efficient use of your resources. is already an important one. The second thing we're doing is also, we started with ODU in framers, in the oil and gas space in the expert development space. We've grown, uh, OTU in our strategy, we've grown. I was, you know, also do an alternative energy sociology. We'll all start supporting next year. Things like solar farms, wind farms, uh, the, the dermatomal environment hydration. So it becomes an and, and an open energy data platform, not just what I want to get into steep that's for new industry, any type of energy industry. So our focus is to create, bring the data of all those various energy data sources to get me to a single data platform you can to use AI and other technology on top of that, to exploit the data, to beat again into a single data platform. >>Liz, I want to ask you about security because security is, is, is such a big concern when it comes to data. How secure is the data on OSD? You, um, actually, can I talk, can I do a follow up on this sustainability talking? Oh, absolutely. By all means. I mean, I want to interject though security is absolutely our top priority. I don't mean to move away from that, but with sustainability, in addition to the benefits of the OSU data platform, when a company moves from on-prem to the cloud, they're also able to leverage the benefits of scale. Now, AWS is committed to running our business in the most environmentally friendly way possible. And our scale allows us to achieve higher resource utilization and energy efficiency than a typical data center. Now, a recent study by four 51 research found that AWS is infrastructure is 3.6 times more energy efficient than the median of surveyed enterprise data centers. Two thirds of that advantage is due to higher, um, server utilization and a more energy efficient server population. But when you factor in the carbon intensity of consumed electricity and renewable energy purchases for 51 found that AWS performs the same task with an 88% lower carbon footprint. Now that's just another way that AWS and OSU are working to support our customers is they seek to better understand their workflows and make their legacy businesses less carbon intensive. >>That's that's incorrect. Those are those statistics are incredible. Do you want to talk a little bit now about security? Absolutely. Security will always be AWS is top priority. In fact, AWS has been architected to be the most flexible and secure cloud computing environment available today. Our core infrastructure is built to satisfy. There are the security requirements for the military global banks and other high sensitivity organizations. And in fact, AWS uses the same secure hardware and software to build an operate each of our regions. So that customers benefit from the only commercial cloud that's hat hits service offerings and associated supply chain vetted and deemed secure enough for top secret workloads. That's backed by a deep set of cloud security tools with more than 200 security compliance and governmental service and key features as well as an ecosystem of partners like Accenture, that can really help our customers to make sure that their environments for their data meet and or exceed their security requirements. Johann, I want you to talk a little bit about how OSD you can be used today. Does it only handle subsurface data? >>Uh, today it's Honda's subserves or Wells data. We got to add to that production around the middle of next year. That means that the whole upstate business. So we've got goes from exploration all the way to production. You've made it together into a single data platform. So production will be added around Q3 of next year. Then a principal. We have a difficult, the elder data that single environment, and we want to extend it then to other data sources or energy sources like solar farms, wind farms, uh, hydrogen, hydro, et cetera. So we're going to add a whore, a whole list of audit day energy source to them and be all the data together into a single data club. So we move from an all in guest data platform to an entity data platform. That's really what our objective is because the whole industry, if you look it over, look at our competition or moving in that same two acts of quantity of course, are very strong in oil and gas, but also increased the, got into other energy sources like, like solar, like wind, like th like highly attended, et cetera. So we would be moving exactly what it's saying, method that, that, that, that the whole OSU can't really support at home. And as a spectrum of energy sources, >>Of course, and Liz and Johan. I want you to close this out here by just giving us a look into your crystal balls and talking about the five and 10 year plan for OSD. We'll start with you, Liz, what do you, what do you see as the future holding for this platform? Um, honestly, the incredibly cool thing about working at AWS is you never know where the innovation and the journey is going to take you. I personally am looking forward to work with our customers, wherever their OSU journeys, take them, whether it's enabling new energy solutions or continuing to expand, to support use cases throughout the energy value chain and beyond, but really looking forward to continuing to partner as we innovate to slay tomorrow's challenges, Johann first, nobody can look at any more nowadays, especially 10 years, but our objective is really in the next five years, you will become the key backbone for energy companies for store your data intelligence and optimize the whole supply energy supply chain, uh, in this world Johan Krebbers Liz Dennett. Thank you so much for coming on the cube virtual. Thank you. I'm Rebecca Knight stay tuned for more of our coverage of the Accenture executive summit >>From around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome everyone to the cubes coverage of the Accenture executive summit. Part of AWS reinvent. I'm your host Rebecca Knight today we're welcoming back to Cuba alum. We have Kishor Dirk. He is the Accenture senior managing director cloud first global services lead. Welcome back to the show Kishore. Thank you very much. Nice to meet again. And, uh, Tristan moral horse set. He is the managing director, Accenture cloud first North American growth. Welcome back to you to Tristin. Great to be back in grapes here again, Rebecca. Exactly. Even in this virtual format, it is good to see your faces. Um, today we're going to be talking about my NAB and green cloud advisor capability. Kishor I want to start with you. So my NAB is a platform that is really celebrating its first year in existence. Uh, November, 2019 is when Accenture introduced it. Uh, but it's, it has new relevance in light of this global pandemic that we are all enduring and suffering through. Tell us a little bit about the lineup platform, what it is that cloud platform to help our clients navigate the complexity of cloud and cloud decisions and to make it faster. And obviously, you know, we have in the cloud, uh, you know, with >>The increased relevance and all the, especially over the last few months with the impact of COVID crisis and exhibition of digital transformation, you know, we are seeing the transformation of the exhibition to cloud much faster. This platform that you're talking about has enabled hardened 40 clients globally across different industries. You identify the right cloud solution, navigate the complexity, provide a cloud specific solution simulate for our clients to meet that strategy business needs. And the clients are loving it. >>I want to go to you now trust and tell us a little bit about how my nav works and how it helps companies make good cloud choice. >>Yeah, so Rebecca, we we've talked about cloud is, is more than just infrastructure and that's what mine app tries to solve for it. It really looks at a variety of variables, including infrastructure operating model and fundamentally what clients' business outcomes, um, uh, our clients are, are looking for and, and identifies the optimal solution for what they need. And we assign this to accelerate. And we mentioned that the pandemic, one of the big focus now is to accelerate. And so we worked through a three-step process. The first is scanning and assessing our client's infrastructure, their data landscape, their application. Second, we use our automated artificial intelligence engine to interact with. We have a wide variety and library of, uh, collective plot expertise. And we look to recommend what is the enterprise architecture and solution. And then third, before we live with our clients, we look to simulate and test this scaled up model. And the simulation gives our clients a way to see what cloud is going to look like, feel like and how it's going to transform their business before they go there. >>Tell us a little bit about that in real life. Now as a company, so many of people are working remotely having to collaborate, uh, not in real life. How is that helping them right now? >>So, um, the, the pandemic has put a tremendous strain on systems, uh, because of the demand on those systems. And so we talk about resiliency. We also now need to collaborate across data across people. Um, I think all of us are calling from a variety of different places where our last year we were all at the VA cube itself. Um, and, and cloud technologies such as teams, zoom that we're we're leveraging now has fundamentally accelerated and clients are looking to onboard this for their capabilities. They're trying to accelerate their journey. They realize that now the cloud is what is going to become important for them to differentiate. Once we come out of the pandemic and the ability to collaborate with their employees, their partners, and their clients through these systems is becoming a true business differentiator for our clients. >>Keisha, I want to talk with you now about my navs multiple capabilities, um, and helping clients design and navigate their cloud journeys. Tell us a little bit about the green cloud advisor capability and its significance, particularly as so many companies are thinking more deeply and thoughtfully about sustainability. >>Yes. So since the launch of my NAB, we continue to enhance capabilities for our clients. One of the significant, uh, capabilities that we have enabled is the being or advisor today. You know, Rebecca, a lot of the businesses are more environmentally aware and are expanding efforts to decrease power consumption, uh, and obviously carbon emissions and, uh, and run a sustainable operations across every aspect of the enterprise. Uh, as a result, you're seeing an increasing trend in adoption of energy, efficient infrastructure in the global market. And one of the things that we did, a lot of research we found out is that there's an ability to influence our client's carbon footprint through a better cloud solution. And that's what we internalize, uh, brings to us, uh, in, in terms of a lot of the client connotation that you're seeing in Europe, North America and others. Lot of our clients are accelerating to a green cloud strategy to unlock greater financial societal and environmental benefit, uh, through obviously cloud-based circular, operational, sustainable products and services. That is something that we are enhancing my now, and we are having active client discussions at this point of time. >>So Tristan, tell us a little bit about how this capability helps clients make greener decisions. >>Yeah. Um, well, let's start about the investments from the cloud providers in renewable and sustainable energy. Um, they have most of the hyperscalers today, um, have been investing significantly on data centers that are run on renewable energy, some incredibly creative constructs on the, how, how to do that. And sustainability is there for a key, um, key item of importance for the hyperscalers and also for our clients who now are looking for sustainable energy. And it turns out this marriage is now possible. I can, we marry the, the green capabilities of the cloud providers with a sustainability agenda of our clients. And so what we look into the way the mind works is it looks at industry benchmarks and evaluates our current clients, um, capabilities and carpet footprint leveraging their existing data centers. We then look to model from an end-to-end perspective, how the, their journey to the cloud leveraging sustainable and, um, and data centers with renewable energy. We look at how their solution will look like and, and quantify carbon tax credits, um, improve a green index score and provide quantifiable, um, green cloud capabilities and measurable outcomes to our clients, shareholders, stakeholders, clients, and customers. Um, and our green plot advisers sustainability solutions already been implemented at three clients. And in many cases in two cases has helped them reduce the carbon footprint by up to 400% through migration from their existing data center to green cloud. Very, very, >>That is remarkable. Now tell us a little bit about the kinds of clients. Is this, is this more interesting to clients in Europe? Would you say that it's catching on in the United States? Where, what is the breakdown that you're seeing right now? >>Sustainability is becoming such a global agenda and we're seeing our clients, um, uh, tie this and put this at board level, um, uh, agenda and requirements across the globe. Um, Europe has specific constraints around data sovereignty, right, where they need their data in country, but from a green, a sustainability agenda, we see clients across all our markets, North America, Europe in our growth markets adopt this. And we have seen case studies and all three months, >>Kesha. I want to bring you back into the conversation. Talk a little bit about how MindUP ties into Accenture's cloud first strategy, your Accenture's CEO, Julie Sweet, um, has talked about post COVID leadership, requiring every business to become a cloud first business. Tell us a little bit about how this ethos is in Accenture and how you're sort of looking outward with it too. >>So Rebecca mine is the launch pad, uh, to a cloud first transformation for our clients. Uh, Accenture, see your jewelry suite, uh, shared the Accenture cloud first and our substantial investment demonstrate our commitment and is delivering greater value for our clients when they need it the most. And with the digital transformation requiring cloud at scale, you know, we're seeing that in the post COVID leadership, it requires that every business should become a cloud business. And my nap helps them get there by evaluating the cloud landscape, navigating the complexity, modeling architecting and simulating an optimal cloud solution for our clients. And as Justin was sharing a greener cloud. >>So Tristan, talk a little bit more about some of the real life use cases in terms of what are we, what are clients seeing? What are the results that they're having? >>Yes. Thank you, Rebecca. I would say two key things right around my notes. The first is the iterative process. Clients don't want to wait, um, until they get started, they want to get started and see what their journey is going to look like. And the second is fundamental acceleration, dependent make, as we talked about, has accelerated the need to move to cloud very quickly. And my nav is there to do that. So how do we do that? First is generating the business cases. Clients need to know in many cases that they have a business case by business case, we talk about the financial benefits, as well as the business outcomes, the green, green clot impact sustainability impacts with minus. We can build initial recommendations using a basic understanding of their environment and benchmarks in weeks versus months with indicative value savings in the millions of dollars arranges. >>So for example, very recently, we worked with a global oil and gas company, and in only two weeks, we're able to provide an indicative savings where $27 million over five years, this enabled the client to get started, knowing that there is a business case benefit and then iterate on it. And this iteration is, I would say the second point that is particularly important with my nav that we've seen in bank of clients, which is, um, any journey starts with an understanding of what is the application landscape and what are we trying to do with those, these initial assessments that used to take six to eight weeks are now taking anywhere from two to four weeks. So we're seeing a 40 to 50% reduction in the initial assessment, which gets clients started in their journey. And then finally we've had discussions with all of the hyperscalers to help partner with Accenture and leverage mine after prepared their detailed business case module as they're going to clients. And as they're accelerating the client's journey, so real results, real acceleration. And is there a journey? Do I have a business case and furthermore accelerating the journey once we are by giving the ability to work in iterative approach. >>I mean, it sounds as though that the company that clients and and employees are sort of saying, this is an amazing time savings look at what I can do here in, in so much in a condensed amount of time, but in terms of getting everyone on board, one of the things we talked about last time we met, uh, Tristin was just how much, uh, how one of the obstacles is getting people to sign on and the new technologies and new platforms. Those are often the obstacles and struggles that companies face. Have you found that at all? Or what is sort of the feedback that you're getting? >>Yeah, sorry. Yes. We clearly, there are always obstacles to a cloud journey. If there were an obstacles, all our clients would be, uh, already fully in the cloud. What man I gives the ability is to navigate through those, to start quickly. And then as we identify obstacles, we can simulate what things are going to look like. We can continue with certain parts of the journey while we deal with that obstacle. And it's a fundamental accelerator. Whereas in the past one, obstacle would prevent a class from starting. We can now start to address the obstacles one at a time while continuing and accelerating the contrary. That is the fundamental difference. >>Kishor I want to give you the final word here. Tell us a little bit about what is next for Accenture might have and what we'll be discussing next year at the Accenture executive summit, >>Rebecca, we are continuously evolving with our client needs and reinventing reinventing for the future. Well, mine has been toward advisor. Our plan is to help our clients reduce carbon footprint and again, migrate to a green cloud. Uh, and additionally, we're looking at, you know, two capabilities, uh, which include sovereign cloud advisor, uh, with clients, especially in, in Europe and others are under pressure to meet, uh, stringent data norms that Kristen was talking about. And the sovereign cloud advisor helps organization to create an architecture cloud architecture that complies with the green. Uh, I would say the data sovereignty norms that is out there. The other element is around data to cloud. We are seeing massive migration, uh, for, uh, for a lot of the data to cloud. And there's a lot of migration hurdles that come within that. Uh, we have expanded mine app to support assessment capabilities, uh, for, uh, assessing applications, infrastructure, but also covering the entire state, including data and the code level to determine the right cloud solution. So we are, we are pushing the boundaries on what mine app can do with mine. Have you created the ability to take the guesswork out of cloud, navigate the complexity? We are rolling risks costs, and we are, you know, achieving client's static business objectives while building a sustainable alerts with being cloud, >>Any platform that can take some of the guesswork out of the future. I am I'm on board with thank you so much, Tristin and Kishore. This has been a great conversation. Stay tuned for more of the cubes coverage of the Accenture executive summit. I'm Rebecca Knight.

>> From theCube studios in Paloalto and Boston, connecting with thought leaders all around the world, this is a Cube conversation. >> Hi, I'm Stu Miniman, and welcome to this special Cube conversation. I'm coming to you from our Boston area studio, and theCube is really mostly about people, about network, and so we're going to have a focus in, we're going to talk about some technology, we're also going to talk a little bit about careers. I want to welcome to the program, I've got two first-time guests on the program. First, Mark Zbikowski. Probably butchered that badly, Mark, sorry, technical advisor, and Blue Gaston. Uh, Gaston. Boy, I'm doing horrible with names here. Software engineer, you're both with Polyverse. But, you know, my last name's Miniman, it has been butchered a million times. But Mark, and Blue, thank you so much for joining us. >> You're welcome. Our pleasure. >> Yes. >> All right. So one of you I've read a lot about online and the other one is Mark, go to the Wikipedia page, stuff like that. So we'll get to that too. So, Blue, maybe start with you, give us a little bit about your background. >> Yeah, so I work at Polyverse now, a cybersecurity startup. But actually I got my undergraduate degree in Philosophy, and from there, kind of just like, what am I going to do with a philosophy degree? And it just weirdly was like a natural transition. I was like, oh, computer science. And kind of the logical, like the technical version of philosophy. So got my master's in philosophy and now, or not philosophy, in computer science, and now have been working at Polyverse. I started as an intern and they hired me on, I think after a month, they were like, no, we want you full-time. So that was cool and I've loved it. So I'm starting off my story, that's kind of where my kick-off point is. >> Awesome. So, and Mark, first of all, you have to give us the connection between yourself and Blue, and a little bit surprising that she waited so long to go into the computer business. >> Uh, okay, I'm her stepfather. It's not surprising that she, you know, wanted to go into computer science. She's got lots of aptitude for it. She was just on a career path and an education path that was primarily logic, analysis, which is basically what we do in computer science. >> All right. So Mark, if you could just give our audience a little bit of a thumbnail sketch as to your background in the tech industry, and it's a storied one. >> Uh, okay. I was, I think, employee number 55 at Microsoft, when I started back in 1981. The first task that they gave me was to work on something that ended up becoming MS-DOS. I worked on MS-DOS for a long time, about five and a half years, worked on a number of other operating systems at Microsoft, ending up with being one of the initial development managers and architects for Windows. I was responsible for all file storage. And I was there for about 26 years. >> Yeah, you know, interesting, you know, when you look on the Wikipedia page, you were the third employee that reached the 25-year milestone. Some guy, Bill Gates, and Steve Balmer, were the first two to reach that milestone. So, you know, quite impressive. I think back, back when I learned computers, it was programming, and you know, today it's coding, and things are quite different there. But, Mark, you were also, you're noted as one of the early hackers there, so what does that mean to you, how have you seen that's been changing? Polyverse is in the cybersecurity realm, so would love your kind of viewpoint on just hacking in general. >> Oh, the early days, well my hacking started pretty much when I was in eighth or ninth grade back in Detroit. We had access to an academic operating system called MTS by way of Wayne State University. I grew up in, just in the suburbs of Detroit. And we had access to it, and for me Excuse me. Hacking at the time was all about trying to understand and learn stuff that was arcane and hidden and mysterious. Figuring out how, for example, password encryption algorithms worked, figuring out how operating systems worked, because at the time, there were very few organized textbooks about how to construct operating systems. Even though operating systems had been around for 20 years. So my early, earliest stuff was in basically, finding holes in security at MTS, and that's how I started, in what they would say "hacking", but it was very innocent, it was very, let's see what we can do! As opposed to, let's extract information, let's go and ransom people's data for bitcoin, which is, you know, I think, a wrong direction to go. >> Yeah. I'm curious your thoughts as the decades have progressed, you know, hacking today, what's your take on, you know, there's the white hats and the black hats, and everything in between. >> Uh, it's kind of an arms race. (laughs) Everything that the white hats will throw up, the black hats will eventually attack to some degree. Social engineering is sort of the ultimate way that people have been getting around, you know, software protections. I think it's unfortunate that there is such a financial reward to the black hat side of things, as counter to one's ethics. I think there's a lot of slippery slopes involved, in terms of, you know, boy, these companies shouldn't be making money, so I deserve my bit. I think that it's much better that, you know, people should come at this from an intellectual, you know, exploration standpoint, rather than an exploitative. But that's the nature of the world. >> Yeah, well, Blue, maybe we can help connect the dots towards what you both do at Polyverse. You mentioned you started as an intern, and I loved the article that talked about this. Well, you know, you're going to be an intern. Can you fix the internet for us? And you did some things to help, you know, help stop some of that malicious hacking. >> Yeah, I, that was crazy. I was very intimidated when I heard that, you're going to be fixing the internet. What I've been working at the company, which is different from our flagship product, but kind of in the same vein, is to stop malicious php javascript code execution. So that's what they came in, that's how they prefaced that problem to me. It was, you're going to go fix the internet. Um, and it was crazy. It was really cool and surprisingly, a lot of philosophy that goes into the way we look at our problem-solving at Polyverse, and how we tackle problems, but of course, I have my Jedi master Mark over here, and I was constantly, "What do you think about this? Isn't this crazy? "Like, look at how Polyverse is attacking this." And I think finally I broke him down, and I was like, come join. Come jump in, and you be the foresight, and you tell us what we're going to do in a year or two. And I convinced him, and now, he's, he's with us too. >> Excellent. So, Mark, tell us a little bit about, you know, more about Polyverse, your role there. In the industry there's a lot of talk about, you know, lots of money obviously gets spent on cybersecurity, but it's still a major challenge in the industry. So what's your role there and how's Polyverse helping to attack that? >> Well, my title is Technology Advisor, and I'm one of a small collection of people who have pretty wide-ranging expertise across operating systems, networks, compilers, languages, development tools, all of that. And our goal is, you know, my role, as well the other Jedi masters, is to take a look at what Polyverse is doing at present, try to figure out where we need to go, try to figure out what the next set of challenges are, use our broad experience and knowledge of the computing milieu, and try to figure out what are the tough issues we need to face? We make some progress on those tough issues, and then turn everything over for the mainline Polyverse development staff to bring it to reality. We're not like researchers, we're much more into the product planning side of things, but product planning in, I hate to use this word, but in a visionary sense. (Blue laughs) >> Yeah, no, it's-- >> We look for the vision. We're not visionaries. We look for the vision. >> You're a visionary, Mark. Admit it. >> Excellent. Well, I do love the, you know, Jedi analogy there. When you look at, I'm curious to your thoughts, both of you, you know, some of the real challenges and opportunities facing the cybersecurity industry. It's a large financial industry company, they'll spend a billion dollars and, you know, does that make them secure? Well, at least they've done what they can and they're pushing enough pieces. But, you know, fundamentally, we understand that this is such a huge issue. >> I think-- >> Blue? >> Well, (laughs) I can try to answer. I think Polyverse recognizes that as well. So we're trying to create new solutions, that instead of just being compliant and checking the boxes, we're actually trying to create systems and products that will stop attacks from actually working. Rather than being reactive and being responsive, we're trying to build these systems out where the attacks just don't work as they're currently designed. And I think we, you know, and to do so in an easy-to-deploy, time-saving kind of way is definitely our goal. Rather than the status quo and, you know, we're fighting inertia, we're trying to, to change that narrative in a really meaningful way. >> Thanks, Blue. Mark, do you have some comments you can add to that? >> Once we started taking individual computers and hooking them up to the internet, where they can communicate fairly freely with each other, and by intent communicate fairly freely with each other, by design, by intent, all of a sudden that opened us to just a wide range of malicious behavior, from being DoS'd, to leaking passwords, et cetera. There are, there's layers and layers that one can do to mitigate these problems. From IT operational manuals to buzz-testing your API, to best practices, it's a, there's a long list. And every bit, every piece of it is important. You need to secure your passwords before you can do anything else. You need to make sure that there's a firewall in your system be fore you go and start, before you even start thinking about doing things like, like what's goin on with what we're doing at Polyverse. It's a, like I said, there's a wide range of tools that people need, that people use, that people spend money on today. Polyverse has got a very unique perspective on how to go and extend this. We, it's a, it's very pragmatic, you know, the realization is that these attackers are going to keep attacking, and they're going to exploit certain features that, despite everyone's best intentions, aren't covered, and we have found a rather unique and novel way to prevent people from doing it. Is it going to solve everything? No. There's still, there's all these other early layers that need to be taken care of first, before the more sophisticated tools that, for example, that Polyverse has or that other companies have. >> Great. Well, Blue, you talked a little bit about it, but, you know, love your, what you've found, you know, working together as a family dynamic here. You know, specifically. >> Um, (laughs) I think it's really cool. What's the best, I'll say this, is when, I always like asking Mark his opinion, because why wouldn't I? The brain that guy has, and just the experience, he can add so much. Every once in a while, I'll go, and I'll say, you know, oh, this is what I'm working on, and here's what I'm kind of thinking, and he'll say, oh, yeah, well what about this? And I'll actually get to explain something to him. And I got to tell you, that feels really good. Is when I get to say, oh, well, actually it looks like this, and this was my plan, and he's like, oh yeah, definitely. And I get that validation, which is really cool. And I can, you know, drive to his house and bug him whenever I want to. I know where he lives, so if I'm really stuck, or just want to bounce ideas off of him, it's really cool. It's really cool, and I, you know, strong-armed, not strong-armed, I enticed him to come and join Polyverse just by the cool things that we're doing, and I think that's cool too. To now be able to work on something together. >> Yeah, and Mark, sounds like you're learning some things from Blue. Give us your side of that relationship. >> Well, it's a great relationship. Blue, um, Blue never hesitates to challenge. (Blue laughs) >> Blue: Okay. And that, I'm saying that in a very positive sense. Um, you know, she'll come up, every so often I'll get a text from her that says, "Help!" >> Oh my god! (laughing) >> Yes. Sorry. At least I'm not showing it. (laughs) But it's great. And we get together and we talk about stuff, and she says, you know, here's the problem I'm facing, and I'll ask her about it and she gets to go and teach me about what her problem is. I'm a big fan of teaching. I think one of the frustrations that Blue has is I almost never give her the answer when she asks a question. (laughs) >> Not even when I was in school, >> Yeah, not even when you were in school. I was always asking the questions and leading her to the answer rather than just giving it to her. >> Or saying, well why don't we sit down and I'll teach you how to implement knowledge. Just like, oh my god. What are you doing? >> Yeah. So, yeah, I'm a big fan of teaching and learning by way of teaching. One of the things I do is I'm an affiliate with the University of Washington, and I teach every year one quarter of their Operating Systems class. And I love teaching, I love seeing the light go on. But every year, when I'm teaching a class that I know pretty well, I learn something new. By a question the student asks, or by reading a paper that I'm asking the students to read, I learn something new just about every year. And so having Blue teach me is a way that I get to learn, but I think in the process Blue also gets to learn as well. You know, in the process of teaching me. >> Yeah, well, that's such a great point. All right, want to give you both the final word on what's exciting you, what draws you to working in the cybersecurity industry. >> Um, I'll start. (laughs) So when I started at Polyverse, I actually got to, as an intern, own my own product. And in, I think, less than a month now, we're actually officially releasing that product, polyscripting. Officially, like Marketing is coming up with materials for it, and that was right out of school is when I started on this project, so it's kind of like a big deal for me. You know, I've owned the project, I'd say like 90% of it, over the last year or two, and now I get to see it come into fruition. So that's really exciting to me. Um, you know, that's exciting. So I'm excited about that, I'm excited about what Polyverse is doing in general. So, yeah. >> And Mark? >> Yeah. It's great working in a startup, it's great working with a bunch of very, very bright, energetic people. For me, contributing to that environment is extremely valuable. Helping Polyverse out, they're, you know, cybersecurity is problem. Trying to come up with good, effective solutions that are really pragmatic in terms of, you know, we're not going to solve every problem, but here's a great little space that we're going to solve all the problems in. That's, there's a huge appeal to that for me. >> Well, Mark and Blue, thank you so much for joining. Appreciate you sharing some of the personal as well as the professional journeys that you've both been on. Thanks so much. >> Yeah, thank you >> Yeah, you're welcome. >> All right. Thank you for watching theCube. I'm Stu Miniman. Thanks for watching. (soothing music)

>> Announcer: From theCUBE studios in Palo Alto and Boston, connecting with thought leaders all around the world, this is a CUBE Conversation. >> Hey, welcome back everybody, Jeff Frick here with theCUBE, we're in our Palo Alto studio today, the COVID thing is continuing to go, and one of the huge impacts, right, is obviously in the conference business, our world. Those things have all been canceled or made virtual, and everyone's still trying to figure out, what does a virtual event look like, what are the characteristics of it, and we're really excited to have one of our favorite CUBE alumni, guest host extraordinaire, Keith Townsend. You know him as the CTO advisor joining us, Keith jumped in with both feet, right when this thing went down, and said "I'm going to have my own CTO Advisor "virtual conference," so first off, Keith, I miss you, great to see you, we haven't run into each other at the Sands in an awfully long time, so great to see you, how are you doing? >> Good to see you, if it's only virtual, good to see you too, Jeff. >> So tell us about your decision to jump in with both feet, and go ahead and test the waters on this virtual conference concept. >> So I talked about this a little bit on a random, just a YouTube update, but roughly 30, 35% of my revenue comes from in-person events. And plus my brand, The CTO Advisor, is tied to people seeing me on theCUBE, seeing me at the shows, creating the content, kind of on the ground, guerrilla style, kind of like how John started out early on. So we needed a practical solution for most things, one, we feed off the energy of the community, so we need to be on the ground as much as possible, so that we can create content and get you guys the stories and the data that you need to make purchasing decisions, and two, we needed the practical problem of solving our own revenue problems, so we jumped in, head in, to say "Let's do a virtual event." I don't know if I would've done it if I wasn't as naive as I was back then, but we jumped in. >> So before we jump into the processes, make sure, give us a full-on plug, when is it, where should people go, registration I assume is still open, want to just get that out there for the folks. >> So even if you see this after registration closes, quote unquote closes, it's April 21st, >> 10: 30 AM central to 3:30 PM central, that's US time. You can register at CTOAdvisorVirtualConference.com. >> Excellent, so let's talk about some of the interesting things about virtual. One of the things as you said in a physical event, you've got people, you've got time and space and geography that we all come together in that space, and there's a lot of advantages to everybody being at the same place at the same time. A virtual event, almost by definition, is now you've broken up the segments of content capture, if you will, and creation, which can or cannot be on that date. The actual display, or the publishing of that content, if you will, and then the consumption of that content, which may or may not happen on the 21st. How have you worked with this expanded palette, if you will, to be able to work in an asynchronous world, and how are you finding it in terms of actually day to day execution? >> So you guys have done plenty of remote content at this point. When you're in theCUBE studio, you have commercial internet, it's fairly reliable when you're on premises, maybe a little bit less reliable from the sense that it's conference-centered, but it's still enterprise class internet access, so you can do real-time video on theCUBE fine. We can go to Cube.tv, Cube.net, and see what you guys are doing real-time, and it's pretty much without blip. In the virtual conference world, what we're dealing with where I'm coming in, remote to you, while my video and audio looks fine now, it may blip. So we embrace two things. We embrace the fact that this is a virtual event, so in a background, you'll see that we're in Keith Townsend's basement, the other thing that you'll see is that we won't produce live content, because there's not much value in it being live, if I can't interact with you. One of the great things about theCUBE, is that it's live, but there's this element that people are on the ground, they're watching it live, they're interacting with it live, we're tweeting about it, so how do you reproduce, if not that exact feeling of it being live and you're being part of it, but the conversation around the content, and that's what we focused on, creating high quality video content, that you can consume, kind of as a watch party, so on Twitter, in the platform that we're using, we're having conversations real-time, so that you can enjoy the community, and the speakers who are presenting, you can interact with them because they're not presenting real-time, they're in the chat room, they're on Twitter, they're running as their session is running, and they're able to interact with you, so we've embraced the medium, and then after the fact of course we can do all kinds of things to run asynchronous content after the fact, 'cause the majority of people will watch it after the video's done. >> All right, and I'm just curious, how many sessions are you going to have, approximately? >> So we have I think 21 sessions, in a five hour period, so we're running three separate tracks, two super techy, geeky tracks, then a sponsored track is kind of by itself, and we're not expecting everyone to consume it all at one time. >> Right, you know it's just so interesting to me, talking about your tracks. If you were to go rent a venue, that had the capacity to run 21 tracks over five hours, it'd be a pretty decent-sized venue, it'd be expensive, and then you would have to pick your sessions and your tracks based on the limitations of the budget that you had and the window that you had of rooms that you could put these people in, and who could do it now, when, there, the other thing, and so it's really interesting that now this opens up the amount of sessions, is really a function of what you can manage, or what the community can kind of self-organize, you're not really limited by how many rooms are in the Sands Convention Center, and the other thing that you brought up, which I think people completely miss is that if the content is recorded in advance and puts in the can, to your point, the presenter can actually participate in the conversation while the session is happening, which they can't do in a physical event, because they're actually presenting, so, we had a guy in the other day, Ben Nelson, he talked about a car is not a mechanical horse, it's not the same, digital's not the same as physical, and there are some things that aren't as cool, but there's a whole lot of things that you can do in the digital space that you can't do in the physical space. >> Yeah, a lot of my presenters were kind of put off by the idea of, "Wait, hold on, I'm not going to present live? "How will I interact with webinars now?" And I think this is the other end of the spectrum, Jeff, I think you guys have probably found this too, it's not a in-person event, and it's also not a webinar, so don't treat it as a webinar. You don't have to have these canned, phony questions that some people have behind the scenes, it is a real, authentic thing. Oddly enough, I discovered this as part of helping my church put on their worship service. I was watching the service, I'll look off the screen a little bit to the left, I was watching the service, and the minister's delivering his sermon, and in the Zoom meeting, there he is, playing with his little two year old daughter, while he's giving the talk, and I just opened chat at him, and next thing I know there's an explosion of conversation around just life and the topic at hand, so it is a really unique experience. >> Yeah, I think that's a really important point, it's not only what is a digital event, but what is it not, and it can't be a webinar, and when we were first going through this kind of shake-up, and we were really trying to identify some of those things, and we specifically did not want a digital event to be a webinar, 'cause what's a webinar, it's generally a one way communication of information for the vast majority of the session that you're sitting there, and they only open it up to Q&A at the very end, and it's only a moderated Q&A that very few people get a chance to get their question in, and you don't know how they're picking, and it only goes to the hosts, so, really having an open, live engagement around an engaged group of people, with a piece of content as kind of the coalescing of those people, really, it's not a webinar, it's a very different kind of experience, and sounds like you're really embracing that. >> Yeah, it'll never replace a live event, live has, again we talked about the energy, the, people are like "Do you really "want to smell the Sands, Keith?" You know what, it's all part of the energy, it's instant reminders to "Oh, I remember when I interviewed Pat Gelsinger here," and you have these instant cues that we as humans love, we don't get that, but I think it is something that's going to be with us to stay and it'll augment, I'd love to hear how you guys are thinking about how being able to have this capability will augment theCUBE once we return to physical events. >> Yeah, I mean I think this behavior that we're now been forced to engage in, in terms of increased working from home, and kind of increased use of videoconferencing, and that is a different communication mode, I think those behaviors are going to stick quite a bit, actually, I think if you look at what a conference is, there's a couple different tracks, as you said, there's the expression going around, kind of the rally moment, right, the keynote, we want, we have a strong message, the CEO wants to get something out, and I think that's of tremendous value, but then you look at all the breakout sessions and the information flow and the community engagement, those quite frankly can be done online much more efficiently and with much less cost, so will the new conference be kind of this, the celebration and basically a customer appreciation event, they want to have a party, but really that, I don't think it will be quite the information flow, 'cause why should product group A wait until the conference date, if they're ready to release their information, and wait for product group B or C or D, so this kind of forced aggregation of the communication into this very small window of three days in Vegas, I don't think it makes any sense, you know, it's Waterfall versus DevOps, and if this group's got stuff and they're ready to go, again, why hold the information back, it really doesn't make sense, and decouple the customer celebration, the rally moment, if you will, and the education, they don't necessarily have to be this contiguous big unit for three days in Vegas. >> Yeah, I'm looking forward to first quarter 2021, usually January, February, first half of March, really slow news channel product teams release stuff and they really want some big stage to release it, I think this will really make the dissemination of information coming from product teams super interesting as folks like theCUBE, The CTO Advisor, we're able to put on independent events virtually that have a sense of gravitas to it, that our partners will come and embrace. >> Yeah, the other thing, Keith, and I wonder, as you've been collecting your content for your show next week is that, the pressure on the quality of the content has escalated dramatically, right? If you're stuck in a huge conference hall, surrounded by 10,000 people, in the middle of a keynote that's not that exciting, it's kind of hard to get up and walk out. But if you're sitting at your desk with the entire world an alt-tab away, not to mention pesky things like email and Slack and everything else that we have as a distraction, it's really going to come in on the content provider and the engaged community to deliver, or else you're going to lose the audience, and I think it's going to be really interesting, people that overly have relied on the 100 foot video screen and the electronic violin music in the morning, and some of these tips and tricks, aren't going to carry the weight, because if it's just you sitting in front of a screen and you got to deliver the message, it's got to be crisp, it's got to be powerful, and it's got to be engaging, or people are just going to step away. >> And more importantly, how do you bring people back? So, you know how, when I take a break at a conference, I'm kind of captured. Eventually I'm going to walk back to the conference center, I might go back out to take a call, et cetera, but getting people to come back, even if the content has been awesome and engaging and great, how do you get 'em to come back, they don't have to come back that day, or even real time, but they have to come back to the portal, so we're working on kind of the next 30 days after the event, this is the thing that's really funny about putting on a virtual event, there's kind of the exhale after the day of the event, a virtual event, you know what, you've got a third of your audience that first day, a third of the audience the next week, and then the rest of the audience creeps in over the next three or four weeks, and how do you engage them, how do you get them to come back, and ultimately consume your content and your message? It's something that I haven't, I don't know if I've cracked the formula for it yet, but it is going to be a very interesting challenge. >> Yeah, but I think we have, right, in the way, how do you consume video today, how do you find information, right, you go to YouTube or to Google and you search, right, and right now the biggest phenom in pop media is the Tiger King, right, so when do people watch the Tiger King, how do they hear about the Tiger King, when do they actually sit down and watch it, has nothing to do with when you watch it unless we decide to trade messages, I say "Hey, Keith, have you seen the new episode?" So when you look at consumption patterns, to me it's really interesting, it's kind of bifurcated, you either binge watch, and just really get into something that you're into, and you just go go go for hours and hours and hours, or you're getting snippets, you're getting little quick hits, quick hits, quick hits, and I think it's this kind of ugly middle, where you don't have enough content or richness or engagement to have people hang, but you're a little bit longer than a quick hit just to get your message out, and I think it's really going to kind of bifurcate, and the beauty of digital is you can consume it in lots of different ways, and piece parts, and you don't have to necessarily kind of sit through kind of a straight row consumption as a captive audience, I think the opportunity's really really good, if the content is up to snuff, properly tagged, search terms, all those types of things of course as well. >> So yeah, John talks about the value of community a lot, and one of our co-hosts on theCUBE, and also a CUBE alum is Corey Quinn, and he does a really great job of this with curating content after it's been consumed live. He'll to his audience say "You know what, I'm going to live tweet this session "from three months ago," and that refreshes the conversation, it's not about when the content was created, it's about the conversation, as long as it's relevant, and finding mediums to help amplify that message. >> Yeah, I think it's just a great opportunity, you know, we used to do some work with Live Nation in another lifetime, right, and Live Nation around concerts, they had that particular event when you go to the show, and a lot of their efforts on the marketing side were what they call extending the glow, right, extending the glow after, and also kind of building the excitement before, and moving that window of that event to more than just the night that the show played, and I think we've got the same opportunity here, that's why again if you get good quality content, it's not speeds and feeds, but it's evergreen themes that have legs, you can go back to that well and you can stir that thing up, and you can get it back out there again, and then again hopefully people stumble upon it, whether it's via community or whatever. The other thing I think that's really interesting is you talked about community, and you talked about QuinnyPig, @QuinnyPig I think is his Twitter handle, is this whole idea of collaboration, and I think that's another thing that we can take from the internet, I know you do a lot of that, so working with other influencers if you will, or other people in the communities, and introducing each other's community to one another, I think it's a really big part of what makes a lot of the big YouTubers famous is that they do things together and they kind of cross-pollinate their communities, and if there's some overlap there then they both have kind of a win-win, and again I think in digital, where you don't have destruction, you don't have single use, you can use stuff more than once, it really opens up this opportunity for much more win-win, let's work together, and build community together, cross leverage, versus it's either yours or mine, and it's really more of a competitive thing. >> And I've been collaborating a lot with some of my European peers, and you bring up a really interesting concept. Our friends at VMware's going to be putting on VMworld in the next few months, and they usually had a US conference and a European conference, were both pretty sizable conferences. It's basically going to run concurrently as one conference. So if it's going to run as one conference, why do I have to limit the live experience to the US timezone? Why can't I cater this, and why is it just a fixed hour, I don't know if it will be, but it shouldn't just be a fixed hour event, it's going to be a all-out hour event that's going to happen across Asia, Europe, and the US, and tailoring the content to each continent and time zone, and cross-pollinating, so that content that I would not have typically have gotten at the US event, or in the Europe event, I can now get that experience and cross-cultural flavor as a natural part of digital, so there's a lot of opportunity, there's a lot to miss about in-person events, but I think there's opportunities that are just massively untapped. >> Yeah, yeah, and I'm just going to get one more concept, which I don't think is getting enough action, get your take on it, but if you think of the value to the company, let's just stick with VMware for a minute, we're great fans of Pat and Sanjay, there is a information transfer when Pat gets up and does his keynote as from one to many tens of thousands, and there's value there, and again we talked about this rallying moment, but think of turning that on its head, which is really what digital provides, now there's an opportunity for Pat and Sanjay and the entire VMware senior team and junior team and product managers to now flip that information flow. So if you think of the user experience from the attendees' point of view, is it better for Sanjay to talk to 10,000 people in an audience, or would Sanjay rather hear from 10,000 people, and have that flow of information going back in? So if you think of it as a community event versus a one way communication of here's our exciting news, I think the value to the sponsor goes up dramatically, 'cause there's so much institutional knowledge and tribal knowledge and experience within all those people that are just sitting passively listening to that keynote. If this is a way to better suck that information back into the company, I don't think they'll ever go back to the other way it was. >> Yeah, two points, two data points on that. One, again, from the worship side of the house, at our Easter service, our church enabled every member who cared to to kind of do a five, eight second "Hey, this is the Townsend family, "happy Easter," and then 15 minutes before the live church service started, they just ran a video of family after family after family that I recognize, saying "Hi, happy Easter," so you have that moment, and how do you capture that online? VMware's social media team already does this well, they amplify end user content, there was a guy that did a video on how to install VMware Cloud Foundation in three hours, went viral. You have these opportunities, again, to hear from sources and have conversations that's really not practical from a typical conference perspective. I think I heard it best the other day, one of my attendees and presenters said "You know what, Keith, the virtual conference "is such a democratizing event because "it enables me, whether I could not afford "to go to a conference before, "or I couldn't travel, or whatever reasons "I could not attend a conference before," the virtual conference gives opportunities for collaborations that could not have taken place otherwise. >> Yeah, it's great, so again, Keith, thank you for spending a few minutes with us and sharing your thoughts, and again, for everybody, April 21st 2020, next week, >> 10: 30 AM central time, join the CTO virtual conference. Keith, always great to catch up, man. >> You too, Jeff, thanks a lot. >> All right, take care. He's Keith, I'm Jeff, you're watching theCUBE, thanks for watching, I'll see you next time. (calm music)

>>It's the queue covering the virtual vertical Big Data Conference 2020. Brought to you by vertical. >>Hello, everybody. Welcome to the new Normal. You're watching the Cube, and it's remote coverage of the vertical big data event on digital or gone Virtual. My name is Dave Volante, and I'm here with Colin Mahoney, who's a senior vice president at Micro Focus and the GM of Vertical Colin. Well, strange times, but the show goes on. Great to see you again. >>Good to see you too, Dave. Yeah, strange times indeed. Obviously, Safety first of everyone that we made >>a >>decision to go Virtual. I think it was absolutely the right all made it in advance of how things have transpired, but we're making the best of it and appreciate your time here, going virtual with us. >>Well, Joe and we're super excited to be here. As you know, the Cube has been at every single BDC since its inception. It's a great event. You just you just presented the key note to your to your audience, You know, it was remote. You didn't have that that live vibe. And you have a lot of fans in the vertical community But could you feel the love? >>Yeah, you know, it's >>it's hard to >>feel the love virtually, but I'll tell you what. The silver lining in all this is the reach that we have for this event now is much broader than it would have been a Z you know, you know, we brought this event back. It's been a few years since we've done it. We're super excited to do it, obviously, you know, in Boston, where it was supposed to be on location, but there wouldn't have been as many people that could participate. So the silver lining in all of this is that I think there's there's a lot of love out there we're getting, too. I have a lot of participants who otherwise would not have been able to participate in this. Both live as well. It's a lot of these assets that we're gonna have available. So, um, you know, it's out there. We've got an amazing customers and of practitioners with vertical. We've got so many have been with us for a long time. We've of course, have a lot of new customers as well that we're welcoming, so it's exciting. >>Well, it's been a while. Since you've had the BDC event, a lot of transpired. You're now part of micro focus, but I know you and I know the vertical team you guys have have not stopped. You've kept the innovation going. We've been following the announcements, but but bridge the gap between the last time. You know, we had coverage of this event and where we are today. A lot has changed. >>Oh, yeah, a lot. A lot has changed. I mean, you know, it's it's the software industry, right? So nothing stays the same. We constantly have Teoh keep going. Probably the only thing that stays the same is the name Vertical. Um and, uh, you know, you're not spending 10 which is just a phenomenal released for us. So, you know, overall, the the organization continues to grow. The dedication and commitment to this great form of vertical continues every single release we do as you know, and this hasn't changed. It's always about performance and scale and adding a whole bunch of new capabilities on that front. But it's also about are our main road map and direction that we're going towards. And I think one of the things have been great about it is that we've stayed true that from day one we haven't tried to deviate too much and get into things that are barred to outside your box. But we've really done, I think, a great job of extending vertical into places where people need a lot of help. And with vertical 10 we know we're going to talk more about that. But we've done a lot of that. It's super exciting for our customers, and all of this, of course, is driven by our customers. But back to the big data conference. You know, everybody has been saying this for years. It was one of the best conferences we've been to just so really it's. It's developers giving tech talks, its customers giving talks. And we have more customers that wanted to give talks than we had slots to fill this year at the event, which is another benefit, a little bit of going virtually accommodate a little bit more about obviously still a tight schedule. But it really was an opportunity for our community to come together and talk about not just America, but how to deal with data, you know, we know the volumes are slowing down. We know the complexity isn't slowing down. The things that people want to do with AI and machine learning are moving forward in a rapid pace as well. There's a lot talk about and share, and that's really huge part of what we try to do with it. >>Well, let's get into some of that. Um, your customers are making bets. Micro focus is actually making a bet on one vertical. I wanna get your perspective on one of the waves that you're riding and where are you placing your bets? >>Yeah, No, it's great. So, you know, I think that one of the waves that we've been writing for a long time, obviously Vertical started out as a sequel platform for analytics as a sequel, database engine, relational engine. But we always knew that was just sort of takes that we wanted to do. People were going to trust us to put enormous amounts of data in our platform and what we owe everyone else's lots of analytics to take advantage of that data in the lots of tools and capabilities to shape that data to get into the right format. The operational reporting but also in this day and age for machine learning and from some pretty advanced regressions and other techniques of things. So a huge part of vertical 10 is just doubling down on that commitment to what we call in database machine learning and ai. Um, And to do that, you know, we know that we're not going to come up with the world's best algorithms. Nor is that our focus to do. Our advantage is we have this massively parallel platform to ingest store, manage and analyze the data. So we made some announcements about incorporating PM ML models into the product. We continue to deepen our python integration. Building off of a new open source project we started with uber has been a great customer and partner on This is one of our great talks here at the event. So you know, we're continuing to do that, and it turns out that when it comes to anything analytics machine learning, certainly so much of what you have to do is actually prepare the big shape the data get the data in the right format, apply the model, fit the model test a model operationalized model and is a great platform to do that. So that's a huge bet that were, um, continuing to ride on, taking advantage of and then some of the other things that we've just been seeing. You continue. I'll take object. Storage is an example on, I think Hadoop and what would you point through ultimately was a huge part of this, but there's just a massive disruption going on in the world around object storage. You know, we've made several bets on S three early we created America Yang mode, which separates computing story. And so for us that separation is not just about being able to take care of your take advantage of cloud economics as we do, or the economics of object storage. It's also about being able to truly isolate workloads and start to set the sort of platform to be able to do very autonomous things in the databases in the database could actually start self analysing without impacting many operational workloads, and so that continues with our partnership with pure storage. On premise, we just announced that we're supporting beyond Google Cloud now. In addition to Amazon, we supported on we've got a CFS now being supported by are you on mode. So we continue to ride on that mega trend as well. Just the clouds in general. Whether it's a public cloud, it's a private cloud on premise. Giving our customers the flexibility and choice to run wherever it makes sense for them is something that we are very committed to. From a flexibility standpoint. There's a lot of lock in products out there. There's a lot of cloud only products now more than ever. We're hearing our customers that they want that flexibility to be able to run anywhere. They want the ease of use and simplicity of native cloud experiences, which we're giving them as well. >>I want to stay in that architectural component for a minute. Talk about separating compute from storage is not just about economics. I mean apart Is that you, you know, green, really scale compute separate from storage as opposed to in chunks. It's more efficient, but you're saying there's other advantages to operational and workload. Specificity. Um, what is unique about vertical In this regard, however, many others separate compute from storage? What's different about vertical? >>Yeah, I think you know, there's a lot of differences about how we do it. It's one thing if you're a cloud native company, you do it and you have a shared catalog. That's key value store that all of your customers are using and are on the same one. Frankly, it's probably more of a security concern than anything. But it's another thing. When you give that capability to each customer on their own, they're fully protected. They're not sharing it with any other customers. And that's something that we hear a lot of insights from our customers. They want to be able to separate compute and storage. But they want to be able to do this in their own environment so that they know that in their data catalog there's no one else is. You share in that catalog, there's no single point of failure. So, um, that's one huge advantage that we have. And frankly, I think it just comes from being a company that's operating on premise and, uh, up in the cloud. I think another huge advantages for us is we don't know what object storage platform is gonna win, nor do we necessarily have. We designed the young vote so that it's an sdk. We started with us three, but it could be anything. It's DFS. That's three. Who knows what what object storage formats were going to be there and then finally, beyond just the object storage. We're really one of the only database companies that actually allows our customers to natively operate on data in very different formats, like parquet and or if you're familiar with those in the Hadoop community. So we not only embrace this kind of object storage disruption, but we really embrace the different data formats. And what that means is our customers that have data pipelines that you know, fully automated, putting this information in different places. They don't have to completely reload everything to take advantage of the Arctic analytics. We can go where the data is connected into it, and we offer them a lot of different ways to take advantage of those analytics. So there are a couple of unique differences with verdict, and again, I think are really advance. You know, in many ways, by not being a cloud native platform is that we're very good at operating in different environments with different formats that changing formats over time. And I don't think a lot of the other companies out there that I think many, particularly many of the SAS companies were scrambling. They even have challenges moving from saying Amazon environment to a Microsoft azure environment with their office because they've got so much unique Band Aid. Excuse me in the background. Just holding the system up that is native to any of those. >>Good. I'm gonna summarize. I'm hearing from you your Ferrari of databases that we've always known. Your your object store agnostic? Um, it's any. It's the cloud experience that you can bring on Prem to virtually any cloud. All the popular clouds hybrid. You know, aws, azure, now Google or on Prem and in a variety of different data formats. And that is, I think, you know, you need the combination of those I think is unique in the marketplace. Um, before we get into the news, I want to ask you about data silos and data silos. You mentioned H DFs where you and I met back in the early days of big data. You know, in some respects, you know, Hadoop help break down the silos with distributing the date and leave it in place, and in other respects, they created Data Lakes, which became silos. And so we have. Yet all these other sales people are trying to get to, Ah, digital transformation meeting, putting data at their core virtually obviously, and leave it in place. What's your thoughts on that in terms of data being a silo buster Buster, How does verdict of way there? >>Yeah, so And you're absolutely right, I think if even if you look at his due for all the new data that gets into the do. In many ways, it's created yet another large island of data that many organizations are struggling with because it's separate from their core traditional data warehouse. It's separate from some of the operational systems that they have, and so there might be a lot of data in there, but they're still struggling with How do I break it out of that large silo and or combine it again? I think some some of the things that verdict it doesn't part of the announcement just attend his migration tools to make it really easy. If you do want to move it from one platform to another inter vertical, but you don't have to move it, you can actually take advantage of a lot of the data where it resides with vertical, especially in the Hadoop brown with our external table storage with our building or compartment natively. So we're very pragmatic about how our customers go about this. Very few customers, Many of them tried it with Hadoop and realize that didn't work. But very few customers want a wholesale. Just say we're going to throw everything out. We're gonna get rid of our data warehouse. We're gonna hit the pause button and we're going to go from there. Just it's not possible to do that. So we've spent a lot of time investing in the product, really work with them to go where the data is and then seamlessly migrate. And when it makes sense to migrate, you mentioned the performance of America. Um, and you talked about it is the variety. It definitely is. And one other thing that we're really proud of this is that it actually is not a gas guzzler. Easy either One of the things that we're seeing, a lot of the other cloud databases pound for pound you get on the 10th the hardware vertical running up there. You get over 10 x performance. We're seeing that a lot, so it's Ah, it's not just about the performance, but it's about the efficiency as well. And I think that efficiency is really important when it comes to silos. Because there's there's just only so much horsepower out there. And it's easier for companies to play tricks and lots of servers environment when they start up for so many organizations and cloud and frankly, looking at the bills they're getting from these cloud workloads that are running. They really conscious of that. >>Yeah. The big, big energy companies love the gas guzzlers. A lot of a lot of cloud. Cute. But let's get into the news. Uh, 10 dot io you shared with your the audience in your keynote. One of the one of the highlights of data. What do we need to know? >>Yeah, so, you know, again doubling down on these mega trends, I'll start with Machine Learning and ai. We've done a lot of work to integrate so that you can take native PM ml models, bring them into vertical, run them massively parallel and help shape you know your data and prepare it. Do all the work that we know is required true machine learning. And for all the hype that there is around it, this is really you know, people want to do a lot of unsupervised machine learning, whether it's for healthcare fraud, detection, financial services. So we've doubled down on that. We now also support things like Tensorflow and, you know, as I mentioned, we're not going to come up with the best algorithms. Our job is really to ensure that those algorithms that people coming up with could be incorporated, that we can run them against massive data sets super efficiently. So that's that's number one number two on object storage. We continue to support Mawr object storage platforms for ya mode in the cloud we're expanding to Google G CPI, Google's cloud beyond just Amazon on premise or in the cloud. Now we're also supporting HD fs with beyond. Of course, we continue to have a great relationship with our partners, your storage on premise. Well, what we continue to invest in the eon mode, especially. I'm not gonna go through all the different things here, but it's not just sort of Hey, you support this and then you move on. There's so many different things that we learn about AP I calls and how to save our customers money and tricks on performance and things on the third areas. We definitely continue to build on that flexibility of deployment, which is related to young vote with. Some are described, but it's also about simplicity. It's also about some of the migration tools that we've announced to make it easy to go from one platform to another. We have a great road map on these abuse on security, on performance and scale. I mean, for us. Those are the things that we're working on every single release. We probably don't talk about them as much as we need to, but obviously they're critically important. And so we constantly look at every component in this product, you know, Version 10 is. It is a huge release for any product, especially an analytic database platform. And so there's We're just constantly revisiting you know, some of the code base and figuring out how we can do it in new and better ways. And that's a big part of 10 as well. >>I'm glad you brought up the machine Intelligence, the machine Learning and AI piece because we would agree that it is really one of the things we've noticed is that you know the new innovation cocktail. It's not being driven by Moore's law anymore. It's really a combination of you. You've collected all this data over the last 10 years through Hadoop and other data stores, object stores, etcetera. And now you're applying machine intelligence to that. And then you've got the cloud for scale. And of course, we talked about you bringing the cloud experience, whether it's on Prem or hybrid etcetera. The reason why I think this is important I wanted to get your take on this is because you do see a lot of emerging analytic databases. Cloud Native. Yes, they do suck up, you know, a lot of compute. Yeah, but they also had a lot of value. And I really wanted to understand how you guys play in that new trend, that sort of cloud database, high performance, bringing in machine learning and AI and ML tools and then driving, you know, turning data into insights and from what I'm hearing is you played directly in that and your differentiation is a lot of the things that we talk about including the ability to do that on from and in the cloud and across clouds. >>Yeah, I mean, I think that's a great point. We were a great cloud database. We run very well upon three major clouds, and you could argue some of the other plants as well in other parts of the world. Um, if you talk to our customers and we have hundreds of customers who are running vertical in the cloud, the experience is very good. I think it would always be better. We've invested a lot in taking advantage of the native cloud ecosystem, so that provisioning and managing vertical is seamless when you're in that environment will continue to do that. But vertical excuse me as a cloud platform is phenomenal. And, um, you know, there's a There's a lot of confusion out there, you know? I think there's a lot of marketing dollars spent that won't name many of the companies here. You know who they are, You know, the cloud Native Data Warehouse and it's true, you know their their software as a service. But if you talk to a lot of our customers, they're getting very good and very similar. experiences with Bernie comic. We stopped short of saying where software is a service because ultimately our customers have that control of flexibility there. They're putting verdict on whichever cloud they want to run it on, managing it. Stay tuned on that. I think you'll you'll hear from or more from us about, you know, that going going even further. But, um, you know, we do really well in the cloud, and I think he on so much of yang. And, you know, this has really been a sort of 2.5 years and never for us. But so much of eon is was designed around. The cloud was designed around Cloud Data Lakes s three, separation of compute and storage on. And if you look at the work that we're doing around container ization and a lot of these other elements, it just takes that to the next level. And, um, there's a lot of great work, so I think we're gonna get continue to get better at cloud. But I would argue that we're already and have been for some time very good at being a cloud analytic data platform. >>Well, since you open the door I got to ask you. So it's e. I hear you from a performance and architectural perspective, but you're also alluding two. I think something else. I don't know what you can share with us. You said stay tuned on that. But I think you're talking about Optionality, maybe different consumption models. That am I getting that right and you share >>your difficult in that right? And actually, I'm glad you wrote something. I think a huge part of Cloud is also has nothing to do with the technology. I think it's how you and seeing the product. Some companies want to rent the product and they want to rent it for a certain period of time. And so we allow our customers to do that. We have incredibly flexible models of how you provision and purchase our product, and I think that helps a lot. You know, I am opening the door Ah, a little bit. But look, we have customers that ask us that we're in offer them or, you know, we can offer them platforms, brawl in. We've had customers come to us and say please take over systems, um, and offer something as a distribution as I said, though I think one thing that we've been really good at is focusing on on what is our core and where we really offer offer value. But I can tell you that, um, we introduced something called the Verdict Advisor Tool this year. One of the things that the Advisor Tool does is it collects information from our customer environments on premise or the cloud, and we run through our own machine learning. We analyze the customer's environment and we make some recommendations automatically. And a lot of our customers have said to us, You know, it's funny. We've tried managed service, tried SAS off, and you guys blow them away in terms of your ability to help us, like automatically managed the verdict, environment and the system. Why don't you guys just take this product and converted into a SAS offering, so I won't go much further than that? But you can imagine that there's a lot of innovation and a lot of thoughts going into how we can do that. But there's no reason that we have to wait and do that today and being able to offer our customers on premise customers that same sort of experience from a managed capability is something that we spend a lot of time thinking about as well. So again, just back to the automation that ease of use, the going above and beyond. Its really excited to have an analytic platform because we can do so much automation off ourselves. And just like we're doing with Perfect Advisor Tool, we're leveraging our own Kool Aid or Champagne Dawn. However you want to say Teoh, in fact, tune up and solve, um, some optimization for our customers automatically, and I think you're going to see that continue. And I think that could work really well in a bunch of different wallets. >>Welcome. Just on a personal note, I've always enjoyed our conversations. I've learned a lot from you over the years. I'm bummed that we can't hang out in Boston, but hopefully soon, uh, this will blow over. I loved last summer when we got together. We had the verdict throwback. We had Stone Breaker, Palmer, Lynch and Mahoney. We did a great series, and that was a lot of fun. So it's really it's a pleasure. And thanks so much. Stay safe out there and, uh, we'll talk to you soon. >>Yeah, you too did stay safe. I really appreciate it up. Unity and, you know, this is what it's all about. It's Ah, it's a lot of fun. I know we're going to see each other in person soon, and it's the people in the community that really make this happen. So looking forward to that, but I really appreciate it. >>Alright. And thank you, everybody for watching. This is the Cube coverage of the verdict. Big data conference gone, virtual going digital. I'm Dave Volante. We'll be right back right after this short break. >>Yeah.

>> Jeff: Hello, everybody and thank you for Joining us today for the virtual "Vertica VBC" 2020. Today's breakout session has been titled "Optimizing Query Performance and Resource Pool Tuning" I'm Jeff Ealing, I lead Vertica marketing. I'll be your host for this breakout session. Joining me today are Rakesh Banula, and Abhi Thakur, Vertica product technology engineers and key members of the Vertica customer success team. But before we begin, I encourage you to submit questions or comments during the virtual session. You don't have to wait. Just type your question or comment in the question box below the slides and click Submit. There will be a Q&A session at the end of the presentation. We'll answer as many questions we're able to during that time. Any questions we don't address, we'll do our best to answer them offline. Alternatively, visit Vertica forums at forum.vertica.com to post your questions there after the session. Our engineering team is planning to Join the forums to keep the conversation going. Also a reminder that you can maximize your screen by clicking the double arrow button in the lower right corner of your slides. And yes, this virtual session is being recorded, will be available to view on demand this week. We'll send you a notification as soon as it's ready. Now let's get started. Over to you Rakesh. >> Rakesh: Thank you, Jeff. Hello, everyone. My name is Rakesh Bankula. Along with me, we have Bir Abhimanu Thakur. We both are going to cover the present session on "Optimizing Query Performance and Resource Pool Tuning" In this session, we are going to discuss query optimization, how to review the query plans and how to get the best query plans with proper production design. Then discuss on resource allocations and how to find resource contention. And we will continue the discussion on important use cases. In general, to successfully complete any activity or any project, the main things it requires are the plan. Plan for that activity on what to do first, what to do next, what are things you can do in parallel? The next thing you need, the best people to work on that project as per the plan. So, first thing is a plan and next is the people or resources. If you overload the same set of people, our resources by involving them in multiple projects or activities or if any person or resource is sick in a given project is going to impact on the overall completion of that project. The same analogy we can apply through query performance too. For a query to perform well, it needs two main things. One is the best query plan and other is the best resources to execute the plan. Of course, in some cases, resource contention, whether it can be from system side or within the database may slow down the query even when we have best query plan and best resource allocations. We are going to discuss each of these three items a little more in depth. Let us start with query plan. User submits the query to database and Vertica Optimizer generates the query plan. In generating query plans, optimizer uses the statistics information available on the tables. So, statistics plays a very important role in generating good query plans. As a best practice, always maintain up-to-date statistics. If you want to see how query plan looks like, add explain keyword in front of your query and run that query. It displays the query plan on the screen. Other option is BC explained plans. It saves all the explained plans of the queries run on the database. So, once you have a query plan, once you're checking it to make sure plan is good. The first thing I would look for, no statistics are predicted out of range. If you see any of these, means table involved in the query, have no up to date statistics. It is now the time to update the statistics. Next thing to explain plans are broadcast, three segments around the Join operator, global re segments around a group by operators. These indicate during the runtime of the query, data flow between the nodes over the network and will slow down the query execution. As far as possible, prevent such operations. How to prevent this, we will discuss in the projection design topic. Regarding the Join order, check on inner side and outer side, which tables are used, how many rows each side processing. In (mumbles) picking a table, having smaller number of rows is good in case of as shown as, as Join built in memory, smaller the number of rows, faster it is to build the hash table and also helps in consuming less memory. Then check if the plan is picking query specific projection or default projections. If optimizer ignoring any query specific projection, but picking the default super projection will show you how to use query specific hints to follow the plant to pick query specific projections which helps in improving the performance. Okay, here is one example query plan of a query trying to find number of products sold from a store in a given state. This query is having Joins between store table, product table and group by operation to find the count. So, first look for no statistics particularly around storage access path. This plan is not reporting any no statistics. This means statistics are up to date and plan is good so far. Then check what projections are used. This is also around the storage access part. For Join orders check, we have Hash Join in path ID 4 having it In Path ID 6 processing 60,000 rows and outer is in Path ID 7 processing 20 million rows. Inner side processing last record is good. This helps in building hash table quicker by using less memory. Check if any broadcast re segments, Joins in Path ID 4 and also Path ID 3. Both are having inner broadcast, Inners are having 60,000 records are broadcasted to all nodes in the cluster. This could impact the query performance negatively. These are some of the main things which we normally check in the explained plans. Still now, We have seen that how to get good query plans. To get good query plans, we need to maintain up to date statistics and also discussed how to review query plans. Projection design is the next important thing in getting good query plans, particularly in preventing broadcasts re segments. Broadcast re segments happens during Join operation, random existing segmentation class of the projections involved in the Join not matching with the Join columns in the query. These operations causes data flow over the network and negatively impacts the query performance particularly when it transfers millions or billions of rows. These operations also causes query acquire more memory particularly in network send and receive operations. One can avoid these broadcast re segments with proper projection segmentation, say, Join involved between two fact tables, T1, T2 on column I then segment the projections on these T1, T2 tables on column I. This is also called identically segmenting projections. In other cases, Join involved between a fact table and a dimension table then replicate or create an unsegmented projection on dimension table will help avoiding broadcast re segments during Join operation. During group by operation, global re segment groups causes data flow over the network. This can also slow down the query performance. To avoid these global re segment groups, create segmentation class of the projection to match with the group by columns in the query. In previous slides, we have seen the importance of projection segmentation plus in preventing the broadcast re segments during the Join operation. The order by class of production design plays important role in picking the Join method. We have two important Join methods, Merge Join and Hash Join. Merge Join is faster and consumes less memory than hash Join. Query plan uses Merge Join when both projections involved in the Join operation are segmented and ordered on the Join keys. In all other cases, Hash Join method will be used. In case of group by operation too, we have two methods. Group by pipeline and group by Hash. Group by pipeline is faster and consumes less memory compared to group by Hash. The requirements for group by pipeline is, projection must be segmented and ordered by on grouping columns. In all other cases, group by hash method will be used. After all, we have seen importance of stats and projection design in getting good query plans. As statistics are based on estimates over sample of data, it is possible in a very rare cases, default query plan may not be as good as you expected, even after maintaining up-to-date stats and good projection design. To work around this, Vertica providing you some query hints to force optimizer to generate even better query plans. Here are some example Join hints which helps in picking Join method and how to distribute the data, that is broadcast or re segment on inner or outer side and also which group by method to pick. The table level hints helps to force pick query specific projection or skipping any particular projection in a given query. These all hints are available in Vertica documentation. Here are a few general hints useful in controlling how to load data with the class materialization et cetera. We are going to discuss some examples on how to use these query hints. Here is an example on how to force query plan to pick Hash Join. The hint used here is JTYPE, which takes arguments, H for HashJoin, M for MergeJoin. How to place this hint, just after the Join keyword in the query as shown in the example here. Another important Join in this, JFMT, Join For My Type hint. This hint is useful in case when Join columns are lost workers. By default Vertica allocates memory based on column data type definition, not by looking at the actual data length in those columns. Say for example, Join column defined as (mumbles) 1000, 5000 or more, but actual length of the data in this column is, say, less than 50 characters. Vertica going to use more memory to process such columns in Join and also slow down the Join processing. JSMP hint is useful in this particular case. JSMP parameter uses the actual length of the Join column. As shown in the example, using JFMP of V hint helps in reducing the memory requirement for this query and executes faster too. Distrib hint helps in how to force inner or outer side of the Join operator to be distributed using broadcast or re segment. Distrib takes two parameters. First is the outer site and second is the inner site. As shown in the example, DISTRIB(A,R) after Join keyword in the query helps to force re segment the inner side of the Join, outer side, leaving it to optimizer to choose that distribution method. GroupBy Hint helps in forcing query plan to pick Group by Hash or Group by Pipeline. As shown in the example, GB type or hash, used just after group by class in the query helps to force this query to pick Group by Hashtag. See now, we discussed the first part of query performance, which is query plans. Now, we are moving on to discuss next part of query performance, which is resource allocation. Resource Manager allocates resources to queries based on the settings on resource pools. The main resources which resource pools controls are memory, CPU, query concurrency. The important resource pool parameters, which we have to tune according to the workload are memory size, plan concurrency, mass concurrency and execution parallelism. Query budget plays an important role in query performance. Based on the query budget, query planner allocate worker threads to process the query request. If budget is very low, query gets less number of threads, and if that query requires to process huge data, then query takes longer time to execute because of less threads or less parallelism. In other case, if the budget is very high and query executed on the pool is a simple one which results in a waste of resources, that is, query which acquires the resources holds it till it complete the execution, and that resource is not available to other queries. Every resource pool has its own query budget. This query budget is calculated based on the memory size and client and currency settings on that pool. Resource pool status table has a column called Query Budget KB, which shows the budget value of a given resource pool. The general recommendation for query budget is to be in the range of one GB to 10 GB. We can do a few checks to validate if the existing resource pool settings are good or not. First thing we can check to see if query is getting resource allocations quickly, or waiting in the resource queues longer. You can check this in resource queues table on a live system multiple times, particularly during your peak workload hours. If large number of queries are waiting in resource queues, indicates the existing resource pool settings not matching with your workload requirements. Might be, memory allocated is not enough, or max concurrency settings are not proper. If query's not spending much time in resource queues indicates resources are allocated to meet your peak workload, but not sure if you have over or under allocated the resources. For this, check the budget in resource pool status table to find any pool having way larger than eight GB or much smaller than one GB. Both over allocation and under allocation of budget is not good for query performance. Also check in DC resource acquisitions table to find any transaction acquire additional memory during the query execution. This indicates the original given budget is not sufficient for the transaction. Having too many resource pools is also not good. How to create resource pools or even existing resource pools. Resource pool settings should match to the present workload. You can categorize the workload into well known workload and ad-hoc workload. In case of well-known workload, where you will be running same queries regularly like daily reports having same set of queries processing similar size of data or daily ETL jobs et cetera. In this case, queries are fixed. Depending on the complexity of the queries, you can further divide it into low, medium, high resource required pools. Then try setting the budget to 1 GB, 4 GB, 8 GB on these pools by allocating the memory and setting the plan concurrency as per your requirement. Then run the query and measure the execution time. Try couple UP iterations by increasing and then decreasing the budget to find the best settings for your resource pools. For category of ad-hoc workload where there is no control over the number of users going to run the queries concurrently, or complexity of queries user going to submit. For this category, we cannot estimate, in advance, the optimum query budget. So for this category of workload, we have to use cascading resource pool settings where query starts on the pool based on the runtime they have set, then query resources moves to a secondary pool. This helps in preventing smaller queries waiting for resources, longer time when a big query consuming all resources and rendering for a longer time. Some important resource pool monitoring tables, analyze system, you can query resource cues table to find any transaction waiting for resources. You will also find on which resource pool transaction is waiting, how long it is waiting, how many queries are waiting on the pool. Resource pool status gives info on how many queries are in execution on each resource pool, how much memory in use and additional info. For resource consumption of a transaction which was already completed, you can play DC resource acquisitions to find how much memory a given transaction used per node. DC resource pool move table shows info on what our transactions moved from primary to secondary pool in case of cascading resource pools. DC resource rejections gives info on which node, which resource a given transaction failed or rejected. Query consumptions table gives info on how much CPU disk network resources a given transaction utilized. Till now, we discussed query plans and how to allocate resources for better query performance. It is possible for queries to perform slower when there is any resource contention. This contention can be within database or from system side. Here are some important system tables and queries which helps in finding resource contention. Table DC query execution gives the information on transaction level, how much time it took for each execution step. Like how much time it took for planning, resource allocation, actual execution etc. If the time taken is more in planning, which is mostly due to catalog contentions, you can play DC lock releases table as shown here to see how long transactions are waiting to acquire global catalog lock, how long transaction holding GCL x. Normally, GCL x acquire and release should be done within a couple of milliseconds. If the transactions are waiting for a few seconds to acquire GCL x or holding GCL x longer indicates some catalog contention, which may be due to too many concurrent queries or due to long running queries, or system services holding catalog mutexes and causing other transactions to queue up. A query is given here, particularly the system tables will help you further narrow down the contention. You can vary sessions table to find any long-running user queries. You can query system services table to find any service like analyze row counts, move out, merge operation and running for a long time. DC all evens table gives info on what are slower events happening. You can also query system resource usage table to find any particular system resource like CPU memory, disk IO or network throughput, saturating on any node. It is possible once slow node in the cluster could impact overall performance of queries negatively. To identify any slow node in the cluster, we use queries. Select one, and (mumbles) Clearly key one query just executes on initiative node. On a good node, kV one query returns within 50 milliseconds. As shown here, you can use a script to run this, select kV one query on all nodes in the cluster. You can repeat this test multiple times, say five to 10 times then reveal the time taken by this query on all nodes in all tech (mumbles) . If there is any one node taking more than a few seconds compared to other notes taking just milliseconds, then something is wrong with that node. To find what is going on with the node, which took more time for kV one query, run perf top. Perf top gives info on stopped only lister functions in which system spending most of the time. These functions can be counter functions or Vertica functions, as shown here. Based on their systemic spending most of the time we'll get some clue on what is going on with that code. Abhi will continue with the remaining part of the session. Over to you Abhi. >> Bir: Hey, thanks, Rakesh. My name is Abhimanu Thakur and today I will cover some performance cases which we had addressed recently in our customer clusters which we will be applying the best practices just showed by Rakesh. Now, to find where the performance problem is, it is always easy if we know where the problem is. And to understand that, like Rakesh just explained, the life of a query has different phases. The phases are pre execution, which is the planning, execution and post execution which is releasing all the required resources. This is something very similar to a plane taking a flight path where it prepares itself, gets onto the runway, takes off and lands back onto the runway. So, let's prepare our flight to take off. So, this is a use case which is from a dashboard application where the dashboard fails to refresh once in a while, and there is a batch of queries which are sent by the dashboard to the Vertica database. And let's see how we can be able to see where the failure is or where the slowness is. To reveal the dashboard application, these are very shortly queries, we need to see what were the historical executions and from the historical executions, we basically try to find where is the exact amount of time spent, whether it is in the planning phase, execution phase or in the post execution and if they are pretty consistent all the time, which means the plan has not changed in the execution which will also help us determine what is the memory used and if the memory budget is ideal. As just showed by Rakesh, the budget plays a very important role. So DC query executions, one-stop place to go and find your timings, whether it is a timing extra or is it execute plan or is it an abandoned plan. So, looking at the queries which we received and the times from the scrutinize, we find most of the time average execution, the execution is pretty consistent and there is some time, extra time spent in the planning phase which users of (mumbles) resource contention. This is a very simple matrix which you can follow to find if you have issues. So the system resource convention catalog contention and resource contention, all of these contribute mostly because of the concurrency. And let's see if we can drill down further to find the issue in these dashboard application queries. So, to get the concurrency, we pull out the number of queries issued, what is the max concurrency achieved, what are the number of threads, what is the overall percentage of query duration and all this data is available in the V advisor report. So, as soon as you provide scrutinize, we generate the V advisor report which helps us get complete insight of this data. So, based on this we definitely see there is very high concurrency and most of the queries finish in less than a second which is good. There are queries which go beyond 10 seconds and over a minute, but so definitely, the cluster had concurrency. What is more interesting is to find from this graph is... I'm sorry if this is not very readable, but the topmost line what you see is the Select and the bottom two or three lines are the create, drop and alters. So definitely this cluster is having a lot of DDL and DMLs being issued and what do they contribute is if there is a large DDL and DMLs, they cause catalog contention. So, we need to make sure that the batch, what we're sending is not causing too many catalog contention into the cluster which delays the complete plan face as the system resources are busy. And the same time, what we also analyze is the analyze tactics running every hour which is very aggressive, I would say. It should be scheduled to be need only so if a table has not changed drastically that's not scheduled analyzed tactics for the table. A couple more settings has shared by Rakesh is, it definitely plays a important role in the modeled and mode operations. So now, let's look at the budget of the query. The budget of the resource pool is currently at about two GB and it is the 75 percentile memory. Queries are definitely executing at that same budget, which is good and bad because these are dashboard queries, they don't need such a large amount of memory. The max memory as shown here from the capture data is about 20 GB which is pretty high. So what we did is, we found that there are some queries run by different user who are running in the same dashboard pool which should not be happening as dashboard pool is something like a premium pool or kind of a private run way to run your own private jet. And why I made that statement is as you see, resource pools are lik runways. You have different resource pools, different runways to cater different types of plane, different types of flights which... So, as you can manage your resource pools differently, your flights can take off and land easily. So, from this we did remind that the budget is something which could be well done. Now let's look... As we saw in the previous numbers that there were some resource weights and like I said, because resource pools are like your runways. So if you have everything ready, your plane is waiting just to get onto the runway to take off, you would definitely not want to be in that situation. So in this case, what we found is the coolest... There're quite a bit number of queries which have been waited in the pool and they waited almost a second and which can be avoided by modifying the the amount of resources allocated to the resource pool. So in this case, we increase the resource pool to provide more memory which is 80 GB and reduce the budget from two GB to one GB. Also making sure that the plan concurrency is increased to match the memory budget and also we moved the user who was running into the dashboard query pool. So, this is something which we have gone, which we found also in the resource pool is the execution parallelism and how this affects and what what number changes. So, execution parallelism is something which allocates the plan, allocates the number of threads, network buffers and all the data around it before even the query executes. And in this case, this pool had auto, which defaults to the core count. And so, dashboard queries not being too high on resources, they need to just get what they want. So we reduced the execution parallelism to eight and this drastically brought down the amount of threads which were needed without changing the time of execution. So, this is all what we saw how we could tune before the query takes off. Now, let's see what path we followed. This is the exact path what we followed. Hope of this diagram helps and these are the things which we took care of. So, tune your resource pool, adjust your execution parallelism based on the type of the queries the resource pool is catering to and match your memory sizes and don't be too aggressive on your resource budget. And see if you could replace your staging tables with temporary tables as they help a lot in reducing the DDLs and DMLs, reducing the catalog contention and the places where you cannot replace them with the truncate tables, reduce your analyzed statics duration and if possible, follow the best practices for a couple more operations. So moving on, let's let our query take a flight and see what best practices can be applied here. So this is another, I would say, very classic example of query where the query has been running and suddenly stops to fail. And if there is... I think most of the other seniors in a Join did not fit in memory. What does this mean? It basically means the inner table is trying to build a large Hash table, and it needs a lot of memory to fit. There are only two reasons why it could fail. One, your statics are outdated and your resource pool is not letting you grab all the memory needed. So in this particular case, the resource pool is not allowing all the memory it needs. As you see, the query acquire 180 GB of memory, and it failed. When looking at the... In most cases, you should be able to figure out the issue looking at the explained plan of the query as shared by Rakesh earlier. But in this case if you see, the explained plan looks awesome. There's no other operator like in a broadcast or outer V segment or something like that, it's just Join hash. So looking further we find into the projection. So inner is on segmented projection, the outer is segmented. Excellent. This is what is needed. So in this case, what we would recommend is go find further what is the cost. The cost to scan this row seems to be pretty high. There's the table DC query execution in their profiles in Vertica, which helps you drill down to every smallest amount of time, memory and what were the number of rows used by individual operators per pack. So, while looking into the execution engine profile details for this query, we found the amount of time spent is on the Join operator and it's the Join inner Hash table build time, which has taking huge amount of time. It's just waiting basically for the lower operators can and storage union to pass the data. So, how can we avoid this? Clearly, we can avoid it by creating a segmented projection instead of unsegmented projection on such a large table with one billion rows. Following the practice to create the projection... So this is a projection which was created and it was segmented on the column which is part of the select clause over here. Now, that plan looks nice and clean still, and the execution of this query now executes in 22 minutes 15 seconds and the most important you see is the memory. It executes in just 15 GB of memory. So, basically to what was done is the unsegmented projection which acquires a lot of memory per node is now not taking that much of memory and executing faster as it has been divided by the number of nodes per node to execute only a small share of data. But, the customer was still not happy as 22 minutes is still high. And let's see if we can tune it further to make the cost go down and execution time go down. So, looking at the explained plan again, like I said, most of the time, you could see the plan and say, "What's going on?" In this case, there is an inner re segment. So, how could we avoid the inner re segments? We can avoid the inner re segment... Most of the times, all the re segments just by creating the projection which are identically segmented which means your inner and outer both have the same amount, same segmentation clause. The same was done over here, as you see, there's now segment on sales ID and also ordered by sales ID which helps us execute the query drop from 22 minutes to eight minutes, and now the memory acquired is just equals to the pool budget which is 8 GB. And if you see, the most What is needed is the hash Join is converted into a merge Join being the ordered by the segmented clause and also the Join clause. So, what this gives us is, it has the new global data distribution and by changing the production design, we have improved the query performance. But there are times when you could not have changed the production design and there's nothing much which can be done. In all those cases, as even in the first case of Vertica after fail of the inner Join, the second Vertica replan (mumbles) spill to this operator. You could let the system degrade by acquiring 180 GB for whatever duration of minutes the query had. You could simply use this hand to replace and run the query in the very first go. Let the system have all the resources it needs. So, use hints wherever possible and filter disk is definitely your option where there're no other options for you to change your projection design. Now, there are times when you find that you have gone through your query plan, you have gone through every other thing and there's not much you see anywhere, but you definitely look at the query and you feel that, "Now, I think I can rewrite this query." And how what makes you decide that is you look at the query and you see that the same table has been accessed several times in my query plan, how can I rewrite this query to access my table just once? And in this particular use case, a very simple use case where a table is scanned three times for several different filters and then a union in Vertica union is kind of costly operator I would say, because union does not know what's the amount of data which should be coming from the underlying query. So we allocate a lot of resources to keep the union running. Now, we could simply replace all these unions by simple "Or" clause. So, simple "Or" clause changes the complete plan of the query and the cost drops down drastically. And now the optimizer almost know the exact amount of rows it has to process. So change, look at your query plans and see if you could make the execution in the profile or the optimizer do better job just by doing some small rewrites. Like if there are some tables frequently accessed you could even use a "With" clause which will do an early materialization and make use the better performance or for the union which I just shared and replace your left Joins with right Joins, use your (mumbles) like shade earlier for you changing your hash table types. This is the exact part what we have followed in this presentation. Hope this presentation was helpful in addressing, at least finding some performance issues in your queries or in your class test. So, thank you for listening to our presentation. Now we are ready for Q&A.

>> Joy: Welcome to the Virtual Big Data Conference. Vertica is so excited to host this event. I'm Joy King, and I'll be your host for today's Big Data Conference Keynote Session. It's my honor and my genuine pleasure to lead Vertica's product and go-to-market strategy. And I'm so lucky to have a passionate and committed team who turned our Vertica BDC event, into a virtual event in a very short amount of time. I want to thank the thousands of people, and yes, that's our true number who have registered to attend this virtual event. We were determined to balance your health, safety and your peace of mind with the excitement of the Vertica BDC. This is a very unique event. Because as I hope you all know, we focus on engineering and architecture, best practice sharing and customer stories that will educate and inspire everyone. I also want to thank our top sponsors for the virtual BDC, Arrow, and Pure Storage. Our partnerships are so important to us and to everyone in the audience. Because together, we get things done faster and better. Now for today's keynote, you'll hear from three very important and energizing speakers. First, Colin Mahony, our SVP and General Manager for Vertica, will talk about the market trends that Vertica is betting on to win for our customers. And he'll share the exciting news about our Vertica 10 announcement and how this will benefit our customers. Then you'll hear from Amy Fowler, VP of strategy and solutions for FlashBlade at Pure Storage. Our partnership with Pure Storage is truly unique in the industry, because together modern infrastructure from Pure powers modern analytics from Vertica. And then you'll hear from John Yovanovich, Director of IT at AT&T, who will tell you about the Pure Vertica Symphony that plays live every day at AT&T. Here we go, Colin, over to you. >> Colin: Well, thanks a lot joy. And, I want to echo Joy's thanks to our sponsors, and so many of you who have helped make this happen. This is not an easy time for anyone. We were certainly looking forward to getting together in person in Boston during the Vertica Big Data Conference and Winning with Data. But I think all of you and our team have done a great job, scrambling and putting together a terrific virtual event. So really appreciate your time. I also want to remind people that we will make both the slides and the full recording available after this. So for any of those who weren't able to join live, that is still going to be available. Well, things have been pretty exciting here. And in the analytic space in general, certainly for Vertica, there's a lot happening. There are a lot of problems to solve, a lot of opportunities to make things better, and a lot of data that can really make every business stronger, more efficient, and frankly, more differentiated. For Vertica, though, we know that focusing on the challenges that we can directly address with our platform, and our people, and where we can actually make the biggest difference is where we ought to be putting our energy and our resources. I think one of the things that has made Vertica so strong over the years is our ability to focus on those areas where we can make a great difference. So for us as we look at the market, and we look at where we play, there are really three recent and some not so recent, but certainly picking up a lot of the market trends that have become critical for every industry that wants to Win Big With Data. We've heard this loud and clear from our customers and from the analysts that cover the market. If I were to summarize these three areas, this really is the core focus for us right now. We know that there's massive data growth. And if we can unify the data silos so that people can really take advantage of that data, we can make a huge difference. We know that public clouds offer tremendous advantages, but we also know that balance and flexibility is critical. And we all need the benefit that machine learning for all the types up to the end data science. We all need the benefits that they can bring to every single use case, but only if it can really be operationalized at scale, accurate and in real time. And the power of Vertica is, of course, how we're able to bring so many of these things together. Let me talk a little bit more about some of these trends. So one of the first industry trends that we've all been following probably now for over the last decade, is Hadoop and specifically HDFS. So many companies have invested, time, money, more importantly, people in leveraging the opportunity that HDFS brought to the market. HDFS is really part of a much broader storage disruption that we'll talk a little bit more about, more broadly than HDFS. But HDFS itself was really designed for petabytes of data, leveraging low cost commodity hardware and the ability to capture a wide variety of data formats, from a wide variety of data sources and applications. And I think what people really wanted, was to store that data before having to define exactly what structures they should go into. So over the last decade or so, the focus for most organizations is figuring out how to capture, store and frankly manage that data. And as a platform to do that, I think, Hadoop was pretty good. It certainly changed the way that a lot of enterprises think about their data and where it's locked up. In parallel with Hadoop, particularly over the last five years, Cloud Object Storage has also given every organization another option for collecting, storing and managing even more data. That has led to a huge growth in data storage, obviously, up on public clouds like Amazon and their S3, Google Cloud Storage and Azure Blob Storage just to name a few. And then when you consider regional and local object storage offered by cloud vendors all over the world, the explosion of that data, in leveraging this type of object storage is very real. And I think, as I mentioned, it's just part of this broader storage disruption that's been going on. But with all this growth in the data, in all these new places to put this data, every organization we talk to is facing even more challenges now around the data silo. Sure the data silos certainly getting bigger. And hopefully they're getting cheaper per bit. But as I said, the focus has really been on collecting, storing and managing the data. But between the new data lakes and many different cloud object storage combined with all sorts of data types from the complexity of managing all this, getting that business value has been very limited. This actually takes me to big bet number one for Team Vertica, which is to unify the data. Our goal, and some of the announcements we have made today plus roadmap announcements I'll share with you throughout this presentation. Our goal is to ensure that all the time, money and effort that has gone into storing that data, all the data turns into business value. So how are we going to do that? With a unified analytics platform that analyzes the data wherever it is HDFS, Cloud Object Storage, External tables in an any format ORC, Parquet, JSON, and of course, our own Native Roth Vertica format. Analyze the data in the right place in the right format, using a single unified tool. This is something that Vertica has always been committed to, and you'll see in some of our announcements today, we're just doubling down on that commitment. Let's talk a little bit more about the public cloud. This is certainly the second trend. It's the second wave maybe of data disruption with object storage. And there's a lot of advantages when it comes to public cloud. There's no question that the public clouds give rapid access to compute storage with the added benefit of eliminating data center maintenance that so many companies, want to get out of themselves. But maybe the biggest advantage that I see is the architectural innovation. The public clouds have introduced so many methodologies around how to provision quickly, separating compute and storage and really dialing-in the exact needs on demand, as you change workloads. When public clouds began, it made a lot of sense for the cloud providers and their customers to charge and pay for compute and storage in the ratio that each use case demanded. And I think you're seeing that trend, proliferate all over the place, not just up in public cloud. That architecture itself is really becoming the next generation architecture for on-premise data centers, as well. But there are a lot of concerns. I think we're all aware of them. They're out there many times for different workloads, there are higher costs. Especially if some of the workloads that are being run through analytics, which tend to run all the time. Just like some of the silo challenges that companies are facing with HDFS, data lakes and cloud storage, the public clouds have similar types of siloed challenges as well. Initially, there was a belief that they were cheaper than data centers, and when you added in all the costs, it looked that way. And again, for certain elastic workloads, that is the case. I don't think that's true across the board overall. Even to the point where a lot of the cloud vendors aren't just charging lower costs anymore. We hear from a lot of customers that they don't really want to tether themselves to any one cloud because of some of those uncertainties. Of course, security and privacy are a concern. We hear a lot of concerns with regards to cloud and even some SaaS vendors around shared data catalogs, across all the customers and not enough separation. But security concerns are out there, you can read about them. I'm not going to jump into that bandwagon. But we hear about them. And then, of course, I think one of the things we hear the most from our customers, is that each cloud stack is starting to feel even a lot more locked in than the traditional data warehouse appliance. And as everybody knows, the industry has been running away from appliances as fast as it can. And so they're not eager to get locked into another, quote, unquote, virtual appliance, if you will, up in the cloud. They really want to make sure they have flexibility in which clouds, they're going to today, tomorrow and in the future. And frankly, we hear from a lot of our customers that they're very interested in eventually mixing and matching, compute from one cloud with, say storage from another cloud, which I think is something that we'll hear a lot more about. And so for us, that's why we've got our big bet number two. we love the cloud. We love the public cloud. We love the private clouds on-premise, and other hosting providers. But our passion and commitment is for Vertica to be able to run in any of the clouds that our customers choose, and make it portable across those clouds. We have supported on-premises and all public clouds for years. And today, we have announced even more support for Vertica in Eon Mode, the deployment option that leverages the separation of compute from storage, with even more deployment choices, which I'm going to also touch more on as we go. So super excited about our big bet number two. And finally as I mentioned, for all the hype that there is around machine learning, I actually think that most importantly, this third trend that team Vertica is determined to address is the need to bring business critical, analytics, machine learning, data science projects into production. For so many years, there just wasn't enough data available to justify the investment in machine learning. Also, processing power was expensive, and storage was prohibitively expensive. But to train and score and evaluate all the different models to unlock the full power of predictive analytics was tough. Today you have those massive data volumes. You have the relatively cheap processing power and storage to make that dream a reality. And if you think about this, I mean with all the data that's available to every company, the real need is to operationalize the speed and the scale of machine learning so that these organizations can actually take advantage of it where they need to. I mean, we've seen this for years with Vertica, going back to some of the most advanced gaming companies in the early days, they were incorporating this with live data directly into their gaming experiences. Well, every organization wants to do that now. And the accuracy for clickability and real time actions are all key to separating the leaders from the rest of the pack in every industry when it comes to machine learning. But if you look at a lot of these projects, the reality is that there's a ton of buzz, there's a ton of hype spanning every acronym that you can imagine. But most companies are struggling, do the separate teams, different tools, silos and the limitation that many platforms are facing, driving, down sampling to get a small subset of the data, to try to create a model that then doesn't apply, or compromising accuracy and making it virtually impossible to replicate models, and understand decisions. And if there's one thing that we've learned when it comes to data, prescriptive data at the atomic level, being able to show end of one as we refer to it, meaning individually tailored data. No matter what it is healthcare, entertainment experiences, like gaming or other, being able to get at the granular data and make these decisions, make that scoring applies to machine learning just as much as it applies to giving somebody a next-best-offer. But the opportunity has never been greater. The need to integrate this end-to-end workflow and support the right tools without compromising on that accuracy. Think about it as no downsampling, using all the data, it really is key to machine learning success. Which should be no surprise then why the third big bet from Vertica is one that we've actually been working on for years. And we're so proud to be where we are today, helping the data disruptors across the world operationalize machine learning. This big bet has the potential to truly unlock, really the potential of machine learning. And today, we're announcing some very important new capabilities specifically focused on unifying the work being done by the data science community, with their preferred tools and platforms, and the volume of data and performance at scale, available in Vertica. Our strategy has been very consistent over the last several years. As I said in the beginning, we haven't deviated from our strategy. Of course, there's always things that we add. Most of the time, it's customer driven, it's based on what our customers are asking us to do. But I think we've also done a great job, not trying to be all things to all people. Especially as these hype cycles flare up around us, we absolutely love participating in these different areas without getting completely distracted. I mean, there's a variety of query tools and data warehouses and analytics platforms in the market. We all know that. There are tools and platforms that are offered by the public cloud vendors, by other vendors that support one or two specific clouds. There are appliance vendors, who I was referring to earlier who can deliver package data warehouse offerings for private data centers. And there's a ton of popular machine learning tools, languages and other kits. But Vertica is the only advanced analytic platform that can do all this, that can bring it together. We can analyze the data wherever it is, in HDFS, S3 Object Storage, or Vertica itself. Natively we support multiple clouds on-premise deployments, And maybe most importantly, we offer that choice of deployment modes to allow our customers to choose the architecture that works for them right now. It still also gives them the option to change move, evolve over time. And Vertica is the only analytics database with end-to-end machine learning that can truly operationalize ML at scale. And I know it's a mouthful. But it is not easy to do all these things. It is one of the things that highly differentiates Vertica from the rest of the pack. It is also why our customers, all of you continue to bet on us and see the value that we are delivering and we will continue to deliver. Here's a couple of examples of some of our customers who are powered by Vertica. It's the scale of data. It's the millisecond response times. Performance and scale have always been a huge part of what we have been about, not the only thing. I think the functionality all the capabilities that we add to the platform, the ease of use, the flexibility, obviously with the deployment. But if you look at some of the numbers they are under these customers on this slide. And I've shared a lot of different stories about these customers. Which, by the way, it still amaze me every time I talk to one and I get the updates, you can see the power and the difference that Vertica is making. Equally important, if you look at a lot of these customers, they are the epitome of being able to deploy Vertica in a lot of different environments. Many of the customers on this slide are not using Vertica just on-premise or just in the cloud. They're using it in a hybrid way. They're using it in multiple different clouds. And again, we've been with them on that journey throughout, which is what has made this product and frankly, our roadmap and our vision exactly what it is. It's been quite a journey. And that journey continues now with the Vertica 10 release. The Vertica 10 release is obviously a massive release for us. But if you look back, you can see that building on that native columnar architecture that started a long time ago, obviously, with the C-Store paper. We built it to leverage that commodity hardware, because it was an architecture that was never tightly integrated with any specific underlying infrastructure. I still remember hearing the initial pitch from Mike Stonebreaker, about the vision of Vertica as a software only solution and the importance of separating the company from hardware innovation. And at the time, Mike basically said to me, "there's so much R&D in innovation that's going to happen in hardware, we shouldn't bake hardware into our solution. We should do it in software, and we'll be able to take advantage of that hardware." And that is exactly what has happened. But one of the most recent innovations that we embraced with hardware is certainly that separation of compute and storage. As I said previously, the public cloud providers offered this next generation architecture, really to ensure that they can provide the customers exactly what they needed, more compute or more storage and charge for each, respectively. The separation of compute and storage, compute from storage is a major milestone in data center architectures. If you think about it, it's really not only a public cloud innovation, though. It fundamentally redefines the next generation data architecture for on-premise and for pretty much every way people are thinking about computing today. And that goes for software too. Object storage is an example of the cost effective means for storing data. And even more importantly, separating compute from storage for analytic workloads has a lot of advantages. Including the opportunity to manage much more dynamic, flexible workloads. And more importantly, truly isolate those workloads from others. And by the way, once you start having something that can truly isolate workloads, then you can have the conversations around autonomic computing, around setting up some nodes, some compute resources on the data that won't affect any of the other data to do some things on their own, maybe some self analytics, by the system, etc. A lot of things that many of you know we've already been exploring in terms of our own system data in the product. But it was May 2018, believe it or not, it seems like a long time ago where we first announced Eon Mode and I want to make something very clear, actually about Eon mode. It's a mode, it's a deployment option for Vertica customers. And I think this is another huge benefit that we don't talk about enough. But unlike a lot of vendors in the market who will dig you and charge you for every single add-on like hit-buy, you name it. You get this with the Vertica product. If you continue to pay support and maintenance, this comes with the upgrade. This comes as part of the new release. So any customer who owns or buys Vertica has the ability to set up either an Enterprise Mode or Eon Mode, which is a question I know that comes up sometimes. Our first announcement of Eon was obviously AWS customers, including the trade desk, AT&T. Most of whom will be speaking here later at the Virtual Big Data Conference. They saw a huge opportunity. Eon Mode, not only allowed Vertica to scale elastically with that specific compute and storage that was needed, but it really dramatically simplified database operations including things like workload balancing, node recovery, compute provisioning, etc. So one of the most popular functions is that ability to isolate the workloads and really allocate those resources without negatively affecting others. And even though traditional data warehouses, including Vertica Enterprise Mode have been able to do lots of different workload isolation, it's never been as strong as Eon Mode. Well, it certainly didn't take long for our customers to see that value across the board with Eon Mode. Not just up in the cloud, in partnership with one of our most valued partners and a platinum sponsor here. Joy mentioned at the beginning. We announced Vertica Eon Mode for Pure Storage FlashBlade in September 2019. And again, just to be clear, this is not a new product, it's one Vertica with yet more deployment options. With Pure Storage, Vertica in Eon mode is not limited in any way by variable cloud, network latency. The performance is actually amazing when you take the benefits of separate and compute from storage and you run it with a Pure environment on-premise. Vertica in Eon Mode has a super smart cache layer that we call the depot. It's a big part of our secret sauce around Eon mode. And combined with the power and performance of Pure's FlashBlade, Vertica became the industry's first advanced analytics platform that actually separates compute and storage for on-premises data centers. Something that a lot of our customers are already benefiting from, and we're super excited about it. But as I said, this is a journey. We don't stop, we're not going to stop. Our customers need the flexibility of multiple public clouds. So today with Vertica 10, we're super proud and excited to announce support for Vertica in Eon Mode on Google Cloud. This gives our customers the ability to use their Vertica licenses on Amazon AWS, on-premise with Pure Storage and on Google Cloud. Now, we were talking about HDFS and a lot of our customers who have invested quite a bit in HDFS as a place, especially to store data have been pushing us to support Eon Mode with HDFS. So as part of Vertica 10, we are also announcing support for Vertica in Eon Mode using HDFS as the communal storage. Vertica's own Roth format data can be stored in HDFS, and actually the full functionality of Vertica is complete analytics, geospatial pattern matching, time series, machine learning, everything that we have in there can be applied to this data. And on the same HDFS nodes, Vertica can actually also analyze data in ORC or Parquet format, using External tables. We can also execute joins between the Roth data the External table holds, which powers a much more comprehensive view. So again, it's that flexibility to be able to support our customers, wherever they need us to support them on whatever platform, they have. Vertica 10 gives us a lot more ways that we can deploy Eon Mode in various environments for our customers. It allows them to take advantage of Vertica in Eon Mode and the power that it brings with that separation, with that workload isolation, to whichever platform they are most comfortable with. Now, there's a lot that has come in Vertica 10. I'm definitely not going to be able to cover everything. But we also introduced complex types as an example. And complex data types fit very well into Eon as well in this separation. They significantly reduce the data pipeline, the cost of moving data between those, a much better support for unstructured data, which a lot of our customers have mixed with structured data, of course, and they leverage a lot of columnar execution that Vertica provides. So you get complex data types in Vertica now, a lot more data, stronger performance. It goes great with the announcement that we made with the broader Eon Mode. Let's talk a little bit more about machine learning. We've been actually doing work in and around machine learning with various extra regressions and a whole bunch of other algorithms for several years. We saw the huge advantage that MPP offered, not just as a sequel engine as a database, but for ML as well. Didn't take as long to realize that there's a lot more to operationalizing machine learning than just those algorithms. It's data preparation, it's that model trade training. It's the scoring, the shaping, the evaluation. That is so much of what machine learning and frankly, data science is about. You do know, everybody always wants to jump to the sexy algorithm and we handle those tasks very, very well. It makes Vertica a terrific platform to do that. A lot of work in data science and machine learning is done in other tools. I had mentioned that there's just so many tools out there. We want people to be able to take advantage of all that. We never believed we were going to be the best algorithm company or come up with the best models for people to use. So with Vertica 10, we support PMML. We can import now and export PMML models. It's a huge step for us around that operationalizing machine learning projects for our customers. Allowing the models to get built outside of Vertica yet be imported in and then applying to that full scale of data with all the performance that you would expect from Vertica. We also are more tightly integrating with Python. As many of you know, we've been doing a lot of open source projects with the community driven by many of our customers, like Uber. And so now with Python we've integrated with TensorFlow, allowing data scientists to build models in their preferred language, to take advantage of TensorFlow. But again, to store and deploy those models at scale with Vertica. I think both these announcements are proof of our big bet number three, and really our commitment to supporting innovation throughout the community by operationalizing ML with that accuracy, performance and scale of Vertica for our customers. Again, there's a lot of steps when it comes to the workflow of machine learning. These are some of them that you can see on the slide, and it's definitely not linear either. We see this as a circle. And companies that do it, well just continue to learn, they continue to rescore, they continue to redeploy and they want to operationalize all that within a single platform that can take advantage of all those capabilities. And that is the platform, with a very robust ecosystem that Vertica has always been committed to as an organization and will continue to be. This graphic, many of you have seen it evolve over the years. Frankly, if we put everything and everyone on here wouldn't fit on a slide. But it will absolutely continue to evolve and grow as we support our customers, where they need the support most. So, again, being able to deploy everywhere, being able to take advantage of Vertica, not just as a business analyst or a business user, but as a data scientists or as an operational or BI person. We want Vertica to be leveraged and used by the broader organization. So I think it's fair to say and I encourage everybody to learn more about Vertica 10, because I'm just highlighting some of the bigger aspects of it. But we talked about those three market trends. The need to unify the silos, the need for hybrid multiple cloud deployment options, the need to operationalize business critical machine learning projects. Vertica 10 has absolutely delivered on those. But again, we are not going to stop. It is our job not to, and this is how Team Vertica thrives. I always joke that the next release is the best release. And, of course, even after Vertica 10, that is also true, although Vertica 10 is pretty awesome. But, you know, from the first line of code, we've always been focused on performance and scale, right. And like any really strong data platform, the execution engine, the optimizer and the execution engine are the two core pieces of that. Beyond Vertica 10, some of the big things that we're already working on, next generation execution engine. We're already actually seeing incredible early performance from this. And this is just one example, of how important it is for an organization like Vertica to constantly go back and re-innovate. Every single release, we do the sit ups and crunches, our performance and scale. How do we improve? And there's so many parts of the core server, there's so many parts of our broader ecosystem. We are constantly looking at coverages of how we can go back to all the code lines that we have, and make them better in the current environment. And it's not an easy thing to do when you're doing that, and you're also expanding in the environment that we are expanding into to take advantage of the different deployments, which is a great segue to this slide. Because if you think about today, we're obviously already available with Eon Mode and Amazon, AWS and Pure and actually MinIO as well. As I talked about in Vertica 10 we're adding Google and HDFS. And coming next, obviously, Microsoft Azure, Alibaba cloud. So being able to expand into more of these environments is really important for the Vertica team and how we go forward. And it's not just running in these clouds, for us, we want it to be a SaaS like experience in all these clouds. We want you to be able to deploy Vertica in 15 minutes or less on these clouds. You can also consume Vertica, in a lot of different ways, on these clouds. As an example, in Amazon Vertica by the Hour. So for us, it's not just about running, it's about taking advantage of the ecosystems that all these cloud providers offer, and really optimizing the Vertica experience as part of them. Optimization, around automation, around self service capabilities, extending our management console, we now have products that like the Vertica Advisor Tool that our Customer Success Team has created to actually use our own smarts in Vertica. To take data from customers that give it to us and help them tune automatically their environment. You can imagine that we're taking that to the next level, in a lot of different endeavors that we're doing around how Vertica as a product can actually be smarter because we all know that simplicity is key. There just aren't enough people in the world who are good at managing data and taking it to the next level. And of course, other things that we all hear about, whether it's Kubernetes and containerization. You can imagine that that probably works very well with the Eon Mode and separating compute and storage. But innovation happens everywhere. We innovate around our community documentation. Many of you have taken advantage of the Vertica Academy. The numbers there are through the roof in terms of the number of people coming in and certifying on it. So there's a lot of things that are within the core products. There's a lot of activity and action beyond the core products that we're taking advantage of. And let's not forget why we're here, right? It's easy to talk about a platform, a data platform, it's easy to jump into all the functionality, the analytics, the flexibility, how we can offer it. But at the end of the day, somebody, a person, she's got to take advantage of this data, she's got to be able to take this data and use this information to make a critical business decision. And that doesn't happen unless we explore lots of different and frankly, new ways to get that predictive analytics UI and interface beyond just the standard BI tools in front of her at the right time. And so there's a lot of activity, I'll tease you with that going on in this organization right now about how we can do that and deliver that for our customers. We're in a great position to be able to see exactly how this data is consumed and used and start with this core platform that we have to go out. Look, I know, the plan wasn't to do this as a virtual BDC. But I really appreciate you tuning in. Really appreciate your support. I think if there's any silver lining to us, maybe not being able to do this in person, it's the fact that the reach has actually gone significantly higher than what we would have been able to do in person in Boston. We're certainly looking forward to doing a Big Data Conference in the future. But if I could leave you with anything, know this, since that first release for Vertica, and our very first customers, we have been very consistent. We respect all the innovation around us, whether it's open source or not. We understand the market trends. We embrace those new ideas and technologies and for us true north, and the most important thing is what does our customer need to do? What problem are they trying to solve? And how do we use the advantages that we have without disrupting our customers? But knowing that you depend on us to deliver that unified analytics strategy, it will deliver that performance of scale, not only today, but tomorrow and for years to come. We've added a lot of great features to Vertica. I think we've said no to a lot of things, frankly, that we just knew we wouldn't be the best company to deliver. When we say we're going to do things we do them. Vertica 10 is a perfect example of so many of those things that we from you, our customers have heard loud and clear, and we have delivered. I am incredibly proud of this team across the board. I think the culture of Vertica, a customer first culture, jumping in to help our customers win no matter what is also something that sets us massively apart. I hear horror stories about support experiences with other organizations. And people always seem to be amazed at Team Vertica's willingness to jump in or their aptitude for certain technical capabilities or understanding the business. And I think sometimes we take that for granted. But that is the team that we have as Team Vertica. We are incredibly excited about Vertica 10. I think you're going to love the Virtual Big Data Conference this year. I encourage you to tune in. Maybe one other benefit is I know some people were worried about not being able to see different sessions because they were going to overlap with each other well now, even if you can't do it live, you'll be able to do those sessions on demand. Please enjoy the Vertica Big Data Conference here in 2020. Please you and your families and your co-workers be safe during these times. I know we will get through it. And analytics is probably going to help with a lot of that and we already know it is helping in many different ways. So believe in the data, believe in data's ability to change the world for the better. And thank you for your time. And with that, I am delighted to now introduce Micro Focus CEO Stephen Murdoch to the Vertica Big Data Virtual Conference. Thank you Stephen. >> Stephen: Hi, everyone, my name is Stephen Murdoch. I have the pleasure and privilege of being the Chief Executive Officer here at Micro Focus. Please let me add my welcome to the Big Data Conference. And also my thanks for your support, as we've had to pivot to this being virtual rather than a physical conference. Its amazing how quickly we all reset to a new normal. I certainly didn't expect to be addressing you from my study. Vertica is an incredibly important part of Micro Focus family. Is key to our goal of trying to enable and help customers become much more data driven across all of their IT operations. Vertica 10 is a huge step forward, we believe. It allows for multi-cloud innovation, genuinely hybrid deployments, begin to leverage machine learning properly in the enterprise, and also allows the opportunity to unify currently siloed lakes of information. We operate in a very noisy, very competitive market, and there are people, who are in that market who can do some of those things. The reason we are so excited about Vertica is we genuinely believe that we are the best at doing all of those things. And that's why we've announced publicly, you're under executing internally, incremental investment into Vertica. That investments targeted at accelerating the roadmaps that already exist. And getting that innovation into your hands faster. This idea is speed is key. It's not a question of if companies have to become data driven organizations, it's a question of when. So that speed now is really important. And that's why we believe that the Big Data Conference gives a great opportunity for you to accelerate your own plans. You will have the opportunity to talk to some of our best architects, some of the best development brains that we have. But more importantly, you'll also get to hear from some of our phenomenal Roth Data customers. You'll hear from Uber, from the Trade Desk, from Philips, and from AT&T, as well as many many others. And just hearing how those customers are using the power of Vertica to accelerate their own, I think is the highlight. And I encourage you to use this opportunity to its full. Let me close by, again saying thank you, we genuinely hope that you get as much from this virtual conference as you could have from a physical conference. And we look forward to your engagement, and we look forward to hearing your feedback. With that, thank you very much. >> Joy: Thank you so much, Stephen, for joining us for the Vertica Big Data Conference. Your support and enthusiasm for Vertica is so clear, and it makes a big difference. Now, I'm delighted to introduce Amy Fowler, the VP of Strategy and Solutions for FlashBlade at Pure Storage, who was one of our BDC Platinum Sponsors, and one of our most valued partners. It was a proud moment for me, when we announced Vertica in Eon mode for Pure Storage FlashBlade and we became the first analytics data warehouse that separates compute from storage for on-premise data centers. Thank you so much, Amy, for joining us. Let's get started. >> Amy: Well, thank you, Joy so much for having us. And thank you all for joining us today, virtually, as we may all be. So, as we just heard from Colin Mahony, there are some really interesting trends that are happening right now in the big data analytics market. From the end of the Hadoop hype cycle, to the new cloud reality, and even the opportunity to help the many data science and machine learning projects move from labs to production. So let's talk about these trends in the context of infrastructure. And in particular, look at why a modern storage platform is relevant as organizations take on the challenges and opportunities associated with these trends. The answer is the Hadoop hype cycles left a lot of data in HDFS data lakes, or reservoirs or swamps depending upon the level of the data hygiene. But without the ability to get the value that was promised from Hadoop as a platform rather than a distributed file store. And when we combine that data with the massive volume of data in Cloud Object Storage, we find ourselves with a lot of data and a lot of silos, but without a way to unify that data and find value in it. Now when you look at the infrastructure data lakes are traditionally built on, it is often direct attached storage or data. The approach that Hadoop took when it entered the market was primarily bound by the limits of networking and storage technologies. One gig ethernet and slower spinning disk. But today, those barriers do not exist. And all FlashStorage has fundamentally transformed how data is accessed, managed and leveraged. The need for local data storage for significant volumes of data has been largely mitigated by the performance increases afforded by all Flash. At the same time, organizations can achieve superior economies of scale with that segregation of compute and storage. With compute and storage, you don't always scale in lockstep. Would you want to add an engine to the train every time you add another boxcar? Probably not. But from a Pure Storage perspective, FlashBlade is uniquely architected to allow customers to achieve better resource utilization for compute and storage, while at the same time, reducing complexity that has arisen from the siloed nature of the original big data solutions. The second and equally important recent trend we see is something I'll call cloud reality. The public clouds made a lot of promises and some of those promises were delivered. But cloud economics, especially usage based and elastic scaling, without the control that many companies need to manage the financial impact is causing a lot of issues. In addition, the risk of vendor lock-in from data egress, charges, to integrated software stacks that can't be moved or deployed on-premise is causing a lot of organizations to back off the all the way non-cloud strategy, and move toward hybrid deployments. Which is kind of funny in a way because it wasn't that long ago that there was a lot of talk about no more data centers. And for example, one large retailer, I won't name them, but I'll admit they are my favorites. They several years ago told us they were completely done with on-prem storage infrastructure, because they were going 100% to the cloud. But they just deployed FlashBlade for their data pipelines, because they need predictable performance at scale. And the all cloud TCO just didn't add up. Now, that being said, well, there are certainly challenges with the public cloud. It has also brought some things to the table that we see most organizations wanting. First of all, in a lot of cases applications have been built to leverage object storage platforms like S3. So they need that object protocol, but they may also need it to be fast. And the said object may be oxymoron only a few years ago, and this is an area of the market where Pure and FlashBlade have really taken a leadership position. Second, regardless of where the data is physically stored, organizations want the best elements of a cloud experience. And for us, that means two main things. Number one is simplicity and ease of use. If you need a bunch of storage experts to run the system, that should be considered a bug. The other big one is the consumption model. The ability to pay for what you need when you need it, and seamlessly grow your environment over time totally nondestructively. This is actually pretty huge and something that a lot of vendors try to solve for with finance programs. But no finance program can address the pain of a forklift upgrade, when you need to move to next gen hardware. To scale nondestructively over long periods of time, five to 10 years plus is a crucial architectural decisions need to be made at the outset. Plus, you need the ability to pay as you use it. And we offer something for FlashBlade called Pure as a Service, which delivers exactly that. The third cloud characteristic that many organizations want is the option for hybrid. Even if that is just a DR site in the cloud. In our case, that means supporting appplication of S3, at the AWS. And the final trend, which to me represents the biggest opportunity for all of us, is the need to help the many data science and machine learning projects move from labs to production. This means bringing all the machine learning functions and model training to the data, rather than moving samples or segments of data to separate platforms. As we all know, machine learning needs a ton of data for accuracy. And there is just too much data to retrieve from the cloud for every training job. At the same time, predictive analytics without accuracy is not going to deliver the business advantage that everyone is seeking. You can kind of visualize data analytics as it is traditionally deployed as being on a continuum. With that thing, we've been doing the longest, data warehousing on one end, and AI on the other end. But the way this manifests in most environments is a series of silos that get built up. So data is duplicated across all kinds of bespoke analytics and AI, environments and infrastructure. This creates an expensive and complex environment. So historically, there was no other way to do it because some level of performance is always table stakes. And each of these parts of the data pipeline has a different workload profile. A single platform to deliver on the multi dimensional performances, diverse set of applications required, that didn't exist three years ago. And that's why the application vendors pointed you towards bespoke things like DAS environments that we talked about earlier. And the fact that better options exists today is why we're seeing them move towards supporting this disaggregation of compute and storage. And when it comes to a platform that is a better option, one with a modern architecture that can address the diverse performance requirements of this continuum, and allow organizations to bring a model to the data instead of creating separate silos. That's exactly what FlashBlade is built for. Small files, large files, high throughput, low latency and scale to petabytes in a single namespace. And this is importantly a single rapid space is what we're focused on delivering for our customers. At Pure, we talk about it in the context of modern data experience because at the end of the day, that's what it's really all about. The experience for your teams in your organization. And together Pure Storage and Vertica have delivered that experience to a wide range of customers. From a SaaS analytics company, which uses Vertica on FlashBlade to authenticate the quality of digital media in real time, to a multinational car company, which uses Vertica on FlashBlade to make thousands of decisions per second for autonomous cars, or a healthcare organization, which uses Vertica on FlashBlade to enable healthcare providers to make real time decisions that impact lives. And I'm sure you're all looking forward to hearing from John Yavanovich from AT&T. To hear how he's been doing this with Vertica and FlashBlade as well. He's coming up soon. We have been really excited to build this partnership with Vertica. And we're proud to provide the only on-premise storage platform validated with Vertica Eon Mode. And deliver this modern data experience to our customers together. Thank you all so much for joining us today. >> Joy: Amy, thank you so much for your time and your insights. Modern infrastructure is key to modern analytics, especially as organizations leverage next generation data center architectures, and object storage for their on-premise data centers. Now, I'm delighted to introduce our last speaker in our Vertica Big Data Conference Keynote, John Yovanovich, Director of IT for AT&T. Vertica is so proud to serve AT&T, and especially proud of the harmonious impact we are having in partnership with Pure Storage. John, welcome to the Virtual Vertica BDC. >> John: Thank you joy. It's a pleasure to be here. And I'm excited to go through this presentation today. And in a unique fashion today 'cause as I was thinking through how I wanted to present the partnership that we have formed together between Pure Storage, Vertica and AT&T, I want to emphasize how well we all work together and how these three components have really driven home, my desire for a harmonious to use your word relationship. So, I'm going to move forward here and with. So here, what I'm going to do the theme of today's presentation is the Pure Vertica Symphony live at AT&T. And if anybody is a Westworld fan, you can appreciate the sheet music on the right hand side. What we're going to what I'm going to highlight here is in a musical fashion, is how we at AT&T leverage these technologies to save money to deliver a more efficient platform, and to actually just to make our customers happier overall. So as we look back, and back as early as just maybe a few years ago here at AT&T, I realized that we had many musicians to help the company. Or maybe you might want to call them data scientists, or data analysts. For the theme we'll stay with musicians. None of them were singing or playing from the same hymn book or sheet music. And so what we had was many organizations chasing a similar dream, but not exactly the same dream. And, best way to describe that is and I think with a lot of people this might resonate in your organizations. How many organizations are chasing a customer 360 view in your company? Well, I can tell you that I have at least four in my company. And I'm sure there are many that I don't know of. That is our problem because what we see is a repetitive sourcing of data. We see a repetitive copying of data. And there's just so much money to be spent. This is where I asked Pure Storage and Vertica to help me solve that problem with their technologies. What I also noticed was that there was no coordination between these departments. In fact, if you look here, nobody really wants to play with finance. Sales, marketing and care, sure that you all copied each other's data. But they actually didn't communicate with each other as they were copying the data. So the data became replicated and out of sync. This is a challenge throughout, not just my company, but all companies across the world. And that is, the more we replicate the data, the more problems we have at chasing or conquering the goal of single version of truth. In fact, I kid that I think that AT&T, we actually have adopted the multiple versions of truth, techno theory, which is not where we want to be, but this is where we are. But we are conquering that with the synergies between Pure Storage and Vertica. This is what it leaves us with. And this is where we are challenged and that if each one of our siloed business units had their own stories, their own dedicated stories, and some of them had more money than others so they bought more storage. Some of them anticipating storing more data, and then they really did. Others are running out of space, but can't put anymore because their bodies aren't been replenished. So if you look at it from this side view here, we have a limited amount of compute or fixed compute dedicated to each one of these silos. And that's because of the, wanting to own your own. And the other part is that you are limited or wasting space, depending on where you are in the organization. So there were the synergies aren't just about the data, but actually the compute and the storage. And I wanted to tackle that challenge as well. So I was tackling the data. I was tackling the storage, and I was tackling the compute all at the same time. So my ask across the company was can we just please play together okay. And to do that, I knew that I wasn't going to tackle this by getting everybody in the same room and getting them to agree that we needed one account table, because they will argue about whose account table is the best account table. But I knew that if I brought the account tables together, they would soon see that they had so much redundancy that I can now start retiring data sources. I also knew that if I brought all the compute together, that they would all be happy. But I didn't want them to tackle across tackle each other. And in fact that was one of the things that all business units really enjoy. Is they enjoy the silo of having their own compute, and more or less being able to control their own destiny. Well, Vertica's subclustering allows just that. And this is exactly what I was hoping for, and I'm glad they've brought through. And finally, how did I solve the problem of the single account table? Well when you don't have dedicated storage, and you can separate compute and storage as Vertica in Eon Mode does. And we store the data on FlashBlades, which you see on the left and right hand side, of our container, which I can describe in a moment. Okay, so what we have here, is we have a container full of compute with all the Vertica nodes sitting in the middle. Two loader, we'll call them loader subclusters, sitting on the sides, which are dedicated to just putting data onto the FlashBlades, which is sitting on both ends of the container. Now today, I have two dedicated storage or common dedicated might not be the right word, but two storage racks one on the left one on the right. And I treat them as separate storage racks. They could be one, but i created them separately for disaster recovery purposes, lashing work in case that rack were to go down. But that being said, there's no reason why I'm probably going to add a couple of them here in the future. So I can just have a, say five to 10, petabyte storage, setup, and I'll have my DR in another 'cause the DR shouldn't be in the same container. Okay, but I'll DR outside of this container. So I got them all together, I leveraged subclustering, I leveraged separate and compute. I was able to convince many of my clients that they didn't need their own account table, that they were better off having one. I eliminated, I reduced latency, I reduced our ticketing I reduce our data quality issues AKA ticketing okay. I was able to expand. What is this? As work. I was able to leverage elasticity within this cluster. As you can see, there are racks and racks of compute. We set up what we'll call the fixed capacity that each of the business units needed. And then I'm able to ramp up and release the compute that's necessary for each one of my clients based on their workloads throughout the day. And so while they compute to the right before you see that the instruments have already like, more or less, dedicated themselves towards all those are free for anybody to use. So in essence, what I have, is I have a concert hall with a lot of seats available. So if I want to run a 10 chair Symphony or 80, chairs, Symphony, I'm able to do that. And all the while, I can also do the same with my loader nodes. I can expand my loader nodes, to actually have their own Symphony or write all to themselves and not compete with any other workloads of the other clusters. What does that change for our organization? Well, it really changes the way our database administrators actually do their jobs. This has been a big transformation for them. They have actually become data conductors. Maybe you might even call them composers, which is interesting, because what I've asked them to do is morph into less technology and more workload analysis. And in doing so we're able to write auto-detect scripts, that watch the queues, watch the workloads so that we can help ramp up and trim down the cluster and subclusters as necessary. There has been an exciting transformation for our DBAs, who I need to now classify as something maybe like DCAs. I don't know, I have to work with HR on that. But I think it's an exciting future for their careers. And if we bring it all together, If we bring it all together, and then our clusters, start looking like this. Where everything is moving in harmonious, we have lots of seats open for extra musicians. And we are able to emulate a cloud experience on-prem. And so, I want you to sit back and enjoy the Pure Vertica Symphony live at AT&T. (soft music) >> Joy: Thank you so much, John, for an informative and very creative look at the benefits that AT&T is getting from its Pure Vertica symphony. I do really like the idea of engaging HR to change the title to Data Conductor. That's fantastic. I've always believed that music brings people together. And now it's clear that analytics at AT&T is part of that musical advantage. So, now it's time for a short break. And we'll be back for our breakout sessions, beginning at 12 pm Eastern Daylight Time. We have some really exciting sessions planned later today. And then again, as you can see on Wednesday. Now because all of you are already logged in and listening to this keynote, you already know the steps to continue to participate in the sessions that are listed here and on the previous slide. In addition, everyone received an email yesterday, today, and you'll get another one tomorrow, outlining the simple steps to register, login and choose your session. If you have any questions, check out the emails or go to www.vertica.com/bdc2020 for the logistics information. There are a lot of choices and that's always a good thing. Don't worry if you want to attend one or more or can't listen to these live sessions due to your timezone. All the sessions, including the Q&A sections will be available on demand and everyone will have access to the recordings as well as even more pre-recorded sessions that we'll post to the BDC website. Now I do want to leave you with two other important sites. First, our Vertica Academy. Vertica Academy is available to everyone. And there's a variety of very technical, self-paced, on-demand training, virtual instructor-led workshops, and Vertica Essentials Certification. And it's all free. Because we believe that Vertica expertise, helps everyone accelerate their Vertica projects and the advantage that those projects deliver. Now, if you have questions or want to engage with our Vertica engineering team now, we're waiting for you on the Vertica forum. We'll answer any questions or discuss any ideas that you might have. Thank you again for joining the Vertica Big Data Conference Keynote Session. Enjoy the rest of the BDC because there's a lot more to come

>>Live from Denver, Colorado. It's the cube covering com vault go 2019 brought to you by Combolt. >>Hey, welcome back to the cube at Lisa Martin with Steve men and men and we are coming to you alive from combo go 19 please to welcome to the cube, a gent from Microsoft Azure. We've got Ben call principal program manager. Ben, welcome. Thank you. Thanks for having me on. Thanks for coming on. So Microsoft combo, what's going on with the partnership? >>They wouldn't have have great storage pond is in data management space. We've been working with Convult for 20 years now in Microsoft and and they've been working with us on Azure for that as long as I can remember not being on that the Azure business for about seven years now. So just a long time in cloud terms like dog ears and it's sort of, they've been doing a huge amount there around getting customer data into the cloud, reducing costs, getting more resiliency and then also letting them do more with the data. So they're a pretty good partner to have and they make it much easy for their customers to to go and leverage cloud. >> So Ben, you know, in my career I've had lots of interactions with the Microsoft storage team. Things have changed a little bit when you're now talking about Azure compared to more, it was the interaction with the operating system or the business suite at had. >>So maybe bring us up to date as those people that might not have followed where kind of the storage positioning inside of Microsoft is now that when we talk about Azure and your title. Yeah, we, we sort of can just, just briefly, we worked very heavily with our own premises brethren, they are actually inside the O team is inside of the Azure engineering old male, which is kind of funny, but we do a load of things there. If he started looking at, firstly on that, that hybrid side, we have things like Azure files. It's a highly resilient as a service SMB NFS file Shafter a hundred terabytes, but that interacts directly with windows server to give you Azure file sync. So there is sort of synergies there as well. What I'm doing personally, my team, we work on scale storage. The big thing we have in there is owl is out blood storage technology, which really is the underpinning technology fault. >>Preapproval storage and Azure, which is an including our SAS offerings, which are hosted on Azure too. So disc is on blood storage of files on blood storage. You look at Xbox live, all these kind of stuff is a customer to us. So we build that out and we were doing work there and that's, that's really, really interesting. And how we do it. And that's not looking at going, we're gonna buy some compute, we're going to buy some storage, we're going to build it out, we're going to run windows or hyper V or maybe VM-ware with hoc with windows running on the VMware, whatever else. This is more a story about we're gonna provide you storage as a service. You didn't get a minimum of like 11 nines at your ability. And and be able to have that scale to petabytes of capacity in one logical namespace and give you multiple gigabytes, double digit gigabytes of throughput to that storage. >>And now we're even that about to multiple protocols. So rest API century. Today we've got Azure stack storage, EU API, she can go and use, but we give you that consistency of the actual backend storage and the objects and the data available via more than just one protocol. You can go and access that via HDFS API. We talk about data lakes all the time. For us, our blood storage is a data Lake. We turn on hierarchal namespace and you can go and access that via other protocols like as I mentioned HDFS as well. So that is a big story about what we want to do. We want to make that data available at crazy scale, have no limits in the end to the capacity or throughput or performance and over any protocol. That's kind of our lawn on the Hill about what we want to get to. >>And we've been talking to the Combolt team about some of the solutions that they are putting in the cloud. The new offering metallic that came out. They said if my customer has Azure storage or storage from that other cloud provider, you could just go ahead and use that. Maybe how familiar and how much I know you've been having about run metallic. >> We were working, we work pretty tightly with the product team over Convolt around this and my team as well around how do we design and how do we make it work the best and we're going to continue working to optimize as they get to beyond initial launch to go, wow, we've got data sets we we can analyze. We knew how to, we wanted out of tune it. Now really we love the solution particularly more because you know the default if you don't select the storage type where you want to go, you will run on Azure. >>So really sort of be cued off to the relationship there. They chose us as a first place we'll go to, but they've also done the choice for customers. So some customers may want to take it to another cloud. That's fine. It's reasonable. I mean we totally understand it's going to be a multicloud world and that's a reality for any large company. Our goal is to make sure we're growing faster than the competitors, not to knock out the competitors altogether because that just won't happen. So they've got that ability to go and, yeah, Hey, we'll use Azure as default because they feel we're offering the best support and the best solution there. But then if they have that customer, same customer wants to turn around and use a competitor of ours, fine as well. And I see people talking about that today where they may want to mitigate risks and say, I'm going to do, I'm doing off office three, six five on a, taken off this three 65 backup. It's cool. You use metallic, it'll take it maybe to a different region in Asia and they're backing up. They still going, well, I'm still all in on Microsoft. They may want to take it to another cloud or even take it back to on premise. So that does happen too because just in case of that moment we can get that data back in a different location. Something >>so metallic talking about that is this new venture is right. It's a Convolt venture and saw that the other day and thought that's interesting. So we dug into it a little bit yesterday and it's like a startup operating within a 20 year old company, which is very interesting. Not just from an incumbent customer perspective, but an incumbent partner perspective. How have you seen over the last few years and particularly bad in the last nine months with big leadership and GTM changes for condo? How has the partnership with Microsoft evolved as a result of those changes? >>Um, it's always been interesting. I guess when you start looking at adventure and everything seems to, things change a little bit. Priorities may change just to be fair, but we've had that tight relationship for a long time and a relationship level and an exec leadership level, nothing's really changed. But in the way they're building this platform, we, we sit down out of my team at the Azure engineering group and we'll sit down and do things like ideations. Like here's where we see gaps in the markets, here's what we believe could happen. And look back in July, we had inspire, which is our partner conference in Las Vegas and we sat down with their OT, our OT in a room, we'll talking about these kinds of things. And this is I think about two months after they may have started the initial development metallic from what I understand, but we're talking about exactly what they're doing with metallic offered as a service in Azure as, Hey, how about we do this? So we think it's really cool. It opens up a new market to convert I think too. I mean they're so strong in the enterprise, but they don't do much in the smaller businesses because with the full feature product, it also has inherent complexibility complexity around it. So by doing metallic, is it click, click, next done thing. They really opening I think new markets to them and also to us as a partner. >>I was going to add, you know, kind of click on that because they developed this very quickly. This is something that I think what student were here yesterday, metallic was kind of conceived, designed, built in about six months. So in terms of like acceleration, that's kind of a new area for Combolt. >>Yeah, and I think, I think they're really embracing the fact about let's release our code in production for, for products which are sort of getting the, getting to the, Hey, the product is at the viable stage now, not minimum viable, viable, let's release in production, let's find out how customers are using it and then let's keep optimizing and doing that constant iteration, taking that dev ops approach to let's get it out there, let's get it launched, and then let's do these small batches of changes based on customer need, based on tele telemetry. We can actually get in. We can't get the telemetry without having customers. So that's how it's going to keep working. So I think this initial product we see today, it's just going to keep evolving and improving as they get more data, as they get more information, more feedback, which is exactly what we want to see. >>Well, what will come to the cloud air or something you've been living in for a number of years. Ben, I'd love to hear you've been meeting with customers, they've been asking you questions, gives us some of the, you know, some of the things that, what's top of mind for some of the customers? What kinds of things did they come into Microsoft, Dawn, and how's that all fit together? >>There's many different conferences of interrelate, many different conversations and there'll be, we'll go from talking about, you know, Python machine learning or AI fits in PowerPoint. >>Yeah. >>It's a things like, you know, when are we gonna do incremental snapshots from the manage disks, get into the weeds on very infrastructure centric stuff. We're seeing range of conversations there. The big thing I think I see, keep seeing people call out and make assumptions of is that they're not going to be relevant because cloud, I don't know cloud yet. I don't know this whole coup cube thing, containers, I don't really understand that as well as I think I need to. And an AI, Oh my gosh, what do we even do there? Cause everyone's throwing the words and terms around. But to be honest, I think would still really evident is cloud is still is tiny fraction of enterprise workloads. So let's be honest, it's growing at a huge rate because it is that small fraction. So again, there's plenty of time for people to learn but they shouldn't go and try. >>And so it's not like you go and learn everything in the technology stack from networking to development to database management to, to running a data set of power and cooling. You learn the things that are applicable to what you're trying to do. And the same thing goes to cloud. Any of these technologies go and look at what you need to build for your business. Take it that step and then go and find out the details and levels you want to know. And as someone who's been on Azure for, like I said, almost seven years, which is crazy long. That was, that was literally like being in a startup instead of Microsoft when I joined and I wasn't sure if I wanted to join a licensing company. It's been very evident to me. I will not say I'm an Azure expert and I've been seven years in the platform. >>There are too many things for for me to be an expert in everything on, and I think people sort of just have to realize that anyone's saying that it's bravado. Nothing else. Oh, people. The goal is Microsoft as a platform provider. Hopefully you've got the software and the solution does make a lot of this easier for the customer, so hopefully they shouldn't need to become a Coobernetti's expert because it's baked into your platform. They shouldn't have to worry about some of these offerings because it's SAS. Most customers are there. Some things you need to learn between going from exchange to go into Oh three 65 absolutely. There's some nuances and things like that, but once you get over that initial hurdle, it should be a little easier. I think it's right and I think going back to that, sort of going back to bear principles going, what is the highest level of distraction that's viable for your business or that application or this workload has to always be done with everything. If it's like, well, class, not even viable, running on premises, don't, don't need to apologize for not running in cloud. If I as this, what's happening for you because of security, because of application architecture, run it that way. Don't feel the need and the pressure to have to push it that way. I think too many people get caught up in this shiny stuff up here, which is what you know 1% of people are doing versus the other 99% which is still happening in a lot of the areas we work and have challenges in today. >>That's a great point that you bring up because there is all the buzz words, right? AI, machine learning cloud. You've got to be cloud ready. You've got to be data-driven to customer. To your point going, I just need to make sure that what we have set up for our business is going to allow our business one to remain relevant, but to also be able to harness the power of the data that they have to extract new opportunities, new insights, and not get caught up with, shoot, should we be using automation? Should we be using AI? Everybody's talking about it. I liked that you brought up and I find it very respectfully, he said, Hey, I'm not an Azure expert. You'd been there seven, seven dog years like you said. And I think that's what customers probably gained confidence in is hearing the folks like you that they look to for that guidance and that leadership saying, no, I don't know everything to know. But giving them the confidence that their tribe, they're trusting you with that data and also helping look, trusting you to help them make the right decisions for their business. >>Yeah, and that's, we've got to do that. I mean, I as a tech guy, it's like I've, I've loved seeing the changes. When I joined Microsoft, I, I wasn't lying. I was almost there go enough. I really want to join this company. I was going to go join a startup instead and I got asked to one stage in an interview going, why do you want to join Microsoft? We see you've never applied to, I'd never wanted to. A friend told me to come in and it's just been amazing to see those changes and I'm pretty proud on that. So when we talk about those things we're doing, I mean, I think there is no shame going, I'm just going to lift and shift machines because cloud's about flexibility. If you're doing it just on cost, probably doing it for the wrong reason. It's about that flexibility to go and do something. >>Then change within months and slowly make steps to make things better and better as you find a need as you find the ability, whatever it may be. And some of the big things that we focus on right now with customers is we've got a product called Azure advisor. It'll go until people, when one, you don't build things in a resilient manner. Hey, do you know this has not ha because of this and you can do this. It's like, great. We'll also will tell you about security vulnerabilities that maybe should a gateway here for security. Maybe you should do this or this is not patched. But the big thing of that, it also goes and tells you, Hey, you're overspending. You don't need this much. It provisions, you provision like a Ferrari, you need a, you just need a Prius. Go and run a Prius because it's going to do what you need. >>I need a paler list and that's part of that trusted suit. Getting that understanding, and it's counterintuitive, but we're now like, it's coming out of mozzarella too, which is great. But seeing these guys were dropping contracts and licenses and basically, you know, once every three years I may call the customer, Hey, how about renewal? Now, go from that to now being focused on the customer's actual success. I've focused on their growth in Azure as a platform. Our services growth, like utilization not in sales has been a huge change. It scared some people away, but it's brought a lot more people in and and that sort of counterintuitive spend less money thing actually leads in the longterm to people using more. >>Absolutely. That's definitely not the shrink wrap software company of Microsoft that I remember from the 90s yeah. might be similar to, you know, just as to get Convolt to 2019 is not the same combo that many of us know from 15 years ago. A good >>mutual friend of ours, sort of Simon and myself before I took this job, he and I sat down, we're having a beer and discussing the merits, all not Yvette go to things like that. Same with Convolt there. They're changing such such a great deal with, you know, what they're putting in the cloud, what they're doing with the data, where they're trying to achieve with things like for data management across on premises and cloud with microservices applications and stuff going, Hey, this won't work like this anymore. When you now are doing it on premises and with containers, it's pretty good to see. I'm interested to see how they take that even further to their current audience, which is product predominantly. You know the it pro, the data center admin, storage manager. >>It's funny when you talked about just the choice that customers have and those saying, aye, we shouldn't be following the trends because they're the trends. We actually interviewed a couple of hours ago, one of customers that is all on prime healthcare company and said, he's like, I want to make a sticker that says no cloud and proud and it just what there was, we don't normally hear from them. We always talk about cloud, but for a company to sit down and look at what's best for our business, whether it's, you know, FedRAMP certification challenges or HIPAA or GDPR, other compelling requirements to keep it on prem, it was just refreshing to hear this customer say, >>yeah, I mean it's just appropriate for them. You do what's right for you. I, yeah, it's no shame in any of it. It's, I mean you don't, you definitely don't get fans by it by shaming people about not doing something right. And I mean I've, I'm personally very happy to fee fee, you know, see sort of hype around things like blockchain die down a little bit. So it's a slow database and we should use it for this specific case of that shared ledger. You know, things like that where people don't have to know blockchain. Now I have to know IOT. It's like, yeah, and that hype gets people there, but it also causes a lot of anxiety and it's good to see someone actually not be ashamed of it. And they agree the ones when they do take a step and use cloud citizen may be in the business already, they're probably going to do it appropriately because have a reason, not just because we think this would be cool, right? >>Well not. And how much inherit and complexity does that bring in if somebody is really feeling pressured to follow those trends. And maybe that's when you end up with this hodgepodge of technologies that don't work well together. You're spending way more in as as business it folks are consumers, you know, consumers in their personal lives, they expect things to be accessible, visible, but also cost efficient because they have so much choice. >>Yeah, the choice choice is hard. It's just a, just the conversation I was having recently, for example, just we'll take the storage cause of where we are, right? It's like I'm running something on Azure, I'm a, I'm using Souza, I want an NFS Mount point, which is available to me in Fs. Great, perfect. what do I use as like, well you can use any one of these seven options like that, but what's the right choice? And that's the thing about being a platform can be, we give you a lot of choices, but it's still up to you or up to app hotness. It can really help the customers as well to make the most appropriate choice. And, and I, I pushed back really hard in terms of best practices and things. I hate it because again, it's making the assumption this is the best thing to do. >>It's not. It's always about, you know, what are the patterns that have worked for other people? What are the anti-patterns and what's the appropriate path for me to take? And that's actually how we're building our docs now too. So we, we keep, we keep focusing on our Azure technology and we're bringing out some of the biggest things we've done is how we manage our documentation. It's all open sourced, it's all in markdown on get hub. So you can go in and read a document from someone like myself is doing product management going, this is how to use this product and you're actually, this bit's wrong, this bit needs to be like this and you can go in yourself even now, make a change and we can go, Oh yeah and take that committed in and dual this kind of stuff in that way. So we're constantly taking those documents in that way and getting realtime feedback from customers who are using it, not just ourself in an echo chamber. >>So you get this great insight and visibility that you never had before. Well, Ben, thank you, Georgie stew and me on the queue this afternoon. Excited to hear what's coming up next for Azure. Makes appreciate your time. Thank you for steam and event. I, Lisa Martin, you're watching the cue from Convault go 19.

>>Live from Denver, Colorado. It's the cube covering com vault go 2019 brought to you by Combolt. >>Hey, welcome back to the Q but Lisa Martin with men and men and we are coming to you alive from Conn logo 19 please to welcome to the cube, a gent from Microsoft Azure. We've got Ben Nichol, principal program manager. Ben, welcome. Thank you. Thanks for having me on. Thanks for coming on. So Microsoft combo, what's going on with the partnership? >>They wouldn't have have great storage pond is in data management space. We've been working with Convolt for 20 years now in Microsoft and and they've been working with us on Azure for about as long as I can remember not being on that the Azure business RET seven years now. So just a long time in cloud terms like doggies and it sort of, they'd been doing a huge amount of their around getting customer data into the cloud, reducing costs, getting more resiliency and then also letting them do more with the data. So they were a pretty good partner to have and they make it much easy for their customers to to go and leverage cloud. So Ben, you know, in my career I've had lots of interactions with the Microsoft storage team. Things have changed a little bit when you're now talking about Azure compared to, you know, more. >>It was the interaction with the operating system or the business suite had. So maybe bring us up to date as those people that might not have followed. You know, we're kind of the storage positioning inside of Microsoft is now that when we talk about Azure and your title. Yeah, we, we sort of look and just just briefly, we worked very heavily with our on premises brethren. They actually inside the O S team is inside of the Azure engineering old male, which is kind of funny, but we do a lot of things there. If he started looking at, firstly on that hybrid side, we have things like Azure files. It's a highly resilient as a service SMB NFS file share up to a hundred terabytes but that interacts directly with windows server to give you Azure file sync. So there is sort of synergies there as well. When I'm doing personally my team, we work on scale storage. >>The big thing we have in there is Al is out blood storage technology, which really is the underpinning technology, full Priya tool storage and Azure which is including our SAS offerings which are hosted on Azure too. So disc is on blood storage, our files on blood storage, you look at Xbox live, all these kinds of stuff is a customer to us. So we build that out and we, we are doing work there and that's really, really interesting and how we do it and that's not looking at going we're going to buy some compute, we're going to buy some storage, we're going to build it out, we're going to run windows or hyper V or maybe VMware with windows running on the VMware, whatever else. This is more a story about wigging to provide you storage as a service. You didn't get a minimum of like 11 nines at your ability and and be able to have that scale to petabytes of capacity in one logical namespace and give you multiple gigabytes, double digit gigabytes of throughput to that storage. >>And now we're even moving about to model multiple protocols. So rest API century today we've got Azure stack storage, you pay API, she can go and use, but we give me that consistency of the actual back end storage and the objects and the data available via more than just one protocol. You can go and access that via HDFS API. As we talk about data lakes all the time. For us, our blood storage is a data Lake. We turn on hierarchal namespace and you can go and access that via our other protocols like as I mentioned HDFS as well. So that is a big story about what we want to do. We want to make that data available at crazy scale, have no limits in the end to the capacity or throughput or performance and over any protocol. That's kind of our line in the Hill about what we want to get to. >>And we've been talking to vault team about some of the solutions that they are putting in the cloud. The new offering metallic that came out. They said if my customer has Azure storage or storage from that other cloud provider, you could just go ahead and use that. Maybe how familiar and how much, I know you've been having a run metallic. We were working, we were pretty tightly with the product team over Convolt around this and my team as well around how do we design and how do we make it work the best and we're going to continue working to optimize as they get beyond initial launch to go, wow, we've got data sets we can analyze, we know how to, we wanted out of tune it. Now really we love the solution particularly more because the default, if you don't select the storage type where you want to go, you will run on Azure. >>So really sort of be kudos to the relationship there. They chose us as a first place we'll go to, but they've also done the choice for customers. Say some customers may want to take it to another cloud. That's fine. It's reasonable. I mean, we totally understand it's going to be a multi-cloud world and that's a reality for any large company. Our goal is to make sure we're growing faster than the competitors, not to knock out the competitors all together because that just won't happen. So they've got that ability to go and yet, Hey, we'll use Azure as default because they feel that way, offering the best support and the best solution there. But then if they have that customer, same customer wants to turn around and use a competitor, Val's fine as well. And I see people talking about that today where they may want to mitigate risks and say, I'm going to do, I'm doing all of office three, six, five on a taken office, three, six, five backup. It's cool. Use metallic, it'll take it maybe to a different region in Asia and they're backing up and they still going, well I'm still all in on Microsoft. They may want to take it to another cloud or even take it back to on premises. So that does happen too because just in case of that moment we can get that data back in a different location. Something happens. >>So metallic talking about that is this new venture is right. It's a Combolt venture and saw that the other day and thought that's interesting. So we dug into it a little bit yesterday and it's like a startup operating within a 20 year old company, which is very interesting. Not just from an incumbent customer perspective, but an incumbent partner perspective. How have you seen over the last few years and particularly bad in the last nine months with big leadership and GTM changes for combo? How has the partnership with Microsoft evolved as a result of those changes? >>Um, it's always been interesting. I guess when you start looking at adventure and everything, since things change a little bit, priorities may change just to be fair, but we've had that tight relationship for a long time. At a relationship level and an exec leadership level, nothing's really changed. But in the way they're building this platform, we sit down out of my team, out of the Azure engineering group and we'll sit down and do things like ideations, like here's where we see gaps in the markets, here's what we believe could happen. And look back in July, we had inspire, which is our partner conference in Las Vegas. When we sat down with their OT, our OT in a room, we'll talking about these kinds of things and this is I think about two months after they may have started the initial development metallic from what I understand, but we will talking about exactly what they're doing with metallic offered as a service in Azure is, Hey, how bout we do this? So we think it's really cool. It opens up a new market to Convolt I think too. I mean they're so strong in the enterprise, but they don't do much in smaller businesses because with a full feature product, it also has inherent complexibility complexity around it. So by doing metallic, is it click, click, next done thing. They're really opening, I think, new markets to them and also to us as a partner. >>I was going to ask, you know, kind of click on that because they developed this very quickly. This is something that I think what student were here yesterday, metallic was kind of conceived design built in about six months. So in terms of like acceleration, that's kind of a new area for Combalt. >>Yeah, and I think, I think they're really embracing the fact about um, let's release our code in production for products, which are sort of getting, getting to the, Hey that product is at the viable stage now, not minimum viable, viable, let's release in production, let's find out how customers are using Atlin, let's keep optimizing and doing that constant iteration, taking that dev ops approach to let's get it out there, let's get it launched. And then let's do these small batches of changes based on customer need, based on tele telemetry. We can actually get in. We can't get the telemetry without having customers. So that's how it's going to keep working. So I think this initial product we see today, it's just going to keep evolving and improving as they get more data, as they get more information, more feedback. Which is exactly what we want to see. >>Well, what will come to the cloud air or something you've been living in for a number of years. Ben, I'd love to hear you've been meeting with customers. They've been asking you questions, gives us some of the, you know, some of the things that, what's top of mind for some of the customers? What kinds of things did they come into Microsoft, Dawn, and how's that all fit together? >>There's many different conferences of interrelate, many different conversations and they'll, we will go from talking about, you know, Python machine learning or AI PowerPoint. >>Yeah. >>It's a things like, you know, when are we going to do incremental snapshots from a manage disks? Get into the weeds on very infrastructure century staff. We're seeing range of conversations there. The big thing I think I see, keep seeing people call out and make assumptions of is that they're not going to be relevant because cloud, I don't know cloud yet. I don't know this whole coup cube thing. Containers. I don't, I don't really understand that as well as I think I need to. And an AI, Oh my gosh, what do I even do there? Because everyone's throwing the words and terms around. But to be honest, I think what's still really evident is cloud is still is tiny fraction of enterprise workloads. Let's be honest, it's growing at a huge rate because it is that small fraction. So again, there's plenty of time for people to learn, but they shouldn't go and try and slip. >>It's not like you're going to learn everything in a technology stack, from networking to development to database management to, to running a data set of power and cooling. You learn the things that are applicable to what you're trying to do. And the same thing goes to cloud. Any of these technologies, go and look at what you need to build for your business. Take it to that step and then go and find out the details and levels you want to know. And as someone who's been on Azure for like a cinema seven years, which is crazy long. That was a, that was literally like being in a startup instead of Microsoft when I joined and I wasn't sure if I wanted to join a licensing company. It's been very evident to me. I will not say I'm an Azure expert and I've been seven years in the platform. >>There are too many things throughout my for me to be an expert in everything on and I think people sort of just have to realize that anyone saying that it's bravado, nothing else. The goal is Microsoft as a platform provider. Hopefully you've got the software and the solution to make a lot of this easier for the customer, so hopefully they shouldn't need to become a Kubernetes expert because it's baked into your platform. They shouldn't have to worry about some of these offerings because it's SAS. Most customers are there some things you need to learn between going from, you know, exchange to go into oath bricks, these five. Absolutely. There are some nuances and things like that, but once you get over that initial hurdle, it should be a little easier. I think it's right and I think going back to that, sort of going back to bare principles going, what is the highest level of distraction that's viable for your business or that application or this workload has to always be done with everything. >>If it's like, well, class, not even viable, run it on premises. Don't, don't need to apologize for not running in cloud. If I as is what's happening for you because of security, because of application architecture, run it that way. Don't feel the need and the pressure to have to push it that way. I think too many people get caught up in the shiny stuff up here, which is what you know 1% of people are doing versus the other 99% which is still happening in a lot of the areas we work and have challenges in today. >>That's a great point that you bring up because there is all the buzz words, right? AI, machine learning cloud. You've got to be cloud ready. You've gotta be data-driven to customer, to your point going, I just need to make sure that what we have set up for our business is going to allow our business one to remain relevant, but to also be able to harness the power of the data that they have to extract new opportunities, new insights, and not get caught up with, shoot, should we be using automation? Should we be using AI? Everybody's talking about it. I liked that you brought up and I find it very respectfully, he said, Hey, I'm not an Azure expert. You'd been there seven, seven dog years like you said. And I think that's what customers probably gained confidence in is hearing the folks like you that they look to for that guidance and that leadership saying, no, I don't know everything. To know that giving them the confidence that they're true, they're trusting you with that data and also helping trusting you to help them make the right decisions for their business. >>Yeah. And that that's, we've got to do that. I mean, I, as a tech guy, it's like I've, I've loved seeing the changes. When I joined Microsoft, I, I wasn't lying. I was almost there go inf I really want to join this company. I was going to go join a startup instead. And I got asked to one stage in an interview going, why do you want to join Microsoft? We see you've never applied to that. I never wanted to, a friend told me to come in and it's just been amazing to see those changes and I'm pretty proud on that. Um, so when we talk about, you know, those, the things we're doing, I mean I think there is no shame going, I'm just going to lift and shift machines because cloud is about flexibility. If you're doing it just on cost, probably doing it for the wrong reason, it's about that flexibility to go and do something. >>Then change within months of slowly make steps to make things better and better as you find a need as you find the ability, whatever it may be. And some of the big things that we focus on right now with customers is we've got a product called Azure advisor. It'll go until people want one. You know, you don't build things in a resilient manner. Hey, do you know this is not ha because of this and you can do this. It's like great. Also will tell you about security vulnerabilities that maybe she had a gateway here for security. Maybe you should do this or this is not patched. But the big thing is that it also goes and tells you, Hey, you're overspending. You don't need this much. It provisions, you provision like a Ferrari, you need a, you just need a Prius, go and run a Prius because it's going to do what you need and need to pay a lot less. >>And that's part of that trust. Getting that understanding. And it's counterintuitive that we're now like it's coming out of my team a lot too, which is great. But seeing these guys were dropping contracts and licenses and basically, you know, once every three years I may call the customer, Hey, how bout a renewal now go from that to now being focused on the customer's actual success and focused on their growth in Azure as a platform of our vast services growth like utilization not in sales has been a huge change. It scared some people away but it's brought a lot more people in and and that sort of counterintuitive spin less money thing actually leads in the longterm to people using more. >>Absolutely. That's definitely not the shrink wrap software company of Microsoft that I remember from the 90s yeah, very might be similar to you know, just as volt to 2019 is not the same combo, but many of us know from with 15 >>years and a good mutual friend of ours, sort of Simon and myself before I took this job, he and I sat down, we're having a beer and discussing the merits, all the not evacuate and things like that. Same with. They are changing such, such a great deal with, you know, what they're putting in the cloud, what they're doing with the data, where they're trying to achieve with things like Hedvig for data management across on premises and cloud with microservices applications and stuff going, Hey, this won't work like this anymore. When you now are doing an on premises and we containers, it's pretty good to see. I'm interested to see how they take that even further to their current audience, which is product predominantly, you know, the it pro, the data center admin, storage manager. >>It's funny when you talked about, um, just the choice that customers have and those saying I, we shouldn't be following the trends because they're the trends. We actually interviewed a couple of hours ago, one of Combolt's customers that is all on prime healthcare company and said, he's like, I want to make a secret that says no cloud and proud and it just, what that was, we don't normally hear from them. We always talk about cloud, but for a company to sit down and look at what's best for our business, whether it's, you know, FedRAMP certification challenges or HIPAA or GDPR or other compelling requirements to keep it on prem, it was just refreshing to hear this customer say, >>yeah, I mean it's, it's appropriate for the do what's right for you. I, yeah, it's no shame in any of them. It's, I mean, you don't, you definitely don't get fans by, by shaming people and not doing something right. And I mean, I, I'm personally very happy with the feet, you know, see sort of hype around things like blockchain died down a little bit. So it's a slow database unless you're using for the specific case of that shared ledger, you know, things like that where people don't have to know blockchain. Now I have to know IOT. It's like, yeah. And that hype gets people there, but it also causes a lot of anxiety and it's good to see someone actually not be ashamed of and like, and they grade the ones when they do take a step and use cloud citizen may be in the business already. They're probably going to do it appropriately because have a reason, not just because we think this would be cool. >>Well not and how much inherent and complexity does that bring in if somebody is really feeling pressured to follow those trends and maybe that's when you end up with this hodgepodge of technologies that don't work well together, you're spending way more in as as business it folks are consumers, you know, consumers in their personal lives, they expect things to be accessible, visible, but also cost efficient because they have so much choice. >>Yeah, the choice choice is hard. It's just a, just the conversation is having recently, for example, just we'll take the storage cause of where we are, right? It's like I'm running something on Azure. I'm a, I'm using Souza. I want an office Mount point, which is available to me in Fs. Great. Perfect. what do I use? It's like, well you use any one of these seven options, like what's the right choice? And that's the thing about being a platform company. We give you a lot of choices but it's still up to you or up to harness. It can really help the customers as well to make the most appropriate choice. And I pushed back really hard on terms like best practices and things. I hate it because again, it's making the assumption this is the best thing to do. It's not. It's always about, you know, what are the patterns that have worked for other people, what are the anti-patterns and the appropriate path for me to take. >>And that's actually how we're building our docs now too. So we keep, we keep focusing at our Azure technology and we're bringing out some of the biggest things we've done is how we manage our documentation. It's all open sourced. It's all in markdown on get hub. So you can go and read a document from someone like myself is doing product management going, this is how to use this product and you're actually this bits wrong. This bit needs to be like this, and you can go in yourself, even now, make a change and we can go, Oh yeah, and take that committed in and do all this kind of stuff in that way. So we're constantly taking those documents in that way, in getting real time feedback from customers who are using it, not just ourself and an echo chamber. >>So you get this great insight and visibility that you never had before. Well, Ben, thank you, Georgie stew and me on the Q this afternoon. Excited to hear what's coming up next for Azure. May appreciate your time. Thank you for streaming event. I, Lisa Martin, you're watching the cue from convo. Go 19.