04 / From measurements to investigation

A field is
a connected system.

What happens at an injector can influence producers elsewhere, after a delay. Explore the evidence, change a scenario, and decide what deserves a closer look.

Learning mode · synthetic field. All wells, measurements and responses below are invented. This transparent teaching model uses preset relationships and delays; it is not a trained Graph Neural Network (GNN) or Gated Recurrent Unit (GRU), and does not predict a real field.

1 · Understand the field2 · Check the evidence3 · Ask “what if?”4 · Investigate
01

Understand the connected field

Two injectors. Four producers. One reservoir unit, with a preferred flow path and a partial barrier. Select an injector and compare the three kinds of relationship evidence.

Synthetic field plan viewTwo injectors and four producers in reservoir unit A. A high-permeability corridor connects I-01 toward P-01; a partial barrier separates P-04 from the western area. Relationship lines are illustrative.RESERVOIR UNIT A · PLAN VIEW · NOT TO SCALEHIGH-PERMEABILITY PATHPARTIAL BARRIER
InjectorProducerDashed grey: partial barrier

How a real DDM system differs from this learning model

A GNN can learn relationships across a well network; a GRU can represent how behaviour develops over time. Inputs can include injection, production, water cut, well locations and reservoir units. Real deployment also needs data preparation, validated performance on unseen periods, and engineering review.

This lab instead uses visible, fixed coefficients. Its attention weights are invented examples, not neural-network outputs. It demonstrates the questions and workflow without claiming model accuracy.

02

Check the evidence first

A convincing curve is not enough. Check operating time, missing data and performance on dates the model did not learn from.

An uptime trap

Less volume, same online rate

A well produces 1,000 barrels of liquid per operating day. Change the days it runs in a 30-day month.

Monthly liquid15,000barrels
Calendar-day average500barrels/day

The online rate remains 1,000 barrels/day. Lower monthly volume alone does not prove reservoir decline.

For this exercise the online rate is a fixed assumption. At zero uptime, no online performance can be measured from that month.

Synthetic performance example

Reproduction ≠ forecast validation

ObservedModelled

Show the chart data
Invented liquid rates, barrels/day
MonthObservedModelledPeriod

These twelve points illustrate the distinction only. They are not evidence that a trained model works. Field totals must also be checked at well level.

Synthetic data coverage · same reservoir unit does not guarantee communication
ProducerHistory availableOperating contextReview implication
P-0112 / 12 monthsStable uptimeUseful reference case
P-0212 / 12 monthsLift setting changed recentlySeparate lift effects from injection response
P-0312 / 12 monthsRecent shutdownCompare online rate with calendar-day volume
P-048 / 12 monthsMissing injection-response observationsInsufficient evidence to confirm a weak connection
03

What if injection changes?

Change one injector relative to its base rate of 1,000 barrels/day. Compare the four producers at a chosen horizon. The other injector stays at its base rate.

Watch the delayed response

Baseline oilScenario oil

Read the result carefully

More liquid is not all oil

Change in field oil ratebarrels/day at horizon
Change in field water ratebarrels/day at horizon

Compare the oil benefit with extra water handling, injection demand and facility limits. Endpoint rates are not cumulative volumes.

Screening, not an operating recommendation.

This illustration omits pressure limits, changing fluid properties and coupled network constraints. No uncertainty interval is claimed.

Producer response relative to baseline
ProducerBase oilScenario oilΔ oilΔ waterΔ liquidDelay
Inspect the assumptions and calculation

At time t, the liquid-rate change is injection-rate change × pair coefficient × response fraction. The response fraction is zero before the preset delay, then grows as 1 − exp(−(t − delay) / 45). Oil and water split using each producer's fixed incremental oil fraction.

Pair coefficients and delays are assigned for teaching, not learned. Rates use an illustrative common surface-volume basis; this is not a reservoir material-balance calculation. The model has no forecast uncertainty estimate and does not establish causality.

Transparent synthetic parameters: I-01 / I-02
ProducerLiquid-response coefficientDelay, daysIncremental oil fraction
P-010.60 / 0.0810 / 6560%
P-020.25 / 0.3025 / 3035%
P-030.10 / 0.5550 / 1525%
P-040.02 / 0.1280 / 4515%
04

Where should we investigate?

A candidate is a place to ask a better question. It is not proof of bypassed oil, a confirmed flow path or an instruction to change injection.

Includes scenario assumptions, evidence limitations and proposed next checks.

Check the synthetic truth before trusting a result

In the constructed case, I-01 has a strong path to P-01 and weak communication across the partial barrier to P-04. I-02 most strongly affects P-03. Compare positive and negative injection scenarios, including a horizon shorter than the expected delay.

Here those relationships are built into the calculation, so agreement is only a teaching demonstration. A real validation must test a trained model against independent synthetic truth and unseen data, then assess transfer to a new field.

Take the right question back to the field.

Before applying DDM to a real asset, agree on the decision to support, forecast horizon, trusted data sources, reservoir layers and pressure regime. Establish injector history, downtime and known candidate areas with the engineering team.

← Revisit production surveillance Explore the engineering processes →