Talk to us

Case study · Oil & Gas

Steam distribution — 5-well pad sensitivity

A SAGD operator needed to understand steam-distribution sensitivities across a 5-well pad — capital and operating choices interacted with formation behavior in ways that single-well models couldn’t capture..

Talk to us →

Outcome

Aligned

to historical SOR

Problem

A SAGD operator needed to understand steam-distribution sensitivities across a 5-well pad — capital and operating choices interacted with formation behavior in ways that single-well models couldn’t capture.

Approach

R2 built an integrated steam-distribution model combining HYSYS for facility-side thermodynamics, MATLAB for sensitivity analysis, Excel for accessible scenario evaluation, and AnyLogic for pad-level operational dynamics.

Result

Modeled steam-to-oil ratios aligned with historical SOR — the operator could now run capital-and-operating-plan sensitivities with confidence the model reflected reality.

From the engagement

What the work produced.

Engagement interface — steam allocation

Central processing facility schematic showing pad, separator, oil tank, produced water, water treatment, steam generator and boiler water, annotated with flow rates in cubic metres per day, alongside a six-well steam allocation panel and live oil and water rate charts.
The facility model as the operators ran it: flow rates live on the schematic, steam split adjustable per well, and predicted against actual oil and water rates updating alongside.

Engagement output — history match

Well input panel listing reservoir and thermal parameters beside a forecast table comparing historical and simulated oil, water and liquid volumes, with historical versus predicted water rate and cumulative water charts below.
Model against reality, per well. Simulated oil, water and liquid volumes sat within 4.8%, 4.5% and 1.9% of history — the check that had to pass before any sensitivity run was worth reading.

Technologies & methods

The stack behind the outcome.

  • HYSYS
  • MATLAB
  • Excel
  • AnyLogic

Powered by

Have a problem worth engineering?

Let’s connect →