Data at the Center: All Subsurface and Wells Data Stored in a Single Data Platform
-
Multiple OSDU instances, acting as one, around the world addressing the latency distance limitations between 3D users and their applications/data:
- When using 3D apps the maximum distance for reasonable performance is approximately 40 MSEC. This means for global Operators that they need multiple OSDU Platform implementations around the world. In this case Meta and Master data is replicated around the world and real data remains in the region it belongs
- Data (structured/unstructured/real time) to be stored using standard data formats. We move away from proprietary formats and focus on formats that we can use more broadly
- Extracting Metadata to ensure that all data in the OSDU Data Platform can be located using Search or latest Graph technologies: We should be able to do shallow and deep search
- Master data ensuring that we have single set of definitions across OSDU and adjacent Data Platforms
- Well defined set of APIs providing a standard way of accessing the data in the OSDU Data Platform. Make sure that all applications can use a single set of APIs to access all data sources in the OSDU platform
New Generation of Applications being Developed/Acquired:
- Flexible orchestration of workflows
- (Micro) Services driven
- Kubernetes support: All micro services Kubernetes ‘’’driven’’
- User Interface: HTML5 driven (including 3D support) and therefore support for any device such as tablets, phones, etc
- Getting enabled for VR Collaboration support: Important for global cooperation
- Both Physics and Data Driven applications: The latter category gets more and more important when thinking about Machine Learning, etc
- Artificial Intelligence: Exploiting Machine Learning wherever possible
-
Support for existing apps: Often you have existing apps, based on MS Windows desktop/Linux desktop, and we have the opportunity to do an ‘’lift and shift’’ of these applications to the OSDU platform