SCHEDULE User CourseApril 28, 2023

Introduction to Schedule

The Schedule section of an Eclipse data deck Defines simulation wells, connections, vertical

performance, artificial lift, controls and limits. Defines groups, controls and limits. Defines networks, compressors, etc. Specifies time dependent data.

There are more than 100 Eclipse keywords available to generate this section.

A Typical History Match Schedule Section

VFP tables for pressure reporting VFPPROD, VFPINJ Well & completion definition WELSPECS, COMPDAT, COMPRP, COMPVE Measured production & injection rates WCONHIST, WCONINJE, WCONIN Simulator control parameters TUNING, TUNINGL, NEXTSTEP Output control RPTSCHED, RPTRST Simulator advance to 1st rate change DATES Manual workovers; PI modification COMPDAT, WELPI, WPIMULT Shut-ins or opening wells WELOPEN Modified production & injection rates WCONHIST, WCONINJE Simulator advance to 2nd rate change DATES Modified production & injection rates WCONHIST, WCONINJE, WELTARG Simulator advance to 3rd rate change DATES End of simulation, perhaps at present day END

A Typical Prediction Schedule Section-- VFP tables for THP control VFPPROD, VFPINJ-- Well and completion definition, inc. infill wells WELSPECS, COMPDAT, COMPRP, COMPVE-- Production well targets WCONPROD, WELDRAW-- Injection well targets WCONINJ, WCONINJE-- Activate new wells as necessary QDRILL, WDRILTIM, WELSOMIN-- Well PI specification WELPI, WPIMULT-- Automatic workover specification WCUTBACK, WORKLIM, WORKTHP,

COMPLUG, WPLUG-- Place wells on pump or gas lift WLIFT-- Periodic testing of shut wells WTEST-- Time taken to perform automatic workovers WORKLIM-- Well and completion economic limits CECON, WECON, WECONINJ-- Tolerance for economic limits and targets WLIMTOL-- Group hierarchical structure GRUPTREE-- Distribute production among wells GCONPROD, GUIDERAT, WGRUPCON,

PRIORITY, WELPRI-- Distribute injection amongst wells GCONINJE, GUIDERAT, WGRUPCON,

PRIORITY, WELPRI, WINJMULT-- Satellite production and injection GSATPROD, GSATINJE-- Group and field economic limits GECON-- Simulator control parameters TUNING, TUNINGL, NEXTSTEP-- Output control RPTSCHED, RPTRST-- Simulator advance and termination DATES, TSTEP, END

Introduction to Schedule

Generating a Schedule Section

Involves massive amount of data processing.

Grid dependent.

Simulation time framework dependent.

Requires knowledge of a large number of keywords and

formats.

Introduction to Schedule

Schedule prepares and validates production and completion data for Eclipse

Schedule calculates simulator production rates and well connection factors for any given time framework and grid. Allows quick updating and

easy iterative workflow.

Introduction to Schedule

Schedule uses advanced visualisation tools for data validation. Allows easy quality control.

Macros and Templates to simplify time consuming keyword creation tasks. Automatic generation of

common keywords with user specified default item values.

OCS

GGS

CTF

OCS

Wells- Paths- Tubulars- Chokes- Completions- Workovers- Production - Injection

NetworkGroups-Capacities-Demands

Simulation GridCell Properties

Geological Model

Schematic of Data Handling in Schedule

Basic Data Flow

Production Data[OFM / Finder]

Well Events[OFM / Finder]

Well Path[ OFM / Finder /

FloGrid ]Simulation Grid

[FloGrid]

Schedule

ECLIPSE

Results

Basic Input Files

Simulation Grid file – formatted / unformatted grid files

Well production data – OFM keyword files

Well completion & workover data – Schedule specific keyword

file

Well path – Eclipse trajectory file

Tubing string assembly – Schedule specific keyword file

Data Input - Production

Data Input Styles

Import Free and Fixed Formatted Keyword ASCII Files

Export options in

Oil Field Manager

Finder

Interactive input in table panels

Extract data from ECLIPSE data file.

Production Data Sources

Allocated data Periodic (daily, monthly, quarterly,….) Calendar or Stream Rates and uptimes Volumes and uptimes Cumulatives and uptimes

Test data Sporadic Stream rate, test period Volumes and test period

Production Data Handling SchematicR

a te

Time Period

Rat

e

Measured Data

Schedule StorageSimulator Rate

Data Storage in Schedule

Data stored as per day production rates (stb/d,..)

Data is recorded by DATE

The smallest unit of production time is a DAY.

Only change in production is recorded.

Duplicate data is not stored.

Missing data is interpreted as per user specification

Zero production, OR

Previous production rate

Data Input – Production Keyword Files

Header: Data Specification

Periodicity – Daily, Monthly, Sporadic.

Directives for handling missing data.

Calendar/Stream Rates & Uptimes.

Units for rates, volumes, time, uptime.

Specify free or fixed format for data.

Data file / Definition file location (optional).

Body: Data in column defined by keyword sequence.

Data Input – Production Periodicity Keywords Default

Monthly production and injection. Rates apply from beginning of month. Cum. Volume at end of month (*CUMULATIVE).

Keywords *Daily *Monthly *Yearly Sporadic - specially defined OFM type tables.

Data Input – Production Missing Data

The *ZERO_MISSING directive.

Set any missing data to zero at the time of import.

Missing/expected date depends on chosen periodicity.

Use *REPORT_MISSING for issuing warnings.

Set in configuration file (ECL.CFG) as True / False.

Will affect all imported files.

Overrule by using *IGNORE_MISSING.

Data Input – ProductionRates – Stream / Calendar *UUCRATES – rate is uncompensated for uptime.

qstored = qgiven = q * uptime_fraction (Default)

*UCRATES – rate is compensated for uptime.

qstored = qgiven * uptime_fraction

Example: A well produces 30 bbl of oil in September with an uptime of 15 days (0.5).

*UUCRATES: Read in rate should be 1 bbl/day

*UCRATES: Read in rate should be 2 bbl/day.

Data Input – Production Units for Volumes

Metric - *METRIC Volumes in Sm3 for liquid and gas. *MSM3 – all volumes in 1000 Sm3.

*MSM3 GAS (modifier for *MSM3) *MSM3 LIQUID (modifier for *MSM3)

Field - *FIELD STB for liquids / MSCF for gas.

*MSTB – liquid volumes in 1000 STB. *MMSCF – gas volumes in 1000 MSCF.

Imported data is converted to project units.

Data Input – Production Units for Time

Default units depend on periodicity. Daily Monthly

Modifiers *HRS_IN_DAYS – units for time keywords set to hours in

the day. *MNS_IN_YEARS – Months in the Year

Data Input – ProductionData Keywords (1) Identifier

*WELL – well names will appear in specified column. *NAME, *WELLNAME – implies following data applies to

the particular well.

Time Period *DATE, *DAY, *MONTH, *YEAR, *YY/MM, *YYMMDD,

*MMDDYY, *DDMMMYYYY, ..

Data Input – ProductionData Keywords (2) Interval Production Time

*DAYS – number of days on production for the month. Units can be modified by *HRS_IN_DAYS. *YEARLY would imply days in the year.

*UPTIME_FRACTION – uptimes in fractions. Must be used with *DAYS / Default is 1.0

Production volume / rate *OIL, *GAS, *WATER Units depend on periodicity and units modifiers.

Data Input – ProductionData Keywords (3) Interval Injection Time

*(O/W/G)IDAY – injection time Default is *DAYS or full period (days in the month). *HRS_IN_DAYS (hours in the day) *YEARLY (days in the year).

Injection volume / rate *OINJ, *GINJ, *WINJ Units depend on periodicity and units modifiers.

Data Input – ProductionFormat Keywords Data Format Specification

Format Blocks *FORMAT / *END_FORMAT.

*FORMAT / *END_FORMAT. Alternative Free Format Specification

Keywords in column headers.

*FORMAT

*WELL 1 6

*DATE 8 15

*OIL 16 25

*END_FORMAT

*FREE_FORMAT

*WELL

*DATE

*OIL

*END_FORMAT

*DAILY

*WELL *DATE *OIL *GAS *WATER *UPTIME

Well Path

Trajectory File - Well path in grid I, J, K coordinates. Cell entry/exit points in map

coordinates (x, y, z) Cell entry/exit faces (Z-, Z+,

…) Cell permeability and net-

to-gross. Deviation File – Well path in

map coordinates (UTM)

Entry point/face

Exit point / face

I

J K

Z-I-

3D VisualisationWell Completions vs. Connections

Input Data - Well Geometry

Well / Multi-lateral branch Geometry Deviation Survey

File import in GRID format ( x, y, md, tvd ) OFM, Finder, FloGrid and GRID.

3D viewer create/edit Trajectory (I, J, K, …)

File import FloGrid / GRID export format

Table Edit Extract trajectory / deviation from Eclipse data file

Input Data - Multi-segment Wells

Tubing Description File Keyword based ASCII Tubular information for

multiphase flow calculation through

casing tubing

Location of devices Packers, chokes and

other inflow devices

Packers

PerforationsWell1%Branch1

Well1%Branch2

Inflow Controls

Well1 (annulus)

Well1:02

Well1:01

Choke Well1%Branch3

VFP table forvertical flow

VFP table forhorizontal flow

VFP table forICDs & chokes

Input Data – MSW Keywords

Branch Naming convention Wellname%Branchname

Keywords CASING – well/branch, MD, id, int. roughness. TUBING – name, start/end casing, MD, id, od, int/ext

roughness. PACKER – name, casing name, MD. CHOKE - name, casing name, MD. INFLOW – name, tubing name, MD.

Events

Events are Triggers that cause

A DATE keyword to be inserted in the Schedule section.

A change in well specifications, PI, etc.

A Change in operating controls

Import from ASCII File

Enter data interactively.

Extract data from Eclipse data file.

Input Data – Well Events

Characteristics of Well Events Event name keyword ( perforation, plug,…) Date Depth(s) - length

PI parameters – rw, Kh, S

BHP (will be output in the WCONHIST keyword) VFP Table Number (Change VFP table number in use)

Well Events will be converted to Eclipse Keywords and inserted at the appropriate date.

Input Data – Well Events

Input Data – Events

Keyword Events Eclipse Keyword and data items Date

User Events Insert user comments Create user defined time steps (TSTEP)

Input Data - Simulation Grid

Grid Geometry Import

Structured grid

*.(F)GRID-file (Eclipse Office / FloGrid / GRID)

Unstructured grid

*.(F)PGRID-file (Flogrid)

Grid Property Import

*.(F)INIT file (Eclipse Office)

Input Data - Simulation Grid

Coordinate Systems ( axes and units ) Map

Well paths in maps coordinates Grid

Grid Origin in map coordinates Grid axes in map coordinates

Wells intersecting grid ?? Check out Config File

Group-Well Hierarchy

FIELD

group1

group2

well1

well2

well3

well4

well5

FIELD

group2

group1

well3

well2

well1

well5

well4

*GROUPNODE

group1 FIELD

group2 FIELD

*LEAFNODE

well1 group1

well2 group2

well3 group2

Control Network Time Dependent Group-Well

Hierarchy Import ASCII keyword File. Create / assign wells / groups

interactively. Create network configuration

at different times. Extract from Eclipse Data File.

Control Network Panel Primary data processing

module Create well under groups. Export data to files. Launch Events Editor for

wells / groups / field. Display completion /event

graphs. Graph / Table Production. Start trajectory / segment

edit. 3D well visualization

Date for Network

WellsGroupsAvailableDrag items

to buildnetwork

Item List Panel

Repository of wells and groups Pick wells and groups to build

networks. Launch Events Editor for wells /

groups / field. Display completion /event

graphs. Graph / Table Production. Start trajectory / segment edit. 3D well visualization

Production Data Handling

Review data in 2D plots and Tables.

Compute and display group and field production.

Compute and display cumulative and averaged production (WCONHIST).

Create / Edit data in tables.

Event Data Handling

Review group and well events.

Create / Edit events. Templates Macros

Display completion / event graphs. maps events onto grid respect geological layers

QC Production / Events

ScalableFlowDiagram

Event

Status lineshows eventattributes

Celllocation

ToggleAxis tom. depth

Events – Layer Shifts

Grid Cell surfaces are planar and approximate the model structure

Schedule can shift events to fit within a specified grid layer.

Define a layer Table.

Geological layer

Grid layer

Well Trajectory

Perforation

Layer Modelling

Simple Shift events moved into layer clipped if necessary relative position of

events not honoured

Layer Modelling

Scaled Shift Total event range is

scaled to total layer length.

Length not honoured. relative position of

events honoured.

Layer Modelling

Relative Shift events moved into layer. Length honoured. relative position of

events not honoured.

Simulation Time Frame Work

TFM is the DATE sequence Time Step Control

User defined periods with varying time steps. Define start and end of

History & Prediction. Split simulation time

into intervals with varying time step frequency.

Output DATE keywords.

Time Frame Work - Modifiers

Event Triggers Option to modify the base time

framework by inserting DATEs at event times.

Choose particular event types as triggers.

User Events Enter a TSTEP keyword.

Enter explicit DATES (*2000a)

Time Frame Work - Shift Events

Associate a shift criteria with each event Earlier DATE Later DATE None – Don’t Shift

Time Frame work panel choose Apply – shift the events according to given criteria. Ignore – create time step at event time. Custom – choose behaviour based on event type.

Time Frame Work - Average Rates

Events Keyword Generation Internal Keyword

keyword generated by Schedule from event specifications

e.g. perforation COMPDAT (internal)

COMPDAT input Eclipse file – keyword event.

Template Keyword

used to default missing data in Internal keywords.

wildcards for well names does pattern selection.

Macros

keywords that propagate through the network.

TEMPLATE Keywords

Defined at the Field or Group Level and applied to lower level in the hierarchy on a particular date. generated on Schedule section export. Existing data has priority. Lower level templates have priority. Cannot be applied on Macro generated

keywords. Apply to name patterns.

MACRO Keywords Define at Field or group level at certain date to generate

keywords. Generated on Schedule Section Export. Well keyword (Wxxx..) generates this keyword for all wells

lower in the hierarchy. Similar Group keyword (Gxxx..) generation. Existing keyword and data items have priority. Lower level Macros have priority. Apply to name patterns.

Well & Perforation Modelling

Compute Trajectory. Calculate well connection

factor.

Well Connection Factor

Three part Peaceman formula with full vector representation and accounts for: Orientation of well path

Trajectory defines cell entry and exit points and a resulting trajectory vector

perforation vector defined by events Permeability tensor Partial completion Damage skin can be specified separately

Connection Factor

KH in the i direction:

KHi = {(Kj*Kk)1/2 hi}

I - Transmissibility :

Ti = cKHi/(ln(roi/rw) +S)

Cell Connection Factor:

CCF = (Ti2 + Tj

2 +Tk2)1/2

Ref.: SPE 18854 – “Predicting Horizontal/Slanted Well

Production by Mathematical Modeling” by Chang, M,M,

et. al.

Cell Permeability in I, J, & K

Simulation Cell

Ki

Kk

Kj

Perforationsfrom Events

Well Segment in Cellfrom Trajectory

h1

h2

Connection Factor

Net-to-gross term Eclipse 100 option: multiplier for

Cell Dz. hk ( k-component of the perforation vector).

Eclipse 300 option: multiplier for hk ( k-component of the perforation vector).

Scaled permeability option: multiplier for Perm_i and Perm_j.

ECLIPSE - COMPDAT

Transmissibility factor for the connection – CCF (optional). Well bore diameter – rw (required). Effective Kh of the connection – Kh (optional)

assumes entire cell is completed. Skin Factor – S (optional) . D-Factor – non-Darcy flow (optional).

alternatively use WDFAC keyword.

COMPDAT Generation

Pseudo Skin Sps = constant * Kh / CCF – ln(ro/rw) Accounts for position and partial completion within cell. Combines with Eclipse (cell) Kh Schedule CCF.

COMPDAT – Multiple Completions

Multiple completions in a Cell are grouped into a single connection factor, skin and well bore radius.

CCFi = f(hi, rwi, si, …) CCF = CCFi

rw = rwi*hi / hi

S = si*hi / hi

h1

h2

rw

rw

s

s

IJ

K

COMPDAT – Welltest Modifier

Scaling of connection factors using Welltest Event. KHw >= 0

Khcomp_1 = Khcomp_1*[ Khwelltest / (Khi) ]i =1, …n completions.

KHw < 0 Kh1 as computed from trajectory information.

COMPDAT Export Options

Export Options Suppress Skin, export CCF and Kh.

Skin will be defaulted to 0.0 Include CCF, Kh and damage Skin. Suppress CCF, export skin and

Eclipse Kh. Pseudo skin exported.

Suppress CCF, Skin and Kh Eclipse will compute CCF.

Schedule Generation Options .. Use Trajectory / property file permeability for CCF. Specify threshold perforation length (% or abs.). Generate COMPVE keywords.

Threshold height for COMPVE. Specify Layer Shift Method. Suppress History – WCONHIST not generated. Suppress stream rates – WEFAC not generated. Suppress warnings, comments and errors.

Exporting Schedule Sections

Export entire control network or selected wells.

Start and End as per simulation time frame work.

Configuration as per export options selected.

Internal keywords are generated only on export.

Editing an internal keyword converts it to a keyword event.

Details of error, warning messages and comments are

explained in the user guide.

Convert Eclipse Models

A Schedule project can be approximated from an existing Eclipse

data file by extracting data from keywords.

Extract Trajectory (requires grid).

Build Deviations (requires trajectory).

Extract Events (requires grid / trajectory).

Extract Production Data (from WCONHIST).

Grid geometry and cell property files are assumed available from

simulation runs.

History Match / Prediction Tools

Import Eclipse Summary Files. Overlay historical and simulated production data.

Import Eclipse Restart Files. Analyse history matches – pressure, saturations versus

well completions. Review predictions – target infill wells.

3D Viewer

Edit Well paths / create new wells.

View well deviation, trajectory, completions and connections.

Multi-segment well display. Compare completions with

grid connections. View only well cells or entire

grid.

3D Visualization

Animation tools for critical analysis of history match.

Perforation / completions plugs with time

Overlay time dependent array properties imported from Eclipse restart files.

Good Luck !