DATA BASTION

A 90-day pilot, scoped tight.

Three phases, three deliverables, one operator basin. We load your data into OSDU, walk a regulator-style audit, and hand the keys to your team.

Three phases. Thirty days each.

Each phase ends with a demo and a written deliverable. If phase 1 doesn't land, phase 2 doesn't start. No open-ended discovery.

Weeks 01–30 · Phase 1

Data ingest

Map your operator's existing well master and production history into OSDU master-data. We work from a sample (well master ~5,000 rows, production ~50,000 rows is enough) and scale the loader once the schema mapping is signed off.

  • GeoJSON map of every loaded well, on your basin extent
  • Capability counts: how many wells have trajectories, tops, production, logs
  • Baseline audit pass: every loaded record traceable to source row + ingest run
Weeks 31–60 · Phase 2

Regulator dry-run

Pick one real well and one real quarter. We produce the full audit envelope — every edit, every materializer run, every source record id — and walk a stakeholder through it end-to-end. The point is to fail in a dry-run, not in front of the regulator.

  • Audit envelope (PDF + JSON) for the chosen well-quarter
  • Walkthrough session with one of your auditors or regulatory leads
  • Gap list: what your current process can't answer that the envelope now can
Weeks 61–90 · Phase 3

Handoff

Your team learns to query records, edit through the audited path, and trigger materializers. We pair-program two of your engineers through the runbook. The pilot closes with a final demo to your executive sponsor and a go / no-go decision on rollout.

  • Runbook (Markdown, in your repo): query, edit, materialize, restore
  • Two trained engineers on your side, signed off against the runbook
  • Final demo + go / no-go memo to the executive sponsor

Both sides have homework.

The pilot only works if both sides commit upfront. Here's the split. If any row on the left is a blocker, tell us in the discovery call.

You bring

  • Data sample — well master ~5,000 rows + production ~50,000 rows is enough to prove the loader; full corpus comes after phase 1 sign-off
  • 1 SME — one subject-matter expert available for weekly sync calls (60 min) and ad-hoc Slack
  • Deploy target — your cloud account, your on-prem cluster, or our bastion (we charge the same either way)
  • Sponsor — one executive who owns the go / no-go at week 90

We bring

  • OSDU stack — multi-tenant, Aramco Standard 1.0.0, already loaded and proven on 1,350,000 ProductionVolumes
  • Ingest scripts — the same loaders that put 338,292 wells into the demo partition
  • Audit harness — the envelope generator behind phase 2, batteries included
  • Weekly demo — every Friday, 30 minutes, screen-share, what shipped this week
  • Hand-off docs — runbook, schema map, materializer catalog — all in your repo at week 90

Talk to us.

The discovery call is 30 minutes. We'll ask which basin, which regulator, which existing systems. If the fit is wrong we'll say so on the call. If it's right we send a one-page pilot scope within 48 hours.