>>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.

(upbeat music) >> From around the globe, it's theCUBE with digital coverage of Postgres Vision 2021 brought to you by EDB. >> Well, hi everybody John Walls here on theCUBE and we're now welcoming Jeremy Wilmot who is the chief product officer at ACI Worldwide part of the Postgres movement, you might say or certainly benefiting from the great value that Postgres is providing a number of enterprises across the globe. Jeremy good to see you today and first off, congratulations you are the first guest I've talked to maybe in a year and a half in their office. So good for you. >> Thanks (chuckles) John that's very kind of you John and great to see you and thanks for having me here. Yeah, it's great to be in the office, it really is. I'm here in Miami in South Florida and getting some sort of normalcy back is great for all of us and I'm certainly enjoying it. So thank you before (indistinct) has been. >> I'm sure you are, yeah, congratulations on that front. First off, let's talk about ACI Worldwide for the folks in our audience who aren't familiar with the payments, your role in terms of that payment ecosystem. Tell us a little bit about ACI Worldwide. >> Sure, well, primarily we're a software company. That's ACI, we started 1975 in Omaha, Nebraska built the first debit card system and ATM system for first National Bank of Omaha and over the last 45 years, we've globalized ourselves, we have, we are delivering mission-critical real-time payment systems across the world to banks to merchants to billers, we help them meet the payment needs of their consumers and their corporates. So we process, manage digital payments, we power omni-commerce and e-commerce payments, we present and process bill payments, we manage fraud, we manage the risk all within that and as I said on a global basis 13 of the G20 countries with a leading DDA account or current account payment processing software in those countries and have been for many years. >> So, as the CPO then quite obviously in the financial space your plate is quite full these days in terms of providing for your client base. How would you characterize maybe the evolution in terms of product development that you've been through in the financial world here over the past say, three to five years, where were you back then to where you are now and what role has Postgres played in that journey? >> Sure, yeah. So, specific to the Postgres part of the ecosystem, previously five-plus years ago our previous database solution was complex, it was expensive, it was hard to change and maintain and we leveraged multiple pieces of software from multiple vendors as a result of that. So at that time we looked for an alternative that was simpler and better and we went through a very comprehensive due diligence process, we explored both open source and license models of database to support our solution and when we looked at all of the options we determined that 2ndQuadrant Postgres was the one that provided the most comprehensive solution we were looking for. It had the right mix of capabilities and performance at the right total cost of ownership that we were looking for. And in the payments world as you can imagine, you've got to to be 24/7 365. And we also required a lower cost of ownership than we had before. But we also wanted a greater flexibility and time to market that we could pass on to our customers. And then the last thing I'd say that we were looking for was a multi-deployment capability. And what I mean by that is that we would be able to use this new platform, Postgres platform in our own data centers in our own private cloud, but we could also deploy it in the public cloud, whether we would run it or whether our customers would run it. We wanted that ability to mix and match between these different deployment options. >> So you've talked about a lot of key elements here attributes in terms of availability, accessibility reliability, security obviously. Walk us through those in terms of why you think 2ndQuadrant was addressing your needs in those particular areas or any others for that matter but what it was that checked the box specifically about what Postgres was offering you as opposed to what these other possible solutions and services were that you were looking at. >> Yeah, I think, we're very focused on being able to identify what our customers need and when they're offering services to consumers and to their corporates what is it that they require that's going to enable them to win and compete. And payments industry has a lot of cost pressures within it. It has regulation, it has consumer convenience and the whole movement of digitalization that puts a lot of downward pressure on the cost space. And those who are going to win in the payment space need to be able to address that. So, that is relevant for our banks, for our merchants, for the billers. They all come under very similar regulatory pressure and market pressure and as a result, the ability to reduce dramatically in a very significant way, the total cost of ownership upon which the payment software was going to be operating that was one of the key elements that was very important to us as we made that decision. The second one I think was to enable us to be able to do what we are good at and what our customers expect us to do. And that in turn enables them to focus on their core competencies. We're a software company, we own our own IP we manage our own software for the needs of the 24/7 365 payment requirements and therefore the merchant or the biller or the bank can really focus in on the digital experience for their customers, focusing on their core competencies and what they need to do to win. That was a second key factor for us. I think the third one for us was as well speed to market. Speed to market for ourselves and being competitive to the alternative to ACI, but also more importantly a speed to market for our customers. And there are, the payment world is highly regulated requires significant certification in order to launch new services that's often the long pole in the tent. So we want to be able to get to that point as quickly as possible. And being able to have a public cloud deployment open systems capabilities that would really allow us to pass on that speed to market to those customers. So for example, an acquirer, a payment acquirer moving into a new geographical country they want to compete in they can (indistinct) on their competitors by launching minimum viable products in six to nine months that is five years ago, that could have been a 24 to 30 months endeavor for them to take on. So I, those were important considerations for us as we were choosing a longterm partner for the Postgres world and the public cloud world. >> Obviously, so you've talked a lot about your relationship with your clients and I know you have a really keen awareness of the need to ensure that trust, to ensure that reliability to ensure the collaboration. How about your relationship on the other side with EDB and in terms of all those elements so how has that evolved over a period of time and what kind of service and what kind of value do you think are you deriving from that relationship now? >> So with EDB, first of all, our journey started with 2ndQuadrant and now EDB. And we were specifically looking at the, one area was at the Bi-Directional Replication BDR that we were wanting to support with our solutions particularly in the public cloud. And that was going to enable us to replace multiple pieces of software from multiple vendors. And so we were to create that solution that was right for ACI, it was right for our customers from a functionality and agility and a cost perspective. So technologically with the non-functional requirements and the reliability, availability, serviceability aspects that we were looking for that was in partnership with 2ndQuadrant and EDB, that was a key element. I think the second piece of it is we worked really well with 2ndQuadrant EDB in terms of partnering to meet the needs of the market. It's great to have the right technology in place but then you need your partners really to be able to work with you tactically real-time in order to win in the market and make it work. And I found that they'd been a great partner for us to be able to do that and to be able to react quickly, do the right thing and really enable us to be a great partner to our customers as we deliver real-time payments, as we deliver the acquiring capabilities, as we deliver a modernization for the big banks that we work with as well. >> Now, before I let you go, I'm going to give you a two-part question here. That's always one way to squeeze a little more info (laughing) to the guest. First off advice. You've been through this transformation obviously you're very happy with all that has transpired, so your advice to others who are considering this journey. And then secondly, what can they and you do you think expect in terms of future challenges, opportunities how we might want to frame that with Postgres? Like, where are we going from here, basically? So, two parts, advice and then where do you think this is headed? >> So advice, I certainly learnings from us versus advice is number one, be very thorough in the due diligence that you do and be very clear on what you want and what are your goals that you're looking for. So from an AGI perspective, we were clear that total cost of ownership in terms of the stack that we were going to be providing to our customers. That was very important, number one number two, nonfunctional requirements. So I've talked about the mission criticality of payments 24/7 365. That was a key second piece. And then the third one, ease of deployment. I talked about that, multi-cloud deployment that we were looking for. So we were clear what we wanted and we we took our time from a due diligence point of view. It's a multi-year decision being made so it's not something specifically I think we want to rush into. In terms of looking forward and where do we go from here? Performance is critical so further up performance enhancements, ability for rapid failover availability, near 100% availability that we're looking for five-nines and above, working together with Postgres in order to make those failovers more seamless because they will happen, particularly in the real-time payments world, where we're now seeing billions of transactions happening in a week and soon that will be in a day, they will need to be able to deal with. And for all of this to happen in a public cloud environment, we, I think all understand a lot of the benefits of public cloud and we need to be able to provide this failover availability capability in the public cloud but also in a hybrid cloud environments we're in a multi-cloud environment, so we need to keep working that and make that happen that will make Postgres a payment-grade infrastructure that could power the world's real-time payments and we would love to be able to do that into the future. >> Well, Jeremy thanks for the insights, we appreciate that and once again, congratulations on getting back in that office. I know it's probably a pretty welcomed addition to your regimen now. >> Yeah, John, thank you very much and thanks to everyone who's dialed in for this and John I look forward to welcoming you in the office soon. >> Very good sir, I look forward to that as well. I'll take you up on that in Miami for sure. John Walls here on theCUBE talking with Jeremy Wilmot is the chief product officer at ACI Worldwide. part of our Postgres Vision 2021 coverage. (upbeat music)

(upbeat music) >> From around the globe, it's theCUBE with digital coverage of Postgres Vision 2021 brought to you by EDB. >> Well, hi everybody John Walls here on theCUBE and we're now welcoming Jeremy Wilmot who is the chief product officer at ACI Worldwide part of the Postgres movement, you might say or certainly benefiting from the great value that Postgres is providing a number of enterprises across the globe. Jeremy good to see you today and first off, congratulations you are the first guest I've talked to maybe in a year and a half in their office. So good for you. >> Thanks (chuckles) John that's very kind of you John and great to see you and thanks for having me here. Yeah, it's great to be in the office, it really is. I'm here in Miami in South Florida and getting some sort of normalcy back is great for all of us and I'm certainly enjoying it. So thank you before (indistinct) has been. >> I'm sure you are, yeah, congratulations on that front. First off, let's talk about ACI Worldwide for the folks in our audience who aren't familiar with the payments, your role in terms of that payment ecosystem. Tell us a little bit about ACI Worldwide. >> Sure, well, primarily we're a software company. That's ACI, we started 1975 in Omaha, Nebraska built the first debit card system and ATM system for first National Bank of Omaha and over the last 45 years, we've globalized ourselves, we have, we are delivering mission-critical real-time payment systems across the world to banks to merchants to billers, we help them meet the payment needs of their consumers and their corporates. So we process, manage digital payments, we power omni-commerce and e-commerce payments, we present and process bill payments, we manage fraud, we manage the risk all within that and as I said on a global basis 13 of the G20 countries with a leading DDA account or current account payment processing software in those countries and have been for many years. >> So, as the CPO then quite obviously in the financial space your plate is quite full these days in terms of providing for your client base. How would you characterize maybe the evolution in terms of product development that you've been through in the financial world here over the past say, three to five years, where were you back then to where you are now and what role has Postgres played in that journey? >> Sure, yeah. So, specific to the Postgres part of the ecosystem, previously five-plus years ago our previous database solution was complex, it was expensive, it was hard to change and maintain and we leveraged multiple pieces of software from multiple vendors as a result of that. So at that time we looked for an alternative that was simpler and better and we went through a very comprehensive due diligence process, we explored both open source and license models of database to support our solution and when we looked at all of the options we determined that 2ndQuadrant Postgres was the one that provided the most comprehensive solution we were looking for. It had the right mix of capabilities and performance at the right total cost of ownership that we were looking for. And in the payments world as you can imagine, you've got to to be 24/7 365. And we also required a lower cost of ownership than we had before. But we also wanted a greater flexibility and time to market that we could pass on to our customers. And then the last thing I'd say that we were looking for was a multi-deployment capability. And what I mean by that is that we would be able to use this new platform, Postgres platform in our own data centers in our own private cloud, but we could also deploy it in the public cloud, whether we would run it or whether our customers would run it. We wanted that ability to mix and match between these different deployment options. >> So you've talked about a lot of key elements here attributes in terms of availability, accessibility reliability, security obviously. Walk us through those in terms of why you think 2ndQuadrant was addressing your needs in those particular areas or any others for that matter but what it was that checked the box specifically about what Postgres was offering you as opposed to what these other possible solutions and services were that you were looking at. >> Yeah, I think, we're very focused on being able to identify what our customers need and when they're offering services to consumers and to their corporates what is it that they require that's going to enable them to win and compete. And payments industry has a lot of cost pressures within it. It has regulation, it has consumer convenience and the whole movement of digitalization that puts a lot of downward pressure on the cost space. And those who are going to win in the payment space need to be able to address that. So, that is relevant for our banks, for our merchants, for the billers. They all come under very similar regulatory pressure and market pressure and as a result, the ability to reduce dramatically in a very significant way, the total cost of ownership upon which the payment software was going to be operating that was one of the key elements that was very important to us as we made that decision. The second one I think was to enable us to be able to do what we are good at and what our customers expect us to do. And that in turn enables them to focus on their core competencies. We're a software company, we own our own IP we manage our own software for the needs of the 24/7 365 payment requirements and therefore the merchant or the biller or the bank can really focus in on the digital experience for their customers, focusing on their core competencies and what they need to do to win. That was a second key factor for us. I think the third one for us was as well speed to market. Speed to market for ourselves and being competitive to the alternative to ACI, but also more importantly a speed to market for our customers. And there are, the payment world is highly regulated requires significant certification in order to launch new services that's often the long pole in the tent. So we want to be able to get to that point as quickly as possible. And being able to have a public cloud deployment open systems capabilities that would really allow us to pass on that speed to market to those customers. So for example, an acquirer, a payment acquirer moving into a new geographical country they want to compete in they can (indistinct) on their competitors by launching minimum viable products in six to nine months that is five years ago, that could have been a 24 to 30 months endeavor for them to take on. So I, those were important considerations for us as we were choosing a longterm partner for the Postgres world and the public cloud world. >> Obviously, so you've talked a lot about your relationship with your clients and I know you have a really keen awareness of the need to ensure that trust, to ensure that reliability to ensure the collaboration. How about your relationship on the other side with EDB and in terms of all those elements so how has that evolved over a period of time and what kind of service and what kind of value do you think are you deriving from that relationship now? >> So with EDB, first of all, our journey started with 2ndQuadrant and now EDB. And we were specifically looking at the, one area was at the Bi-Directional Replication BDR that we were wanting to support with our solutions particularly in the public cloud. And that was going to enable us to replace multiple pieces of software from multiple vendors. And so we were to create that solution that was right for ACI, it was right for our customers from a functionality and agility and a cost perspective. So technologically with the non-functional requirements and the reliability, availability, serviceability aspects that we were looking for that was in partnership with 2ndQuadrant and EDB, that was a key element. I think the second piece of it is we worked really well with 2ndQuadrant EDB in terms of partnering to meet the needs of the market. It's great to have the right technology in place but then you need your partners really to be able to work with you tactically real-time in order to win in the market and make it work. And I found that they'd been a great partner for us to be able to do that and to be able to react quickly, do the right thing and really enable us to be a great partner to our customers as we deliver real-time payments, as we deliver the acquiring capabilities, as we deliver a modernization for the big banks that we work with as well. >> Now, before I let you go, I'm going to give you a two-part question here. That's always one way to squeeze a little more info (laughing) to the guest. First off advice. You've been through this transformation obviously you're very happy with all that has transpired, so your advice to others who are considering this journey. And then secondly, what can they and you do you think expect in terms of future challenges, opportunities how we might want to frame that with Postgres? Like, where are we going from here, basically? So, two parts, advice and then where do you think this is headed? >> So advice, I certainly learnings from us versus advice is number one, be very thorough in the due diligence that you do and be very clear on what you want and what are your goals that you're looking for. So from an AGI perspective, we were clear that total cost of ownership in terms of the stack that we were going to be providing to our customers. That was very important, number one number two, nonfunctional requirements. So I've talked about the mission criticality of payments 24/7 365. That was a key second piece. And then the third one, ease of deployment. I talked about that, multi-cloud deployment that we were looking for. So we were clear what we wanted and we we took our time from a due diligence point of view. It's a multi-year decision being made so it's not something specifically I think we want to rush into. In terms of looking forward and where do we go from here? Performance is critical so further up performance enhancements, ability for rapid failover availability, near 100% availability that we're looking for five-nines and above, working together with Postgres in order to make those failovers more seamless because they will happen, particularly in the real-time payments world, where we're now seeing billions of transactions happening in a week and soon that will be in a day, they will need to be able to deal with. And for all of this to happen in a public cloud environment, we, I think all understand a lot of the benefits of public cloud and we need to be able to provide this failover availability capability in the public cloud but also in a hybrid cloud environments we're in a multi-cloud environment, so we need to keep working that and make that happen that will make Postgres a payment-grade infrastructure that could power the world's real-time payments and we would love to be able to do that into the future. >> Well, Jeremy thanks for the insights, we appreciate that and once again, congratulations on getting back in that office. I know it's probably a pretty welcomed addition to your regimen now. >> Yeah, John, thank you very much and thanks to everyone who's dialed in for this and John I look forward to welcoming you in the office soon. >> Very good sir, I look forward to that as well. I'll take you up on that in Miami for sure. John Walls here on theCUBE talking with Jeremy Wilmot is the chief product officer at ACI Worldwide. part of our Postgres Vision 2021 coverage. (upbeat music)

>> Male Voiceover: Live from Atlanta, Georgia, it's theCUBE, covering Citrix Synergy Atlanta 2019. Brought to you by Citrix. >> Hi, welcome back to theCUBE. Lisa Martin with Keith Townsend and we're coming to you live from the show floor of Citrix Synergy 2019 in Atlanta, Georgia. And we're welcoming to theCUBE for the first time Adam Jones, the chief revenue officer of the Miami Marlins. Adam, it's great to have you on theCUBE. >> Pleasure to join you both today. >> So, baseball fans, White Sox, San Francisco Giants, Miami Marlins. Always cool to talk sports and technology when we can bring those two things together. I think the San Francisco Giants and the Miami Marlins might have something in common right now, but regardless of the standings, everybody wants to go to a game. You have to deliver, as chief revenue officer, a great a fan experience. You got to make sure all the vendors are there to deliver what those fans want, regardless of the standings. People still want to go to the games. Talk to us a little bit about your role as the CRO of the Miami Marlins, how long you've been doing it, and then we'll get into what you're doing with Citrix. >> Sure. So, joined the Marlins 18 months ago as part of new ownership and the new leadership team brought in to reset the standard for what the Miami Marlins organization could be. We want to be a world class sport entertainment enterprise. That means we're going to evolve beyond a traditional baseball team and ballpark. 26 years into the history of the franchise, eight years into the operating rights of a ballpark, and there's a lot of work to be done around those two assets but as we take the organization forward, we want to continue to broaden that enterprise to focus on more sport and entertainment offerings. >> So, chief revenue officer. We don't get many chief revenue officers at a technology conference. Help make the connection. You're a busy person. What made you take time out of your schedule to come to Citrix Synergy? >> Well, I think it's indicative of the culture we're building within our organization that we're putting data at the very center of our culture. We're going to make informed and timely decisions and we need our technology to enable that culture. And so, when it came to where we were going to align our IT group and it's a group that has built out a very robust, on-prem infrastructure over the past seven years following the opening of Marlins Park, the alignment under strategy, which was my initial title coming in, and now chief revenue officer as I took on more responsibility for the business side of the organization, was a strategic decision to make sure that the infrastructure was meeting the requirements of the organization as we rapidly evolve what our priorities are and what we need in order to deliver on their very aggressive and lofty expectations for their organization. >> So this morning during the keynote, we heard a lot about the digital workplace, the employee experience being really critical for any type of organization's digital transformation, and I just thought it was a really interesting viewpoint because we go to a lot of tech shows here at theCUBE, all over the world, and we don't often talk about employee experience or even culture, as a leading edge indicator of how successful a digital transformation is going to be, but employee experience is really critical to any business because whether those employees are interacting with seven to 10 apps a day based on their job, or they're interacting with your other users, in your case, Marlins fans, making sure those employees are productive, have what they need, in a personalized way, is critical. Talk to us about what the employee experience means for the Marlins, and also, as an indicator on the revenue side. >> Absolutely, so we have an evolving workforce. It's very young across a very diverse enterprise of activities. What we've been able to do in partnership with Citrix since day one of the ballpark, where we went from an organization of roughly 100-150 employees around the team to 300 plus across the team and the ballpark, is build out an infrastructure that was very light in terms of hardware, focused very much on the digital workspace keeps us very nimble, allows us to deploy capital in areas that we see tremendous value back in terms of application and utility. So, as we continue to make our workforce more mobile, I ask them to deliver and work at a higher rate of speed. We need to arm them with the tools that allow them to perform those roles in the office, out of the office, engage beyond more just than a 81 day transactional relationship across Marlins baseball, but how across 12 months out of the year, creating that 365 day touchpoint. They still have tools and access in order to create those memories, those engagements that we want with the market. >> So, talking about customer experience, Marlin baseball is more than just the 300 employees. It is your partners, it's all of your contractors. When I go to a ballpark, I don't see Mark the hot dog vendor I see Mark, the guy that works for the Marlins. My user experience, my customer experience needs to be excellent across that. As CRO, that's part of your responsibility, assuring that the whole Marlin family is presented as one unity. Talk to us about from not just a user experience perspective but also, security expectations of how you need to make that real for your customers. >> Sure, on the experience side, what we are doing is resetting the standard, not only for Marlins and for South Florida, but the industry as a whole. We've brought on a lot of great talent to the organization from across the industry that knows what's worked, what hasn't across our peers. We're applying that. We're challenging conventional practice trying to get out in front of the curve as to what is going to be the future of a game day experience, what is a sport entertainment enterprise more holistically. And so, as a result, we have to arm our employees with those tools that will allow them to engage consistently across all the touchpoints with our fans, with our partners. Try not to centralize data to the point where only a select few have and feel informed and empowered to make decisions and take action, but disseminate that information and empower everyone to deliver consistently across all of those touchpoints. On the security side, being a public interest entity, we're vulnerable. We're a target. There's plenty of precedent around the type of activity that these types of organizations can be prone to try to address, and so, security is a number one priority of ours to make sure that the IP we're creating maintains and stays ours, as well as the information we are collecting around our customers, around our players, stays within that secure environment as well. >> So if I think about going to a baseball game, which I love, there are so many sellable moments there. Whether I'm in the stands and I want to go buy food and beverage, or I want a new hat, or some sort of merchandise for my nephew or something. You have, as CRO, you've got all these different sellable moments, not just in the ballpark, in the physical experience, but even online. So having this kind of cohesive opportunity to sell not just tickets, but food and beverage, merchandise, in person, on mobile, on a tablet, on a desktop, it's got to be a critical part of your strategy Talk about the alignment with yourself and you said a lot of your IT guys have FOMO cause you're here, but I imagine that those experiences are essential that you have the right foundation and technological foundation to deliver sellable moments that deliver. >> That's right. So the ecosystem of a sport is a fairly diverse one from the ticketing transaction to all of the ballpark touchpoints. What we're trying to create is that 12 month relationship with a fan, so that goes into creating a lot of content and how we distribute that content, in order to continue to earn that engagement well beyond 81 plus dates of baseball. And the technology behind there, in terms of our storage and our accessibility, is what allows us to begin to personalize and tailor not only those core, traditional transactions and touchpoints of sport, but how we've begun to transition into more of that broader entertainment enterprise in making sure that we can deliver those as personalized and tailored as we can. >> So there was another Chicago team that showed the age of baseball. It was over 100 years before they won a-- >> Another Chicago team-- >> Yeah, another Chicago team that won a championship. So baseball has a lot of tradition. You're in a unique opportunity that you're coming into a new ownership, but still, baseball has traditions that are hard to compete against. So let's talk about what are some of the cultural changes and opportunities that you see that baseball needs to engage in where technology can help. >> Why I think an interesting thought around baseball and where it's been scrutinized as whether we pace a play or number of games, of not keeping up with the times, not being as snackable, short-form consumption as other sporting content. As everything tracks that way, baseball starts to differentiate itself in terms of the ability to create a very distinct and differentiated experience to a millennial, to a family, to an older consumer who has grown up with the traditions of baseball. And so while baseball needs to continue to innovate and modernize, there's actually this interesting equilibrium as to how much it continues to challenge those traditions that differentiate it from many of other points of contact and where it should continue to preserve those elements to hold what has been generational-type engagement. >> You know a great example of that is mlb.com and being able to watch a game anywhere. Baseball does an amazing job of embracing digital transformation, at least in baseball. One of the things that we talked about, or that David talked about onstage today, is the seven trillion dollar opportunity. That's big, even in baseball numbers. There's no bigger sporting numbers than baseball, but seven trillion dollars is opportunity. What are you excited about coming out of this show when you look at some of the potential game efficiencies from some of the automation announcements that were made today? >> For our organization, while there has been significant investment in infrastructure, great collaboration with Citrix up until this point. The exciting transformation for us is our migration into more of a hybrid cloud environment, which is going to allow us to onboard a number of new applications, tools, for our sales team, our service team, our game presentation groups, to continue to innovate and challenge how they've gone to market in the past. And having Citrix as a partner that has that environment for us to step into, one, gives us a ton of assurance in taking that next step and having someone that continues to bring us new tools within that environment, as well. So our ability to collaborate across the organization, I'd say we've only just skimmed the surface as to the true capability and power of a lot of the tools we've had in place, and very excited about unlocking the true power and potential of that environment moving forward. >> So this is your second season with the Marlins. You spent 15 years at PWC and before we went live, I thought, wow, that must have been a pretty big change going from PWC to major league baseball. But you actually have quite a history in sports. Tell us a little about that and maybe some of the similarities between major league baseball as an industry to other industries that kind of surprised you. >> Sure. Organizations couldn't be different, more different, in terms of profile and in set-up. What I did day-to-day, advising across sport and entertainment leading the sports practice at PWC positioned me for this incredible opportunity or challenge that is the Miami Marlins and what we're building in this aggressive vision that we've set as to how we're going to reset the standard and become world class as an enterprise. PWC and the history with the firm and professional services gave me a unique perspective as to how to take on many of the challenges that we have. Had the opportunity working across sport to really understand what works, what doesn't, so that we can avoid some of those missteps that others who have taken on this roadmap ahead of us have encountered. The breadth of infrastructure that a firm of PWC's size, also gives me a little more of a lens as to what the power and scale of a large organization can deliver in more of a small, mid-size business form, and not accept size or employee base as a constraint as to the types of tools and sophistication of our technology that we can deploy within a sports organization. >> Well, Adam, thank you so much for joining Keith and me on theCUBE this afternoon, talking about how you are helping to make big positive impacts for the Miami Marlins. We appreciate your time. >> I enjoyed it. Thank you. >> Go MLB. All right, for Keith Townsend, I'm Lisa Martin. You're watching theCUBE, live from our first day of coverage of Citrix Synergy 2019. Thanks for watching. (upbeat music)

>> Narrator: Live from Las Vegas. It's the CUBE covering ServiceNow Knowledge 2018. Brought to you by ServiceNow. >> Welcome back everyone to the CUBE's live coverage of ServiceNow Knowledge 18 in Las Vegas Nevada. I'm your host Rebecca Knight. We've got two guests for this panel. We have Katie Benedict who is director advisory people in change at KPMG and Michelle Esposito who is the AVP technology planning for JM Family Enterprises. Welcome Katie and Michelle. >> Thank you for having us. >> So I want to start out with you Michelle, explain to our viewers what JM Family Enterprises is. >> Sure, JM Family's, we're a privately held company located in south Florida. We have about 4,200 associates across the country and I describe us as a diversified automotive company. So we started 50 years ago, it's actually our 50th anniversary. Distributing Toyotas in the U.S. We were the first distributor and we still distribute to the five south eastern states but since then we've grown and expanded into other sectors of the automotive industry. Including auto finance and warranty and insurance products. >> Okay so diversified portfolio of services. >> Yes. >> So recently you had a situation, an implementation situation. Can you tell our viewers a little bit about it and then I want you to chime in Katie with how you worked on it too. >> Sure. So we were an existing ServiceNow customer. We implemented the product back in 2011 and at the time we really just tried to make it look like our old product. We wanted to minimize the disruption to the organization so we said let's just make it look and behave like the old product did. Seemed like a good idea at the time but with that and with the change that happened over time it became very complex to use and it really just wasn't meeting our needs. So, after much consultation with a lot of experts in the field we decided to re-implement ServiceNow. We believed in the platform, we believed in its capabilities and what it could do for us but we needed to start over. So with that comes a lot of change for our organization. People re used to doing things a certain way, they're used to the processes that we already had in place. So trying to get them on board and understand the why to what we were doing was really important. >> And Katie that's where you fit in. So tell us a little bit about KPMG's approach to making this easier, because as Michelle said. We are human nature, we're just resistant to change and sort of we like it the old way. This is hard. So how, what, can you tell us a little bit about your approach. >> Exactly. We were thrilled that JM Family chose KPMG as their implementation partner and really some of things we brought specifically to the table for this re-implementation. Was some of our accelerators. Our process packs to really optimize the new processes that JM Family was using but then also our organizational change management and learning and development capabilities. We specialize in IT transformation from a people perspective and group of a specialized in ServiceNow. We've done, well over 50 implementations of ServiceNow. So we wanted to look from that people perspective, how do we get the right level of buy in. How do we make sure that people understand why we're doing the change. Get that early, quick adoption. A continuous feedback loop we implement a change agent network. Which I've found was one of the most effective things we could have done especially at JM Family given the nature of their organization and given some of the cultural considerations there and it was a tremendous success there I feel. I mean the people there, the associates there were so involved in the initiative and really partnered with our team. As a single team, it wasn't JM Family and KPMG it was one implementation team working together in tandem to make this change happen. >> So what did you learn in the sense of what were people's, what were the sticking points? And then how did you overcome them? >> Yeah. Sure I can take that. As much as people were supportive of the re-implementation and really knew we needed to do it we found that they were still very much embedded with the way we did it today. So even going into this knowing what a huge change management effort it was I was still surprised at how much effort we had to put into it. So it took a lot of communication, a lot of different methods of communication and engagement to get people to really understand what we were doing and why we were doing it. Repetition really explaining it, the change agent network was huge for us and what we did there was. We pulled in some of our bigger supporters and some of our detractors and they were able to kind of permeate the organization in the different departments within IT to really help sell what we were doing. To bring back questions and concerns. So that was really key. >> What was that like bringing in the people who were really butting heads? I mean and how do you navigate between those two factions? >> Honestly I think it was great because I'd rather get that feedback while we're going through the process than hear about it later and hear the implementation not be successful. So in some cases when people brought that feedback that maybe wasn't so positive it was just a matter of more communication, more training but in other times it was you know we really scratched our head and said maybe we really need the rethink about this. Maybe they've got something here and we may need to tweak our approach or do something a little differently. But it was as Katie mentioned, the engagement level was phenomenal. So the positive and the negative we really had a very engaged team. >> So coming out of this Katie, what would you say are sort of the best practices for other leaders that are doing implementation, re-implementations and maybe dealing with some resistance? >> I would say definitely whether it's the implementation or a re-implementation. Don't forget about your people. The technology, especially ServiceNow is fabulous and your processes are generally are standard. You can align to idle processes but getting the adoption is really key and so remembering that this is a transformation. It's not just an implementation of the technology. Paying attention to the people, making sure that they're on board. They know what you're doing, why you're doing it and really what's in it for them is vital to making this a successful project. >> As you're looking at the ServiceNow platform and what you do for JM Family Enterprises what do you see looking ahead as sort of ways you can augment and enhance? >> Oh they have a lot of ideas going forward right now which is very exciting. >> It is, you know we focused in, we're in a second phase implementation. Our first phase really focused on the core ITSM functions and now we're dipping our toe into some other areas. The PPM suite, vendor management, performance analytics. So we're really continuing to mature our use of the product and even looking beyond that. You know we have interest in some of the security operations and even further than that into some of the financial management capabilities. So we definitely plan to continue invest in the platform and see what it can do for us. >> You're evolving just as ServiceNow is evolving too. >> Yes we are. >> Well Michelle and Katie thanks so much for coming on the CUBE. It was great having you. >> Thank you so much. >> I'm Rebecca Knight, we will have much more of the CUBE's live coverage of ServiceNow Knowledge 18. Hashtag no 18 just after this.

>> Announcer: Live from the Washington D.C. It's the CUBE covering AWS Public Sector Summit 2017. Brought to you be Amazon Web Services and it's partner Ecosystem. >> Welcome back here on the CUBE as we continue our coverage of the AWS Public Sector Summit 2017. Along with John Furrier, I'm John Walls we're in the Walter E. Washington Convention Center. For the sixth show, of almost 10,000 attending. somewhere in that ball park. It's come along way in a very short period of time. AWS has a lot to feel good about. >> It's a good reinvent for Public Sector. It's huge. >> And not just to think about government. We think about education as well. We had a couple of segments about that. We are going to talk about government with our next guest. If we get a name wrong on this segment shame on us, John Stephenson with John Walls and John Furrier. John's a senior manage at Public Policy at AWS. John nice to have you with us we appreciate that. >> Thank you for having me. >> Thank you for your time. So your focus primarily state and local governments. What exactly as the conduit do you want to bring to their table from of AWS? >> Well I'm Senior Manager, of Public Policy for Amazon Web Services in the Eastern United States. I handle state and local government relations in the Eastern U.S. from Texas to Main and then South Florida. I help our business and also our partners in government to understand how public policy can enable cloud and modern technologies. It's a very exciting place to be because there's a lot going on in state and local government when it comes to IT modernization and cloud right now. >> I think about government too. There's that big umbrella we can put on (mumbles). It's public service. But federal government has a place and state and local. I think much more responsive, much more grass roots. So those applications are much more immediate. I would think. Does that come into play with you? That you need to be a little more nimble. Or you're helping your clients to be a litter more nimble or more agile? >> Absolutely, if you look at what state and local governments are doing. Essential services from delivering health care to taking out the trash, providing public safety, providing education it's handled at the state and local government. If you look at the number of times you touch government. It is state and local. Think about renewing a driver license. Think about paying a parking ticket. Think about getting a zoning permit for remodeling of your house. You're dealing with state and local government. The demands on state and local government are also higher. They're holding more data on citizens than the Federal government. They are undergoing massive population changes. It's either positive or negative. State and local governments which have budget constraints. Need to be more nimble, more innovative. They are natural early adopters and first movers of technology. If you look at some of the more exciting things about technology that are happening in the government space. I think it's happening at state and local government in the U.S. >> Smart cities by the way is the hottest trend. Intel one of the key sponsors of this show. We had two folks on here. AI is going to be a real nice gateway for some of these innovations on their side. They have 5G opportunities. They have transformation. Lot of technology going on under the covers, under the hood if you will. One of them is smart cities and that is something that is just mind blowing. Just from a technology stand point but even more mind blowing from a policy perspective. Who sets the rules? What side does the car run on? What digital services are the citizens going to get? Who pays for them? What does the government do? What does the private sector do? These are issues that need to be grappled with. Your thoughts on how you guys look at that? And how are your constituents engaging with that and thinking about it? >> I'm glad you mentioned smart cities because there's a lot of activity going on in that space. If you look at the internet of things technologies alone. One of the enablers of smart cities. As many as 53% of state and local government according to NASCIO are looking at these technologies or deploying them. It's great to see that because that will enable a lot of potential from smarter government services, better government services, improving service delivery and improving constituent fulfillment. Which resonates with us, as part of Amazon. We're all about our customer fulfillment and delighting our customer. >> Lower prices and ship things faster that's Bezos' ethos. That's Amazon's culture. >> Exactly. >> And you could deliver services any digital service. >> Everything we do starts with the customer and we work backwards. In the conversations I've had with policy makers in the state and local governments. They see smart cities as a way to do that. Everything from improving transportation in places like Columbus, Ohio. To improving connectivity and engagement with the internet in places Kansas City, Missouri. And new ways of delivering services in places like New York and Los Angeles. It's very exciting stuff. Policy makers are coming to us and others in the industry. What are the policies? What are the best practices that can enable these technologies? We've been working with them. Providing information on what we're seeing around the world. How open data can be made (mumbles). How security and compliance can be built into applications. And we're happy to provide that because we know from working in the cloud ourselves. The potential that's there for state and local government. >> You want to foster innovation but at the same time you don't want to create this restrictive environment. Or have legacy be the baggage that holds things back. In fact you look at some of the best smart cities implementation. It's Singapore. It's Dubai. It's areas all over the world. In some cases it didn't have real strong infrastructure. So now come back to your role. As you look at the U.S. which has great infrastructure. Except for broadband connectivity, we'd be faster. They have some pre-existing conditions. They're under pressure. The cloud is a prefect vehicle for them. Because they can come in with their existing stuff. Get apps and services online quicker. How are you dealing with the challenge of? OK, calm down we're not going to take over the world. No, skynet's not coming. You know terminator reference. That's a concern, privacy. Lot of in policy issues, to be dealt with. How do you handle those? >> I think with any policy issue. I've been in public policy for a while now. It really starts with education. Understanding in really simple layman's terms. What the cloud is. And what it is not. It is a very transformative technology. It is not an end all one size fits all technology. What we've done is help educate policy makers by understanding the potential of cloud. What it can do in terms of cost savings, improved security, and being more agile. And to tell that story, we don't use PowerPoints at Amazon. We're not coming in and giving PowerPoint presentations. >> Good ole flesh pounding, hand shakes, and hit the streets. >> We'll more importantly it's sharing the customer's stories We're talking with them about what's happening at the New York City Department of Transportation. We're talking with them about what's happening at the city of Los Angeles with their emergency operation center. About how cities are using cloud technologies to deliver far superior products and services faster. >> So what is New York doing and what is L.A. doing specifically? >> New York city they have their iRide application to help citizens get from one point to the other much more quickly and safely as part of their Vision Zero campaign. Anyone who's been in New York, and I've been in New York quite a few times. Knows that traffic and be a real pain getting from part of Manhattan to the other. So what iRide does, is it helps people navigate Manhattan and the other boroughs much more quickly and efficiently using all the modes of transportation available to them. The city of New York was able to deploy that much more quickly, to many more people. They're able to update it, keep it secure thanks to cloud technology offered by AWS. The city of Los Angeles. They face cyber attacks everyday. Then there are the huge cost of maintaining that security. But with cloud they're able to build out event management systems and integrate those with their Homeland Security technologies and practices. And to be able to do it for a fraction of the cost using traditional systems, traditional IT, and traditional practices. It's very exciting. Suddenly local government can move at the speed and agility of a startup. Which has made Amazon very innovative. Last year we launched over a thousand new services and features. Local governments are seeing that. They want to be more like us and others in the industry. That are using cloud to deliver new products and services. And be better at their job. >> And the education, I say it probably patience in the educational role. You think about just the civil liberties of the citizens. That's really job one. Because I think most people get spooked. Whoa all this surveillance. The thing about it, just watching Patriots Day with my family. You know the Boston bombing, Boston strong with Mark Wahlberg. These things actually happen all the time. And we take for granted the some of the things we have in the surveillance community for the kinds of data that's out there. The same time that's the balance. Can you bring me value with my liberties. It's the same compliance scheme. Same governance game. This is the public sector. >> Well, that's where I think cloud has a great story to tell With cloud you get the benefits of economies of scale. Of Amazon with security and also with privacy. We have multiple compliance frameworks. Everything from HIPPA, FERPA, CJIS, Criminal Justice Information Systems. We are zealous guardians of security and our customer's privacy. We don't look at data. We don't share data about with out our customer's permission. We have very strong safeguards. That's why if you look a the customer base of Amazon from banks to government agencies, health care companies. Even companies like Netflix and you would think they're a competitor of ours. They're running their IT in AWS. They trust us even though with Amazon video and Amazon prime. You would think they're a competitor. But they've put that level of trust in us and our systems and our practices that they can put their data there. And we're hearing it from customer after customer. That they feel more safer and more secure with their data in the cloud offered by AWS. And we've shared that with government officials. And they take great comfort in those statements. >> You hit on something earlier. When you said that state governments and local governments have more data at their disposal than the federal government has about their consumers. Because of that, how much higher do find their concerns to be, in terms of cyber security, in terms of hack proof secured networks and systems as opposed to what might happen at the federal level. Cause we think federal. We think big. About what happened with the U.S. government's payment systems last year OPM. State and local they've got a lot more data they're protecting >> I've had a great opportunity in my current job to talk with a lot of IT officials and policy makers in the state. And, often times a meeting will start. And they'll say I've read about this. I've heard about this. And we're often able to say that's not an issue with the cloud offered the AWS. Or that's something we've already addressed through our security and compliance frame works. For example, I was in one meeting and a state policy maker asked me, well what do you do about HIPPA compliance. We have HIPPA compliance in AWS. And then he tried to ask questions, well what about this, what about that. And each time our team was able to tell the state policy maker. We meet that. We exceed that. We actually help write the standard for that compliance frame work. What we've been able to show that policy maker and others. The cloud just offers a far superior security posture than what they can do on their own. It's taken some time because the cloud is new. And as we like to say, it's still day one in this field. But we are very confident as word gets out. More and more people will be trusting particularly in state government their data to the cloud. Because of the superiority it offers on so many different levels. >> Well certainly the words getting out. This event here is just as big as it's ever been (mumbles). Use to be a little summit, now it's grown. There's a lot of interest. >> It's very exciting for me. I've been to reinvent now twice. And this is just so delightful to see so many people from government from the U.S. from internationally here to learn about the cloud share their stories. It's really inspirational to see what's possible. >> That's a testament to Teresa Carlson. Who was just years ago knocking on doors. That was before cloud was cloud. Now it's just come a long way. Congratulations to the whole team. >> Thank you. It's really to delightful to see. And I can't wait to see what's in store for next year and after that. >> We still got a little bit here to go John Don't kick us out. John Stephenson, Public Policy at AWS. Thanks for being with us we appreciate that. >> Thank you. >> Thank you. With John Furrier, I'm John Walls and we'll be back with more here on the CUBE from Washington D.C. right after this. (upbeat music)