Case study · Warehouse · Oil & gas
Master data & cross-reference architecture
One well, one property, one answer — no matter which source system you ask.
Problem
Across an upstream operator's systems — accounting, production, land — the same well or property was represented differently: different identifiers, different hierarchies, different spellings. Reports built on different sources wouldn't tie out, and a commercial MDM product covered only part of the estate. Anyone who has tried to reconcile a PROPNUM against a well identifier from another system knows exactly how this feels.
Approach
I built the end-to-end cross-reference (Xref) integration across a large Snowflake estate, establishing Well Master and Property Master reporting foundations as the single spine that every downstream subsystem could join to. Where the commercial MDM product (EnerHub) fell short, I added an architecture and development layer over it to incorporate the resources it was missing, rather than fighting the product or replacing it.
The work extended through master-data alignment and reporting requirements: unified property views for consistent property-level reporting, and well-master views that downstream production, land, and finance reporting could all trust as the authoritative mapping.
Architecture
Outcome
Downstream teams gained a unified well and property view that every subsystem — production variance, land, data quality, finance reporting — could join to without re-deriving mappings. The Xref foundations became load-bearing infrastructure for the rest of the reporting estate, and property-level reporting finally agreed with itself across systems.