>>The Cube presents Ignite 22, brought to you by Palo Alto Networks. >>Welcome back to Vegas. Guys. We're happy that you're here. Lisa Martin here covering with Dave Valante, Palo Alto Networks Ignite 22. We're at MGM Grand. This is our first day, Dave of two days of cube coverage. We've been having great conversations with the ecosystem with Palo Alto executives, with partners. One of the things that they have is unit 42. We're gonna be talking with them next about cyber intelligence. And the threat data that they get is >>Incredible. Yeah. They have all the data, they know what's going on, and of course things are changing. The state of play changes. Hold on a second. I got a text here. Oh, my Netflix account was frozen. Should I click on this link? Yeah. What do you think? Have you had a, it's, have you had a little bit more of that this holiday season? Yeah, definitely. >>Unbelievable, right? A lot of smishing going on. >>Yeah, they're very clever. >>Yeah, we're very pleased to welcome back one of our alumni to the queue. Wendy Whitmore is here, the SVP of Unit 42. Welcome back, Wendy. Great to have >>You. Thanks Lisa. So >>Unit 42 created back in 2014. One of the things that I saw that you said in your keynote this morning or today was everything old is still around and it's co, it's way more prolific than ever. What are some of the things that Unit 42 is seeing these days with, with respect to cyber threats as the landscape has changed so much the last two years alone? >>You know, it, it has. So it's really interesting. I've been responding to these breaches for over two decades now, and I can tell you that there are a lot of new and novel techniques. I love that you already highlighted Smishing, right? In the opening gate. Right. Because that is something that a year ago, no one knew what that word was. I mean, we, it's probably gonna be invented this year, right? But that said, so many of the tactics that we have previously seen, when it comes to just general espionage techniques, right? Data act filtration, intellectual property theft, those are going on now more than ever. And you're not hearing about them as much in the news because there are so many other things, right? We're under the landscape of a major war going on between Russia and Ukraine of ransomware attacks, you know, occurring on a weekly basis. And so we keep hearing about those, but ultimately these nations aid actors are using that top cover, if you will, as a great distraction. It's almost like a perfect storm for them to continue conducting so much cyber espionage work that like we may not be feeling that today, but years down the road, they're, the work that they're doing today is gonna have really significant impact. >>Ransomware has become a household word in the last couple of years. I think even my mom knows what it is, to some degree. Yeah. But the threat actors are far more sophisticated than they've ever written. They're very motivated. They're very well funded. I think I've read a stat recently in the last year that there's a ransomware attack once every 11 seconds. And of course we only hear about the big ones. But that is a concern that goes all the way up to the board. >>Yeah. You know, we have a stat in our ransomware threat report that talks about how often victims are posted on leak sites. And I think it's once every seven minutes at this point that a new victim is posted. Meaning a victim has had their data, a victim organization had their data stolen and posted on some leak site in the attempt to be extorted. So that has become so common. One of the shifts that we've seen this year in particular and in recent months, you know, a year ago when I was at Ignite, which was virtual, we talked about quadruple extortion, meaning four different ways that these ransomware actors would go out and try to make money from these attacks in what they're doing now is often going to just one, which is, I don't even wanna bother with encrypting your data now, because that means that in order to get paid, I probably have to decrypt it. Right? That's a lot of work. It's time consuming. It's kind of painstaking. And so what they've really looked to do now is do the extortion where they simply steal the data and then threaten to post it on these leak sites, you know, release it other parts of the web and, and go from there. And so that's really a blending of these techniques of traditional cyber espionage with intellectual property theft. Wow. >>How trustworthy are those guys in terms of, I mean, these are hackers, right? In terms of it's really the, the hacker honor system, isn't it? I mean, if you get compromised like that, you really beholden to criminals. And so, you >>Know, so that's one of the key reasons why having the threat intelligence is so important, right? Understanding which group that you're dealing with and what their likelihood of paying is, what's their modus operandi. It's become even more important now because these groups switch teams more frequently than NFL trades, you know, free agents during the regular season, right? Or players become free agents. And that's because their infrastructure. So the, you know, infrastructure, the servers, the systems that they're using to conduct these attacks from is actually largely being disrupted more from law enforcement, international intelligence agencies working together with public private partnerships. So what they're doing is saying, okay, great. All that infrastructure that I just had now is, is burned, right? It's no longer effective. So then they'll disband a team and then they'll recruit a new team and it's constant like mixing and matching in players. >>All that said, even though that's highly dynamic, one of the other areas that they pride themselves on is customer service. So, and I think it's interesting because, you know, when I said they're not wanting to like do all the decryption? Yeah. Cuz that's like painful techni technical slow work. But on the customer service side, they will create these customer service portals immediately stand one up, say, you know, hey it's, it's like an Amazon, you know, if you've ever had to return a package on Amazon for example, and you need to click through and like explain, you know, Hey, I didn't receive this package. A portal window pops up, you start talking to either a bot or a live agent on the backend. In this case they're hu what appeared to be very much humans who are explaining to you exactly what happened, what they're asking for, super pleasant, getting back within minutes of a response. And they know that in order for them to get paid, they need to have good customer service because otherwise they're not going to, you know, have a business. How, >>So what's the state of play look like from between nation states, criminals and how, how difficult or not so difficult is it for you to identify? Do you have clear signatures? My understanding in with Solar Winds it was a little harder, but maybe help us understand and help our audience understand what the state of play is right now. >>One of the interesting things that I think is occurring, and I highlighted this this morning, is this idea of convergence. And so I'll break it down for one example relates to the type of malware or tools that these attackers use. So traditionally, if we looked at a nation state actor like China or Russia, they were very, very specific and very strategic about the types of victims that they were going to go after when they had zero day. So, you know, new, new malware out there, new vulnerabilities that could be exploited only by them because the rest of the world didn't know about it. They might have one organization that they would target that at, at most, a handful and all very strategic for their objective. They wanted to keep that a secret as long as possible. Now what we're seeing actually is those same attackers going towards one, a much larger supply chain. >>So, so lorenzen is a great example of that. The Hafnia attacks towards Microsoft Exchange server last year. All great examples of that. But what they're also doing is instead of using zero days as much, or you know, because those are expensive to build, they take a lot of time, a lot of funding, a lot of patience and research. What they're doing is using commercially available tools. And so there's a tool that our team identified earlier this year called Brute Rael, C4 or BRC four for short. And that's a tool that we now know that nation state actors are using. But just two weeks ago we invested a ransomware attack where the ransomware actor was using that same piece of tooling. So to your point, yak can get difficult for defenders when you're looking through and saying, well wait, they're all using some of the same tools right now and some of the same approaches when it comes to nation states, that's great for them because they can blend into the noise and it makes it harder to identify as >>Quickly. And, and is that an example of living off the land or is that B BRC four sort of a homegrown hacker tool? Is it, is it a, is it a commercial >>Off the shelf? So it's a tool that was actually, so you can purchase it, I believe it's about 2,500 US dollars for a license. It was actually created by a former Red teamer from a couple well-known companies in the industry who then decided, well hey, I built this tool for work, I'm gonna sell this. Well great for Red teamers that are, you know, legitimately doing good work, but not great now because they're, they built a, a strong tool that has the ability to hide amongst a, a lot of protocols. It can actually hide within Slack and teams to where you can't even see the data is being exfiltrated. And so there's a lot of concern. And then now the reality that it gets into the wrong hands of nation state actors in ransomware actors, one of the really interesting things about that piece of malware is it has a setting where you can change wallpaper. And I don't know if you know offhand, you know what that means, but you know, if that comes to mind, what you would do with it. Well certainly a nation state actor is never gonna do something like that, right? But who likes to do that are ransomware actors who can go in and change the background wallpaper on a desktop that says you've been hacked by XYZ organization and let you know what's going on. So pretty interesting, obviously the developer doing some work there for different parts of the, you know, nefarious community. >>Tremendous amount of sophistication that's gone on the last couple of years alone. I was just reading that Unit 42 is now a founding member of the Cyber Threat Alliance includes now more than 35 organizations. So you guys are getting a very broad picture of today's threat landscape. How can customers actually achieve cyber resilience? Is it achievable and how do you help? >>So I, I think it is achievable. So let me kind of parse out the question, right. So the Cyber Threat Alliance, the J C D C, the Cyber Safety Review Board, which I'm a member of, right? I think one of the really cool things about Palo Alto Networks is just our partnerships. So those are just a handful. We've got partnerships with over 200 organizations. We work closely with the Ukrainian cert, for example, sharing information, incredible information about like what's going on in the war, sharing technical details. We do that with Interpol on a daily basis where, you know, we're sharing information. Just last week the Africa cyber surge operation was announced where millions of nodes were taken down that were part of these larger, you know, system of C2 channels that attackers are using to conduct exploits and attacks throughout the world. So super exciting in that regard and it's something that we're really passionate about at Palo Alto Networks in terms of resilience, a few things, you know, one is visibility, so really having a, an understanding of in a real, as much of real time as possible, right? What's happening. And then it goes into how you, how can we decrease operational impact. So that's everything from network segmentation to wanna add the terms and phrases I like to use a lot is the win is really increasing the time it takes for the attackers to get their work done and decreasing the amount of time it takes for the defenders to get their work done, right? >>Yeah. I I call it increasing the denominator, right? And the ROI equation benefit over or value, right? Equals equals or benefit equals value over cost if you can increase the cost to go go elsewhere, right? Absolutely. And that's the, that's the game. Yeah. You mentioned Ukraine before, what have we learned from Ukraine? I, I remember I was talking to Robert Gates years ago, 2016 I think, and I was asking him, yeah, but don't we have the best cyber technology? Can't we attack? He said, we got the most to lose too. Yeah. And so what have we learned from, from Ukraine? >>Well, I, I think that's part of the key point there, right? Is you know, a great offense essentially can also be for us, you know, deterrent. So in that aspect we have as an, as a company and or excuse me, as a country, as a company as well, but then as partners throughout all parts of the world have really focused on increasing the intelligence sharing and specifically, you know, I mentioned Ukrainian cert. There are so many different agencies and other sorts throughout the world that are doing everything they can to share information to help protect human life there. And so what we've really been concerned with, with is, you know, what cyber warfare elements are going to be used there, not only how does that impact Ukraine, but how does it potentially spread out to other parts of the world critical infrastructure. So you've seen that, you know, I mentioned CS rrb, but cisa, right? >>CISA has done a tremendous job of continuously getting out information and doing everything they can to make sure that we are collaborating at a commercial level. You know, we are sharing information and intelligence more than ever before. So partners like Mania and CrowdStrike, our Intel teams are working together on a daily basis to make sure that we're able to protect not only our clients, but certainly if we've got any information relevant that we can share that as well. And I think if there's any silver lining to an otherwise very awful situation, I think the fact that is has accelerated intelligence sharing is really positive. >>I was gonna ask you about this cause I think, you know, 10 or so years ago, there was a lot of talk about that, but the industry, you know, kind of kept things to themselves, you know, a a actually tried to monetize some of that private data. So that's changing is what I'm hearing from you >>More so than ever more, you know, I've, I mentioned I've been in the field for 20 years. You know, it, it's tough when you have a commercial business that relies on, you know, information to, in order to pay people's salaries, right? I think that has changed quite a lot. We see the benefit of just that continuous sharing. There are, you know, so many more walls broken down between these commercial competitors, but also the work on the public private partnership side has really increased some of those relationships. Made it easier. And you know, I have to give a whole lot of credit and mention sisa, like the fact that during log four J, like they had GitHub repositories, they were using Slack, they were using Twitter. So the government has really started pushing forward with a lot of the newer leadership that's in place to say, Hey, we're gonna use tools and technology that works to share and disseminate information as quickly as we can. Right? That's fantastic. That's helping everybody. >>We knew that every industry, no, nobody's spared of this. But did you notice in the last couple of years, any industries in particular that are more vulnerable? Like I think of healthcare with personal health information or financial services, any industries kind of jump out as being more susceptible than others? >>So I think those two are always gonna be at the forefront, right? Financial services and healthcare. But what's been really top of mind is critical infrastructure, just making sure right? That our water, our power, our fuel, so many other parts of right, the ecosystem that go into making sure that, you know, we're keeping, you know, houses heated during the winter, for example, that people have fresh water. Those are extremely critical. And so that is really a massive area of focus for the industry right now. >>Can I come back to public-private partnerships? My question is relates to regulations because the public policy tends to be behind tech, the technology industry as an understatement. So when you take something like GDPR is the obvious example, but there are many, many others, data sovereignty, you can't move the data. Are are, are, is there tension between your desire as our desire as an industry to share data and government's desire to keep data private and restrict that data sharing? How is that playing out? How do you resolve that? >>Well I think there have been great strides right in each of those areas. So in terms of regulation when it comes to breaches there, you know, has been a tendency in the past to do victim shaming, right? And for organizations to not want to come forward because they're concerned about the monetary funds, right? I think there's been tremendous acceleration. You're seeing that everywhere from the fbi, from cisa, to really working very closely with organizations to, to have a true impact. So one example would be a ransomware attack that occurred. This was for a client of ours within the United States and we had a very close relationship with the FBI at that local field office and made a phone call. This was 7:00 AM Eastern time. And this was an organization that had this breach gone public, would've made worldwide news. There would've been a very big impact because it would've taken a lot of their systems offline. >>Within the 30 minutes that local FBI office was on site said, we just saw this piece of malware last week, we have a decryptor for it from another organization who shared it with us. Here you go. And within 60 minutes, every system was back up and running. Our teams were able to respond and get that disseminated quickly. So efforts like that, I think the government has made a tremendous amount of headway into improving relationships. Is there always gonna be some tension between, you know, competing, you know, organizations? Sure. But I think that we're doing a whole lot to progress it, >>But governments will make exceptions in that case. Especially for something as critical as the example that you just gave and be able to, you know, do a reach around, if you will, on, on onerous regulations that, that ne aren't helpful in that situation, but certainly do a lot of good in terms of protecting privacy. >>Well, and I think there used to be exceptions made typically only for national security elements, right? And now you're seeing that expanding much more so, which I think is also positive. Right. >>Last question for you as we are wrapping up time here. What can organizations really do to stay ahead of the curve when it comes to, to threat actors? We've got internal external threats. What can they really do to just be ahead of that curve? Is that possible? >>Well, it is now, it's not an easy task so I'm not gonna, you know, trivialize it. But I think that one, having relationships with right organizations in advance always a good thing. That's a, everything from certainly a commercial relationships, but also your peers, right? There's all kinds of fantastic industry spec specific information sharing organizations. I think the biggest thing that impacts is having education across your executive team and testing regularly, right? Having a plan in place, testing it. And it's not just the security pieces of it, right? As security responders, we live these attacks every day, but it's making sure that your general counsel and your head of operations and your CEO knows what to do. Your board of directors, do they know what to do when they receive a phone call from Bloomberg, for example? Are they supposed supposed to answer? Do your employees know that those kind of communications in advance and training can be really critical and make or break a difference in an attack. >>That's a great point about the testing but also the communication that it really needs to be company wide. Everyone at every level needs to know how to react. Wendy, it's been so great having, >>Wait one last question. Sure. Do you have a favorite superhero growing up? >>Ooh, it's gotta be Wonder Woman. Yeah, >>Yeah, okay. Yeah, so cuz I'm always curious, there's not a lot of women in, in security in cyber. How'd you get into it? And many cyber pros like wanna save the world? >>Yeah, no, that's a great question. So I joined the Air Force, you know, I, I was a special agent doing computer crime investigations and that was a great job. And I learned about that from, we had an alumni day and all these alumni came in from the university and they were in flight suits and combat gear. And there was one woman who had long blonde flowing hair and a black suit and high heels and she was carrying a gun. What did she do? Because that's what I wanted do. >>Awesome. Love it. We >>Blonde >>Wonder Woman. >>Exactly. Wonder Woman. Wendy, it's been so great having you on the program. We, we will definitely be following unit 42 and all the great stuff that you guys are doing. Keep up the good >>Work. Thanks so much Lisa. Thank >>You. Day our pleasure. For our guest and Dave Valante, I'm Lisa Martin, live in Las Vegas at MGM Grand for Palo Alto Ignite, 22. You're watching the Cube, the leader in live enterprise and emerging tech coverage.

>> We're back at the Seaport in Boston. Dave Vellante and Paul Gill. You're watching The Cubes coverage of Red Hat Summit, 2022. A little different this year, a smaller venue. Maybe a thousand people. Love the keynotes, compressed. Big virtual audience. So we're happy to be coming to you live, face to face. It's been a while since we've had these, for a lot of folks, this is their first in person event. You know, it's kind of weird getting used to that, but I think in the next few months, it's going to become the new, sort of quasi abnormal. Francis Chow is here. He's the Vice President and GM of In-Vehicle OS and Edge at Red Hat. Francis, welcome. That's the most interesting title we've had all week. So thanks for coming here. >> Thank you, Dave. Thank you, Paul, for having me here. >> So The Edge, I mean The Edge is, we heard about the International Space Station. We heard about ski boots, of course In-Vehicle. What's the Edge to you? >> Well, to me Edge actually could mean many different things, right? The way we look at Edge is, there is the traditional enterprise Edge, where this is the second tier, third tier data centers that this extension from your core, the network and your centralized data center, right to remote locations. And then there are like Telco Edge, right? where we know about the 5G network, right Where you deploy bay stations and which would have a different size of requirements right. Of traditional enterprise edge networks. And then there are Operational Edge where we see the line of business operating on those locations, right? Things like manufacturing for oil rigs, retail store, right? So very wide variety of Edge that are doing OT type of technology, and then last but not least there is the customer on or kind of device edge where we now putting things into things like cars, as you said, like ski booth, and have that interaction with the end consumers. >> Is this why? I mean, there's a lot of excitement at Red. I could tell among the Red hat people about this GM deal here is this why that's so exciting to them? This really encompasses sort of all of those variants of the edge in automotive, in automobile experience. Doesn't it? >> I think why this is exciting to the industry and also to us is that if you look at traditionally how automotive has designed, right the way the architect vehicle today has many subsystems, they are all purpose viewed, very tight cut, coupled with hardware and software. And it's very difficult to reuse, right? So their cause of development is high. The time to develop is long and adding to that there is a lengthy safety certification process which also kind of make it hard. Because every time you make a change in the system you have to re-certify it again. >> Right. >> And typically it takes about six to 12 months to do so. Every time you make a change. So very lengthy passes, which is important because we want to ensure occupants are safe in a vehicle. Now what we bring to the table, which I think is super exciting is we bring this platform approach. Now you can use a consistent platform that is open and you can actually now run multiple doming applications on the same platform which means automakers can reuse components across model years and brands. That will lower the development cost. Now I think one of the key things that we bring to the table is that we introduce a new safety certification approach called Continuous Safety Certification. We actually announced that in our summit last year with the intent, "Hey, we're going to deliver this functional certified Linux platform" Which is the first four Linux. And the way we do it is we work with our partner Excedr to try to define that approach. And at the high level the idea really is to automate that certification process just like how we automate software development. Right, we are adding that monitoring capabilities with functional safety related artifacts in our CI three pipeline. And we are able to aim to cut back that kind of certification time to a fraction of what is needed today. So what we can do, I think with this collaboration with GM, is help them get faster time to market, and then lower development costs. Now, adding to that, if you think about a modern Linux platform, you can update it over the air, right? This is the capability that we are working with GM as well. Now what customers can expect now, right for future vehicle is there will be updates on apps and services, just like your cell phone, right. Which makes your car more capable over time and more relevant for the long term. >> So there's some assumptions you're making at the edge. First of all, you described a spectrum retail store which you know, to me, okay, it's Edge, but you can take an X-86 box or a hyper converged infrastructure throw it in there. And there's some opportunities to do some stuff in real time, but it's kind of an extension natural extension of IT. Whereas in vehicle you got to make some assumptions spotty connectivity to do software download and you can't do truck rolls at the far edge, right? None of that is okay, and so there's some assumptions there and as you say, your role is to compress the time to market, but also deliver a better consumer >> Absolutely. >> Experience, so what can we expect? You started to talk about the future of in vehicle, you know, or EVs, if you will, what should we expect as consumers? You, you're saying over the year software we're seeing that with some of the EV makers, for sure. But what's the future look like? >> I think what consumers can expect is really over a period of time, right? A similar experience, like what you have with your mobile mobile device, right? If you look back 15, 20 years, right? You buy a phone, right? That's the feature that you have with your phone, right? No update, it is what it is right, for the lifetime of the product which is pretty much what you have now, if you buy a vehicle, right. You have those features capabilities and you allow it for the lifetime of the vehicle. >> Sometimes you have to drive in for a maintenance, a service to get a software update. >> We can talk about that too right. But as we make the systems, update-able right you can now expect more frequent and seamless update of both the operating system and the application services that sit on top of that. Right, so I think right in the future consumers can expect more capable vehicles after you purchase it because new developmental software can now be done with an update over the air. >> I assume this relationship with GM is not exclusive. Are you talking with other automakers as well? >> We are talking to auto makers, other auto makers. What we working with GM is really a product that could work for the industry, right? This is actually what we both believe in is the right thing to do right? As we are able to standardize how we approach the infrastructure. I think this is a good thing for the whole industry to help accelerate innovation for the entire industry. >> Well which is sort of natural next question. Are we heading toward an open automotive platform? Like we have an open banking platform in that industry. Do you see the possibility that there could be a single platform that all or most of the auto makers will work on? >> I wouldn't use the word single, but I definitely would use the word open. Right? Our goal is to build this open platform, right. Because we believe in open source, right. We believe in community, right. If we make it open, we have more contributors to come in and help to make the system better in a way faster. And actually like you said, right. Improve the quality, right, better. Right, so that the chance of recall is now lower with, with this approach. >> You're using validated patterns as part of this initiative. Is that right? And what is a validated pattern? How is it different from a reference architecture? Is it just kind of a new name for reference architecture? or what value does it bring to the relation? >> For automotive right, we don't have a validated pattern yet but they can broadly kind of speak about what that is. >> Yeah. >> And how we see that evolve over time. So validated pattern basically is a combination of Red Hat products, multiple Red Hat products and partner products. And we usually build it for specific use case. And then we put those components together run rigorous tests to validate it that's it going to work, so that it becomes more repeatable and deployable for those particular edge use cases. Now we do work with our partners to make it happen, right. Because in the end, right we want to make a solution that is about 80% of the way and allow our partners to kind of add more value and their secret sauce on top and deploy it. Right, and I'll give you kind of one example, right You just have the interview with the Veterans Affairs team, right. One of our patents, right? The Medical Diagnosis Pattern, right. Actually we work with them in the early development stage of that. Right, what it does is to help make assessments on pneumonia with chest X rates, right. So it's a fully automated data pipeline. We get the chest x-ray from an object store use AIML to diagnose whether there's new pneumonia. And then I'll put that in a dashboard automated with the validated pattern. >> So you're not using them today, but can we expect that in the future? It sounds like >> Yes absolutely it's in the works, yes. >> It would be a perfect vertical. >> How do you believe your work with GM? I mean, has implications across Red hat? It seems like there are things you're going to be doing with GM that could affect other parts of your own product portfolio. >> Oh, absolutely. I think this actually is, it's a pivotal moment for Red Hat and the automotive industry. And I think broadly speaking for any safety conscious industry, right. As we create this Proof-point right that we can build a Linux system that is optimized for footprint performance, realtime capabilities, and be able to certify it for safety. Right I think all the adjacent industry, right. You think about transportation, healthcare, right. Industry that have tight safety requirements. It's just opened up the aperture for us to adjust those markets in the future. >> So we talked about a lot about the consumerization of IT over the last decade. Many of us feel as though that what's going on at the Edge, the innovations that are going on at the Edge realtime AI inferencing, you know, streaming data ARM, the innovations that ARM and others are performing certainly in video until we heard today, this notion of, you know, no touch, zero touch provisioning that a lot of these innovations are actually going to find their way into the enterprise. Kind of a follow on fault of what you were just talking about. And there's probably some future disruptions coming. You can almost guarantee that, I mean, 15 years or so we get that kind of disruption. How are you thinking about that? >> Well, I think you company, right. Some of the Edge innovation, right. You're going to kind of bring back to enterprise over time. Right but the one thing that you talk about zero touch provisioning right. Is critical right? You think about edge deployments. You're going to have to deal with a very diverse set of environments on how deployments are happen. Right think about like tail code based stations, right. You have somewhere between 75,000 to 100,000 base stations in the US for each provider right. How do you deploy it? Right, if you let's say you push one update or you want the provision system. So what we bring to the table in the latest open shift release is that, hey we make provisioning zero touch right, meaning you can actually do that without any menu intervention. >> Yeah, so I think the Edge is going to raise the bar for the enterprise, I guess is my premise there. >> Absolutely. >> So Francis, thanks so much for coming on The Cube. It's great to see you and congratulations on the collaboration. It's a exciting area for you guys. >> Thank you again, Dave and Paul. >> Our pleasure, all right keep it right there. After this quick break, we'll be back. Paul Gill and Dave Vellante you're watching The Cubes coverage Red Hat Summit 2022 live from the Boston Seaport. Be right back.

welcome back to the cube's presentation of the aws executive summit at re invent 2021 made possible by accenture my name is dave vellante we're going to look at how digital infrastructure is helping to transform consumer experiences specifically how an insurance company is changing its industry by incentivizing and rewarding consumers who change their behavior to live healthier lives a real passion of of mine and getting to the really root cause of health with me now are simon guest who's the chief executive officer of generality vitality gmbh and niels mueller who's the managing director at the cloud first application engineering lead for the european market at accenture gentlemen welcome to the cube thanks for having us you're very welcome simon generally vitality it's a really interesting concept that you guys have envisioned and now put into practice tell us how does it all work sure no problem and thanks for for having us on dave it's a pleasure to be here so look uh generally vitality is in its uh it's core pretty simple concepts so it's uh it's a program that you have on your phone and the idea of this program is that it's a it's a wellness coach for you as an individual and it's going to help you to understand your health and where you are in terms of the state of your health at the moment and it's going to take you on a journey to improve your your lifestyle and your wellness and hopefully help you to lead a healthier and a more sort of mindful life i guess is is the best way of summarizing it from um from our point of view with insurance company of course you know our historical role has always been to uh be the company that's there if something goes wrong you know so if unfortunately you pass away or you have sickness in your in your life or in your family's life that's that's historically been our role but what we see with generality vitality is something a little bit different so it's a program that really is uh supposed to be with you every day of your life to help you to live a healthier life it's something that we already have in in four european markets in fact in five from this week i'm a little bit behind the time so we're live already in in germany in france in austria and italy and in spain and fundamentally what we what we do dave is too is to say to customers look if you want to understand your health if you want to improve it by moving a little bit more by visiting the doctor more by eating healthier by healthy choices on a daily basis we're going to help you to do that and we're going to incentivize you for going on this journey and making healthy choices and we're going to reward you for for doing the same so you know we partner up with with great companies like garmin like adidas like big brands that are let's say invested in this health and wellness space so that we can produce really an ecosystem for customers that's all about live well make good choices be healthy have an insurance company that partners you along that journey and if you do that we're going to reward you for for that so you know we're here not just in the difficult times which of course is one of our main roles but we're here as a partner as a lifetime partner to you too to help you feel better and live a better life i love it i mean it sounds so simple but but it's i'm sure it's very complicated to to make the technology simple for the user you've got mobile involved you've got the back end and we're going to get into some of the tech but first i want to understand the member engagement and some of the lifestyle changes simon that you've analyzed what's the feedback that you're getting from your customers what does the data tell you how do the incentives work as well what what is the incentive for the the member to actually do the right thing sure look i think actually the the covered uh situation that we've had in the last sort of two years has really crystallized the fact that this is something that we really ought to be doing and something that our customers really value so i mean look just to give you a bit of a sort of information about how it works for for customers so what we try to do with them is is to get customers to understand uh their current health situation you know using their phone so uh you know we ask our customers to go through a sort of health assessment around how they live what they eat how they sleep you know and to go through that sort of process uh and to give them what a vitality age which is a sort of uh you know sort of actuarial comparison with their real age so i'm i'm 45 but unfortunately my my vitality age is 49 and it means i have some work to do to bring that back together uh and what we see is that you know two-thirds of our customers take this test every year because they want to see how they are progressing on an annual basis in terms of living a healthier life and if what if what they are doing is having an impact on their life expectancy and their lifespan and their health span so how long are they going to live healthier for so you see them really engaging in this in this approach of understanding their current situation then what we know actually because the program is built around this model that uh really activity and moving and exercise is the biggest contributor to living a healthier life we know that the majority of deaths are caused by lifestyle illness is like you know poor nutrition and smoking and drinking alcohol and not exercising and so a lot of the program is really built around getting people to move more and it's not about being an athlete it's about you know getting off the the underground one station earlier walking home or making sure you do your 10 000 steps a day and what we see is that that sort of 40 of our customers are on a regularly basis linking either their phone or their their exercise device to our program and downloading that data so that they can see how how much they are exercising and at the same time what we do is we set we set our customers weekly challenges to say look if you can move a little bit more than last week we are going to to reward you for that and we see that you know almost half of our customers are achieving this weekly goal every week and it's really a fantastic level of engagement that normally is an insurer uh we don't see the way the rewards work is is pretty simple it's similar in a way to an airline program so every good choice you make every activity you do every piece of good food that you eat when you check your on your health situation we'll give you points and the more points you get you go through through a sort of status approach of starting off at the bottom status and ending up at a gold and then a platinum status and the the higher up you get in the status that the higher the value of the rewards that we give you so almost a quarter of our customers now and this is accelerated through provide they've reached that platinum status so they are the most engaged customers that we we have and those ones who are really engaging in the in the program and what we really try to create is this sort of virtuous circle that says if you live well you make good choices you improve your health you you progress through the program and we give you better and stronger and more uh valuable rewards for for doing that and some of those rewards are are around health and wellness so it might be that you get you get a discount on on gym gear from adidas it might be that you get a discount on a uh on a device from garmin or it might be actually on other things so we also give people amazon vouchers we also give people uh discounts on holidays and another thing that we we did actually in the last year which we found really powerful is that we've given the opportunity for our customers to convert those rewards into charitable donations because we we work in generality with a with a sort of um campaign called the human safety net which is helping out the poorest people in society and some what our customers do a lot of the time is instead of taking those financial rewards for themselves they convert it into a charitable donation so we're actually also thinking wellness and feeling good and insurance and some societal good so we're really trying to create a virtuous circle of uh of engagement with our customers i mean that's a powerful cocktail i love it you got the the data because if i see the data then i can change my behavior you got the gamification piece you actually have you know hard dollar rewards you could give those to charities and and you've got the the most important which is priceless can't put a value on good health i got one more question for simon and niels i'd love you to chime in as well on this question how did you guys decide simon to engage with accenture and aws and the cloud to build out this platform what's the story behind that collaboration was there unique value that you saw that that you wanted to tap that you feel like they bring to the table what was your experience yeah look i mean we worked at accenture as well because the the the sort of construct of this vitality proposition is a pretty a pretty complex one so you mentioned that the idea is simple but the the build is not so uh is not so simple and that that's the case so accenture's been part of that journey uh from the beginning they're one of the partners that we work with but specifically around the topic of rewards uh you know we're we're a primarily european focused organization but when you take those countries that i mentioned even though we're next to each other geographically we're quite diverse and what we wanted to create was really a sustainable and reusable and consistent customer experience that allowed us to go and get to market with an increasing amount of efficiency and and to do that we needed to work with somebody who understood our business has this historical let's say investment in in the vitality concept so so knows how to bring it to life but that what then could really support us in making uh what can be a complex piece of work as simple and as as replicable as possible across multiple markets because we don't want to go reinventing the wheel every time we do we move to a new market so we need to find a balance between having a consistent product a consistent technology offer a consistent customer experience with the fact that we we operate in quite diverse markets so this was let's say the the reason for more deeply engaging with accenture on this journey thank you very much niels why don't you comment on on that as well i'd love to to get your thoughts and and really really it's kind of your role here i mean accenture global si deep expertise in industry but also technology what are your thoughts on this topic yeah i'd love to love to comment so when we started the journey it was pretty clear from the outset that we would need to build this on cloud in order to get this scalability and this ability to roll out to different markets have a central solution that can act as a template for the different markets but then also have the opportunity to localize different languages different partners for the rewards there's different reward partners in the different markets so we needed to build in an asset basically that could work as a tempos centrally standardizing things but also leaving enough flexibility to to then localize in the individual markets and if we talk about some of the more specific requirements so one one thing that gave us headaches in the beginning was the authentication of the users because each of the markets has their own systems of record where the basically the authentication needs to happen and we somehow needed to still find a holistic solution that comes through the central platform and we were able to do that at the end through the aws cognito service sort of wrapping the individual markets uh local idp systems and by now we've even extended that solution to have a standalone cloud native kind of idp solution in place for markets that do not have a local idp solution in place or don't want to use it for for this purpose yeah so you had you had data you have you had the integration you've got local laws you mentioned the flexibility you're building ecosystems that are unique to the to the local uh both language and and cultures uh please you had another comment i interrupted you yeah i know i just wanted to expand basically on the on the requirements so that was the central one being able to roll this out in a standardized way across the markets but then there were further requirements for example like being able to operate that platform with very low operations overhead there is no large i.t team behind generally vitality that you know works to serve us or can can act as this itis backbone support so we needed to have basically a solution that runs itself that runs on autopilot and that was another big big driver for first of all going to cloud but second of all making specific choices within cloud so we specifically chose to build this as a cloud native solution using for example manage database services you know with automatic backup with automatic ability to restore data that scales automatically that you know has all this built in which usually maybe a database administrator would take care of and we applied that concept basically to every component to everything we looked at we we applied this requirement of how can this run on autopilot how can we make this as much managed by itself within the cloud as possible and then land it on these services and for example we also used the the api gateway from from aws for our api services that also came in handy when for example we had some response time issues with the third party we needed to call and then we could just with a flick of a button basically introduce caching on the level of the api gateway and really improve the user experience because the data you know wasn't updated so much so it was easier to cache so these are all experiences i think that that proved in the end that we made the right choices here and the requirements that that drove that to to have a good user experience niels would you say that the architecture is is a sort of a data architecture specifically is it a decentralized data architecture with sort of federated you know centralized governance or is it more of a centralized view what if you could talk about that yeah it's it's actually a centralized platform basically so the core product is the same for all the markets and we run them as different tenants basically on top of that infrastructure so the data is separated in a way obviously by the different tenants but it's in a central place and we can analyze it in a central fashion if if the need arises from from the business and the reason i ask that simon is because essentially i look at this as a as largely a data offering for your customers and so niels you were talking about the local language and simon as well i would imagine that that the local business lines have specific requirements and specific data requirements and so you've got to build an architecture that is flexible enough to meet those needs yet at the same time can ensure data quality and governance and security that's not a trivial challenge i wonder if you both could comment on that yeah maybe maybe i'll give a start and then simon can chime in so um what we're specifically doing is managing the rewards experience right so so our solution will take care of tracking what rewards have been earned for what customer what rewards have been redeemed what rewards can be unlocked on the next level and we we foreshadow a little bit to to motivate to incentivize the customer and as that data sits in an aws database in a tenant by tenant fashion and you can run analysis on top of that maybe what you're getting into is also the let's say the exercise data the fitness device tracking data that is not specifically part of what my team has built but i'm sure simon can comment a little bit on that angle as well yeah please yeah sure sure yeah sure so look i think them the topic of data and how we use it uh in our business is a very is very interesting one because it's um it's not historically being seen let's say as the remit of insurers to go beyond the you know the the data that you need to underwrite policies or process claims or whatever it might be but actually we see that this is a whole point around being able to create some shared value in in this kind of product and and what i mean by that is uh look if you are a customer and you're buying an insurance policy it might be a life insurance or health insurance policy from from generali and we are giving you access to this uh to this program and through that program you are living a healthier life and that might have a you know a positive impact on generali in terms of you know maybe we're going to increase our market share or maybe we're going to lower claims or we're going to generate value out of that then one of the points of this program is that we then share that value back with customers through the rewards on the platform that we that we've built here and of course being able to understand that data and to quantify it and to value that data is an important part of the of the the different stages of how you of how much value you are creating and it's also interesting to know that you know in a couple of our markets we we operate in the corporate space so not with retail customers but with with organizations and one of the reasons that those companies give vitality to their employees is that they want to see things like the improved health of a workforce they want to see higher presenteeism lower absenteeism of employees and of course being able to demonstrate that there's a sort of correlation between participation in the vitality program and things like that is also is also important and as we've said the markets are very different so we need to be able to to take the data uh that we have out of the vitality program uh and be able in in the company that that i'm managing to to interpret that data so that in our insurance businesses we are able to make good decisions about the kind of insurance products we i think what's interesting to uh to make clear is that actually that the kind of health data that we generate stays purely within the vitality business itself and what we do inside the vitality business is to analyze that data and say okay is this is this also helping our insurance businesses to to drive uh yeah you know better top line and bottom line in the in the relevant business lines and this is different per company and per mark so yeah being able to interrogate that data understand it apply it in different markets and different uh distribution systems and different kinds of approaches to insurance is an is an important one yes it's an excellent example of a digital business in in you know we talk about digital transformation what does that mean this is what it means i i'd love i mean it must be really interesting board discussions because you're transforming an industry you're lowering overall cost i mean if people are getting less sick that's more profit for your company and you can choose to invest that in new products you can give back some to your corporate clients you can play that balancing act you can gain market share and and you've got some knobs to turn some levers uh for your stakeholders which is which is awesome neil something that i'm interested in i mean it must have been really important for you to figure out how to determine and measure success i mean you're obviously removed it's up it's up to generality vitality to get adoption for for their customers but at the same time the efficacy of your solution is going to determine you know the ease of of of delivery and consumption so so how did you map to the specific goals what were some of the key kpis in terms of mapping to their you know aggressive goals besides the things we already touched on i think one thing i would mention is the timeline right so we we started the team ramping in january or february and then within six months basically we had the solution built and then we went through a extensive test phase and within the next six months we had the product rolled out to three markets so this speed to value speed to market that we were able to achieve i think is one of the key um key criteria that also simon and team gave to us right there was a timeline and that timeline was not going to move so we needed to make a plan adjust to that timeline and i think it's both a testament to to the team's work that they did that we made this timeline but it also is enabled by technologies like cloud i have to say if i go back five years ten years if if you had to build in a solution like this on a corporate data center across so many different markets and each managed locally there would have been no way to do this in 12 months right that's for sure yeah i mean simon you're a technology company i mean insurance has always been a tech heavy company but but as niels just mentioned if you had to do that with it departments in each region so my question is is now you've got this it's almost like non-recurring engineering costs you've got that it took one year to actually get the first one done how fast are you able to launch into new markets just from a technology perspective not withstanding any you know local regulations and figuring out to go to market is that compressed yeah so if you are specifically technology-wise i think we would be able to set up a new market including localizations that often involves translation of because in europe you have all the different languages and so on at i would say four to six weeks we probably could stand up a localized solution in reality it takes more like six to nine months to get it rolled out because there's many other things involved obviously but just our piece of the solution we can pretty quickly localize it to a new market but but simon that means that you can spend time on those other factors you don't have to really worry so much about the technology and so you've launched in multiple european markets what do you see for the future of this program come to america you know you can fight you can find that this program in america dave but with one of our competitors we're not we're not operating so much in uh but you can find it if you want to become a customer for sure but yes you're right so look i think from from our perspective uh you know to put this kind of business into a new market it's not it's not an easy thing because what we're doing is not offering it just as a as a service on a standalone basis to customers we want to link it with with insurance business in the end we are an insurance business and we want to to see the value that comes from that so there's you know there's a lot of effort that has to go into making sure that we land it in the right way also from a customer publishing point of view with our distribution and they are they are quite different so so yeah look coming to the question of what's next i mean it comes in three stages for me so as i mentioned we are uh in five markets already uh in next in the first half of 2022 we'll also come to to the czech republic and poland uh which we're excited to to do and that will that will basically mean that we we have this business in in the seven main uh general markets in europe related to life and health business which is the most natural uh let's say fit for something like vitality then you know the next the sort of second part of that is to say okay look we have a program that's very heavily focused around uh activity and rewards and that that's a good place to start but you know wellness these days is not just about you know can you move a bit more than you did historically it's also about mental well-being it's about sleeping good it's about mindfulness it's about being able to have a more holistic approach to well-being and and covert has taught us and customer feedback has taught us actually that this is something where we need to to go and here we need to have the technology to move there as well so to be able to work with partners that are not just based on on on physical activity but also also on mindfulness so this is how one other way we'll develop the proposition and i think the third one which is more strategic and and we are you know really looking into is there's clearly something in the whole uh perception of incentives and rewards which drives a level of engagement between an insurer like generali and its customers that it hasn't had historically so i think we need to learn you know forget you know forgetting about the specific one of vitality being a wellness program but if there's an insurer there's a role for us to play where we offer incentives to customers to do something in a specific way and reward them for doing that and it creates value for us as an insurer then then this is probably you know a place we want to investigate more and to be able to do that in in other areas means we need to have the technology available that is as i said before replicable faster market can adapt quickly to to other ideas that we have so we can go and test those in in different markets so yes we have to we have to complete our scope on vitality we have to get that to scale and be able to manage all of this data at scale all of those rewards at real scale and uh to have the technology that allows us to do that without without thinking about it too much and then to say okay how do we widen the proposition and how do we take the concept of vitality that sits behind vitality to see if we can apply it to other areas of our business and that's really what the future is is going to look like for us you know the the isolation era really taught us that if you're not a digital business you're out of business and pre-kov a lot of these stories were kind of buried uh but the companies that have invested in digital are now thriving and this is an awesome example jeff another point is that jeff amebacher one of the founders of cloudera early facebook employee famously said about 10 12 years ago the best and greatest engineering minds of our my generation are trying to figure out how to get people to click on ads and this is a wonderful example of how to use data to change people's lives so guys congratulations best of luck really awesome example of applying technology to create an important societal outcome really appreciate you your time on the cube thank you thanks bye-bye all right and thanks for watching this segment of thecube's presentation of the aws executive summit at reinvent 2021 made possible by accenture keep it right there for more deep dives [Music] you

(upbeat music) >> Welcome back to theCUBE's presentation of the AWS Executive Summit at re:Invent 2021 made possible by Accenture. My name is Dave Vellante. We're going to look at how digital infrastructure is helping to transform consumer experiences, specifically how an insurance company is changing its industry by incentivizing and rewarding consumers who changed their behavior to live healthier lives, a real passion of mine, and getting to the really root cause of health. With me now are Simon Guest, who's the Chief Executive Officer of Generali Vitality, GmbH, and Nils Muller-Sheffer, who's the Managing Director at the Cloud First Application Engineering Lead for the European market at Accenture. Gentlemen, welcome to theCUBE. >> Thanks for having us. >> You're very welcome Simon. Simon, Generali Vitality is a really interesting concept that you guys have envisioned and now put it into practice. Tell us how does it all work? >> Sure. No problem. And thanks for having us on David, pleasure to be here. So look, Generali Vitality is in its core a pretty simple concept. It's a program that you have on your phone. And the idea of this program is that it's a wellness coach for you as an individual, and it's going to help you to understand your health and where you are in terms of the state of your health at the moment, and it's going to take you on a journey to improve your lifestyle and your wellness, and hopefully help you to live a healthier and a more sort of mindful life, I guess, is the best way of summarizing it. From our point of view as an insurance company, of course, our historical role has always been to be the company that's there if something goes wrong. So if unfortunately you pass away or you have sickness in your life or your family's life, that's historically been our role. But what we see with Generali Vitality is something a little bit different. So it's a program that really is supposed to be with you every day of your life to help you to live a healthier life. It's something that we already have in for European markets and in fact, in five from this week, I'm a little bit behind the times. So we're live already in Germany, in France, in Austria, in Italy and in Spain. And fundamentally what we do Dave, is to say to customers, "Look, if you want to understand your health, if you want to improve it by moving a little bit more, or by visiting the doctor more, by eating healthier, by healthy choices on a daily basis, we're going to help you to do that. And we're going to incentivize you for going on this journey and making healthy choices. And we're going to reward you for doing the same." So, we partner up with great companies like Garmin, like Adidas, like big brands that are, let's say, invested in this health and wellness space so that we can produce really an ecosystem for customers that's all about live well, make good choices, be healthy, have an insurance company that partners you along that journey. And if you do that, we've going to reward you for that. So, we're here not just in a difficult times, which of course is one of our main roles, but we're here as a partner, as a lifetime partner to you to help you feel better and live a better life. >> I love it, I mean, it sounds so simple, but I'm sure it's very complicated to make the technology simple for the user. You've got mobile involved, you've got the back end and we're going to get into some of the tech, but first I want to understand the member engagement and some of the lifestyle changes Simon that you've analyzed. What's the feedback that you're getting from your customers? What does the data tell you? How do the incentives work as well? What is the incentive for the member to actually do the right thing? >> Sure, I think actually that the COVID situation that we've had in the last sort of two years is really crystallized the fact that this is something that we really ought to be doing and something that our customers really value. Just to give you a bit of a sort of information about how it works for our customers. So what we try to do with them, is to get customers to understand their current health situation, using their phone. So, we asked our customers to go through a sort of health assessments around how they live, what they eat, how they sleep, and to go through that sort of process and to give them all the Vitality age, which is a sort of actuarial comparison with their real age. So I'm 45, but unfortunately my Vitality age is 49 and it means I have some work to do to bring that back together. And what we see is that, two thirds of our customers take this test every year because they want to see how they are progressing on an annual basis in terms of living a healthier life. And if what they are doing is having an impact on their life expectancy and their lifespan and their health span. So how long are they going to live healthier for? So you see them really engaging in this approach of understanding that current situation. Then what we know actually, because the program is built around this model that's really activity and moving, and exercise is the biggest contributors to living a healthier life. We know that the majority of deaths are caused by lifestyle illnesses like poor nutrition and smoking and drinking alcohol and not exercising. And so a lot of the program is really built around getting people to move more. And it's not about being an athlete. It's about, getting off the underground one station earlier and walking home or making sure you do your 10,000 steps a day. And what we see is that that sort of 40% of our customers are on a regularly basis linking either their phone or their exercise device to our program and downloading that data so that they can see how much they are exercising. And at the same time, what we do is we set our customers weekly challenges to say, look, if you can move a little bit more than last week, we are go into to reward you for that. And we see that almost half of our customers are achieving this weekly goal every week. And it's really a level of engagement that normally as an insurer, we don't see. The way that rewards work is pretty simple. It's similar in a way to an airline program. So every good choice you make every activity to every piece of good food that you eat. When you check your on your health situation, we'll give you points. And the more points you get, you go through through a sort of status approach of starting off at the bottom status and ending up at a golden and a platinum status. And the higher up you get in the status, the higher the value of the rewards that we give you. So almost a quarter of our customers now, and this has accelerated through COVID have reached that platinum status. So they are the most engaged customers that we have and those ones who are really engaging in the program. And what we really tried to create is this sort of virtuous circle that says If you live well, you make good choices, you improve your health, you progress through the program and we give you better and stronger and more valuable rewards for doing that. And some of those rewards are around health and wellness. So it might be that you get a discounts on gym gear from Adidas, it might be that you get a discount on a device from Garmin, or it might be actually on other things. We also give people Amazon vouchers. We also give people discounts on holidays. And another thing that we did actually in the last year, which we found really powerful is that we've given the opportunity for our customers to convert those rewards into charitable donations. Because we work in generosity with a sort of campaign called The Human Safety Net, which is helping out the poorest people in society. And so what our customers do a lot of the time is instead of taking those financial rewards for themselves, they convert it into a charitable donation. So we're actually also linking wellness and feeling good and insurance and some societal goods. So we're really trying to create a virtuous circle of engagement with our customers. >> That's a powerful cocktail. I love it. You've got the data, because if I see the data, then I can change my behavior. You've got the gamification piece. You actually have hard dollar rewards. You could give those to charities and you've got the most important, which is priceless, you can't put a value on good health. I got one more question for Simon and Nils I'd love for you to chime in as well on this question. How did you guys decide, Simon, to engage with Accenture and AWS and the cloud to build out this platform? What's the story behind that collaboration? Was there unique value that you saw that you wanted to tap, that you feel like they bring to the table? What was your experience? >> Yeah, we work with Accenture as well because the sort of constructs of this Vitality proposition is a pretty complex one. So you mentioned that the idea is simple, but the build is not so simple and that's the case. So Accenture has been part of that journey from the beginning. They are one of the partners that we work with, but specifically around the topic of rewards, we're primarily European focused organization, but when you take those countries that I mentioned, even though we're next to each other geographically, we're quite diverse. And what we wanted to create was really a sustainable and reusable and consistent customer experience that allowed us to go get to market with an increasing amounts of efficiency. And to do that, we needed to work with somebody who understood our business, has this historical, let's say investment in the Vitality concepts and so knows how to bring it to life, but then could really support us in making what can be a complex piece of work, as simple, as replicable as possible across multiple markets, because we don't want to go reinventing the wheel every time we knew we moved to a new market. So we need to find a balance between having a consistent product, a consistent technology offer, a consistent customer experience with the fact that we operate in quite diverse markets. So this was, let's say the reason for more deeply engaging with Accenture on this journey. >> Thank you very much, Nils, why don't you comment on that as well? I'd love to get your thoughts and really is kind of your role here, an Accenture global SI, deep expertise in industry, but also technology, what are your thoughts on this topic? >> Yeah, I'd love to love to comment. So when we started the journey, it was pretty clear from the outset that we would need to build this on cloud in order to get this scalability and this ability to roll out to different markets, have a central solution that can act as a template for the different markets, but then also have the opportunity to localize different languages, different partners for the rewards, there's different reward partners in the different markets. So we needed to build an asset basically that could work as a template, centrally standardizing things, but also leaving enough flexibility to then localize in the individual markets. And if we talk about some of the most specific requirements, so one thing that gave us headaches in the beginning was the authentication of the users because each of the markets has their own systems of record where the, basically the authentication needs to happen. And if we somehow needed to still find a holistic solution that comes through the central platform, and we were able to do that at the end through the AWS cognitive service, sort of wrapping the individual markets, local IDP systems. And by now we've even extended that solution to have a standalone cloud native kind of IDP solution in place for markets that do not have a local IDP solution in place, or don't want to use it for this purpose. >> So you had data, you had the integration, you've got local laws, you mentioned the flexibility, you're building ecosystems that are unique to the local, both language and cultures. Please, you had another comment, I interrupted you. >> No, I just wanted to expand basically on the requirements. So that was the central one being able to roll this out in a standardized way across the markets, but then there were further requirements. For example, like being able to operate the platform with very low operations overhead. There is no large IT team behind Generali Vitality that, works disservice or can act as this backbone support. So we needed to have basically a solution that runs itself that runs on autopilot. And that was another big, big driver for first of all, going to cloud, but second of all, making specific choices within cloud. So we specifically chose to build this as a cloud native solution using for example, managed database services, with automatic backup, with automatic ability to restore data that scales automatically that has all this built in which usually maybe in a database administrator would take care of. And we applied that concept basically to every component, to everything we looked at, we applied this requirement of how can this run on autopilot? How can we make this as much managed by itself within the cloud as possible, and then lend it on these services. For example, we also use the API gateway from AWS for our API services that also came in handy when, for example, we had some response time issues with the third party we needed to call. And then we could just with a flick of a button basically, introduced caching on the level of the API gateway and really improve the user experience because the data wasn't updated so much, so it was easier to cache. So these are all experiences I think that that proved in the end that we made the right choices here and the requirements that drove that to have a good user experience. >> Would you say that the architecture is a sort of a, data architecture specifically, is it a decentralized data architecture with sort of federated, centralized governance? Or is it more of a centralized view, wonder if you could talk about that? >> Yeah, it's actually a centralized platform basically. So the core product is the same for all the markets and we run them as different tenants basically on top of the infrastructure. So the data is separated in a way, obviously by the different tenants, but it's in a central place and we can analyze it in a central fashion if the need arises from the business. >> And the reason I asked that Simon is because essentially I look at this as largely a data offering for your customers. And so Nils, you were talking about the local language and Simon as well. I would imagine that the local business lines have specific requirements and specific data requirements. And so you've got to build an architecture that is flexible enough to meet those needs yet at the same time can ensure data quality and governance and security. And that's not a trivial challenge. I wonder if you both could comment on that. >> Yeah, maybe I'll give a start and then Simon can chime in. So what we're specifically doing is managing the rewards experience, so our solution will take care of tracking what rewards have been earned for what customer, what rewards have been redeemed, what rewards can be unlocked on the next level, and we foreshadow a little bit to motivate incentivize the customer and asset that data sits in an AWS database by tenant fashion. And you can run analysis on top of that. Maybe what you're getting into is also the, let's say the exercise data, the fitness device tracking data that is not specifically part of what my team has built, but I'm sure Simon can comment a little bit on that angle as well. >> Yeah, please. >> Yeah, sure. I think the topic of data and how we use it in our business is a very interesting one because it's not historically been seen, let's say as the remit of insurance to go beyond the data that you need to underwrite policies or process claims or whatever it might be. But actually we see that this is a whole point around being able to create some shared value in this kind of products. And what I mean by that is, if you are a customer and you're buying an insurance policy, it might be a life insurance or health insurance policy from Generali, and we're not giving you access to this program. And through that program, you are living a healthier life and that might have a positive impact on generosity in terms of, maybe we're going to increase our market share, or maybe we are going through lower claims, or we're going to generate value of that then. One of the points of this program is we then share that value back with customers, through the rewards on the platform that we've built here. And of course, being able to understand that data and to quantify it and to value that data is an important part of the different stages of how much value you are creating. And it's also interesting to know that, in a couple of our markets, we operate in the corporate space. So not with retail customers, but with organizations. And one of the reasons that those companies give Vitality to their employees is that they want to see things like the improved health of a workforce. They want to see higher presenteeism, lower absenteeism of employees, and of course, being able to demonstrate that there's a sort of correlation between participation in the Vitality program and things like that is also important. And as we've said, the markets are very different. So we need to be able to take the data that we have out of the Vitality Program and be able in the company that I'm managing to interpret that data so that in our insurance businesses, we are able to make good decisions about kind of insurance product we have. I think what's interesting to make clear is that actually that the kind of health data that we generate states purely within the Vitality business itself and what we do inside the Vitality business is to analyze that data and say, is this also helping our insurance businesses to drive better top line and bottom line in the relevant business lines? And this is different per company. Being able to interrogate that data, understand it, apply it in different markets, in different distribution systems and different kinds of approaches to insurance is an important one, yes. >> It's an excellent example of a digital business and we talked about digital transformation. What does that mean? This is what it means. It must be really interesting board discussions because you're transforming an industry, you're lowering overall costs. I mean, if people are getting less sick, that's more profit for your company and you can choose to invest that in new products, you can give back some to your corporate clients, you can play that balancing act, you can gain market share. And you've got some knobs to turn, some levers, for your stakeholders, which is awesome. Nils, something that I'm interested in, it must've been really important for you to figure out how to determine and measure success. Obviously it's up to Generali Vitality to get adoption for their customers, but at the same time, the efficacy of your solution is going to determine, the ease of delivery and consumption. So, how did you map to the specific goals? What were some of the key KPIs in terms of mapping to their aggressive goals. >> Besides the things we already touched on, I think one thing I would mention is the timeline. So, we started the team ramping in January, February, and then within six months basically, we had the solution built and then we went through a extensive test phase. And within the next six months we had the product rolled out to three markets. So this speed to value, speed to market that we were able to achieve, I think is one of the key criteria that also Simon and team gave to us. There was a timeline and that time I was not going to move. So we needed to make a plan, adjust to that timeline. And I think it's both a testament to the team's work that we met this timeline, but it also is enabled by a technology stack cloud. I have to say, if I go back five years, 10 years, if you had to build in a solution like this on a corporate data center across so many different markets and each managed locally, there would've been no way to do this in 12 months, that's for sure. >> Yeah, Simon, you're a technology company. I mean, insurance has always been a tech heavy company, but as Nils just mentioned, if you had to do that with IT departments in each region. So my question is now you've got this, it's almost like nonrecurring engineering costs, it took one year to actually get the first one done, how fast are you able to launch into new markets just from a technology perspective, not withstanding local regulations and figuring out the go to market? Is that compressed? >> So you asked specifically technology-wise I think we would be able to set up a new market, including localizations that often involves translation of, because in Europe you have all the different languages and so on, I would say four to six weeks, we probably could stand up a localized solution. In reality, it takes more like six to nine months to get it rolled out because there's many other things involved, obviously, but just our piece of the solution, we can pretty quickly localize it to a new market. >> But Simon, that means that you can spend time on those other factors, you don't have to really worry so much about the technology. And so you've launched in multiple European markets, what do you see for the future of this program? Come to America. >> You can find that this program in America Dave, but with one of our competitors, we're not operating so much in the US, but you can find it if you want to become a customer for sure. But yes, you're right. I think from our perspective, to put this kind of business into a new market is not an easy thing because what we're doing is not offering it just as a service on a standalone basis to customers, we want to link it with insurance business. In the end, we are an insurance business, and we want to see the value that comes from that. So there's a lot of effort that has to go into making sure that we land it in the right way, also from a customer proposition points of view with our distribution, they are all quite different. Coming to the question of what's next? It comes in three stages for me. So as I mentioned, we are in five markets already. In the first half of 2022, we'll also come to the Czech Republic and Poland, which we're excited to do. And that will basically mean that we have this business in the seven main Generali markets in Europe related to life and health business, which is the most natural at let's say fit for something like Vitality. Then, the sort of second part of that is to say, we have a program that is very heavily focused around activity and rewards, and that's a good place to start, but, wellness these days is not just about, can you move a bit more than you did historically, it's also about mental wellbeing, it's about sleeping good, it's about mindfulness, it's about being able to have a more holistic approach to wellbeing and COVID has taught us, and customer feedback has taught is actually that this is something where we need to go. And here we need to have the technology to move there as well. So to be able to work with partners that are not just based on physical activity, but also on mindfulness. So this is how one other way we will develop the proposition. And I think the third one, which is more strategic and we are really looking into is, there's clearly something in the whole perception of incentives and rewards, which drives a level of engagement between an insurer like Generali and its customers that it hasn't had historically. So I think we need to learn, forgetting about the specific one or Vitality being a wellness program, but if there's an insurer, there's a role for us to play where we offer incentives to customers to do something in a specific way and reward them for doing that. And it creates value for us as an insurer, then this is probably a place that we'd want to investigate more. And to be able to do that in other areas means we need to have the technology available, that is, as I said before, replicable faster market can adapt quickly to other ideas that we have, so we can go and test those in different markets. So yes, we have to, we have to complete our scope on Vitality, We have to get that to scale and be able to manage all of this data at scale, all of those rewards that real scale, and to have the technology that allows us to do that without thinking about it too much. And then to say, okay, how do we widen the proposition? And how do we take the concept that sits behind Vitality to see if we can apply it to other areas of our business. And that's really what the future is going to look like for us. >> The isolation era really taught us that if you're not a digital business, you're out of business, and pre COVID, a lot of these stories were kind of buried, but the companies that have invested in digital are now thriving. And this is an awesome example, and another point is that Jeff Hammerbacher, one of the founders of Cloudera, early Facebook employee, famously said about 10, 12 years ago, "The best and greatest engineering minds of my generation are trying to figure out how to get people to click on ads." And this is a wonderful example of how to use data to change people's lives. So guys, congratulations, best of luck, really awesome example of applying technology to create an important societal outcome. Really appreciate your time on theCUBE. Thank you. >> Bye-bye. >> All right, and thanks for watching this segment of theCUBE's presentation of the AWS Executive Summit at re:Invent 2021 made possible by Accenture. Keep it right there for more deep dives. (upbeat music)

to have Rodger Goodell fly to a tech conference to sit with you and then bring his team talk about the deal. >> Well, ya know, we've been partners with the NFL for a while with the Next Gen Stats that they use on all their telecasts and one of the things I really like about Roger is that he's very curious and very interested in technology and the first couple times I spoke with him he asked me so many questions about ways the NFL might be able to use the Cloud and digital transformation to transform their various experiences and he's always said if you have a creative idea or something you think that could change the world for us, just call me he said or text me or email me and I'll call you back within 24 hours. And so, we've spent the better part of the last year talking about a lot of really interesting, strategic ways that they can evolve their experience both for fans, as well as their players and the Player Health and Safety Initiative, it's so important in sports and particularly important with the NFL given the nature of the sport and they've always had a focus on it, but what you can do with computer vision and machine learning algorithms and then building a digital athlete which is really like a digital twin of each athlete so you understand, what does it look like when they're healthy and compare that when it looks like they may not be healthy and be able to simulate all kinds of different combinations of player hits and angles and different plays so that you could try to predict injuries and predict the right equipment you need before there's a problem can be really transformational so we're super excited about it. >> Did you guys come up with the idea or was it a collaboration between them? >> It was really a collaboration. I mean they, look, they are very focused on players safety and health and it's a big deal for their- you know, they have two main constituents the players and fans and they care deeply about the players and it's a-it's a hard problem in a sport like Football, I mean, you watch it. >> Yeah, and I got to say it does point out the use cases of what you guys are promoting heavily at the show here of the SageMaker Studio, which was a big part of your Keynote, where they have all this data. >> Andy: Right. >> And they're data hoarders, they hoard data but the manual process of going through the data was a killer problem. This is consistent with a lot of the enterprises that are out there, they have more data than they even know. So this seems to be a big part of the strategy. How do you get the customers to actually wake up to the fact that they got all this data and how do you tie that together? >> I think in almost every company they know they have a lot of data. And there are always pockets of people who want to do something with it. But, when you're going to make these really big leaps forward; these transformations, the things like Volkswagen is doing where they're reinventing their factories and their manufacturing process or the NFL where they're going to radically transform how they do players uh, health and safety. It starts top down and if the senior leader isn't convicted about wanting to take that leap forward and trying something different and organizing the data differently and organizing the team differently and using machine learning and getting help from us and building algorithms and building some muscle inside the company it just doesn't happen because it's not in the normal machinery of what most companies do. And so it always, almost always, starts top down. Sometimes it can be the Commissioner or CEO sometimes it can be the CIO but it has to be senior level conviction or it doesn't get off the ground. >> And the business model impact has to be real. For NFL, they know concussions, hurting their youth pipe-lining, this is a huge issue for them. the low level building blocks and stitch them together creatively however they see fit to create whatever's in their-in their heads. And then we have the second segment of customers that say look, I'm willing to give up some of that flexibility in exchange for getting 80% of the way there much faster.

>> Hi, my name is Andy Clemenko. I'm a Senior Solutions Engineer at StackRox. Thanks for joining us today for my talk on labels, labels, labels. Obviously, you can reach me at all the socials. Before we get started, I like to point you to my GitHub repo, you can go to andyc.info/dc20, and it'll take you to my GitHub page where I've got all of this documentation, socials. Before we get started, I like to point you to my GitHub repo, you can go to andyc.info/dc20, (upbeat music) >> Hi, my name is Andy Clemenko. I'm a Senior Solutions Engineer at StackRox. Thanks for joining us today for my talk on labels, labels, labels. Obviously, you can reach me at all the socials. Before we get started, I like to point you to my GitHub repo, you can go to andyc.info/dc20, and it'll take you to my GitHub page where I've got all of this documentation, I've got the Keynote file there. YAMLs, I've got Dockerfiles, Compose files, all that good stuff. If you want to follow along, great, if not go back and review later, kind of fun. So let me tell you a little bit about myself. I am a former DOD contractor. This is my seventh DockerCon. I've spoken, I had the pleasure to speak at a few of them, one even in Europe. I was even a Docker employee for quite a number of years, providing solutions to the federal government and customers around containers and all things Docker. So I've been doing this a little while. One of the things that I always found interesting was the lack of understanding around labels. So why labels, right? Well, as a former DOD contractor, I had built out a large registry. And the question I constantly got was, where did this image come from? How did you get it? What's in it? Where did it come from? How did it get here? And one of the things we did to kind of alleviate some of those questions was we established a baseline set of labels. Labels really are designed to provide as much metadata around the image as possible. I ask everyone in attendance, when was the last time you pulled an image and had 100% confidence, you knew what was inside it, where it was built, how it was built, when it was built, you probably didn't, right? The last thing we obviously want is a container fire, like our image on the screen. And one kind of interesting way we can kind of prevent that is through the use of labels. We can use labels to address security, address some of the simplicity on how to run these images. So think of it, kind of like self documenting, Think of it also as an audit trail, image provenance, things like that. These are some interesting concepts that we can definitely mandate as we move forward. What is a label, right? Specifically what is the Schema? It's just a key-value. All right? It's any key and pretty much any value. What if we could dump in all kinds of information? What if we could encode things and store it in there? And I've got a fun little demo to show you about that. Let's start off with some of the simple keys, right? Author, date, description, version. Some of the basic information around the image. That would be pretty useful, right? What about specific labels for CI? What about a, where's the version control? Where's the source, right? Whether it's Git, whether it's GitLab, whether it's GitHub, whether it's Gitosis, right? Even SPN, who cares? Where are the source files that built, where's the Docker file that built this image? What's the commit number? That might be interesting in terms of tracking the resulting image to a person or to a commit, hopefully then to a person. How is it built? What if you wanted to play with it and do a git clone of the repo and then build the Docker file on your own? Having a label specifically dedicated on how to build this image might be interesting for development work. Where it was built, and obviously what build number, right? These kind of all, not only talk about continuous integration, CI but also start to talk about security. Specifically what server built it. The version control number, the version number, the commit number, again, how it was built. What's the specific build number? What was that job number in, say, Jenkins or GitLab? What if we could take it a step further? What if we could actually apply policy enforcement in the build pipeline, looking specifically for some of these specific labels? I've got a good example of, in my demo of a policy enforcement. So let's look at some sample labels. Now originally, this idea came out of label-schema.org. And then it was a modified to opencontainers, org.opencontainers.image. There is a link in my GitHub page that links to the full reference. But these are some of the labels that I like to use, just as kind of like a standardization. So obviously, Author's, an email address, so now the image is attributable to a person, that's always kind of good for security and reliability. Where's the source? Where's the version control that has the source, the Docker file and all the assets? How it was built, build number, build server the commit, we talked about, when it was created, a simple description. A fun one I like adding in is the healthZendpoint. Now obviously, the health check directive should be in the Docker file. But if you've got other systems that want to ping your applications, why not declare it and make it queryable? Image version, obviously, that's simple declarative And then a title. And then I've got the two fun ones. Remember, I talked about what if we could encode some fun things? Hypothetically, what if we could encode the Compose file of how to build the stack in the first image itself? And conversely the Kubernetes? Well, actually, you can and I have a demo to show you how to kind of take advantage of that. So how do we create labels? And really creating labels as a function of build time okay? You can't really add labels to an image after the fact. The way you do add labels is either through the Docker file, which I'm a big fan of, because it's declarative. It's in version control. It's kind of irrefutable, especially if you're tracking that commit number in a label. You can extend it from being a static kind of declaration to more a dynamic with build arguments. And I can show you, I'll show you in a little while how you can use a build argument at build time to pass in that variable. And then obviously, if you did it by hand, you could do a docker build--label key equals value. I'm not a big fan of the third one, I love the first one and obviously the second one. Being dynamic we can take advantage of some of the variables coming out of version control. Or I should say, some of the variables coming out of our CI system. And that way, it self documents effectively at build time, which is kind of cool. How do we view labels? Well, there's two major ways to view labels. The first one is obviously a docker pull and docker inspect. You can pull the image locally, you can inspect it, you can obviously, it's going to output as JSON. So you going to use something like JQ to crack it open and look at the individual labels. Another one which I found recently was Skopeo from Red Hat. This allows you to actually query the registry server. So you don't even have to pull the image initially. This can be really useful if you're on a really small development workstation, and you're trying to talk to a Kubernetes cluster and wanting to deploy apps kind of in a very simple manner. Okay? And this was that use case, right? Using Kubernetes, the Kubernetes demo. One of the interesting things about this is that you can base64 encode almost anything, push it in as text into a label and then base64 decode it, and then use it. So in this case, in my demo, I'll show you how we can actually use a kubectl apply piped from the base64 decode from the label itself from skopeo talking to the registry. And what's interesting about this kind of technique is you don't need to store Helm charts. You don't need to learn another language for your declarative automation, right? You don't need all this extra levels of abstraction inherently, if you use it as a label with a kubectl apply, It's just built in. It's kind of like the kiss approach to a certain extent. It does require some encoding when you actually build the image, but to me, it doesn't seem that hard. Okay, let's take a look at a demo. And what I'm going to do for my demo, before we actually get started is here's my repo. Here's a, let me actually go to the actual full repo. So here's the repo, right? And I've got my Jenkins pipeline 'cause I'm using Jenkins for this demo. And in my demo flask, I've got the Docker file. I've got my compose and my Kubernetes YAML. So let's take a look at the Docker file, right? So it's a simple Alpine image. The org statements are the build time arguments that are passed in. Label, so again, I'm using the org.opencontainers.image.blank, for most of them. There's a typo there. Let's see if you can find it, I'll show you it later. My source, build date, build number, commit. Build number and get commit are derived from the Jenkins itself, which is nice. I can just take advantage of existing URLs. I don't have to create anything crazy. And again, I've got my actual Docker build command. Now this is just a label on how to build it. And then here's my simple Python, APK upgrade, remove the package manager, kind of some security stuff, health check getting Python through, okay? Let's take a look at the Jenkins pipeline real quick. So here is my Jenkins pipeline and I have four major stages, four stages, I have built. And here in build, what I do is I actually do the Git clone. And then I do my docker build. From there, I actually tell the Jenkins StackRox plugin. So that's what I'm using for my security scanning. So go ahead and scan, basically, I'm staging it to scan the image. I'm pushing it to Hub, okay? Where I can see the, basically I'm pushing the image up to Hub so such that my StackRox security scanner can go ahead and scan the image. I'm kicking off the scan itself. And then if everything's successful, I'm pushing it to prod. Now what I'm doing is I'm just using the same image with two tags, pre-prod and prod. This is not exactly ideal, in your environment, you probably want to use separate registries and non-prod and a production registry, but for demonstration purposes, I think this is okay. So let's go over to my Jenkins and I've got a deliberate failure. And I'll show you why there's a reason for that. And let's go down. Let's look at my, so I have a StackRox report. Let's look at my report. And it says image required, required image label alert, right? Request that the maintainer, add the required label to the image, so we're missing a label, okay? One of the things we can do is let's flip over, and let's look at Skopeo. Right? I'm going to do this just the easy way. So instead of looking at org.zdocker, opencontainers.image.authors. Okay, see here it says build signature? That was the typo, we didn't actually pass in. So if we go back to our repo, we didn't pass in the the build time argument, we just passed in the word. So let's fix that real quick. That's the Docker file. Let's go ahead and put our dollar sign in their. First day with the fingers you going to love it. And let's go ahead and commit that. Okay? So now that that's committed, we can go back to Jenkins, and we can actually do another build. And there's number 12. And as you can see, I've been playing with this for a little bit today. And while that's running, come on, we can go ahead and look at the Console output. Okay, so there's our image. And again, look at all the build arguments that we're passing into the build statement. So we're passing in the date and the date gets derived on the command line. With the build arguments, there's the base64 encoded of the Compose file. Here's the base64 encoding of the Kubernetes YAML. We do the build. And then let's go down to the bottom layer exists and successful. So here's where we can see no system policy violations profound marking stack regimes security plugin, build step as successful, okay? So we're actually able to do policy enforcement that that image exists, that that label sorry, exists in the image. And again, we can look at the security report and there's no policy violations and no vulnerabilities. So that's pretty good for security, right? We can now enforce and mandate use of certain labels within our images. And let's flip back over to Skopeo, and let's go ahead and look at it. So we're looking at the prod version again. And there's it is in my email address. And that validated that that was valid for that policy. So that's kind of cool. Now, let's take it a step further. What if, let's go ahead and take a look at all of the image, all the labels for a second, let me remove the dash org, make it pretty. Okay? So we have all of our image labels. Again, author's build, commit number, look at the commit number. It was built today build number 12. We saw that right? Delete, build 12. So that's kind of cool dynamic labels. Name, healthz, right? But what we're looking for is we're going to look at the org.zdockerketers label. So let's go look at the label real quick. Okay, well that doesn't really help us because it's encoded but let's base64 dash D, let's decode it. And I need to put the dash r in there 'cause it doesn't like, there we go. So there's my Kubernetes YAML. So why can't we simply kubectl apply dash f? Let's just apply it from standard end. So now we've actually used that label. From the image that we've queried with skopeo, from a remote registry to deploy locally to our Kubernetes cluster. So let's go ahead and look everything's up and running, perfect. So what does that look like, right? So luckily, I'm using traefik for Ingress 'cause I love it. And I've got an object in my Kubernetes YAML called flask.doctor.life. That's my Ingress object for traefik. I can go to flask.docker.life. And I can hit refresh. Obviously, I'm not a very good web designer 'cause the background image in the text. We can go ahead and refresh it a couple times we've got Redis storing a hit counter. We can see that our server name is roundrobing. Okay? That's kind of cool. So let's kind of recap a little bit about my demo environment. So my demo environment, I'm using DigitalOcean, Ubuntu 19.10 Vms. I'm using K3s instead of full Kubernetes either full Rancher, full Open Shift or Docker Enterprise. I think K3s has some really interesting advantages on the development side and it's kind of intended for IoT but it works really well and it deploys super easy. I'm using traefik for Ingress. I love traefik. I may or may not be a traefik ambassador. I'm using Jenkins for CI. And I'm using StackRox for image scanning and policy enforcement. One of the things to think about though, especially in terms of labels is none of this demo stack is required. You can be in any cloud, you can be in CentOs, you can be in any Kubernetes. You can even be in swarm, if you wanted to, or Docker compose. Any Ingress, any CI system, Jenkins, circle, GitLab, it doesn't matter. And pretty much any scanning. One of the things that I think is kind of nice about at least StackRox is that we do a lot more than just image scanning, right? With the policy enforcement things like that. I guess that's kind of a shameless plug. But again, any of this stack is completely replaceable, with any comparative product in that category. So I'd like to, again, point you guys to the andyc.infodc20, that's take you right to the GitHub repo. You can reach out to me at any of the socials @clemenko or andy@stackrox.com. And thank you for attending. I hope you learned something fun about labels. And hopefully you guys can standardize labels in your organization and really kind of take your images and the image provenance to a new level. Thanks for watching. (upbeat music) >> Narrator: Live from Las Vegas It's theCUBE. Covering AWS re:Invent 2019. Brought to you by Amazon Web Services and Intel along with it's ecosystem partners. >> Okay, welcome back everyone theCUBE's live coverage of AWS re:Invent 2019. This is theCUBE's 7th year covering Amazon re:Invent. It's their 8th year of the conference. I want to just shout out to Intel for their sponsorship for these two amazing sets. Without their support we wouldn't be able to bring our mission of great content to you. I'm John Furrier. Stu Miniman. We're here with the chief of AWS, the chief executive officer Andy Jassy. Tech athlete in and of himself three hour Keynotes. Welcome to theCUBE again, great to see you. >> Great to be here, thanks for having me guys. >> Congratulations on a great show a lot of great buzz. >> Andy: Thank you. >> A lot of good stuff. Your Keynote was phenomenal. You get right into it, you giddy up right into it as you say, three hours, thirty announcements. You guys do a lot, but what I liked, the new addition, the last year and this year is the band; house band. They're pretty good. >> Andy: They're good right? >> They hit the queen notes, so that keeps it balanced. So we're going to work on getting a band for theCUBE. >> Awesome. >> So if I have to ask you, what's your walk up song, what would it be? >> There's so many choices, it depends on what kind of mood I'm in. But, uh, maybe Times Like These by the Foo Fighters. >> John: Alright. >> These are unusual times right now. >> Foo Fighters playing at the Amazon Intersect Show. >> Yes they are. >> Good plug Andy. >> Headlining. >> Very clever >> Always getting a good plug in there. >> My very favorite band. Well congratulations on the Intersect you got a lot going on. Intersect is a music festival, I'll get to that in a second But, I think the big news for me is two things, obviously we had a one-on-one exclusive interview and you laid out, essentially what looks like was going to be your Keynote, and it was. Transformation- >> Andy: Thank you for the practice. (Laughter) >> John: I'm glad to practice, use me anytime. >> Yeah. >> And I like to appreciate the comments on Jedi on the record, that was great. But I think the transformation story's a very real one, but the NFL news you guys just announced, to me, was so much fun and relevant. You had the Commissioner of NFL on stage with you talking about a strategic partnership. That is as top down, aggressive goal as you could get to have Rodger Goodell fly to a tech conference to sit with you and then bring his team talk about the deal. >> Well, ya know, we've been partners with the NFL for a while with the Next Gen Stats that they use on all their telecasts and one of the things I really like about Roger is that he's very curious and very interested in technology and the first couple times I spoke with him he asked me so many questions about ways the NFL might be able to use the Cloud and digital transformation to transform their various experiences and he's always said if you have a creative idea or something you think that could change the world for us, just call me he said or text me or email me and I'll call you back within 24 hours. And so, we've spent the better part of the last year talking about a lot of really interesting, strategic ways that they can evolve their experience both for fans, as well as their players and the Player Health and Safety Initiative, it's so important in sports and particularly important with the NFL given the nature of the sport and they've always had a focus on it, but what you can do with computer vision and machine learning algorithms and then building a digital athlete which is really like a digital twin of each athlete so you understand, what does it look like when they're healthy and compare that when it looks like they may not be healthy and be able to simulate all kinds of different combinations of player hits and angles and different plays so that you could try to predict injuries and predict the right equipment you need before there's a problem can be really transformational so we're super excited about it. >> Did you guys come up with the idea or was it a collaboration between them? >> It was really a collaboration. I mean they, look, they are very focused on players safety and health and it's a big deal for their- you know, they have two main constituents the players and fans and they care deeply about the players and it's a-it's a hard problem in a sport like Football, I mean, you watch it. >> Yeah, and I got to say it does point out the use cases of what you guys are promoting heavily at the show here of the SageMaker Studio, which was a big part of your Keynote, where they have all this data. >> Andy: Right. >> And they're data hoarders, they hoard data but the manual process of going through the data was a killer problem. This is consistent with a lot of the enterprises that are out there, they have more data than they even know. So this seems to be a big part of the strategy. How do you get the customers to actually wake up to the fact that they got all this data and how do you tie that together? >> I think in almost every company they know they have a lot of data. And there are always pockets of people who want to do something with it. But, when you're going to make these really big leaps forward; these transformations, the things like Volkswagen is doing where they're reinventing their factories and their manufacturing process or the NFL where they're going to radically transform how they do players uh, health and safety. It starts top down and if the senior leader isn't convicted about wanting to take that leap forward and trying something different and organizing the data differently and organizing the team differently and using machine learning and getting help from us and building algorithms and building some muscle inside the company it just doesn't happen because it's not in the normal machinery of what most companies do. And so it always, almost always, starts top down. Sometimes it can be the Commissioner or CEO sometimes it can be the CIO but it has to be senior level conviction or it doesn't get off the ground. >> And the business model impact has to be real. For NFL, they know concussions, hurting their youth pipe-lining, this is a huge issue for them. This is their business model. >> They lose even more players to lower extremity injuries. And so just the notion of trying to be able to predict injuries and, you know, the impact it can have on rules and the impact it can have on the equipment they use, it's a huge game changer when they look at the next 10 to 20 years. >> Alright, love geeking out on the NFL but Andy, you know- >> No more NFL talk? >> Off camera how about we talk? >> Nobody talks about the Giants being 2 and 10. >> Stu: We're both Patriots fans here. >> People bring up the undefeated season. >> So Andy- >> Everybody's a Patriot's fan now. (Laughter) >> It's fascinating to watch uh, you and your three hour uh, Keynote, uh Werner in his you know, architectural discussion, really showed how AWS is really extending its reach, you know, it's not just a place. For a few years people have been talking about you know, Cloud is an operational model its not a destination or a location but, I felt it really was laid out is you talked about Breadth and Depth and Werner really talked about you know, Architectural differentiation. People talk about Cloud, but there are very-there are a lot of differences between the vision for where things are going. Help us understand why, I mean, Amazon's vision is still a bit different from what other people talk about where this whole Cloud expansion, journey, put ever what tag or label you want on it but you know, the control plane and the technology that you're building and where you see that going. >> Well I think that, we've talked about this a couple times we have two macro types of customers. We have those that really want to get at the low level building blocks and stitch them together creatively however they see fit to create whatever's in their-in their heads. And then we have the second segment of customers that say look, I'm willing to give up some of that flexibility in exchange for getting 80% of the way there much faster. In an abstraction that's different from those low level building blocks. And both segments of builders we want to serve and serve well and so we've built very significant offerings in both areas. I think when you look at microservices um, you know, some of it has to do with the fact that we have this very strongly held belief born out of several years of Amazon where you know, the first 7 or 8 years of Amazon's consumer business we basically jumbled together all of the parts of our technology in moving really quickly and when we wanted to move quickly where you had to impact multiple internal development teams it was so long because it was this big ball, this big monolithic piece. And we got religion about that in trying to move faster in the consumer business and having to tease those pieces apart. And it really was a lot of impetus behind conceiving AWS where it was these low level, very flexible building blocks that6 don't try and make all the decisions for customers they get to make them themselves. And some of the microservices that you saw Werner talking about just, you know, for instance, what we-what we did with Nitro or even what we did with Firecracker those are very much about us relentlessly working to continue to uh, tease apart the different components. And even things that look like low level building blocks over time, you build more and more features and all of the sudden you realize they have a lot of things that are combined together that you wished weren't that slow you down and so, Nitro was a completely re imagining of our Hypervisor and Virtualization layer to allow us, both to let customers have better performance but also to let us move faster and have a better security story for our customers. >> I got to ask you the question around transformation because I think that all points, all the data points, you got all the references, Goldman Sachs on stage at the Keynote, Cerner, I mean healthcare just is an amazing example because I mean, that's demonstrating real value there there's no excuse. I talked to someone who wouldn't be named last night, in and around the area said, the CIA has a cost bar like this a cost-a budget like this but the demand for mission based apps is going up exponentially, so there's need for the Cloud. And so, you see more and more of that. What is your top down, aggressive goals to fill that solution base because you're also a very transformational thinker; what is your-what is your aggressive top down goals for your organization because you're serving a market with trillions of dollars of spend that's shifting, that's on the table. >> Yeah. >> A lot of competition now sees it too, they're going to go after it. But at the end of the day you have customers that have a demand for things, apps. >> Andy: Yeah. >> And not a lot of budget increase at the same time. This is a huge dynamic. >> Yeah. >> John: What's your goals? >> You know I think that at a high level our top down aggressive goals are that we want every single customer who uses our platform to have an outstanding customer experience. And we want that outstanding customer experience in part is that their operational performance and their security are outstanding, but also that it allows them to build, uh, build projects and initiatives that change their customer experience and allow them to be a sustainable successful business over a long period of time. And then, we also really want to be the technology infrastructure platform under all the applications that people build. And we're realistic, we know that you know, the market segments we address with infrastructure, software, hardware, and data center services globally are trillions of dollars in the long term and it won't only be us, but we have that goal of wanting to serve every application and that requires not just the security operational premise but also a lot of functionality and a lot of capability. We have by far the most amount of capability out there and yet I would tell you, we have 3 to 5 years of items on our roadmap that customers want us to add. And that's just what we know today. >> And Andy, underneath the covers you've been going through some transformation. When we talked a couple of years ago, about how serverless is impacting things I've heard that that's actually, in many ways, glue behind the two pizza teams to work between organizations. Talk about how the internal transformations are happening. How that impacts your discussions with customers that are going through that transformation. >> Well, I mean, there's a lot of- a lot of the technology we build comes from things that we're doing ourselves you know? And that we're learning ourselves. It's kind of how we started thinking about microservices, serverless too, we saw the need, you know, we would have we would build all these functions that when some kind of object came into an object store we would spin up, compute, all those tasks would take like, 3 or 4 hundred milliseconds then we'd spin it back down and yet, we'd have to keep a cluster up in multiple availability zones because we needed that fault tolerance and it was- we just said this is wasteful and, that's part of how we came up with Lambda and you know, when we were thinking about Lambda people understandably said, well if we build Lambda and we build this serverless adventure in computing a lot of people were keeping clusters of instances aren't going to use them anymore it's going to lead to less absolute revenue for us. But we, we have learned this lesson over the last 20 years at Amazon which is, if it's something that's good for customers you're much better off cannibalizing yourself and doing the right thing for customers and being part of shaping something. And I think if you look at the history of technology you always build things and people say well, that's going to cannibalize this and people are going to spend less money, what really ends up happening is they spend less money per unit of compute but it allows them to do so much more that they ultimately, long term, end up being more significant customers. >> I mean, you are like beating the drum all the time. Customers, what they say, we encompass the roadmap, I got that you guys have that playbook down, that's been really successful for you. >> Andy: Yeah. >> Two years ago you told me machine learning was really important to you because your customers told you. What's the next traunch of importance for customers? What's on top of mind now, as you, look at- >> Andy: Yeah. >> This re:Invent kind of coming to a close, Replay's tonight, you had conversations, you're a tech athlete, you're running around, doing speeches, talking to customers. What's that next hill from if it's machine learning today- >> There's so much I mean, (weird background noise) >> It's not a soup question (Laughter) And I think we're still in the very early days of machine learning it's not like most companies have mastered it yet even though they're using it much more then they did in the past. But, you know, I think machine learning for sure I think the Edge for sure, I think that um, we're optimistic about Quantum Computing even though I think it'll be a few years before it's really broadly useful. We're very um, enthusiastic about robotics. I think the amount of functions that are going to be done by these- >> Yeah. >> robotic applications are much more expansive than people realize. It doesn't mean humans won't have jobs, they're just going to work on things that are more value added. We're believers in augmented virtual reality, we're big believers in what's going to happen with Voice. And I'm also uh, I think sometimes people get bored you know, I think you're even bored with machine learning already >> Not yet. >> People get bored with the things you've heard about but, I think just what we've done with the Chips you know, in terms of giving people 40% better price performance in the latest generation of X86 processors. It's pretty unbelievable in the difference in what people are going to be able to do. Or just look at big data I mean, big data, we haven't gotten through big data where people have totally solved it. The amount of data that companies want to store, process, analyze, is exponentially larger than it was a few years ago and it will, I think, exponentially increase again in the next few years. You need different tools and services. >> Well I think we're not bored with machine learning we're excited to get started because we have all this data from the video and you guys got SageMaker. >> Andy: Yeah. >> We call it the stairway to machine learning heaven. >> Andy: Yeah. >> You start with the data, move up, knock- >> You guys are very sophisticated with what you do with technology and machine learning and there's so much I mean, we're just kind of, again, in such early innings. And I think that, it was so- before SageMaker, it was so hard for everyday developers and data scientists to build models but the combination of SageMaker and what's happened with thousands of companies standardizing on it the last two years, plus now SageMaker studio, giant leap forward. >> Well, we hope to use the data to transform our experience with our audience. And we're on Amazon Cloud so we really appreciate that. >> Andy: Yeah. >> And appreciate your support- >> Andy: Yeah, of course. >> John: With Amazon and get that machine learning going a little faster for us, that would be better. >> If you have requests I'm interested, yeah. >> So Andy, you talked about that you've got the customers that are builders and the customers that need simplification. Traditionally when you get into the, you know, the heart of the majority of adoption of something you really need to simplify that environment. But when I think about the successful enterprise of the future, they need to be builders. how'l I normally would've said enterprise want to pay for solutions because they don't have the skill set but, if they're going to succeed in this new economy they need to go through that transformation >> Andy: Yeah. >> That you talk to, so, I mean, are we in just a total new era when we look back will this be different than some of these previous waves? >> It's a really good question Stu, and I don't think there's a simple answer to it. I think that a lot of enterprises in some ways, I think wish that they could just skip the low level building blocks and only operate at that higher level abstraction. That's why people were so excited by things like, SageMaker, or CodeGuru, or Kendra, or Contact Lens, these are all services that allow them to just send us data and then run it on our models and get back the answers. But I think one of the big trends that we see with enterprises is that they are taking more and more of their development in house and they are wanting to operate more and more like startups. I think that they admire what companies like AirBnB and Pintrest and Slack and Robinhood and a whole bunch of those companies, Stripe, have done and so when, you know, I think you go through these phases and eras where there are waves of success at different companies and then others want to follow that success and replicate it. And so, we see more and more enterprises saying we need to take back a lot of that development in house. And as they do that, and as they add more developers those developers in most cases like to deal with the building blocks. And they have a lot of ideas on how they can creatively stich them together. >> Yeah, on that point, I want to just quickly ask you on Amazon versus other Clouds because you made a comment to me in our interview about how hard it is to provide a service to other people. And it's hard to have a service that you're using yourself and turn that around and the most quoted line of my story was, the compression algorithm- there's no compression algorithm for experience. Which to me, is the diseconomies of scale for taking shortcuts. >> Andy: Yeah. And so I think this is a really interesting point, just add some color commentary because I think this is a fundamental difference between AWS and others because you guys have a trajectory over the years of serving, at scale, customers wherever they are, whatever they want to do, now you got microservices. >> Yeah. >> John: It's even more complex. That's hard. >> Yeah. >> John: Talk about that. >> I think there are a few elements to that notion of there's no compression algorithm for experience and I think the first thing to know about AWS which is different is, we just come from a different heritage and a different background. We ran a business for a long time that was our sole business that was a consumer retail business that was very low margin. And so, we had to operate at very large scale given how many people were using us but also, we had to run infrastructure services deep in the stack, compute storage and database, and reliable scalable data centers at very low cost and margins. And so, when you look at our business it actually, today, I mean its, its a higher margin business in our retail business, its a lower margin business in software companies but at real scale, it's a high volume, relatively low margin business. And the way that you have to operate to be successful with those businesses and the things you have to think about and that DNA come from the type of operators we have to be in our consumer retail business. And there's nobody else in our space that does that. So, you know, the way that we think about costs, the way we think about innovation in the data center, um, and I also think the way that we operate services and how long we've been operating services as a company its a very different mindset than operating package software. Then you look at when uh, you think about some of the uh, issues in very large scale Cloud, you can't learn some of those lessons until you get to different elbows of the curve and scale. And so what I was telling you is, its really different to run your own platform for your own users where you get to tell them exactly how its going to be done. But that's not the way the real world works. I mean, we have millions of external customers who use us from every imaginable country and location whenever they want, without any warning, for lots of different use cases, and they have lots of design patterns and we don't get to tell them what to do. And so operating a Cloud like that, at a scale that's several times larger than the next few providers combined is a very different endeavor and a very different operating rigor. >> Well you got to keep raising the bar you guys do a great job, really impressed again. Another tsunami of announcements. In fact, you had to spill the beans earlier with Quantum the day before the event. Tight schedule. I got to ask you about the musical festival because, I think this is a very cool innovation. It's the inaugural Intersect conference. >> Yes. >> John: Which is not part of Replay, >> Yes. >> John: Which is the concert tonight. Its a whole new thing, big music act, you're a big music buff, your daughter's an artist. Why did you do this? What's the purpose? What's your goal? >> Yeah, it's an experiment. I think that what's happened is that re:Invent has gotten so big, we have 65 thousand people here, that to do the party, which we do every year, its like a 35-40 thousand person concert now. Which means you have to have a location that has multiple stages and, you know, we thought about it last year and when we were watching it and we said, we're kind of throwing, like, a 4 hour music festival right now. There's multiple stages, and its quite expensive to set up that set for a party and we said well, maybe we don't have to spend all that money for 4 hours and then rip it apart because actually the rent to keep those locations for another two days is much smaller than the cost of actually building multiple stages and so we thought we would try it this year. We're very passionate about music as a business and I think we-I think our customers feel like we've thrown a pretty good music party the last few years and we thought we would try it at a larger scale as an experiment. And if you look at the economics- >> At the headliners real quick. >> The Foo Fighters are headlining on Saturday night, Anderson Paak and the Free Nationals, Brandi Carlile, Shawn Mullins, um, Willy Porter, its a good set. Friday night its Beck and Kacey Musgraves so it's a really great set of um, about thirty artists and we're hopeful that if we can build a great experience that people will want to attend that we can do it at scale and it might be something that both pays for itself and maybe, helps pay for re:Invent too overtime and you know, I think that we're also thinking about it as not just a music concert and festival the reason we named it Intersect is that we want an intersection of music genres and people and ethnicities and age groups and art and technology all there together and this will be the first year we try it, its an experiment and we're really excited about it. >> Well I'm gone, congratulations on all your success and I want to thank you we've been 7 years here at re:Invent we've been documenting the history. You got two sets now, one set upstairs. So appreciate you. >> theCUBE is part of re:Invent, you know, you guys really are apart of the event and we really appreciate your coming here and I know people appreciate the content you create as well. >> And we just launched CUBE365 on Amazon Marketplace built on AWS so thanks for letting us- >> Very cool >> John: Build on the platform. appreciate it. >> Thanks for having me guys, I appreciate it. >> Andy Jassy the CEO of AWS here inside theCUBE, it's our 7th year covering and documenting the thunderous innovation that Amazon's doing they're really doing amazing work building out the new technologies here in the Cloud computing world. I'm John Furrier, Stu Miniman, be right back with more after this short break. (Outro music)

(upbeat electronic music) >> Narrator: From theCUBE studios in Palo Alto and Boston, connecting with thought leaders all around the world, this is a CUBE conversation! >> Hi, I'm Stu Miniman, your host for Cloud Native Insight. When we launched this series, one of the things we wanted to talk about was that we're not just using cloud as a destination, but really enabling new ways of thinking, being able to use the innovations underneath the cloud, and that if you use services in the cloud, that you're not necessarily locked into a solution or can't move forward. And that's why I'm really excited to help welcome to the program, I have the co-founders of Vendia. First we have Dr. Tim Wagner, he is the co-founder and CEO of the company, as well as generally known in the industry as the father of Serverless from the AWS Lambda, and his co-founder, Shruthi Rao, she is the chief business officer at Vendia, also came from AWS where she worked on blockchain solutions. Tim, Shruthi, thanks so much for joining us. >> Thanks for having us in here, Stu. Great to join the show. >> All right, so Shruthi, actually if we could start with you because before we get into Vendia, coming out of stealth, you know, really interesting technology space, you and Tim both learned a lot from working with customers in your previous jobs, why don't we start from you. Block chain of course had a lot of learnings, a lot of things that people don't understand about what it is and what it isn't, so give us a little bit about what you've learned and how that lead towards what you and Tim and the team are doing with Vendia. >> Yeah, absolutely, Stu! One, the most important thing that we've all heard of was this great gravitational pull towards blockchain in 2018 and 2019. Well, I was one of the founders and early adopters of blockchain from Bitcoin and Ethereum space, all the way back from 2011 and onwards. And at AWS I started the Amazon Managed Blockchain and launched Quantum Ledger Database, two services in the block chain category. What I learned there was, no surprise, there was a gold rush to blockchain from many customers. We, I personally talked to over 1,092 customers when I ran Amazon Managed Blockchain for the last two years. And I found that customers were looking at solving this dispersed data problem. Most of my customers had invested in IoT and edge devices, and these devices were gathering massive amounts of data, and on the flip side they also had invested quite a bit of effort in AI and ML and analytics to crunch this data, give them intelligence. But guess what, this data existed in multiple parties, in multiple clouds, in multiple technology stacks, and they needed a mechanism to get this data from wherever they were into one place so they could the AI, ML, analytics investment, and they wanted all of this to be done in real time, and to gravitated towards blockchain. But blockchain had quite a bit of limitations, it was not scalable, it didn't work with the existing stack that you had. It forced enterprises to adopt this new technology and entirely new type of infrastructure. It didn't work cross-cloud unless you hired expensive consultants or did it yourself, and required these specialized developers. For all of these reasons, we've seen many POCs, majority of POCs just dying on the vine and not ever reaching the production potential. So, that is when I realized that what the problem to be solved was not a trust problem, the problem was dispersed data in multiple clouds and multiple stacks problem. Sometimes multiple parties, even, problem. And that's when Tim and I started talking about, about how can we bring all of the nascent qualities of Lambda and Serverless and use all of the features of blockchain and build something together? And he has an interesting story on his own, right. >> Yeah. Yeah, Shruthi, if I could, I'd like to get a little bit of that. So, first of all for our audience, if you're watching this on the minute, probably want to hit pause, you know, go search Tim, go watch a video, read his Medium post, about the past, present, and future of Serverless. But Tim, I'm excited. You and I have talked in the past, but finally getting you on theCUBE program. >> Yeah! >> You know, I've looked through my career, and my background is infrastructure, and the role of infrastructure we know is always just to support the applications and the data that run business, that's what is important! Even when you talk about cloud, it is the applications, you know, the code, and the data that are important. So, it's not that, you know, okay I've got near infinite compute capacity, it's the new things that I can do with it. That's a comment I heard in one of your sessions. You talked about one of the most fascinating things about Serverless was just the new creativity that it inspired people to do, and I loved it wasn't just unlocking developers to say, okay I have new ways to write things, but even people that weren't traditional coders, like lots of people in marketing that were like, "I can start with this and build something new." So, I guess the question I have for you is, you know we had this idea of Platform as a Service, or even when things like containers launched, it was, we were trying to get close to that atomic unit of the application, and often it was talked about, well, do I want it for portability? Is it for ease of use? So, you've been wrangling and looking at this (Tim laughing) from a lot of different ways. So, is that as a starting point, you know, what did you see the last few years with Lambda, and you know, help connect this up to where Shruthi just left off her bit of the story. >> Absolutely. You know, the great story, the great success of the cloud is this elimination of undifferentiated heavy lifting, you know, from getting rid of having to build out a data center, to all the complexity of managing hardware. And that first wave of cloud adoption was just phenomenally successful at that. But as you say, the real thing businesses wrestle with are applications, right? It's ultimately about the business solution, not the hardware and software on which it runs. So, the very first time I sat down with Andy Jassy to talk about what eventually become Lambda, you know, one of the things I said was, look, if we want to get 10x the number of people to come and, you know, and be in the cloud and be successful it has to be 10 times simpler than it is today. You know, if step one is hire an amazing team of distributed engineers to turn a server into a full tolerance, scalable, reliable business solution, now that's going to be fundamentally limiting. We have to find a way to put that in a box, give that capability, you know, to people, without having them go hire that and build that out in the first place. And so that kind of started this journey for, for compute, we're trying to solve the problem of making compute as easy to use as possible. You know, take some code, as you said, even if you're not a diehard programmer or backend engineer, maybe you're just a full-stack engineer who loves working on the front-end, but the backend isn't your focus, turn that into something that is as scalable, as robust, as secure as somebody who has spent their entire career working on that. And that was the promise of Serverless, you know, outside of the specifics of any one cloud. Now, the challenge of course when you talk to customers, you know, is that you always heard the same two considerations. One is, I love the idea of Lamdba, but it's AWS, maybe I have multiple departments or business partners, or need to kind of work on multiple clouds. The other challenge is fantastic for compute, what about data? You know, you've kind of left me with, you're giving me sort of half the solution, you've made my compute super easy to use, can you make my data equally easy to use? And so you know, obviously the part of the genesis of Vendia is going and tackling those pieces of this, giving all that promise and ease of use of Serverless, now with a model for replicated state and data, and one that can cross accounts, machines, departments, clouds, companies, as easily as it scales on a single cloud today. >> Okay, so you covered quite a bit of ground there Tim, if you could just unpack that a little bit, because you're talking about state, cutting across environments. What is it that Vendia is bringing, how does that tie into solutions like, you know, Lamdba as you mentioned, but other clouds or even potentially on premises solutions? So, what is, you know, the IP, the code, the solution that Vendia's offering? >> Happy to! So, let's start with the customer problem here. The thing that every enterprise, every company, frankly, wrestles with is in the modern world they're producing more data than ever, IMT, digital journeys, you know, mobile, edge devices. More data coming in than ever before, at the same time, more data getting consumed than ever before with deep analytics, supply chain optimization, AI, ML. So, even more consumers of ever more data. The challenge, of course, is that data isn't always inside a company's four walls. In fact, we've heard 80% or more of that data actually lives outside of a company's control. So, step one to doing something like AI, ML, isn't even just picking a product or selecting a technology, it's getting all of your data back together again, so that's the problem that we set out to solve with Vendia, and we realized that, you know, and kind of part of the genesis for the name here, you know, Vendia comes from Venn Diagram. So, part of that need to bring code and data together across companies, across tech stacks, means the ability to solve some of these long-standing challenges. And we looked at the two sort of big movements out there. Two of them, you know, we've obviously both been involved in, one of them was Serverless, which amazing ability to scale, but single account, single cloud, single company. The other one is blockchain and distributed ledgers, manages to run more across parties, across clouds, across tech stacks, but doesn't have a great mechanism for scalability, it's really a single box deployment model, and obviously there are a lot of limitations with that. So, our technology, and kind of our insight and breakthrough here was bringing those two things together by solving the problems in each of them with the best parts of the other. So, reimagine the blockchain as a cloud data implementation built entirely out of Serverless components that have all of the scale, the cost efficiencies, the high utilization, like all of the ease of deployment that something like Lambda has today, and at the same time, you know, bring state to Serverless. Give things like Lambda and the equivalent of other clouds a simple, easy, built-in model so that applications can have multicloud, multi-account state at all times, rather than turning that into a complicated DIY project. So, that was our insight here, you know and frankly where a lot of the interesting technology for us is in turning those centralized services, a centralized version of Serverless Compute or Serverless Database into a multi-account, multicloud experience. And so that's where we spent a lot of time and energy trying to build something that gives customers a great experience. >> Yeah, so I've got plenty of background in customers that, you know, have the "information silos", if you will, so we know, when the unstructured data, you know so much of it is not searchable, I can't leverage it. Shruthi, but maybe it might make sense, you know, what is, would you say some of the top things some of your early customers are saying? You know, I have this pain point, that's pointing me in your direction, what was leading them to you? And how does the solution help them solve that problem? >> Yeah, absolutely! One of our design partners, our lead design partners is this automotive company, they're a premier automotive company, they want, their end goal is to track car parts for warranty recall issues. So, they want to track every single part that goes into a particular car, so they're about 30 to 35,000 parts in each of these cars, and then all the way from manufacturing floor to when the car is sold, and when that particular part is replaced eventually, towards the end of the lifecycle of that part. So for this, they have put together a small test group of their partners, a couple of the parts manufacturers, they're second care partners, National Highway Safety Administration is part of this group, also a couple of dealers and service centers. Now, if you just look at this group of partners, you will see some of these parties have high technology, technology backgrounds, just like the auto manufacturers themselves or the part manufacturers. Low modality or low IT-competency partners such as the service centers, for them desktop PCs are literally the IT competency, and so does the service centers. Now, most of, majority of these are on multiple clouds. This particular auto customer is on AWS and manufactures on Azure, another one is on GCP. Now, they all have to share these large files between each other, making sure that there are some transparency and business rules applicable. For example, two partners who make the same parts or similar parts cannot see each other's data. Most of the participants cannot see the PII data that are not applicable, only the service center can see that. National Highway Safety Administration has read access, not write access. A lot of that needed to be done, and their alternatives before they started using Vendia was either use point-to-point APIs, which was very expensive, very cumbersome, it works for a finite small set of parties, it does not scale, as in when you add more participants into this particular network. And the second option for them was blockchain, which they did use, and used Hyperledger Fabric, they used Ethereum Private to see how this works, but the scalability, with Ethereum Private, it's about 14 to 15 transactions per second, with Hyperledger Fabric it taps out at 100, or 150 on a good day, transaction through, but it's not just useful. All of these are always-on systems, they're not Serverless, so just provisioning capacity, our customers said it took them two to three weeks per participant. So, it's just not a scalable solution. With Vendia, what we delivered to them was this virtual data lake, where the sources of this data are on multiple clouds, are on multiple accounts owned by multiple parties, but all of that data is shared on a virtual data lake with all of the permissions, with all of the logging, with all of the security, PII, and compliance. Now, this particular auto manufacturer and the National Highway Safety Administration can run their ML algorithms to gain intelligence off of it, and start to understand patterns, so when certain parts go bad, or what's the propensity of a certain manufacturing unit producing faulty parts, and so on, and so forth. This really shows you this concept of unstructured data being shared between parties that are not, you know, connected with each other, when there are data silos. But I'd love to follow this up with another example of, you know, the democratization, democratization is very important to Vendia. When Tim launched Lambda and founded the AWS Serverless movement as a whole, and at AWS, one thing, very important thing happened, it lowered the barrier to entry for a new wave of businesses that could just experiment, try out new things, if it failed, they scrap it, if it worked, they could scale it out. And that was possible because of the entry point, because of the paper used, and the architecture itself, and we are, our vision and mission for Vendia is that Vendia fuels the next generation of multi-party connected distributed applications. My second design partner is actually a non-profit that, in the animal welfare industry. Their mission is to maintain a no-kill for dogs and cats in the United States. And the number one reason for over populations of dogs and cats in the shelters is dogs lost, dogs and cats lost during natural disasters, like the hurricane season. And when that happens, and when, let's say your dogs get lost, and you want to find a dog, the ID or the chip-reading is not reliable, they want to search this through pictures. But we also know that if you look at a picture of a dog, four people can come up with four different breed names, and this particular non-profit has 2,500 plus partners across the U.S., and they're all low to no IT modalities, some of them have higher IT competency, and a huge turnover because of volunteer employees. So, what we did for them was came up with a mechanism where they could connect with all 2,500 of these participants very easily in a very cost-effective way and get all of the pictures of all of the dogs in all these repositories into one data lake so they can run some kind of a dog facial recognition algorithm on it and identify where my lost dog is in minutes as opposed to days it used to take before. So, you see a very large customer with very sophisticated IT competency use this, also a non-profit being able to use this. And they were both able to get to this outcome in days, not months or years, as, blockchain, but just under a few days, so we're very excited about that. >> Thank you so much for the examples. All right, Tim, before we get to the end, I wonder if you could take us under the hood a little bit here. My understanding, the solution that you talk about, it's universal apps, or what you call "unis" -- >> Tim: Unis? (laughs) >> I believe, so if I saw that right, give me a little bit of compare and contrast, if you will. Obviously there's been a lot of interest in what Kubernetes has been doing. We've been watching closely, you know there's connections between what Kubernetes is doing and Serverless with the Knative project. When I saw the first video talking about Vendia, you said, "We're serverless, and we're containerless underneath." So, help us understand, because at, you know, a super high level, some of the multicloud and making things very flexible sound very similar. So you know, how is Vendia different, and why do you feel your architecture helps solve this really challenging problem? >> Sure, sure, awesome! You know, look, one of the tenets that we had here was that things have to be as easy as possible for customers, and if you think about the way somebody walks up today to an existing database system, right? They say, "Look, I've got a schema, I know the shape of my data." And a few minutes later I can get a production database, now it's single user, single cloud, single consumer there, but it's a very fast, simple process that doesn't require having code, hiring a team, et cetera, and we wanted Vendia to work the same way. Somebody can walk up with a JSON schema, hand it to us, five minutes later they have a database, only now it's a multiparty database that's decentralized, so runs across multiple platforms, multiple clouds, you know, multiple technology stacks instead of being single user. So, that's kind of goal one, is like make that as easy to use as possible. The other key tenet though is we don't want to be the least common denominator of the cloud. One of the challenges with saying everyone's going to deploy their own servers, they're going to run all their own software, they're going to build, you know, they're all going to co-deploy a Kubernetes cluster, one of the challenges with that is that, as Shruthi was saying, first, anyone for whom that's a challenge, if you don't have a whole IT department wrapped around you that's a difficult proposition to get started on no matter how amazing that technology might be. The other challenge with it though is that it locks you out, sort of the universe of a lock-in process, right, is the lock-out process. It locks you out of some of the best and brightest things the public cloud providers have come up with, and we wanted to empower customers, you know, to pick the best degree. Maybe they want to go use IBM Watson, maybe they want to use a database on Google, and at the same time they want to ingest IoT on AWS, and they wanted all to work together, and want all of that to be seamless, not something where they have to recreate an experience over, and over, and over again on three different clouds. So, that was our goal here in producing this. What we designed as an architecture was decentralized data storage at the core of it. So, think about all the precepts you hear with blockchain, they're all there, they all just look different. So, we use a no SQL database to store data so that we can scale that easily. We still have a consensus algorithm, only now it's a high speed serverless and cloud function based mechanism. You know, instead of smart contracts, you write things in a cloud function like Lambda instead, so no more learning Solidity, now you can use any language you want. So, we changed how we think about that architecture, but many of those ideas about people, really excited about blockchain and its capabilities and the vision for the future are still alive and well, they've just been implemented in a way that's far more practical and effective for the enterprise. >> All right, so what environments can I use today for your solution, Shruthi talked about customers spanning across some of the cloud, so what's available kind of today, what's on the roadmap in the future? Will this include beyond, you know, maybe the top five or six hyper scalers? Can I do, does it just require Serverless underneath? So, will things that are in a customer's own data center eventually support that. >> Absolutely. So, what we're doing right now is having people sign up for our preview release, so in the next few weeks, we're going to start turning that on for early access to developers. That'll be, the early access program, will be multi-account, focused on AWS, and then end of summer, well be doing our GA release, which will be multicloud, so we'll actually be able to operate across multiple clouds, multiple cloud services, on different platforms. But even from day one, we'll have API support in there. So, if you got a service, could even be running on a mainframe, could be on-prem, if it's API based you can still interact with the data, and still get the benefits of the system. So, developers, please start signing up, you can go find more information on vendia.net, and we're really looking forward to getting some of that early feedback and hear more from the people that we're the most excited to have start building these projects. >> Excellent, what a great call to action to get the developers and users in there. Shruthi, if you could just give us the last bit, you know, the thing that's been fascinating, Tim, when I look at the Serverless movement, you know, I've talked to some amazing companies that were two or three people (Tim laughing) and out of their basement, and they created a business, and they're like, "Oh my gosh, I got VC funding, and it's usually sub $10,000,000. So, I look at your team, I'd heard, Tim, you're the primary coder on the team. (Tim laughing) And when it comes to the seed funding it's, you know, compared to many startups, it's a small number. So, Shruthi, give us a little bit if you could the speeds and feeds of the company, your funding, and any places that you're hiring. Yeah, we are definitely hiring, lets me start from there! (Tim laughing) We're hiring for developers, and we are also hiring for solution architects, so please go to vendia.net, we have all the roles listed there, we would love to hear from you! And the second one, funding, yes. Tim is our main developer and solutions architect here, and look, the Serverless movement really helped quite a few companies, including us, to build this, bring this to market in record speeds, and we're very thankful that Tim and AWS started taking the stands, you know back in 2014, 2013, to bring this to market and democratize this. I think when we brought this new concept to our investors, they saw what this could be. It's not an easy concept to understand in the first wave, but when you understand the problem space, you see that the opportunity is pretty endless. And I'll say this for our investors, on behalf of our investors, that they saw a real founder market-fit between us. We're literally the two people who have launched and ran businesses for both Serverless and blockchain at scale, so that's what they thought was very attractive to them, and then look, it's Tim and I, and we're looking to hire 8 to 10 folks, and I think we have gotten to a space where we're making a meaningful difference to the world, and we would love for more people to join us, join this movement and democratize this big dispersed data problem and solve for this. And help us create more meanings to the data that our customers and companies worldwide are creating. We're very excited, and we're very thankful for all of our investors to be deeply committed to us and having conviction on us. >> Well, Shruthi and Tim, first of all, congratulations -- >> Thank you, thank you. >> Absolutely looking forward to, you know, watching the progress going forward. Thanks so much for joining us. >> Thank you, Stu, thank you. >> Thanks, Stu! >> All right, and definitely tune in to our regular conversations on Cloud Native Insights. I'm your host Stu Miniman, and looking forward to hearing more about your Cloud Native Insights! (upbeat electronic music)

>>from around the globe. It's the queue with digital coverage of women transforming technology brought to you by VM Ware. >>Hi, Lisa Martin covering the fifth annual Women Transforming Technology event the first time it has been running in. So we're not coming to you from Palo Alto today coming to you from San Jose that I'm really excited to be talking with one of the event speakers, the founder of Happier Inc. Natalie Kogan. Natalie, Welcome to the Cube. Thanks so much for having me great to join you, even virtually. Exactly. And we're so fortunate that this I guess, if you can, if you can put a positive spin on it that this event happened when we have technology to still be able to enable as much interaction into a conversations or multiple way conversations as possible. And I know that you just did a session and a couple of days ago at the Digital Women transforming Allergy then But before we get into that, I saw your Ted talk was awesome and it's it's such a and the timeliness happier as a subject, couldn't be more, um, really pivotal. Tell me a little bit about what happier is what the inspiration Waas for your company? >>Definitely. So as many entrepreneurs. The inspiration was my personal journey. So I grew up in the former study on when I was 13 years old, my parents and I left everything and everyone behind and on a journey deep fried becomes refugees did the United States, and we had, as you can imagine, this is a really difficult experience with several months and refugee settlements in Europe before getting permission to come to the U. S. As refugees. And we started our journey and the projects that have destroyed, you know, on welfare and food stamps, very grateful to have an opportunity, but really, really tough. And I was really overwhelmed. That was a teenager. I spoke almost no English, and it was all overwhelming for me. And I kind of decided for myself that if I could just work really hard, achieve a lot of things become successful, then I would feel happy. And then I would just feel like honor this American dream. And for the next 20 years, I did work very, very hard. I did become very successful. I reached the price of four for success. I worked at Mackenzie, you know, the very well known consulting firm. By the age of 25 I was a managing director. We're a venture capital firm in New York. There's fewer than 6% women in venture capital. I started for different companies. I was part of Microsoft in the tech companies, and on the outside I was a feeding incredible stuff. And while I still am still proud of every single thing I achieved, whenever I would've David, I feel happy. And then it was just like the bubble just off, and I didn't feel happy anymore. And so I pushed myself harder and harder because I equated happiness for the achievement. Until, after two decades of doing this, I just couldn't do it anymore. I completely burnt out. Um, it was a really, really dark time in my life, and I knew I had to find a different way to live so that I could do work that's meaningful to me, but that I could also honor myself as a human and find joy in the present. And that led me to doing a lot of research in psychiatry and psychology and neuroscience and learning all of these incredible skills and practices that changed my life, starting with gratitude, which is how you cultivate join the present moment and really inspired me to leave. My career is a technology exact behind you found happier. We have the same mission since we've been founded and that is to help millions of people. Dr. In working in life by practicing science, back skills to cultivate there will be what are >>some of the scientific skills behind it and anything that that, you see that is even more pivotal in week eight of this work from home shelter in place? >>Yes. You know it It sounds really weird to say, but I feel like I've been preparing my full life. Do you help people right now? Because the skills that I have learned and I share are so essential. And >>the two that I >>would mention that I've been you know, we've been doing all these virtual sessions for teams and companies, and this is the ones I talk about. The first is the skill of gratitude. You know, gratitude is just very simply zooming in on something in your life that is good. That is positive. That is meaningful. and honoring it with your full appreciation. And you know, we're all right now going for so many challenges and we all have with all the negativity bias. And that means we're much more sensitive humans, anything that's negative and anything that positive and when we're going through a challenge, that negativity biases even more sensitive. So I know many folks right now are feeling really overwhelmed with their own feelings, but their own sense of loss and fear and with all the negative news and so practicing gratitude is essential because when you pause and you focus on the things >>in your life as it is, >>um, it's the challenge that you do appreciate. You remind your brain that the the challenge is not everything, that there is more to your life than what is going wrong. And that actually helps you to feel a little bit less stressed and anxious. And the other piece of science that I love to share is another skill that I talked about, which does Ah, and acceptance. Really. It simply means that we learn, look at how things are and how we feel with clarity instead of judgment, right and shorthand for judgment is should shouldn't feel like this. It shouldn't be this way, and that's having clarity. Allowing yourself to actually feel the difficult feelings helps us to move through them with a little bit more easy. I think it's one of the most, um, powerful mindset. A mindset shift that I learned on my journey is that happiness does not mean that you feel positive all the time. Happiness and emotional being means that we embrace all of our different feelings, including the difficult one, and we learned how to move through them with compassion. What are >>some of the things that when you're talking to the C suite executives that certain companies, whether it's bm ware or others, how our executive teams managers, where does the emotional health come in to the play? Knowing that these folks are managing teams, there are, we're seeing, as you point out, you know, the negativity vice. We're seeing the numbers of unemployment go up and up and up. Where is emotional health in terms of priority at the executive level? So this is >>one of the it, so it sounds really weird to say, but all of a sudden its like in this huge wave it already started, right? Some companies and we work with many of them already understood. The executives already understood that employee well, being an emotional health, it's not an extra. It is not optional. It is non negotiable. If you want your people to be at their best, there are literally mountains of research that show that when you cultivate, employees will be people are more productive, more resilient. More so, Cecil, they still better problems. But happened in this crisis is that the companies that were in a place where oh, this isn't really important or this is nice to have They are now recognizing that this is actually the most important thing that they could invest in for the success and longevity and survival of their businesses. And so I'm actually incredibly grateful for that. I don't like that off that we have to pay for it. But I am incredibly grateful that in this challenging time, more and more leaders there understanding that their own well being and the emotional health of their employees is non negotiable, not just for survival of their businesses, but if they want to be at their best and actually figure out how to thrive in whatever the future holds. >>And I'm glad to hear that, because the massive amount of uncertainty that we're all facing is unprecedented. You know, you can't pick up the phone and call your Brian mother and say, What did you guys do back in the day? And honestly, even if there had been something similar, 1918 hasn't been that long ago. People have nowadays are used to getting everything that you want on demand and also being able to get connected. Um, have good WiFi and be able to deliver what your clients what your what your bosses expect. The uncertainty factor that really weighs heavily on emotion is a huge inhibitor to productivity negotiation. Being worry >>if I can jump in uncertainty is the hardest thing for a brain to deal with. Our brains would rather know that something very bad will definitely happen. Then the B and uncertainty and I've actually been talking so much the companies and leaders about this, that this is literally the most stressed that we can experience because our brains number one job and I'm the founder of a company called Happier. But I always say that your brain number one job is not to keep you happy. It >>is to help you surmise. And so >>you're bring this constantly Evaluating your environment is the state of fruit or is a dangerous right fighter. But we know that was fun. What's happening right now is that the brain and I've come up with an answer. It doesn't know. Is it safe? Is it not safe? And I don't just mean in a macro way, um, macroeconomic way with the virus. I mean day to day. Things change day to day. We're juggling kids and family, and our businesses are changing so the brain doesn't give up. It's still tries really hard to figure out how to keep your state and that hard that working overtime the way it does that is by releasing stress hormones. So on top of just the very real challenges that so many folks have with worrying about loved ones juggling, working from home and family, there's also this chronic level of stress the world feeling because of uncertainty. >>Tell me a little bit about the interactive session that you held at WT through the other day. What were some of the common concerns or questions that you heard from the >>audience. Yeah, it's really interesting. It was such a great session, and we we had a lot of questions. We could not answer all the questions. Um, and I think that it means a lot to make it really thought about what they wanted to ask. There's a couple of things that emerged as common thread. The first was, How do I help someone in my life a colleague that I manage a loved one? How do I help them during this time if they're really overwhelmed or stressed? They're feeling sad, and we talked about the seal of acceptance, and we talked about how it might be our instincts to immediately cheer up the first thing. But actually, the bigger gift we can give them is to let them know that it's okay to not be okay and to honor their feelings with our effectiveness, and that actually helped them get through. So that was one of the themes that came up a lot. Another one was, with all of this uncertainty and the stress, like people would ask, I have trouble getting motivated like I love my job I love what I do, but I have so much trouble getting motivated, and that is very real. And the first thing that if anyone listening, feels this way, um, there's nothing wrong with you. Think about the amount of energy you're brain is using on all the stress. So no wonder you feel more fired and not as motivated. And so we talked about practicing self compassion, Um, in our expectations of ourselves and recognizing that we're undergoing something unprecedented and so difficult and then get motivated connecting the past on your to do list. Do How do they help someone else? Because that is where we connect first since the purpose, right, So that projects you're working on with your team or that presentation that you just can't get motivated to do. Ask yourself who does this help and actually answer the question? And in that moment, you connect yourself the purpose, which helps us be more resilient and more motivated. >>Get a notification or lack thereof is a huge problem, and I you know, you can't think it's not just may, not just you. It's got to be all the way up to the tops of companies that are really struggling because, as you say, the brain is so focused right now and busy and trying to assess things. And there are no concrete answers. But one of the things that you said I read your article in The Washington Post that you just did in the last week or so with your daughter and with my daughter. Yeah, with your daughter Mia. And the validation was Start on. And it it's so simple. But it's one of those things that I think often we think, Well, let me explain something and try to help you in that way without maybe stepping back and going well, actually help me. But what helps you? Are you seeing that that the executive leaders are also kind of stepping back and asking their teams? How are the ways that you want me to communicate with you? Or is that something that's happened? You know, I think that >>we are in an era of, um, human embracing leadership of, and I am so welcoming the era of leaders who are leading with their humanity first and are embracing the humanity of their people first. You know, I have this, um, actually working on my next book right now with this for leaders. And I have this concept, um, because I was a leader for so many years, and I always thought that I keep my emotions hidden, that emotions really didn't have anything to do with work. So I have this part that for leaders, they imagine you're holding a white board, and this is your emotional whiteboard on it are written your feeling. Whether you want to admit them or not, that team feels them, and it's the same for everyone on the team. So when you walk into a meeting, whether the virtual meeting or in person what is written on your emotional whiteboard, what are you feeling? And how are you approaching others? What do you want to be written on your emotional whiteboard, right? I think, as leaders, we would say, Well, I want to stay there, hear about you as my employees, that I want to hear how you're feeling. But think about are the actions you're taking aligning with with on your emotional whiteboard, right? And so listening and hearing, you know, I have this, um, came up with shorthand. Really? For me as a leader during a challenging time, and it's at C D. The first is acknowledge. Acknowledge your own challenges. Acknowledge your teams challenges, right. Validation. This point we're talking about, he is prepare genuinely care, right? So don't just do it as a check mark. But bring your humanity and compassionate actually care about people. There's so much research that when employees know that their leader cares about them, that on its own is hopeful for them. So there will be in their productivity. And he acts. So a c c es teach by example. So do the things that you want, your employees, the follow. And, um, I do see leaders stepping up more and more in their passion and their acceptance. And again, I think this is, ah, difficult but unique moment in time Do elevate our human embracing leadership. >>Do you advise women and men? Teoh. When we talked about gratitude a few minutes ago, right down, maybe. Right. Maybe it helps with your visual learner or someone that learns by storytelling to write things down, Maybe write down each day a few things. Maybe they seem so simple that you're grateful for, Or maybe even I like the idea of the emotional White Board. I can see that as something that would be helpful to write down. Do you recommend that to folks and maybe write down what your actual emotional thing is and what you want it to be? So a couple >>things on that. So the short answer is yes, you know, when it comes to gratitude, Um, it doesn't really matter how you practice like people say to me like I'm not a journalist, that's fine. That as long as you're specific and your gratitude So instead of I'm grateful for my family, how about I'm really grateful that I could give my daughter hug before I started interview? Right? So the more specific, the better. And actually the smaller the better. You talked about small things. Research shows that it's the frequency of small, positive experiences that contribute thoroughly. Satisfaction more than anything, grants so the smaller the better and capturing does health, so you can write in a journal. You can write it on a sticky notes. Maybe it's a text that you send to a friend to encourage them to practice practice as a leader. Maybe it's an email that you send to your teams. The factoring in some way really does help. And when it comes to the emotional white board, the practice that I share with, um, everyone is a check in. Check in with yourself, right? It's so incredible. You know, we have this group for women executives elevating women leaders. Is that all Vertical group, the year long program. It was worked well before this. So we have a group that goes with us every year, and one of the practice that we do is in the morning and in the afternoon, you check in with yourself on just day all my feeling, and you would not believe the impact that that has on their ability to solve problems on their ability to show up as their best just by pausing and checking in, like, How am I feeling what is in my emotional whiteboard? Acknowledging that without Dutchman being compassionate towards yourself and then saying, What is one thing I can shift if I would like you feel differently? >>The acknowledgement piece is critical, I think because it's it's the vulnerability to step up and go. I don't feel great about this and let me let me say that out loud. Maybe it helps me become accountable to that or expect it to a boss or a colleague that put it out there. That's a hard thing for people to do. Especially I think there is this dichotomy of people being concerned about John Safety when we're seeing what's going on in the news. Did any of that have come up during your WT two session about? I'm afraid to admit that I'm not motivated because our company's experiencing layoff. >>Yeah, it's definitely come up in the session and other sessions of kind of finding that balance. And look, you have to be realistic because we all have different filters in our teams. You have to be realistic about your leadership. But what I find over and over is that authenticity wins today, right? So, um, you have to you have to make all right how much you share. But even if it's just a little bit of Acknowledgments, it is helpful because it helps you not resist it so much and more likely than not. There's somebody on your team who feel similarly so that, by the way, there's comfort in knowing we're not alone. there's actually neurological comfort in knowing we're not alone like we need that sense of safety, but also you made them be able to move through that and brainstorm together and help each other get motivated. So you know, you have to judge by the culture of your team. But authenticity and you acknowledging your humanity to whatever degree you feel comfortable is usually an incredibly hopeful practice to help you be at your best, whatever that means. That >>day, I couldn't agree with you more. I always The authenticity is contagious. Natalie. It's been so great having you on the program. I wish we could keep chatting, but it is time to go. Thank you so much so folks can go toe happier, dot com or help your fellow happier and more. How about your home? Lots >>of lots of tons of free block posts and videos on all of the different practices I shared more about anything we do. So yes, come visit us that happier dot com and thank you so much for such thoughtful questions. I'm always incredibly grateful for thoughtful questions at interviews, but I really appreciate that. Well, >>good. Now it's been a pleasure having you. And I want to thank you for watching on behalf of Natalee code. And I'm Lisa Martin covering women transforming technology. The virtual version 2025. For now. >>Yeah! Yeah, yeah, yeah, yeah, yeah!

>> From the Palace of Fine Arts in San Francisco, it's theCUBE, covering AT&T Spark. Now here's Jeff Frick. >> Hey welcome back everybody, Jeff Frick here with theCUBE. We're at San Francisco, at the historic Palace of Fine Arts, it's a beautiful spot, it's redone, they moved Exploratorium out a couple years ago, so now it's in a really nice event space, and we're here for the AT&T Spark Event, and the conversation's all around 5G. But we're excited to have our first guest, and he's working on something that's a little bit tangential to 5G-related, but not absolutely connected, but really important work, it's Chris Sambar, he is the SVP of FirstNet at AT&T, Chris, great to see you. >> Thanks Jeff, great to be here, I appreciate it. >> Yeah, so you had a nice Keynote Presentation, talking about FirstNet. So for people I've missed, that aren't familiar, what is AT&T FirstNet? >> Sure, I'll give a quick background. As I was mentioning up there, tomorrow is the 17-year Anniversary of 9/11. So 17 years ago tomorrow, a big problem in New York City. Lots of first responders descended on the area. All of them were trying to communicate with each other, they were trying to use their radios, which they're you know, typically what you see a first responder using, the wireless networks in the area. Unfortunately challenges, it wasn't working. They were having trouble communicating with each other, their existing wireless networks were getting congested, and so the 9/11 Commission came out with a report years later, and they said we need a dedicated communications network, just for First Responders. So they spun all this up and they said, we're going to dedicate some Spectrum, 20 megahertz of D-Class Spectrum, which is really prime Spectrum. Seven billion dollars and we're going to set up this Federal entity, called the FirstNet Authority, and they're going to create a Public Safety Network across America. So FirstNet Authority spent a few years figuring out how to do it, and they landed on what we have today, which was a Public/Private Partnership, between AT&T, and Public Safety throughout America, and we're building them a terrific network across the country. It is literally a separate network so when I, I think of wireless in America, I think of four main commercial carriers, AT&T, Verizon, T-Mobile, Sprint. This is the 5th carrier, this is Public Safety's Wireless Network just for them. >> So when you say an extra network, so it's a completely separate, obviously you're leveraging infrastructure, like towers and power and those types of things. But it's a completely separate network, than the existing four that you mentioned. >> Yeah, so if you walk into our data centers throughout the country, you're going to see separate hardware, physical infrastructure that is just for FirstNet, that's the core network just for this network. On the RAN, the Radio Access Network, we've got antennas that have Band 14 on them, that's Public Safety's Band, dedicated just for them when they need it. So yeah, it's literally a physically separate network. The SIM card that goes into a FirstNet device, is a different SIM card than our commercial users would use, because it's separate. >> So one of the really interesting things about 5G, and kind of the evolution of wireless is, is taking some of the load that has been taken by like WiFi, and other options for fast, always on connectivity. I would assume radio, and I don't know that much about radio frequencies that have been around forever with communications in, in First Responders. Is the vision that the 5G will eventually take over that type of communication as well? >> Yeah, absolutely. If you look at the evolution of First Responder, and Public Safety Communications, for many years now they've used radios. Relatively small, narrow Spectrum bands for Narrow Band Voice, right, just voice communications. It really doesn't do data, maybe a little bit, but really not much. Now they're going to expand to this Spectrum, the D-Class, the D-Block Spectrum, excuse me, which is 700 megahertz, it's a low-band Spectrum, that'll provide them with Dedicated Spectrum, and then the next step, as you say, is 5G, so take the load off as Public Safety comes into the, the new Public Safety Communications space, that they've really been wanting for years and years, they'll start to utilize 5G as well on our network. >> So where are you on the development of FirstNet, where are you on the rollout, what's the sequence of events? >> The first thing we did, the award was last year in March 2017. The first thing we did was we built out the core network. When I talked about all that physical infrastructure, that basically took a year to build out, and it was pretty extensive, and about a half a billion dollars so, that was the first thing we did, that completed earlier this year. >> Was that nationwide or major metro cities or how-- >> Nationwide, everywhere in the country. >> Nationwide, okay. >> So now what we're doing is, we are putting the Spectrum that we were given, or I should say we were leased for 25 years, we're putting that Spectrum up across our towers all over the country so, that will take five years, it's a five-year build-out, tens of thousands of towers across America, will get this Public Safety Spectrum, for Public Safety, and for their use. >> Right. Will you target by GEO, by Metro area, I mean, how's it going to actually happen? That's a huge global rollout, five years is a long time. How you kind of prioritize, how are you really going to market with this? >> The Band 14 Spectrum is being rolled out in the major, the major dense areas across the country. I will tell you that by the end of the rollout, five years from now, 99% of the population of America, will have Band 14 Spectrum, so the vast majority of the population. Other areas where we don't roll it out, rural areas for example, all of the features that Public Safety wants, we call them (mumbles) and priority, which is the features to allow them to always have access to the network whenever they need it. Those features will be on our regular commercial Spectrum. So if Band 14 isn't there, the network will function exactly as if it were there for them. >> Right. Then how do you roll it out to the agencies, all the First Responders, the Fire, the Police, the EMTs, et cetera? How do they start to take advantage of this opportunity? >> Sure, so we started that earlier this year. We really started in a March-April timeframe in earnest, signing up agencies, and the uptake's been phenomenal. It's over 2500 Public Safety Agencies across America, over 150,00, and that number grows by thousands every week. That's actually a pretty old number but, they are signing up in droves. In fact, one of the problems we were having initially is, handling the volume of First Responders that wanted to sign up, and the reason is they're seeing that, whether it's a fire out in Oregon, and they need connectivity in the middle of nowhere, in a forest where there's no wireless connectivity at all, we'll bring a vehicle out there, put up an antenna and provide them connectivity. Whether it's a Fourth of July show, or a parade, or an active shooter, wherever large groups of people, combined together and the network gets congested, they're seeing that wow, my device works no matter what. I can always send a text message, I can send a video, it just works. Where it didn't work before. So they love it, and they're really, they're really signing up in droves, it's great. >> It's really interesting because it's, it's interesting that this was triggered, as part of the post 9/11 activity to make things better, and make things safer. But there was a lot of buzz, especially out here in the West with, with First Responders in the news, who were running out of band width. As you said, the Firefighters, the fire's been burning out here, it seems like forever, and really nobody thinking about those, or obviously they're probably roaming on their traditional data plan, and they're probably out there, for weeks and weeks at a time, that wasn't part of their allocation, when they figured out what plan they should be. So the timing is pretty significant, and there's clearly a big demand for this. >> Absolutely. So that example that you sight is a really good one. Two weeks ago, there was a lot in the news about a fire agency in the West, that said they were throttled by their carrier. It was a commercial carrier, and commercial carriers have terms and conditions, that sometimes they need to throttle usage, if you get to a certain level. That's how commercial networks work. >> Right, right. >> FirstNet was built with not only different technology, hardware, software, but with different terms and conditions. Because we understand that, when a First Responder responds to your house, we don't want that to be the minute in time, when their network, their plan got maxed out, and now they're getting throttled. >> Right. >> So we don't have any throttling on the FirstNet Network. So it's not only the hardware, software, technical aspects of the network, but the terms and conditions are different. It's what you would expect that a First Responder would have and want on their device, and that's what we're providing for them. >> Right, and the other cool thing that you mentioned is, we see it all the time, we go to a lot of conferences. A lot of people probably experience it at, at big events right, is that still today, WiFi and traditional LTE, has hard times in super-dense environments, where there's just tons and tons and tons of bodies I imagine, absorbing all that signal, as much as anything else, so to have a separate Spectrum in those type of environments which are usually chaotic when you got First Responders, or some of these mass events that you outlined, is a pretty important feature, to not get just completely wiped out by everybody else happening to be there at the same time. >> Exactly. I'll give you two quick examples, that'll illustrate what you just said. The first one is, on the Fourth of July, in downtown Washington D.C. You can imagine that show. It's an awesome show, but there are hundreds of thousands of people that gather around that Washington Monument, to watch the show. And the expectation is at the peak of the show, when all those people are there, you're not really going to be sending text messages, or calling people, the network's probably just not going to work very well. That's, we've all gotten used to that. >> Right, right. >> This year, I had First Responders, who were there during the event, sending me videos of the fireworks going off. Something that never would've been possible before, and them saying oh my gosh. The actually works the way it's supposed to work, we can use our phones. Then the second example, which is a really sad example. There was a recent school shooting down in Florida. You had Sheriffs, Local Police, Ambulances. You even had some Federal Authorities that showed up. They couldn't communicate with each other, because they were on different radio networks. Imagine if they had that capability of FirstNet, where they could communicate with each other, and the network worked, even though there were thousands of people that were gathering around that scene, to see what was going on. So that's the capability we're bringing to Public Safety, and it's really good for all of us. >> Do you see that this is kind of the, the aggregator of the multi-disparate systems that exist now, as you mentioned in, in your Keynote, and again there's different agencies, they've got different frequencies, they've got Police, Fire, Ambulance, Federal Agencies, that now potentially this, as just kind of a unified First Responder network, becomes the defacto way, that I can get in touch with anyone regardless of of where they come from, or who they're associated with? >> That is exactly the vision of FirstNet. In major cities across America, Police, Fire, Emergency Medical typically, are on three different radio networks, and it's very difficult for them to communicate with each other. They may have a shared frequency or two between them, but it's very challenging for them. Our goal is to sign all of them up, put them on one LTE network, the FirstNet Network, customized for them, so they can all communicate with each other, regardless of how much congestion is on the network. So that's the vision of FirstNet. >> Then that's even before you get into the 5G impacts, which will be the data impacts, whereas I think again, you showed in some of your examples, the enhanced amount of data that they can bring to bear, on solving a problem, whether it's a layout of a building for the Fire Department or drone footage from up above. We talked to Menlo Park Fire, they're using drones more and more to give eyes over the fire to the guys down on the ground. So there's a lot of really interesting applications that you can get more better data, to drive more better applications through that network, to help these guys do their job. >> Yeah, you've got it, the smart city's cameras, don't you want that to be able to stream over the network, and give it to First Responders, so they know what they're going to encounter, when they show up to the scene of whatever issue's going on in the city, of course you do, and you need a really reliable, stable network to provide that on. >> Well Chris, this is not only an interesting work, but very noble, and an important work, so appreciate all of the efforts that you're putting in, and thanks for stopping by. >> I appreciate it Jeff, it's been great talking with you. >> Alright, he's Chris, I'm Jeff, you're watching theCUBE, we're in San Francisco at the Palace of Fine Arts, at AT&T Spark. Thanks for watching, we'll see you next time. (bright music)

>> Announcer: Live from Chicago, Illinois, it's the Cube covering VeeamON 2018. Brought to you by Veeam. >> Welcome back to Chicago, everybody. This is the Cube, the leader in live tech coverage, and you're watching our exclusive coverage of VEEAMON 2018. #VeeamON. My name is Dave Vallante and I'm here with my cohost Stuart Miniman. Stu, great to be working with you again. >> Thanks Dave. Admiral, David G. Simpson is here. He's a former Chief Public Safety and homeland Security Bureau and CEO, currently, of Pelorus, a consultancy that helps organizations think through some of the risk factors that they face. David, welcome to the Cube. Thanks so much for taking time out. >> It's my pleasure to be here. >> So, as I was saying, we, we missed a big chunk of your keynote this morning cause we had to come back to the cube and do our open, but let's start with your background and kind of why you're here. >> Sure, well, I spent over three decades in the Navy where my responsibilities throughout included the resiliency of the ability to command and control forces in areas around the world not always so nice and often arduous and often at sea. So, that experience really has given me a very good appreciation, not only for how important economy of operations is, but how difficult it can be and how important the details are, so I am a natural fan of what FEMA's doing to make that easier for organizations. After DOD, I was recruited by the chairman of the FCC to lead the Public Safety Homeland Security Bureau for the Federal Communications Commission. And, in that position, I have responsibility for the nation's climate one system, emergency alerting, and the resiliency of over 30,000 telecommunication companies in the domestic market, so both experiences really have given me a very good insight into the need, the consequence of not getting it right, how to prepare to get it right, but also an ability to look at what's coming down the pike with the new telecommunications technologies that will really be game changers for functionality in the new internet of things environment. >> So, three decades of public service. First of all, thank you. >> Thank you. It's quite an accomplishment. And then, we had talked off camera that we, a couple of years ago, had Robert Gates on and we were gettin' detailed into how the experience that someone like you has had in the public sector translated to the private sector. It used to be there was just such a huge gap between, you know, what you did and what a, what a company had to, had to worry about. Do you see that gap closing? And, maybe, you could add some color to that. >> Sure, and in particular, in the cyber arena, you know, cyber, unlike the land, sea, and air domains, is a domain of Man's own making and the constraints around that domain are of our own choosing. And, we're not constrained by physics, we're constrained by the investment decisions we make and the contours of that expanding environment. But, the internet started out as a DOD research and development project, ARPA, so it has not been unusual for DOD to be out in front in some of the development aspects where counterintuitively we would, normally, see industry out in front. The same occurred I believe with cyber when our intelligence community over 10 years ago said, hey, this is a great thing, this internet thing. And, it's super that we're doing more and more communications, that we're talking with devices at the edge around the battle space, but it's vulnerable to attack and we need to organize, so that we are capable in the defense of that great cyber set of functionality that we've built. >> Could you expand? Just, so, you're doing some teaching in the cyber security world too. Maybe you could share a little bit what you're doing and what you see as kind of the state of this today >> Yeah, well, thank you for asking that about a year ago, the dean of the business school of Virginia Tech, asked me if I wouldn't consider building a cyber program for the business school. Tech has always had a strong engineering component to cyber security and it's led by a good friend of mine Dr. Charles Clancy with some superb research going on, but, increasingly, over two thirds of the work roles, in cyber security are not engineering. They really have much more to do with traditional business functions. Yet, most business leaders aren't well prepared to assess that risk environment, let alone appreciate it, and then, drive investments to address risk reduction. So, at Virginia Tech, we've built a series of four courses that in the MBA programs, the Masters of Accounting, the Masters of Business IT, we are now teaching prospective business leaders how to look at the risk environment and organize an investment structure using the NIST, or National Institute of the Standards of Technology, risk management framework, so that can be done in a repeatable way that communicates well with industry. And, companies like Veeam have an important role to play in that space because Veeam really translates much of the engineering complexities into business understandable conditions by which decisions about that data space can really be made. >> I want to share an observation that we had on the Cube last year, one of my favorite interviews was with a gentleman from ICIT, James Scott. He's a security expert, you may know him. And, we asked him what the biggest threat was to United States and his answer surprised me. I thought it was going to be, you know, cyber warfare or risks to critical infrastructure, he said the weaponization of social media was the number one threat, like wow. And, we had a really interesting discussion about that and, you know, I think of, you know, your background, loose lips sink ships, people on social give up there credentials, all of a sudden, you've got some outside bad actors controlling the narrative, controlling the meme and controlling the population without firing a shot. Wow, so what are your thoughts on social media and it's risk to our society and how to deal with it? >> Well, we're seeing in the last year, that he's very prescient, right, in that you can lockdown all the bits and the bytes and get the integrity, the confidentiality, and the availability of your data sets taken care of, but in a world where the public square, if you will, is now a virtual public square, if an adversary can change the perception of reality in that public square, or if they can cause our democracy to lose confidence in that public square, then an adversary can really achieve a kill, if you will, a desired effect in a way that is very negative for the country, so I don't see that though as being completely distinguished from cyber security. I see, in my mind, that we need to expand the universe, to protect the universe of cyber into that cognitive space. And, we need to understand, increasingly, the origin of comment in the social media arena. We need to understand therole algorithms have to play in amplifying a message and suppressing other messages. And, we need to, I think, have a greater accountability for businesses that are in that virtual public square line of business to help consumers and communities continue to have confidence in that public square and we're, we're challenged in that area. 'cause see Mark Zuckerberg's testimony, right >> Sure. >> Illuminated some big challenges there. >> Yeah, I mean, my heart went out to Zuckerberg, it was, I was like the poor guy, he's just trying to build out a social network and now he's getting, you know, attacked by politicians who are saying, wow you mean you use data for political gain, or you allowed somebody to do it. >> He was in a tough spot. >> And politicians themselves, I think, were a bit embarrassed in revealing their lack of tech savvy in a world where we should expect policy makers to be at least aware enough of the parameters around the virtual public square where they can help develop the right policy to ensure that this continues to be a net asset for the United States, for communities, and for consumers. >> Technology kind of got us into this problem, but, technology, in and of itself, is not going to get out of, get us out of this problem >> Right. >> It's others in the organization, the lines of business, the policies, the practices, some of the work that you do in your teachings, may be >> Yeah, absolutely and when I talk to aspiring business leaders, I communicate a couple of things to them. One, they need to get their heads out of being the decider as the CEO. Increasingly, they will be creating decision environments, right, where decision operations occur and are driven by algorithms, by machine learning, and AI, and so they've got to be thinking, about how do they create those environments to deliver the right kind of decision results that they're looking for. The second piece that I talk to them about, that's counterintuitive, is that they need to, as they bring in network functional virtualization and more and more software oriented things that used to be hardware, they've got to understand the risk exposure from that and bring in, they can, a way to address cyber risk as they introduce new functionality in the market. >> Well, it's interesting of an Admiral talking about network function virtualization, I'm very impressed. Admiral Simpson, thanks very much for coming on the Cube. >> Sure. >> Really a pleasure having you and best of luck in your work. >> Well, thank you and it's great to be here with the Veeam professionals that, I think, are really building a command and control layer of an enterprise of data space that will be very important for the future. >> Alright, okay, thanks for watching everybody. We will be right back, Stu Miniman and Dave Vallante from VeeamOn 2018, you're watching the Cube. >> Great thanks. (upbeat music)

>> Announcer: Live from New Orleans, Louisiana. It's theCUBE, covering .NEXT conference 2018, brought to you by Nutanix. >> Welcome back, we're here in New Orleans in the state of Louisiana, and to help Keith Townsend and myself, Stu Miniman, wrap up we're glad to have one more customer. We have the great state of Louisiana here with us, we have Michael Allison, who's the Chief Technology Officer. We also have Derek Williams, who's the Director of Data Center Operations. Gentleman, thanks so much for joining us. >> Thank you. >> Thanks for having us. >> All right, so I think we all know what the state of Louisiana is, hopefully most people can find it on a map, it's a nice easy shape to remember from my kids and the like. But, Michael, why don't we start with you? Talk to us first about kind of the purview of your group, your organization, and some of the kind of biggest challenges you've been facing in recent times. Sure, we are part of the Office of Technology Services, which is a consolidated IT organization for the state of Louisiana. We were organized about four years ago. Actually four years ago this July. And that brought in the 16 Federated IT groups into one large organization. And we have the purview of the executive branch, which includes those typical agencies like Children and Family Services, Motor Vehicles, Public Safety, Health and Hospitals, Labor, etc. >> And Derek, you've got the data center operations, so give us a little bit of a scope. We heard how many organizations in there, but what do you all have to get your arms around? >> Sure, so we had, you know, there's often a joke that we make that if they've ever made it we own one of each. So we had a little bit of every type of technology. So what we've really been getting our arms around is trying to standardize technologies, get a standard stack going, an enterprise level thing. And really what we're trying to do is become a service provider to those customers where we have standard lines of service and set enterprise level platforms that we migrate everybody onto. So do you actually have your own data centers? Your own hosting facilities? What's kind of the real estate look like? >> Absolutely, so we have, the state has two primary data centers that we utilize, and then we also use a number of cloud services as well as some third-party providers for offsite services. >> So obviously just like every other state in the union, you guys have plenty of money. >> Always. >> Way too many employees and just no challenges. Let's talk about what are the challenges? You know, coming together, bringing that many organizations together, there's challenges right off the bat. What are some of the challenges as you guys look to provide services to the great people of Louisiana? >> Well as Derek kind of eluded to, technology debt is deep. We have services that are aging at about 40 years old, that are our tier one services. And they were built in silos many, many years ago. So being able to do the application or actualization, being able to identify those services, then when we actually shift to the cultural side, actually bringing 16 different IT organizations into one, having all those individuals now work together instead of apart. And not in silos. That was probably one of the biggest challenges that we had over the last few years is really breaking down those cultural barriers and really coming together as one organization. >> Yeah I totally agree with that. The cultural aspect has been the biggest piece for us. Really getting in there and saying, you know a lot of small and medium size IT shops could get away without necessarily having the proper governance, structures in place, and a lot of people wore a lot of hats. So now we're about 800 strong in the Office of Technology Services, and that means people are very aligned to what they do operationally. And so that's been a big shift and kind of that cultural shift has really been where we've had to focus on to make that align properly to the business needs. >> Mike, what was the reason that led you down the path towards Nutanix? Maybe set us up with a little bit of the problem statement? We heard some of the heterogeneous nature and standardization which seems to fit into a theme we've heard lots of times with Nutanix. But was there a specific use case or what led you towards that path? Well, about four years ago the Department of Health and Hospitals really had a case where they needed to modernize their Medicaid services, eligibility and enrollment. CMS really challenged them to build an infrastructure that was in line with their MIDAS standards. There was modular, COTS, configuration over customization. Federal government no longer wants to build monolithic systems that don't integrate and are just big silos. So what we did was we gravitated to that project. We went to CMS and said, hey why don't we take what you're asking us to build and build it in a way that we can expand throughout the enterprise to not only affect the Department of Health but also Children of Family Services, and be able to expand it to Department of Corrections, etc. That was our use case, and having an anchor tenent with the Department of Health that has a partner with CMS really became the lynch pin in this journey. That was our first real big win. >> Okay how did you hear first about Nutanix? Was there a bake off you went through? >> It was, yes, very similar. It was the RP process took a year or so and we were actually going down the road of procuring some V blocks, and right before the Christmas vacations our Deputy CIO says hey, why don't you go look to see if there's other solutions that are out there? Challenge Derek, myself, and some others to really expand the horizons. Say, if we're going to kind of do this greenfield, what else is out there? And right before he got on his Christmas cruise he dropped that on our lap and about a month later we were going down the Dell Nutanix route. And to be honest it was very contentious, and it actually took a call from Michael Dell who I sent to voicemail twice before I realized who it was, but you know, those are the kind of decisions and the buy in from Dell executives that really allowed us to comfortably make this decision and move forward. >> So technology doesn't exactly move fast in any government because, you know, people process technology and especially in the government, people and process, as you guys have deployed Nutanix throughout your environment, what are some of the wins and what are some of the challenges? >> That's a funny point because we talk about this a lot. The fact that our choice was really between something like VBlock, which was an established player that had been for a long time, and something a little more bleeding edge. And part of the hesitancy to move to something like Nutanix was the idea that hey, we have a lot of restricted data, CJIS, HIPAA, all those kind of things across the board, RS1075 comes into play, and there was hesitancy to move to something new, but one of the things that we said exactly was we are not as agile as private sector. The procurement process, all the things that we have to do, put us a little further out. So it did come into play that when we look at that timeline the stuff that's bleeding edge now, by the time we have it out there in production it's probably going to be mainstream. So we had to hedge our bets a little. And you know, we really had to do our homework. Nutanix was, you know, kind of head and shoulders above a lot of what we looked at, and I had resiliency to it at first, so credit to the Deputy CIO, he made the right call, we came around on it, it's been awesome ever since you know, one of the driving things for us too was getting out there and really looking at the business case and talking to the customers. One of the huge things we kept hearing over and over was the HA aspect of it. You know, we need the high availability, we need the high availability. The other interesting thing that we have from the cost perspective is we are a cost recovery agency now that we're consolidated. So what you use you get charged for, you get a bill every month just like a commercial provider. You know, use this many servers, this much storage, you get that invoice for it. So we needed a way that we could have an environment that's scaled kind of at a linear cost that we could just kind of add these nodes to without having to go buy a new environment and have this huge kind of CAPX expenditure. And so at the end of the day it lived up to the hype and we went with Nutanix and we haven't regretted it, so. >> How are the vendors doing overall, helping you move to that really OP-X model, you said, love to hear what you're doing with cloud overall. Nutanix is talking about it. Dell's obviously talking about that. How are the vendors doing in general? And we'd love to hear specifically Dell Nutanix. >> We've had the luxury of having exceptionally good business partners. The example I'd like to give is, about four months into this project we realized that we were treated Nutanix as a traditional three-tier architecture. We were sending a lot of traffic more south. When we did the analysis we asked the question, a little cattywampus, it was how do we straighten this out? And so we posed a question on a Tuesday about how do we fix this, how do we drive the network back into the fabric? By Thursday we were on a phone call with VMWare. By the following Monday we had two engineers on site with a local partner with NSX Ninja. And we spent the next two months, with about different iterations of how to re-engineer the solution and really look at the full software-defined data center, not just software-defined storage and compute. It is really how do we then evolve this entire solution building upon Nutanix and then layering upon on top of that the VMWare solutions that kind of took us to that next level. >> Yeah and I think the key term in there is business partner. You know, it sounds a little corny to say, but we don't look at them as just vendors anymore. When we choose a technology or direction or an architecture, that is the direction we go for the entire state for that consolidated IT model. So, we don't just need a vendor. We need someone that has a vested interest in seeing us succeed with the technology, and that's what we've gotten out of Nutanix, out of Dell, and they've been willing to, you know, if there's an issue, they put the experts on site, it's not just we'll get some people on a call. They're going to be there next week, we're going to work with you guys and make it work. And it's been absolutely key in making this whole thing go. >> And as a CTO one of the challenges that we have is, as Derek has executed his cloud vision, is how do we take that and use it as an enabler, an accelerant to how we look at our service design, service architecture, how do we cloud optimize this? So as we're talking about CICD and all these little buzzwords that are out there, is how can we use this infrastructure to be that platform that kind of drives that from kind of a grass root, foundation up, whereas sometimes it's more of a pop down approach, we're taking somewhat of an opposite. And now we're in that position where we can now answer the question of now what, what do we do with it now? >> So sounds like you guys are a mixed VMWare, Nutanix hardware, I mean software, Dell hardware shop, foundation you've built the software-defined data center foundation, something that we've looked at for the past 10 years in IT to try and achieve, which is a precursor, or the foundation, to cloud. Nutanix has made a lot of cloud announcements. How does Nutanix's cloud announcements, your partnership with Dell match with what you guys plan when it comes to cloud? >> That's a perfect lead in for us. So you're absolutely right. We have had an active thought in our head that we need to move toward SDDC, software-defined data center is what we wanted to be at. Now that we've achieved it the next step for us is to say hey, whether it's an AWS or whomever, an Azure type thing, they are essentially an SDDC as well. How do we move workloads seamlessly up and down in a secure fashion? So the way we architected things in our SDDC, we have a lot of customers. We can't have lateral movement. So everything's microsegmentation across the board. What we've been pursuing is a way to move VM workloads essentially seamlessly up to the cloud and back down and have those microsegmentation rules follow whether it goes up or back down. That's kind of the zen state for us. It's been an interesting conference for us, because we've seen some competitors to that model. Some of the things Nutanix is rolling out, we're going to have to go back and take a very serious look at on that roadmap to see how it plays out. But, suddenly multicloud, if we can get to that state we don't care what cloud it's in. We don't have to learn separate stacks for different providers. That is a huge gap for us right now. We have highly available environment between two data centers where we run two setups active active that are load balanced. So the piece we're missing now is really an offsite DR that has that complete integration. So the idea that we could see a hurricane out in the golf, and 36, 48 hours away, and know that we might be having some issues. Being able to shift workloads up to the cloud, that's perfect for us. And you know, then cost comes into play. All that kind of stuff that we might have savings, economy of scale, all plays in perfectly for us. So we are super excited about where that's going and some of the technologies coming up are going to be things we're going to be evaluating very carefully over the next year. >> At the end of the day it's all about our constituents. We have to take data, turn it into information that they can consume at the pace that they want to. Whether it be traditional compute in a desktop or mobile or anywhere in between. It was our job to make sure that these services are available and usable when they need it, especially in the time of a disaster or just in day-to-day life. So that's the challenge that we have when delivering services to our citizens and constituents. >> All right, well Mike and Derek, really appreciate you sharing us the journey you've been on, how you're helping the citizens here in the great state of Louisiana. For Keith Townsend, I'm Stu Miniman. Thanks so much for watching our program. It's been a great two days here. Be sure to check out theCUBE.net for all of our programming. Thanks Nutanix and the whole crew here, and thank you for watching theCUBE. >> Thank you.

>> Announcer: From Milpitas, California, at the edge of Silicon Valley, it's The Cube. Covering autonomous vehicles. Brought to you by Western Digital. >> Hey, welcome back everybody, Jeff Frick here with the Cube. We're at Western Digital in Milpitas, California at the Auto Tech Council, Autonomous vehicle meetup, get-together, I'm exactly sure. There's 300 people, they get together every year around a lot of topics. Today is all about autonomous vehicles, and really, this whole ecosystem of startups and large companies trying to solve, as I was just corrected, not the thousands of problems but the millions and billions of problems that are going to have to be solved to really get autonomous vehicles to their ultimate destination, which is, what we're all hoping for, is just going to save a lot of lives, and that's really serious business. We're excited to have the guy that's kind of running the whole thing, Derek Curtain. He's the chairman of the Auto Tech Council. Derek, saw you last year, great to be back, thanks for having us. >> Well, thanks for having me back here to chat. >> So, what's really changed in the last year, kind of contextually, since we were here before? I think last year it was just about, like, mapping for autonomous vehicles. >> Yes. >> Which is an amazing little subset. >> There's been a tremendous amount of change in one year. One thing I can say right off the top that's critically important is, we've had fatalities. And that really shifts the conversation and refocuses everybody on the issue of safety. So, there's real vehicles out there driving real miles and we've had some problems crop up that the industry now has to re-double down in their efforts and really focus on stopping those, and reducing those. What's been really amazing about those fatalities is, everybody in the industry anticipated, 'oh' when somebody dies from these cars, there's going to be the governments, the people, there's going to be a backlash with pitchforks, and they'll throw the breaks on the whole effort. And so we're kind of hoping nobody goes out there and trips up to mess it up for the whole industry because we believe, as a whole, this'll actually bring safety to the market. But a few missteps can create a backlash. What's surprising is, we've had those fatalities, there's absolutely some issues revealed there that are critically important to address. But the backlash hasn't happened, so that's been a very interesting social aspect for the industry to try and digest and say, 'wow, we're pretty lucky.' and 'Why did that happen?' and 'Great!' to a certain extent. >> And, obviously, horrible for the poor people that passed away, but a little bit of a silver lining is that these are giant data collection machines. And so the ability to go back after the fact, to do a postmortem, you know, we've all seen the video of the poor gal going across the street in the dark and they got the data off the one, 101 87. So luckily, you know, we can learn from it, we can see what happened and try to move forward. >> Yeah, it is, obviously, a learning moment, which is absolutely not worth the price we pay. So, essentially, these learning moments have to happen without the human fatalities and the human cost. They have to happen in software and simulations in a variety of ways that don't put people in the public at risk. People outside the vehicle, who haven't even chosen to adopt those risks. So it's a terrible cost and one too high to pay. And that's the sad reality of the whole situation. On the other hand, if you want to say silver lining, well, there is no fatalities in a silver lining but the upside about a fatality in the self-driving world is that in the human world we're used to, when somebody crashes a car they learn a valuable lesson, and maybe the people around them learned a valuable lesson. 'I'm going to be more careful, I'm not going to have that drink.' When an autonomous car gets involved in any kind of an accident, a tremendous number of cars learn the lesson. So it's a fleet learning and that lesson is not just shared among one car, it might be all Teslas or all Ubers. But something this serious and this magnitude, those lessons are shared throughout the industry. And so this extremely terrible event is something that actually will drive an improvement in performance throughout the industry. >> That's a really good, that's a super good point. Because it is not a good thing. But again, it's nice that we can at least see the video, we could call kind of make our judgment, we could see what the real conditions were, and it was a tough situation. What's striking to me, and it came up in one of the other keynotes is, on one hand is this whole trust issue of autonomous vehicles and Uber's a great example. Would you trust an autonomous vehicle? Or will you trust some guy you don't know to drive your daughter to the prom? I mean, it's a really interesting question. But now we're seeing, at least in the Tesla cases that have been highlighted, people are all in. They got a 100% trust. >> A little too much trust. >> They think level five, we're not even close to level five and they're reading or, you know, doing all sorts of interesting things in the car rather than using it as a driver assist technology. >> What you see there is that there's a wide range of customers, a wide range users and some of them are cautious, some of them will avoid the technology completely and some of them will abuse it and be over confident in the technology. In the case of Tesla, they've been able to point out in almost every one of their accidents where their autopilot is involved, they've been able to go through the logs and they've been able to exonerate themselves and say, 'listen, this was customer misbehavior. Not our problem. This was customer misbehavior.' And I'm a big fan, so I go, 'great!' They're right. But the problem is after a certain point, it doesn't matter who's fault it is if your tool can be used in a bad way that causes fatalities to the person in the car and, once again, to people outside the car who are innocent bystanders in this, if your car is a tool in that, you have reconsider the design of that tool and you have to reconsider how you can make this idiot proof or fail safe. And whether you can exonerate yourself by saying, 'the driver was doing something bad, the pedestrian was doing something bad,' is largely irrelevant. People should be able to make mistakes and the systems need to correct those mistakes. >> But, not to make excuses, but it's just ridiculous that people think they're driving a level five car. It's like, oh my goodness! Really. >> Yeah when growing up there was that story or the joke of somebody that had cruise control in the R.V. so they went in the back to fry up some bacon. And it was a running joke when I was a kid but you see now that people with level two autonomous cars are kind of taking that joke a little too far and making it real and we're not ready for that. >> They're not ready. One thing that did strike that is here today that Patty talked about, Patty Rob from Intel, is just with the lane detection and the forward-looking, what's the technical term? >> There's forward-looking radar for braking. >> For braking, the forward-looking radar. And the crazy high positive impact on fatalities just those two technologies are having today. >> Yeah and you see the Insurance Institute for Highway Safety and the entire insurance industry, is willing to lower your rates if you have some of these technologies built into your car because these forward-looking radars and lidars that are able to apply brakes in emergency situations, not only can they completely avoid an accident and save the insurer a lot of money and the driver's life and limb, but even if they don't prevent the accident, if they apply a brake where a human driver might not have or they put the break on one second before you, it could have a tremendous affect on the velocity of the impact and since the energy that's imparted in a collision is a function of the square of the velocity, if you have a small reduction of velocity, you could have a measurable impact on the energy that's delivered in that collision. And so just making it a little slower can really deliver a lot of safety improvements. >> Right, so want to give you a chance to give a little plug in terms of, kind of, what the Auto Tech Council does. 'Cause I think what's great with the automotive industry right, is clearly, you know, is born in the U.S. and in Detroit and obviously Japan and Europe those are big automotive presences. But there's so much innovation here and we're seeing them all set up these kind of innovation centers here in the Bay area, where there's Volkswagen or Ford and the list goes on and on. How is the, kind of, your mission of bringing those two worlds together? Working, what are some of the big hurdles you still have to go over? Any surprises, either positive or negative as this race towards autonomous vehicles seems to be just rolling down the track? >> Yeah, I think, you know, Silicone Valley historically a source of great innovation for technologies. And what's happened is that the technologies that Silicone Valley is famous for inventing, cloud-based technology and network technology, processing, artificial intelligence, which is machine learning, this all Silicone Valley stuff. Not to say that it isn't done anywhere else in the world, but we're really strong in it. And, historically, those may not have been important to a car maker in Detroit. And say, 'well that's great, but we had to worry about our transmission, and make these ratios better. And it's a softer transmission shift is what we're working on right now.' Well that era is still with us but they've layered on this extremely important software-based and technology-based innovation that now is extremely important. The car makers are looking at self-driving technologies, you know, the evolution of aid as technologies as extremely disruptive to their world. They're going to need to adopt like other competitors will. It'll shift the way people buy cars, the number of cars they buy and the way those cars are used. So they don't want to be laggards. No car maker in the world wants to come late to that party. So they want to either be extremely fast followers or be the leaders in this space. So to that they feel like well, 'we need to get a shoulder to shoulder with a lot of these innovation companies. Some of them are pre-existing, so you mentioned Patti Smith from Intel. Okay we want to get side by side with Intel who's based here in Silicone Valley. The ones that are just startups, you know? Outside I see a car right now from a company called Iris, they make driver monitoring software that monitors the state of the driver. This stuff's pretty important if your car is trading off control between the automated system and the driver, you need to know what the driver's state is. So that's startup is here in Silicone Valley, they want to be side by side and interacting with startups like that all the time. So as a result, the car companies, as you said, set up here in Silicone Valley. And we've basically formed a club around them and said, 'listen, that's great! We're going to be a club where the innovators can come and show their stuff and the car makers can come and kind of shop those wares. >> It's such crazy times because the innovation is on so many axis for this thing. Somebody used in the keynote care, or Case. So they're connected, they're autonomous, so the operation of them is changing, the ownership now, they're all shared, that's all changing. And then the propulsion in the motors are all going to electric and hybrid, that's all changing. So all of those factors are kind of flipping at the same time. >> Yeah, we just had a panel today and the subject was the changes in supply chain that Case is essentially going to bring. We said autonomy but electrification is a big part of that as well. And we have these historic supply chains that have been very, you know, everyone's going as far GM now, so GM will have these premier suppliers that give them their parts. Brake stores, motors that drive up and down the windows and stuff, and engine parts and such. And they stick year after year with the same suppliers 'cause they have good relationships and reliability and they meet their standards, their factories are co-located in the right places. But because of this Case notion and these new kinds of cars, new range of suppliers are coming into play. So that's great, we have suppliers for our piston rods, for example. Hey, they built a factory outside Detroit and in Lancing real near where we are. But we don't want piston rods anymore we want electric motors. We need rare earth magnets to put in our electric motors and that's a whole new range of suppliers. That supply either motors or the rare earth magnets or different kind of, you know, a switch that can transmit right amperage from your battery to your motor. So new suppliers but one of the things that panel turned up that was really interesting is, specifically, was, it's not just suppliers in these kind of brick and mortar, or mechanical spaces that car makers usually had. It's increasing the partners and suppliers in the technology space. So cloud, we need a cloud vendor or we got to build the cloud data center ourselves. We need a processing partner to sell us powerful processors. We can't use these small dedicated chips anymore, we need to have a central computer. So you see companies like Invidia and Intel going, 'oh, that's an opportunity for us we're keen to provide.' >> Right, exciting times. It looks like you're in the right place at the right time. >> It is exciting. >> Alright Derek, we got to leave it there. Congratulations, again, on another event and inserting yourself in a very disruptive and opportunistic filled industry. >> Yup, thanks a lot. >> He's Derek, I'm Jeff, you're watching The Cube from Western Digital Auto Tech Council event in Milpitas, California. Thanks for watching and see you next time. (electronic music)

>> Narrator: Live from San Juan, Puerto Rico. It's theCUBE, covering Blockchain Unbound. Brought to you by Blockchain Industries. >> Hello everyone, welcome back to our exclusive coverage of, in Puerto, Rico for Blockchain Unbound. This is the industry conference room. People around the world from Silicon Valley, New York, and around the glove, coming to Puerto, Rico to talk about Blockchain decentralized internet cryptocurrency and really the future of society and global economic value creation of course our continuing coverage is focusing La Sierra for 2018. Our next guest is Mark Jeffery, CEO and Co-Founder of a company called Guardian Circle. Welcome. >> Thank you, thanks for having me. >> So you guys are doing something really interesting, so we, first of all, we like to geek out, as Fred say, "We're alpha-geeks." But we love IoT, cloud computing. You're doing something really interesting right now with Blockchain and this new decentralized internet around something of a critical infrastructure nature. Take a minute to talk about Guardian Circle's product, the coin, token that you're doing, and what it all means. >> So, Guardium is the token, the company's called Guardian Circle. Together they comprise global decentralized emergency response. So, six billion people on earth have no 911, There's just no magic number you can call, right? So hold that in your mind for a second. The other one billion of us, we do have 911, but it's not very good, it hasn't been really updated since the 60's. If you call 911 and if you're lucky enough to not get a busy signal, they have no idea where you are. Your location information is not transmitted. Which Uber can find you more easily than 911. Which is just insane, but that is the way it is. So, nevermind, so throw all that out >> So 911 is broken? 911 is broken. >> Yep If you have it, it's broken, and most people don't have it, so throw the whole thing out the window, let's start over. What would we build today? The way the world should work is whenever you're in trouble, no matter where you are on the globe, all you should have to do is press a button, that button sends an alert up to the Cloud, the Cloud looks down and sees what people and resources are already nearby, and then activates, coordinates, pushes all that help to you as quickly as possible. So, ten people in three minutes. That's what were, that's our-- >> So a couple things going on. So to me when you say, what should we start from scratch, put in my little operating system design network solutions add on, all kind of rolled into one as a stable, fault-tolerant, resilient, robust, always on network. >> Yes. >> Database that is fully interoperable and updated in real time of every number, every location, every persons capability to understand the discovery and resolution of a number. >> Yeah, so >> So that sounds like the internet. That sounds like the internet. >> (laughs) Well that's a little bit, probably further than we're going right now, but yes. Ultimately, you're correct. That would be the ultimate-- >> So no legacy baggage, 1960's Telco. >> No >> We're talking about immobile, in Africa for instance, there's more mobile penetration than anything else. That's what they got. >> Yes. >> So every country is their own sovereign kind of architecture? >> Yes >> Are you guys looking at it from a global perspective or regional? >> Global, so we think that, I mean, this is, this thing should be mobile native, location aware, and the alert should go out to multiple parties. And the phone number is your identifier in this system, but it's effectively an IP based system, really, so you're right. We have to balance that against privacies, so you get to decide who is on your alert grid, right? So you have to emphatically say, yes my friends, family and neighbors, and the subscription services, and if available, these official services. >> So Blockchain can solve the immutability privacy issue? >> Yes. >> The decentralized nature of network effect is a dynamic that people look for in good deals or good architecture. That's in place. >> Yes. >> People have a social graph, interest graphs connections. So the analog world is going digital. I mean, the old days was, is there a doctor in the house? But you were limited by how far you could yell. >> Right. >> So here you're saying literally, if you connect properly, the users in charge are their, their data. >> Yeah. >> They can dictate what they want to connect to, where, is that kind of how it works, is it peer to peer? >> Yeah, it's sort of peer to peer. I mean, a lot of people think, a lot of people mishear me a little bit and think that when you press that button, the alert goes out to everybody that's nearby, right? So total strangers that may or may not be trustworthy are suddenly coming, that's not what I'm saying. That is not what we're doing because we don't want to accidentally summon Jack the Ripper, like that's, you don't want to make a bad situation worse, right? So, you explicitly invite people into your protection grid, we call them guardians, hence, Guardian Circle, that would be your guardian circle. And you can have an unlimited number of them, so six, 6000, however many friends you have. Then we will also feature paid subscription services where you will be able to subscribe to, like, your local EMT collective, or your local license and bonded arms security, or if you're in a remote corner of the world, you could subscribe to the guy with a truck, who could run you down the mountain, right? When you're having medical problems. So it's going to vary depending on where you are in the world. We're also working with the Women's Safety Xprize, we're a partner, we're the backend of that prize. Which is an IoT device contest to make a panic button device, right? So when you push the panic button, what happens? It goes into Guardian Circle. >> So how does token economics fit into this? So I'm getting why it's tokenizable, How does it work mechanically? Do I buy tokens for safety? Is it like, I mean, take us through some of the use cases. >> Yeah sure, so there's five different ways in which we use the token. The first one is, obviously, to create the, to buy emergency response subscriptions. Now we're going to allow you, or provide a way for you to, as a consumer, just swipe your credit card in the app, and in the background you'll be purchase Guardium tokens, right? And it'll re-up every month if you don't have enough in, it'll be that sort of thing. So you might not even really be conscious of the fact that you're using cryptocurrency. If you are, there's a wallet that'll allow you to just use the cryptocurrency manually, the way you do any, any right now, right? >> And. >> So there's that. >> Okay so continue. >> Yep, the second thing we're going to do, we think that giving will be a big behavior in our universe, so you're going to be able to send Guardium directly to a beneficiary in the developing world. And what's cool about that is it doesn't go through a governments, a bank, or an organization. So remember Red Cross in Haiti? Can't happen here, and we're going to go even further than that, down the road, you're going to be able to track every dollar that you donated as easily as a FedEx, right? >> So you are creating a direct relationship between people who might want to help people and then a direct access for resources for the user. >> Correct. >> And so that's the primary, kind of a two >> That's one major flywheel. >> major flywheels going on. >> Just like people sponsor a child, safety is one of the biggest problems in the world. In fact, some people say, this guy named, Greg Hahn, who says it's the number one problem in the world that all other problems flow from the fact that people in the developing world aren't safe. Why don't they have water? Cause they're not safe. Why don't they have education? Cause they're not safe. Lawlessness has to be solved first. >> Trust is a huge part of this too. >> Yeah. >> So how do I set this up, where are you guys in the system, is there a product up and running, how do people get involved with your project? Take a minute to share that. >> Sure, so we have apps released today and they're distributed world-wide on IOS, Android, and Alexa. We also have an open API that lets anyone plug any alert device into our grid, obviously we have to, we want to know who you are first, but basically everyone is welcome. And so, and then our token sales site is at Guardium, Guardium.co. >> G, Guard, ium, Guardium. >> Yes, Guardium. >> And then Guardian Circle? >> Correct. >> Guardium with the m and the end of the token. What's the plan, what are you guys, how much have you raised, what's the story? Yeah, so we're selling ten million dollars worth of tokens, which represents 30% overall, 33% overall. We have a 100 million tokens in the sys, that, that's it, that will ever be distributed. It's on the NEO Blockchain, so we are, we are, we're sort of different from a lot of other folks. We're one of the very first western, we're not the first but we're one of the firsts. >> NEO has a good reputation of high performance. >> Yes >> Is that one of the considerations you had for them? >> Yeah, without a doubt. I mean, we deal in emergencies, so our tolerance for things like CryptoKitty swamping the network is very low. So yeah, so we liked what NEO had to say in a lot of ways because of that. >> I interviewed the CryptoKitties at Polycon, interesting story. It's a Pokemon moment for the internet stare. Well congratulations Mark, what's next for you guys, get through the sale, how's the team makeup look, what's going on with the company? >> Yeah, get through, I mean, definitely get through the sale is the biggest thing right now. We're a small team of, like about five people, plus some contractors. The next big thing that we have on our agenda is we're going out to India in four weeks to actually test the Xprize IoT panic button devices on the streets of Mumbai, so Guardian Circle plus device. >> Intense environment a lot of people there. >> Yeah. >> So let's talk about you. What is your background that got you here, or was there an itch you were scratching? Why this time, also the way to attract a lot of alph entrepreneurs, this is a disruptive time, but why Mark Jeffrey's, why now, why Guradian Circle, what's the passion behind it? >> So, well I started life as an engineer, but I won't bore you with all my adventures up until this moment. But in 2013, I became very interested in Bitcoin, wrote a book called, Bitcoin Explained Simply. Got the book, got the little crazy thoughts in my head. >> You're an author, speaker >> Right, same thing. >> distinguished influencer. (laughs) >> So that was sort of how that side began. In 2014, I basically, my girlfriend at the time had a stroke, she's fine, but at the time she was all alone. And she was on the floor of her garage, and I took her to the hospital, brought her back, and afterwards, I realized, she was alone for about a half an hour, if this had been a real stroke, this could have been very serious, she could have died, she could have been paralyzed. And she was drowning in help, there were about seven people who were either driving by or nearby while this was going on, within a 1000 yards. And she had no way to get to them. >> Yeah, yeah, a personal example of what you're doing. >> And I also realized, the other component was, all the help, I didn't know six, five of the other six people, they're her friends, they're not mine. But during her emergency, all of us need to be sharing location and in communication with each other immediately. And the importance of that just cannot be overstated in emergencies, seconds count. And so putting instant communications so that we can coordinate a response is the second-half of the problem. I initially did not intend to build an app. I went looking for this app and what I discovered was there are a ton of panic button apps, but all of them neglected solving the second-half of the problem, which is organizing the response. >> Yeah. >> And getting people on, in the same-- >> Mobilizing resources. >> Yeah, getting everyone into a war room without requiring them to know each other ahead of time, that was the big thing, no one had thought of that, so. >> It's like rolling up services when you need it instantly. It's like a compiler. >> It's at hawk services. >> You know, compile everything >> Yes, exactly. >> at real time assembly. >> Real time assembly, yeah >> Operating system. (laughs) >> that's exactly, it's great. That's actually a really good way to put it, yeah. >> No, but this is also pretty important, so it was a great personal example, thanks for sharing that personal story. But you know, there's a avalanches, whether you're a skier, it's people who go rock climbing, there's all kinds of use cases where a mountain biker is missing, all kinds of-- >> Remote locations are really big ones. >> I'm scuba diving, where are people, where were they last? So a lot of this is, are location based, and no one knows what the situation is, so the alerting is only one step to the value chain. >> It is, but I think, sorry you have a question. >> No, no, I was going to ask you, where does it go from there? >> Well I think, I think there are a lot of, I think safety check-ins, I think there's other things that we can do, but the one thing that, the one lesson that I've seen again, and again, and again, and again is that the companies that fail invariably, oh, the companies that don't focus always fail. So you got to pick one thing and be the best in the world at that one thing. And the emergency situation is our one thing, and that's big enough. >> Well, I think you have a great opportunity and we'll splint through the, as the evolution of this market grows, it's kind of a moving train, but the value promises is legit. I was talking to Fred Krueger, your friend and colleague in the business, it's a marketplace of these days, so it's money and marketplaces, in your case it's safety, marketplace. I could envision a day with your services where I publish and subscribe to services, I got in a catalog. >> Yes. >> Hey, I know my risks, everyone knows what they do in vanity, or risk factors whether you're jumping out of an airplane, or double black diamond skier. I would love to go to Lake Tahoe, or a mountain, or a place like this, and saying, I'm going to take some chances, here's what I'm going to subscribe to. >> (laughs) You're going to have to subscribe to some extra tokens while you're there. >> I would use Guardium. It could be more, I'm just brainstorming, thinking out loud, but I mean, that's the kind of web services framework you could bring. >> That's exactly right. >> Is that they way you guys are thinking about it? >> I do, I do, I'm so focused on this sort of food and shelter stage of our life right now. >> Yeah, get an ICO done. So yeah, we've got tons of all those ideas written done but we're not quite there yet, but when we get there, great ideas, absolutely. >> Well the use cases are changing because the peoples expectations are changing and now technology can meet these cases. So I'm seeing a lot of social entrepreneurship being done that are coming in through a funding vehicles that never would have got funded on venture capital funding. >> Totally correct. >> Whether it's battered women applications, human trafficking, safety apps, stuff that can make money, not be a kazillion, billion dollar business, but really change society and makeup. >> You've hit the nail on the head. There are a lot of Blockchain companies or ICO companies, this stuff, the venture guys, would never fund it because their model doesn't allow for it. They have, all these things have to be Facebook potentially, or they just have no tolerance for it. >> And the philanthropy world is not incented on economics, and also when the project loses its grant or funding the stack just gets thrown away. >> So this allows for sustainability for mission-based investing and developing. Slowly, I see societal entrepreneurship categorically going to boom from this wave. >> Yeah, totally agree. >> Across the board. >> The world will become a better place, we'll have better companies. >> Mark Jeffery, Guardian Circle, co-founder and CEO. This is theCUBE's exclusive coverage here on the ground in Puerto, Rico for Blockchain Unbound. A lot of great stuff here, a lot of great start-ups, investors, of course theCUBE. 2018 will be covering all the shows. I'm John Furrier, thanks for watching.

(upbeat techno music) >> Announcer: Live, from Orlando, Florida. It's The Cube. Covering ServiceNow Knowledge17. Brought to you by ServiceNow. (upbeat techno music) >> We're back at Knowledge17. Dave Vellante with Jeff Frick. Josh Gluck is here, he's the deputy CIO of Weill Cornell Medical College in the big apple. Thanks for coming to The Cube. >> Thanks very much for having me. >> Tell us about Weill Cornell, It's a collaboration with Sloan Kettering, originally, and ... >> Yeah, we're a three part, mission-oriented institution. Patient care, being first. Our physician organization delivers patient care in New York City. We're partnered with New York Presbyterian Hospital, Memorial Sloan Kettering Cancer Center, and also the hospital for special surgery. >> So, let's get right into it. CIO, you were probably doing some of the CIO activities here, this week. Love to hear about that. But let's get right into how you're, you know, using automation, how you're using the ServiceNow platform. Let's talk in the context of IT transformation. >> Yeah. So we've been a ServiceNow customer since 2012. We actually went live on 12/12/12. Everybody thought that was a joke, but it turned out to be the real "go live" date. You know, and as the platform's matured, and as our organization's matured, you know, we started focused on ITSM, strictly. Over the last few years though, we've found that, you know, our focus for ServiceNow should be the equivalent of building a 3-1-1 platform for the administrative departments. So we've onboarded folks in HR. We're doing case management now with ServiceNow. Obviously all the ITSM, ITIL-based processes. We've worked with our Department of Environmental Health and Safety. To help them with some of the regulatory compliance, about workflows that they need to have in place. We've also built out Project and Portfolio Management in ServiceNow, and we've been doing it, actually, since the beginning. We worked with ServiceNow pretty intimately to build out those functions. And now, we're actually at the point where, the platform has surpassed what we custom developed back in the early days. And we're really focused on understanding where we can unwrap some of those customizations, and just go to the native portfolio. >> Yeah, I wanted to ask you about that. >> Yeah. >> So, that's not an uncommon story and how complicated is it to unwrap that stuff? 'Cause obviously, you don't want the custom mods there if you don't have to have them. >> Yeah, well you know we spent, what, five, six years now, focused on developing the platform to meet our needs, meet our process. You know, we're academics at heart. Right, being part of Cornell University. So, I think we have a habit of sometimes overthinking solutions. So, our customizations are pretty complex. We also though, understand that it's a heavy lift for us to keep it up. So, we partner with ServiceNow, we've had them come in and help us to an evaluation of what really could be done with a slight change to our process. Or, even just direct support for our process, straight out of the box. We're really excited about the stuff that's coming out of Jakarta. >> Okay, so it's fair to say, I mean, we've all been there. Where you have software development problems, and you go "ah, jeez, I wish I had done it differently." But, when we talk to folks like you, that are unwrapping, unraveling, custom mods, there's no regrets. You got a lot of value >> Josh: Yeah, no. >> out of 'em. And now you're moving forward, right? >> Josh: Yep. Yeah we >> That's interesting. >> Josh: Definitely did the right thing, at the right time. You know, we went through an evolution, in the way that we did Project and Portfolio Management internally at Weill Cornell. And we're focused on some of the high-level problems, high-order problems today, that some organizations may not get to. Right, we're doing resource management, proactive scheduling, and you know, for us to get to the next level, the enhancements that are available in Jakarta are around time-carding and resource management, are really going to help us, I think, not overthink the problem. And come to some standard that the rest of the industry, or other verticals are using, in how they do their resource management. >> And Josh, the 3-1-1 concept is interesting. When did you go from "this is our an ITSM tool, that's going to be pretty cool." >> Yeah. >> To "this is a platform, that we can now take this kind of 3-1-1 approach, and use that as kind of an overarching mission, >> Yeah. >> for that which you're trying to accomplish"? >> I think the concept ... I think when we first went into partnership with ServiceNow, we knew that we wanted it to be more than just a replacement for heat, right? I've actually been with two different organizations. New York Presbyterian Hospital and Weill Cornell, who have come from other ITIL platforms, ITSM platforms, and moved to ServiceNow. I was a BMC Remedy customer for a long time at New York Presbyterian. We were a heat customer at Weill Cornell, prior to going to ServiceNow. So, I think we were all familiar with the fact that it doesn't make sense to buy these point products, to do all of these different workflows. Let's buy a platform. ServiceNow represented that platform. Even in its early stages, we knew that we wanted to do more with it. We had conversations about process users. And I know you guys were talking a little bit before about changes to the license model that are happening. >> Dave: Yep. >> But we really wanted it to be something we could develop further. Our first project just happened to be, in both cases "we have an ITSM platform that isn't working." Remedy at NYP, heat at Weill Cornell. "Let's get off of it, and get onto ServiceNow." But I think, we didn't start calling it the 3-1-1 until maybe a year or two ago. >> Okay. >> And it really started with Case Management. I think that was a big deal. >> It's a good little marketing, CIO selling. >> Josh: Yeah. >> You know, Daniel Pink. How large of an organization ... >> Josh: Is, IT, or Weill Cornell itself? >> Weill Cornell. >> We're between ... We're about five-thousand and change. >> Okay, so not enormous. But, the reason for the question is, at what point does it make sense to bring in a ServiceNow? You know, our little fifty-person company. You know, we're trying ... >> Josh: Yeah. But it's still not there yet. Is it size of company? Is it size of problem? What is your advice there? >> You know, I think it's actually a good idea for most mid-level companies to talk to ServiceNow. And I think there's even a play for some small businesses. It depends on what you want to get out of the tool. Right? I mean, if you're going to use it as just a simple incident-response system, which isn't really the value that ServiceNow provides, it might be a hard sell. But, because it's a hosted system, because there is such a wealth of partners in the community now, and such a following for ServiceNow, I don't know. If you were a ten-person organization and you were customer focused, and you wanted to use it to do ... >> Jeff: Yep, yeah, that makes sense. A couple of different business processes, it could actually make sense for you. >> Josh, really tight schedule today, we'll give you the last word on Knowledge17, some of the things that have excited you, what's the bumper sticker on K17 for you? >> I think the keynotes have been great. I think you guys at The Cube have been doing a great job, of also, >> Dave: Thank you very much, appreciate that. >> you know, getting people up here and asking 'em tough questions and stuff. I appreciate you going easy on me. Than you. But, it's been great. It's been a really good show. >> Well come back again, and we'll really go at it. So, thanks very much Josh, >> Josh: Thank you. appreciate your time. Alright, keep it right there everybody. We'll be back with our next guest, right after this short break. (upbeat techno music)

>> Announcer: Live from Orlando, Florida, it's theCUBE! Covering ServiceNow Knowledge17. Brought to you by ServiceNow. >> We're back in Orlando, everybody. This is theCUBE, the leader in live tech coverage. We go out to the events, we extract the signal from the noise. We're here at Knowledge17. I'm Dave Vellante, with my cohost Jeff Frick. Donna Woodruff is here, she's the service enablement leader at Cox Automotive. Donna, thanks for coming to theCUBE. >> Hi, thank you for having me. >> Good to see you, you're welcome. Tell us a little bit about Cox Automotive, and specifically your role. Are you an IT practitioner by trade, or business process person? Share with us. >> A little bit of everything, actually. First of all, Cox Automotive is a large, privately-held organization that's part of the Cox Enterprises family. We are changing the way the world buys, sells, and owns vehicles. We are made up of five key solution group areas. Everything from inventory solutions, which includes our auto auctions, and everything to get cars from dealerships to our auctions and back out again for their inventory. We have financial services, which provides floor planning to our dealerships so they can buy cars from our auctions. We have media services, which are all about how do you connect the cars that you're selling to retail customers, so autotrader.com, Kelley Blue Book are some notable brands as part of our organization. We develop software around analytics, and an ERP system for dealerships, to help them move their inventory and do their floor planning, so they can maximize sales in their dealerships. And then of course we have international. We are a global company. We have over 34,000 team members that we support. We're a very heterogeneous organization, and that can drive complexity into the organization. My role is, I am the service enablement leader. I am based out of technology, but I look at my role as much broader than that. It's about solving problems for our business and being able to deliver services internally and externally, and help the organization run more efficient and effectively. >> So you've seen, you know, the narrative in IT, and ServiceNow's described that very well over the years, IT getting beat up, and you only call IT when there's a problem, and obviously the platform and the adoption of that have changed a lot of organizations, presumably you experience something similar. So, take us back to the beginning days, the early days of what it was like, the before and after ServiceNow. What led you to that decision? What were some of the drivers, how'd you get there? >> Absolutely. Well, Kelley Blue Book was an acquisition for Autotrader group of companies about four or five years ago, and they had implemented ServiceNow as a help desk ticketing system. When we acquired them, we saw some great wins with the platform that we thought, hey, this really should be our help desk ticketing system. And so it brought under cross that small group of companies, but it was always viewed as a help desk ticketing system. Over time, just like many other platforms, it starts to get highly customized. Fast-forward to a couple of years ago, we had a need. I was supporting HR and communications from a technology liaison perspective. The problem that they were trying to solve was that they have two employee service centers, one on the East Coast, one on the West Coast, that were staffed by analysts, and they primarily helped our auto auction personnel deal with their benefits and questions around just HR. All the way down to time sheet corrections and things like that. They came to me with this problem, and they said, "You know, we've been using Remedy to some extent." We were in a transitional time in the organization where we were collapsing our help desk tools onto ServiceNow, and they said, "We need some help, here." "We just want to do a few requests." Well, we identified early on as that liaison that I really think that this ticketing platform can do what you need it do. Myself along with a business analyst and an intern sat down with the business, we understood the requirements, and that was the launch of our HR portal. While we were in there-- >> Just you, an analyst, and an intern. >> That's correct. That's correct. And we weren't developers. It was all about configuration. But we understood the tool, we understand that this is really no different than any other business process, and we set out to deliver the first service catalog around HR services. Since then, we haven't looked back. We learned a lot about the platform. We diagrammed out what was wrong with how the service desk had been highly customized, we sat down with our VP and we just showed him the diagram and said, "We think that this platform can do a lot more." He listened to us, and he turned to us, and he said, "Well, do you guys want the platform?" And I turned to my team, and I said, "Do you guys want it?" We took it on, and since then, in the last 18 months, we have expanded the platform very broadly. We've implemented performance analytics to improve our help desk services. Beyond the HR portal, we are now implementing governance risk compliance, a vulnerability management. We're now doing PPM as well. We are re-looking at our CMDB because we want to do more with automation. We've done some orchestration with storage agility and how we can get those engineers more productive by doing zero-touch ticket requests from our developers to expand file shares and to sunset file shares, or to request new file shares with other applications. >> So what'd you do with all the custom mods, when you talked about the Kelley Blue Book coming over. Did you sort of scrub the hose and start over, or-- >> Well, you know what, we took it back to out of the box, and it wasn't difficult to do. We just rationalized the things that were duplicated across requests and incident, we pulled it back to out of the box, we took an agile approach. My team now is very agile. We do weekly releases on the platform. By bringing it back to out of the box, it allows us to upgrade to the latest major feature releases within a two-week period. Because of that, we're able to adopt and consume the new product enhancements that ServiceNow has to offer very, very quickly. >> So, obviously you had success, or you wouldn't have been able to expand the footprint so radically. How are you measuring success, how did you go from a little bitty thing to a very large thing? >> I think it's about visibility. Visibility and strong leadership support, and showing how we're getting better incrementally over time. I think one of the strategic things that we've done, probably in the last six months, is implement performance analytics, which that started to show the behaviors of how people were working within the platform, how they were addressing incidents, how they were responding to our mean time to response, to our mean time to closure of a ticket, the aging of these tickets. When we first implemented performance analytics, we found a lot of anomalies in the platform. We found orphaned assignment groups, which to the behavior of the organization, they weren't necessarily working the system the way they should be. >> Jeff: Orphaned assignment groups. >> Orphaned assignment groups. Tickets were going in and they were backing up, and nobody was working them. So, allowed us to change the behavior of the organization, to drive consistency in how they were using this, which then made the metrics more meaningful. Now people are running their areas of operation from the platform. >> So the next thing I got to ask you, we talked about it in the open, is behavior. Tech's hard, but it's not that hard compared to people and process. How did you get people at that moment of truth, when I need something, to not send an email like I'm used to, and to actually execute my work through this tool? >> Well, one thing we did that was very unique, and we've continued to do that is as we roll out major feature functionality, we actually create commercials about ServiceNow, about the platform. Internally, we call it Service Station. Everything is associated with a vehicle. We've promoted our brand around the platform as well, and our brand is about doing things more simply, getting things routed to the right people, that's why it's better than email, and demonstrating the power of what it will do to you, and getting those answers more quickly instead of going to your favorite IT person or your favorite HR person. How this platform is helping you get to your answers more quickly, as well as all the self-service capabilities and the knowledge articles around, hey, fix it yourself. You don't have to talk to somebody on the phone. But we still give that personalized touch if they really need help and they want to talk to an individual. >> So really, a lot more carrots than sticks. >> Lot more carrots than sticks, absolutely. It's if you can solve your problem faster, why not? 'Cause at the end of the day, that's ultimately what you want to do. Solve your problem, and get on to the rest of your day. >> How long does it take for a typical employee to go, "Ah, this is fantastic!", and to really shift their behavior and buy in and start selling it, as your advocate? >> I think we're doing a better job now, introducing it to our new hires as soon as they get engaged in the organization, about this is your platform to go to when and if you need help. And here's how easy it is to find the things that you need. It's something that just happens over time, and I think if you address some of those small wins, you create advocates in the organization, and when they have a good experience, they tell others. So some of it's word-of-mouth, some of it is internal promotion. A big part of it is leveraging the platform to get the work done and having a great user experience along the way. >> Donna, you mentioned Service Catalog and CMDB, these are consistently two components that allow customers like you to get more leverage out of the ServiceNow platform. So, specifically as it relates to CMDB, what are you doing there? Do you have a single CMDB across the organization? Is that something you're considering? >> That's probably one of our next big transformational areas. We do have a CMDB within the platform that's been used primarily around the linkages for incident, problem, and change management. But we know that we need to do more with it, and like I said before, we've grown through acquisition, so there's a number of other CMDBs. And we are in the process of bringing that all together onto the ServiceNow platform. Because we're seeing the power of everything else that that connects to. And that's also going to be a key on how we promote more orchestration, more automation, more about the health of our services. >> So, ServiceNow's obviously promoting you guys throughout this event, showcasing some of the things that you've been doing. What've you been talking to other customers about? What are you most proud of? >> Honestly, I'm really proud of my team (laughs), because we are responding to the needs of the organization, and the fact that you can add value through what you do on a day-to-day basis is great. I think one of the most unique things that, in terms of the application, is we actually built an application for our safety auctions. So, as you can imagine, we have a hundred auctions. There's a lot of people working in the auctions. We have everything that a dealership would have, and we have lanes of vehicles running through to be auctioned off with our dealerships. So we have service areas, we have vehicles and people moving about the auction. So safety is a very critical thing for our organization. About a year ago, the safety director came and said, "You know, we have this problem. "We are doing these auctions' safety checklist "around compliance, how can we make "our auctions a safer place?" "You know, we don't have a lot of money, "but we think there's a better way to do it." And they explained the process where they had six area safety managers that were distributed across these hundred auctions, and trying to get the safety message out there through making sure people were wearing their goggles, or that they had all the appropriate OSHA standards in place. So after having a lot of conversations around this, again, we found ServiceNow would be a great solution. We did work with a partner to help us build it, but we took a very manual process and we automated it on the platform. Now we've moved the safety business process to the auctions themselves, where they own it. The general manager's involved, the shop leads are involved in it. And what it's done, it's been a catalyst to reducing our workers' comp claims. We've seen a two basis point improvement over the number of workers' comp claims, which is cost-avoidance, you know. When your average worker comp claim can be around $10,000, that's a significant saving. With a very, very small investment, we saw a 3,000% ROI on this initiative alone. We're bringing visibility to the process, using the platform and the reporting capabilities. It's gotten the general managers and the shop leads engaged and having the conversation about safety. >> This is great, 'cause you got the platform piece of it, and went from basic application delivery to seeing that it is just a workflow tool. >> Donna: Exactly. >> And the benefit of the automation, and now applying it to, I don't think they announced a auto auction safety module this morning. >> No. (laughing) >> Not yet, but we are doing a session... (Donna laughs) >> It's pretty impactful that you were able to see that, execute it with a really small investment, like you said, your initial one with you, an analyst and an intern, and now, really grow and expand the footprint within the organization. >> Yeah, it's really just about business processes in general. You've got everything you need to collect some attributes, or some information, you need to route it or get approvals around it, and then you can measure it. And you can see what's going on with that business process, and then you focus on, how do we improve the business process? The tool helps enable that and facilitate that. >> And how has the conversation around IT value changed, since you started this journey, right? >> Yeah. >> It used to be very cost-focused, I'm sure. Has it evolved to more of a, you mentioned ROI? >> It is, look at it, it's still cost-focused. It's still about savings, but it's also about how do we get things done in an organization more efficiently, with less people pushing paper, and actually focused on solving problems. And being able to measure how we get better in the activities that we're supporting. And then the dollars will follow. >> Dave: Is there a recognition in the business units, that things are changing? >> You know, there really is. One of the areas that we're starting to see real recognition is we're now dipping our toe into customer service management. We brought two platforms together with one of our business units that we acquired in the last year. They were doing some things on Zendesk, they were doing some things on another tool, and they were the same team. So, we've taken that experience, we've brought those agents onto the platform. We didn't change the experience for the customer just yet, because we wanted our agents to be very successful and help them work differently than through email. We pull those channels onto the platform, and now they have a dashboard of these issues in supporting our lenders, who are our customers. Next is really around the portal, in changing the experience for those end customers. Moving it out of the reply to all with email and making it more measurable. We've gotten halfway there, and we see a big growth area there for us, and making a better experience around our customers' support. >> And are you sunsetting some of these other systems as you bring stuff in? >> We absolutely are. I mean, our goal is to eliminate all other ticketing-type systems. In fact, all of the people that are on those ticketing systems, like, "When can we get on the platform?" "We want to be there now." "Help us get there." But bringing things together is going to help us across all of our functional areas, in supporting our customers and our team members much more effectively. It really is becoming our system of action, where you go to get things done. >> Donna, what, from your perspective, is on ServiceNow's to-do list? >> ServiceNow's to-do list. You know, and I've been pretty vocal with ServiceNow, it's like, make it easier for us to use and consume the other capabilities of the platform much more quickly. Allow us to use the great capabilities with some of our external collaborators a little bit more effectively. And I think that's where it is. I think ServiceNow does a fantastic job of bringing more capabilities and maturing all of their service areas. I like the fact that they have two major feature releases a year, and we consume them as quickly as they can send them out, probably faster than some other customers do. And continue to listen to your customers. Just, listen to what our problems are, and our needs are, and continue to answer them. They're doing a good job of that. >> Well, Donna, I have to say thanks for all the great products you guys build. The Kelley Blue Book, we've used it for years-- >> Oh, wonderful! >> And Autotrader, it's a great way to shop for vehicles. So thanks for that! >> You're welcome! >> Dave: Thanks for coming on theCUBE. >> Thank you so much. >> Thanks for sharing your story. >> Keep it right there, everybody. Jeff and I will be back with our next guest. This is theCUBE, we're live from Knowledge17. We'll be right back. (energetic music)