 Okay, good morning, everyone, afternoon or evening, wherever you are. I'm Richard Davis. I'm the CIO at Catalyst Data Management and joining me today and Michael Wilhite, who's the manager of GIS here at Catalyst and is also spending time as a developer on the OSDU GIS consumption zone and Debassus Chatterjee, who's our director of research and analytics and also our OSDU PMC vice chair. A little background on Catalyst, for those of you that don't know us, we were founded in 1985 as Kalman Technologies, changing our name to Catalyst Data Management in 2012, and we have offices around the globe providing data management services to our global customer base. We presently host 95 petabytes of subsurface data for our clients, which is split roughly two thirds in our private cloud data centers in the US, Canada, UK, Norway, Malaysia and Australia. And one third in AWS and Azure data centers, both Catalyst managed and client managed. This 95 petabytes represents millions of seismic surveys and wells and thousands of interpretation projects or cataloged in our eyeglass catalog today. Our main service lines are a digital transformation, which includes contextualization of data, storage and protection, consulting, e-brokerage, data analytics, and of course data management. We've been a member of OSDU since February 2019. We've pioneered the EDS wrapper for connecting external data sources to OSDU services. We've got an in-house OSDU R3M9 on AWS. And just this week, we started the installation of an OSDU R3M10 on Azure for in-house development and OSDU service provision needs. So given that context of the background of Catalyst, our OSDU related development is in the area of data management services. Among the tools we've developed are some desktop data loading tools that leverage manifest-based ingestion and some web-based data management tools that sit on top of the OSDU data platform. So today, Michael is going to give an overview of our data loading tools, a reference data manager, and I'll search and order portal. So over to you, Michael. All right. Thank you, Richard. We've got a few tools. So in the interest of time, we'll be briefly touching on our OSDU accelerators here. So if you'd like any more information or for a more in-depth demo, please get in touch with us and we'll be happy to go into more details on any of these tools. So first, what we're going to look at is a loader for manifest-based ingestion for creating master data records. This tool makes it easy for loading metadata into OSDU using an Excel template that everybody seems to be familiar with. But first, you will need to sign in and OSDU uses OAuth and it can be a bit confusing if you've never used OAuth before. We made it pretty easy just by filling out the values in this box here, which if you're using OSDU in the cloud, you can get from your CSPs or if you're deployed locally, you can get it from your IT team. Our configuration wizard allows for importing and exporting of your OAuth information, so it makes setting up and sharing pretty easy. I've already got an instance here signed in. So once you're signed in, all you have to do is click Generate Template and it produces an Excel file that goes into your OSDU instance and grabs reference or lookup values and adds that to your Excel sheet. So I've got a pre-populated Excel sheet here. So one of the nice things about this is like any of the lookup values are now dropdowns. So you can see this is data that was referenced in OSDU. So you don't need to remember what the reference is. It will automatically pull those values for you as a dropdown to reduce errors. And any dates are also validated as well, so make sure that the dates are in range and in the right format. And as you can see down here towards the bottom, these are all of the master data fields that you can potentially fill out and submit. So all of these will change depending on what the references are. And once when you're happy with that, you can just go ahead and hit Save and then you just load data and then select the Excel file that you've just used. And I pre-did this already, so this is what it looks like after you've clicked load data. It'll tell you what it actually inserted. And for backup, it actually saves a JSON object into a template location. And you can actually review these JSON templates to see exactly what it's submitting to OSDU in the backend for you. So all of this data is required for OSDU and it'll fill out any of the fields that you filled out and automatically submit that stuff. You can also get here a run ID and this you can view in the Airflow console if anybody is familiar with the Airflow. This comes with OSDU real quick. You can actually check the progress of how that submission is going here in OSDU and see if there was any problems in the Airflow console. So this is to be fair, this is just loading the metadata for the master records. If you want to actually load data, we also have another tool. This one is for SEG-Y loading. You can see it has a very similar interface as the other one where you need to sign in and configure a connection. You can also, this one that you select a folder, tell it where the SEG-Y folders or the SEG-Y data is in the folder. Once when you add all from folder, it'll also ask you if there's any subfolders it wants to search. You can tell it yes or no and then the clear all or remove selection. Once when you've selected a SEG-Y here, you click on extract SEG-Y information and you can see it pulls out some of the common binary and trace header values from the SEG-Y file. So here we got inline and cross line, word format type, dimensions. And if you are looking for the EPSDIQ or if you need to make adjustments to where the coordinates or the inline and cross line is, you can click this button here and it pulls up and does a quick scan of the text header for your EPSDIQ. So you can double check to see if the values are in the right location along with byte locations that you can adjust here. 7377, this is kind of like where the standard SEG-Y data is. You can also click on this trace tab. This will preview some of the traces and the respective values. So you can make sure the coordinates are in the right spot and the scaler is correct. You can also override or tell it to no scale on the scalers. So once when you're happy with that, you can hit submit and rerun it and it will repopulate this here for you. And then you can click on upload SEG-Y file to S3. So this will put it into your cloud bucket. So you will actually be uploading the data to the OSDU storage and then click load to actually load the metadata record to your OSDU instance. This is for SEG-Ys. We also have a tool for well logs. Same similar interface, same thing with the SEG-Y. You'll click and tell it where your data is. Here I've preloaded up a last file. You can add all or you can add a single one and extract logs and auto match once when your logs are shown here. And it will pull out the data from the last files and then click load to load the data into OSDU. And finally, we have also a generic document loader. So same deal here. We've got a folder that I've already selected. I'll click add all from folder. Here's the prompt. Well, here's just two dummy records that I've added here. It lists the digital format, how many pages. This all goes into OSDU as well. Here you can tie it to specific entities here. So for example, if this was a well board document, we can actually click on select a specific entry. We can search in our OSDU instance. We'll just do a wildcard search real quick to see what well boards we have. I wanted to tie this document to, for example, is just a test well one here. It will automatically fill out that data for you. So that it'll be tied to the appropriate record. We don't like leaving orphan records not tied to a master document. So clicking load here will load these data into OSDU. All these tools will also put the JSON payload into your temp folder for you to also review. So these are the sort of the desktop tools that we have to help quickly get data into your OSDU instance. I'm going to move on to some of our web based tools. This first one here is a reference manager. So like you saw in the Excel spreadsheet where those dropdowns were coming from. This is the reference manager here. And so all of these values are references in OSDU and there is quite a lot of them. This page here makes it pretty easy to just customize or add or remove data. You can search for a specific reference here in the search bar. If you find one that you want to edit, you can click on it. It will go into your instance. You can quickly add a new one, or if you want to modify or delete, just click on the one that you want. And you can change the code, name or description, update or just straight up delete this. This shows the references in the specific partition that you're in. So OSDU can have multiple partitions and you can click on this and change the partition, which may change some of the permissions that you have if you have a multi-part OSDU install. So that's the reference manager. I'm going to move on to the search and order POC. So this one is our web based tool that's driven here by a map. It also has the same partition dropdown, so you can view data in different partitions. This is just a POC, so right now we're only displaying the Wellbore and Seismic as sort of a common workflow. You can search for items through the Wildcard search text. You can change some of the layers. You can also just do spatial queries as well. So we just wanted to grab a few items here. I'm just going to select these guys. And these should pull back some relevant metadata for each one of the objects here. So we've got Seismic Acquisition Survey here. It's got the appropriate metadata for these. You see it's a little bit different from the Wellbore, so that's unique IDs. If you want to see the associated work product component or inventory records here, you can click on this. It'll search through OSDU and display that information for you as well. So here we've got the segwi file with some metadata from the segwi itself. Here's Wellbore that we selected. So we've expanded this one. We can see some of the inventory records we've got loaded this specific Wellbore. There's a signal survey here and a well log. And you might notice this little download icon here. If you've got permissions, you can click on the download icon, and this will pop up an immediate download. So you can just say direct download live demo. Let's see if I can submit. This should download it straight to records. The download is ready. Click on this. I'll just save this to my desktop. And if we go to the desktop, we should have the raw data. There we are. So this is the actual trajectory behind the metadata here downloaded locally, if I have the right permissions. So that all looks good here. If we go back to our web app, we can also, instead of doing direct downloads, if you are a part of a cloud instance, we can also do multi-selects. So Wellbore trajectory and a well log here. You'll see a little delivery request pop up over here for submitting orders. So we can click on submit order. We can do a direct download again, but if we also have a cloud bucket attached, we can actually just copy it straight from the OSDU into a cloud bucket here. So if we click submit on this guy, this should copy it over to our specific S3 bucket that we have for Amazon. And here you can see the time it took the bucket, a key name, and then the actual S3 path over here that you can actually retrieve the files from. So that's a that's a pretty quick and dirty list of our tools for the desktop, being able to put data into OSDU. So our reference manager here allows editing references and then our map based search and order POC. So hopefully these tools can help you on your OSDU journey and or at least help you get started.