... | ... | @@ -4,16 +4,24 @@ The Wellbore Data Management Service (Wellbore DMS) provides a single consistent |
|
|
|
|
|
As can be seen below, the Wellbore DMS is located at the heart of the OSDU data platform leveraging its common services for indexing, authentication, security etc. while adhering to its usage patterns and common behavior for client isolation, data lifecycle etc..
|
|
|
|
|
|
It will include type-safe entity access and optimized accessors for bulk data of many data entity types such as logs,
|
|
|
trajectories, checkshots.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
![image](uploads/1ee0f408baf2819aa1c15af5fcced571/image.png)
|
|
|
|
|
|
The Wellbore Domain Data Management Service include type-safe entity access and optimized accessors for bulk data such as logs, trajectories, checkshots.
|
|
|
|
|
|
The scope for the R3 delivery will be API's for the following data entities: Wellbore, Logset and Log.
|
|
|
- A valid Logset is a group of logs with a common reference. The values for the reference need to be in decreasing order.
|
|
|
- A valid Log is a series of numerical values (no support today for alphanumeric logs) in n columns.
|
|
|
- Details on specific methods to be delivered for this release is documented [here](R3-details)
|
|
|
**Release 3 scope**
|
|
|
|
|
|
The Release 3 scope will be focused on the following themes:
|
|
|
* Leveraging OSDU services for Entitlements, Legal compliance, Indexing and Schema validation.
|
|
|
* Provide extensible architecture that allows easily addition of a new cloud provider, by isolating the domain business logic from the cloud-specific technologies.
|
|
|
* Enabling specific access methods for the following data entities : Wellbore, Logset and Log. More details can be found [here](R3-details)
|
|
|
* Provide a build pipeline and a deployment pipeline for GCP
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
**Wellbore DDMS Architecture**
|
... | ... | |