OSDU Data Definitions Join Smart Data Models: 6 Candidate Models for Wells, Wellbores and Subsurface Data

Smart Data Models’ Candidates repository now includes a new candidate standard from the energy industry: osdu-data-definitions, with 6 candidate models translated from the OSDU Data Definitions of The Open Group OSDU Forum. They cover organisations, fields, wells, wellbores, wellbore trajectories and well logs. The OSDU schemas are published under Apache-2.0. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each one validated against its schema.

About the OSDU Data Definitions

OSDU (Open Subsurface Data Universe) is a forum of The Open Group. It builds an open, vendor-neutral data platform for the energy industry. Its Data Definitions are the JSON schemas of the platform’s records, called kinds. There are master data (wells, wellbores, fields, organisations…), work-product components (well logs, trajectories, markers, seismic, reservoir models…), reference data and datasets. Every record has the same envelope (id, kind, access control, legal tags, lineage, frame of reference) around a data block with the domain attributes. Many of these attributes come from PPDM, Energistics and other industry standards. This translation uses release v0.30.1, the latest one.

The models

Model OSDU kind What it describes Attributes
Organisation master-data–Organisation:1.2.0 Operators, service companies, regulators 33
Field master-data–Field:1.1.0 A hydrocarbon deposit that has been exploited commercially 29
Well master-data–Well:1.5.0 The surface origin of a set of wellbores, with operators, states and events 54
Wellbore master-data–Wellbore:1.5.1 A hole from the surface to its deepest point, with depths, trajectory type, products and bottom-hole location 66
WellboreTrajectory work-product-component–WellboreTrajectory:1.4.0 A directional survey of a wellbore 85
WellLog work-product-component–WellLog:1.5.0 Measurements along a wellbore against depth or time, with their curves 58

Real open data in the examples

The examples all describe one real well: AKM-11 (Oudega-Akkrum-11), an onshore gas exploration well in Friesland, the Netherlands, spudded in 1978. The records come from the TNO dataset that OSDU prepared for its open test data (Apache-2.0; the data originally come from the Dutch NLOG portal, which allows redistribution). The set covers the well, its wellbore with coordinates in the original ED50 / UTM 31N system and in WGS 84, its trajectory, its 1978 composite well log (gamma ray, sonic, density and neutron curves), the field and the current operator. The test data were written for an older schema version, so the translator migrated each record to the current one. Each example lists these changes in its source attribute.

Translation notes

  • The data block becomes the entity. Every attribute of an OSDU record’s data block, including those inherited from OSDU’s shared abstract schemas, becomes an entity attribute with its OSDU name unchanged (FacilityName, VerticalMeasurements, SpatialLocation, Curves…).
  • The envelope is kept where it carries meaning. The OSDU id becomes osduId. The NGSI-LD id urn:ngsi-ld:Well:osdu:1013 is built from it and can be turned back into it. kind, meta (the units and coordinate reference systems of the values), ancestry, tags and legal stay. Platform access control and system audit fields are left out.
  • Links between models are Relationships. Operators and service companies point to Organisation, a wellbore to its Well, logs and trajectories to their Wellbore. Links to OSDU reference data (well status, trajectory type, units, CRS…) keep the OSDU record ids, because those code lists are extensible and their namespace depends on the deployment.
  • Nested where OSDU nests. Spatial locations, vertical measurements, facility events and log curves keep their full OSDU structure. The shared abstract schemas are converted once per model into $defs.
  • Ready for geo-queries. Each model gets an NGSI-LD location, the GeoJSON geometry from OSDU’s own WGS 84 coordinates. It is the only addition to the OSDU content.
  • Current attributes only. Attributes that OSDU has deprecated are left out. The @context of each model maps every term to its definition in the published OSDU schema files.

Try it, and tell us what’s missing

These are Candidates: carefully sourced first translations, not yet official Smart Data Models subjects. Points to review: the mapping of the OSDU record envelope, the choice of Relationships versus OSDU ids, and the overlap of Organisation with the existing dataModel.Organization. Natural next steps are Basin, wellbore markers, rigs and hole sections, and the OSDU production and seismic kinds.

Browse the models, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/osdu-data-definitions

Bookmark the permalink.

Comments are closed.