(soothing music) >> Hey everyone, welcome to this event, "Build Your Cloud Center of Excellence." I'm your host, Lisa Martin. In the next 15 minutes or so my guest and I are going to be talking about redefining cloud operations, an application modernization for customers, and specifically how partners are helping to speed up that process. As you saw on our first two segments, we talked about problems enterprises are facing with cloud operations. We talked about redefining cloud operations as well to solve these problems. This segment is going to be focusing on how Hitachi Vantara's partners are really helping to speed up that process. We've got Johnson Controls here to talk about their partnership with Hitachi Vantara. Please welcome both of my guests, Prem Balasubramanian is with us, SVP and CTO Digital Solutions at Hitachi Vantara. And Suresh Mothikuru, SVP Customer Success Platform Engineering and Reliability Engineering from Johnson Controls. Gentlemen, welcome to the program, great to have you. >> Thank. >> Thank you, Lisa. >> First question is to both of you and Suresh, we'll start with you. We want to understand, you know, the cloud operations landscape is increasingly complex. We've talked a lot about that in this program. Talk to us, Suresh, about some of the biggest challenges and pin points that you faced with respect to that. >> Thank you. I think it's a great question. I mean, cloud has evolved a lot in the last 10 years. You know, when we were talking about a single cloud whether it's Azure or AWS and GCP, and that was complex enough. Now we are talking about multi-cloud and hybrid and you look at Johnson Controls, we have Azure we have AWS, we have GCP, we have Alibaba and we also support on-prem. So the architecture has become very, very complex and the complexity has grown so much that we are now thinking about whether we should be cloud native or cloud agnostic. So I think, I mean, sometimes it's hard to even explain the complexity because people think, oh, "When you go to cloud, everything is simplified." Cloud does give you a lot of simplicity, but it also really brings a lot more complexity along with it. So, and then next one is pretty important is, you know, generally when you look at cloud services, you have plenty of services that are offered within a cloud, 100, 150 services, 200 services. Even within those companies, you take AWS they might not know, an individual resource might not know about all the services we see. That's a big challenge for us as a customer to really understand each of the service that is provided in these, you know, clouds, well, doesn't matter which one that is. And the third one is pretty big, at least at the CTO the CIO, and the senior leadership level, is cost. Cost is a major factor because cloud, you know, will eat you up if you cannot manage it. If you don't have a good cloud governance process it because every minute you are in it, it's burning cash. So I think if you ask me, these are the three major things that I am facing day to day and that's where I use my partners, which I'll touch base down the line. >> Perfect, we'll talk about that. So Prem, I imagine that these problems are not unique to Johnson Controls or JCI, as you may hear us refer to it. Talk to me Prem about some of the other challenges that you're seeing within the customer landscape. >> So, yeah, I agree, Lisa, these are not very specific to JCI, but there are specific issues in JCI, right? So the way we think about these are, there is a common issue when people go to the cloud and there are very specific and unique issues for businesses, right? So JCI, and we will talk about this in the episode as we move forward. I think Suresh and his team have done some phenomenal step around how to manage this complexity. But there are customers who have a lesser complex cloud which is, they don't go to Alibaba, they don't have footprint in all three clouds. So their multi-cloud footprint could be a bit more manageable, but still struggle with a lot of the same problems around cost, around security, around talent. Talent is a big thing, right? And in Suresh's case I think it's slightly more exasperated because every cloud provider Be it AWS, JCP, or Azure brings in hundreds of services and there is nobody, including many of us, right? We learn every day, nowadays, right? It's not that there is one service integrator who knows all, while technically people can claim as a part of sales. But in reality all of us are continuing to learn in this landscape. And if you put all of this equation together with multiple clouds the complexity just starts to exponentially grow. And that's exactly what I think JCI is experiencing and Suresh's team has been experiencing, and we've been working together. But the common problems are around security talent and cost management of this, right? Those are my three things. And one last thing that I would love to say before we move away from this question is, if you think about cloud operations as a concept that's evolving over the last few years, and I have touched upon this in the previous episode as well, Lisa, right? If you take architectures, we've gone into microservices, we've gone into all these server-less architectures all the fancy things that we want. That helps us go to market faster, be more competent to as a business. But that's not simplified stuff, right? That's complicated stuff. It's a lot more distributed. Second, again, we've advanced and created more modern infrastructure because all of what we are talking is platform as a service, services on the cloud that we are consuming, right? In the same case with development we've moved into a DevOps model. We kind of click a button put some code in a repository, the code starts to run in production within a minute, everything else is automated. But then when we get to operations we are still stuck in a very old way of looking at cloud as an infrastructure, right? So you've got an infra team, you've got an app team, you've got an incident management team, you've got a soft knock, everything. But again, so Suresh can talk about this more because they are making significant strides in thinking about this as a single workload, and how do I apply engineering to go manage this? Because a lot of it is codified, right? So automation. Anyway, so that's kind of where the complexity is and how we are thinking, including JCI as a partner thinking about taming that complexity as we move forward. >> Suresh, let's talk about that taming the complexity. You guys have both done a great job of articulating the ostensible challenges that are there with cloud, especially multi-cloud environments that you're living in. But Suresh, talk about the partnership with Hitachi Vantara. How is it helping to dial down some of those inherent complexities? >> I mean, I always, you know, I think I've said this to Prem multiple times. I treat my partners as my internal, you know, employees. I look at Prem as my coworker or my peers. So the reason for that is I want Prem to have the same vested interest as a partner in my success or JCI success and vice versa, isn't it? I think that's how we operate and that's how we have been operating. And I think I would like to thank Prem and Hitachi Vantara for that really been an amazing partnership. And as he was saying, we have taken a completely holistic approach to how we want to really be in the market and play in the market to our customers. So if you look at my jacket it talks about OpenBlue platform. This is what JCI is building, that we are building this OpenBlue digital platform. And within that, my team, along with Prem's or Hitachi's, we have built what we call as Polaris. It's a technical platform where our apps can run. And this platform is automated end-to-end from a platform engineering standpoint. We stood up a platform engineering organization, a reliability engineering organization, as well as a support organization where Hitachi played a role. As I said previously, you know, for me to scale I'm not going to really have the talent and the knowledge of every function that I'm looking at. And Hitachi, not only they brought the talent but they also brought what he was talking about, Harc. You know, they have set up a lot and now we can leverage it. And they also came up with some really interesting concepts. I went and met them in India. They came up with this concept called IPL. Okay, what is that? They really challenged all their employees that's working for GCI to come up with innovative ideas to solve problems proactively, which is self-healing. You know, how you do that? So I think partners, you know, if they become really vested in your interests, they can do wonders for you. And I think in this case Hitachi is really working very well for us and in many aspects. And I'm leveraging them... You started with support, now I'm leveraging them in the automation, the platform engineering, as well as in the reliability engineering and then in even in the engineering spaces. And that like, they are my end-to-end partner right now? >> So you're really taking that holistic approach that you talked about and it sounds like it's a very collaborative two-way street partnership. Prem, I want to go back to, Suresh mentioned Harc. Talk a little bit about what Harc is and then how partners fit into Hitachi's Harc strategy. >> Great, so let me spend like a few seconds on what Harc is. Lisa, again, I know we've been using the term. Harc stands for Hitachi application reliability sectors. Now the reason we thought about Harc was, like I said in the beginning of this segment, there is an illusion from an architecture standpoint to be more modern, microservices, server-less, reactive architecture, so on and so forth. There is an illusion in your development methodology from Waterfall to agile, to DevOps to lean, agile to path program, whatever, right? Extreme program, so on and so forth. There is an evolution in the space of infrastructure from a point where you were buying these huge humongous servers and putting it in your data center to a point where people don't even see servers anymore, right? You buy it, by a click of a button you don't know the size of it. All you know is a, it's (indistinct) whatever that name means. Let's go provision it on the fly, get go, get your work done, right? When all of this is advanced when you think about operations people have been solving the problem the way they've been solving it 20 years back, right? That's the issue. And Harc was conceived exactly to fix that particular problem, to think about a modern way of operating a modern workload, right? That's exactly what Harc. So it brings together finest engineering talent. So the teams are trained in specific ways of working. We've invested and implemented some of the IP, we work with the best of the breed partner ecosystem, and I'll talk about that in a minute. And we've got these facilities in Dallas and I am talking from my office in Dallas, which is a Harc facility in the US from where we deliver for our customers. And then back in Hyderabad, we've got one more that we opened and these are facilities from where we deliver Harc services for our customers as well, right? And then we are expanding it in Japan and Portugal as we move into 23. That's kind of the plan that we are thinking through. However, that's what Harc is, Lisa, right? That's our solution to this cloud complexity problem. Right? >> Got it, and it sounds like it's going quite global, which is fantastic. So Suresh, I want to have you expand a bit on the partnership, the partner ecosystem and the role that it plays. You talked about it a little bit but what role does the partner ecosystem play in really helping JCI to dial down some of those challenges and the inherent complexities that we talked about? >> Yeah, sure. I think partners play a major role and JCI is very, very good at it. I mean, I've joined JCI 18 months ago, JCI leverages partners pretty extensively. As I said, I leverage Hitachi for my, you know, A group and the (indistinct) space and the cloud operations space, and they're my primary partner. But at the same time, we leverage many other partners. Well, you know, Accenture, SCL, and even on the tooling side we use Datadog and (indistinct). All these guys are major partners of our because the way we like to pick partners is based on our vision and where we want to go. And pick the right partner who's going to really, you know make you successful by investing their resources in you. And what I mean by that is when you have a partner, partner knows exactly what kind of skillset is needed for this customer, for them to really be successful. As I said earlier, we cannot really get all the skillset that we need, we rely on the partners and partners bring the the right skillset, they can scale. I can tell Prem tomorrow, "Hey, I need two parts by next week", and I guarantee it he's going to bring two parts to me. So they let you scale, they let you move fast. And I'm a big believer, in today's day and age, to get things done fast and be more agile. I'm not worried about failure, but for me moving fast is very, very important. And partners really do a very good job bringing that. But I think then they also really make you think, isn't it? Because one thing I like about partners they make you innovate whether they know it or not but they do because, you know, they will come and ask you questions about, "Hey, tell me why you are doing this. Can I review your architecture?" You know, and then they will try to really say I don't think this is going to work. Because they work with so many different clients, not JCI, they bring all that expertise and that's what I look from them, you know, just not, you know, do a T&M job for me. I ask you to do this go... They just bring more than that. That's how I pick my partners. And that's how, you know, Hitachi's Vantara is definitely one of a good partner from that sense because they bring a lot more innovation to the table and I appreciate about that. >> It sounds like, it sounds like a flywheel of innovation. >> Yeah. >> I love that. Last question for both of you, which we're almost out of time here, Prem, I want to go back to you. So I'm a partner, I'm planning on redefining CloudOps at my company. What are the two things you want me to remember from Hitachi Vantara's perspective? >> So before I get to that question, Lisa, the partners that we work with are slightly different from from the partners that, again, there are some similar partners. There are some different partners, right? For example, we pick and choose especially in the Harc space, we pick and choose partners that are more future focused, right? We don't care if they are huge companies or small companies. We go after companies that are future focused that are really, really nimble and can change for our customers need because it's not our need, right? When I pick partners for Harc my ultimate endeavor is to ensure, in this case because we've got (indistinct) GCI on, we are able to operate (indistinct) with the level of satisfaction above and beyond that they're expecting from us. And whatever I don't have I need to get from my partners so that I bring this solution to Suresh. As opposed to bringing a whole lot of people and making them stand in front of Suresh. So that's how I think about partners. What do I want them to do from, and we've always done this so we do workshops with our partners. We just don't go by tools. When we say we are partnering with X, Y, Z, we do workshops with them and we say, this is how we are thinking. Either you build it in your roadmap that helps us leverage you, continue to leverage you. And we do have minimal investments where we fix gaps. We're building some utilities for us to deliver the best service to our customers. And our intention is not to build a product to compete with our partner. Our intention is to just fill the wide space until they go build it into their product suite that we can then leverage it for our customers. So always think about end customers and how can we make it easy for them? Because for all the tool vendors out there seeing this and wanting to partner with Hitachi the biggest thing is tools sprawl, especially on the cloud is very real. For every problem on the cloud. I have a billion tools that are being thrown at me as Suresh if I'm putting my installation and it's not easy at all. It's so confusing. >> Yeah. >> So that's what we want. We want people to simplify that landscape for our end customers, and we are looking at partners that are thinking through the simplification not just making money. >> That makes perfect sense. There really is a very strong symbiosis it sounds like, in the partner ecosystem. And there's a lot of enablement that goes on back and forth it sounds like as well, which is really, to your point it's all about the end customers and what they're expecting. Suresh, last question for you is which is the same one, if I'm a partner what are the things that you want me to consider as I'm planning to redefine CloudOps at my company? >> I'll keep it simple. In my view, I mean, we've touched upon it in multiple facets in this interview about that, the three things. First and foremost, reliability. You know, in today's day and age my products has to be reliable, available and, you know, make sure that the customer's happy with what they're really dealing with, number one. Number two, my product has to be secure. Security is super, super important, okay? And number three, I need to really make sure my customers are getting the value so I keep my cost low. So these three is what I would focus and what I expect from my partners. >> Great advice, guys. Thank you so much for talking through this with me and really showing the audience how strong the partnership is between Hitachi Vantara and JCI. What you're doing together, we'll have to talk to you again to see where things go but we really appreciate your insights and your perspectives. Thank you. >> Thank you, Lisa. >> Thanks Lisa, thanks for having us. >> My pleasure. For my guests, I'm Lisa Martin. Thank you so much for watching. (soothing music)

(soothing music) >> Hey everyone, welcome to this event, "Build Your Cloud Center of Excellence." I'm your host, Lisa Martin. In the next 15 minutes or so my guest and I are going to be talking about redefining cloud operations, an application modernization for customers, and specifically how partners are helping to speed up that process. As you saw on our first two segments, we talked about problems enterprises are facing with cloud operations. We talked about redefining cloud operations as well to solve these problems. This segment is going to be focusing on how Hitachi Vantara's partners are really helping to speed up that process. We've got Johnson Controls here to talk about their partnership with Hitachi Vantara. Please welcome both of my guests, Prem Balasubramanian is with us, SVP and CTO Digital Solutions at Hitachi Vantara. And Suresh Mothikuru, SVP Customer Success Platform Engineering and Reliability Engineering from Johnson Controls. Gentlemen, welcome to the program, great to have you. >> Thank. >> Thank you, Lisa. >> First question is to both of you and Suresh, we'll start with you. We want to understand, you know, the cloud operations landscape is increasingly complex. We've talked a lot about that in this program. Talk to us, Suresh, about some of the biggest challenges and pin points that you faced with respect to that. >> Thank you. I think it's a great question. I mean, cloud has evolved a lot in the last 10 years. You know, when we were talking about a single cloud whether it's Azure or AWS and GCP, and that was complex enough. Now we are talking about multi-cloud and hybrid and you look at Johnson Controls, we have Azure we have AWS, we have GCP, we have Alibaba and we also support on-prem. So the architecture has become very, very complex and the complexity has grown so much that we are now thinking about whether we should be cloud native or cloud agnostic. So I think, I mean, sometimes it's hard to even explain the complexity because people think, oh, "When you go to cloud, everything is simplified." Cloud does give you a lot of simplicity, but it also really brings a lot more complexity along with it. So, and then next one is pretty important is, you know, generally when you look at cloud services, you have plenty of services that are offered within a cloud, 100, 150 services, 200 services. Even within those companies, you take AWS they might not know, an individual resource might not know about all the services we see. That's a big challenge for us as a customer to really understand each of the service that is provided in these, you know, clouds, well, doesn't matter which one that is. And the third one is pretty big, at least at the CTO the CIO, and the senior leadership level, is cost. Cost is a major factor because cloud, you know, will eat you up if you cannot manage it. If you don't have a good cloud governance process it because every minute you are in it, it's burning cash. So I think if you ask me, these are the three major things that I am facing day to day and that's where I use my partners, which I'll touch base down the line. >> Perfect, we'll talk about that. So Prem, I imagine that these problems are not unique to Johnson Controls or JCI, as you may hear us refer to it. Talk to me Prem about some of the other challenges that you're seeing within the customer landscape. >> So, yeah, I agree, Lisa, these are not very specific to JCI, but there are specific issues in JCI, right? So the way we think about these are, there is a common issue when people go to the cloud and there are very specific and unique issues for businesses, right? So JCI, and we will talk about this in the episode as we move forward. I think Suresh and his team have done some phenomenal step around how to manage this complexity. But there are customers who have a lesser complex cloud which is, they don't go to Alibaba, they don't have footprint in all three clouds. So their multi-cloud footprint could be a bit more manageable, but still struggle with a lot of the same problems around cost, around security, around talent. Talent is a big thing, right? And in Suresh's case I think it's slightly more exasperated because every cloud provider Be it AWS, JCP, or Azure brings in hundreds of services and there is nobody, including many of us, right? We learn every day, nowadays, right? It's not that there is one service integrator who knows all, while technically people can claim as a part of sales. But in reality all of us are continuing to learn in this landscape. And if you put all of this equation together with multiple clouds the complexity just starts to exponentially grow. And that's exactly what I think JCI is experiencing and Suresh's team has been experiencing, and we've been working together. But the common problems are around security talent and cost management of this, right? Those are my three things. And one last thing that I would love to say before we move away from this question is, if you think about cloud operations as a concept that's evolving over the last few years, and I have touched upon this in the previous episode as well, Lisa, right? If you take architectures, we've gone into microservices, we've gone into all these server-less architectures all the fancy things that we want. That helps us go to market faster, be more competent to as a business. But that's not simplified stuff, right? That's complicated stuff. It's a lot more distributed. Second, again, we've advanced and created more modern infrastructure because all of what we are talking is platform as a service, services on the cloud that we are consuming, right? In the same case with development we've moved into a DevOps model. We kind of click a button put some code in a repository, the code starts to run in production within a minute, everything else is automated. But then when we get to operations we are still stuck in a very old way of looking at cloud as an infrastructure, right? So you've got an infra team, you've got an app team, you've got an incident management team, you've got a soft knock, everything. But again, so Suresh can talk about this more because they are making significant strides in thinking about this as a single workload, and how do I apply engineering to go manage this? Because a lot of it is codified, right? So automation. Anyway, so that's kind of where the complexity is and how we are thinking, including JCI as a partner thinking about taming that complexity as we move forward. >> Suresh, let's talk about that taming the complexity. You guys have both done a great job of articulating the ostensible challenges that are there with cloud, especially multi-cloud environments that you're living in. But Suresh, talk about the partnership with Hitachi Vantara. How is it helping to dial down some of those inherent complexities? >> I mean, I always, you know, I think I've said this to Prem multiple times. I treat my partners as my internal, you know, employees. I look at Prem as my coworker or my peers. So the reason for that is I want Prem to have the same vested interest as a partner in my success or JCI success and vice versa, isn't it? I think that's how we operate and that's how we have been operating. And I think I would like to thank Prem and Hitachi Vantara for that really been an amazing partnership. And as he was saying, we have taken a completely holistic approach to how we want to really be in the market and play in the market to our customers. So if you look at my jacket it talks about OpenBlue platform. This is what JCI is building, that we are building this OpenBlue digital platform. And within that, my team, along with Prem's or Hitachi's, we have built what we call as Polaris. It's a technical platform where our apps can run. And this platform is automated end-to-end from a platform engineering standpoint. We stood up a platform engineering organization, a reliability engineering organization, as well as a support organization where Hitachi played a role. As I said previously, you know, for me to scale I'm not going to really have the talent and the knowledge of every function that I'm looking at. And Hitachi, not only they brought the talent but they also brought what he was talking about, Harc. You know, they have set up a lot and now we can leverage it. And they also came up with some really interesting concepts. I went and met them in India. They came up with this concept called IPL. Okay, what is that? They really challenged all their employees that's working for GCI to come up with innovative ideas to solve problems proactively, which is self-healing. You know, how you do that? So I think partners, you know, if they become really vested in your interests, they can do wonders for you. And I think in this case Hitachi is really working very well for us and in many aspects. And I'm leveraging them... You started with support, now I'm leveraging them in the automation, the platform engineering, as well as in the reliability engineering and then in even in the engineering spaces. And that like, they are my end-to-end partner right now? >> So you're really taking that holistic approach that you talked about and it sounds like it's a very collaborative two-way street partnership. Prem, I want to go back to, Suresh mentioned Harc. Talk a little bit about what Harc is and then how partners fit into Hitachi's Harc strategy. >> Great, so let me spend like a few seconds on what Harc is. Lisa, again, I know we've been using the term. Harc stands for Hitachi application reliability sectors. Now the reason we thought about Harc was, like I said in the beginning of this segment, there is an illusion from an architecture standpoint to be more modern, microservices, server-less, reactive architecture, so on and so forth. There is an illusion in your development methodology from Waterfall to agile, to DevOps to lean, agile to path program, whatever, right? Extreme program, so on and so forth. There is an evolution in the space of infrastructure from a point where you were buying these huge humongous servers and putting it in your data center to a point where people don't even see servers anymore, right? You buy it, by a click of a button you don't know the size of it. All you know is a, it's (indistinct) whatever that name means. Let's go provision it on the fly, get go, get your work done, right? When all of this is advanced when you think about operations people have been solving the problem the way they've been solving it 20 years back, right? That's the issue. And Harc was conceived exactly to fix that particular problem, to think about a modern way of operating a modern workload, right? That's exactly what Harc. So it brings together finest engineering talent. So the teams are trained in specific ways of working. We've invested and implemented some of the IP, we work with the best of the breed partner ecosystem, and I'll talk about that in a minute. And we've got these facilities in Dallas and I am talking from my office in Dallas, which is a Harc facility in the US from where we deliver for our customers. And then back in Hyderabad, we've got one more that we opened and these are facilities from where we deliver Harc services for our customers as well, right? And then we are expanding it in Japan and Portugal as we move into 23. That's kind of the plan that we are thinking through. However, that's what Harc is, Lisa, right? That's our solution to this cloud complexity problem. Right? >> Got it, and it sounds like it's going quite global, which is fantastic. So Suresh, I want to have you expand a bit on the partnership, the partner ecosystem and the role that it plays. You talked about it a little bit but what role does the partner ecosystem play in really helping JCI to dial down some of those challenges and the inherent complexities that we talked about? >> Yeah, sure. I think partners play a major role and JCI is very, very good at it. I mean, I've joined JCI 18 months ago, JCI leverages partners pretty extensively. As I said, I leverage Hitachi for my, you know, A group and the (indistinct) space and the cloud operations space, and they're my primary partner. But at the same time, we leverage many other partners. Well, you know, Accenture, SCL, and even on the tooling side we use Datadog and (indistinct). All these guys are major partners of our because the way we like to pick partners is based on our vision and where we want to go. And pick the right partner who's going to really, you know make you successful by investing their resources in you. And what I mean by that is when you have a partner, partner knows exactly what kind of skillset is needed for this customer, for them to really be successful. As I said earlier, we cannot really get all the skillset that we need, we rely on the partners and partners bring the the right skillset, they can scale. I can tell Prem tomorrow, "Hey, I need two parts by next week", and I guarantee it he's going to bring two parts to me. So they let you scale, they let you move fast. And I'm a big believer, in today's day and age, to get things done fast and be more agile. I'm not worried about failure, but for me moving fast is very, very important. And partners really do a very good job bringing that. But I think then they also really make you think, isn't it? Because one thing I like about partners they make you innovate whether they know it or not but they do because, you know, they will come and ask you questions about, "Hey, tell me why you are doing this. Can I review your architecture?" You know, and then they will try to really say I don't think this is going to work. Because they work with so many different clients, not JCI, they bring all that expertise and that's what I look from them, you know, just not, you know, do a T&M job for me. I ask you to do this go... They just bring more than that. That's how I pick my partners. And that's how, you know, Hitachi's Vantara is definitely one of a good partner from that sense because they bring a lot more innovation to the table and I appreciate about that. >> It sounds like, it sounds like a flywheel of innovation. >> Yeah. >> I love that. Last question for both of you, which we're almost out of time here, Prem, I want to go back to you. So I'm a partner, I'm planning on redefining CloudOps at my company. What are the two things you want me to remember from Hitachi Vantara's perspective? >> So before I get to that question, Lisa, the partners that we work with are slightly different from from the partners that, again, there are some similar partners. There are some different partners, right? For example, we pick and choose especially in the Harc space, we pick and choose partners that are more future focused, right? We don't care if they are huge companies or small companies. We go after companies that are future focused that are really, really nimble and can change for our customers need because it's not our need, right? When I pick partners for Harc my ultimate endeavor is to ensure, in this case because we've got (indistinct) GCI on, we are able to operate (indistinct) with the level of satisfaction above and beyond that they're expecting from us. And whatever I don't have I need to get from my partners so that I bring this solution to Suresh. As opposed to bringing a whole lot of people and making them stand in front of Suresh. So that's how I think about partners. What do I want them to do from, and we've always done this so we do workshops with our partners. We just don't go by tools. When we say we are partnering with X, Y, Z, we do workshops with them and we say, this is how we are thinking. Either you build it in your roadmap that helps us leverage you, continue to leverage you. And we do have minimal investments where we fix gaps. We're building some utilities for us to deliver the best service to our customers. And our intention is not to build a product to compete with our partner. Our intention is to just fill the wide space until they go build it into their product suite that we can then leverage it for our customers. So always think about end customers and how can we make it easy for them? Because for all the tool vendors out there seeing this and wanting to partner with Hitachi the biggest thing is tools sprawl, especially on the cloud is very real. For every problem on the cloud. I have a billion tools that are being thrown at me as Suresh if I'm putting my installation and it's not easy at all. It's so confusing. >> Yeah. >> So that's what we want. We want people to simplify that landscape for our end customers, and we are looking at partners that are thinking through the simplification not just making money. >> That makes perfect sense. There really is a very strong symbiosis it sounds like, in the partner ecosystem. And there's a lot of enablement that goes on back and forth it sounds like as well, which is really, to your point it's all about the end customers and what they're expecting. Suresh, last question for you is which is the same one, if I'm a partner what are the things that you want me to consider as I'm planning to redefine CloudOps at my company? >> I'll keep it simple. In my view, I mean, we've touched upon it in multiple facets in this interview about that, the three things. First and foremost, reliability. You know, in today's day and age my products has to be reliable, available and, you know, make sure that the customer's happy with what they're really dealing with, number one. Number two, my product has to be secure. Security is super, super important, okay? And number three, I need to really make sure my customers are getting the value so I keep my cost low. So these three is what I would focus and what I expect from my partners. >> Great advice, guys. Thank you so much for talking through this with me and really showing the audience how strong the partnership is between Hitachi Vantara and JCI. What you're doing together, we'll have to talk to you again to see where things go but we really appreciate your insights and your perspectives. Thank you. >> Thank you, Lisa. >> Thanks Lisa, thanks for having us. >> My pleasure. For my guests, I'm Lisa Martin. Thank you so much for watching. (soothing music)

>> From theCUBE Studios in Palo Alto in Boston, bringing you data-driven insights from theCUBE and ETR, this is Breaking Analysis with Dave Vellante. >> While never really meant to be a consumer tech event, the rapid ascendancy of smartphones sucked much of the air out of Mobile World Congress over the years, now MWC. And while the device manufacturers continue to have a major presence at the show, the maturity of intelligent devices, longer life cycles, and the disaggregation of the network stack, have put enterprise technologies front and center in the telco business. Semiconductor manufacturers, network equipment players, infrastructure companies, cloud vendors, software providers, and a spate of startups are eyeing the trillion dollar plus communications industry as one of the next big things to watch this decade. Hello, and welcome to this week's Wikibon CUBE Insights, powered by ETR. In this Breaking Analysis, we bring you part two of our ongoing coverage of MWC '23, with some new data on enterprise players specifically in large telco environments, a brief glimpse at some of the pre-announcement news and corresponding themes ahead of MWC, and some of the key announcement areas we'll be watching at the show on theCUBE. Now, last week we shared some ETR data that showed how traditional enterprise tech players were performing, specifically within the telecoms vertical. Here's a new look at that data from ETR, which isolates the same companies, but cuts the data for what ETR calls large telco. The N in this cut is 196, down from 288 last week when we included all company sizes in the dataset. Now remember the two dimensions here, on the y-axis is net score, or spending momentum, and on the x-axis is pervasiveness in the data set. The table insert in the upper left informs how the dots and companies are plotted, and that red dotted line, the horizontal line at 40%, that indicates a highly elevated net score. Now while the data are not dramatically different in terms of relative positioning, there are a couple of changes at the margin. So just going down the list and focusing on net score. Azure is comparable, but slightly lower in this sector in the large telco than it was overall. Google Cloud comes in at number two, and basically swapped places with AWS, which drops slightly in the large telco relative to overall telco. Snowflake is also slightly down by one percentage point, but maintains its position. Remember Snowflake, overall, its net score is much, much higher when measuring across all verticals. Snowflake comes down in telco, and relative to overall, a little bit down in large telco, but it's making some moves to attack this market that we'll talk about in a moment. Next are Red Hat OpenStack and Databricks. About the same in large tech telco as they were an overall telco. Then there's Dell next that has a big presence at MWC and is getting serious about driving 16G adoption, and new servers, and edge servers, and other partnerships. Cisco and Red Hat OpenShift basically swapped spots when moving from all telco to large telco, as Cisco drops and Red Hat bumps up a bit. And VMware dropped about four percentage points in large telco. Accenture moved up dramatically, about nine percentage points in big telco, large telco relative to all telco. HPE dropped a couple of percentage points. Oracle stayed about the same. And IBM surprisingly dropped by about five points. So look, I understand not a ton of change in terms of spending momentum in the large sector versus telco overall, but some deltas. The bottom line for enterprise players is one, they're just getting started in this new disruption journey that they're on as the stack disaggregates. Two, all these players have experience in delivering horizontal solutions, but now working with partners and identifying big problems to be solved, and three, many of these companies are generally not the fastest moving firms relative to smaller disruptive disruptors. Now, cloud has been an exception in fairness. But the good news for the legacy infrastructure and IT companies is that the telco transformation and the 5G buildout is going to take years. So it's moving at a pace that is very favorable to many of these companies. Okay, so looking at just some of the pre-announcement highlights that have hit the wire this week, I want to give you a glimpse of the diversity of innovation that is occurring in the telecommunication space. You got semiconductor manufacturers, device makers, network equipment players, carriers, cloud vendors, enterprise tech companies, software companies, startups. Now we've included, you'll see in this list, we've included OpeRAN, that logo, because there's so much buzz around the topic and we're going to come back to that. But suffice it to say, there's no way we can cover all the announcements from the 2000 plus exhibitors at the show. So we're going to cherry pick here and make a few call outs. Hewlett Packard Enterprise announced an acquisition of an Italian private cellular network company called AthoNet. Zeus Kerravala wrote about it on SiliconANGLE if you want more details. Now interestingly, HPE has a partnership with Solana, which also does private 5G. But according to Zeus, Solona is more of an out-of-the-box solution, whereas AthoNet is designed for the core and requires more integration. And as you'll see in a moment, there's going to be a lot of talk at the show about private network. There's going to be a lot of news there from other competitors, and we're going to be watching that closely. And while many are concerned about the P5G, private 5G, encroaching on wifi, Kerravala doesn't see it that way. Rather, he feels that these private networks are really designed for more industrial, and you know mission critical environments, like factories, and warehouses that are run by robots, et cetera. 'Cause these can justify the increased expense of private networks. Whereas wifi remains a very low cost and flexible option for, you know, whatever offices and homes. Now, over to Dell. Dell announced its intent to go hard after opening up the telco network with the announcement that in the second half of this year it's going to begin shipping its infrastructure blocks for Red Hat. Remember it's like kind of the converged infrastructure for telco with a more open ecosystem and sort of more flexible, you know, more mature engineered system. Dell has also announced a range of PowerEdge servers for a variety of use cases. A big wide line bringing forth its 16G portfolio and aiming squarely at the telco space. Dell also announced, here we go, a private wireless offering with airspan, and Expedo, and a solution with AthoNet, the company HPE announced it was purchasing. So I guess Dell and HPE are now partnering up in the private wireless space, and yes, hell is freezing over folks. We'll see where that relationship goes in the mid- to long-term. Dell also announced new lab and certification capabilities, which we said last week was going to be critical for the further adoption of open ecosystem technology. So props to Dell for, you know, putting real emphasis and investment in that. AWS also made a number of announcements in this space including private wireless solutions and associated managed services. AWS named Deutsche Telekom, Orange, T-Mobile, Telefonica, and some others as partners. And AWS announced the stepped up partnership, specifically with T-Mobile, to bring AWS services to T-Mobile's network portfolio. Snowflake, back to Snowflake, announced its telecom data cloud. Remember we showed the data earlier, it's Snowflake not as strong in the telco sector, but they're continuing to move toward this go-to market alignment within key industries, realigning their go-to market by vertical. It also announced that AT&T, and a number of other partners, are collaborating to break down data silos specifically in telco. Look, essentially, this is Snowflake taking its core value prop to the telco vertical and forming key partnerships that resonate in the space. So think simplification, breaking down silos, data sharing, eventually data monetization. Samsung previewed its future capability to allow smartphones to access satellite services, something Apple has previously done. AMD, Intel, Marvell, Qualcomm, are all in the act, all the semiconductor players. Qualcomm for example, announced along with Telefonica, and Erickson, a 5G millimeter network that will be showcased in Spain at the event this coming week using Qualcomm Snapdragon chipset platform, based on none other than Arm technology. Of course, Arm we said is going to dominate the edge, and is is clearly doing so. It's got the volume advantage over, you know, traditional Intel, you know, X86 architectures. And it's no surprise that Microsoft is touting its open AI relationship. You're going to hear a lot of AI talk at this conference as is AI is now, you know, is the now topic. All right, we could go on and on and on. There's just so much going on at Mobile World Congress or MWC, that we just wanted to give you a glimpse of some of the highlights that we've been watching. Which brings us to the key topics and issues that we'll be exploring at MWC next week. We touched on some of this last week. A big topic of conversation will of course be, you know, 5G. Is it ever going to become real? Is it, is anybody ever going to make money at 5G? There's so much excitement around and anticipation around 5G. It has not lived up to the hype, but that's because the rollout, as we've previous reported, is going to take years. And part of that rollout is going to rely on the disaggregation of the hardened telco stack, as we reported last week and in previous Breaking Analysis episodes. OpenRAN is a big component of that evolution. You know, as our RAN intelligent controllers, RICs, which essentially the brain of OpenRAN, if you will. Now as we build out 5G networks at massive scale and accommodate unprecedented volumes of data and apply compute-hungry AI to all this data, the issue of energy efficiency is going to be front and center. It has to be. Not only is it a, you know, hot political issue, the reality is that improving power efficiency is compulsory or the whole vision of telco's future is going to come crashing down. So chip manufacturers, equipment makers, cloud providers, everybody is going to be doubling down and clicking on this topic. Let's talk about AI. AI as we said, it is the hot topic right now, but it is happening not only in consumer, with things like ChatGPT. And think about the theme of this Breaking Analysis in the enterprise, AI in the enterprise cannot be ChatGPT. It cannot be error prone the way ChatGPT is. It has to be clean, reliable, governed, accurate. It's got to be ethical. It's got to be trusted. Okay, we're going to have Zeus Kerravala on the show next week and definitely want to get his take on private networks and how they're going to impact wifi. You know, will private networks cannibalize wifi? If not, why not? He wrote about this again on SiliconANGLE if you want more details, and we're going to unpack that on theCUBE this week. And finally, as always we'll be following the data flows to understand where and how telcos, cloud players, startups, software companies, disruptors, legacy companies, end customers, how are they going to make money from new data opportunities? 'Cause we often say in theCUBE, don't ever bet against data. All right, that's a wrap for today. Remember theCUBE is going to be on location at MWC 2023 next week. We got a great set. We're in the walkway in between halls four and five, right in Congress Square, stand CS-60. Look for us, we got a full schedule. If you got a great story or you have news, stop by. We're going to try to get you on the program. I'll be there with Lisa Martin, co-hosting, David Nicholson as well, and the entire CUBE crew, so don't forget to come by and see us. I want to thank Alex Myerson, who's on production and manages the podcast, and Ken Schiffman, as well, in our Boston studio. Kristen Martin and Cheryl Knight help get the word out on social media and in our newsletters. And Rob Hof is our editor-in-chief over at SiliconANGLE.com. He does some great editing. Thank you. All right, remember all these episodes they are available as podcasts wherever you listen. All you got to do is search Breaking Analysis podcasts. I publish each week on Wikibon.com and SiliconANGLE.com. All the video content is available on demand at theCUBE.net, or you can email me directly if you want to get in touch David.Vellante@SiliconANGLE.com or DM me @DVellante, or comment on our LinkedIn posts. And please do check out ETR.ai for the best survey data in the enterprise tech business. This is Dave Vellante for theCUBE Insights, powered by ETR. Thanks for watching. We'll see you next week at Mobile World Congress '23, MWC '23, or next time on Breaking Analysis. (bright music)

(soothing music) >> Hey everyone, welcome to this event, "Build Your Cloud Center of Excellence." I'm your host, Lisa Martin. In the next 15 minutes or so my guest and I are going to be talking about redefining cloud operations, an application modernization for customers, and specifically how partners are helping to speed up that process. As you saw on our first two segments, we talked about problems enterprises are facing with cloud operations. We talked about redefining cloud operations as well to solve these problems. This segment is going to be focusing on how Hitachi Vantara's partners are really helping to speed up that process. We've got Johnson Controls here to talk about their partnership with Hitachi Vantara. Please welcome both of my guests, Prem Balasubramanian is with us, SVP and CTO Digital Solutions at Hitachi Vantara. And Suresh Mothikuru, SVP Customer Success Platform Engineering and Reliability Engineering from Johnson Controls. Gentlemen, welcome to the program, great to have you. >> Thank. >> Thank you, Lisa. >> First question is to both of you and Suresh, we'll start with you. We want to understand, you know, the cloud operations landscape is increasingly complex. We've talked a lot about that in this program. Talk to us, Suresh, about some of the biggest challenges and pin points that you faced with respect to that. >> Thank you. I think it's a great question. I mean, cloud has evolved a lot in the last 10 years. You know, when we were talking about a single cloud whether it's Azure or AWS and GCP, and that was complex enough. Now we are talking about multi-cloud and hybrid and you look at Johnson Controls, we have Azure we have AWS, we have GCP, we have Alibaba and we also support on-prem. So the architecture has become very, very complex and the complexity has grown so much that we are now thinking about whether we should be cloud native or cloud agnostic. So I think, I mean, sometimes it's hard to even explain the complexity because people think, oh, "When you go to cloud, everything is simplified." Cloud does give you a lot of simplicity, but it also really brings a lot more complexity along with it. So, and then next one is pretty important is, you know, generally when you look at cloud services, you have plenty of services that are offered within a cloud, 100, 150 services, 200 services. Even within those companies, you take AWS they might not know, an individual resource might not know about all the services we see. That's a big challenge for us as a customer to really understand each of the service that is provided in these, you know, clouds, well, doesn't matter which one that is. And the third one is pretty big, at least at the CTO the CIO, and the senior leadership level, is cost. Cost is a major factor because cloud, you know, will eat you up if you cannot manage it. If you don't have a good cloud governance process it because every minute you are in it, it's burning cash. So I think if you ask me, these are the three major things that I am facing day to day and that's where I use my partners, which I'll touch base down the line. >> Perfect, we'll talk about that. So Prem, I imagine that these problems are not unique to Johnson Controls or JCI, as you may hear us refer to it. Talk to me Prem about some of the other challenges that you're seeing within the customer landscape. >> So, yeah, I agree, Lisa, these are not very specific to JCI, but there are specific issues in JCI, right? So the way we think about these are, there is a common issue when people go to the cloud and there are very specific and unique issues for businesses, right? So JCI, and we will talk about this in the episode as we move forward. I think Suresh and his team have done some phenomenal step around how to manage this complexity. But there are customers who have a lesser complex cloud which is, they don't go to Alibaba, they don't have footprint in all three clouds. So their multi-cloud footprint could be a bit more manageable, but still struggle with a lot of the same problems around cost, around security, around talent. Talent is a big thing, right? And in Suresh's case I think it's slightly more exasperated because every cloud provider Be it AWS, JCP, or Azure brings in hundreds of services and there is nobody, including many of us, right? We learn every day, nowadays, right? It's not that there is one service integrator who knows all, while technically people can claim as a part of sales. But in reality all of us are continuing to learn in this landscape. And if you put all of this equation together with multiple clouds the complexity just starts to exponentially grow. And that's exactly what I think JCI is experiencing and Suresh's team has been experiencing, and we've been working together. But the common problems are around security talent and cost management of this, right? Those are my three things. And one last thing that I would love to say before we move away from this question is, if you think about cloud operations as a concept that's evolving over the last few years, and I have touched upon this in the previous episode as well, Lisa, right? If you take architectures, we've gone into microservices, we've gone into all these server-less architectures all the fancy things that we want. That helps us go to market faster, be more competent to as a business. But that's not simplified stuff, right? That's complicated stuff. It's a lot more distributed. Second, again, we've advanced and created more modern infrastructure because all of what we are talking is platform as a service, services on the cloud that we are consuming, right? In the same case with development we've moved into a DevOps model. We kind of click a button put some code in a repository, the code starts to run in production within a minute, everything else is automated. But then when we get to operations we are still stuck in a very old way of looking at cloud as an infrastructure, right? So you've got an infra team, you've got an app team, you've got an incident management team, you've got a soft knock, everything. But again, so Suresh can talk about this more because they are making significant strides in thinking about this as a single workload, and how do I apply engineering to go manage this? Because a lot of it is codified, right? So automation. Anyway, so that's kind of where the complexity is and how we are thinking, including JCI as a partner thinking about taming that complexity as we move forward. >> Suresh, let's talk about that taming the complexity. You guys have both done a great job of articulating the ostensible challenges that are there with cloud, especially multi-cloud environments that you're living in. But Suresh, talk about the partnership with Hitachi Vantara. How is it helping to dial down some of those inherent complexities? >> I mean, I always, you know, I think I've said this to Prem multiple times. I treat my partners as my internal, you know, employees. I look at Prem as my coworker or my peers. So the reason for that is I want Prem to have the same vested interest as a partner in my success or JCI success and vice versa, isn't it? I think that's how we operate and that's how we have been operating. And I think I would like to thank Prem and Hitachi Vantara for that really been an amazing partnership. And as he was saying, we have taken a completely holistic approach to how we want to really be in the market and play in the market to our customers. So if you look at my jacket it talks about OpenBlue platform. This is what JCI is building, that we are building this OpenBlue digital platform. And within that, my team, along with Prem's or Hitachi's, we have built what we call as Polaris. It's a technical platform where our apps can run. And this platform is automated end-to-end from a platform engineering standpoint. We stood up a platform engineering organization, a reliability engineering organization, as well as a support organization where Hitachi played a role. As I said previously, you know, for me to scale I'm not going to really have the talent and the knowledge of every function that I'm looking at. And Hitachi, not only they brought the talent but they also brought what he was talking about, Harc. You know, they have set up a lot and now we can leverage it. And they also came up with some really interesting concepts. I went and met them in India. They came up with this concept called IPL. Okay, what is that? They really challenged all their employees that's working for GCI to come up with innovative ideas to solve problems proactively, which is self-healing. You know, how you do that? So I think partners, you know, if they become really vested in your interests, they can do wonders for you. And I think in this case Hitachi is really working very well for us and in many aspects. And I'm leveraging them... You started with support, now I'm leveraging them in the automation, the platform engineering, as well as in the reliability engineering and then in even in the engineering spaces. And that like, they are my end-to-end partner right now? >> So you're really taking that holistic approach that you talked about and it sounds like it's a very collaborative two-way street partnership. Prem, I want to go back to, Suresh mentioned Harc. Talk a little bit about what Harc is and then how partners fit into Hitachi's Harc strategy. >> Great, so let me spend like a few seconds on what Harc is. Lisa, again, I know we've been using the term. Harc stands for Hitachi application reliability sectors. Now the reason we thought about Harc was, like I said in the beginning of this segment, there is an illusion from an architecture standpoint to be more modern, microservices, server-less, reactive architecture, so on and so forth. There is an illusion in your development methodology from Waterfall to agile, to DevOps to lean, agile to path program, whatever, right? Extreme program, so on and so forth. There is an evolution in the space of infrastructure from a point where you were buying these huge humongous servers and putting it in your data center to a point where people don't even see servers anymore, right? You buy it, by a click of a button you don't know the size of it. All you know is a, it's (indistinct) whatever that name means. Let's go provision it on the fly, get go, get your work done, right? When all of this is advanced when you think about operations people have been solving the problem the way they've been solving it 20 years back, right? That's the issue. And Harc was conceived exactly to fix that particular problem, to think about a modern way of operating a modern workload, right? That's exactly what Harc. So it brings together finest engineering talent. So the teams are trained in specific ways of working. We've invested and implemented some of the IP, we work with the best of the breed partner ecosystem, and I'll talk about that in a minute. And we've got these facilities in Dallas and I am talking from my office in Dallas, which is a Harc facility in the US from where we deliver for our customers. And then back in Hyderabad, we've got one more that we opened and these are facilities from where we deliver Harc services for our customers as well, right? And then we are expanding it in Japan and Portugal as we move into 23. That's kind of the plan that we are thinking through. However, that's what Harc is, Lisa, right? That's our solution to this cloud complexity problem. Right? >> Got it, and it sounds like it's going quite global, which is fantastic. So Suresh, I want to have you expand a bit on the partnership, the partner ecosystem and the role that it plays. You talked about it a little bit but what role does the partner ecosystem play in really helping JCI to dial down some of those challenges and the inherent complexities that we talked about? >> Yeah, sure. I think partners play a major role and JCI is very, very good at it. I mean, I've joined JCI 18 months ago, JCI leverages partners pretty extensively. As I said, I leverage Hitachi for my, you know, A group and the (indistinct) space and the cloud operations space, and they're my primary partner. But at the same time, we leverage many other partners. Well, you know, Accenture, SCL, and even on the tooling side we use Datadog and (indistinct). All these guys are major partners of our because the way we like to pick partners is based on our vision and where we want to go. And pick the right partner who's going to really, you know make you successful by investing their resources in you. And what I mean by that is when you have a partner, partner knows exactly what kind of skillset is needed for this customer, for them to really be successful. As I said earlier, we cannot really get all the skillset that we need, we rely on the partners and partners bring the the right skillset, they can scale. I can tell Prem tomorrow, "Hey, I need two parts by next week", and I guarantee it he's going to bring two parts to me. So they let you scale, they let you move fast. And I'm a big believer, in today's day and age, to get things done fast and be more agile. I'm not worried about failure, but for me moving fast is very, very important. And partners really do a very good job bringing that. But I think then they also really make you think, isn't it? Because one thing I like about partners they make you innovate whether they know it or not but they do because, you know, they will come and ask you questions about, "Hey, tell me why you are doing this. Can I review your architecture?" You know, and then they will try to really say I don't think this is going to work. Because they work with so many different clients, not JCI, they bring all that expertise and that's what I look from them, you know, just not, you know, do a T&M job for me. I ask you to do this go... They just bring more than that. That's how I pick my partners. And that's how, you know, Hitachi's Vantara is definitely one of a good partner from that sense because they bring a lot more innovation to the table and I appreciate about that. >> It sounds like, it sounds like a flywheel of innovation. >> Yeah. >> I love that. Last question for both of you, which we're almost out of time here, Prem, I want to go back to you. So I'm a partner, I'm planning on redefining CloudOps at my company. What are the two things you want me to remember from Hitachi Vantara's perspective? >> So before I get to that question, Lisa, the partners that we work with are slightly different from from the partners that, again, there are some similar partners. There are some different partners, right? For example, we pick and choose especially in the Harc space, we pick and choose partners that are more future focused, right? We don't care if they are huge companies or small companies. We go after companies that are future focused that are really, really nimble and can change for our customers need because it's not our need, right? When I pick partners for Harc my ultimate endeavor is to ensure, in this case because we've got (indistinct) GCI on, we are able to operate (indistinct) with the level of satisfaction above and beyond that they're expecting from us. And whatever I don't have I need to get from my partners so that I bring this solution to Suresh. As opposed to bringing a whole lot of people and making them stand in front of Suresh. So that's how I think about partners. What do I want them to do from, and we've always done this so we do workshops with our partners. We just don't go by tools. When we say we are partnering with X, Y, Z, we do workshops with them and we say, this is how we are thinking. Either you build it in your roadmap that helps us leverage you, continue to leverage you. And we do have minimal investments where we fix gaps. We're building some utilities for us to deliver the best service to our customers. And our intention is not to build a product to compete with our partner. Our intention is to just fill the wide space until they go build it into their product suite that we can then leverage it for our customers. So always think about end customers and how can we make it easy for them? Because for all the tool vendors out there seeing this and wanting to partner with Hitachi the biggest thing is tools sprawl, especially on the cloud is very real. For every problem on the cloud. I have a billion tools that are being thrown at me as Suresh if I'm putting my installation and it's not easy at all. It's so confusing. >> Yeah. >> So that's what we want. We want people to simplify that landscape for our end customers, and we are looking at partners that are thinking through the simplification not just making money. >> That makes perfect sense. There really is a very strong symbiosis it sounds like, in the partner ecosystem. And there's a lot of enablement that goes on back and forth it sounds like as well, which is really, to your point it's all about the end customers and what they're expecting. Suresh, last question for you is which is the same one, if I'm a partner what are the things that you want me to consider as I'm planning to redefine CloudOps at my company? >> I'll keep it simple. In my view, I mean, we've touched upon it in multiple facets in this interview about that, the three things. First and foremost, reliability. You know, in today's day and age my products has to be reliable, available and, you know, make sure that the customer's happy with what they're really dealing with, number one. Number two, my product has to be secure. Security is super, super important, okay? And number three, I need to really make sure my customers are getting the value so I keep my cost low. So these three is what I would focus and what I expect from my partners. >> Great advice, guys. Thank you so much for talking through this with me and really showing the audience how strong the partnership is between Hitachi Vantara and JCI. What you're doing together, we'll have to talk to you again to see where things go but we really appreciate your insights and your perspectives. Thank you. >> Thank you, Lisa. >> Thanks Lisa, thanks for having us. >> My pleasure. For my guests, I'm Lisa Martin. Thank you so much for watching. (soothing music)

>> From the Cube Studios in Palo Alto in Boston, bringing you data-driven insights from The Cube and ETR. This is "Breaking Analysis" with Dave Vellante. >> The world's leading telcos are trying to shed the stigma of being monopolies lacking innovation. Telcos have been great at operational efficiency and connectivity and living off of transmission, and the costs and expenses or revenue associated with that transmission. But in a world beyond telephone poles and basic wireless and mobile services, how will telcos modernize and become more agile and monetize new opportunities brought about by 5G and private wireless and a spate of new innovations and infrastructure, cloud data and apps? Hello, and welcome to this week's Wikibon CUBE Insights powered by ETR. In this breaking analysis and ahead of Mobile World Congress or now, MWC23, we explore the evolution of the telco business and how the industry is in many ways, mimicking transformations that took place decades ago in enterprise IT. We'll model some of the traditional enterprise vendors using ETR data and investigate how they're faring in the telecommunications sector, and we'll pose some of the key issues facing the industry this decade. First, let's take a look at what the GSMA has in store for MWC23. GSMA is the host of what used to be called Mobile World Congress. They've set the theme for this year's event as "Velocity" and they've rebranded MWC to reflect the fact that mobile technology is only one part of the story. MWC has become one of the world's premier events highlighting innovations not only in Telco, mobile and 5G, but the collision between cloud, infrastructure, apps, private networks, smart industries, machine intelligence, and AI, and more. MWC comprises an enormous ecosystem of service providers, technology companies, and firms from virtually every industry including sports and entertainment. And as well, GSMA, along with its venue partner at the Fira Barcelona, have placed a major emphasis on sustainability and public and private partnerships. Virtually every industry will be represented at the event because every industry is impacted by the trends and opportunities in this space. GSMA has said it expects 80,000 attendees at MWC this year, not quite back to 2019 levels, but trending in that direction. Of course, attendance from Chinese participants has historically been very high at the show, and obviously the continued travel issues from that region are affecting the overall attendance, but still very strong. And despite these concerns, Huawei, the giant Chinese technology company. has the largest physical presence of any exhibitor at the show. And finally, GSMA estimates that more than $300 million in economic benefit will result from the event which takes place at the end of February and early March. And The Cube will be back at MWC this year with a major presence thanks to our anchor sponsor, Dell Technologies and other supporters of our content program, including Enterprise Web, ArcaOS, VMware, Snowflake, Cisco, AWS, and others. And one of the areas we're interested in exploring is the evolution of the telco stack. It's a topic that's often talked about and one that we've observed taking place in the 1990s when the vertically integrated IBM mainframe monopoly gave way to a disintegrated and horizontal industry structure. And in many ways, the same thing is happening today in telecommunications, which is shown on the left-hand side of this diagram. Historically, telcos have relied on a hardened, integrated, and incredibly reliable, and secure set of hardware and software services that have been fully vetted and tested, and certified, and relied upon for decades. And at the top of that stack on the left are the crown jewels of the telco stack, the operational support systems and the business support systems. For the OSS, we're talking about things like network management, network operations, service delivery, quality of service, fulfillment assurance, and things like that. For the BSS systems, these refer to customer-facing elements of the stack, like revenue, order management, what products they sell, billing, and customer service. And what we're seeing is telcos have been really good at operational efficiency and making money off of transport and connectivity, but they've lacked the innovation in services and applications. They own the pipes and that works well, but others, be the over-the-top content companies, or private network providers and increasingly, cloud providers have been able to bypass the telcos, reach around them, if you will, and drive innovation. And so, the right-most diagram speaks to the need to disaggregate pieces of the stack. And while the similarities to the 1990s in enterprise IT are greater than the differences, there are things that are different. For example, the granularity of hardware infrastructure will not likely be as high where competition occurred back in the 90s at every layer of the value chain with very little infrastructure integration. That of course changed in the 2010s with converged infrastructure and hyper-converged and also software defined. So, that's one difference. And the advent of cloud, containers, microservices, and AI, none of that was really a major factor in the disintegration of legacy IT. And that probably means that disruptors can move even faster than did the likes of Intel and Microsoft, Oracle, Cisco, and the Seagates of the 1990s. As well, while many of the products and services will come from traditional enterprise IT names like Dell, HPE, Cisco, Red Hat, VMware, AWS, Microsoft, Google, et cetera, many of the names are going to be different and come from traditional network equipment providers. These are names like Ericsson and Huawei, and Nokia, and other names, like Wind River, and Rakuten, and Dish Networks. And there are enormous opportunities in data to help telecom companies and their competitors go beyond telemetry data into more advanced analytics and data monetization. There's also going to be an entirely new set of apps based on the workloads and use cases ranging from hospitals, sports arenas, race tracks, shipping ports, you name it. Virtually every vertical will participate in this transformation as the industry evolves its focus toward innovation, agility, and open ecosystems. Now remember, this is not a binary state. There are going to be greenfield companies disrupting the apple cart, but the incumbent telcos are going to have to continue to ensure newer systems work with their legacy infrastructure, in their OSS and BSS existing systems. And as we know, this is not going to be an overnight task. Integration is a difficult thing, transformations, migrations. So that's what makes this all so interesting because others can come in with Greenfield and potentially disrupt. There'll be interesting partnerships and ecosystems will form and coalitions will also form. Now, we mentioned that several traditional enterprise companies are or will be playing in this space. Now, ETR doesn't have a ton of data on specific telecom equipment and software providers, but it does have some interesting data that we cut for this breaking analysis. What we're showing here in this graphic is some of the names that we've followed over the years and how they're faring. Specifically, we did the cut within the telco sector. So the Y-axis here shows net score or spending velocity. And the horizontal axis, that shows the presence or pervasiveness in the data set. And that table insert in the upper left, that informs as to how the dots are plotted. You know, the two columns there, net score and the ends. And that red-dotted line, that horizontal line at 40%, that is an indicator of a highly elevated level. Anything above that, we consider quite outstanding. And what we'll do now is we'll comment on some of the cohorts and share with you how they're doing in telecommunications, and that sector, that vertical relative to their position overall in the data set. Let's start with the public cloud players. They're prominent in every industry. Telcos, telecommunications is no exception and it's quite an interesting cohort here. On the one hand, they can help telecommunication firms modernize and become more agile by eliminating the heavy lifting and you know, all the cloud, you know, value prop, data center costs, and the cloud benefits. At the same time, public cloud players are bringing their services to the edge, building out their own global networks and are a disruptive force to traditional telcos. All right, let's talk about Azure first. Their net score is basically identical to telco relative to its overall average. AWS's net score is higher in telco by just a few percentage points. Google Cloud platform is eight percentage points higher in telco with a 53% net score. So all three hyperscalers have an equal or stronger presence in telco than their average overall. Okay, let's look at the traditional enterprise hardware and software infrastructure cohort. Dell, Cisco, HPE, Red Hat, VMware, and Oracle. We've highlighted in this chart just as sort of indicators or proxies. Dell's net score's 10 percentage points higher in telco than its overall average. Interesting. Cisco's is a bit higher. HPE's is actually lower by about nine percentage points in the ETR survey, and VMware's is lower by about four percentage points. Now, Red Hat is really interesting. OpenStack, as we've previously reported is popular with telcos who want to build out their own private cloud. And the data shows that Red Hat OpenStack's net score is 15 percentage points higher in the telco sector than its overall average. OpenShift, on the other hand, has a net score that's four percentage points lower in telco than its overall average. So this to us talks to the pace of adoption of microservices and containers. You know, it's going to happen, but it's going to happen more slowly. Finally, Oracle's spending momentum is somewhat lower in the sector than its average, despite the firm having a decent telco business. IBM and Accenture, heavy services companies are both lower in this sector than their average. And real quickly, snowflake's net score is much lower by about 12 percentage points relative to its very high average net score of 62%. But we look for them to be a player in this space as telcos need to modernize their analytics stack and share data in a governed manner. Databricks' net score is also much lower than its average by about 13 points. And same, I would expect them to be a player as open architectures and cloud gains steam in telco. All right, let's close out now on what we're going to be talking about at MWC23 and some of the key issues that we'll be unpacking. We've talked about stack disaggregation in this breaking analysis, but the key here will be the pace at which it will reach the operational efficiency and reliability of closed stacks. Telcos, you know, in a large part, they're engineering heavy firms and much of their work takes place, kind of in the basement, in the dark. It's not really a big public hype machine, and they tend to move slowly and cautiously. While they understand the importance of agility, they're going to be careful because, you know, it's in their DNA. And so at the same time, if they don't move fast enough, they're going to get hurt and disrupted by competitors. So that's going to be a topic of conversation, and we'll be looking for proof points. And the other comment I'll make is around integration. Telcos because of their conservatism will benefit from better testing and those firms that can innovate on the testing front and have labs and certifications and innovate at that level, with an ecosystem are going to be in a better position. Because open sometimes means wild west. So the more players like Dell, HPE, Cisco, Red Hat, et cetera, that do that and align with their ecosystems and provide those resources, the faster adoption is going to go. So we'll be looking for, you know, who's actually doing that, Open RAN or Radio Access Networks. That fits in this discussion because O-RAN is an emerging network architecture. It essentially enables the use of open technologies from an ecosystem and over time, look at O-RAN is going to be open, but the questions, you know, a lot of questions remain as to when it will be able to deliver the operational efficiency of traditional RAN. Got some interesting dynamics going on. Rakuten is a company that's working hard on this problem, really focusing on operational efficiency. Then you got Dish Networks. They're also embracing O-RAN. They're coming at it more from service innovation. So that's something that we'll be monitoring and unpacking. We're going to look at cloud as a disruptor. On the one hand, cloud can help drive agility, as we said earlier and optionality, and innovation for incumbent telcos. But the flip side is going to also do the same for startups trying to disrupt and cloud attracts startups. While some of the telcos are actually embracing the cloud, many are being cautious. So that's going to be an interesting topic of discussion. And there's private wireless networks and 5G, and hyperlocal private networks, they're being deployed, you know, at the edge. This idea of open edge is also a really hot topic and this trend is going to accelerate. You know, the importance here is that the use cases are going to be widely varied. The needs of a hospital are going to be different than those of a sports venue are different from a remote drilling location, and energy or a concert venue. Things like real-time AI inference and data flows are going to bring new services and monetization opportunities. And many firms are going to be bypassing traditional telecommunications networks to build these out. Satellites as well, we're going to see, you know, in this decade, you're going to have, you're going to look down at Google Earth and you're going to see real-time. You know, today you see snapshots and so, lots of innovations going in that space. So how is this going to disrupt industries and traditional industry structures? Now, as always, we'll be looking at data angles, right? 'Cause it's in The Cube's DNA to follow the data and what opportunities and risks data brings. The Cube is going to be on location at MWC23 at the end of the month. We got a great set. We're in the walkway between halls four and five, right in Congress Square, it's booths CS60. So we'll have a full, they're called Stan CS60. We have a full schedule. I'm going to be there with Lisa Martin, Dave Nicholson and the entire Cube crew, so don't forget to stop by. All right, that's a wrap. I want to thank Alex Myerson, who's on production and manages the podcast, Ken Schiffman as well. Kristin Martin and Cheryl Knight help get the word out on social media and in our newsletters. And Rob Hof is our editor-in-chief over at Silicon Angle, does some great stuff for us. Thank you all. Remember, all these episodes are available as podcasts. Wherever you listen, just search "Breaking Analysis" podcasts I publish each week on wikibon.com and silicon angle.com. And all the video content is available on demand at thecube.net. You can email me directly at david.vellante@silicon angle.com. You can DM me at dvellante or comment on my LinkedIn post. Please do check out etr.ai for the best survey data in the enterprise tech business. This is Dave Vellante for The Cube Insights powered by ETR. Thanks for watching and we'll see you at Mobile World Congress, and/or at next time on "Breaking Analysis." (bright music) (bright music fades)

(upbeat music) >> Hey everyone. Welcome to theCUBE's special program series "Women of the Cloud", brought to you by AWS. I'm your host for the program, Lisa Martin. Very pleased to welcome back one of our alumni to this special series, Dr. Tendu Yogurtcu joins us, the CTO of Precisely. >> Lisa: Tendu, it's great to see you, it's been a while, but I'm glad that you're doing so well. >> Geez, it's so great seeing you too, and thank you for having me. >> My pleasure. I want the audience to understand a little bit about you. Talk to me a little bit about you, about your role and what are some of the great things that you're doing at Precisely. >> Of course. As CTO, my current role is driving technology vision and innovation, and also coming up with expansion strategies for Precisely's future growth. Precisely is the leader in data integrity. We deliver data with trust, with maximum accuracy, consistency, and also with context. And as a CTO, keeping an eye on what's coming in the business space, what's coming up with the emerging challenges is really key for me. Prior to becoming CTO, I was General Manager for the Syncsort big data business. And previously I had several engineering and R&D leadership roles. I also have a bit of academia experience. I served as a part-time faculty in computer science department in a university. And I am a person who is very tuned to giving back to my community. So I'm currently serving as a advisory board member in the same university. And I'm also serving as a advisory board member for a venture capital firm. And I take pride in being a dedicated advocate for STEM education and STEM education for women in particular, and girls in the underserved areas. >> You have such a great background. The breadth of your background, the experience that you have in the industry as well in academia is so impressive. I've known you a long time. I'd love the audience to get some recommendations from you. For those of the audience looking to grow and expand their careers in technology, what are some of the things that you that you've experienced that you would recommend people do? >> First, stay current. What is emerging today is going to be current very quickly. Especially now we are seeing more change and change at the increased speed than ever. So keeping an eye on on what's happening in the market if you want to be marketable. Now, some of the things that I will say, we have shortage of skills with data science, data engineering with security cyber security with cloud, right? We are here talking about cloud in particular. So there is a shortage of skills in the emerging technologies, AI, ML, there's a shortage of skills also in the retiring technologies. So we are in this like spectrum of skills shortage. So stay tuned to what's coming up. That's one. And on the second piece is that the quicker you tie what you are doing to the goals of the business, whether that's revenue growth whether that's customer retention or cost optimization you are more likely to grow in your career. You have to be able to articulate what you are doing and how that brings value to business to your boss, to your customers. So that becomes an important one. And then third one is giving back. Do something for the women in technology while being a woman in technology. Give back to your community whether that's community is gender based or whether it's your alumni, whether it's your community social community in your neighborhood or in your country or ethnicity. Give back to your community. I think that's becoming really important. >> I think so too. I think that paying it forward is so critical. I'm sure that you have a a long list of mentors and sponsors that have guided you along the way. Giving back to the community paying it forward I think is so important. For others who might be a few years behind us or even maybe have been in tech for the same amount of time that are looking to grow and expand their career having those mentors and sponsors of women who've been through the trenches is inspiring. It's so helpful. And it really is something that we need to do from a diversity perspective alone, right? >> Correct. Correct. And we have seen that, we have seen, for example Covid impact in women in particular. Diverse studies done by girls who quote on Accenture that showed that actually 50% of the women above age 35 were actually dropping out of the technology. And those numbers are scary. However, on the other side we have also seen incredible amount of technology innovation during that time with cloud adoption increasing with the ability to actually work remotely if you are even living in not so secure areas, for example that created more opportunities for women to come back to workforce as well. So we can turn the challenges to opportunities and watch out for those. I would say tipping points. >> I love that you bring up such a great point. There are so, so the, the data doesn't lie, right? The data shows that there's a significant amount of churn for women in technology. But to your point, there are so many opportunities. You mentioned a minute ago the skills gap. One of the things we talk about often on theCUBE and we're talking about cybersecurity which is obviously it's a global risk for companies in every industry, is that there's massive opportunity for people of, of any type to be able to grow their skills. So knowing that there's trend, but there's also so much opportunity for women in technology to climb the ladder is kind of exciting. I think. >> It is. It is exciting. >> Talk to me a little bit about, I would love for the audience to understand some of your hands-on examples where you've really been successful helping organizations navigate digital transformation and their entry and success with cloud computing. What are some of those success stories that you're really proud of? >> Let me think about, first of all what we are seeing is with the digital transformation in general, every single business every single vertical is becoming a technology company. Telecom companies are becoming a technology company. Financial services are becoming a technology company and manufacturing is becoming a technology company. So every business is becoming technology driven. And data is the key. Data is the enabler for every single business. So when we think about the challenges, one of the examples that I give a big challenge for our customers is I can't find the critical data, I can't access it. What are my critical data elements? Because I have so high volumes growing exponentially. What are the critical data elements that I should care and how do I access that? And we work at Precisely with 99 of Fortune 100. So we have two 12,000 customers in over a hundred countries which means we have customers whose businesses are purely built on cloud, clean slate. We also have businesses who have very complex set of data platforms. They have financial services, insurance, for example. They have critical transactional workloads still running on mainframes, IBM i servers, SAP systems. So one of the challenges that we have, and I work with key customers, is on how do we make data accessible for advanced analytics in the cloud? Cloud opens up a ton of open source tools, AI, ML stack lots of tools that actually the companies can leverage for that analytics in addition to elasticity in addition to easy to set up infrastructure. So how do we make sure the data can be actually available from these transactional systems, from mainframes at the speed that the business requires. So it's not just accessing data at the speed the business requires. One of our insurance customers they actually created this data marketplace on Amazon Cloud. And the, their challenge was to make sure they can bring the fresh data on a nightly basis initially and which became actually half an hour, every half an hour. So the speed of the business requirements have changed over time. We work with them very closely and also with the Amazon teams on enabling bringing data and workloads from the mainframes and executing in the cloud. So that's one example. Another big challenge that we see is, can I trust my data? And data integrity is more critical than ever. The quality of data, actually, according to HBR Harvard Business Review survey, 47% of every new record of data has at least one critical data error, 47%. So imagine, I was talking with the manufacturing organization couple of weeks ago and they were giving me an example. They have these three letter quotes for parts and different chemicals they use in the manufacturing. And the single letter error calls a shutdown of the whole manufacturing line. >> Wow. >> So that kind of challenge, how do I ensure that I can actually have completeness of data cleanness of data and consistency in that data? Moreover, govern that on a continuous basis becomes one of the use cases that we help customers. And in that particular case actually we help them put a data governance framework and data quality in their manufacturing line. It's becoming also a critical for, for example ESG, environment, social and governance, supply chain, monitoring the supply chain, and assessing ESG metrics. We see that again. And then the third one, last one. I will give an example because I think it's important. Hybrid cloud becoming critical. Because there's a purest view for new companies. However, facilitating flexible deployment models and facilitating cloud and hybrid cloud is also where we really we can help our customers. >> You brought up some amazingly critical points where it comes to data. You talked about, you know, a minute ago, every company in every industry has to become a technology company. You could also say every company across every industry has to become a data company. They have to become a software company. But to your point, and what it sounds like precisely is really helping organizations to do is access the data access data that has high integrity data that is free of errors. Obviously that's business critical. You talked about the high percentage of errors that caused manufacturing shutdown. Businesses can't, can't have that. That could potentially be life-ending for an organization. So it sounds like what you're talking about data accessibility, data integrity data governance and having that all in real time is table stakes for businesses. Whether it's your grocery store, your local coffee shop a manufacturing company, and e-commerce company. It's table stakes globally these days. >> It is, and you made a very good point actually, Lisa when you talked about the local coffee shop or the retail. One other interesting statistic is that almost 80% of every data has a location attribute. So when we talk about data integrity we no longer talk about just, and consistency of data. We also talk about context, right? When you are going, for example, to a new town you are probably getting some reminders about where your favorite coffee shop is or what telecom company has an office in that particular town. Or if you're an insurance company and a hurricane is hitting southern Florida. Then you want to know how the path of that hurricane is going to impact your customers and predict the claims before they happen. Also understand the propensity of the potential customers that you don't yet have. So location and context, those additional attributes of demographics, visitations are creating actually more confident business insights. >> Absolutely. And and as the consumer we're becoming more and more demanding. We want to be able to transact things so easily whether it's in our personal life at the grocery store, at that cafe, or in our business life. So those demands from the customer are also really influencing the direction that companies need to go. And it's actually, I think it's quite exciting that the amount of personalization the location data that you talk about that comes in there and really helps companies in every industry deliver these the cloud can, these amazing, unique personalized experiences that really drive business forward. We could talk about that all day long. I have no problem. But I want to get in our final minutes here, Tendu. What do you see as in your crystal ball as next for the cloud? How do you see your role as CTO evolving? >> Sure. For what we are seeing in the cloud I think we will start seeing more and more focus on sustainability. Sustainable technologies and governance. Obviously cloud migrations cloud modernizations are helping with that. And we, we are seeing many of our customers they started actually assessing the ESG supply chain and reporting on metrics whether it's the percentage of face or energy consumption. Also on the social metrics on diversity age distribution and as well as compliance piece. So sustainability governance I think that will become one area. Second, security, we talked about IT security and data privacy. I think we will see more and more investments around those. Cybersecurity in particular. And ethical data access and ethics is becoming center to everything we are doing as we have those personalized experiences and have more opportunities in the cloud. And the third one is continued automation with AI, ML and more focus on automation because cloud enables that at scale. And the work that we need to do is too time-intensive and too manual with the amount of data. Data is powering every business. So automation is going to be an increased focus how my role evolves with that. So I have this unique combination. I have been open to non-linear career paths throughout my growth. So I have an understanding of how to innovate and build products that solve real business problems. I also have an understanding of how to sell them build partnerships that combined with the the scale of growth, the hyper growth that we have absorbed in precisely 10 times growth within the last 10 years through a combination of organic innovation and acquisitions really requires the speed of change. So change, implementing change at scale as well as at speed. So taking those and bringing them to the next challenge is the evolution of my role. How do I bring those and tackle keep an eye on what's coming as a challenge in the industry and how they apply those skills that I have developed throughout my career to that next challenge and evolve with it, bring the innovation to data to cloud and the next challenge that we are going to see. >> There's so much on the horizon. It's, there are certainly challenges, you know within technology, but there's so much opportunity. You've done such a great job highlighting your career path the, the big impact that you're helping organizations make leveraging cloud and the opportunity that's there for the rest of us to really get in there get our hands dirty and solve problems. Tendu, I always love our conversations. It's been such a pleasure having you back, back on theCUBE. Thank you for joining us on this special program series today. >> Thank you Lisa. And also thanks to AWS for the opportunity. >> Absolutely. This is brought, brought to us by AWS. For Dr.Tendu, you are good to go. I'm Lisa Martin. You're watching theCUBE special program series Women of the Cloud. We thank you so much for watching and we'll see you soon. (upbeat music)

Hello and welcome back to Supercloud 2 where we examine the intersection of cloud and data in the 2020s. My name is Dave Vellante. Our Supercloud panel, our power panel is back. Maribel Lopez is the founder and principal analyst at Lopez Research. Sanjeev Mohan is former Gartner analyst and principal at Sanjeev Mohan. And Keith Townsend is the CTO advisor. Folks, welcome back and thanks for your participation today. Good to see you. >> Okay, great. >> Great to see you. >> Thanks. Let me start, Maribel, with you. Bob Muglia, we had a conversation as part of Supercloud the other day. And he said, "Dave, I like the work, you got to simplify this a little bit." So he said, quote, "A Supercloud is a platform." He said, "Think of it as a platform that provides programmatically consistent services hosted on heterogeneous cloud providers." And then Nelu Mihai said, "Well, wait a minute. This is just going to create more stove pipes. We need more standards in an architecture," which is kind of what Berkeley Sky Computing initiative is all about. So there's a sort of a debate going on. Is supercloud an architecture, a platform? Or maybe it's just another buzzword. Maribel, do you have a thought on this? >> Well, the easy answer would be to say it's just a buzzword. And then we could just kill the conversation and be done with it. But I think the term, it's more than that, right? The term actually isn't new. You can go back to at least 2016 and find references to supercloud in Cornell University or assist in other documents. So, having said this, I think we've been talking about Supercloud for a while, so I assume it's more than just a fancy buzzword. But I think it really speaks to that undeniable trend of moving towards an abstraction layer to deal with the chaos of what we consider managing multiple public and private clouds today, right? So one definition of the technology platform speaks to a set of services that allows companies to build and run that technology smoothly without worrying about the underlying infrastructure, which really gets back to something that Bob said. And some of the question is where that lives. And you could call that an abstraction layer. You could call it cross-cloud services, hybrid cloud management. So I see momentum there, like legitimate momentum with enterprise IT buyers that are trying to deal with the fact that they have multiple clouds now. So where I think we're moving is trying to define what are the specific attributes and frameworks of that that would make it so that it could be consistent across clouds. What is that layer? And maybe that's what the supercloud is. But one of the things I struggle with with supercloud is. What are we really trying to do here? Are we trying to create differentiated services in the supercloud layer? Is a supercloud just another variant of what AWS, GCP, or others do? You spoken to Walmart about its cloud native platform, and that's an example of somebody deciding to do it themselves because they need to deal with this today and not wait for some big standards thing to happen. So whatever it is, I do think it's something. I think we're trying to maybe create an architecture out of it would be a better way of saying it so that it does get to those set of principles, but it also needs to be edge aware. I think whenever we talk about supercloud, we're always talking about like the big centralized cloud. And I think we need to think about all the distributed clouds that we're looking at in edge as well. So that might be one of the ways that supercloud evolves. >> So thank you, Maribel. Keith, Brian Gracely, Gracely's law, things kind of repeat themselves. We've seen it all before. And so what Muglia brought to the forefront is this idea of a platform where the platform provider is really responsible for the architecture. Of course, the drawback is then you get a a bunch of stove pipes architectures. But practically speaking, that's kind of the way the industry has always evolved, right? >> So if we look at this from the practitioner's perspective and we talk about platforms, traditionally vendors have provided the platforms for us, whether it's distribution of lineage managed by or provided by Red Hat, Windows, servers, .NET, databases, Oracle. We think of those as platforms, things that are fundamental we can build on top. Supercloud isn't today that. It is a framework or idea, kind of a visionary goal to get to a point that we can have a platform or a framework. But what we're seeing repeated throughout the industry in customers, whether it's the Walmarts that's kind of supersized the idea of supercloud, or if it's regular end user organizations that are coming out with platform groups, groups who normalize cloud native infrastructure, AWS multi-cloud, VMware resources to look like one thing internally to their developers. We're seeing this trend that there's a desire for a platform that provides the capabilities of a supercloud. >> Thank you for that. Sanjeev, we often use Snowflake as a supercloud example, and now would presumably would be a platform with an architecture that's determined by the vendor. Maybe Databricks is pushing for a more open architecture, maybe more of that nirvana that we were talking about before to solve for supercloud. But regardless, the practitioner discussions show. At least currently, there's not a lot of cross-cloud data sharing. I think it could be a killer use case, egress charges or a barrier. But how do you see it? Will that change? Will we hide that underlying complexity and start sharing data across cloud? Is that something that you think Snowflake or others will be able to achieve? >> So I think we are already starting to see some of that happen. Snowflake is definitely one example that gets cited a lot. But even we don't talk about MongoDB in this like, but you could have a MongoDB cluster, for instance, with nodes sitting in different cloud providers. So there are companies that are starting to do it. The advantage that these companies have, let's take Snowflake as an example, it's a centralized proprietary platform. And they are building the capabilities that are needed for supercloud. So they're building things like you can push down your data transformations. They have the entire security and privacy suite. Data ops, they're adding those capabilities. And if I'm not mistaken, it'll be very soon, we will see them offer data observability. So it's all works great as long as you are in one platform. And if you want resilience, then Snowflake, Supercloud, great example. But if your primary goal is to choose the most cost-effective service irrespective of which cloud it sits in, then things start falling sideways. For example, I may be a very big Snowflake user. And I like Snowflake's resilience. I can move from one cloud to another cloud. Snowflake does it for me. But what if I want to train a very large model? Maybe Databricks is a better platform for that. So how do I do move my workload from one platform to another platform? That tooling does not exist. So we need server hybrid, cross-cloud, data ops platform. Walmart has done a great job, but they built it by themselves. Not every company is Walmart. Like Maribel and Keith said, we need standards, we need reference architectures, we need some sort of a cost control. I was just reading recently, Accenture has been public about their AWS bill. Every time they get the bill is tens of millions of lines, tens of millions 'cause there are over thousand teams using AWS. If we have not been able to corral a usage of a single cloud, now we're talking about supercloud, we've got multiple clouds, and hybrid, on-prem, and edge. So till we've got some cross-platform tooling in place, I think this will still take quite some time for it to take shape. >> It's interesting. Maribel, Walmart would tell you that their on-prem infrastructure is cheaper to run than the stuff in the cloud. but at the same time, they want the flexibility and the resiliency of their three-legged stool model. So the point as Sanjeev was making about hybrid. It's an interesting balance, isn't it, between getting your lowest cost and at the same time having best of breed and scale? >> It's basically what you're trying to optimize for, as you said, right? And by the way, to the earlier point, not everybody is at Walmart's scale, so it's not actually cheaper for everybody to have the purchasing power to make the cloud cheaper to have it on-prem. But I think what you see almost every company, large or small, moving towards is this concept of like, where do I find the agility? And is the agility in building the infrastructure for me? And typically, the thing that gives you outside advantage as an organization is not how you constructed your cloud computing infrastructure. It might be how you structured your data analytics as an example, which cloud is related to that. But how do you marry those two things? And getting back to sort of Sanjeev's point. We're in a real struggle now where one hand we want to have best of breed services and on the other hand we want it to be really easy to manage, secure, do data governance. And those two things are really at odds with each other right now. So if you want all the knobs and switches of a service like geospatial analytics and big query, you're going to have to use Google tools, right? Whereas if you want visibility across all the clouds for your application of state and understand the security and governance of that, you're kind of looking for something that's more cross-cloud tooling at that point. But whenever you talk to somebody about cross-cloud tooling, they look at you like that's not really possible. So it's a very interesting time in the market. Now, we're kind of layering this concept of supercloud on it. And some people think supercloud's about basically multi-cloud tooling, and some people think it's about a whole new architectural stack. So we're just not there yet. But it's not all about cost. I mean, cloud has not been about cost for a very, very long time. Cloud has been about how do you really make the most of your data. And this gets back to cross-cloud services like Snowflake. Why did they even exist? They existed because we had data everywhere, but we need to treat data as a unified object so that we can analyze it and get insight from it. And so that's where some of the benefit of these cross-cloud services are moving today. Still a long way to go, though, Dave. >> Keith, I reached out to my friends at ETR given the macro headwinds, And you're right, Maribel, cloud hasn't really been about just about cost savings. But I reached out to the ETR, guys, what's your data show in terms of how customers are dealing with the economic headwinds? And they said, by far, their number one strategy to cut cost is consolidating redundant vendors. And a distant second, but still notable was optimizing cloud costs. Maybe using reserve instances, or using more volume buying. Nowhere in there. And I asked them to, "Could you go look and see if you can find it?" Do we see repatriation? And you hear this a lot. You hear people whispering as analysts, "You better look into that repatriation trend." It's pretty big. You can't find it. But some of the Walmarts in the world, maybe even not repatriating, but they maybe have better cost structure on-prem. Keith, what are you seeing from the practitioners that you talk to in terms of how they're dealing with these headwinds? >> Yeah, I just got into a conversation about this just this morning with (indistinct) who is an analyst over at GigaHome. He's reading the same headlines. Repatriation is happening at large scale. I think this is kind of, we have these quiet terms now. We have quiet quitting, we have quiet hiring. I think we have quiet repatriation. Most people haven't done away with their data centers. They're still there. Whether they're completely on-premises data centers, and they own assets, or they're partnerships with QTX, Equinix, et cetera, they have these private cloud resources. What I'm seeing practically is a rebalancing of workloads. Do I really need to pay AWS for this instance of SAP that's on 24 hours a day versus just having it on-prem, moving it back to my data center? I've talked to quite a few customers who were early on to moving their static SAP workloads onto the public cloud, and they simply moved them back. Surprising, I was at VMware Explore. And we can talk about this a little bit later on. But our customers, net new, not a lot that were born in the cloud. And they get to this point where their workloads are static. And they look at something like a Kubernetes, or a OpenShift, or VMware Tanzu. And they ask the question, "Do I need the scalability of cloud?" I might consider being a net new VMware customer to deliver this base capability. So are we seeing repatriation as the number one reason? No, I think internal IT operations are just naturally come to this realization. Hey, I have these resources on premises. The private cloud technologies have moved far along enough that I can just simply move this workload back. I'm not calling it repatriation, I'm calling it rightsizing for the operating model that I have. >> Makes sense. Yeah. >> Go ahead. >> If I missed something, Dave, why we are on this topic of repatriation. I'm actually surprised that we are talking about repatriation as a very big thing. I think repatriation is happening, no doubt, but it's such a small percentage of cloud migration that to me it's a rounding error in my opinion. I think there's a bigger problem. The problem is that people don't know where the cost is. If they knew where the cost was being wasted in the cloud, they could do something about it. But if you don't know, then the easy answer is cloud costs a lot and moving it back to on-premises. I mean, take like Capital One as an example. They got rid of all the data centers. Where are they going to repatriate to? They're all in the cloud at this point. So I think my point is that data observability is one of the places that has seen a lot of traction is because of cost. Data observability, when it first came into existence, it was all about data quality. Then it was all about data pipeline reliability. And now, the number one killer use case is FinOps. >> Maribel, you had a comment? >> Yeah, I'm kind of in violent agreement with both Sanjeev and Keith. So what are we seeing here? So the first thing that we see is that many people wildly overspent in the big public cloud. They had stranded cloud credits, so to speak. The second thing is, some of them still had infrastructure that was useful. So why not use it if you find the right workloads to what Keith was talking about, if they were more static workloads, if it was already there? So there is a balancing that's going on. And then I think fundamentally, from a trend standpoint, these things aren't binary. Everybody, for a while, everything was going to go to the public cloud and then people are like, "Oh, it's kind of expensive." Then they're like, "Oh no, they're going to bring it all on-prem 'cause it's really expensive." And it's like, "Well, that doesn't necessarily get me some of the new features and functionalities I might want for some of my new workloads." So I'm going to put the workloads that have a certain set of characteristics that require cloud in the cloud. And if I have enough capability on-prem and enough IT resources to manage certain things on site, then I'm going to do that there 'cause that's a more cost-effective thing for me to do. It's not binary. That's why we went to hybrid. And then we went to multi just to describe the fact that people added multiple public clouds. And now we're talking about super, right? So I don't look at it as a one-size-fits-all for any of this. >> A a number of practitioners leading up to Supercloud2 have told us that they're solving their cloud complexity by going in monocloud. So they're putting on the blinders. Even though across the organization, there's other groups using other clouds. You're like, "In my group, we use AWS, or my group, we use Azure. And those guys over there, they use Google. We just kind of keep it separate." Are you guys hearing this in your view? Is that risky? Are they missing out on some potential to tap best of breed? What do you guys think about that? >> Everybody thinks they're monocloud. Is anybody really monocloud? It's like a group is monocloud, right? >> Right. >> This genie is out of the bottle. We're not putting the genie back in the bottle. You might think your monocloud and you go like three doors down and figure out the guy or gal is on a fundamentally different cloud, running some analytics workload that you didn't know about. So, to Sanjeev's earlier point, they don't even know where their cloud spend is. So I think the concept of monocloud, how that's actually really realized by practitioners is primary and then secondary sources. So they have a primary cloud that they run most of their stuff on, and that they try to optimize. And we still have forked workloads. Somebody decides, "Okay, this SAP runs really well on this, or these analytics workloads run really well on that cloud." And maybe that's how they parse it. But if you really looked at it, there's very few companies, if you really peaked under the hood and did an analysis that you could find an actual monocloud structure. They just want to pull it back in and make it more manageable. And I respect that. You want to do what you can to try to streamline the complexity of that. >> Yeah, we're- >> Sorry, go ahead, Keith. >> Yeah, we're doing this thing where we review AWS service every day. Just in your inbox, learn about a new AWS service cursory. There's 238 AWS products just on the AWS cloud itself. Some of them are redundant, but you get the idea. So the concept of monocloud, I'm in filing agreement with Maribel on this that, yes, a group might say I want a primary cloud. And that primary cloud may be the AWS. But have you tried the licensed Oracle database on AWS? It is really tempting to license Oracle on Oracle Cloud, Microsoft on Microsoft. And I can't get RDS anywhere but Amazon. So while I'm driven to desire the simplicity, the reality is whether be it M&A, licensing, data sovereignty. I am forced into a multi-cloud management style. But I do agree most people kind of do this one, this primary cloud, secondary cloud. And I guarantee you're going to have a third cloud or a fourth cloud whether you want to or not via shadow IT, latency, technical reasons, et cetera. >> Thank you. Sanjeev, you had a comment? >> Yeah, so I just wanted to mention, as an organization, I'm complete agreement, no organization is monocloud, at least if it's a large organization. Large organizations use all kinds of combinations of cloud providers. But when you talk about a single workload, that's where the program arises. As Keith said, the 238 services in AWS. How in the world am I going to be an expert in AWS, but then say let me bring GCP or Azure into a single workload? And that's where I think we probably will still see monocloud as being predominant because the team has developed its expertise on a particular cloud provider, and they just don't have the time of the day to go learn yet another stack. However, there are some interesting things that are happening. For example, if you look at a multi-cloud example where Oracle and Microsoft Azure have that interconnect, so that's a beautiful thing that they've done because now in the newest iteration, it's literally a few clicks. And then behind the scene, your .NET application and your Oracle database in OCI will be configured, the identities in active directory are federated. And you can just start using a database in one cloud, which is OCI, and an application, your .NET in Azure. So till we see this kind of a solution coming out of the providers, I think it's is unrealistic to expect the end users to be able to figure out multiple clouds. >> Well, I have to share with you. I can't remember if he said this on camera or if it was off camera so I'll hold off. I won't tell you who it is, but this individual was sort of complaining a little bit saying, "With AWS, I can take their best AI tools like SageMaker and I can run them on my Snowflake." He said, "I can't do that in Google. Google forces me to go to BigQuery if I want their excellent AI tools." So he was sort of pushing, kind of tweaking a little bit. Some of the vendor talked that, "Oh yeah, we're so customer-focused." Not to pick on Google, but I mean everybody will say that. And then you say, "If you're so customer-focused, why wouldn't you do a ABC?" So it's going to be interesting to see who leads that integration and how broadly it's applied. But I digress. Keith, at our first supercloud event, that was on August 9th. And it was only a few months after Broadcom announced the VMware acquisition. A lot of people, myself included said, "All right, cuts are coming." Generally, Tanzu is probably going to be under the radar, but it's Supercloud 22 and presumably VMware Explore, the company really... Well, certainly the US touted its Tanzu capabilities. I wasn't at VMware Explore Europe, but I bet you heard similar things. Hawk Tan has been blogging and very vocal about cross-cloud services and multi-cloud, which doesn't happen without Tanzu. So what did you hear, Keith, in Europe? What's your latest thinking on VMware's prospects in cross-cloud services/supercloud? >> So I think our friend and Cube, along host still be even more offended at this statement than he was when I sat in the Cube. This was maybe five years ago. There's no company better suited to help industries or companies, cross-cloud chasm than VMware. That's not a compliment. That's a reality of the industry. This is a very difficult, almost intractable problem. What I heard that VMware Europe were customers serious about this problem, even more so than the US data sovereignty is a real problem in the EU. Try being a company in Switzerland and having the Swiss data solvency issues. And there's no local cloud presence there large enough to accommodate your data needs. They had very serious questions about this. I talked to open source project leaders. Open source project leaders were asking me, why should I use the public cloud to host Kubernetes-based workloads, my projects that are building around Kubernetes, and the CNCF infrastructure? Why should I use AWS, Google, or even Azure to host these projects when that's undifferentiated? I know how to run Kubernetes, so why not run it on-premises? I don't want to deal with the hardware problems. So again, really great questions. And then there was always the specter of the problem, I think, we all had with the acquisition of VMware by Broadcom potentially. 4.5 billion in increased profitability in three years is a unbelievable amount of money when you look at the size of the problem. So a lot of the conversation in Europe was about industry at large. How do we do what regulators are asking us to do in a practical way from a true technology sense? Is VMware cross-cloud great? >> Yeah. So, VMware, obviously, to your point. OpenStack is another way of it. Actually, OpenStack, uptake is still alive and well, especially in those regions where there may not be a public cloud, or there's public policy dictating that. Walmart's using OpenStack. As you know in IT, some things never die. Question for Sanjeev. And it relates to this new breed of data apps. And Bob Muglia and Tristan Handy from DBT Labs who are participating in this program really got us thinking about this. You got data that resides in different clouds, it maybe even on-prem. And the machine polls data from different systems. No humans involved, e-commerce, ERP, et cetera. It creates a plan, outcomes. No human involvement. Today, you're on a CRM system, you're inputting, you're doing forms, you're, you're automating processes. We're talking about a new breed of apps. What are your thoughts on this? Is it real? Is it just way off in the distance? How does machine intelligence fit in? And how does supercloud fit? >> So great point. In fact, the data apps that you're talking about, I call them data products. Data products first came into limelight in the last couple of years when Jamal Duggan started talking about data mesh. I am taking data products out of the data mesh concept because data mesh, whether data mesh happens or not is analogous to data products. Data products, basically, are taking a product management view of bringing data from different sources based on what the consumer needs. We were talking earlier today about maybe it's my vacation rentals, or it may be a retail data product, it may be an investment data product. So it's a pre-packaged extraction of data from different sources. But now I have a product that has a whole lifecycle. I can version it. I have new features that get added. And it's a very business data consumer centric. It uses machine learning. For instance, I may be able to tell whether this data product has stale data. Who is using that data? Based on the usage of the data, I may have a new data products that get allocated. I may even have the ability to take existing data products, mash them up into something that I need. So if I'm going to have that kind of power to create a data product, then having a common substrate underneath, it can be very useful. And that could be supercloud where I am making API calls. I don't care where the ERP, the CRM, the survey data, the pricing engine where they sit. For me, there's a logical abstraction. And then I'm building my data product on top of that. So I see a new breed of data products coming out. To answer your question, how early we are or is this even possible? My prediction is that in 2023, we will start seeing more of data products. And then it'll take maybe two to three years for data products to become mainstream. But it's starting this year. >> A subprime mortgages were a data product, definitely were humans involved. All right, let's talk about some of the supercloud, multi-cloud players and what their future looks like. You can kind of pick your favorites. VMware, Snowflake, Databricks, Red Hat, Cisco, Dell, HP, Hashi, IBM, CloudFlare. There's many others. cohesive rubric. Keith, I wanted to start with CloudFlare because they actually use the term supercloud. and just simplifying what they said. They look at it as taking serverless to the max. You write your code and then you can deploy it in seconds worldwide, of course, across the CloudFlare infrastructure. You don't have to spin up containers, you don't go to provision instances. CloudFlare worries about all that infrastructure. What are your thoughts on CloudFlare this approach and their chances to disrupt the current cloud landscape? >> As Larry Ellison said famously once before, the network is the computer, right? I thought that was Scott McNeley. >> It wasn't Scott McNeley. I knew it was on Oracle Align. >> Oracle owns that now, owns that line. >> By purpose or acquisition. >> They should have just called it cloud. >> Yeah, they should have just called it cloud. >> Easier. >> Get ahead. >> But if you think about the CloudFlare capability, CloudFlare in its own right is becoming a decent sized cloud provider. If you have compute out at the edge, when we talk about edge in the sense of CloudFlare and points of presence, literally across the globe, you have all of this excess computer, what do you do with it? First offering, let's disrupt data in the cloud. We can't start the conversation talking about data. When they say we're going to give you object-oriented or object storage in the cloud without egress charges, that's disruptive. That we can start to think about supercloud capability of having compute EC2 run in AWS, pushing and pulling data from CloudFlare. And now, I've disrupted this roach motel data structure, and that I'm freely giving away bandwidth, basically. Well, the next layer is not that much more difficult. And I think part of CloudFlare's serverless approach or supercloud approaches so that they don't have to commit to a certain type of compute. It is advantageous. It is a feature for me to be able to go to EC2 and pick a memory heavy model, or a compute heavy model, or a network heavy model, CloudFlare is taken away those knobs. and I'm just giving code and allowing that to run. CloudFlare has a massive network. If I can put the code closest using the CloudFlare workers, if I can put that code closest to where the data is at or residing, super compelling observation. The question is, does it scale? I don't get the 238 services. While Server List is great, I have to know what I'm going to build. I don't have a Cognito, or RDS, or all these other services that make AWS, GCP, and Azure appealing from a builder's perspective. So it is a very interesting nascent start. It's great because now they can hide compute. If they don't have the capacity, they can outsource that maybe at a cost to one of the other cloud providers, but kind of hiding the compute behind the surplus architecture is a really unique approach. >> Yeah. And they're dipping their toe in the water. And they've announced an object store and a database platform and more to come. We got to wrap. So I wonder, Sanjeev and Maribel, if you could maybe pick some of your favorites from a competitive standpoint. Sanjeev, I felt like just watching Snowflake, I said, okay, in my opinion, they had the right strategy, which was to run on all the clouds, and then try to create that abstraction layer and data sharing across clouds. Even though, let's face it, most of it might be happening across regions if it's happening, but certainly outside of an individual account. But I felt like just observing them that anybody who's traditional on-prem player moving into the clouds or anybody who's a cloud native, it just makes total sense to write to the various clouds. And to the extent that you can simplify that for users, it seems to be a logical strategy. Maybe as I said before, what multi-cloud should have been. But are there companies that you're watching that you think are ahead in the game , or ones that you think are a good model for the future? >> Yes, Snowflake, definitely. In fact, one of the things we have not touched upon very much, and Keith mentioned a little bit, was data sovereignty. Data residency rules can require that certain data should be written into certain region of a certain cloud. And if my cloud provider can abstract that or my database provider, then that's perfect for me. So right now, I see Snowflake is way ahead of this pack. I would not put MongoDB too far behind. They don't really talk about this thing. They are in a different space, but now they have a lakehouse, and they've got all of these other SQL access and new capabilities that they're announcing. So I think they would be quite good with that. Oracle is always a dark forest. Oracle seems to have revived its Cloud Mojo to some extent. And it's doing some interesting stuff. Databricks is the other one. I have not seen Databricks. They've been very focused on lakehouse, unity, data catalog, and some of those pieces. But they would be the obvious challenger. And if they come into this space of supercloud, then they may bring some open source technologies that others can rely on like Delta Lake as a table format. >> Yeah. One of these infrastructure players, Dell, HPE, Cisco, even IBM. I mean, I would be making my infrastructure as programmable and cloud friendly as possible. That seems like table stakes. But Maribel, any companies that stand out to you that we should be paying attention to? >> Well, we already mentioned a bunch of them, so maybe I'll go a slightly different route. I'm watching two companies pretty closely to see what kind of traction they get in their established companies. One we already talked about, which is VMware. And the thing that's interesting about VMware is they're everywhere. And they also have the benefit of having a foot in both camps. If you want to do it the old way, the way you've always done it with VMware, they got all that going on. If you want to try to do a more cross-cloud, multi-cloud native style thing, they're really trying to build tools for that. So I think they have really good access to buyers. And that's one of the reasons why I'm interested in them to see how they progress. The other thing, I think, could be a sleeping horse oddly enough is Google Cloud. They've spent a lot of work and time on Anthos. They really need to create a certain set of differentiators. Well, it's not necessarily in their best interest to be the best multi-cloud player. If they decide that they want to differentiate on a different layer of the stack, let's say they want to be like the person that is really transformative, they talk about transformation cloud with analytics workloads, then maybe they do spend a good deal of time trying to help people abstract all of the other underlying infrastructure and make sure that they get the sexiest, most meaningful workloads into their cloud. So those are two people that you might not have expected me to go with, but I think it's interesting to see not just on the things that might be considered, either startups or more established independent companies, but how some of the traditional providers are trying to reinvent themselves as well. >> I'm glad you brought that up because if you think about what Google's done with Kubernetes. I mean, would Google even be relevant in the cloud without Kubernetes? I could argue both sides of that. But it was quite a gift to the industry. And there's a motivation there to do something unique and different from maybe the other cloud providers. And I'd throw in Red Hat as well. They're obviously a key player and Kubernetes. And Hashi Corp seems to be becoming the standard for application deployment, and terraform, or cross-clouds, and there are many, many others. I know we're leaving lots out, but we're out of time. Folks, I got to thank you so much for your insights and your participation in Supercloud2. Really appreciate it. >> Thank you. >> Thank you. >> Thank you. >> This is Dave Vellante for John Furrier and the entire Cube community. Keep it right there for more content from Supercloud2.

>>The Cube presents Ignite 22, brought to you by Palo Alto Networks. >>Welcome back everyone. Happy afternoon. It's Lisa Martin and Dave Valante of the Cube. We are live at MGM Grand. This is Palo Alto Ignite 22, our second day of coverage. Dave, we've had some amazing conversations, as we always do on the queue, but cybersecurity one of my favorite topics. So interesting to hear what Palo Alto Networks is doing, how it's differentiating itself and how it's ecosystem is >>Growing. Yeah, well one of the things I always, I often use ServiceNow as a reference example. I go back to 2013, had a kind of a tiny ecosystem and then sort of watched it grow. And one of those key signs was when the global system integrators actually began to lean in Accenture, obviously world class, one of the, you know, definitely in the top, you know, they talk about top five QBs, Accenture, you know, top five GSI easily. >>Yep. So, and in fact, Accenture, we've got Rex Stex in here, senior managing director at Accenture Security. You guys have been the GSI partner of the year for Palo Alto Networks for four years in a row, six years plus strong partnership. Give us a little flavor and history of the pan of the Palo Alto partnership with et cetera. >>I think, you know, we started early, right? And I think as they've evolved, we've evolved our partnership with them and as they've gone, you know, to more of a software footprint with, you know, around cloud security and network security and sassy, we've, we've seen a lot of growth and we're super excited about the opportunity that's ahead of us and the meaningful outcomes that we've been providing our clients as it relates to, you know, vendor consolidation, toll consolidation, tech debt reduction. You know, there's a lot of opportunity here to simplify our clients' lives with them. And that's something we're super excited about. >>Simplification, consolidation, been a theme of the last couple of days. Talk about some of the joint accomplishments that you guys have achieved. I know that you developed a lot of offers across all of Palo Alto Network's, GTMs, what are some of the highlights that come to mind? I >>Think one of the things that we're most excited about, you know, that being client specific is what we've been able to do on, on, on the network side with sasi and, and zero trust, network access. You know, as when Covid hit, there was a lot of change that happened with remote workforce and, you know, clients couldn't log in because their VPNs were crashing left and right. And so we were able to, you know, go in and help stand up, you know, this, you know, zero trust network infrastructure and help our clients get back online and get their employees back to work in a productive manner. And then it's evolved with the hybrid work model over time. And so it's, it's been a, that's probably the most gratifying cause there was a real crisis at, at a certain point in time, you know, a couple years ago were >>There Rex, were there unintended consequences of that, you know, rapid, we were forced, you know, the forced march to digital in terms of just multiple tools, plugging holes, and then sort of stepping back, you know, post isolation economy saying, okay, hey, we got through this, but now we need to take a new direction, new >>Strategy. I think that there, there isn't an intended consequence if you look at, most clients have, I saw a number 76, we counted as around 80 different security vendors and tools that they managed because a lot of people went and went after best of breed type capabilities. And, and so what we've seen now is, is the need to, you know, rationalize that, you know, their, their infrastructure and their, and their capability and, and consolidate and reduce that and, and move to, you know, more of what I would call platform providers. Cause if you may have, when you have 80 products, you have 80 integrations, 80 points of failure, and it gets very complex and, you know, there's a lot of finger pointing. And so as we're starting to see clients take a step back and say, Hey, look, if I, you know, spend the time to, you know, I call it modernization, but you know, modernize my security infrastructure and footprint focused around, you know, automation, orchestration, leveraging, you know, true ml and I know there's are buzzwords, but, you know, but you know, using 'em in, in, in the proper fashion, right? >>They, they can, you know, reduce that footprint, save a bunch of money, right? And, and, and drive that cost savings and then help scale their business. Cuz you have all these different vendors and what security is typically in the digital footprint is the slowdown, right? We, we've typically been the bottleneck in the past. And what we're seeing with, with, with what, you know, we've been very focused on is helping our clients scale their security footprints and their infrastructure and, you know, through automation orchestration, I i, I always say some folks do it your mess for less with labor arbitrage and bodies, but they're not enough security people in the world to do this. And so we're very focused on automation and orchestration and driving that into, into the market. >>Yeah. So you don't want to be in the business of, of filling those holes with labor. >>Exactly. You >>Want to actually get paid for outcomes. >>A hundred percent. And everything we've done is we've tried to simplify things not only for, you know, big Accenture, but even for our clients so that, you know, we can be focused on business outcomes, not necessarily technology outcomes. Cuz doing technology for the sake of technology. Is that unintended consequence that you described earlier, >>Speaking of transformation and outcomes I should say, what are you hearing most from CIOs and CISOs in terms of what they need now to be able to transform, to deliver the business outcomes so that they can become secure data companies regardless of industry? Yep. >>I think the, the biggest thing we're seeing right now is the need to, you know, leverage true automation and orchestration. We have to break the headcount model. There's not enough security professionals in the world to do, you know, to solve the world's problems. In order to scale that, you know, it's one of the reasons we're, you know, partnering with Palo Alto is because of, you know, the capabilities and the investments they've made in innovation to help drive that automation and orchestration through, you know, numerous capabilities from stock transformation to to to sassy cloud security, et cetera. But our clients need scale. They need to be able to go fast and net pace and they need to, they need to do it with confidence securely. And that, that's one of the big focuses. But the other focus is, is we're starting to see a need to, you know, vendor consolidation in the market. You've seen the acquisitions, I'm sure you've talked to people in over the last couple days. You know, there's, there's a, a tremendous amount of consolidation going around. And what our clients, you know, are asking for is, Hey, I need to reduce the number of vendors I interact with. I need to simplify my infrastructure, I need to focus on automation and, and orchestration from that perspective, >>What's happening with multi-cloud? What are you hearing from from customers? You know, we hear a lot of the, the, the conversations about, oh it's, you know, it's, and I agree by the way, multi-cloud is kind of a symptom of multi-vendor, you know, Chuck Whittens thing about multi-cloud by default versus design, you know, it's good, good line and I think rings true, but, but what a customer's telling you in terms of the real challenges generally and then specifically around security. >>I think it's, you know, each cloud service product has their own security capabilities and security models and, and, and being able to train the people to be able to manage those different models. I think that's where, you know, tools like, you know, Prisma Cloud for instance come in and help clients be able to manage the security and compliance of those infrastructures in, in a way to do that. And then to be able to manage applications security consistently, right? It's not just the cloud itself, but it's actually the applications that may, you know, cross, you know, be for, for resiliency but you know, be in, you know, multi-cloud, you know, multiple clouds and being able to make sure you have consistent security across those. And I think, you know, one of the things that it's permeated is, is just the, with data and identity and, and you know, cloud infrastructure and tolerance management, it's been a big problem cuz it's like the wild, wild west. I always look, when I look at identity and the cloud and how it's done, it, it looks like 1995 identity. It's, it's, it's ridiculously backwards. And so, you know, we've seen things like, you know, keem that have come into play to help manage those relationships and, and simplify it across multiple clouds consistently, if that makes sense. >>Yep. >>You, you mentioned Prisma Cloud most recently Accenture and Palo Alto developed the Secure Cloud Express. Correct. Can you talk to us a little bit about what that is and what outcomes is it gonna enable? Yeah, >>So great question and we're pretty excited about this cuz what we did with that was we manage cloud, you know, our cloud environments for numerous customers. So we've developed hundreds of policies that, you know, we implemented in Prisma Cloud to manage, you know, multiple clients, our internal infrastructure. And what we did was we said, well, most of our clients have to build those from scratch. So what we said is we will come in, in the best of week of time and come in and, and do a data-driven exercise to show our clients, you know, where where they sit from a, from a security perspective as it relates leveraging Prisma cloud and, and those policies that we've created. And what, what that has led to is another step, which is where we're focused on auto remediation. So, you know, when you, when you get, when you get the findings, then what do you do with them, right? If you have hundreds or thousands in some cases we've had clients with 1100 findings and they just sit there and they go, whoa, you know, so to speak. And so what we've done is we try to take those highest, most frequent findings and build securities code to auto remediate those for clients so they can choose to implement that and work down those, you know, findings very quickly, which helps, you know, drive more value out of, out of their prisma cloud >>Purchases. Accenture obviously has deep industry expertise around the globe. What are you seeing in terms of industries actually? So as they digitize not just their IT transformation but a business transformation, there are starting to see companies, financial services in particular bring their business to their cloud, sify their business. And specifically I'm interested in what's happening at the edge with operations technology. We just talked about healthcare and and medical devices. What's happening there? How connected or disconnected is that to the rest of the estate, the multi-cloud on-prem, et cetera? I >>Mean, I think OT is, is fairly disconnected, right? Sure. From, from that perspective, obviously, but I, I, I think what we're starting to see is an uptick, you know, on, I think secure edge and Sassy will come to OT cause it's a better way. Because what happens is if someone, you know, gets into the network, they can traverse it, right? And if they can apply those zero trust principles to ot, which is you're talking to people that have been, you know, wearing hard hats Yeah. And engineers, that's a big shift for them. And so, but I think that you'll start to see that play more prevalence, you know, with the industries like, you know, financial services, we're seeing a huge uptick in cloud adoption, right? They were, they were slow to do it, but now they're, they're going at pace and faster than most, right? Yeah, sure. And I think, you know, healthcare is a, is another big one where we've seen a lot of migration and a lot of need for multi-cloud. Cuz you know, some, they may be running their analytics on, you know, Google and, and their workloads on Azure, right? Or aws. And so you're starting to see a lot of people leveraging the best of what each cloud provider does well >>From that. And, and just an aside on that Palo Alto survey, we saw construction was one of the hardest hit industries. Yeah. Which I, I was like, what? And then of course it's because they're not really focused on security. They're focused on building stuff. No, >>It's really interesting. We're working with a large builder, I can't say the name, but one of the things that they're looking to do is, you know, they're moving to the cloud and they're building the capability to manage some of the, you know, largest skyscrapers in the world, but also manage the OT sensors and also do selling that creating another business, not only just managing those buildings, but managing other people's buildings for them and ha and selling security as a service for that because they built that capability around their devices and, and, and switches, hvac, et cetera. Do, >>Do you think that because I mean, you know, the operations technology, they're engineers and they're hardcore, like, don't touch my stuff. Exactly. And so do you feel like as, I mean I know that business has kind of done a reach around everything, you know, be becoming connected, but do you feel like they're gonna be more on top of it then, then, then sort of the, the broad commercial market has been? Or is it gonna be wild West all over again? >>My hope is that, you know, us as gsi, you know, my fellow GSIs, that we will help our clients make the better decisions this time around and, and not go to the wild, wild west. And you know, we see a lot of it in manufacturing, you know, if you saw, you know, with the, you know, the invasion Ukraine, you know, one of the big groups that was hit was manufacturing, right? There was factory shut down all over the world, you know, and, and so, you know, and that is an OT environment, but I, you know, what we've seen is them are, you know, those clients take more serious steps to protect those environments cuz they're on, you know, windows 10 servers running, you know, large machines. So we're starting to see a lot more care and feeding in into those environments as well. >>Can I ask you a question about the conversations that you're having? That survey that Dave mentioned, it's was released yesterday. There's a board behind us, what's next in cyber? That was the survey and amazing data that came from it. Like 96% of organizations have been hit by at least one attack in the last year. They were surprised that the number was that high, but we know that no industry, no company is safe. But one of the things that the survey found that, that surprised me was that we always say, oh, security is a board level conversation. We know that to some degree. But what they found was lack of alignment between the board and the executive level. In your Accenture's relationships, I know you guys have deep relationships across organizations and their boards. Can you help bring the board together with the executives and, and really not just talk about cybersecurity, but really develop a cybersecurity transformation strategy that actually delivers resilience? >>Yeah, no ab absolutely. And we've, we, we actually took a step back and, and reorganized our business this last year. And one of those areas that we focused on was within strategy and the C-suite agenda, right? And we actually published looking at gia, it was either the CEO handbook, I think it's what we called it, but they helped them and board be able to, you know, drive more meaningful conversations that relates to risk and and whatnot. And so we're very focused on that right now. And it's, we need to up-level our conversations within the organization. Cause even the buyers in these large, you know, two years ago was mainly the cso, now we're dealing with the cio, CTOs, cfo because these are, you know, meaningful business conversations, right? That are driving business outcomes and security needs to be a business enabler, not, not a a, a bottleneck >>Is the chief data officer starting to emerge as, as we see, you know, Nikesh said yesterday in his keynote and we talked about it with him when he was here, security is a data problem. >>Yep. It is. It's a huge data problem. And we're starting to, you know, I think we've talked a lot about zero trust, but zero trust data is, is a, is a significant problem, right? Because that you talk about the wild, wild west is we see clients that have people that have in, you know, they, they have access to, you know, what we call dev development environment data, right? But then you find out that they can hop four levels over into production data and this been exposed to, you know, the wrong people, you know, not focused on that least privileged aspect. I think data's a real problem, you know, per na kesha's statement in the cloud. It's something that really needs to be addressed. And I think we're starting to see a lot of innovation around that area. Cuz what typical data security has always been, I have all these problems, it creates, I call it noise, right? I got thousands of findings and then just, you know, need just sit there and they go, what do I do? Right? It's too much. And so I think there, there's gonna be more intelligence around that and more, you know, what I call auto remediation, right? Being able to remediate those findings quickly from from that >>Perspective. I've been watching this board behind us. Yeah. It's this what's next in cyber. And people come in and they write, it's just been growing, you know, all week and somebody just wrote sock transformation. Yeah. We were just sort of talking about earlier what, what, in your estimation, what percent of organizations that you target. I understand that you're not going after the, you know, mom and pop organizations, but what percent of that, you know, fat middle and the tip of the pyramid, that a euro, that's your sweet spot. What percent of those organizations don't have a sock? >>I mean, most every organization has a sock. You know, I talked to, you know, CISOs of large financial service organization, they said, do we even need a sock anymore? It could be a virtual sock so to speak, but I think, you know, am was SOC transformation. I think we could potentially head to something like that. But you know, but what's really been strange is there's been, you know, what we call soar, right? Security, you know, orchestration, automation, whatever. And what another, >>Another acronym, their >>Acronym that I security that I might brain is >>Hold apologize. >>But you know, they've, people have never really driven the value out of it because they build these automation playbooks and, and for one company to do it and build 20 of 'em or 30 of 'em to ha it doesn't pay off in the long run. And what we're starting to see is people, you know, bring to the table more crowdsource these capabilities so that they can scale those sock transformations. Cause it's really about, you know, orchestration and automation. That's where, you know, nirvana comes in because it's not about people with headsets on looking at, you know, 20 screens. It's not helpful, right? The humans, we make mistakes. And so if we can automate as much of that as possible, get rid of the false positives, leverage AI and and ML to do that. And I think we're starting to see, you know, what I would call more advanced AI and ml. I think in the early days in security, AI and ML was very nascent and, and, and now you're starting to see, you know, more powerful concepts come in better learning, better outcomes out of that. >>Well, it was a lot of modeling in the cloud still is, but it's increasingly going toward real time inference and that's, you know, game changing. >>Agreed. >>Last question for you. What's are some of the things that are next on the plate for Accenture and Palo Networks? What's next up? >>I think, you know, we're very focused on, on Sassy right now in, in the market. And I think we think that is, you know, I think both of us think that's the next big wave, right? Because I think what we learned out of, you know, these last two and a half, three years is that these concepts work, but they can actually scale out to drive significant cost savings. I mean, if you look at Accenture, you know, we don't have a a network backbone anymore. We're pure cloud wan, right? We're leveraging the internet for that. And I think that and what we're trying to do with Palo Alto and driving, you know, cloud WAN and Sassy as a service, I think will be super, super meaningful. And, and, and, and >>Well that's interesting. That has implications for a number of companies out >>There. Yeah. Well I think, you know, it's obviously the, you know, it, it's a, it is a big implication for a lot of, a lot of, you know, our customers even, right? Yeah. And so we have to be very careful and thoughtful about how we work to make that happen over time. >>Right. A lot of opportunity. Rex, thank you so much for joining us on the program and really dissecting what Accenture and Palo Alto are doing, all the value in it for organizations across industries. We appreciate your insights. Yep. >>Thank you >>For Rex Dexon and Dave Valante. I'm Lisa Martin, you're watching the Cubes stick around. Dave and I will be right back with our next guest. This is the Cube, the leader in live, emerging and enterprise tech coverage.

foreign welcome back to re invent 2022 we're wrapping up four days well one evening and three solid days wall-to-wall of cube coverage I'm Dave vellante John furrier's birthday is today he's on a plane to London to go see his nephew get married his his great Sister Janet awesome family the furriers uh spanning the globe and uh and John I know you wanted to be here you're watching in Newark or you were waiting to uh to get in the plane so all the best to you happy birthday one year the Amazon PR people brought a cake out to celebrate John's birthday because he's always here at AWS re invented his birthday so I'm really pleased to have two really special guests uh former Cube host Cube Alum great wikibon contributor Stu miniman now with red hat still good to see you again great to be here Dave yeah I was here for that cake uh the twitterverse uh was uh really helping to celebrate John's birthday today and uh you know always great to be here with you and then with this you know Awesome event this week and friend of the cube of many time Cube often Cube contributor as here's a cube analyst this week as his own consultancy sarbj johal great to see you thanks for coming on good to see you Dave uh great to see you stu I'm always happy to participate in these discussions and um I enjoy the discussion every time so this is kind of cool because you know usually the last day is a getaway day and this is a getaway day but this place is still packed I mean it's I mean yeah it's definitely lighter you can at least walk and not get slammed but I subjit I'm going to start with you I I wanted to have you as the the tail end here because cause you participated in the analyst sessions you've been watching this event from from the first moment and now you've got four days of the Kool-Aid injection but you're also talking to customers developers Partners the ecosystem where do you want to go what's your big takeaways I think big takeaways that Amazon sort of innovation machine is chugging along they are I was listening to some of the accessions and when I was back to my room at nine so they're filling the holes in some areas but in some areas they're moving forward there's a lot to fix still it doesn't seem like that it seems like we are done with the cloud or The Innovation is done now we are building at the millisecond level so where do you go next there's a lot of room to grow on the storage side on the network side uh the improvements we need and and also making sure that the software which is you know which fits the hardware like there's a specialized software um sorry specialized hardware for certain software you know so there was a lot of talk around that and I attended some of those sessions where I asked the questions around like we have a specialized database for each kind of workload specialized processes processors for each kind of workload yeah the graviton section and actually the the one interesting before I forget that the arbitration was I asked that like why there are so many so many databases and IRS for the egress costs and all that stuff can you are you guys thinking about reducing that you know um the answer was no egress cost is not a big big sort of uh um show stopper for many of the customers but but the from all that sort of little discussion with with the folks sitting who build these products over there was that the plethora of choice is given to the customers to to make them feel that there's no vendor lock-in so if you are using some open source you know um soft software it can be on the you know platform side or can be database side you have database site you have that option at AWS so this is a lot there because I always thought that that AWS is the mother of all lock-ins but it's got an ecosystem and we're going to talk about exactly we'll talk about Stu what's working within AWS when you talk to customers and where are the challenges yeah I I got a comment on open source Dave of course there because I mean look we criticized to Amazon for years about their lack of contribution they've gotten better they're doing more in open source but is Amazon the mother of all lock-ins many times absolutely there's certain people inside Amazon I'm saying you know many of us talk Cloud native they're like well let's do Amazon native which means you're like full stack is things from Amazon and do things the way that we want to do things and you know I talk to a lot of customers they use more than one Cloud Dave and therefore certain things absolutely I want to Leverage The Innovation that Amazon has brought I do think we're past building all the main building blocks in many ways we are like in day two yes Amazon is fanatically customer focused and will always stay that way but you know there wasn't anything that jumped out at me last year or this year that was like Wow new category whole new way of thinking about something we're in a vocals last year Dave said you know we have over 200 services and if we listen to you the customer we'd have over two thousand his session this week actually got some great buzz from my friends in the serverless ecosystem they love some of the things tying together we're using data the next flywheel that we're going to see for the next 10 years Amazon's at the center of the cloud ecosystem in the IT world so you know there's a lot of good things here and to your point Dave the ecosystem one of the things I always look at is you know was there a booth that they're all going to be crying in their beer after Amazon made an announcement there was not a tech vendor that I saw this week that was like oh gosh there was an announcement and all of a sudden our business is gone where I did hear some rumbling is Amazon might be the next GSI to really move forward and we've seen all the gsis pushing really deep into supporting Cloud bringing workloads to the cloud and there's a little bit of rumbling as to that balance between what Amazon will do and their uh their go to market so a couple things so I think I think we all agree that a lot of the the announcements here today were taping seams right I call it and as it relates to the mother of all lock-in the reason why I say that it's it's obviously very much a pejorative compare Oracle company you know really well with Amazon's lock-in for Amazon's lock-in is about bringing this ecosystem together so that you actually have Choice Within the the house so you don't have to leave you know there's a there's a lot to eat at the table yeah you look at oracle's ecosystem it's like yeah you know oracle is oracle's ecosystem so so that is how I think they do lock in customers by incenting them not to leave because there's so much Choice Dave I agree with you a thousand I mean I'm here I'm a I'm a good partner of AWS and all of the partners here want to be successful with Amazon and Amazon is open to that it's not our way or get out which Oracle tries how much do you extract from the overall I.T budget you know are you a YouTube where you give the people that help you create a large sum of the money YouTube hasn't been all that profitable Amazon I think is doing a good balance of the ecosystem makes money you know we used to talk Dave about you know how much dollars does VMware make versus there um I think you know Amazon is a much bigger you know VMware 2.0 we used to think talk about all the time that VMware for every dollar spent on VMware licenses 15 or or 12 or 20 were spent in the ecosystem I would think the ratio is even higher here sarbji and an Oracle I would say it's I don't know yeah actually 1 to 0.5 maybe I don't know but I want to pick on your discussion about the the ecosystem the the partner ecosystem is so it's it's robust strong because it's wider I was I was not saying that there's no lock-in with with Amazon right AWS there's lock-in there's lock-in with everything there's lock-in with open source as well but but the point is that they're they're the the circle is so big you don't feel like locked in but they're playing smart as well they're bringing in the software the the platforms from the open source they're picking up those packages and saying we'll bring it in and cater that to you through AWS make it better perform better and also throw in their custom chips on top of that hey this MySQL runs better here so like what do you do I said oh Oracle because it's oracle's product if you will right so they are I think think they're filing or not slenders from their go to market strategy from their engineering and they listen to they're listening to customers like very closely and that has sort of side effects as well listening to customers creates a sprawl of services they have so many services and I criticized them last year for calling everything a new service I said don't call it a new service it's a feature of a existing service sure a lot of features a lot of features this is egress our egress costs a real problem or is it just the the on-prem guys picking at the the scab I mean what do you hear from customers so I mean Dave you know I I look at what Corey Quinn talks about all the time and Amazon charges on that are more expensive than any other Cloud the cloud providers and partly because Amazon is you know probably not a word they'd use they are dominant when it comes to the infrastructure space and therefore they do want to make it a little bit harder to do that they can get away with it um because um yeah you know we've seen some of the cloud providers have special Partnerships where you can actually you know leave and you're not going to be charged and Amazon they've been a little bit more flexible but absolutely I've heard customers say that they wish some good tunning and tongue-in-cheek stuff what else you got we lay it on us so do our players okay this year I think the focus was on the upside it's shifting gradually this was more focused on offside there were less talk of of developers from the main stage from from all sort of quadrants if you will from all Keynotes right so even Werner this morning he had a little bit for he was talking about he he was talking he he's job is to Rally up the builders right yeah so he talks about the go build right AWS pipes I thought was kind of cool then I said like I'm making glue easier I thought that was good you know I know some folks don't use that I I couldn't attend the whole session but but I heard in between right so it is really adopt or die you know I am Cloud Pro for last you know 10 years and I think it's the best model for a technology consumption right um because of economies of scale but more importantly because of division of labor because of specialization because you can't afford to hire the best security people the best you know the arm chip designers uh you can't you know there's one actually I came up with a bumper sticker you guys talked about bumper sticker I came up with that like last couple of weeks The Innovation favorite scale they have scale they have Innovation so that's where the Innovation is and it's it's not there again they actually say the market sets the price Market you as a customer don't set the price the vendor doesn't set the price Market sets the price so if somebody's complaining about their margins or egress and all that I think that's BS um yeah I I have a few more notes on the the partner if you you concur yeah Dave you know with just coming back to some of this commentary about like can Amazon actually enable something we used to call like Community clouds uh your companies like you know Goldman and NASDAQ and the like where Industries will actually be able to share data uh and you know expand the usage and you know Amazon's going to help drive that API economy forward some so it's good to see those things because you know we all know you know all of us are smarter than just any uh single company together so again some of that's open source but some of that is you know I think Amazon is is you know allowing Innovation to thrive I think the word you're looking for is super cloud there well yeah I mean it it's uh Dave if you want to go there with the super cloud because you know there's a metaphor for exactly what you described NASDAQ Goldman Sachs we you know and and you know a number of other companies that are few weeks at the Berkeley Sky Computing paper yeah you know that's a former supercloud Dave Linthicum calls it metacloud I'm not really careful I mean you know I go back to the the challenge we've been you know working at for a decade is the distributed architecture you know if you talk about AI architectures you know what lives in the cloud what lives at the edge where do we train things where do we do inferences um locations should matter a lot less Amazon you know I I didn't hear a lot about it this show but when they came out with like local zones and oh my gosh out you know all the things that Amazon is building to push out to the edge and also enabling that technology and software and the partner ecosystem helps expand that and Pull It in it's no longer you know Dave it was Hotel California all of the data eventually is going to end up in the public cloud and lock it in it's like I don't think that's going to be the case we know that there will be so much data out at the edge Amazon absolutely is super important um there some of those examples we're giving it's not necessarily multi-cloud but there's collaboration happening like in the healthcare world you know universities and hospitals can all share what they're doing uh regardless of you know where they live well Stephen Armstrong in the analyst session did say that you know we're going to talk about multi-cloud we're not going to lead with it necessarily but we are going to actually talk about it and that's different to your points too than in the fullness of time all the data will be in the cloud that's a new narrative but go ahead yeah actually Amazon is a leader in the cloud so if they push the cloud even if they don't say AWS or Amazon with it they benefit from it right and and the narrative is that way there's the proof is there right so again Innovation favorite scale there are chips which are being made for high scale their software being tweaked for high scale you as a Bank of America or for the Chrysler as a typical Enterprise you cannot afford to do those things in-house what cloud providers can I'm not saying just AWS Google cloud is there Azure guys are there and few others who are behind them and and you guys are there as well so IBM has IBM by the way congratulations to your red hat I know but IBM won the award um right you know very good partner and yeah but yeah people are dragging their feet people usually do on the change and they are in denial denial they they drag their feet and they came in IBM director feed the cave Den Dell drag their feed the cave in yeah you mean by Dragon vs cloud deniers cloud deniers right so server Huggers I call them but they they actually are sitting in Amazon Cloud Marketplace everybody is buying stuff from there the marketplace is the new model OKAY Amazon created the marketplace for b2c they are leading the marketplace of B2B as well on the technology side and other people are copying it so there are multiple marketplaces now so now actually it's like if you're in in a mobile app development there are two main platforms Android and Apple you first write the application for Apple right then for Android hex same here as a technology provider as and I I and and I actually you put your stuff to AWS first then you go anywhere else yeah they are later yeah the Enterprise app store is what we've wanted for a long time the question is is Amazon alone the Enterprise app store or are they partner of a of a larger portfolio because there's a lot of SAS companies out there uh that that play into yeah what we need well and this is what you're talking about the future but I just want to make a point about the past you talking about dragging their feet because the Cube's been following this and Stu you remember this in 2013 IBM actually you know got in a big fight with with Amazon over the CIA deal you know and it all became public judge wheeler eviscerated you know IBM and it ended up IBM ended up buying you know soft layer and then we know what happened there and it Joe Tucci thought the cloud was Mosey right so it's just amazing to see we have booksellers you know VMware called them books I wasn't not all of them are like talking about how great Partnerships they are it's amazing like you said sub GC and IBM uh with the the GSI you know Partnership of the year but what you guys were just talking about was the future and that's what I wanted to get to is because you know Amazon's been leading the way I I was listening to Werner this morning and that just reminded me of back in the days when we used to listen to IBM educate us give us a master class on system design and decoupled systems and and IO and everything else now Amazon is you know the master educator and it got me thinking how long will that last you know will they go the way of you know the other you know incumbents will they be disrupted or will they you know keep innovating maybe it's going to take 10 or 20 years I don't know yeah I mean Dave you actually you did some research I believe it was a year or so ago yeah but what will stop Amazon and the one thing that worries me a little bit um is the two Pizza teams when you have over 202 Pizza teams the amount of things that each one of those groups needs to take care of was more than any human could take care of people burn out they run out of people how many amazonians only last two or three years and then leave because it is tough I bumped into plenty of friends of mine that have been you know six ten years at Amazon and love it but it is a tough culture and they are driving werner's keynote I thought did look to from a product standpoint you could say tape over some of the seams some of those solutions to bring Beyond just a single product and bring them together and leverage data so there are some signs that they might be able to get past some of those limitations but I still worry structurally culturally there could be some challenges for Amazon to keep the momentum going especially with the global economic impact that we are likely to see in the next year bring us home I think the future side like we could talk about the vendors all day right to serve the community out there I think we should talk about how what's the future of technology consumption from the consumer side so from the supplier side just a quick note I think the only danger AWS has has that that you know Fred's going after them you know too big you know like we will break you up and that can cause some disruption there other than that I think they they have some more steam to go for a few more years at least before we start thinking about like oh this thing is falling apart or anything like that so they have a lot more they have momentum and it's continuing so okay from the I think game is on retail by the way is going to get disrupted before AWS yeah go ahead from the buyer's side I think um the the future of the sort of Technology consumption is based on the paper uh use and they actually are turning all their services to uh they are sort of becoming serverless behind the scenes right all analytics service they had one service left they they did that this year so every service is serverless so that means you pay exactly for the amount you use the compute the iops the the storage so all these three layers of course Network we talked about the egress stuff and that's a problem there because of the network design mainly because Google has a flatter design and they have lower cost so so they are actually squeezing the their their designing this their services in a way that you don't waste any resources as a buyer so for example very simple example when early earlier In This Cloud you will get a VM right in Cloud that's how we started so and you can get 20 use 20 percent of the VM 80 is getting wasted that's not happening now that that has been reduced to the most extent so now your VM grows as you grow the usage and if you go higher than the tier you picked they will charge you otherwise they will not charge you extra so that's why there's still a lot of instances like many different types you have to pick one I think the future is that those instances will go away the the instance will be formed for you on the fly so that is the future serverless all right give us bumper sticker Stu and then Serb G I'll give you my quick one and then we'll wrap yeah so just Dave to play off of sharp G and to wrap it up you actually wrote about it on your preview post for here uh serverless we're talking about how developers think about things um and you know Amazon in many ways you know is the new default server uh you know for the cloud um and containerization fits into the whole serverless Paradigm uh it's the space that I live in uh you know every day here and you know I was happy to see the last few years serverless and containers there's a blurring a line and you know subject we're still going to see VMS for a long time yeah yeah we will see that so give us give us your book Instagram my number six is innovation favorite scale that's my bumper sticker and and Amazon has that but also I I want everybody else to like the viewers to take a look at the the Google Cloud as well as well as IBM with others like maybe you have a better price to Performance there for certain workloads and by the way one vendor cannot do it alone we know that for sure the market is so big there's a lot of room for uh Red Hats of the world and and and Microsoft's the world to innovate so keep an eye on them they we need the competition actually and that's why competition Will Keep Us to a place where Market sets the price one vendor doesn't so the only only danger is if if AWS is a monopoly then I will be worried I think ecosystems are the Hallmark of a great Cloud company and Amazon's got the the biggest and baddest ecosystem and I think the other thing to watch for is Industries building on top of the cloud you mentioned the Goldman Sachs NASDAQ Capital One and Warner media these all these industries are building their own clouds and that's where the real money is going to be made in the latter half of the 2020s all right we're a wrap this is Dave Valente I want to first of all thank thanks to our great sponsors AWS for for having us here this is our 10th year at the cube AMD you know sponsoring as well the the the cube here Accenture sponsor to third set upstairs upstairs on the fifth floor all the ecosystem partners that came on the cube this week and supported our mission for free content our content is always free we try to give more to the community and we we take back so go to thecube.net and you'll see all these videos go to siliconangle com for all the news wikibon.com I publish weekly a breaking analysis series I want to thank our amazing crew here you guys we have probably 30 35 people unbelievable our awesome last session John Walls uh Paul Gillen Lisa Martin Savannah Peterson John Furrier who's on a plane we appreciate Andrew and Leonard in our ear and all of our our crew Palo Alto Boston and across the country thank you so much really appreciate it all right we are a wrap AWS re invent 2022 we'll see you in two weeks we'll see you two weeks at Palo Alto ignite back here in Vegas thanks for watching thecube the leader in Enterprise and emerging Tech coverage [Music]

(upbeat music) >> Hello, everyone. Welcome to theCUBE's coverage here at AWS re:Invent 2022. This is the Executive Summit with Accenture. I'm John Furrier, your host of theCUBE with two great guests coming on today, really talking about the future, the role of humans. Radically human is going to be the topic. Paul Daugherty, the group Chief Executive Technology and CTO at Accenture. And Jim Wilson, Global Managing Director of Thought Leadership and Technology Research, Accenture. Gentlemen, thank you for coming on theCUBE for this conversation around your new hit book, "Radically Human." >> Thanks, John. It's great to be with you and great to be present at re:Invent. >> We've been following you guys for many, many years now, over a decade. You always have the finger on the pulse. I mean, and as these waves come in, it's really important to understand impact. And more than ever, we're in this, I call it the systems thinking, revolution is going on now where things have consequences and machines are now accelerating their role. Developers are becoming the front lines of running companies, seeing a massive shift. This new technology is transforming the business and shaping our future as as humans. And so I love the book, very, very strong content, really right on point. What was the motivation for the book? And congratulations, but I noticed you got the structure, part one and part two, this book seems to be packing a big punch. What was the motivation, and what was some of the background in putting the book together? >> That's a great question, John. And I'll start, and then, Jim, my co-author and colleague and partner on the book can join in too. If you step back from the book itself, we'd written a first book called "Human + Machine", which focused a lot on artificial intelligence and talked about the potential and future of artificial intelligence to create a more human future for us with the human plus machine pairing. And then when we started working on the next book, it was the COVID era. COVID came on line as we were writing the book. And that was causing really an interesting time in technology for a lot of companies. I mean, think back to what you were doing. Once COVID hit, every company became more dependent on technology. Technology was the lifeline. And so Jim and I got interested in what the impacts of that were on companies, and what was different from the first research we had done around our first book. And what we found, which was super interesting, is that pre-pandemic, the leading companies, the digital leaders that were applying cloud data, AI, and related technologies faster, we're outperforming others by a factor of 2x. And that was before the pandemic. After the pandemic, we redid the research and the gap widened into 5x. And I think that's played a lot into our book. And we talk about that in the opening of our book. And the message there is exactly what you said is technology is not just the lifeline from the pandemic, but now technology is the heart and soul of how companies are driving innovation, how they're responding to global crises around inflation, energy, supply chain crisis because of the war in Ukraine, et cetera. And companies need the technology more than ever. And that's what we're writing about in "Radically Human." And we're taking a step beyond our previous book to talk about what we believe is next. And it's really cloud, data and AI, and the metaverse that signal out as three trends that are really driving transformative change for companies. In the first part of the book, to your question on the structure, talks about the roadmap to that. We talked about the ideas framework, five areas where you need to change your thinking, flip your assumptions on how to apply technology. And then the second part of the book talks about the differentiators that we believe are going to set companies apart as they look to implement this technology and transform their companies for the future. >> Jim, weigh in on this flipping the script, flipping the assumptions. >> You used a really important word there and that is systems. I think when we think about artificial intelligence, and when Paul and I have now talking to companies, a lot of executives think of AI as a point solution. They don't think about AI in terms of taking a systems approach. So we were trying to address that. All right, if you're going to build a roadmap, a technology roadmap for applying intelligent technologies like artificial intelligence, how do you take a holistic systematic view? And that's really the focus of the first section of the book. And then as Paul mentioned, how do you take those systems and really differentiate it using your talent, focusing on trust, experiences and sustainability? >> I like how it reads. It's almost like a masterclass book because you set the table. It's like, 'cause people right now are like in the mode of what's going on around me? I've been living through three years of COVID. We're coming out the other side. The world looks radically different. Humans are much more important. Automation's great, but people are finding out that the human's key, but people are trying to figure out where am I today. So I think the first part really to me hits home. Like, here's the current situation and then part two is here's how you can get better. And it's not just about machines, machines, machines and automation, automation, automation. We're seeing examples where the role of the human, the person in society, whether it's individually or as part of a group, are really now key assets in that kind of this new workforce or this new production system or society. >> Yeah. And just to take a couple examples from the book and highlight that, I think you're exactly right. And that's where "Radically Human", the title came from. And what's happening with technology is that technology itself is becoming more human like in its capability. When you think about the power of the transformer technologies and other things that we're reading about a lot. And the whole hypothesis or premise of the book I should say, is that the more human like the technology is, the more radically human or the more radical the human potential improvement is, the bigger the opportunity. It's pairing the two together rather than, as you said, just looking at the automation or the machine side of it. That's really the radical leap. And one thing Jim and I talked about in context of the book is companies really often haven't been radical enough in applying technology to really get to dramatic gains that they can get. Just a couple examples from the ideas framework, the I in IDEAS. The ideas framework is the first part of the book. The five areas to flip your assumptions. The I stands for intelligence and we're talking about more human and less artificial in terms of the intelligence techniques. Things like common sense learning and other techniques that allow you to develop more powerful ways of engaging people, engaging humans in the systems that we build using the kind of systems thinking that Jim mentioned. And things like emotional AI, common sense AI, new techniques in addition to machine, the big data driven machine learning techniques, which are essential to vision and solving big problems like that. So that's just an example of how you bring it together and enable that human potential. >> I love the idea, go ahead Jim. >> I was going to say we've been used to adapting to technology, and contorting our fingers to keyboards and so on for a long time. And now we're starting to see that technology is in fact beginning to adapt to us and become more natural in many instances. One point that we make is now in the human technology nexus, in fact, the human is in the ascended. That's one of the big ideas that we try to put out there in this book. >> I love the idea of flipping the script, flipping the assumptions, but ideas framework is interesting. I for intelligence, D for data, E for expertise, A for architecture, S for strategy. Notice the strategies last. Normally in the old school days, it's like, hey, strategy first and execution. Really interesting how you guys put that together. It feels like business is becoming agile and iterative and how it's going to be forming. Can you guys, I mean that's my opinion, but I think observing how developers becoming much more part of the app. I mean, if you take digital transformation to its conclusion, the application is the company, It's not a department serving the business, it is the business, therefore developers are running the business, so to speak. This is really radical. I mean, this is how I'm seeing it. What's your reaction to that? Do you see similar parallels to this transformation if you take it down to a conclusion and strategy is just what you do after you get the outcomes you need? What's your reaction to that? >> Yeah, I think one of the most lasting elements of the book might be that chapter on strategy in my opinion, because you need to think about it differently. The old way of doing strategy is dead. You can't do it the way you used to do it. And that's what we tried to lay out with the S in IDEAS, the strategy. The subtitle that chapter is we're all technology companies now. And if you're a technology driven company, the way you need to think about and every company is becoming, that's what I hear when I talk to these suites and CEOs and boards, is everybody's recognizing the essential role that technology plays and therefore they need to master technology. Well, you need to think about strategy differently then because of the pace of technology innovation. And so you need to throw out the old way of doing it. We suggest three new archetypes of how to do strategy that I think are really important. It's about continuous strategy in all cases. An example is one of the techniques we talk about, forever beta, which is, think about a Tesla or companies that it's never quite done. They're always improving and the product is designed to be connected and improving. So it changes along the product and the strategy along how you deploy it to consumers changes as you go. And that's an example of a very different approach to strategy that we believe is essential to consider as you look at the future. Yeah, those multi-month strategy sessions might play out over two or three quarters of going away. And strategy and execution are becoming almost simultaneous these days as Paul was saying. >> It's interesting because that's the trend you're seeing with more data, more automation, but the human plays a much critical role. And just aside on the Tesla example, is well documented. I think I wrote about in a post just this week that during the model three, Elon wanted full automation and had to actually go off scripts and get to humans back in charge 'cause it wasn't working properly. Now they have a balance. But that brings up to part two, which I like, which is this human piece of it. We always talk about skills gaps, there's not enough people to do this, that and the other thing. And talent was a big part of that second half, trust, talent, experiences. That's more of the person's role, either individually as part of a collective group. Is talent the scarce resource now where that's the goal, that's the key 'cause it all could point to that in a way. Skills gap points to, hey, humans are valuable. In fact the value's going up if it's properly architected. What's your reaction to that, guys? Because I think that's something that is not, kind of nuanced point, but it's a feature, not a bug maybe, I don't know. What's your thoughts? >> Yeah, go ahead Jim. >> I was going to say it, we're dramatically underestimating the amount of focus we need to put on talent. That's why we start off that second part of the book, really zooming in on talent. I think you might think that for every hundred dollars that you put into a technology initiative, you might put 50 or 75 into re-skilling initiatives to really compliment that. But what we're seeing is companies need to be much more revolutionary in their focus on talent. We saw economic analysis recently that pointed out that for every $1 you spend on technology, you are likely going to need to spend about $9 on intangible human capital. That means on talent, on getting the best talent, on re-skilling and on changing processes and work tasks. So there's a lot of work that needs to be done. Really that's human focus. It's not just about adopting the technology. Certainly the technology's critical, but we're underestimating the amount of focus that needs to go into the talent factors. >> That's a huge point. >> And I think some of the elements of talent that become really critical that we talked about in the book are becoming a talent creator. We believe the successful companies of the future are going to be able not just to post a job opening and hire people in because there's not going to be enough. And a lot of the jobs that companies are creating don't exist 'cause the technology changing so fast. So the companies that succeed are going to know how to create talent, bring in people, apprentices and such, and shape to tale as they go. We're doing a significant amount of that in our own company. They're going to be learning based organizations where you'll differentiate, you'll get the best employees if you provide better learning environments because that's what employees want. And then democratizing access to technology. Things like Amazon's Honeycode is an example, low-code/no-code development to spread development to wider pools of people. Those types of things are really critical going forward to really unlock the talent potential. And really what you end up with is, yeah, the human talent's important, but it's magnified and multiplied by the power of people, giving them in essence superpowers in using technology in new ways. >> I think you nailed it, that's super important. That point about the force multiplier when you put things in combination, whether it's group constructs, two pizza teams flexing, leveraging the talent. I mean, this is a new configuration. You guys are nailing it there. I love that piece. And I think groups and collectives you're going to start to see a lot more of that. But again, with talent comes trust when you start to have these ephemeral and or forming groups that are forming production systems or experiences. So trust comes up a lot. You guys see the metaverse as an important part there. Obviously metaverse is a pretext to the virtual world where we're going to start to create these group experiences and create new force multipliers. How does the metaverse play into this new radically human world, and what does it mean for the future of business? >> Yeah, I think the metaverse is radically misunderstood to use the word title when we're not with the title of our book. And we believe that the metaverse does have real big potential, massive potential, and I think it'll transform the way we think about digital more so than we've changed our thinking on digital in the last 10 years. So that's the potential of the metaverse. And it's not just about the consumer things, it's about metaverse and the enterprise. It's about the new products you create using distributed ledger and other technologies. And it's about the industrial metaverse of how you bring digital twins and augmented workers online in different ways. And so I believe that it has tremendous potential. We write about that in the book and it really takes radically human to another level. And one way to think about this is cloud is really becoming the operating system of business. You have to build your enterprise around the cloud as you go forward. That's going to shape the way you do business. AI becomes the insight and intelligence in how you work, infused with the human talent and such as we said. And the metaverse then reshapes the experience layers. So you have cloud, AI building on top of this metaverse providing a new way to generate experiences for employees, citizens, consumers, et cetera. And that's the way it unfolds, but trust becomes more important because just as AI raises new questions around trust, every technology raises new questions around trust. The metaverse raises a whole new set of questions. And in the book we outline a five-part framework or five essential parts of the framework around how you establish trust as you implement these new technologies. >> Yeah, we're seeing that about three quarters of companies are really trying to figure out trust, certainly with issues like the metaverse more broadly across their IT so they're focusing on security and privacy, transparency, especially when you're talking about AI systems, explainability. One of the more surprising things that we learned when doing the book, when we were doing the research is that we saw that increasingly consumers and employees want systems to be informed by a sense of humanity. So one company that we've been looking at that's been developing autonomous vehicles, self-driving car systems, they're actually training the system by emulating human behavior. So turning the cameras on test drivers to see how they learn and then training the AI using that sense of humanity 'cause other drivers on the road find human behavior more trustworthy. And similarly, that system is also using explainable AI to actually show which human behaviors that AI system is learning from. Some really interesting innovations happening in that trust space. John. >> Jim, I think you bring up a great point that's worth talking more about. Because you're talking about how human behaviors are being put into the design of new things like machines or software. And we're living in this era of cloud scale, which is compressing this transformation timeline and we've been calling it supercloud, some call it multi-cloud, but it's really a new thing happening where you're seeing an acceleration of the transformation. We think it's going to happen much faster in the next five to 10 years. And so that means these new things are emerging, not just, hey, I'm running a virtual event with chat and some video. It's group behavior, it's groups convening, talking, getting things done, debating, doing things differently. And so this idea of humans informing design decisions or software with low-code/no-code, this completely changes strategy. I mean this is a big point of the book. >> Yeah, no, I go back to one of the, the E in the IDEAS framework is expertise. And we talk about from machine learning to machine teaching, which is exactly that. Machine learning is maybe humans tag data and stuff and feed into algorithms. Machine teaching is how do you really leverage the human expertise in the systems that you develop with AI. One of the examples we give is one of the large consumer platforms that uses human designers to give the system a sense of aesthetic design and product design. A very difficult thing, especially with changing fashion interest and everything else to encode in algorithms and to even have AI do, even if you have fast amounts of data, but with the right human insight and human expertise injected in, you can create amazing new capability that responds to consumers in a much more powerful way. And that's an example of what you just said, John, bringing the two together. >> Well, yeah, it's interesting. I want to to get your thoughts as we get wrap up here soon. How do you apply all these human-centric technologies to the future of business? As you guys talk to leaders in the enterprise of their businesses, as they look at the horizon, they see the the future. They got to start thinking about things like generative AI and how they can bring some of these technologies to the table. We were talking about if open source continues to grow the way it's going, there might not be any code to write, it just writes itself at some point. So you got supply chain issues with security. These are new things you guys are hitting in the book where these are new dynamics, new power dynamics in how things get built. So if you're a business owner and leader, this is a new opportunity, a challenge certainly that is an opportunity. How do you apply all this stuff for business? >> I'll go first then Jim can add in. But the first thing I think starts with recognizing the role that technology does play and investing accordingly in it. So the right technology talent, rethinking the way you do strategy as we talked about earlier and recognizing how you need to build a foundation. That's why the fact you're at re:Invent is so important because companies are, again, rebuilding that operating system of their business in the cloud. And you need that as the foundation to go forward, to do, to build the other types of capabilities. And then I think it's developing those talent systems as well. Do you have the right talent brand? Are you attracting the right employees? Are you developing them in the right way so that you have the right future talent going forward? And then you marry the two together and that's what gives you the radically human formula. >> Yeah. When we were developing that first part of the book, Paul and I did quite a bit of research, and Paul kind of alluded to that research earlier, but one of the things that we saw in really the first year of the pandemic was that there was a lot of first time adoption of intelligent technologies like artificial intelligence. One statistic is that 70% of companies that had never tried AI before went ahead and tried it during the pandemic. So first time adoption rates were way up, but the thing is companies were not trying to do it themselves and to necessarily build an AI department. They were partnering and it's really important to find a partner, often a cloud partner as a way to get started, start small scale, and then scale up doing experiments. So that was one of the key insights that we had. You don't need to do it all yourself. >> If you see the transformation of just AWS, we're here at re:Invent, since we've been covering the events since 2013, every year there's been a thematic thing. It was startups, enterprise, now builders, and now change your company. This year it's continuing that same thing where you're starting to see new things happen. It's not just lift and shift and running a SaaS application on the cloud. People are are changing and refactoring and replatforming categorical applications in for this new era. And we're calling it supercloud, superservices, superapps, 'cause they're different. They're doing different things in leveraging large scale CapEx, large scale talent pools, or talent pools in certain ways. So this is real, something's happening here and we've been talking about it a lot lately. So I have to ask you guys, how does a company know if they're radical enough? Like what is radical? How can I put a pin in that? It's like take a temperature or we like radical enough, what some tell signs can you guys share for companies that are really leaning into this new next inflection point because there are new things happening? How do you know if you're you're pushing the envelope radical enough to take advantage? >> Yeah, I think one. >> You can go ahead, Paul. >> Yeah, I was going to say one of the tests is the impact on your business. You have to start by looking at all this in the context of your business, and is it really taking you to another level? You said it perfectly, John, it used to be we used to talk about migration and workloads to the cloud and things like that. That's still something you need to do. But now our focus with a lot of our customers is on how do you innovate and grow your business in the cloud? What's the platform that you're using for your new digital products and services you're offering to your consumers. I mean it is the business and I think that's the test whether you're being radical enough is on the one hand, are you really using the technology to drive differentiation and real growth and change in your business? And are you equipping people, your human talent with the capabilities they need to perform in very different ways? And those are the two tests that I would give. >> Totally agree. >> Interesting enough, we love this topic and you guys, again, the book is spot on. Very packs of big punch on content, but very relevant in today. And I think one of the things we're looking at is that people who do things differently take advantage of some of these radical approaches like IDEAS, your framework, and understand where they are and what's available and what's coming around the corner. They stand out in the pack or create new business opportunities because the CapEx is taken care of. Now you got your cloud, I mean you're building clouds on top of clouds or something's happening. I think you see it, look at like companies like Snowflake, it's a data warehouse on the cloud. What does that mean? They didn't build a cloud, they used Amazon. So you're starting to see these new things pop up. >> Yeah and that's a good example. And it sounds like a simple thing, data warehouse in the cloud, but the new business capability that a technology like that allows and the portability of being able to connect and use data across cloud environments and such is tremendously powerful. And I think that's why, you talk about companies doing things differently, that's why it's great, again, that you're at re:Invent. If you look at the index of our book, you'll see AWS mentioned a number of times 'cause we tell a lot of customer company stories about how they're leveraging AWS capabilities in cloud and AI to really do transformative things in their business. And I think that's what it's all about. >> Yeah, and one of the things too in the book, it's great 'cause it has the systems thinking, it's got really relevant information, but you guys have seen the movie before. I think one of the wild cards in this era is global. We're global economy, you've got regions, you've got data sovereignty, you're seeing all kinds of new things emerging. Thoughts on the global impact 'cause you take your book and you overlay that to business, like you got to operate all over the world as a human issue, as a geography issue. What's your guys take on the global impact? >> Well that's why you got to think about cloud as one technology. We talked about in the book and cloud is, I think a lot of people think, well, clouds, it's almost old news. Maybe it's been around for a while. As you said, you've been going to re:Invent since 2013. Cloud is really just getting started. And it's 'cause the reasons you said, when you look at what you need to do around sovereign cloud capability if you're in Europe. For many companies it's about multi-cloud capabilities that you need to deploy differently in different regions. And they need to, in some cases for good reason, they have hybrid cloud capability that they match on their own. And then there's the edge capability which comes into play in different ways. And so the architecture becomes very complex and we talk the A in IDEAS is architecture. We talk about all this and how you need to move from the old conception of architecture, which was more static and just modularity was the key thing you thought about. It's more the idea of a living system, of living architecture that's expanding and is what's much more dynamic. And I think that's the way you need to think about it as you manage in a global environment today with the pace of technology advancement. >> Yeah, the innovation is here. It's not stopping. How do you create some defacto standards while not stunting the innovation is going to be a big discussion as these new flipped assumptions start to generate more activity. It's going to be very interesting to watch. Gentlemen, thank you so much for spending the time here on theCUBE as we break down your new book, "Radically Human" and how business leads can flip the script on their business assumptions and put ideas and access to work. This is a big part of the cloud show at re:Invent. Thanks so much for sharing and congratulations on a great book. >> Thanks, John. And just one point I'd add is that one of the things we do talk about in talent is the need to reskill talent. People who need to be relevant in the rapidly changing future. And that's one area where I think we all as institutions, as communities and individuals need to do more is to help those that need to reskilling. And the final point I mentioned is that we've mentioned at the end of the book that all proceeds from the book are being donated to NGOs and nonprofits that are focused on reskilling those who need a skill refresh in light of the radically human change in technology that's happening. >> Great. Buy the book. Proceeds go to a great cause and it's a very relevant book. If you're in the middle of this big wave that's coming. this is a great book. There's a guidepost and also give you some great ideas to reset, reflip the scripts, refactor, replatform. Guys, thanks for coming on and sharing. I really appreciate it. Again, congratulations. >> Thanks, John. >> Thanks, John. Great discussion. >> You're watching theCUBE here covering the executive forum here at AWS re:Invent '22. I'm John Furrier, you're host with Accenture. Thanks for watching. (gentle music)

(techno music) >> Welcome back to the Cube. I'm John Walls. We continue our coverage here at AWS reInvent 22. We're in the Venetian in Las Vegas, wrapping up our day one coverage here in the executive summit sponsored by Accenture and with me to talk about Accenture, couple of guys who are no strangers at all to the Cube. In fact, I think we got to give you like alumni passes or something. (Chris and Merim laugh) We got to come up with something like that. Um, Merim Becirovic is with us. Uh, Merim's a global IT at Accenture. And Chris Wegmann, who's already been on once today, as a matter of fact. >> Yeah (indistinct) >> So we're going to start charging you rent, Chris. (Chris and Merim laugh) Uh, global technology and practice lead with the AWS business group at Accenture. Good, glad to have you both back and, um, you're welcome to the Cube any time, by the way. >> So don't be scared. >> Thanks, great to be back. Let's talk about >> Sure. >> What, what you folks have been up to. So, um, you are, as we were talking earlier, you are where a lot of your clients would like to be. You, you've begun this transformation. You have fully migrated to the cloud, you've learned, right? >> Yes. You've hit all the bumps along the way. So talk about your journey. >> Yeah. >> And then how you think that experience could be translated to what your clients are going through. >> Yeah, so I'll, I'll hit it from the lessons learned and working together with our business group partners. We, so Accenture's journey to the cloud is complete. We have finished that journey, and as part of that journey, we have migrated all of the services it takes to run Accenture to the public cloud. So now that's done. That was complete. But now we are this, now it is this cloud continuum living in the cloud. And the, now, the thing we talk about, and I'd love to have Chris, you know, shine a little bit more, is we have built our digital core in a cloud, now. We're no longer dependent on data centers. And that has given us tremendous flexibility around how to enable the business as it has grown significantly since we started this journey a few years back. >> Yeah, you know, Merim, like you talk about, right? We talk about our client, we've talked to our clients about building this digital core, right? And, and we've been through that as Accenture, as a global IT organization, you know. Supporting well over 720,000 people. >> Yeah. >> Right? That growth over the last year has been tremendous. Right? So, without the strong digital core built on cloud, right? We couldn't do that, right? We couldn't add that number of people, right? We couldn't make the, the, the changes were needed during, uh, Covid to bring people home, working from home. You know, whether it being uh, the way we changed our business model or things like that, um, you know that was all enabled by cloud. It couldn't be done without that. And, you know, also the variable in our business, right? Is very tied now to our cloud consumption, right? So, you know, it goes up, it goes down, right? We've, you know, Merim and his team have completely built their, their their core with those, with those concepts uh, in mind. >> Yeah, I mean, you're talking about, you know, 700, 800,000 employees and how many countries did you say? >> 130 different countries, at least. >> 130 different countries. So, I mean, no small task, obviously, uh, to get everything done. When did you start? >> So our cloud journey, effectively, we started in 2015. And we were done, kind of right before Covid around 2019. We took a pause for a couple of different things but we could have probably done that faster. And if we were, if I was to do it again now, today we could probably do it in two to three years, flat. With everything that we've learned so far. >> So what's the application, then, to your clients' experiences that, I mean, been there, done that, right? >> You can, exactly right. I mean, you know, we always say that we want to be our best credential, right? And Merim and his team are our best credential in this space. Um, so, you know, a lot of our customers, you know, struggle making that commitment. A lot of 'em are past that struggle, now. They're committed, they're going. Uh, but I talk to a lot of my customers about, you know, do I, do I migrate? Do I modernize? You know, how do I do it? And, and it was interesting with Accenture, right? It, it started out very much as a migration program. >> Yeah. >> Right, so, we made the decision, Merim and his team made the decision to do a migration and now a modernization, right? And, and that's proven very effective. Uh, it, it's, it's, it's proven, you know, uh, we got that core in place, right? We were able to build off of that versus, you know, spending- it would've taken a lot more time just to start with a modernization approach. >> Yeah. Where, where do you draw the line between the two, between migration and modernization, then? Because just by migrating alone, you are modernizing, you know, some of your operations, so you're getting up to speed. But, but how do you draw that line and then how do you get people to jump over it? >> So I, I'll hit it from how our lessons learned. So, when we first started and we did the migrations it was literally lift and shift. And it was a lot of argument about lift and shift isn't worth it. But we found out it was, because it wasn't just about moving the work loads and keeping it like a data center. It was moving the work loads and then optimizing because everything in the cloud was significantly faster. So then I didn't have to consume all the services the same way I did in the data center. I can actually consume them smaller. But also as time went by, what we learned is, hey, now these services are working here. Which ones are actually costing us more money to run? And not that they were costing more than the data center, but it's relative to the cloud which ones cost more in the cloud? Then we looked at that and said, okay how do we want to modernize those? And then we modernized as container capabilities started the evolving, got much more mature. We shifted a lot of workloads to containers. But otherwise, the other principle we push very hard is big consumption of Lambda and uh, serverless capabilities on Amazon. So we have refactored multiple applications to give us that capability to say we no longer need the IAS capabilities, those servers, those VM's, and we run on, on serverless capability. And what's great about that is, now I don't have a server to patch, to scan, to remediate, to upgrade. I've moved away from that capability. And the teams can focus more on building the business capabilities the business wants. Um, like we did to our pricing team. I don't know if you knew this one, Chris, but all the pricing capability has been redone to be cloud native on, on AWS. >> And how, how do you deal with the folks that, that still kind of have a foot in the on-prem world that, um, that they're just not ready to give it up? You know, they, they like the control, they like the self-management. >> Yeah. >> They, they want to be in charge. >> Well, yeah. I mean, a lot of, a lot of our customers, it's, there's a reason why they need on-prem still. And there is on-prem, let's be clear. I mean, it, it is a hybrid cloud world for most of our, our customers, right? Whether they got manufacturing, whether they've got, you know, datas that are, you know, SCADA systems or, or operational IT systems that have to be close to their, their execution or to their, to their factories and things like that. So that's going to happen. I think everyone, and I shouldn't say everyone, but you know, most of our customers know they need to get there, right? And are somewhere on their journey, right? Very few have not started at all. Uh, but it's about acceleration, right? And I, I do think, um, we're going to see more and more acceleration. We saw it with Covid, right? >> Mm-hm. >> And then, you know, obviously I think we're going to see it again, right? With you know, kind of what's going on with the economy and stuff like that. It, it's, you know, it's a great way to push that change through. >> Right. >> And I, I'm really excited, to be honest what I'm really excited about, if I look at what Merim and his team's doing, is they're just leveraging that digital core and truly taking the investments that the hyper scaler's are making, the AWS's are making, and leveraging 'em. So we're not making that investment, right? We're a capital white company, right? So we don't like making good capital investments, right? And we're taking advantage of the capital investments. And we couldn't do that of the, of the hyper scales. We couldn't do that without being there. Right? >> Right. >> We just couldn't do it. >> And maybe, John, if I can build on that. >> Sure. >> Like, one of, one of the things for me when I think about the cloud is, I'm not alone. You know, because when you're in a data center when you're running a data center, you're kind of on an island. And on that island, if you've got security issues, if you got stuff you're dealing with with attackers, you know, you're, you're kind of on an island and you're alone. Whereas in this world, I am where all the investment is, where all the security capabilities are being built, and I have partners that are there with us that help us when these situations come up. So for me, I'm very uh, grateful that we pushed very hard in the beginning to get here. But I wouldn't have it any other way. For us. >> So like, do you- do you want to live outside the fort? >> Yeah. >> No >> No. (laughs) >> You're exactly right. >> Yeah. >> I don't want to live outside the fort. >> Right. >> There are a lot of bad guys out there right now. >> Yeah. >> All right, so, the journey is over. >> Right. You can unpack your bags and get comfortable, right? (Merim laughs) >> No. >> Hardly. >> No. >> So, so what is the, what has this done in terms of setting you up for your future plans? And, and >> So I'll talk about a couple different things and maybe you can build on it, Chris, from what you're seeing, like for us, we, we got very good at, I hate the concept of just FinOps but it's the way of being in the cloud. It's different than running a data center and uh, the way we think about building services, consuming services, allocating services, provisioning services. There's just so much more flexibility there that we can completely fine tune the service that we want to provide. That helps us from when we think about 360 degree value, as we talk to our clients, for ourselves to say it also helps just simply on the sustainability agenda, right, because now, as Amazon builds their capabilities to be more sustainable, those SKUs are available to us, we can naturally consume those SKUs much more effectively. Um, and then uh, the next thing to me, what I'm, what I'm especially excited about is all the stuff we're doing around network. So, you know, pre-Covid, 95% of our traffic was just straight to the internet because we had already finished the journey. So now what do you need a wide area network for anymore? >> Right. >> If you're not routing traffic between data centers what do you need it for? So, we have been working with, with AWS especially, like building these cloud land type capabilities and consuming it. So think of consuming, uh, network same way as you do the cloud. So I'm excited about that one. >> Yeah. That, that, I'm super excited about that, right? Because you know, network's at the core of everything you do, right? And there's always a lot of concern, hey, when I go to the cloud, my network costs are going to go up, right? Um, but I think we've proven, right? >> Yes. >> Being able, that those costs can come down, right? And we can have a better experience, uh, deal with the ebbs and flows of our business whether it's people working from home, people working in the office, you know, or at the client sites. We, we've, you know, we've got that cloud-based backbone that we support. You know, I, I mean Merim, I agree a hundred percent. I think you and your team have done a great job of cost management, cloud cost management, optimization, right? You didn't stop, right? >> No. >> You didn't lo- you didn't just live after the migration on VMs. Right? You know, you went serverless, you went, you know, containerization. >> Yep. >> Uh, and that's kept our cloud bill going down. >> Yes. >> Right. Versus going up, right? >> Yes. >> And I hear from a lot of customers concerned about cloud costs and that type of stuff, but you've proven right, >> Yes. >> That you can keep it flat, if not going down because you're using those last minutes. Sustainability is the other thing that I truly am, I, I love, right? Is, you know, we're all trying to become a more sustainable, sustainable organization. We're trying to help our clients become more sustainable organizations. And you know, you know, your ability to take on Gravitant processors, right? Which use less power. >> Yes. >> Right? Overnight, right? >> Yes. >> Or, hey, I'm using a, you know a, uh, serverless lambda, whatever, right? And I'm not running that server. >> Right. >> You know, so, you're able to show that sustainability gains, um, you know, very quickly. Which you could not do, right? You know, in just doing cloud basic migrations. >> Well, I tell you what I think is impressive, is that you put your money where your mouth is, right? >> Yep. (laughs) >> Is that, that it's, and, and if I'm going to be a client, not to, you know, give you guys a pat on the back, you don't need it. You're doing great without me. But I'd say you've been there, you've done that. And, and so I can learn from you. You understand my pain. >> Yes. >> You understand my reservations, my challenges and uh, you could be my, my headlights here. (Merim laughs) >> So, I think great approach. Kudos to you and certainly wish you both success and to your fourth and fifth appearances on the Cube. (Merim and Chris laugh) Um, we have slots tomorrow if you're arou- available. So, maybe we'll fill it up >> There you go. >> and bring it back again. >> Awesome. >> Guys, thanks for being here. >> Sure. >> It was very nice. >> Appreciate the time. >> All right. >> That's great. >> I've been talking, uh, about Accenture. This is the, of course, executive summit being sponsored by Accenture here at AWS reInvent 22. I'm John Walls. You're watching the Cube, the leader in tech coverage.

(mellow music) >> Oh, welcome back to theCUBE. We continue our coverage here at AWS re:Invent 22. We're in the Venetian in Las Vegas, and this place is hopping. I'm tell you what. It is a nearly standing room only that exhibit floor is jam packed, and it's been great to be along for the ride here on Accenture's sponsorship at the Executive summit as well. We'll talk about Pfizer today, you know them quite well, one of the largest biopharmaceutical companies in the world but their tech footprint is impressive, to say the least. And to talk more about that is Wes Barnes, senior Director of Pfizer's Digital Hosting Solutions. Wes, good to see you, sir. >> Good to meet you, John. >> And Jon Harrison, the North American lead for Infrastructure and engineering at Accenture. Jon, good to see you as well. >> Good to see you as well. >> Thanks for joining us. >> Happy to be here. >> Alright, so let's jump in. Pfizer, we make drugs, right? >> Pharmaceuticals. >> Yes. >> Among the most preeminent, as I said biopharms in the world. But your tech capabilities and your tech focus as we were talking about earlier, has changed dramatically in the 18 years that you've been there. >> Yep. >> Now, talk about that evolution a little bit to where you were and what you have to be now. >> Yeah, yeah. It's interesting. When I started at Pfizer, IT was an enabling function. It was akin to HR or our facilities function. And over the past couple years, it's dramatically changed. Where Digital now is really at the center of everything we do across Pfizer. You know it really is a core strategic element of our business. >> Yeah. And those elements that you were talking about, just in terms of whether it's research, whether it's your patients, I don't want to go through the laundry lists the litany of things, but the touch points with data and what you need it to do for you in terms of you know, computations, what you, the list is long. It's pretty impressive. >> Yeah, yeah, for sure yeah. >> I mean, shed some light on that for us. >> We cannot release a medicine without the use of technology. And if you think about research now, a huge component of our research is computational chemistry. Manufacturing medicines now is a practice in using data and analytics and predictive machine learning and analytics capabilities to help us determine how to best you know, apply the capabilities to deliver the outcomes that we need. The way in which we connect with patients and payers now is wholly digital. So it's an entirely different way of operating than it was 10 years ago. >> And the past three years, pretty remarkable in many respects, to say the least, I would think, I mean, John, you've seen what Pfizer's been up to, talk about maybe just this, the recent past and all that has happened and what they've been able to do. >> Yeah, I mean, what is so exciting to me about working with a company like Pfizer and working in life sciences more broadly is the impact that they make on patients around the world world, right? I mean, think about those past three years and Pfizer stepped up and met the moment for all of us, right? And as we talk a little bit about the role that we played together with Pfizer with AWS in their journey to the cloud, it's so motivating for myself personally it's so motivating for every single person on the team that we ask to spend nights and weekends migrating things to the cloud, creating new capabilities, knowing that at the end of the day, the work that they're doing is making the world a healthier place. >> Yeah, we talk so much about modernization now, right? And it's, but it kind of means different things to different people depending on where you're coming into the game, right? If you've been smart and been planning all along then this is not a dramatic shift in some cases though, for others it is. Right? >> Yeah. >> Traumatic in some cases for some people. >> For sure. >> For Pfizer, I mean talk about how do you see modernization and what does it mean to your operations? >> Following our success of the COVID program of 2021, I mean it became evident to us that, you know we needed to maintain a new pace of innovation and in fact try to find ways to accelerate that pace of innovation. And as I said earlier everything we do at Pfizer is centered around digital. But despite that, and despite 10 years of consolidating infrastructure and moving towards modern technology, last year, only 10% of Pfizer's infrastructure was in the native public cloud. So we had a problem to solve. In fact, I remember, you know, we had to build up our clinical systems to support the volume of work that we were doing for COVID-19 vaccine. We were rolling things into our data center to build up the capacity to achieve what we needed to achieve. Moving to the public cloud became more imperative to try to achieve the scale and the modern capabilities that we need. >> And so where did you come into play here with this? Because obviously as a partner you're right alongside for the ride but you saw these inherent challenges that they had and how did Accenture answer the bell there? >> Well, so look, I mean we saw Pfizer react to the pandemic. We saw them seize the moment. We talked together about how IT needed to move quicker and quicker towards the cloud to unlock capabilities that would serve Pfizer's business well into the future. And together we laid out some pretty ambitious goals. I mean, really moving at a velocity in a pace that I think for both Accenture and AWS surpassed the velocity and pace that we've done anywhere else. >> Yeah, right, yeah. >> So we've set out on an ambitious plan together. You know, I was kind of reflecting about some of the successes, what went well what didn't in preparation for re:Invent. And you know, many of the folks that'll listen to this will remember the old days of moving data centers when you'd have a war room you'd have a conference bridge open the whole time. Someone would be running around the tile floor in the data center, do a task, call back up to the bridge and say, what do I do next, right? Then when I think about what we did together at Pfizer in moving towards the public cloud, I mean, we had weekends most weekends where we were running a wave with 10,000 plus discrete activities. >> Yeah. >> Wow. >> Right, so that old model doesn't scale. >> Right. >> And we really anchored, >> You have a very crowded data center with a lot of people running into each other. >> You'd have a whole lot of people running around. But we really anchored to an Accenture capability that we call myNav Migrate. I know you guys have talked about it here before so I won't go into that. But what we found is that we approached this problem of velocity not as a technical problem to solve for but as a loading and optimization problem of resources. Right, thought about it just a little bit different way and made sure that we could programmatically control command and control of the program in a way that people didn't have to wait around all Saturday afternoon to be notified that their next activity was ready, right? They could go out, they could live their day and they could get a notification from the platform that says, hey it's about your turn. Right, they could claim it they could do it, they could finish it, and that was really important to us. I mean, to be able to control the program in that type of way at scale. >> Yeah, by the way, the reason we went as fast it was a deliberate choice and you'll talk to plenty of folks who have a five year journey to the public cloud. And the reason we wanted to move as fast as we did and Jon talked about some of it, we wanted to get the capabilities to the business as quickly as we could. The pace of innovation was such that we had to offer native cloud capabilities we had to offer quickly. We also knew that by compressing the time it took to get to the cloud, we could focus the organization get it done as economically as possible but then lift all boats with the tide and move the organization forward in terms of the skills and the capabilities that we need to deliver modern outcomes. >> So, you know, we talk about impacts internally, obviously with your processes, but beyond that, not just scientists not just chemists, but to your, I mean, millions of customers, right? We're talking, you know, globally here. What kind of impacts can you see that directly relate to them, and benefits that they're receiving by this massive technical move you've made? >> Pfizer's mission is breakthroughs that change patient lives. I mean, the work that we do the work that everybody does within Pfizer is about delivering therapies that, you know provide health outcomes that make people live longer, live healthier lives. For us, modernizing our infrastructure means that we can enable the work of scientists to find novel therapies faster or find things that perhaps couldn't have been found any other way without some of the modern technologies that we're bringing to bear. Saving money within infrastructure and IT is treasure that we can pour back into the important areas of research or development or manufacturing. We're also able to, you know, offer an ecosystem and a capability in which we connect with patients differently through digital mechanisms. And modern cloud enables that, you know, using modern digital experiences and customer experience, and patient experience platforms means that we can use wearable devices and mobile technologies and connect to people in different ways and offer solutions that just didn't exist a couple years ago. >> And so, I mean, you're talking about IoT stuff too, right? >> 100%. >> It's way out on the edge and personal mobile, in a mobile environment. And so challenges in terms of you know, data governance and compliance and security, all these things, right? They come into play because it's personal health information. So how, as you've taken them, you know to this public cloud environment how much of a factor are those considerations? Because, you know, this is not just a product a service, it's a live human being. >> Yeah. I mean, you start with that, you think about it through the process and you think about it afterwards, right, I mean, that has to be a core factor in every stage of the program, and it was. >> So in, in terms of where you are now, then, okay, it's not over. >> It's never over. >> I mean, you know, as good as you are today and as fast as you are and as accurate and as efficient. >> Yeah. >> Got to get better, right? You got to stay competitive. >> Yeah. >> So where do you find that? Because, you know, with powers being what they are with speed and what it is how much more is there to squeeze out of this rock? >> There's a lot more to squeeze out of the rock. If you think about what we've done over the past year it's about creating sort of a new minimum viable product for infrastructure. So we've sort of raised the bar and created an environment upon which we can continue to innovate that innovation is going to continue sort of forever at this point. You know, the next focus for us is how to identify the business processes that deliver the greatest value ultimately to our patients. And use the modern platform that we've just built to improve those processes to deliver things faster, deliver new capabilities. Pfizer is making a huge investment in digital medicines therapies that are delivered through smart devices through wearables using, as I said technology that didn't exist before. That wouldn't be possible without the platform that we've built. So over the past year, we've come a long way but I think that we've effectively set the table for all of the things that are yet to come. >> So, Jon, how do you then, as you've learned a lot about life science or, and certainly Pfizer with what they're up to, how do you then apply, you know, what you know about their world to what you know about the tech world and make it actionable for growth to make it actionable for, for future expansion? >> Yeah, I mean, we start by doing it together, right? I think that's a really important part. Accenture brings a wealth of knowledge, both industry experience and expertise, technology experience and expertise. We work together with our clients like Pfizer with our partners like AWS to bring the best across that power of three to meet clients where they're at to understand where they want to go, and then create a bespoke approach that meets their business needs. And that's effectively what we're doing now, right? I mean, if you think about the phase that we've just went through, I mean, a couple of fast facts here no pun intended, right? 7,800 server instances across 11 operating system versions 7,500 databases across 20 database versions, right? 4,700 applications, 350,000 migration activities managed across an eight month period. >> In eight months. >> Yeah. But that's not the goal, right? The goal is now to take, to Wes' point that platform that's been developed and leverage that to the benefit of the business ultimately to the benefit of the patient. >> You know, why them, we have we've talked a lot about Pfizer, but why Accenture? What, what, what's, 'cause it's got to be a two way street, right? >> We've had a long partnership with Accenture. Accenture supports a huge component of our application environment at Pfizer and has for quite a long time. Look, we didn't make it easy on them. We put them up against a large number of world class SIs. But look, Accenture brought, you know, sort of what I think of as the trifecta here. They brought the technical capabilities and knowledge of the AWS environment. They brought the ability to really understand the business outcomes that we were trying to achieve and a program leadership capability that, you know I think is world class. And Jon talked about myNav, you know, we recognized that doing what we were trying to do in the time that we were doing it required new machinery, new analytics and data capabilities that just didn't exist. Automation didn't exist. Some people experience capabilities that would allow us to interface with application owners and users at a velocity and a pace and a scale that just hasn't been seen before at Pfizer. Accenture brought all three of those things together and I think they did a great job helping us get to where we need to be. >> When you hear Jon rattle through the stats like he just did, right? We talk about all, I mean, not that I'm going to ask you to pat yourself on the back but do you ever, >> He should. >> Does it blow your mind a little bit, honestly that you're talking about that magnitude of activity in that compressed period of time? That's extraordinary. >> It's 75% of our global IT footprint now in the public cloud, which is fantastic. I mean, look, I think the timing was right. I think Pfizer is in a little bit of a unique position coming off of COVID. We are incredibly motivated to keep the pace up, I mean across all lines of business. So, you know what we found is a really willing leadership team, executive leadership team, digital leadership team to endorse a change of this magnitude. >> Well, it's a great success story. It's beyond impressive. So congratulations to both you on that front and certainly you wish you continued success down the road as well. >> Thank you. >> Thank you gentlemen. >> Thank you. >> Good job. >> Pfizer, and boy, you talk about a job well done. Just spectacular. All right, you are watching our coverage here on theCUBE, we're at the AWS re:Invent 22 show. This is Executive Summit sponsored by Accenture and you're watching theCUBE the leader in high tech coverage.

(soft music) >> We're in Las Vegas at The Venetian for our continued coverage here of re:Invent '22, AWS's big show going on. Great success off to a wonderful start. We're in the Executive Summit sponsored by Accenture. And we're going to talk about public health and the cloud, how those have come together in the great state of North Carolina. Charles Carter is going to help us do that. He's assistant secretary for technology services with the state of North Carolina's Department of Health and Human Services. Charles, good to see you. Thanks for joining us here on "theCUBE". >> Thank you very much for having me. >> Yeah, thanks for making the time. So first off, let's talk about what you do on the homefront before what you're doing here and where you're going. But in terms of kind of what your plan has been, what your journey has been from a cloud perspective and how you've implemented that and where you are right now in your journey. >> Sure, so we started. When I got there, we didn't have a cloud footprint at all. There was a- >> Host: Which was how long ago? >> I got there in 2016, so about six years. >> Host: Six, seven years, yeah. >> Yeah, five, six years. So anyways, we started off with our first module within our Medicaid expansion. And that was the first time that we went into the cloud. We worked with AWS to do our encounter processing system. And it was an incredible success. I think the ease of use was really kind of something that people weren't quite ready for. But it was really exciting to see that. And the scalability, to be able to turn that on and cover the entirety of North Carolina was awesome. So once we saw that and get a little taste of it, then we really wanted to start implementing it throughout DHHS. And we marshaled in a cloud-only cloud-first strategy where you had to actually get an exemption not to go to the cloud. And that was a first for our state. So that was really kind of the what launched us. But then COVID hit. And once COVID came in, that took us to a new level. COVID forced us to build technologies that enabled a better treatment, a better care, a better response from our team. And so we were able to stand up platforms in 48 hours. We were able to stand up COVID vaccine management systems in six weeks. And none of that would've been possible without the cloud. >> So forced your hand in a way because all of a sudden you've got this extraordinarily remote workforce, right, and people trying to- And you're doing different tasks that were totally unexpected, right, prior to that. What kind of a shock to the system was that from I get from an IT perspective? >> Yeah, so from a state government perspective, for example, you never hear you have all the money you need and you have to do it quickly. It just doesn't work like that. But this was a rare moment in time where you had this critical need. The entire country and our state population was kind of on edge. How do we move through this? How do we factor our lives into this new integration? What is this virus? Is it spreading in my county, in my city, my zip code? Where is it? And that kind of desperation really kind of focused everybody in on build me technologies that can get me the data that I need to make good healthcare decisions, good clinical decisions. And so that was our challenge. Cloud enabled it because it can scale so quickly. We can set up things, we can exchange data. We can move data around a lot easier. And the security is better from our perspective. So that COVID experience really kind of pushed us, you know, if you will, out the door. And we're never going back because it's just too good. >> Yeah, was that the aha moment then in a way because you had to do so much so fast and before capabilities that maybe you didn't have or maybe hadn't tapped? >> Yeah, yeah. >> I mean what was the accelerant there? Was COVID that big, or was it somebody who had to make a decision to say, this is where we're going with this, somebody in your shoes or somebody with whom you work? >> Yeah, no, I mean cloud at the end of the day, we knew that in order to do what we needed to do we couldn't do it on-prem. It wasn't an option. So if we wanted to build these capabilities, if we wanted to bring in technologies that really brought data to our key, our governor, our secretary, to make good decisions on behalf of our residents in North Carolina, then we were going to have to build things quickly. And the only way you can do that is in the cloud. So it was when they came back and said, "We need these things," there's only one answer. That's a good thing about technology. It's pretty binary, so it was either go with what we had, which wasn't adequate, or build to what we knew we could do and pretty short order. And because of that, we were able to actually usher in a huge expansion of cloud footprint within DHHS. And now we've actually been able to implement it in other departments simply because of our expertise. And that's been a huge asset for the state of North Carolina as a whole. >> So what's your measuring stick then for value in terms of identifying benefit? 'Cause it's not really about cost. This is about service, I assume, right? >> Right. >> So, you know, how do you quantify the values and the benefits that you're deriving from this migration over to the cloud? >> So from our perspective, it hits several different areas. I mean, you can start in security. We know that if we're in the cloud the tools that can manage and give us visibility in the cloud are 10 times better than an on-prem environment. And so if we can take a lot of these legacy systems and move them to the cloud, we'll be in a better security posture. So we have that piece of it. The other part of it is the data aspect of it, being able to- We're 33 divisions strong, right? We have a large footprint. We have a lot of siloed data elements. And cloud allows us to start integrating those data sets in a much more usable fashion so that we can see that if Charles Carter's in one area in division, a specific division with DHHS, is he somewhere else? And if he is somewhere else, then how do we provide a better clinical care for that individual? And those are conversations that we can't really have if we don't move to the cloud. So those types of- And of course there's always the OKRs, the actual measurements that you apply to things that we're doing. But at the end of the day, can we get the requirements from our business partners, bring those requirements to bear in technology, and really enable the indoctrination of these requirements throughout our clinical and healthcare kills? >> What about they're always pillars here, right? Governance, huge pillar, security, huge pillar, especially in your world, right? >> Yeah. >> So making that move over to the cloud and still recognizing that these are essentials that you have to have in place, I wouldn't say adjustments, but what kind of, I guess, recognition have you had toward that and making sure that you're still very true to those principles that are vital in the terms of public health? >> It is a great question because our secretary at the time and our governor, Roy Cooper, were very focused on enabling transparency. We had to be very transparent with what we were doing because the residents in North Carolina were just really kind of, "What's going on?" It was a scary time for a lot of us. So transparency was a key element towards our success. And in order to do that, you've got to have proper security. You got to have proper governance. You've got to have proper builds within technology that really enable that kind of visibility. One of the things that we did very early on was we set up a governance structure for our cloud environments so that as we wanted to and stand up an easy-to environment or we wanted to do some sort of work within a cloud or stand up in a different environment, we were able actually to set up a framework for how do you introduce that. Are you doing it correctly? Do you have the proper security on it? Do you have the funding for it? Like all the steps that you need to really kind of build into the scaffolding around a lot of these efforts we had to put in place and pretty quickly to get them going. But once we did that, the acceptance and the adoption of it was just tremendous. I mean, it was a light on for all of our business partners 'cause they understood I can either build on-prem, in which case I won't be able to get what I want in any kind of reasonable time period. Or I can build on cloud. And I can have it in some cases in 48 hours. >> Right, tomorrow. >> Yeah, exactly. >> You know, it was a huge difference. >> So where are you there? I mean, this is just not like a really big old lift and shift and we're all done and this is great. Cloud's taken care of all of our needs. Where are you in terms of the journey that you're undertaking? And then ultimately where do you want to go, like how far? What kind of goals have you set for yourself for the next two, three years down the road? >> Yeah, so this is an exciting part because we have actually- Like I mentioned earlier, we are a cloud-first cloud-only strategy, right? There's no reasons for us to be on-prem. It's just a matter of us kind of sunsetting legacy systems and bringing on cloud performance. We hope to be a 60% of our applications, which we have over 400 applications. So it's pretty large footprint. But we're wanting to migrate all of that to the cloud by 2025. So if we can achieve that, I think we'll be well on our way. And the momentum will carry forward for us to do that. We've actually had to do a reorganization of our whole IT structure. I think this is an important part to maintain that momentum because we've reorganized our staff, reorganized ourselves so that we can focus more on how do you adopt cloud, how do you bring in platforms which are all cloud-based, how do you use data within those systems? And that has allowed us to kind of think differently about our responsibilities, who's accountable for what, and to kind of keep those, that momentum going. So we've got some big projects that are on right now. Some of them are lift and shift, like you mentioned. We have a project with kind of a clumsy, monolithic system. It's called (indistinct). We're trying to migrate that to the cloud. We're in the process of doing that. And it's an excellent demonstration of capability once we pull that off. And then of course any new procurement that we put out there no one's making anything for on-prem anymore. Everyone's making their SaaS products for cloud-based experiences. Or if we're going to build or just use integrators then we'll build that in house. But all of it's based on cloud. >> And you mentioned SaaS. How much of this stuff are you doing on your own? And how much are you doing through managed services? >> Yeah, so like I mentioned, we have over 400 applications. So we had a pretty large footprint, right? >> Big, it's huge, right. >> So we're only who we are, and we can only build so much. So we're kind of taking- We did a application rationalization effort, which kind of identified some threats to our systems. Like maybe they're older things, FoxPro, kind of older languages that we're using. And in some cases we got people who are retiring. And there's not many people who can support that anymore. So how do we take those and migrate them to the cloud, either put them on a Salesforce or ServiceNow or Microsoft Dynamics platform and really kind of upgrade those systems? So we're in the process of kind of analyzing those elements. But yeah, that's kind of the exciting launch, if you will, of kind of taking the existing visibility of our applications and then applying it to what we're capable of with the cloud. >> And if you had advice that you could give to your colleagues who are in public health or just in public, the public sector- And your resources, they're finite. This is kind of what you have to deal with. And yet you have needs, and you're trying to stay current. You've got talent challenges, right? You've got rev or spending challenges. So if you could sit down your colleagues in a room and say, "Okay, this has been our experience. Here's what I would keep an eye out for," what kind of headlights would you beat for them? >> Yeah, so I think the biggest aha that I'd like to share with my contemporaries out there is that you've got a great ability to lower your costs, to excite your own personnel because they want to work on the new stuff. We've actually set up a whole professional development pathway within our organization to start getting people certified on AWS, certified on other platforms, to get them ready to start working in those environments. And so all of that work that we're been doing is coming together and allowing us to maintain the momentum. So what I'd recommend to people is, A, look at your own individual staff. I don't think you need to go outside to find the talent. I think you can train the talent that you have interior. I think you've got to aggressively pursue modernization because modernization enables a lot more. It's less expensive. It enables quicker adoption of business requirements and modern business requirements. And then lastly, focus on your data sharing because what you're going to find in the platforms and in the clouds is that there is a lot more opportunities for data integrations and conjoining disparate data sources. So if you can do those elements, you'll find that your capabilities on the business side are much more, much greater on the other end. >> Don't be scared, right, jump in? (laughing) >> Definitely don't be scared. Don't be, the water's warm. (host laughing) Come on in, you're fine, you're fine. (laughing) >> No little toe dipping in there. You're going to dive into the deep end, let her rip. >> Exactly, just go right in, just go right in. >> Well, it sounds like you've done that with great success. >> I'm very happy with it. >> Congratulations on that. And wish you success down the road. >> Thank you very much, I appreciate it. >> Yeah, thank you, Charles. All right, back with more. You are watching theCUBE here in Las Vegas. theCUBE of course the leader, as you know, in tech coverage. (soft music)

>>Now welcome back to the Cube as we continue our coverage here. AWS Reinvent 2022, going out here at the Venetian in Las Vegas. Tens of thousands of attendees. That exhibit Hall is full. Let me tell you, it's been something else. Well, here in the executive summit, sponsored by Accenture. Accenture rather. We're gonna talk about Baptist Health, what's going on with that organization down in South Florida with me. To do that, I have Tony Abro, who's the SVP and Chief Digital and Information Officer. I have Ashley Lane, the managing director of the Accenture Healthcare Practice, and on the far end Poop Kumar, who is the VP and cto Baptist Health Florida won and all. Welcome. Thank you. First off, let's just talk about Baptist Health, the size of your footprint. One and a half million patient visits a year, not a small number. >>That was probably last year's number, but okay. >>Right. But not a small number about your footprint and, and what, I guess the client base basically that you guys are serving in it. >>Absolutely. So we are the largest organization in South Florida system provider and the 11 hospitals soon to be 12, as you said, it's probably about 1.8 million by now. People were, were, were supporting a lot of other units and you know, we're focusing on the four southern counties of South Florida. Okay. >>So got day Broward. Broward, yep. Down that way. Got it. So now let's get to your migration or your cloud transformation. As we're talking about a lot this week, what's been your, I guess, overarching goal, you know, as you worked with Accenture and, and developed a game plan going forward, you know, what was on the front end of that? What was the motivation to say this is the direction we're going to go and this is how we're gonna get there? >>Perfect. So Baptist started a digital transformation initiative before I came about three years ago. The board, the executive steering committee, decided that this is gonna be very important for us to support us, to help our patients and, and consumers. So I was brought in for that digital transformation. And by the way, digital transformation is kind of an umbrella. It's really business transformation with technology, digital technologies. So that's, that's basically where we started in terms of consumer focused and, and, and patient focus. And digital is a big word that really encompasses a lot of things. Cloud is one of, of course. And, you know, AI and ML and all the things that we are here for this, this event, you know, and, and we've started that journey about two years ago. And obviously cloud is very important. AWS is our main cloud provider and clearly in AWS or any club providers is not just the infrastructure they're providing, it's the whole ecosystem that provides us back value into, into our transformation. And then somebody, I think Adam this morning at the keynote said, this is a team sport. So with this big transformation, we need all the help and that we can get to mines and, and, and hands. And that's where Accenture has been invaluable over the last two years. >>Yeah, so as a team sport then depu, you, you've got external stakeholders, otherwise we talked about patience, right? Internal, right. You've, you've got a whole different set of constituents there, basically, but it takes that team, right? You all have to work together. What kind of conversations or what kind of actions, I guess have you had with different departments and what different of sectors of, of the healthcare business as Baptist Health sees it in order to bring them along too, because this is, you know, kind of a shocking turn for them too, right? And how they're gonna be doing business >>Mostly from an end user perspective. This is something that they don't care much about where the infrastructure is hosted or how the services are provided from that perspective. As long as the capabilities function in a better way, they are seemingly not worried about where the hosting is. So what we focus on is in terms of how it's going to be a better experience for, from them, from, from their perspective, right? How is it going to be better responsiveness, availability, or stability overall? So that's been the mode of communication from that perspective. Other than that, from a, from a hosting and service perspective, the clientele doesn't care as much as the infrastructure or the security or the, the technology and digital teams themselves. >>But you know, some of us are resistant to change, right? We're, we're just, we are old dogs. We don't like new tricks and, and change can be a little daunting sometimes. So even though it is about my ease of use and my efficiency and why I can then save my time on so and so forth, if I'm used to doing something a certain way, and that's worked fine for me and here comes Tony and Depo and here comes a, >>They're troublemaker >>And they're stir my pot. Yeah. So, so how do you, the work, you were giving advice maybe to somebody watching this and say, okay, you've got internal, I wouldn't say battles, but discussions to be held. How did you navigate through that? >>Yeah, no, absolutely. And Baptist has been a very well run system, very successful for 60 something odd years. Clearly that conversation did come, why should we change? But you always start with, this is what we think is gonna happen in the future. These are the changes that very likely will happen in the future. One is the consumer expectations are the consumer expectations in terms of their ability to have access to information, get access to care, being control of the process and their, their health and well-being. Everything else that happens in the market. And so you start with the, with that, and that's where clearly there are, there are a lot of signs that point to quite a lot of change in the ecosystem. And therefore, from there, the conversation is how do we now meet that challenge, so to speak, that we all face in, in, in healthcare. >>And then from there, you kind of designed the, a vision of where we want to be in terms of that digital transformation and how do we get there. And then once that is well explained and evangelized, and that's part of our jobs with the help of our colleagues who have, have been doing this with others, then is the, what I call a tell end show. We're gonna say, okay, in this, in this road, we're gonna start with this. It's a small thing and we're gonna show you how it works in terms of, in terms of the process, right? And then as, as you go along and you deliver some things, people understand more, they're on board more and they're ready for for more. So it's iterative from small to larger. >>The proof is always in the place, right? If you can show somebody, so actually I, I obviously we know about Accenture's role, but in terms of almost, almost what Tony was just saying, that you have to show people that it works. How, how do you interface with a client? And when you're talking about these new approaches and you're suggesting changes and, and making these maybe rather dramatic proposals, you know, to how they do things internally, from Accenture's perspective, how do you make it happen? How, how do you bring the client along in this case, batches >>Down? Well, in this case, with Tony and Depu, I mean, they have been on this journey already at another client, right? So they came to Baptist where they had done a similar journey previously. And so it wasn't really about convincing >>Also with Accenture's >>Health, also with Accenture's Health, correct. But it wasn't about telling Tony Dupe, how do we do this? Or anything like that. Cuz they were by far the experts and have, you know, the experience behind it. Well, it's really like, how do we make sure that we're providing the right, right team, the right skills to match, you know, what they wanted to do and their aspirations. So we had brought the, the healthcare knowledge along with the AWS knowledge and the architects and you know, we said that we gotta, you know, let's look at the roadmap and let's make sure that we have the right team and moving at the right pace and, you know, testing everything out and working with all the different vendors in the provider world specifically, there's a lot of different vendors and applications that are, you know, that are provided to them. It's not a lot of custom activity, you know, applications or anything like that. So it was a lot of, you know, working with other third party that we really had to align with them and with Baptist to make sure that, you know, we were moving together at speed. >>Yeah, we've heard about transformation quite a bit. Tony, you brought it up a little bit ago, depu, just, if you had to define transformation in this case, I mean, how big of a, of a, of a change is that? I mean, how, how would you describe it when you say we're gonna transform our, you know, our healthcare business? I mean, I think there are a lot of things that come to my mind, but, but how do you define it and, and when you're, when you're talking to the folks with whom you've got to bring along on this journey? >>So there's the transformation umbrella and compos two or three things. As Tony said, there is this big digital transformation that everybody's talking about. Then there is this technology transformation that powers the digital transformation and business transformation. That's the outcome of the digital transformation. So I think we, we started focusing on all three areas to get the right digital experience for the consumers. We have to transform the way we operate healthcare in its current state or, or in the existing state. It's a lot of manual processes, a lot of antiquated processes, so to speak. So we had to go and reassess some of that and work with the respective business stakeholders to streamline those because in, it's not about putting a digital solution out there with the anti cured processes because the outcome is not what you expect when you do that. So from that perspective, it has been a heavy lifting in terms of how we transform the operations or the processes that facilitates some of the outcomes. >>How do you know it's working >>Well? So I I, to add to what Deep was saying is I think we are fortunate and that, you know, there are a lot of folks inside Baptist who have been wanting this and they're instrumental to this. So this is not a two man plus, you know, show is really a, you know, a, a team sport. Again, that same. So in, in that, that in terms of how do we know it works well when, when we define what we want to do, there is some level of precision along the way. In those iterations, what is it that we want to do next, right? So whatever we introduce, let's say a, a proper fluid check in for a patient into a, for an appointment, we measure that and then we measure the next one, and then we kind of zoom out and we look at the, the journey and say, is this better? >>Is this better for the consumer? Do they like it better? We measure that and it's better for the operations in terms of, but this is the interesting thing is it's always a balance of how much you can change. We want to improve the consumer experience, but as deeply said, there's lot to be changed in, in the operations, how much you do at the same time. And that's where we have to do the prioritization. But you know, the, the interesting thing is that a lot of times, especially on the self servicing for consumers, there are a lot of benefits for the operations as well. And that's, that's where we're in, we're in it together and we measure. Yeah, >>Don't gimme too much control though. I don't, I'm gonna leave the hard lifting for you. >>Absolutely, absolutely right. Thank you. >>So, and, and just real quick, Ashley, maybe you can shine some light on this, about the relationship, about, about next steps, about, you know, you, you're on this, this path and things are going well and, and you've got expansion plans, you want, you know, bring in other services, other systems. Where do you want to take 'em in the big picture in terms of capabilities? >>Well, I, I mean, they've been doing a fantastic job just being one of the first to actually say, Hey, we're gonna go and make an investment in the cloud and digital transformation. And so it's really looking at like, what are the next problems that we need to solve, whether it's patient care diagnosis or how we're doing research or, you know, the next kind of realm of, of how we're gonna use data and to improve patient care. So I think it's, you know, we're getting the foundation, the basics and everything kind of laid out right now. And then it's really, it's like what's the next thing and how can we really improve the patient care and the access that they have. >>Well, it sure sounds like you have a winning accommodation, so I I keep the team together. >>Absolutely. >>Teamwork makes the dream >>Work. Absolutely. It is, as you know. So there's a certain amount of, if you look at the healthcare industry as a whole, and not, not just Baptist, Baptist is, you know, fourth for thinking, but entire industry, there's a lot of catching up to do compared to whatever else is doing, whatever else the consumers are expecting of, of an entity, right? But then once we catch up, there's a lot of other things that we were gonna have to move on, innovate for, for problems that we maybe we don't know we have will have right now. So plenty of work to do. Right. >>Which is job security for everybody, right? >>Yes. >>Listen, thanks for sharing the story. Yeah, yeah. Continued success. I wish you that and I appreciate the time and expertise here today. Thank you. Thanks for being with us. Thank you. Thank you. We'll be back with more. You're watching the Cube here. It's the Executive Summit sponsored by Accenture. And the cube, as I love to remind you, is the leader in tech coverage.

(steady music) >> Oh, welcome back here on theCUBE. I'm John Walls, we're in The Venetian and day one of a jam-packed three days here at AWS re:Invent '22. This is the Executive Summit sponsored by Accenture, and it is Merck time. And I mean, it is loaded with Merck time. We have quite the panel here, in fact. First threesome of the day, by the way. I see you guys have really loaded up nicely. Ron Kim is with us, the SVP and CTO of Merck. Ron, good to see you, sir. >> Thanks, John. >> Also, Fran Gaetens, who's the VP of Technology Infrastructure, Operations, and Experience, which I want to hear more about. Love that job title, Fran. >> Thanks, John. >> And Sean Finnerty, VP of Cloud and Infrastructure Technology. Again, everybody here from Merck. So fellows, thanks for being with us. >> Thanks, John. >> Appreciate the time. >> Yeah. >> So let's just talk about Merck, first off in general in terms of what's happening with the cloud. And Ron, I'll let you jump onto that first. I realize this talk of journey, right? >> Mm-hm. >> It's different for everybody, different slices depending upon where you are, where you start, where you need to finish. Where are you right now in terms of what you're doing with the cloud? >> Yeah, John, we've been on this journey for about two years, have done some great work and achieve some great results in proving we could move to the cloud, moving to the cloud at scale, achieving really measurable financial and operational results. Where we're focusing now going forward is transforming the business. And as you know, our business is saving and improving lives. And so when we talk about moving things to the cloud, it's much more than just moving servers or things like that. It's really contributing towards our business that saves and improves lives. So for our work that we work on together moving into the cloud, the stakes are high, but we think the opportunity's great. And the way to seize that opportunity is what we're doing now, is our BlueSky program and working with AWS and Accenture on it. >> Yeah, so two years, you're two years in. It's like nascent stage still, right? I mean, and it never ends, (laughs) frankly. >> Yeah. >> But talk about that progression and was it, you know, baby steps, was it diving in? I mean, how do you decide, you know, the batting order basically here about how you're going to get things going? >> The early parts of the the two-year journey so far, we're really starting small, primarily driven by a central team. And we did that consciously to get momentum, build the foundation, prove again we could move things to the cloud with success, we could start to scale. And then as that journey went on, now instead of just relying on the central team, we're starting to get the rest of the company involved. So this is not just this team doing the cloud journey. It's the whole company, and that's an ongoing journey, getting all the different stakeholders involved and things like that. But I think that's where we are on the journey now, is look, let's lock arms with everybody in the company. So it's a Merck-wide cloud transformation, not just the BlueSky team. >> Right, and of course, as you know, the C-suite's got to be behind all this. And we hear about how that it's now being driven in some cases, you know, these kind of transformations, whether it's from CEO level down the CTO and CIO and what have you. Fran, the experience part of your job. I just want to get to that real quick. So you know, how do you define that? >> Yeah. First of all, I'm delighted you asked. >> Okay. (laughs) >> And the focus on experience that my team's accountable for transcends, you know, our cloud journey. We have held for the last three years within my organization a priority that's focused on improving the experience that colleagues in our company have with workplace technology and services. And so I'd come into this role at the time and thought carefully, you know, about how to best title our organization in a way that would draw curiosity or inquisition. >> Sure. >> A very creative colleague that we have an opportunity to work with in our company suggested the term, and I loved it and ran with it. And today, it's, you know, still something that we spend a significant portion of cycles focused on. >> Well, it's a very clear signal, right? And a reminder as well that ultimately the experience whether it's your internal stakeholders or external, your customers, right, that you're delivering a very pleasant and efficient, and hopefully you said life-saving >> Yeah. >> experience as well. And I think that'd be a pretty good reminder for your team, isn't it? >> It is. >> "Hey, we're all part of the experience here." >> Yeah. >> Yeah. Right, so Sean, let's talk about some of the things that we've discussed here, branching out within Merck. >> Yep. >> You know, and making it a company effort, not just an IT effort. Right, now all of a sudden, you're into everybody's business and everybody is sharing this. I mean, is there buying that's necessary here? I mean, how do you bring that bunch along? You've all lived it, you know it. They're experiencing it for the first time. >> Yeah, it's a great question and it's one we get quite a bit walking the halls here at re:Invent. We're very lucky in that we do have, you mentioned earlier, top-down support, right? So when we're talking about moving to the cloud, we're not just running around the halls of the technology, you know, cubes of all the people that are sitting there at computers banging away every day. We're meeting with the CEO and a significant portion of the executive team, talking about how does our cloud journey underpin our business transformation aspirations? How do we speed up scientific research? How do we do clinical trials more effectively? How do we manufacture medicine more effectively, more reliably? Those are all underpinned by this technology transformation that we're embarking on sort of from the bottoms up, and meeting in the middle with the top-down strategic imperative to transform the business by leveraging technology. So that clear and unambiguous support coming from the C-suite at our company allows us to prioritize very aggressively and point at that mission to say, "Hey, we're not just here to talk about moving a server or two. We're here to talk about how we transform scientific research and discovery in the interest of our patients and delivering medicine more effectively, more quickly." So it's really, really interesting. >> Yeah, and so being on one side of that, you know, obviously you're dealing with people, whether chemists, scientists, whomever doing computational chemistry whatever it might be. They know their business and you're trying to integrate these new capabilities into their business, right? How do you do that? I mean, how do you know what they need and how do they tell you what they need when they don't know what you have? (laughs) >> That's quite a question. >> Yeah. I got there. >> Yeah, I mean, my initial thought is, you know, there has to be a compelling value to anybody getting impacted by this. And that's what we all work to do. So whether it's faster, less lead time, reducing cycle times, more reliability, innovation, I mean, there has to be something in it for them, and the work we're doing crosses that whole spectrum. So some of the efforts we have, "Hey, this is a cost-savings effort, this is for agility, this is for speed." So you know, it can't be just we're just doing this for the sake of moving of the cloud. There has some business value in it. And you know, Sean and the team have done a great job on kind of putting the rigor behind how do we describe that value so people then say, "Is that value really there or not? And does it really add up?" And I think that's been one of the keys to our success, is the work that Sean and members of his team have been doing is there's a pretty rigorous way we track our progress. And we've involved finance from day one in that. So having their buy in, you know, gives the whole set of results a lot of credibility. >> But tell me about that, Sean, about in terms of identifying value and quantifying it, in terms that a bottom line can orient to that. >> Yeah, absolutely. I mean, I've been at the cloud migration game myself personally for years, right? I got into this game back in 2011. The challenge of those programs has always been articulating the value associated with migrating stuff. It's easy to say, "I'm going to take a server. I'm going to move it from here to here. Then that difference is X, point at that." That's easy, everyone can understand that. But the labor efficiencies and the business value and the business transformation that comes with moving a capability from on-prem or from another hosting service to the cloud and transforming how we deliver, manage, operate, and scale those solutions, that's really where the power of this comes from, is business value tied to discrete actions, moving systems with a plan from one point to another point. And then being able to clearly articulate the value by implementing, as Ron mentioned, models we've created. So we've created actually financial calculation models to put dollars and cents next to labor efficiencies, time liberated, you know, the ability to deliver with higher velocity, higher quality, higher reliability. Those now have dollar values associated with them, which we're able to take, apply to our portfolio, and look for those opportunities that jump out as, "Hey, you know, that one's worth a million bucks. Let's prioritize that one. The ones that maybe have lower value or less business impact, you know, let's put those to the side and get to those later." So we can constantly demonstrate that not only are we raising our ability to deliver for our patients, but we're also delivering value back to the corporation to invest in other things that need focus and attention. >> Yeah, so talk about AWS and Accenture a little bit about, I mean, obviously big players with this. I'm assuming that interaction, maybe Fran, you know, talk about the partnership and again, how they have helped you get to the point that where you currently reside. >> Yeah, our partnership with both firms has been longstanding. That said, you know, what's changed in a market way happened a couple years ago when we originated this cloud acceleration program that we called BlueSky. We worked directly with Accenture to develop a comprehensive business case that, you know, fundamentally lined out the detail of our intention, how we would prosecute this work, and you know, among other things be crystal clear about the value at stake and how we would capture and realize that over time. So you know, through that lens, it's really taken a village with parties from all three firms, you know, to come together, prosecute this important work, but likewise, as I like to say, keep score, you know, in the context of value because ultimately, it's the one thing that we can talk about unambiguously with the program in the context of measurable results. >> Because of the work you do, obviously, you know, invaluable in many respects. But just the thought about cloud, and I know governance, security, compliance, all these things are critical. You know, how do those weigh in, in terms of considerations you have to make? And especially going forward as you develop new ideas, new things, ideas you're trying to bring to market, >> Yeah. >> I mean, how much does that play and the cloud and what exposures there might be? >> Yeah, it plays in quite a bit. And no matter what type of work we do, cloud or on-premise, I mean, security is of utmost importance. That's how we operate. Now what's interesting is when we think about in AWS, you know, AWS has the ability, they have the the scale and the learnings from multiple clients, right? So rather than a single company like us trying to figure out security on our own, we can benefit from what are all the lessons that they've learned that they bake back into their platform. So that's been a great benefit. But regardless of our partner, we'll always be very, a lot of scrutiny about security no matter what. And that's how we should operate. But the benefits of the platform within AWS, I mean, there's a lot of security intelligence built in from their experience, so that's- >> If I can add to that- >> Sure. >> Yeah. To build on prior remarks that Sean had articulated, this migration to the cloud, right, happens to be a catalyst for a broader transformation. One where we're fundamentally changing our ways of working. Ways that consider, you know, topics like security, compliance, documentation, regulatory requirements. And choosing to bake those in to these solutions from the onset rather than consider them as an appendage or an afterthought. So you know, the cloud is a really important part of this. You know, there's no mistake about it, but it's also a powerful catalyst for something that's broader. >> Tremendously more efficient, right? With our thinking and how we're going to plan and how we're going to execute. >> Yeah, and to build on that even more, we view it as an opportunity to raise the bar on our compliance, security, and regulatory readiness game. As we're touching applications across our portfolio, rearchitecting, leaning in on things like the well-architected framework and other things that AWS and Accenture bring to bear. We set the bar higher when we move things from where they are today to a new destination and introduce automation so that that uplift of control does not come at the cost of additional time or labor. It's simply we're raising the bar in ourselves. We're using this transformational opportunity to implement that change. Our customers are along for the ride and reap the benefits of the fact that, you know, we've raised the bar on ourselves, basically. >> Well, you said two years, so the first steps, and I'm sure the next ones are going to be just as successful. I really appreciate the time. Thanks for sharing that and for bringing so much expertise at the table. >> Thanks, John. >> Appreciate that, good to have you guys with us. >> Thanks. >> Talking about Merck and their cloud transformation. Love that word, we've been talking a lot about it this week. You're watching theCUBE, of course, here at the Executive Summit sponsored by Accenture. And theCUBE being, of course, the leader at tech coverage. (calm music)

(relaxing intro music) >> Welcome back to theCUBE's Coverage here live at reinvent 2022. We're here at the Executive Summit upstairs with the Accenture Set three sets broadcasting live four days with theCUBE. I'm John Furrier your host, with two great guests, cube alumnis, back Tanuja Randery, managing director Amazon web service for Europe middle East and Africa, known as EMEA. Welcome back to the Cube. >> Thank you. >> Great to see you. And Karthik Narain, who's the Accenture first cloud lead. Great to see you back again. >> Thank you. >> Thanks for coming back on. All right, so business transformation is all about digital transformation taken to its conclusion. When companies transform, they are now a digital business. Technologies powering value proposition, data security all in the keynotes higher level service at industry specific solutions. The dynamics of the industry are changing radically in front of our eyes for for the better. Karthik, what's your position on this as Accenture looks at this, we've covered all your successes during the pandemic with AWS. What, what do you guys see out there now as this next layer of power dynamics in the industry take place? >> I think cloud is getting interesting and I think there's a general trend towards specialization that's happening in the world of cloud. And cloud is also moving from a general purpose technology backbone to providing specific industry capabilities for every customer within various industries. But the industry cloud is not a new term. It has been used in the past and it's been used in the past in various degrees, whether that's building horizontal solutions, certain specialized SaaS software or providing capabilities that are horizontal for certain industries. But we see the evolution of industry cloud a little differently and a lot more dynamic, which is we see this as a marketplace where ecosystem of capabilities are going to come together to interact with a common data platform data backbone, data model with workflows that'll come together and integrate all of this stuff and help clients reinvent their industry with newer capabilities, but at the same time use the power of democratized innovation that's already there within that industry. So that's the kind of change we are seeing where customers in their strategy are going to implement industry cloud as one of the tenants as they go through their strategy. >> Yeah, and I see in my notes, fit for purposes is a buzzword people are talking about right size in the cloud and then just building on that. And what's interesting, Tanuja I want to get your thoughts because in the US we're one country, so yeah, integrating is kind of within services. You have purview over countries and these regions it's global impact. This is now a global environment. So it's not just the US North America, it's Latin America it's EMEA, this is another variable in the cross connecting of these fit for purpose. What's your view of the these industry specific solutions? >> Yeah, no and thanks Karthik 'cause I'm a hundred percent aligned. You know, I mean, you know this better than me, John, but 90% of workloads have not yet moved to the cloud. And the only way that we think that's going to happen is by bringing together business and IT. So what does that mean? It means starting with business use cases whether that's digital banking or smart connected factories or frankly if it's predictive maintenance or connected beds. But how do we take those use cases leverage them to really drive outcomes with the technology behind them? I think that's the key unlock that we have to get to. And very specifically, and Adam talked about this a lot today, but data, data is the single unifier for all of business and IT coming together to drive value, right? However, the issue is there's a ton of it, (John Furrier chuckling) right? In fact, fun fact if you put all the data that's going to be created over the next five years, which is more than the last 30 years, on a one terabyte little floppy, disk drive, remember those? Well that's going to be 15 round trips to the moon (John Furrier chuckling) and back. That's how much data it is. So our perspective is you got to unify, single data lake, you got to modernize with AI and ML, and then you're going to have to drive innovation on that. Now, I'll give you one tiny example if I may which I love Ryanair, big airline, 150 million passengers. They are also the largest supplier of ham and cheese sandwiches in the air. And catering at that scale is really difficult, right? If you have too much food wastage, sustainability issues, too little customers are really unhappy. So we work with them leveraging AWS cloud and AI ML to build a panini predictor. And in essence, it's taking the data they've got, data we've got, and actually giving them the opportunity to have just the right number of paninis. >> I love the lock and and the key is data to unlock the value. We heard that in the keynote. Karthik, you guys have been working together with AWS and a lot of successes. We've covered some of those on the cube. As you look at these industry solutions they're not the obvious big problems. They're like businesses, you know it could be the pizza shop it could be the dentist office, it could be any business any industry specific carries over. What is the key to unlock it? Is it the data? Is it the solution? What's that key? >> I think, you know the easier answer is all of the about, but like Tanuja said it all starts by bringing the data together and this is a funny thing. It's not creating new data. This data is there within enterprises. Our clients have these data the industries have the data, but for ages these data has been trapped in functional silos and organizations have been doing analytics within those functions. It's about bringing the data together whether that's a single data warehouse or a data mesh. Those are architectural considerations. But it's about bringing cross-functional data together as step one. Step two, is about utilizing the power of cloud for democratized innovation. It's no longer about one company trying to reinvent the wheel, or create a a new wheel within their enterprise. It's about looking around through the power of cloud marketplace to see if there's a solution that is already existing can we use that? Or if I've created something within my company can I use that as a service for others to use? So, the number one thing is using the power of democratized innovation. Second thing is how do you standardize and digitize functions that does not need to be reinvented every single time so that, you know, your organization can do it or you could use that or take that from elsewhere. And the third element is using the power of the platform economy or platforms to find new avenues of revenue opportunity, customer engagement and experiences. So these are all the things that differentiates organization, but all of this is underpinned by a unified data model that helps, you know, use all the (indistinct) there. >> Tanuja, you have mentioned earlier that not everyone has their journey of the cloud looks the same and certainly in the US and EMEA you have different countries and different areas. >> Yep. >> Their journeys are different. Some want speed and fees, some will roll their own. I mean data brick CEO, when I interviewed them that last week, they started database on a credit card swiped it and they didn't want any support. Amazon's knocking on their door saying, "you want support?" "No, we got it covered." Obviously they're from Berkeley and they're nerds, and they're cool. They can roll their own, but not everyone can. >> Yeah. >> And so you have a mix of customer profiles. How do you view that and what's your strategy? How do you get them over productive seeing that business value? What's that transformation look like? >> Yeah, John, you're absolutely right. So you've got those who are born in cloud, they're very savvy, they know exactly what they need. However, what I do find increasingly, even with these digital native customers, is they're also starting to talk business use cases. So they're talking about, "okay how do I take my platform and build a whole bunch of new services on top of that platform?" So, we still have to work with them on this business use case dimension for the next curve of growth that they want to drive. Currently with the global macroeconomic factors obviously they're also very concerned about profitability and costs. So that's one model. In the enterprise space, you have differences. >> Yeah. >> Right, You have the sort of very, very, very savvy enterprises, right? Who know exactly what they're looking for. But for them then it's about how do I lean into sustainability? In fact, we did a survey, and 77% of users that we surveyed said that they could accelerate their sustainably goals by using cloud. So in many cases they haven't cracked that and we can help them do that. So it's really about horses for courses there. And then, then with some other companies, they've done a lot of the basic infrastructure modernization. However, what they haven't been able to yet do is figure out how they're going to actually become a tech company. So I keep getting asked, can I become a tech company? How do I do that? Right? And then finally there are companies which don't have the skills. So if I go to the SMB segment, they don't always have the skills or the resources. And there using scalable market platforms like AWS marketplace, >> Yeah. >> Allows them to get access to solutions without having to have all the capabilities. So it really is- >> This is where partner network really kind of comes in. >> Absolutely. >> Huge value. Having that channel of solution providers I use that term specifically 'cause you're providing the solution for those folks. >> Yeah. Exact- >> And then the folks at the enterprise, we had a quote on the analyst segment earlier on our Cube, "spend more, save more." >> Yeah. >> That's the cloud equations, >> Yeah. because you're going to get it on sustainability you're going to save it on, you're going to save on cost recovery for revenue, time to revenue. So the cloud is the answer for a lot of enterprises out of the recession. >> Absolutely, and in fact, we need to lean in now you heard Adam say this, right? I mean the cost savings potential alone from on-prem to cloud is between 40 and 60 percent. Just that. But I don't think that's it John. >> The bell tightening he said is reigning some right size. Okay, but then also do more, he didn't say that, but analysts are generally saying, if you spend right on the cloud, you'll save more. That's a general thesis. >> Yeah. >> Do you agree with that? >> I absolutely think so. And by the way, usage is, people use it differently as they get smarter. We're constantly working with our customers by the way though, to continuously cost optimize. So you heard about our Graviton3 instances for example. We're using that to constantly optimize, but at the same time, what are the workloads that you haven't yet brought over to the cloud? (John Furrier chuckling) And so supply chain is a great idea. Our health cloud initiative. So we worked with Accenture on the Accenture Health Insights platform, which runs on AWS as an example or the Goldman Sachs one last year, if you remember. >> I do >> The financial cloud. So those, those are some of the things that I think make it easier for people to consume cloud and reimagine their businesses. >> It's funny, I was talking with Adam and we had a little debate about what an ISV is and I talked to the CEO of Mongo. They don't see themselves on the ISV. As they grew up on the cloud, they become platforms, they have their own ISVs and data bricks and Snowflake and others are developing that dynamic. But there's still ISVs out there. So there's a dynamic of growth going on and the need for partners and our belief is that the ecosystem is going to start doubling in size we believe, because of the demand for purpose built or so out of the box. I hate to use that word "out of the box", but you know turnkey solutions that you can buy another one if it breaks. But use the building blocks if you want to build the foundation. That is more durable, more customizable. Do that if you can. >> Well, >> but- >> we've got a phenomenal, >> shall we talk about this? >> Yeah, go get into- >> So, we've built a five year vision together, Accenture and us. which is called Velocity and you'll be much better in describing it, but I'll give you the simple version of Velocity which is taking AWS powered industry solutions and bringing it to market faster, more repeatable and at lower cost. And so think about vertical solutions sitting on a horizontal accelerator platform able to be deployed making transformation less complex. >> Yeah. >> Karthik, weight in on this, because I've talked to you about this before. We've said years ago the horizontal scalability of the cloud's a beautiful thing but verticals where the ML works great too. Now you got ML in all aspects of it. Horizontal verticals here now. >> Yeah, Yeah, absolutely. Again, the power of this kind of platform that we are launching, by the way we're launching tomorrow we are very excited about it, is, create a platform- >> What are you launching tomorrow? Hold on, I got news out there. What's launching? >> We are going to launch a giant platform, which will help clients accelerate their journey to industry cloud. So that's going to happen tomorrow. So what this platform would provide is that this is going to provide the horizontal capabilities that will help clients bootstrap their launch into cloud. And once they get into cloud, they would be able to build industry solutions on this. The way I imagine this is create the chassis that you need for your industry and then add the cartridges, industry cartridges, which are going to be solutions that are going to be built on top of it. And we are going to do this across various industries starting from, you know, healthcare, life sciences to energy to, you know, public services and so on and so forth >> You're going to create a channel machine. A channel creation machine, you're going to allow people to build their own solutions on top of that platform. And that's launching tomorrow. Make sure we get the news on that. >> Exactly. And- >> Ah, No, >> Sorry, and we genuinely believe the power of industry cloud, if you think about it in the past to create a solution one had to be an ISV to create a solution. What cloud is providing for industry today in the concept of industry clouds, this, industry companies are creating industry solution. The best example is, along with, you know, AWS and Accenture, Ecopetrol, which is a leader in the energy industry, has created a platform, you know called Water Intelligence and Management platform. And through this platform, they are attacking the audacious goal of water sustainability, which is going to be a huge problem for humanity that everybody needs to solve. As part of this platform, the goal is to reduce, you know, fresh water usage by 66% or zero, you know, you know, impact to, you know, groundwater is going to be the goal or ambition of Ecopetrol. So all of this is possible because industry players want to jump to the bandwagon because they have all the toolkit of of the cloud that's available with which they could build a software platform with which they can power their entire industry. >> And make money and have a good business. You guys are doing great. Final word, partnership. Where's it go next? You're doing great. Put a plugin for the Accenture AWS partnership. >> Well, I mean we have a phenomenal relationship and partnership, which is amazing. We really believe in the power of three which is the GSI, the ISV, and us together. And I have to go back to the thing I keep focused on 90% of workloads not in cloud. I think together we can enable those companies to come into the cloud. Very importantly, start to innovate launch new products and refuel the economy. So I think- >> We'll have to check on that >> Very, very optimistic. >> We'll have to check on that number. >> That seems a little- >> You got to check on that number. >> 90 seems a little bit amazing. >> 90% of workloads. >> That sounds, maybe, I'd be surprised. Maybe a little bit lower than that. Maybe. We'll see. >> We got to start turning it. >> It's still a lot. >> (laughs) It's still a lot. >> A lot more. Still first, still early days. Thanks so much for the conversation Karthik great to see you again Tanuja, thanks for your time. >> Thank you, John. >> Congratulations, on your success. Okay, this is theCube up here in the executive summit. You're watching theCube, the leader in high tech coverage, we'll be right back with more coverage here, and the Accenture set after the short break. (calm outro music)

(mellow music) >> Oh, welcome back to theCUBE. We continue our coverage here at AWS re:Invent 22. We're in the Venetian in Las Vegas, and this place is hopping. I'm tell you what. It is a nearly standing room only that exhibit floor is jam packed, and it's been great to be along for the ride here on Accenture's sponsorship at the Executive summit as well. We'll talk about Pfizer today, you know them quite well, one of the largest biopharmaceutical companies in the world but their tech footprint is impressive, to say the least. And to talk more about that is Wes Barnes, senior Director of Pfizer's Digital Hosting Solutions. Wes, good to see you, sir. >> Good to meet you, John. >> And Jon Harrison, the North American lead for Infrastructure and engineering at Accenture. Jon, good to see you as well. >> Good to see you as well. >> Thanks for joining us. >> Happy to be here. >> Alright, so let's jump in. Pfizer, we make drugs, right? >> Pharmaceuticals. >> Yes. >> Among the most preeminent, as I said biopharms in the world. But your tech capabilities and your tech focus as we were talking about earlier, has changed dramatically in the 18 years that you've been there. >> Yep. >> Now, talk about that evolution a little bit to where you were and what you have to be now. >> Yeah, yeah. It's interesting. When I started at Pfizer, IT was an enabling function. It was akin to HR or our facilities function. And over the past couple years, it's dramatically changed. Where Digital now is really at the center of everything we do across Pfizer. You know it really is a core strategic element of our business. >> Yeah. And those elements that you were talking about, just in terms of whether it's research, whether it's your patients, I don't want to go through the laundry lists the litany of things, but the touch points with data and what you need it to do for you in terms of you know, computations, what you, the list is long. It's pretty impressive. >> Yeah, yeah, for sure yeah. >> I mean, shed some light on that for us. >> We cannot release a medicine without the use of technology. And if you think about research now, a huge component of our research is computational chemistry. Manufacturing medicines now is a practice in using data and analytics and predictive machine learning and analytics capabilities to help us determine how to best you know, apply the capabilities to deliver the outcomes that we need. The way in which we connect with patients and payers now is wholly digital. So it's an entirely different way of operating than it was 10 years ago. >> And the past three years, pretty remarkable in many respects, to say the least, I would think, I mean, John, you've seen what Pfizer's been up to, talk about maybe just this, the recent past and all that has happened and what they've been able to do. >> Yeah, I mean, what is so exciting to me about working with a company like Pfizer and working in life sciences more broadly is the impact that they make on patients around the world world, right? I mean, think about those past three years and Pfizer stepped up and met the moment for all of us, right? And as we talk a little bit about the role that we played together with Pfizer with AWS in their journey to the cloud, it's so motivating for myself personally it's so motivating for every single person on the team that we ask to spend nights and weekends migrating things to the cloud, creating new capabilities, knowing that at the end of the day, the work that they're doing is making the world a healthier place. >> Yeah, we talk so much about modernization now, right? And it's, but it kind of means different things to different people depending on where you're coming into the game, right? If you've been smart and been planning all along then this is not a dramatic shift in some cases though, for others it is. Right? >> Yeah. >> Traumatic in some cases for some people. >> For sure. >> For Pfizer, I mean talk about how do you see modernization and what does it mean to your operations? >> Following our success of the COVID program of 2021, I mean it became evident to us that, you know we needed to maintain a new pace of innovation and in fact try to find ways to accelerate that pace of innovation. And as I said earlier everything we do at Pfizer is centered around digital. But despite that, and despite 10 years of consolidating infrastructure and moving towards modern technology, last year, only 10% of Pfizer's infrastructure was in the native public cloud. So we had a problem to solve. In fact, I remember, you know, we had to build up our clinical systems to support the volume of work that we were doing for COVID-19 vaccine. We were rolling things into our data center to build up the capacity to achieve what we needed to achieve. Moving to the public cloud became more imperative to try to achieve the scale and the modern capabilities that we need. >> And so where did you come into play here with this? Because obviously as a partner you're right alongside for the ride but you saw these inherent challenges that they had and how did Accenture answer the bell there? >> Well, so look, I mean we saw Pfizer react to the pandemic. We saw them seize the moment. We talked together about how IT needed to move quicker and quicker towards the cloud to unlock capabilities that would serve Pfizer's business well into the future. And together we laid out some pretty ambitious goals. I mean, really moving at a velocity in a pace that I think for both Accenture and AWS surpassed the velocity and pace that we've done anywhere else. >> Yeah, right, yeah. >> So we've set out on an ambitious plan together. You know, I was kind of reflecting about some of the successes, what went well what didn't in preparation for re:Invent. And you know, many of the folks that'll listen to this will remember the old days of moving data centers when you'd have a war room you'd have a conference bridge open the whole time. Someone would be running around the tile floor in the data center, do a task, call back up to the bridge and say, what do I do next, right? Then when I think about what we did together at Pfizer in moving towards the public cloud, I mean, we had weekends most weekends where we were running a wave with 10,000 plus discrete activities. >> Yeah. >> Wow. >> Right, so that old model doesn't scale. >> Right. >> And we really anchored, >> You have a very crowded data center with a lot of people running into each other. >> You'd have a whole lot of people running around. But we really anchored to an Accenture capability that we call myNav Migrate. I know you guys have talked about it here before so I won't go into that. But what we found is that we approached this problem of velocity not as a technical problem to solve for but as a loading and optimization problem of resources. Right, thought about it just a little bit different way and made sure that we could programmatically control command and control of the program in a way that people didn't have to wait around all Saturday afternoon to be notified that their next activity was ready, right? They could go out, they could live their day and they could get a notification from the platform that says, hey it's about your turn. Right, they could claim it they could do it, they could finish it, and that was really important to us. I mean, to be able to control the program in that type of way at scale. >> Yeah, by the way, the reason we went as fast it was a deliberate choice and you'll talk to plenty of folks who have a five year journey to the public cloud. And the reason we wanted to move as fast as we did and Jon talked about some of it, we wanted to get the capabilities to the business as quickly as we could. The pace of innovation was such that we had to offer native cloud capabilities we had to offer quickly. We also knew that by compressing the time it took to get to the cloud, we could focus the organization get it done as economically as possible but then lift all boats with the tide and move the organization forward in terms of the skills and the capabilities that we need to deliver modern outcomes. >> So, you know, we talk about impacts internally, obviously with your processes, but beyond that, not just scientists not just chemists, but to your, I mean, millions of customers, right? We're talking, you know, globally here. What kind of impacts can you see that directly relate to them, and benefits that they're receiving by this massive technical move you've made? >> Pfizer's mission is breakthroughs that change patient lives. I mean, the work that we do the work that everybody does within Pfizer is about delivering therapies that, you know provide health outcomes that make people live longer, live healthier lives. For us, modernizing our infrastructure means that we can enable the work of scientists to find novel therapies faster or find things that perhaps couldn't have been found any other way without some of the modern technologies that we're bringing to bear. Saving money within infrastructure and IT is treasure that we can pour back into the important areas of research or development or manufacturing. We're also able to, you know, offer an ecosystem and a capability in which we connect with patients differently through digital mechanisms. And modern cloud enables that, you know, using modern digital experiences and customer experience, and patient experience platforms means that we can use wearable devices and mobile technologies and connect to people in different ways and offer solutions that just didn't exist a couple years ago. >> And so, I mean, you're talking about IoT stuff too, right? >> 100%. >> It's way out on the edge and personal mobile, in a mobile environment. And so challenges in terms of you know, data governance and compliance and security, all these things, right? They come into play because it's personal health information. So how, as you've taken them, you know to this public cloud environment how much of a factor are those considerations? Because, you know, this is not just a product a service, it's a live human being. >> Yeah. I mean, you start with that, you think about it through the process and you think about it afterwards, right, I mean, that has to be a core factor in every stage of the program, and it was. >> So in, in terms of where you are now, then, okay, it's not over. >> It's never over. >> I mean, you know, as good as you are today and as fast as you are and as accurate and as efficient. >> Yeah. >> Got to get better, right? You got to stay competitive. >> Yeah. >> So where do you find that? Because, you know, with powers being what they are with speed and what it is how much more is there to squeeze out of this rock? >> There's a lot more to squeeze out of the rock. If you think about what we've done over the past year it's about creating sort of a new minimum viable product for infrastructure. So we've sort of raised the bar and created an environment upon which we can continue to innovate that innovation is going to continue sort of forever at this point. You know, the next focus for us is how to identify the business processes that deliver the greatest value ultimately to our patients. And use the modern platform that we've just built to improve those processes to deliver things faster, deliver new capabilities. Pfizer is making a huge investment in digital medicines therapies that are delivered through smart devices through wearables using, as I said technology that didn't exist before. That wouldn't be possible without the platform that we've built. So over the past year, we've come a long way but I think that we've effectively set the table for all of the things that are yet to come. >> So, Jon, how do you then, as you've learned a lot about life science or, and certainly Pfizer with what they're up to, how do you then apply, you know, what you know about their world to what you know about the tech world and make it actionable for growth to make it actionable for, for future expansion? >> Yeah, I mean, we start by doing it together, right? I think that's a really important part. Accenture brings a wealth of knowledge, both industry experience and expertise, technology experience and expertise. We work together with our clients like Pfizer with our partners like AWS to bring the best across that power of three to meet clients where they're at to understand where they want to go, and then create a bespoke approach that meets their business needs. And that's effectively what we're doing now, right? I mean, if you think about the phase that we've just went through, I mean, a couple of fast facts here no pun intended, right? 7,800 server instances across 11 operating system versions 7,500 databases across 20 database versions, right? 4,700 applications, 350,000 migration activities managed across an eight month period. >> In eight months. >> Yeah. But that's not the goal, right? The goal is now to take, to Wes' point that platform that's been developed and leverage that to the benefit of the business ultimately to the benefit of the patient. >> You know, why them, we have we've talked a lot about Pfizer, but why Accenture? What, what, what's, 'cause it's got to be a two way street, right? >> We've had a long partnership with Accenture. Accenture supports a huge component of our application environment at Pfizer and has for quite a long time. Look, we didn't make it easy on them. We put them up against a large number of world class SIs. But look, Accenture brought, you know, sort of what I think of as the trifecta here. They brought the technical capabilities and knowledge of the AWS environment. They brought the ability to really understand the business outcomes that we were trying to achieve and a program leadership capability that, you know I think is world class. And Jon talked about myNav, you know, we recognized that doing what we were trying to do in the time that we were doing it required new machinery, new analytics and data capabilities that just didn't exist. Automation didn't exist. Some people experience capabilities that would allow us to interface with application owners and users at a velocity and a pace and a scale that just hasn't been seen before at Pfizer. Accenture brought all three of those things together and I think they did a great job helping us get to where we need to be. >> When you hear Jon rattle through the stats like he just did, right? We talk about all, I mean, not that I'm going to ask you to pat yourself on the back but do you ever, >> He should. >> Does it blow your mind a little bit, honestly that you're talking about that magnitude of activity in that compressed period of time? That's extraordinary. >> It's 75% of our global IT footprint now in the public cloud, which is fantastic. I mean, look, I think the timing was right. I think Pfizer is in a little bit of a unique position coming off of COVID. We are incredibly motivated to keep the pace up, I mean across all lines of business. So, you know what we found is a really willing leadership team, executive leadership team, digital leadership team to endorse a change of this magnitude. >> Well, it's a great success story. It's beyond impressive. So congratulations to both you on that front and certainly you wish you continued success down the road as well. >> Thank you. >> Thank you gentlemen. >> Thank you. >> Good job. >> Pfizer, and boy, you talk about a job well done. Just spectacular. All right, you are watching our coverage here on theCUBE, we're at the AWS re:Invent 22 show. This is Executive Summit sponsored by Accenture and you're watching theCUBE the leader in high tech coverage.