 Okay, so I'm quite excited to be here to talk about something that we've been working on quite some time I'm very happy to share where we're at and also what you know what we're gonna drive Moving forward, so I'm I forgot that I'm a digital domain manager and a co-bp and with me. I have quite a team I'm Jamie Cruz the head of products for subsurface data platform SLB Chandra Yilishwarapu, I'm the head of products at landmark and the person holding the clicker, so And I'm not cadre. I'm Svera Bransberg from Microsoft Thank you. Okay, click Okay, so this is what we're going through I'm talking a bit about the business and the challenges that we all share Also talking a bit about field development planning that we've been working on with Halliburton for more than a year and also how data mesh and These type of principles can liberate the platforms and moving forward and then some Q&A Okay, so I guess one thing that we all share is the volatility that we have in the market An aqua BP firmly and fundamentally believes that digitalization is one of the main access For us to transform the industry And we are determined to be one of the leaders to transform in the impian industry And now we're here on stage with the partners with Microsoft Halliburton and SLB And I also think it's interesting to see some of the studies that's being done. So this is from an extension Tech vision for 2023 where they're kind of stating that 90% of executives around the globe see that we need to have a change in data management and also the architectural layers of IT And what we see and what we found in this project is that through OSDU and data mesh We will be able to transform the way we build and manage the platforms. We'll have a distributed approach And the Svera will take us through some of the principles that we're working on So a bit on the problem statement. So if you think of just the underground domain in aqua BP What we have is probably around 150 applications Some of them are part of workflow and some of them are just standalone standalone monolithic applications And these are the applications we use to drive decision making and we're always trying to put them into one tenant and Managed them there. It becomes very complicated updates are also Quite hard scalability is for some of these Platforms close to impossible We've also see a change lately in industry that more and more software is provided as a service. That means that there is Tenants being hosted externally where we're sharing data and getting the result back so Together with Halliburton for the last year. We've been working on field development planning And what that really is is to try and aggregate through lineage versioning and connecting to the data sets that we use when we make decisions and That's for all business units for all domains So it's not one platform that has all the workflows, but it connects the platforms together and what we realized So knock-up BP were quite blue SLB in the underground domain or in the express domain But then while construction were quite red and we need to find a way to connect these platforms together and that's where Microsoft came in To with the good burger team to see how can we build and liberate these platforms very differently? So I think that's a good segue over to use Vara to explain a bit about the architectural principles So thank you on Finn We are in a Interoperability session at the OSU forum so that that's why we also here representing four different companies that have to work in an interoperable way and I think for me that they Exciting piece here is what OSDU has sort of started as a journey I think on Finn jumped right into the data mesh principle and say okay. This is what we're gonna do This is what we're really now aspiring to do But I think we have just gotten sort of through the cusp on Enabling OSDU seeing what OSDU can do in terms of creating a self-serve data platform that liberates the data in the companies Microsoft has as an invested Throughout the OSDU journey to make this sort of an enterprise-grade offering And I think we're now seeing that by making this enterprise-grade offering Available for SLB, ARCA, BP, Halliburton, anyone who wants to play on an OSDU platform And then endeavor to connect these instances We can help to address some of these issues that our own Finn talks about because the workflows for the industry are Very very complicated as we all know I think this FTP application that you're gonna hear more about You know later today is a great example for how You know you solve one of these problems and we learn by doing and I think what you're seeing here on the screen I saw all of the Guiding principles that have got us on this journey in terms of saying yes It's OSDU each Partner here will have an OSDU instance and then we will design Federated services that will connect these OSDU's and basically make a combined OSDU instance for the FTP application or any complex workflows that will allow the sort of the complex stacks from SLB and Halliburton to operate one upgrade and hopefully drive robustness and As I said connectivity between the platforms liberate the platforms after we liberated the data with OSDU I Think with that they're gonna leak you know get into the next slide Which is really the exciting one where both Jamie and Chandra is gonna fight over the microphone a little bit So we'll see how that goes for the interoperability thing That's collaboration there right in action So this is quite a big chart. I think we don't need to focus on all the details I think myself and Chandra will talk to this and talk about some of the qualities that we're trying to communicate with this chart I think if we simplify a little bit and just look at the bottom and the middle what we can see With all of our customers the value comes from accelerating workflows That's the bit above the data platform to be able to create business value for customers you have to Find the pain points. I think as we heard this morning the customers pain points measure what the current state is improve Right and then communicate that value back and the key thing is this bottom layer Underneath is there to facilitate and enable that and get rid of some of the friction points and some of the inhibitors That we've had historically in being able to have this seamless integrated Workflows what's very exciting here on this chart as Arnafin talked about was a recognition that you're Implementing that top tier using a combination of platforms and technologies from different providers and that take an advantage of the interoperability And the modular nature of the data model means that we can deploy modern patterns like data mesh So on the bottom here you can see the subsurface platform Being managed Unoperate, you know run by mostly blue with some of the SL tools and some of our data management tools the FTP Tool that you've heard about there without a button and also integrating other platforms connecting platforms here from outside of that environment so this idea that from an Application or workflow perspective we've got a unified platform, but with all of the decoupling and Ability to innovate independently in the different domains and with that I'll pass across to Chandra to add some extra color So there are many 18 minutes All right First and foremost, I think the this particular pattern is Probably the most relevant pattern for operators in the Norwegian continental shelf Hence for a KBP. I just wanted to let everyone know that as of this Monday Discos 2.0, which is a cloud-based Seismic log wells and production data management solution on energy went live for Norway So the the portion on the left the discourse which is really where most of the National data for all of seismic pre post stack all the production data all the wells all of that is live and running through API's most Operators in the continental shelf can actually access that data So that's really one portion of what it is that we're talking about now. We believe in federated virtualized Domain-specific data products and workflows. That is the reason why you see the four of us basically come here and speak about Data mesh is a pattern a deployment pattern that may be relevant to companies such as yourselves Who have multi-region requirements so that you will have multiple? OSdU implementations in each region You have multi-instance. You may have certain versions of OSdU in certain particular Versions getting upgraded at their own pace OSdU provides partitions So you can actually have partitions that can be used for joint ventures versus for corporate and things like that So the idea of data mesh is not new OSdU has some of these concepts of data Segregation already built into it and our requirements are such that we in our companies will actually have multiple OSdU's as an example At Halliburton we have two versions of production OSdU is running One basically used for all of our field operations and the other that we use for more and more of the work that we are trying to do at This point in time So there are already two implementations But I would like to see them as if it's one single OSdU Installation implementation across the entire enterprise you would want the same thing and what you are seeing here is exactly that there are multiple OSdU instances running the data could be in different partitions or different instances They could also be different versions of OSdU running But what we are asking the cloud providers here, especially Microsoft and potentially others to create a fabric By which when we interrogate the lineage the APIs We are interrogating it as if it's a single API and getting the answer back Independent of whether the data was in a particular partition particular instance or in a particular region What that allows us to do is to make sure that each of us who are coming from Individual data products perspective we can actually use different versions of the product to ensure We are ahead. We are able to implement our data products without depending on others So the ability for individual Domains individual regions to actually accelerate the work that they want to do the innovation that they want to bring Remains in the system while from a corporate governance perspective it is all OSdU and that requires a lot of work that Microsoft and cloud service providers have to do But what we are announcing here is that some of the technologies that Halliburton has built and others have built around Federation and virtualization. These are technologies and techniques We are going to be bringing in to make this deployment happen at Akka BP So to summarize if there is something that interests you and peaks you Please reach out to any of us But we look forward to using OSdU as the core to show this particular deployment pattern and and continue to enhance the Data mesh capability. This is basically what we are announcing at this point. Thanks I think one of the one of the things that we've been interested in you Use the phrase data as a product. I think that's an essential way of modularizing and considering that every domain doesn't need every element Of the data model. So as well as looking at the system federated Platform perspective this also gives us an opportunity to consider Those subsets of the model that are needed for individual workflows to accelerate processes combine them together and implement them to support Particular domain so it's helps us break down the monolithic data model into data as a product So that's just another concept I think we're going to hear more of as we go forward with OSdU instead of building a large monolithic Single data model we'll be looking at in that modular data as a product way In fact you as you say that it reminds me every time I speak to our IT organization on the SAP upgrades and the capabilities that we want out of SAP I take a step back and realize that most of us in in our industry. We do massive SAP Upgrades every five years or every ten years and the idea here is with data products And the ability to create a data mesh is that we are incrementally updating our data products on a every two weeks Every four week basis So the innovation is much much faster than dealing with a monolithic application that may constrain the massive upgrades That it becomes so one of the things that we don't want to do is this is to a place where OSdU becomes like SAP These are massive projects to upgrade We have to manage these upgrades over years and years and things like that and without having a capability such as this It may be very very difficult now Of course this pattern may be relevant to only some of the larger companies with multi instance multi domain Kind of capabilities some of the smaller Operators may not have this issue But I think the idea here is to make not make OSdU the long-tent in the pole when it comes to innovation okay, so We shared a lot on the platform side And FACO BP we have a slogan where we're saying we're going to be the first truly Data-driven oil and gas company in the world. So so what does that really mean? Well today? You know, I think we need to be honest that we're quite process driven means we have a business management system that tells us Quite in detail what we should do What we want to achieve by building this is That the actual understanding of the data we have in front of us when we are making decision Tells us where to focus where is the uncertainty? Where do we need to improve the data quality? To make the decisions better So that I think this is underbuilding that strategy and through this this slogan will become a reality Thank you