 Hi, my name is Charles Wynne with TGS, and I have a privilege today to speak to you on behalf of the other Verso partners and tell you a little bit about Verso and the work that we've done with the OSDU. So a couple of interesting facts. First, Verso is a is a cool word that was invented by our marketing departments. Okay, so it actually does have a real meaning, so back in the old days it actually was a shortcut for universal and I think that's kind of why they decided to come with that thing. Another cool fact is in 1592, William Shakespeare used the word Verso in some of his poems or in his stuff. So just an interesting fact about Verso. So another interesting fact about Verso is that it's a joint venture between CTG PGS and TGS, and it's numbers they joined in the fall of 2022. So what is Verso? It's basically a unified ecosystem for multi-client seismic data. We each had our own individual websites that allowed you to go in and look at all of our seismic offerings from a multi-client perspective. So the partners got together and decided to build a common system to help you as operators get a consistent experience. Okay, based on this you basically have access to a large portion of the world's multi-client seismic data. Okay, and basically some of the goals for our system are to make things pretty fast, friendly, and very extensible, and we'll talk about that in later slides, right? So you can easily find your data itself, visualize it, download the entitlements associated with it, as well as get access to things that may be hard to get to right now, like access to reports and contracts and things like that in real time, okay? And we really wanted to basically make it usable across users, across many different disciplines. So we are partners in Verso, you know, the seismic companies, but we're also competitors. So therefore it's really important for us to safeguard against things like antitrust and privacy issues, right? And that's the kind of stuff that we've been talking about as part of OSD so far, right? So it's administered by a third party, and I think one important concept is that Verso does not store any seismic data, okay? All the data itself is stored independently within our own data lakes. I'll talk about that also in some later slides, right? And of course the standard safe identity management and GDPR guidelines also apply. So this is a quick video of Verso. Let's hope it works. Okay, it does. So I'm zoomed into the Gulf of Mexico here, right? And I'm going to move the CG data to the top, right? So it's an easy to use system, you know, it lets you easily manipulate the map, for example, right? I'm going to close that out. And then the next piece of it is I'm going to zoom in a little bit more. And from here, if you hover over a survey or I'm going to go ahead and move to my entitlements, right? So it'll easily take you right to the entitlements. And then if you hover over a survey, it shows you what is the outline of the survey as well as what is entitled, okay? And then once you click into it, you can see support documents such as the reports I talked about, contracts, right? And then if you expand, then you'll see metadata. And this metadata has been standardized across all of the vendors, okay? And then once you open up the documents themselves, you can get to hear like an accession report, for example, as well as visualize the data itself, right? And get a preview of your seismic data, okay? So that's just a quick really fast what Versailles is about, okay? So hang on, let me go back to one. So, you know, you're probably asking now, well, that's pretty interesting, but what's this have to do with OSDU, okay? So as I get more in the technical bits here, we'll talk about how OSDU fits into the picture, okay? So what we have first is the green cloud, and the green cloud is what you saw there. It's our website itself, okay? Behind the scenes, there is a white cloud, and that white cloud is basically each of our, you know, basically data lakes that houses all of our seismic data, all of our metadata, and everything else about each of our seismic vendors, okay? And you'll see here that it's truly cloud agnostic, because each seismic vendor is on a different cloud. You know, we have AWS, Google, Azure represented here, right? And how does Versailles pull its data? What happens is whenever you make a request, right, it makes a asynchronous API call at the same time to each of the vendors to pull the data itself, right? So again, none of the data is actually stored in Versailles. It's actually stored within each of our individual, you know, data lakes, you know, what we're calling, you know, the white cloud, right? So what's the OSDU angle here? Well, what we're doing is we're converting all these existing APIs into OSDU APIs, okay? And I think what that's going to let you do is really basically do the same functions that you saw in that user interface previously, but do it from any, you know, OSDU, you know, kind of, you know, system that you already have, okay? So how are we doing this, right? What we're doing is we're using the EDS, which is the External Data Services. I think Frank, my other colleague, talked to you guys about that also in his previous presentation. But what EDS is allowing us to do is it's going to allow non-OSDU platforms, you know, basically our white clouds, to communicate and work within the OSDU data platform itself, right? So what it does is it functions as an OSDU wrapper into each of our vendor's data lakes, right? So as vendors, we can continue to use our existing systems, you know, without having full-boned OSDU implementations, right? We, you know, at some point we may get there, but right now this is going to allow us to kind of get into the OSDU world quickly and get you the data that you're looking for, okay? So again, it's a, and I guess another key advantage is that this is loosely coupled, right? So by building these wrappers and using EDS, we can keep our existing infrastructure in place and kind of build functionality quickly and allow you to get maximum benefit right away, okay? So I want to take a shout-out to Debass' Chatterjee here. He helped us a lot with the EDS implementation. As a matter of fact, I stole some of the slides from the previous EDS to basically make this slide. So with this permission, of course, okay? So in this slide, what we see is we have an OSDU operator, you know, that has their data platform, and then we have a traditional data vendor one that's using, you know, a standard OSDU data platform, and it makes calls like, you know, registration and fetching and delivery as part of an API, okay? What the reversal vendors are going to do is vendors two and three, because they're part of the reversal ecosystem, they're going to implement the very similar API as using the OSDU EDS, right? So from the operator perspective, it looks, you know, vendors two and three look just like vendor number one, right? So it allows, you know, the vendors two and three to basically work within this ecosystem, you know, without having a full OSDU data platform like vendor one does, okay? So, and it gives us some flexibility behind the scenes, okay? So how did we implement these EDS components, okay? One of our goals was to build as many shared components as possible. We'll also allow each vendor to keep autonomy with its own, you know, with our own individual white clouds, right? So we have at the bottom here, you know, the four vendors, we each have our own data lakes, right? And those are proprietary, right? You know, we each do things our own way, but what we have in the middle here are these connectors, right? So this is basically our OSDU connector that we have in the middle, right? And it consists of elastic search, a database, and all the API plumbing to make all the pieces necessary. And there's a translation layer between our internal data lakes and this, you know, this middle layer here that allows us to talk OSDU, right? And each of those boxes is deployed the same way, right? So we're using Kubernetes, there's Helm charts to do the deployment. So it makes it really easy to keep it upgraded and to keep consistency across all those areas, okay? So one is the benefit. What it allows you to do is, if you're an operator, you can use your standard OSDU APIs and get access to all four of the seismic data, right, from that perspective, right? So you basically can integrate one time with Versal and then get access to all these consistently, okay? So I heard this morning a really good phrase that I'm going to use over and over again which is progress over perfection, okay? So OSDU is hard. It's large and complex, right? So here's an example of kind of progress over perfection, right? So Versal has some data fields that are not mapped to OSDU schemas, right? So what we did is, I guess the slides didn't quite work right. If you look there, the first, the third, fourth and fifth lines, we're using some kind of extension properties. And what those properties allow us to do is use fields that are in Versal that are not part of standard OSDU, right? So we're doing that in order to, again, do progress over profession. We want to release a working product that you can use now versus waiting and doing things better. Now we are committed to basically using maybe Versal properties or extending the other properties in the OSDU to make it compatible. But right now, we really want to get a working product. So what are the shared benefits here? For the vendor, it's basically, it gives us a jumpstart into OSDU for any Versal participant, right? And I think I talked about earlier, it doesn't require a full OSDU implementation in order to allow us to talk to other people such as operators, right? From the operator perspective, they also get a fast jumpstart to connect all the vendor data, right? And I think a key piece is you can do a single integration to access multiple seismic vendors instead of having to do each one individually, right? And I think another key benefit is there's consistency now across the vendors, right? You know, the vendors have worked very hard to make our metadata consistent, right? And to make it easy to find and to be able to do things that filter across seismic data. And what are we doing now? We're starting with simple metadata first, right? We want to do registration, infection, and jazz. And that's what we're working on right now to get working. And then the next steps are, I think, some of the things that you saw in some of the previous presentations, right? We want to be able to allow you to download data, visualize it, as well as stream the data, right? So those are things that we want to work on in later iterations. So of course, not everything is always smooth sailing. We have run into some challenges. Probably the biggest challenge is basically customer entitlements, right? Basically, for seismic data, you know, operators don't always license the entire survey itself, right? So they license portions of seismic surveys, right? So we've been working on how to represent that within OSDU. We have a solution that's working right now, but it may not be ideal. So again, basically progress over perfection. We want to get something out there for you to be able to use, right? Another challenge that we've run into is the acquisition surveys themselves. From the vendor perspective, every reprocess project is another seismic acquisition survey, right? So that basically is kind of different from how OSDU is mapping it. So we are committed to basically doing the mapping in a more clean way, but right now everything is represented as a seismic acquisition survey, okay? And then I think we talked about the other areas already. We want to be able to add flexible visualization, delivering streaming mechanisms, right? And then we've also standardized on data elements, but these need to be mapped to the OSDU data elements, which I showed you in the last slide, okay? So again, we are committed to overcoming these challenges. So Verso is now in production. Trials are in progress. We have a booth upstairs, so please come out there and talk to us. Any of the people from any of the companies can talk to you more about it. And there's going to be a big announcement in the next few weeks about Verso, so please stay tuned. The EDS development is kind of happening right now, and we want to release the first piece of that in the second quarter of 2023, okay? And next steps that we want to do are we want to build more on the size of the DDMS, right? Some pieces like, some of the pieces that we're talking about, to be able to stream the data, download, and do those kind of things. And right now we're actually using GeoServer and OGC map services, like WMS and WFS, in order to do the maps that you saw. We also want to work in the geospatial essential zone and move over to that. So that way you'll get APIs that are not just metadata, but also maps themselves, right? So you'll be able to get all the data that you're looking for from that perspective, okay? So I want to thank you for your time, and these are the contacts themselves from each of the partner companies.