 For our next presentation, we will have Johan Krebbers review the OFP strategy and what is going to be our high-level direction, along with the links to other systems and entities, and also provide a high-level main road map and the steps to that. And for those of you who are just joining us, or were not on earlier, Johan Krebbers is one of the co-chairs of the OFP. He is also the IT CTO for Shell and is accountable for defining and driving the future of IT strategy for Shell. In addition, he maintains an active link with external parties and in particular startups. And Johan is based in Rijswijk in the Netherlands. So Johan, if you would like to continue. Okay, good afternoon, good morning, good evening. Yes, Johan Krebbers out of the hay, close to Rijswijk. Let's talk about strategy and a little bit about the thinking behind it, what we're coming from, what we're heading for. This is the normal architecture picks we show when we talk about open footprint. And I won't go about the architecture, we'll talk a little bit about the thinking behind it. First, you see the gray space. And the gray space is really what the applications are. And the open footprint does not include the applications itself. It's important that our focus is really the data part, how to load the data, how to protect the data, how to access the data. But really if people, what people really can differentiate and shine is of course in the application part. So we really expect companies to come out there, start developing applications on top of their open footprint APIs. That whole ecosystem is very important for the future of open footprint. But that whole ecosystem will also enrich the platform over time, will also give new facilities to the platform over time. So the gray part, although we don't talk about that much because it's a little out the side of scope, open footprint. It is a very important element of open footprint. And we try to simulate that, stimulate it as much as possible that people start developing applications out there, small company, large company, etc. And because the APIs and of course the data below the API is all managed by the open footprint forum. So that's kept independent of any provider out there. The other point made a little bit by Sammy about an hour ago is around, okay, we have here open footprint. And you saw the slide from Gorma a couple of hours ago, where he showed this sitting around the world. It's also very possible. We are also very keen to move to what I always call the open footprint inside story. And Sammy was hinting at that. What we mean by that is really that companies can be any company out there, I won't mention names out here and say, we'd be taking on the open footprint standards, the data definitions, the API standards and embedded in our own platform under our own name. But under the cover, you have open footprint with the standards and the way the data is stored in the standard way, the way it is actually the standard way, but on the outside, it might have a very different name on the box. So that's what we call the open footprint inside. We're also keen for that whole way of work because we also see, also what started happening, that this type of data, the open footprint type of data, so the GED data or the ESD data, more or more becomes part of your normal data platform. So today in this picture, you see it very much as a separate environment, but you can expect, really, you can expect that over time, it becomes more and more part of your standard data platform where you store your business data. You also expect to store your GED data. You also expect to store your EED data. So that's really, you can expect that we see that happening over time and we also will be ready for that. Therefore, we have to be ready for that, what are called open footprint inside story. I won't talk about the blue part because the blue part has already been explained by Surabh the whole architects of power. I want to make a little bit of what we're coming from. There's a little bit of history. If you're also a member of the OSDU forum under the open group and Heidi was in the introduction, was talking about also OSDU forum, then you see a picture, not this similar. And under the cover, we've borrowed a lot of what we call open source facilities from OSDU and how we use that in the open footprint. That gives us more speed. It gives us more flexibility to really get something out quite quickly. That doesn't mean that OSDU and open footprint, therefore, is geared towards one industry because it's not. As explained by Gorma, the pinning of open footprint is that it's industry neutral. It can work in any type of industry. It's not expected to work in a certain type of industry at all. So let's now go further to a little bit of what our overall target is. So we're covering two things. We're covering, of course, at the moment. Our first focus is the whole store of WWF DAG, so scope one, scope two, and scope three. And you've heard about it from a number of players already was meant by that. But we're also looking at the non-GSE scope. So like landfill, water, pollution, etc. That's not our first priority. Our first priority is really address in open footprint the DAG scope. Our second priority is also addressing the non-GSE scope. So we want to bring those two worlds together into a single open footprint data platform, so both the GSE world and the non-GSE world. So it's important to keep in the back of your mind. At the moment, our focus is mentioned in the GSE scope. We're talking about open footprint inside scenarios. And you also heard about Sumuli about reporting. One of our project is really very much so that open footprint becomes really the reporting source of information for reporting status out there for cells B, for WWF, for other ones, for WCSD. And you've heard from Anna about WCSD and we're going to talk later on how the two fit together and where they come together. But we really want to really see, hey, how can we make life of cells B easier? How can we make sure that we get them seamless access to our open footprint environment? So how can we make sure that the open footprint APIs and the cells B reporting input, for instance, are well aligned? So these are things we also are taking into account to really make that world a more seamless world. It's not in place today. We, Sumuli and his team, started discussing next week on Monday, June 28, the first meeting with cells B, okay, how do we bring these two worlds together? And the last one is very important. And then somebody made it earlier today, Anna made the point. We talk about carbon footprint. We talk about this whole world of G and C, etc. Let me also honest to each other. It's still a very immature world. When we started in August last year, and we asked all our members, how are you doing your reporting on carbon footprint at the company level? All of them was purely done based on calculations. None of them were measurement and a calculator was a spreadsheet at the enterprise level was anything under the sun you could think about. That's where we are today. So when we talk about things like over footprint, we have to ensure that it supports that world. And therefore, you also sort of saw it from Surab, we are entertaining a user interface for people who still do the calculations, and that you can easily access the data into an open footprint environment. So we have to, we have to entertain the world of people to measurement. And we have to be ready for a world where people say, so people do calculations, and we have to be ready for the world where people do do measurements. And I'll come back to that measurement story in a moment. Both, of course, there will be a trend to go from calculation to measurements. And the measurements also will change over time. But we should not forget those with MVP one, we will, we have to support people who just do calculations, and it will for some years to come that won't disappear tomorrow. And that's part of our design. And when we thought about open footprint, we made very clear, if we look at MP1 and we see the demo tomorrow afternoon, by the team, you also see the very clear that we have clear support there for that whole story of calculations. And the last point, and we do the market flexible to future, who knows what will be there in two years from now. This whole world is exploding. It's all over the place. And then stands are coming on a day-to-day basis. So we have to be very, very flexible in our thinking, in our design, in the world, when you listen to GOMAR, we have our main concern, our main concern is the flexibility of the data platform, the data model out there. But we will, we do not know what's going to hit us tomorrow, or the day after, or the day after. And we still need to be ready for that. So that last bullet point, they matured to the market, which I spoke about, and secondly, the whole area of, okay, but how do we flexible for the future? Both we need to cover, and both we need to take it to cover. We talk about the strategy from day one. We thought about it, that that's why the choice of the data platform was not something we did on a Friday afternoon at five o'clock. So let's go for a data platform. We need a database that put a database in there and we're done now because flexibility, flexibility and flexibility is important. So it gives a little bit of context where we're coming from and you can bet your money that we still have some things wrong. So I'm fully aware of that. But we go for it. We take our, we take our chances. We take our decisions. We're making very clear decisions. We might have to change them over time. I don't need to explain to anybody of you what scope one, scope two and scope three is all about. From a strategy point of view, our first focus was to get scope one and scope two on the move. So MVP one, a minimum available product one, which is out there. The focus of that was, okay, how do we cover scope one? How do we scope scope two? Scope three was not part of that. That's really what we did, but really say, okay, that is really the basic scope one and scope two. Then with mp2, you're going to hear about it tomorrow, what we do in that space. But mp2, it's really what we add to scope one and scope two, the calculations and I'll come back to it in a moment. Plus, we add a scope three to that space. And of course, scope three is a very interesting one. If you talk about scope three, you talk about many things you need to cater for. You need to cater for loading data from your scope three counterparts. There's a whole raft of systems you need to have around it to make scope three viable as part of your open footprint data platform. But that's where, and of course, if I come back to do what we do beyond that in a moment, I will, this is a lot of that has been covered by Surab, but a couple of things important. First, the underpinning of the open platform, data platform is open source and also standards like for use authenticates is open and de-connect. Standard every enterprise using, every company is using, it's a standard way of doing things. So we want to make sure that the threshold for getting open footprint to be used in your environment, small or large, and we talked about small environments a moment ago, is very low. We have to make sure that inside the data platform, we can support any type of metadata out there. Because metadata, if you heard before, is the crux of the whole data story. It's the crux about the lineage of data. How do you maintain the link between your raw data and your calculated data? It's all about metadata. Maintains that link for you. So that metadata support in the platform is important. I won't talk about reporting because you heard an excellent story from Sumali about reporting a moment ago. So we talked about open and de-connect. You've heard also talking about auditing and talking about accounting. We've kicked off a project and also to really support how we do the whole world of accounting and how we link this to the whole world of audit, trails and logging. These are important components because accounting piece is very important because they haven't embedded as part of the platform. So that's what we've just kicked off as part of our MP2 and MP2 activities. So it's all about, what we do is very incremental. We really want to make sure we get something out and then we build on top of that. We build on top of that. We know where we want the head form, but we're not going to do the one goal because we will never get there. So it's really incremental, get it out, get feedback. Incremental, get out, get feedback and start implementing and improving one after the other. Some of the other points of slide have already been explained so I won't talk about it. Let's also talk about an element of the whole open footprint. We want to have open footprint out over time on multiple platforms. So we have running on, as somebody mentioned before, we have running on IBM, on IBM cloud or Microsoft cloud, on Amazon cloud or Google cloud and other environments. I just made these as examples. They all will be running open footprint. We have to make sure that these versions of open footprint are 100% aligned so that we need to all be part of what we call the common code base, the common code between each of the platforms. Why is that important? That's important for anybody who develops an application or the open footprint platform. As mentioned before, if you open and if you develop an application in the gray part, you want to make sure that that application works on any of the open footprint implementations as an application developer. You don't want to worry about, oh, there's an open footprint implementation on IBM, oh, there's an open footprint implementation on Microsoft, oh, there's an open footprint implementation on something else. You do not care. You have developed an application against open footprint APIs. Your application can be running on a PC, your application can be running on an on-premise system. I don't really care and you should be able to access to make use on the change of the application on any of the open footprint implementations. So it's important for us and a part of our strategy to keep the open footprint implementation across the underlying platforms 100% the same aligned and the same. So this is all part of the whole release strategy. So it's important that we talk about open footprint. You don't just talk about I have open footprint on IBM or open footprint on something else. No, we always talk about we have open footprint in any platform and we have to make sure that an open footprint is aligned on any of these platforms from an application point of view. Because in the end of the day, why do we also do open footprint to give access to rich and innovative applications who can do very intelligent things with the data in the open footprint environment? And of course, but also the second bullet point over here is a little bit about, okay, what about data? As I mentioned in the beginning, we have to make sure we can cater for we can cater for for people who do that the calculators of data. Yeah, just calculate the data. So that's a one in the spectrum. We also have people over time, if you think about scope three, if you think about scope three, we're collecting data from various supply thing companies. It was not to find a future that date will be collected via sensor in the supply chain that date will be connected will be sent via IoT directly to your open footprint environment to be loaded in the open footprint environment. So in one hand, you got your manual data coming in via the calculations. On the other hand, you get your IT data coming in. And we have to cater for both of them for both extremes, of course, and the letter is not there today. But let's talk and let's talk again. He wanted two years from now. And let us be there because it will be, we will find ways to quickly collect carbon data for your supply chain. But that is essential to make this a sustainable environment out there. And both we need to take into account. Yeah, we talked already about the scope. I already mentioned a little bit about scope three a moment ago. Good support of scope three means I need to be able to think about scope three. You need to be able to load the data, give example of IoT over time. There's all by your scope three environment into your own environment. You can also have the other way around. Of course, you could say that whoever runs the scope three will go out there to eat the parties who runs their supply chain on by create that scope three and collect the data in the other way. So there are different ways of starting collecting that data out there. And really is that's really we need to further work out. Another element that often people are say, hey, what about blockchain? Because we would expect that you need a proof of origin. You have to prove that the value you put in from a carbon footprint is really the real value. Because today I can put in any value. I can put in 100. I can put in 200. But there's no proof of origin. And people say, oh, you need to have blockchain in here. And of course, I need over time, I do need to come to a model where I have proof of origin. But as I mentioned, when we start off this whole exercise, if we need to walk before we can run, today, we often still calling blockchain to me is running. So do we need over time something like blockchain from a proof of origin point of view? Yes, we do. Do we need today? No. We need to be ready. We have to make sure we can call Kate or sometime in the future. Our strategy has to include it, but not today, given the environment we're in today. So we need to be ready for the future to clearly get there. Let's talk about the calculation services that will be session tomorrow. This is from William Fox and one other person who will clearly talk about the calculation services. Calculation, of course, we are including part of NP2. It's quite a challenge to really introduce calculation services. Because if you think about it, in our environment, the calculations could be on the one hand sitting totally inside your open footprint through the total calculation engine could be part of open footprint. On the other hand, we would say everything sits outside open footprint. And all that open footprint does, in open footprint, you do a call to an external calculation service. Calculation is being done. You get results back and put the results back in open footprint. There are two extremes, but both we need the support and there will be a number of hybrid versions in between. The calculation engine will, of course, grow with business rule services. The business rule service really will pull this whole story together. We are in the beginning of starting to implement these scenarios. You'll hear tomorrow an excellent story from William on where we're coming from, where we're heading for, and how we see it as developing. And what the challenges are to introduce these calculation engines inside an open footprint environment or have it referred to external services, as just explained. Then the other bodies. Let me focus a little bit on WCST. We've got Anna giving an excellent presentation around what's happening with WCST. And then people say, well, okay, your open footprint and WCST are working close together. And we do. Once a month, we sit together for at least an hour, if not longer, and really a technical detail how we work together. I see two spaces where we can and will work together. The first one, open footprint will be used by, by supply chain companies. So if you're, if you're part of supply chain, you can store your carbon footprint calculations or your product results immediately into open footprint. Because if you're an open footprint company and you're part of supply chain, then of course you can immediately store your supplies and contributions in your open footprint implementation. And then WCST could come along with their solution to extract, to extract the relevant carbon footprint data via the open footprint API from the platform. So we can ensure that so that the open footprint from a certain supply chain company is the feeder for WCST. So that's one interface. That's the one end. So that's one interface. The other interface, I could also be in that same story, I can also be the scope three party where I'm the scope three party where I'm the open footprint, also using open footprint. That means that the result, the total results of WCST when you collect all the results of supply chain, the total results can come into data, data session services into open footprint of that scope three party. And again, I can make sure to make this seamless experience that our APIs are well aligned. So our thinking, our, our work we're doing with them is we need to make sure there's no, that those two ends of the spectrum are well aligned, that our definitions are aligned. And that's, that's really at the beginning of that story was, okay, we have defined our APIs, we have defined all of things, they still have to do it, they have to make sure they're well aligned those two stocks. So we see a clear link over there. And of course, we see lots of other links over there. And, and, and, and we had a question earlier via Heidi asked, oh, should, should governments join open footprint? Of course, they should, should bodies and join because the more they join, the more we can make sure that these things start fit together because in that way it's an ecosystem of companies of organizations who make this successful and nothing else. I won't go through the road by details because we're running a little bit out of time, but I really want my focus was really, really much to focus at, okay, what are we, what are we heading for? So we're heading for an, an, an open footprint implementation, either standalone or embedded with other environments that really has, which is in this, in part of a broad ecosystem for, for providing, if major reporting systems and collected the data with WCSD, feeding WCSD, and there's a whole lot of other systems out there. But in the center, what Overbeant does is it is really, it defines clear data definitions, data standards, and the access of that data. That's what it does. That we focus it across all industries. Supply chain is not all in gas. Supply chain is not what I get, what I call it furniture. Supply chain is every industry we need to cater for. That's what all footprint is across all industries. And you're going to hear tomorrow why that is so important and what we do to make that better and easier. Let me stop over here. I've no idea whether there are any questions or not, but I'm going to stop. Otherwise Heidi gets annoyed with me. Heidi, or Sammy, I don't have any questions out there. You're doing a great job, Johan. You're doing a great job. So do you have a couple of more slides? We'd still have a few more minutes if you want to continue. I don't want to interrupt. I thought we had until six, until five to six. Yeah, we've got a couple of questions, Johan, if we can maybe to jump to those, if that would work. Good, excellent. From Bill, we've got Will or does OFP already consider carbon offset data? It will. It's not yet included today in our definitions, but clearly we're going to do that. That's also part of our roadmap. That's why I said before that whole thinking about the data moment, data capabilities are so essential because these things will come up and clearly we can cater for that. I don't know whether the government is still in the room, but clearly we can cater for that. There's no issue why we can't. But so far we've not included that in our scope yet. It's not part of MP1 or MP2. It will be clear on our future. And it's important those ideas join the forum or join the old forum, say join the old footprint forum, sorry, and really come up with these ideas, suggestions. Technical, we can do it. Just personal matter priority. Cool. Thanks. Yeah. And just to finish out Bill's comments around it, just for the wider group, you know, carbon offset programs and products obviously have various standards and certification information. So the companies are counting for. So I think that's why it was, you know, important from Bill's perspective around carbon neutrality and that's zero and those kinds of goals. So good. Thank you. And I see one more also from Ian. I know Shimoli you've answered it, but maybe I'll put the same question over to you as well. You know, how do you see OFP fitting in in terms of the methane challenge that people are running into at the moment? And both quantifying it as well as reducing methane? Yeah, because we're running the challenge, of course. If I talk from a shell point of view, we're running that challenge. Of course, the first quantifying, that's the biggest challenge we have today. Me quantifying as a site, what is the methane challenge over there? And hope for is really again, what can do it over there? Of course, it's not the magic bullet over there, but of course, you can keep track of that data, can collect that data. I gave example, I gave for the examples of the IOT type of environment. Because if you think, but the first, we first have to figure out how to collect methane data from a large size, we may have a certain size, we can do it. Like in, you've talked about some of our gas fields, we can do it today, but otherwise we just, we have no good method just to do it. The more we have, the more we can find a good method over there and collect, then there's no reason how we, there's no reason why we cannot collect that type of data in open footprint. But it's not, it is really keeping track of it. It's not something which is going to collect it. We need other things to make that collection part work. Good. Excellent. All right. So I think we've got just a minute left before we have Luca come on. I don't see any additional questions. So yeah, no, I think, I think we're good from a Q&A perspective, Johan. Thank you. Thank you very much. All right. Terrific. Thank you so much, Johan. That was excellent, truly excellent. And again, just a reminder that all of these sessions are being recorded and will be available within a few weeks. So thank you again.