SECTOR · ENERGY
The Operating Layer for energy sovereignty.
How Gulf upstream, midstream, downstream and LNG operators run on a substrate that makes AI operate inside their reality — sovereignty by construction, OPEC and Vision 2040 aligned, regulator-resident.
01
Where energy operators stall on AI
Every major Gulf energy operator has run AI pilots. Most have stalled. The pilots that fail do so for the same structural reasons: the AI has nowhere to live inside the operator's actual systems — no ontology of the field, no model of how a turnaround cascades through asset, schedule and supply chain, no permit-to-work integration, no path back from a recommendation into a governed action. A pilot that cannot operate inside the operator's reality is theatre, not capability.
The substrate is the missing layer. With it, AI moves from chat to operation — reading from SAP PM, the historian, the LIMS, the SCADA stream, the tender platform; writing back through governed bridges; making recommendations that named engineers commit; surfacing decisions across upstream, midstream and downstream on the same ontology. The Operating Layer is what makes the sovereign energy operator's AI investment compound rather than evaporate.
02
The energy operator's context graph
The ontology is the entities, relationships and lifecycle events that make a Gulf energy operator legible to AI. Every Tellefsen engagement starts from this reference graph and re-points it to the operator's actual systems. Five domains; one unified context layer.
UPSTREAM
Wells, fields, reservoirs, production
Reservoir
RESERVOIR ENTITY
Well
PRODUCTION UNIT
Field
OPERATIONAL ZONE
Drilling Program
PLANNING ENTITY
Production Allocation
METRIC RESULT
HSE Incident
COMPLIANCE EVENT
MIDSTREAM
Pipelines, transfer, storage
Pipeline Segment
PHYSICAL ASSET
Compression Station
EQUIPMENT ASSET
Tank Farm
STORAGE ENTITY
Custody Transfer Point
METERED ENTITY
Pigging Operation
MAINTENANCE EVENT
Sensor Stream
TIMESERIES EVENT
DOWNSTREAM
Refining, petrochemical, energy balance
Refinery Unit
PROCESS ASSET
Process Stream
FLOW ENTITY
Catalyst Inventory
TRACEABLE ENTITY
Energy Balance
METRIC RESULT
Yield Prediction
ML PREDICTION
Emissions Calc
SUSTAINABILITY METRIC
LNG · PETROCHEMICAL
Trains, cargo, demurrage
Liquefaction Train
PROCESS ASSET
Liquefaction Cycle
PROCESS EVENT
Cargo
TRACEABLE ENTITY
Vessel
LOGISTICS ENTITY
Demurrage Event
COMMERCIAL EVENT
Carbon Accounting
COMPLIANCE METRIC
SOVEREIGN · COMMERCIAL
Compliance, ICV, ministerial
Permit-to-Work
GOVERNANCE EVENT
Turnaround Schedule
PLANNING ENTITY
Tender Board Submission
PROCUREMENT ENTITY
ICV Commitment
NATIONAL VALUE METRIC
OPEC Quota Allocation
REGULATORY ENTITY
Ministerial Reporting
COMPLIANCE OUTPUT
The same ontology, re-pointed to each operator's actual systems. Same structure on every engagement — repetition is the discipline of category ownership.
03
What the Operating Layer makes possible
With the ontology in place, AI moves from isolated pilots to compounding capability. These are the use cases Gulf energy operators are running today on Tellefsen-architected substrates — each one a node in the same operating layer, not a separate system.
Predictive Turnaround Optimisation
The ontology models how a turnaround cascades across asset condition, spare parts, contractor permits and production allocation. AI recommends scope and sequencing; planners commit. Recommendation, not autonomy.
DAYS OF DOWNTIME RECOVERED, PER TURNAROUND
Field-Wide Production Optimisation
Reservoir, well and surface facility data on one graph. AI surfaces underperforming wells, predicts allocation, models intervention scenarios — every output traceable to the source reading, the model version, and the engineer who approved it.
PRODUCTION RECOVERED ACROSS THE FIELD
ICV & Tender Intelligence
The same operating layer absorbs procurement data — Tender Board submissions, ICV commitments, supplier performance — making in-country value targets observable in real time. PDPL-resident, ministerial-grade audit, no data leaves jurisdiction.
ICV COMMITMENTS, OBSERVABLE QUARTERLY
04
Sovereignty as a structural property
The operating layer is enforced at six independent layers on every operation — perimeter, identity, temporal, lineage, egress, cognitive. PDPL compliance is not a policy the operator promises to honour; it is a property the system makes structurally impossible to violate.
PERIMETER
Where data lives
IDENTITY
Who acts on it
TEMPORAL
When it existed
LINEAGE
What it derived from
EGRESS
What crosses out
COGNITIVE
What the model sees
Six perspectives. One architecture. No exceptions.
How an energy operator engages Tellefsen
04 — Engagement Model
The Tellefsen Engagement Model
From operating gap to operating layer in one quarter.
Every engagement runs on the same three-stage rhythm. Fixed price, fixed outcome, our risk — never time-and-materials. Each stage delivers operational value on its own and earns the next.
01
Sprint
8–12 WEEKS · START HERE
We sit with the firm, map the substrate it has, find the operating gap, and produce the Operating Layer Map — the signed-off picture of what gets built and what it returns.
Deliverable
Operating Layer Map · signed off
02
Build
~90 DAYS · FIRST DEPLOYMENT
The first slice of the operating layer, built live in the client's environment to a fixed outcome. Not a pilot — a production system, owned by the client at hand-over.
Deliverable
Production operating layer · keys handed over
03
Retain
ONGOING · OPERATE & EXTEND
The layer operates and evolves — new domains, new ministries, sovereign models plugged in when ready. Each addition extends the substrate without rebuilding it.
Deliverable
Living operating layer · monthly investment
Fixed price · fixed outcome · our risk · never time-and-materials
The Operating Layer is what energy sovereignty is built on. Every Gulf energy operator that runs on it gains a foundation that compounds across upstream, midstream, downstream and LNG — and stays sovereign by construction, regardless of which models, regulators or partnerships come next.
Start with a Sovereign AI SprintFixed price · 8–12 weeks · Operating Layer Map signed off