Oil & gas data

OSDU data modeling and ingestion

[Placeholder] Operators and service companies hold data in WITSML, CSV, vendor databases and spreadsheets. It has to land in OSDU correctly, not just be uploaded, and most failures come from modeling and compliance rather than code.

OSDU data modeling and ingestion

[Placeholder] Mapping source data to the right OSDU kinds and schemas, building manifests and ingestion pipelines, and storing data OSDU-shaped internally so that ingestion later is a mapping, not a rewrite.

Common OSDU ingestion pitfalls

[Placeholder] Records rejected over acl and legal tags and entitlements groups, units stored as submitted with the unit in meta, coordinate reference system handling, schema version drift between milestone releases, and well schemas that are derived from WITSML but not identical to it.

From WITSML to OSDU

[Placeholder] What maps cleanly from WITSML to OSDU, what does not, and where a decision is needed.

OSDU platforms: ADME, AWS Energy Data Insights and self-hosted

[Placeholder] Azure Data Manager for Energy, AWS Energy Data Insights and self-hosted or community OSDU, and how to get a development instance without a large subscription.

DAS and DTS fibre data

[Placeholder] One short paragraph on distributed acoustic and temperature sensing data.

How we work

[Placeholder] Independent senior engineer through bitsort ApS, Denmark, working remotely with clients in Norway and across Europe. Contact info@bitsort.io.