 I'm happy to introduce our first speaker, who has been working on open source and different technology in an organization called Accenture since 2001. Cedelo Burr is the managing director of the Emerging Technology Group at Accenture. He works with Accenture's clients to help them leverage open source in many ways to create businesses to make their business more efficient. Please welcome to the stage Cedelo Burr. So yes, as you mentioned Cedelo Burr is part of Accenture's Emerging Technology practice. I need an open source within Accenture. So I work with our clients on helping to define their next generation application architecture and really that is open source by default. So today I'm going to talk about three different things. A little bit about Accenture's journey to open source that we've taken over the last couple of decades as well as then how we then work with our clients as far as whether it be how to incrementally modernize some of their legacy systems, hopefully to leverage a lot of open source technologies or how do they enable new business capabilities that they're looking to bring to market. And then Cedelo will talk a little bit about some of the open source initiatives that will open with partners and clients as part of those efforts to modernize or to bring new capabilities. So first is briefly on Accenture's open source journey. So back about a decade or so we incorporated intersource, just about 3,000 different projects going on. Of course Accenture's pretty large. We're about, when I first started, we were about 50,000. We're about 440,000, obviously a lot of growth over the last many years. So with those, we wanted to incorporate intersource. So obviously it was a journey for us to keep up a large system integration work that we did for years. And still do, but more and more of that custom development became open source by default. So that was a big effort of ours as far as developing intersource. About seven or eight years ago we looked at our open source policy that we defined and rewrote it, really encouraged the use of, not just the use but the contribution. So as many more millennials were joining Accenture, it was important that we allowed them and really kind of encouraged and incented them to not just use open source but be contributors to the various communities out there, which I'll talk a little bit about. Also our open source initiatives, so certainly we started with intersource. Then we moved to, okay, how can we then either open source or start to work with the various open source communities and foundations. And so one of our efforts really right now is how can we start to measure a lot of those things. So we're working with chaos and GitHub and others as far as how can we quantify that. And then finally, as far as what we're doing now is really looking at kind of the diverse ways we contribute. So certainly code is one way that we contribute, but given kind of Accenture's business, our focus certainly kind of has been as this as expertise. Our roles is different as far as depending on the various duties that we play. Some of it is around doing various testing, applying different industry use cases that we're familiar with as far as based on our various verticals. Some of it's writing documentation. So I think it's important to think about it as a whole, which is, you know, for many of you are looking or contributing to open source projects or probably you're asking, okay, how can I contribute? It's not just about contributing code, that's certainly important. But also there's a lot more ways to contribute, whether it be getting involved in meetups or whether it be writing documentation or other various forms. So here's just briefly just to give you a sense of some of the open source foundations and communities and Accenture's part of this. Certainly the Linux foundation is a large asset. So back at the head summit a couple of years ago, we announced that we were becoming a Gold member of the Linux foundation. So we're the first system integrator to do that. That was a big moment. And since then, we've joined six. So more recently the CNCS, the JS foundation, really reflects the evolution of Accenture, the really kind of weird development it's going, the custom development moving from what we had about 40 or 50 Java developers now to a lot more JavaScript typescripts that reflect that as well as the broader cloud data shift. So that's a little bit of Accenture's journey. We love to talk to any of you about kind of open source and how you take that over to be your governance to others. But now I'm going to talk a little bit more about how do you work with clients? So many clients are not born in the cloud, web-scale companies, and many of them have 30 or 40 years of legacy IT. They have systems that are critical to their operations, whether it be a poor banking system, whether it be a playing system, whether it be reservations, these are the heart and soul of what makes them run day to day. But right, all these great technologies that we were talking about yesterday, the Kubernetes, the KubeLib, all these things that are going on as far as this IS becomes really a service and everything else, right? It becomes open source. They're left with no package. What about all the stuff that we already have? So that's a lot of what I've been talking with clients as well, which is a technique we'll help you to find what your next generation application architectures look like. But we recognize that you have a whole bunch of other stuff today that needs to get modernized in some shape or form at the same time that the business is not going to stop. So some of the challenges they have, these clients as far as work yourselves, that aren't born in the cloud, they have this legacy. Of course, the challenge we're looking at is the various customer expectations are changing. So the degree of personalization that a consumer expects is very center-pride. So me, for example, landed in Beijing for the first time on Saturday, the first two as far as when I got off the plane and got my bag was pulled DD right as far as it fired up and that never had taken a taxi or a cab here. But my first explanation was a cab. In fact, DD didn't know who I am, I speak English, I'm looking for a certain type of car where it takes me, and that's just by default. So that's the expectations of many clients as far as the customers that our clients have. The other aspect as far as the technology in Beijing is happening, currently open source, look at that, the amount of change that's heard, blockchain, IoT, server lists, AI, all these things are happening faster and faster. And many of the business want to take the capabilities around these but what do they need? Also, you have a challenge as far as all these emerging as far as a new market entrance. So in the case of the Marriott of the world or other large hotelers, Airbnb, coming and now being kind of the largest kind of hotel space in the world, larger than many of the largest hotelers combined, displacing them, okay, now what they have to do, as well as then the blurring of industry boundaries so you not have certainly the Alibaba, the Amazon, who started out is too long on retailing, but now it's all about okay, what else can I do, can I become a bank, can I become someone that can be a distributor of medicines, all these other things that are challenging. And then the cross-fracture. So the reality is many CIOs today don't have the luxury of getting more and more budget. In fact, sometimes it's decreasing. Their business as usual is expected to decrease at the same time they're looking to do more with less. So that's kind of the situation there. And combined with that, this challenge, okay, I want to be able to innovate more and more, is where many of them, as we call it, the discontinuity curve or IT discontinuity curve, which is okay, many of these kind of enterprises started out with good core systems. And in those core systems became modified over a year, sometimes decades. But what happened throughout that journey was new change, add something to it, customize it, whether it be a package or something custom. And so as that evolution curve happened, they were able to introduce new capabilities very easily, but there came from a point where $1 investment that used to receive $10 worth of return on investment, it now took $2 to get that savings to return. Then it's three, then it's four, then it's five. Before now, at the bottom, it's essentially where it basically becomes a point where business cases are no longer able to be done, because it takes as much as not more to make changes. The only thing we do is do the regulatory and other kind of things that have to do pipeline. At that point, essentially, the IT organization becomes bankrupt. In the sense that they can no longer do any changes besides this regulatory one. This is a place where a lot of our clients find themselves in struggle. So how can they do this? They no longer have these hundreds of millions of dollar programs anymore. Business wants to build these minimal viable products, get out of chains quickly, bring new things to market, but at the same time, we're sad with this legacy IT, these monolithic systems in some cases that are very difficult to make changes to. So what they need to do, ultimately, is what we talk as far as looking at their systems, is how can they unlock that data? A lot of times, whether these systems aren't as very agile, they may be doing as far as millions, trillions of transactions in some cases, they're great, difficult to make changes to them, but they have data locked inside of them that are very valid with other aspects as far as what was being built to get access to those, they would be very attractive. So a lot of that is how can we unlock the data in these various monolithic systems? How can we then start to build services that provide those capabilities that we want to be able to build on the edge? The systems of differentiation, we still want to have those core systems, and those core systems are going to evolve ideally, whether it be okay to be able to modernize them to either get them back to the point where they are going to do their core function and not to those other things. It's probably built better as micro-services as other things that are very nimble and be able to make those small incremental changes. Or let me move to SAP. We keep to the point where this is something that when we built this 20 years ago, this was really differentiating, but the reality is now this is 95% of what other businesses in our industry use as well. Okay, that makes far more sense to you. Let's go by SAP for that. Let's focus on what we're going to discuss as a system of differentiation. But how can I make that incremental journey? How can I unlock that data? How can I start to build services that I can make those small incremental changes to incorporate new business capability? Maybe slowly evolve some of that legacy system to more of a micro-service cloud-based of architecture, but at the same time be able to move on to solve it, or maybe even place those legacy systems over time. So this is a little bit what the journey starts to look like. So you have that core system, it's kind of built, it's kind of expanded. Many, right, it's kind of how can we unlock that data so it's an introduction of a data lake, and maybe start to create things or add things around automations like RPAs or Vodacross automations, right, they also start to take a little bit of the journey to cloud, right, whether it be private, public, just cloud in general, they start to do that journey, right. So that's the first step, incorporate it into data lake, start to build a bit of a services layer, but then that the next step really be how can we, and this is where it gets to be, reactive of an event-driven architecture, which is really where we see kind of the next generation applications going, right. So it's really how can we now take it's kind of that next step, how can we make these systems more effective, an event-driven meaning, okay, that we can have things happen asynchronously, everything can kind of interact with each other. We don't have to worry about all those interdependencies that was really the problem with some of those monolithic systems that have all these interdependencies, they're difficult to make changes. So that's where we want to get to, we want to get to more of a data event-based approach that we can have those services that are completely independent, we're still being able to access the data, which is great. But how do we get there? What are some of the building blocks to get there? So one of those is to use a change data capture approach. The idea is, okay, all these monolithic systems, how many layers they have within them in the different kind of integration points. The reality is that all the data ultimately triples down some data source, right? The idea of being kind of in a the true kind of system of record, it gets persistent, right, it exists somewhere, right, whether it be a mainframe, whether it be a distributed system, it gets persistent, right? And if you can capture those changes, right, if you can change data capture approach called CDC, if you replicate that, now you can start to get that ability, if you can unlock that data, if you can unlock that data, okay, how do we now make that more event-based? So using event screening technology, whether it be cops or other data streams, right, putting that, you're kind of making that now being able to push onto those event hubs of respect, right? And if we have then micro-services that we can build on top of those, right? But the trick being, okay, everyone when we talk about micro-services, they're like, yeah, reactive architecture, but, you know, working with events is kind of hard. It's the same challenge on the UI. It can be great to be able to have asynchronous events flow through the systems, okay? But, okay, that's very difficult to do. So we're going to continue to do kind of a similar, kind of more surface-oriented architecture that, you know, still is more about the layer if you kind of have various levels of integration and various kind of consumers of those services have to know who they're calling. And really the shift is, okay, how can we get those to be, how can we make it easier to be event-driven, to consume events, to push events. And so that was really the challenge that we kind of solved with something we call the reactive-interactive gateway. So the reactive-interactive gateway basically makes it very easy to consume events through a whole series of different protocols, whether it be Spark or HGP, whether it be over WebSocket to others. And that's what enables, basically, kind of this picture, which is the idea, okay, if we can have legacy systems that we can start doing, we can have micro-coach to push those events, have something to then put those events onto an Event Hub stream. Okay, great. Okay, now that we have that, we can have micro-services that we're building new capabilities around. Or taking legacy systems, right, that we're going to say, hey, this functionality, here, here, and here, we're going to rewrite that using the main-driven design, right, we're going to now define this into a main, and a fit, and a micro-service. We're going to plug it into the Event Hub, right, and we're going to start to consume that. You know, that amount of systems, or at least a good portion of it. And that's really kind of, depending on what really is a core piece of functionality, what's really, you know, kind of some of that band-aider, that kind of, you know, that star, right, that probably shouldn't have been there in the first place, but it became technical data at the time. We had done it the right way, right, in new technologies. We could have seen it in the future. Who would have built this micro-services the years back? The UIs now, like, the challenge there is, okay, if you want them to be able to just consume events, right, we don't have to pose the complexity of having single-page data tasks to be able to consume events. So that's where RIG comes in. It could work with API management products out there as well, but it basically makes it very easy to do, and can do it at a very large scale. And then, also, you have these very notification services and other common services. Okay, this is, normally, I do a demo, but not today, as far as I didn't have time, but certainly love to show it to you. But basically, now that you have these events flowing through the system, right, everything is down in the vent, whether it be a key source that's happening on a single-page deck, whether it be something that's happening when you push the legacy system that's not being pushed into the Event Hub, whether it's a micro-service, everything's talking in the vent. Right, so now you can plug in if you have machine learning and other things, the things that are going across the Event Hub. They're very serious, right? You want to do kind of real-time fraud analytics, okay, you kind of dexact action, whether you want to do all these very sort of cases, right? And the beauty of it is, okay, we did nothing to interdependence, right? And I think you can plug into the Event Hub and start to assume the vent or admit it then, right? Everyone can then, you know, benefit from the Event Hub. So that's where the future is. That's a little bit of what we're taking it. A rig again, the Reactive Interactive Gateway, based on a number of technologies, just actually, this week, it just became a project in TSCF, as far as it could be a project. So, certainly, go check it out as far as it's open source. So, it's something that we want to work certainly, you know, with the Broadband Cloud Foundation and the broader kind of open source communities on it. We think it's quite powerful, right? So, like I said, it can consume ATT, pastas, kinesis, we're working with all the various other cloud providers, saying what other things that we should be able to provide. We're working with the project as a managed service around cloud providers. So, certainly, go check it out. Certainly, looking forward to talk with you as far as the remainder of the day and certainly kind of in the broader landscape as far as the market place in the future. Thank you.