 Our next presentation is going to be about the OFP reference architecture. So, Surabh is going to review a description of the architecture and provide an overview of the data entry along with reporting. Surabh's background, Surabh Roy is a global director with emphasis energy business unit and is emphasis focal point for the open footprint forum along with the OSDU forum consortium. And in his current role, Surabh is responsible for leading energy transition and digital transformation initiatives for emphasis energy, oil and gas clients. So, there you go Surabh, I'll turn it over to you and just make sure that you just put your sticker on the slide and then you can move the arrow forward or backward. Thank you, Heidi. Thank you for the introduction. It's a privilege to be here. Can you hear me well? Yes, we can hear you. Yes. Okay. All right. Excellent. I'm just trying to move the slide. Thank you everyone for joining in greetings from whichever part of the world you're joining us from. Today's session, we're going to cover the reference architecture, the implementation of it, the data entry aspects of it and the reporting. We absolutely appreciate you joining us and sharing the common vision with us. You know, the way we are moving towards getting a better planet as we move forward with this initiative. All right. So, what we're going to cover is there are two parts to the conversation for particularly this session. One is going to be the technical architecture aspects of it and the other is the default user interface that the group has implemented. And I said, default, because as we go through the architecture, we would kind of communicate to yourselves in terms of what you've heard in the past right now in the morning about the ability for organizations to create their own applications on top of the data platform. And so, therefore, the default aspects of it in terms of the UI, excuse me, but before I move forward, I think a few things that we want to call out. First thing is the key contributions aspects of it. This is more of the credit of the reference implementation and the architecture, you know, while the group and the consortium members have reviewed it, especially want to call out the individuals and the companies that contributed to it. And those are IBM, Infosys, Shell, and Vipro. So, I kind of represent them as I walk you through the reference architecture as well as the user interface aspects of it. So, moving on, before we get into the details of it, and I think through the session today, we kind of worked on as to what exactly has been implemented, but just to kind of do a quick recap so that we can connect the dots in terms of how exactly the objective of open for print has gotten translated into how we have implemented the MVP one. How exactly the reference architecture looks like? What are the scalability and the aspects of it? So, just to call out, I think we all appreciate the challenge. We were looking at, you know, the lack of standards for storing defining accessing and exchanging the G, A, G scope data across the supply chain. And I think we got to highlight the fact and we heard Anna talk about it. We heard the questions that came in today. The scope three aspects of it in exchange of data across the supply chain. I think that's becoming the key challenge. And so, therefore, from a forum perspective, the open for print forum perspective, I think a few things are very important for us to kind of reiterate. One is that this is not a particular industry. This is across all industries because we cannot measure if we are not covering all the industries, you know, because as I think I've read it on the one of the slides. Scope 1 and scope 2 for my organization is scope 3 for another organization. This is about, you know, the definitions and the standards. So, you heard some only talk about the ones that we are referring to at this point of time and the roadmap ahead. Early in the morning, you heard about Gommar and Sammy talk about the, the data definitions aspect of it, the data model aspects of it, but one key thing that I want to call out is that, you know, open for print from our standpoint is just not about the standards. It is, but it equally is about the, you know, the implementation aspects of it, the data platform aspects of it, and which is what we're going to cover here today. So, from a, you know, as we move forward, the 1st part of it is the technology architecture. And as we get into the architecture aspects of it, I think some principles are really important. So there are these 12 principles that you see on the screen right now. And these are the technology principles that we are having to to ensure that the data platform 1st and 4 most and big bowl letters is open source. Anybody can leverage it. Anybody can contribute to it. Anybody can implement it on whatever text tax, you know, you have, as long as you're following the standards provide, you know, that we are that we have identified the other thing. I think is really important for us to highlight that, you know, for us to get a head start on kind of. Creating the, the minimum viable product 1.0 get a head start on that. What we have done is we have referenced back to the OS, do you data platform architecture? And those who do not know is do it's. It's an industry initiative on the subsurface data universe. We created an open source platform across the multiple cloud providers. What we have done is we have, you know, we have tried to leverage that data platform so that we can get a head start about, you know, accelerating the deployment aspects of it for this data platform. So that's, that's what has given us, you know, the, the lead that we could just deploy it real quick using the, the world that has already been done by OS to you. And you can, and again, I think in, hi, these initial note, she talked about the open groups initially. We can read more about it, you know, from open group perspective. I think, you know, the 1 thing that to be called out again important is that you can deploy it on the infrastructure you choose for the MVP 1 for the implementation that we have done. We have implemented this on IBM red hats open shift from a, from a, you know, the cloud standpoint as well as the container platform standpoint. And so that's what you would see. We will talk about it more as we get into the next slides. But just to call out the key principles, you know, you were looking at the availability aspects of it, the scalability aspects of it, the authorization element of it. There should be proper role based access for you to see what data and that kind of has driven the fact that, you know, we have looked at the user interface as aspects of it from a, from a persona standpoint and saying that, you know, oh, if you are more of somebody who was, who was overarching in charge of the data versus somebody who's trying to look at the emissions aspects. Of it versus if you're in the audit organization, which parts of the data, what do you look at it? And so on and so forth. So these principles have guided us to get to that point in the, in our data platform structure. Moving on as we kind of go through it and this is this is 1 of the core aspects of it. You saw this slide that at least the architecture diagram in different shapes today. This is just a simplified way of calling out 2 things. I think the 1st is that there are the blue elements that you've seen here, which is a contribution by the organizations to create the data platform. So the infrastructure element of it, the container platform, as I mentioned about the IBM Red Hat, the data ingestion services, the platform services and the application program interfaces, which was the API. So essentially what we're saying is, and I realize this is more of a technology conversation. I'm going to bring in the business element of it so that we can identify as to how this is, this is actually going to work for your organizations as you adopt the open footprints data platform. But essentially what we're saying is that some of these elements are core to the platform and those are contributions. Those are available that you can download, but there is a competing area and which is what you see in the green box at the top, which says the user interface or the consumption apps. And this is the area where the organizations are free to choose or develop or integrate the applications that they want to be the default user interface. And the other thing that I'm going to talk about a little later in this presentation is just an example of how we can extend the APIs that are provided by the underlying data platform to create an application of sorts, let's just say for data entry or for reporting that kind of a thing. But just an example, there is absolute ability for anybody to kind of plug in if they are using something which is available today in terms of data entry and reporting or they want to build something which is a custom developed application of sorts. But few things to note out, I think this can be deployed on any technology as long as we are compliant to the standards. Again, repeating open source 100% open source. You know, there is a focus on, as you can see from the stack of it, there's a focus on microservices based architecture. The top part provided us the ability to kind of place in the future so that, you know, there is enough healthy competition available and we get the best that we can use in terms of the apps available. And so those are the key elements at this point of time in the data architecture, the platform architecture in here. If you look up the open footprint website, you would also find a link where in we have this mentioned and I have put the link at the bottom of the slide which says, you know, the model.pdf that explains in detail about the various components. Further general review of, you know, the modules that are available and how exactly all of this comes together to offer the data platform. I will, if there was for a moment moving on, I think from a perspective of and this part that you see the next slide, which is the slide number 67 coming up for y'all is essentially the focus is on the user interface and reports architecture and why we are bringing this up is just to let you know how easy it is to kind of get the platform, you know, installing your environment and then kind of link it up to any of the applications that you may have or just consume the API is that you that you see from the underlying platform. So ODI what you see is basically the open data interface platform and that's what we have built on the on the IBM architecture right now, especially from a red have open shift perspective. One thing that I want to call out here is the authentication element of it. So you see the key cloak that is mentioned on the right hand side. Essentially, that's our identity provider. So we're using that IDP tool to authenticate users. And so to my previous point where I mentioned that, you know, we kind of looked at it from a persona based aspects of it as to what role based access would be needed. Key cloak gives us that the authentication and the authorization elements of it on the platform to determine, you know, who gets to access what kind of data how they log in and so on and so forth. What is also going to come up is in tomorrow's session and I think Sammy mentioned that earlier today. What we're going to do is we're going to demo the user interface with us with an example of how exactly this is going to work. So you will actually see this working versus just looking at the block diagram that I'm putting it on the screen right now. If you just look at the diagram, what it essentially means is that their API is extended. You basically consume the API is and then just create forms. If you were doing a custom development to kind of consume the data platform and, you know, either write into it or just export the data and kind of see the data on it. So that's more on the reference architecture in the interest of time. I will move forward into the next part of this thing, or rather I should pause for a moment. Are there any pressing questions at this point of time or do we take questions towards the end? I think we can do the questions at the end. So yeah, keep going. So Rob and I'll we'll pick up some of the questions that are coming through. Okay. All right. Thank you for that. So the next part that we're going to talk about is just a trailer of the user interface design of how things have come together. And so this is what you look at the screen is a default view of the UI that the teams have created. To kind of talk about how we're going to use the data platform. I can't beat myself there. This is just one view of it in terms of, you know, the UI that you can use to access the underlying data platform. You're free to create your own consumer APIs and create your own applications and reporting speeds. But essentially, if we look at the, you know, on this thing and I think this ties back to most of the conversation that happened earlier today in terms of the boundary conditions in terms of creating the organization structure and hierarchy within the platform in terms of capturing the emission data and reporting. So all of those have formed the basis of today, you know, of this platform. So if you just look at it from a perspective of, you know, the the tiles that you're seeing here and this kind of is the workflow that would that would work out as you kind of, you know, start leveraging the open for Prince data platform. There is an ability provided for you to kind of set up your organization hierarchy. And this could be from a, you know, from a field asset perspective. This could be from a equipment perspective. This could be from a corporate office perspective based upon scope on scope to what you're looking at. And then the future in the scope 3 perspective as well. There's an ability for, you know, for the organizations to kind of set up their processes, you know, the facilities, all of that. And each of this is governed by the industry at the bottom line of it. So based upon the industry, the templates kind of show up and say that, you know, what kind of, you know, what kind of data you want to capture in here. So we have provided that flexibility considering the fact that, you know, every industry, whether, whether from aviation to shipping to aluminum to, you know, all in gas. They have their own different ways of reporting some of their emissions data. And you would hear more about the industry aspects of it. And our tomorrow session, which, you know, let's go to talk about about the various industries that we are covering. Now, once we have, you know, the ability of this UI and therefore the underlying platform is that, you know, once you've captured your organization data and the process data, you then kind of can go ahead and start capturing your emissions data. Right now, you know, as part of the MVP 1.0, you can just get the data, you know, from one of the from your existing system so you can just manually enter the data in the system. And again, we're going to show this to you when we kind of give the demo of the platform tomorrow. And once you have the emissions data, then it obviously provides you the ability to generate some, you know, some reports so that you can see in various, you know, slice and dice format of how the data would look like. You know, whether you're tracking it by a process or an equipment or a facility, you would be able to do that. The platform also provides the ability to kind of, as I was talking about the role based access. So, you know, whether you want to set up your own geographies are the admin elements of it and providing members access and all of that stuff. The administrator should be able to do that. So the broader level, that's what we have. We do have a placeholder at the right hand, which you see as the MVP 2. And as we go through today's session and tomorrow's session, you would hear about the open for trends forums plan about the MVP 2, which includes the calculations and the scope 3 elements of it and how that is going to get embedded into the data platform and you would be able to leverage that. So, the broader level, that's the, you know, this is, this is what we wanted to cover a quick. Each of these kind of comes together and I think most of it is what. As you can see, there's an ability to do the organization hierarchy setup. There's an ability to do the boundary condition setup. You can enter data for specific period because that becomes very important from a duration standpoint and the time scale standpoint. Then there are simple tabular reports available to generate data and kind of see the organization hierarchy and the emissions data corresponding to it. And then the administration effort of it. So the ballpark level that kind of covers the reference architecture, how we have leveraged the reference architecture to create the underlying data platform. The MVP 1.0 and then how the default UI right now kind of is a flexibility that allows, you know, the end user to able to kind of put in that data. I'll pause. I'll leave the next few minutes open for any questions that we may have on the reference architecture implementation or any of the user interface elements of it. And Sammy, I'm looking at you right now. I've got a couple of questions already for you all queued up. So, so I think you, I think you spoke to some of the IT folks already. So, but first question I think from to Balt is what are the standards required to be compliant with the architecture? Sorry, I just saw, I just see your hand. Sorry, did you mean to talk. No, you can go ahead. I think so, the, from a standards perspective, I think we talked about the underlying principles. So if you, if you just so that 2 aspects of if you just, you know, the reference implementation is something which is a, which will be a downloadable version of it. So once you download the platform, you know, it comes with all the, the bells and whistles for you to ingest the data to kind of generate the reports and so on and so forth from a broader industry standpoint perspective. I think Somali covered that in the previous session as to what we are. And so we can share that offline with yourself as to which standards we are following. But maybe, maybe can you add something to that? You can hear me. Yes, yes, we can. Okay, thanks. The prime step you need to worry about is really the API is to integrate your applications into the data platform. Those are public standards we come out. What we do inside the data platform course is less relevant because people don't have to access to it. So your prime worry needs to be, I have an application. How does the application get access make use of the standard APIs to access the data platform that really should be focusing at from a standard point of view. Cool. Excellent. And then 1 follow up or 1 additional questions from Ben. Are there any plans to provide a hosted version of the platform beta or otherwise for smaller companies to utilize? Absolutely. Absolutely. And I think we would truly benefit by individuals and companies leveraging the data platform that we have, especially 1.0 version, because that will also give us the ability to consume the data that your organization today has and help us improve. The existing, you know, the data platform that we have and kind of big that into our roadmap aspects of it. So, so I think in the next quarter is what I would say that you should have something available. And, you know, that's what is our goal so that you can download a version and be able to leverage that that would also help us as I mentioned, you know, to kind of see what, what are we missing at this point of time within the consortium members. And the kind of big that into our backlog and the roadmap so that we kind of, you know, ensure that your industry, your company, your data that gets covered into our data platform. Yeah. And if I can build on, so I think there's there's there's sort of a second part to that. So, yes, we'll have the reference implementations that people can download and then, you know, implement in their own landscape, for example. But I think also for some smaller companies, they may not have that infrastructure available. So any views on where there might be, you know, other organizations that are providing that reference implementations to be leveraged by the smaller companies. I guess is more that we expected to have enough time. We clearly send some good idea, good point. We see it also fits with the OGU environment where companies stop finding this as a source of pass capability to other companies. I think the same happening over here. There's just a matter of time. We're very early in the process over here. But if companies come up with that, they're free to do so. So I expect it to happen. Exactly. We just said, in a, in the form of a SaaS type environment. Yes. And just to, and just to build maybe one bit on the standards one coming back to that one as well. I mean, there's a number of software organizations that I know are are attending this as well. So I'm sure that, you know, these standards that were published will also then it's not just in this data platform, but ideally get embedded into other SaaS and, you know, past platforms as well that that'll then get built in and embedded as well. So it's, it's a, it's a full ecosystem of companies, software companies and service providers. I think that are participating. Heidi, there's one question I noticed that we didn't answer previously around governments that Andrew had. Do you want to pick up that one? Sure. Thanks, Sammy. And thank you, Rob. The question is, have any governments or associated agencies endorsed or looking to endorse the OFP? And just to answer that, Andrew, at the moment, we are currently in the beginnings of some discussions with some agencies. We welcome, of course, any collaboration or relationship or an endorsement from the government or any agencies. And so if you'd like to pick that up and continue that discussion, I'm happy to do so afterwards. So at the moment we are welcoming and as Johan pointed out, we're still in the early stages. So any feedback or suggestions or recommendations, you know, that would be very fruitful for us. So thanks for the question. And thank you. I'll put it back to Heidi yourself and, and John back to you on the control. Thank you again. All right. Thank you. Again, really well done. Excellent, excellent presentation. And so thank you. So moving on to. I'm sorry, I just noticed that Sirap has some appendices here to his presentation. Obviously these presentations will be made available. So all the attendees will be able to see these appendices. I'm just running through them now, but there are a lot of embedded links there, a lot more information and these will be distributed after the event folks. So you won't miss those. You will see one of those.