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