 Good morning. We're not doing any live demo, so nothing can go wrong. That wasn't our music, right? That was not our music either. We picked the music yesterday. Those guys up there will get to hear about that later on. To get started, I just want to go down the line. It's not something I want to do for the whole panel, but just for this one question. Talk to me for a moment about why you chose Cloud Foundry and how many developers do you support at this point? And why don't we just go down the line and start with our friend from Boeing? Sure. I'll get started the other line. So at Boeing, I used to run the Enterprise Cloud services prior to taking the digital transformation environment and one of the things that we really wanted to do was to really focus on the real transformation, which is with people. So getting the culture changed, getting us more agile, leveraging some of the lean principles that we already love and use for the last few years. So what we wanted to do is we wanted to focus on the people by making technology abundantly easy to use and the first things that I've done is implement the Cloud Foundry with a pivotal distribution as well as get a DevOps tool chain in place. So that really helped us transform the conversation from which technologies to use, which containers, like how to deploy cloud. It became more about how do we actually focus on the business? How do we focus on enabling delivery and the velocity? And we did that actually within the first 80 days we had our first production Cloud Foundry implementation with all the processes as well as our first full end to end DevOps tool chain in place. So we can focus on developing code at the rate we need it. And I think you asked about the scale as well. So that started about 650 days ago and that's about a year and a half. You're counting? Yeah, we're counting. We have a website we count every day. So we went from no users in Cloud Foundry to now about 2,000 users and several thousand application instances, and I think that's about a thousand production applications. And we checked a couple of weeks ago. I was at spring one and we checked the push on a Friday, which is a slow day for us. And we had over 300 pushes to production in that one day, which is pretty amazing for Boeing. That's scale. Yeah. So we use Cloud Foundry at FISAV to underpin our Finkit platform application runtime. And that was driven largely by very similar drivers to Ennis there around an older legacy platform where change and release is were kind of on the quarterly, monthly, possibly annually type basis. And clearly that wasn't a model that was satisfying for us or our customers. And so we were looking to move towards a model which is supported by Cloud Foundry, which helps us to engage better with our development community to be able to deliver change more quickly. We've enhanced the Cloud Foundry kind of application runtime with our own developer environment with an application term developer tool chain and a developer pipeline so that we can push that change now rather than quarterly, six-monthly yearly. We're now making, you know, several hundred changes a day. So it's a massive step change in the way that we work. Me? I guess I'll talk not only about Cognizance usage of Cloud Foundry, but how our clients are using the software. I can't believe I didn't tell this funny story yesterday. I flew in yesterday morning from the US, super jet lagged and jump into a cab and if you've been in a cab here, it's like a, you know, a breakneck experience. We were left and right and up and down roads and all over the place and I was terrified. Where did that cab driver take you? It was coming from the airport. It was like fast and furious. I was like, this is insane. And it got me thinking that, you know, I'm in this cab and I'm feeling terrified and when I talk to our clients and I meet and talk to people about their transformation and their adoption of technology, they kind of feel the same way. They'll talk about their legacy portfolios and then we'll say, how do we achieve outcomes, better outcomes, velocity, value? How do we take all of this value that's locked up and drives revenue for our business? How do we take that on a journey? And then in the process, how do we, you know, redefine those user experiences and go to market more competitively? So we're all in this kind of breakneck, you know, technology adoption and it is all about velocity. We've got to be able to go fast. And when I think about what we do and what we all do in this room, we lead transformation in a time of relentless change. And, you know, if you take the train home tonight, because you're afraid to take the taxi and you talk to someone next to you and you tell them you lead in a time of relentless change, they're going to say, wow, that's exhausting. And it is. So how do you make it less exhausting? By embracing a technology, by embracing a platform that enables velocity, cloud portability and flexibility so that you can focus on your business outcomes. That's what Cloud Foundry means to us and our clients. I took the bus from the airport. It was very pleasant. Maybe that's more like Cloud Foundry. Mickey, when I think about government, I don't necessarily think about speed and fast. Why did you choose Cloud Foundry? So the answer to that is the bit of government I work for, GDS. We started like six years ago with a mission to digitally transform government way back before digital transformation was the current big thing. And so, for us, we got into Cloud Foundry when we were, we are the small bit of government. Government is 500 times bigger than us. What do we give them as a platform that they can run things on in a modern way? Cloud Foundry was easily the most mature and secure option at the time. And we think it still is. So we have hundreds of apps, no good idea of developers but hundreds of thousands. And yeah. It just works. It's going well. Yeah. The interesting challenges when it comes to legacy stuff, naturally, partly because we've been successful, other government departments have found modern platforms to host their own huge projects. But as I'm sure people at Enterprises can appreciate, most of the projects out there that are important aren't that huge. And so we offer a well-supported platform for those services which aren't huge. But they're still quite important. Yeah. You guys are just starting out. Yes. In Thales Digital Factory, we started the journey maybe one year ago. And we bootstrapped our platform in January last year. So we are really at the beginning. But we choose Cloud Foundry because it's a major platform used by big industries and Thales. We are a big industry. We have critical payloads that we have to host and to run for our clients. And Cloud Foundry has a good solution. The solution that provides the right level of security, the right level of configurability. And what we target with that is to reduce the time to market of the applications that our software team provides. So before using such platform, the time between the start of the project and the real work start was maybe four months to order the server to get all the authorization and so on and so on and so on. Now we're able to kick start a project in one hour as soon as we have the project request. And the software team can push its application after one hour. So that's really something that works. Also we want to increase the developer productivity. What we don't want is that developer talk about infrastructure on, let's say, waste time on boilerplate code instead of focusing on the business code. So why we choose Cloud Foundry is because the developer just push a binary and then it works. Does that forget how? But it just works. Good. And consistency of deployment across Clouds too, right? It's also important. And I know at Boeing you use lots of different Clouds as well up to the point where it's painful, I think for you, right? Yeah. I called it yesterday. I think we were Cloud poor when I first started in 2013. And now we're at the point of we signed contracts with all the three big Cloud providers. One we use more heavily than the other two. And then we now have VMware based internal Cloud that's been running for a little while. And then we're also, we have OpenStack. So we are now at least five Clouds and we're also looking at another deployment of container service. So yeah, we're Cloud rich right now. And one of the things that I think that was mentioned earlier that Abby covered, it's very important that as we're getting Cloud rich, a lot of us are getting the push and demand from either our internal customers or just the different technologies. It's important these open source projects to work with each other. And one of the things that I really like about Cloud Foundry and the focus with Pivotal is to really make it easy for the developers and business to adopt technology. So the more of these variations come in, we, I expect more of the open source communities to work with each other and make it easy and continue to make it easy for us to consume the Cloud and not have to jump ship into another Cloud that just will take us back a few years. Now, I think the adoption of Cloud Foundry is also we see it organic, you know, as developers and people are exposed to technology. And they're experimenting with new technologies. They kind of begin from the end. And the end is how do we deploy this quickly? And how do we get user feedback and ensure that the user is omnipresent? And when you think from that point of view, you sort of back into solutions like, you know, Bosch and you think, how do we deploy this to multiple clouds in a consistent way? You know, as fun as it is to carry a pager, nobody really wants to do it anymore. So you're thinking, how can we achieve that same, you know, rigorous SLA across all these different clouds, but the same value and the same outcome to users. So in our experience, it is people fall into it organically as the right tool for the job. I think also as well, I think it's really, you mentioned Bosch there and using Bosch to manage your Cloud Foundry foundations across multiple clouds is awesome. But the extension of that part of the Cloud Foundry ecosystem can actually be extended beyond Cloud Foundry, right? And so we're kind of, if I said, if we're using Bosch to actually manage our non-Cloud Foundry parts of our tool chain as well, which is great, you know. And so all of that stuff about, you know, not worrying about counting a pager and being able to autonomously update our entire estate within reason using Bosch is incredibly powerful and another reason why we're so engaged with the Cloud Foundry community. That's a great point. Do others do the same here? I know you guys love Bosch. That's the first thing I heard about you. Love for Bosch, but Mickey, do you? I guess we've tended to make pretty like use of Bosch in that it's an incredibly powerful tool. But as much as possible, we have other people host things like databases and so on that otherwise we'd have Bosch host. Actually, we've worked with other governments a bit on creating open source service brokers out there to use. And I think for us that's taken away from Bosch usage a lot, because a lot of things we'd use Bosch to do, we can pay other people to do better. Wow. Mike Draup, he said it. Do you take that as a personal affront? I think not a personal affront. I think it's horses for courses, right? And it's really easy to get engaged in kind of flame wars about what's great technology and you've got to do what's right for you and your organisation. For us, our default go-to is Bosch for pretty much anything. We're not dogmatic about it. If it's not a good fit, we won't use it. But that combined with concourse means that we're running seven foundations and a number of other kind of built tool changes with a team of about nine people. That's the win. And I'll pile on that. I intentionally don't want to talk about specific components because it gets into personal traits and interests. But the thing that I like about what Bosch provides is we have about four people and there weren't even full time until we became fully cloud rich. Now we're going to need a couple more. But less than four people, four FTEs to support a couple of thousand developers and fully automated. Our security actually loves Bosch more than anyone else because it automatically repays the virtual machines all the time. So it helps us with our security posture as well. So it's just economics. That security point is a really good one. So the specter meltdown thing that came out a while ago, we were able to patch our entire cloud foundry estate in like a day. It was a click of a button. I think it's funny because it is almost like a religious conversation right sometimes and you land on the wrong side of that discussion. But to me it's about like it's always about value. And there's more than one path to the cloud. And the spirit of DevOps to me is really accountable teams who have the autonomy to make decisions. And certainly we are all biased towards Cloud Foundry. We think we understand and have experienced all the benefits. And they do eventually too. But not everybody starts with Cloud Foundry. Not everybody starts with Bosch. Sometimes you have to go through that learning experience, trial and error, and find your way from the dark side. We absolutely didn't start with Bosch. So we went with one of the managed service providers initially. And we cut our teeth on Cloud Foundry that way and built out our pipelines and engaged our development community. And then we realized after that what value Bosch could add. It was hard. Right. And it's kind of the day one Bosch story is fairly gnarly. But I think the kind of wins that you get on day two are worth the pain. Hang in there. No. Nicholas, you're coming in as kind of the freshest user on the stage here. So you're benefiting a little bit from their pain. Do you still in starting up what kind of pain points that you experience? Maybe some pain points. At the first day of Bosch, I completely joined this. The first day of Bosch is complex and it's hard. It's tough. But at the end, for the availability of the platform, you see the results. So you mentioned the old patching of the platform. We didn't say it because it's obvious. But we have to remind that it's without any downtime. Just that's a real value for the platform. So yes, pain points is the curve to learn stuff. So learn Bosch, learn the old Cloud Foundry ecosystem. It's quite complex. But after sometimes, so we have now maybe nine months of existence on our platform. We have application in Prod's. We have no major incident in terms of security, in terms of just operation of the platform. So that's we are really satisfied. You know what else too? I think you're just getting started. And for anyone who is getting started, when you think about the myriad of choices you have to make, all of the options, containerization, platform deployment mechanisms, and then you think about the most important one, which is the people. And how do you transform those people and expose them to technology in a way where you have some guardrails, yet you still have the flexibility. This is where in our experience, we have seen the strength of Cloud Foundry really shine. It enables you to go fast and experience value. And at the end of the day, revenue is still the score card, right? So we still have to deploy our applications. But it diffuses some of the complications and some of the traditional slowness in building your own platform. We're spending five years building a platform, and then you realize you're the only consumer of that platform. Now, you're hinting at the culture change that comes with implementing something like Cloud Foundry, which is not easy on everybody, especially maybe in the government, for example, you might. Well, I think when we were chatting yesterday, it became clear that all of us have experienced big internal debates as to what direction people want to go with our infrastructure. Cloud Foundry offers some wonderful abstractions. They're quite amazing in terms of what they offer you, whether it's, say, something like running your own Kubernetes, you have loads of choices to make. Some people like that, but whether making those choices delivers value, it's like we're still trying to decide that ourselves. I think one of the things, Boeing being a government contractor, one of the things that was important for us is the culture change, as I mentioned. And what we were able to accomplish by making technologies that are used and abundantly available, and in fact, we made it free as well internally. We focused on the culture and what that did is we transformed and formed a different business and IT working relationship, co-locating and solving business problems. And in fact, our business in the next generation airplane development programs and other key developments that I can't really talk about, that we're leveraging this culture. Please go ahead and talk about them. Yeah, well, then I'll have to, anyway. But we're leveraging it to really accomplish the velocity on even non-traditional, non-software areas. So that's been pretty fruitful for us. And I just have to put this plug in. We are hiring across the globe. So please, yeah, let me know. Anybody not hiring here? We're hiring too. Everybody? They're all hiring. There you go. And I'm afraid there's a big sign here that says our time is up because they only gave us 20 minutes. Thank you, guys. I know there's about 50 other topics we could talk about, but we'll just do that next time. Thank you.