0% found this document useful (0 votes)

269 views70 pages

Intersect Eclipse Simulator User Guide

The Intersect Eclipse Network Simulator (ENS) user guide provides comprehensive instructions on using ENS for evaluating pressure losses in production and injection networks. It details installation, licensing, network modeling, and solution methods, emphasizing the simulator's capabilities in both standalone and coupled modes with the Intersect reservoir simulator. Key functionalities include modeling various network types, managing boundary conditions, and solving non-linear equations for accurate pressure and flow rate calculations.

Uploaded by

Bessam Meghdouri

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

269 views70 pages

Intersect Eclipse Simulator User Guide

Uploaded by

Bessam Meghdouri

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

Intersect

High-resolution reservoir simulator

Eclipse Network Simulator user guide

Version 2024.3
Intersect Eclipse Network Simulator user guide

This work contains the confidential and proprietary trade secrets of SLB and may not be
copied or stored in an information retrieval system, transferred, used, distributed,
translated or retransmitted in any form or by any means, electronic or mechanical, in
whole or in part, without the express written permission of the copyright owner.

Trademarks & Service Marks

SLB, Schlumberger, the SLB logotype, and other words or symbols used to identify the
products and services described herein are either trademarks, trade names or service
marks of SLB and its licensors, or are the property of their respective owners. These
marks may not be copied, imitated or used, in whole or in part, without the express prior
written permission of SLB. In addition, covers, page headers, custom graphics, icons,
and other design elements may be service marks, trademarks, and/or trade dress of
SLB, and may not be copied, imitated, or used, in whole or in part, without the express
prior written permission of SLB. Other company, product, and service names are the
properties of their respective owners.

Eclipse® is a mark of SLB.

An asterisk (*) is used throughout this document to designate other marks of SLB.

Security Notice
The software described herein is configured to operate with at least the minimum
specifications set out by SLB. You are advised that such minimum specifications are
merely recommendations and not intended to be limiting to configurations that may be
used to operate the software. Similarly, you are advised that the software should be
operated in a secure environment whether such software is operated across a network,
on a single system and/or on a plurality of systems. It is up to you to configure and
maintain your networks and/or system(s) in a secure manner. If you have further
questions as to recommendations regarding recommended specifications or security,
please feel free to contact your local SLB representative.
Intersect Eclipse Network Simulator user guide

Table of Contents
1 Introduction .................................................................................................. 1
2 Installation and licensing ............................................................................ 2
3 ENS network models ................................................................................... 3
4 Network solution method ............................................................................ 5
5 Coupling with the Intersect reservoir simulator ....................................... 7
6 Keywords .................................................................................................... 15
BRANPROP ...................................................................................................................... 16
END ................................................................................................................................... 18
ENDINC ............................................................................................................................ 19
ENSVER ........................................................................................................................... 20
FIELD ................................................................................................................................ 21
FILEUNIT .......................................................................................................................... 22
INCLUDE .......................................................................................................................... 23
IPRDIMS ........................................................................................................................... 24
IPROPTNS ........................................................................................................................ 25
LAB ................................................................................................................................... 26
METRIC ............................................................................................................................ 27
NETBALAN ...................................................................................................................... 28
NETCONG ........................................................................................................................ 29
NETCONP ......................................................................................................................... 30
NETCONW ........................................................................................................................ 32
NETIPRG .......................................................................................................................... 33
NETIPRP ........................................................................................................................... 34
NETIPRW .......................................................................................................................... 35
NETLOG ........................................................................................................................... 36
NETSINKG ........................................................................................................................ 37
NETSINKW ....................................................................................................................... 39
NETSOLVE ....................................................................................................................... 41
NETSRCP ......................................................................................................................... 42
NETTPRES ....................................................................................................................... 45
NETTYPE .......................................................................................................................... 46
NETWORK ........................................................................................................................ 47

i
Intersect Eclipse Network Simulator user guide

NGASREM ........................................................................................................................ 48
NOILREM .......................................................................................................................... 49
NWATREM ........................................................................................................................ 50
PVT-M ............................................................................................................................... 51
RPTNET ............................................................................................................................ 52
TITLE ................................................................................................................................ 53
VFPALIAS ......................................................................................................................... 54
VFPIDIMS ......................................................................................................................... 55
VFPINJ .............................................................................................................................. 56
VFPOPTNS ....................................................................................................................... 59
VFPPDIMS ........................................................................................................................ 61
VFPPROD ......................................................................................................................... 62

ii
Intersect Eclipse Network Simulator user guide

1
Introduction
The Eclipse Network Simulator (ENS) is designed to be a simple tool for the reservoir engineer to evaluate
pressure losses in both production and injection networks. ENS functions in two modes, a standalone mode
in which the network can be modeled and tested with various boundary conditions and constraints, and a
coupled mode in which the network can be balanced with the Intersect reservoir simulator.
ENS uses the same technology as is in the Eclipse 300 Extended Network option and hence offers similar
functionality. Specifically, pressure losses within the network are computed from vertical flow performance
(VFP) tables (also known as hydraulics tables in Intersect) interpolated on surface phase flow rates or
ratios. As such there is no fluid modeling undertaken within ENS and compositional affects are not
accounted for. An ENS model can be thought of as a proxy for a more sophisticated network model, but
one which may better suited to full field simulations.
ENS models are either three phase production, water injection or gas injection networks. The topology of
the network may either be a simple dendritic gathering tree or a non-dendritic gathering structure that
contains loops. An ENS network has a fixed pressure terminal node and source or sink boundary conditions
representing the wells. ENS has the concept of chokes and pumps, however these are not devices that the
user controls, rather the pressure drops over these devices are calculated by ENS in order that specified
constraints are honored.
The input model for ENS is an Eclipse-style text file with a limited number of keywords. The principal
keywords are those defining the network topology, the VFP tables associated with the branches, the
network boundary conditions and any constraints present in the network. The same data file also serves as
the input when ENS is used in the coupled mode.
The output from the standalone ENS version is a simple print file documenting the network topology
properties and network solution. There is no concept of time in the standalone mode as the network model
is purely steady state and hence each solve is independent of any other. When running coupled to Intersect,
Field Management manages the simulation timeline and any modifications required to the network during
the simulation are issued by Field Management. Field Management also collates the network solution over
the simulation period and can generate Eclipse format summary files containing this data.

Introduction
1
Intersect Eclipse Network Simulator user guide

2
Installation and licensing
ENS is installed as part of the Intersect simulator installation and the standalone ENS executable is placed
in the same directory as the Intersect simulator, usually a subdirectory of the ecl directory.
The standalone version of ENS can be run from the Schlumberger Simulation Launcher by creating a new
program, using File->New->New Program, then select 'other' and add the program. Enter the details as
shown below, making sure to place the %FILE% command line parameter in double quotes.
• Give ENS as the Name of Program.

• Give the path to the latest [Link] file as the Program to Run; for example C:\ecl\20xx.x
\IX\x64_msmpi\[Link].
• Enter “%FILE%” in the Command Line Parameters box.
• Select Can accept a file as the Input Settings.
• Give DATA as the File Extensions.
The table below details the licenses required to run ENS in standalone mode and also coupled to the
Intersect simulator.

Product Name License String Functionality

ENS networks Enables ENS 20xx.x network simulator using Eclipse network license.
This licensing is only required if running ENS in standalone mode.

The installation instructions for the Intersect simulator are provided in the Intersect Installation and
Deployment Guide. The licenses required for Intersect when running coupled ENS simulations can be
found in the Intersect Release Notes.

Installation and licensing

2
Intersect Eclipse Network Simulator user guide

3
ENS network models
Whether creating a network for standalone analysis or for coupled runs with Intersect, an ENS data file
must first be constructed. The ENS data file should have the file extension .DATA. The ENS data file
follows the same syntax rules as an Eclipse data file and which are documented in the Data File Overview
in the Eclipse Reference Manual. These rules include requiring keywords to start in the first columns and
that character strings containing spaces be enclosed in single quotes.
The ENS data file is divided into a RUNSPEC and SCHEDULE section. As with Eclipse, the dimensions of
the model and key parameters are specified in the RUNSPEC section. The type of network is specified with
the NETTYPE keyword and the unit system using the FIELD , METRIC , PVT-M or LAB keywords. The
dimensions of the network are specified with the NETWORK keyword and the dimensions for the VFP tables
with the VFPPDIMS keyword for production networks, or VFPIDIMS keyword for injection networks.
The minimum dimensions required for a model are reported in the ENS print file at the end of a successful
simulation.
The network topology is specified in the SCHEDULE section using the BRANPROP keyword. This keyword
follows the same syntax the Eclipse keyword, however unlike Eclipse multiple networks cannot be
accommodated within a single ENS model. Each ENS model must consist of a single network terminating
at a single node, but the network does not have to be a dendritic, gathering tree structure and may contain
loops. The pressure at the terminal node is set using the NETTPRES keyword.

Production networks
For a production network, the VFP tables associated with the branches are supplied using the VFPPROD
keyword, frequently using separate files using the INCLUDE keyword. Source boundary conditions
representing wells or import streams are defined using the NETSRCP keyword. Source boundary conditions
have a status of either OPEN or SHUT. When a source is shut, a zero flow rate boundary condition is
applied; however the remaining keyword data is still required to ensure that the network solution is
consistent between a SHUT source and a source that is unable to flow due to the network pressure being
too low. Source conditions can be one of three types:
• Constant rate where the phase rates are specified.
• Productivity index (PI) where the phases rates are proportional to the pressure difference between the
node and the specified no-flow pressure.
• Inflow performance relationship (IPR) where the phase flow verses pressure is specified using a table.

ENS network models

3
Intersect Eclipse Network Simulator user guide

If the IPR source condition is used then the tabulated data is supplied with the NETIPRP keyword.
The NETSRCP keyword additionally allows a wellhead choke to be specified. If a wellhead choke is active
and an IPR source condition is being used, the pressure drop over the choke will automatically be adjusted
by ENS to ensure that the pressure at the source node does not fall below the minimum pressure in the IPR
table. In this manner the well is controlled so as not to exceed the maximum flow rates in the IPR table.
The position of the wellhead choke will depend on whether the network conceptually starts at bottom hole
or tubing head.
Within a production network, only source boundary conditions can be specified although water and gas can
be removed from the network using the NGASREM and NWATREM keywords, at either a specified fraction
or rate.
Constraints can be placed on node flow rates and pressures and ENS will then control the pressure drop at
these locations in order to meet the specified constraint. This functionality can be thought of as an
automatic choke. Not all rate constraints are achievable since the minimum and maximum flow rates in the
network depend on the boundary conditions. If a rate constraint lies outside of the achievable range then
ENS will modify the constraint to the extents of the achievable range and notify the user. In a production
network node pressures can be constrained to be higher than the free flowing value, and flows to be less
than the free flowing value by choking the flow at the specified node. If a node pressure is less than the free
flowing pressure or a flow rate higher than the free flowing rate is required, then pressure assistance can be
activated in the NETSRCP keyword. This option enables a negative pressure drop to be calculated
emulating a pump. In the ENS model there is no concept of pump power and the pump is assumed to be
sufficiently powerful to achieve the constraint target.
Having defined the topology and associated boundary conditions, a solve of the network can be requested
using the NETSOLVE keyword. The calculated node pressures and flow rates are reported in the ENS print
file. The user can then modify aspects of the network model (such as the source conditions and constraints)
before instructing further network solves. The flow rates reported in the ENS print file have the convention
that positive values are taken as flows from the source boundaries in the direction of the terminal node. The
RPTNET keyword can also be used to control the amount of information that is included in the print file as
well as the numerical precision of the reports.

Injection networks
Creating an ENS injection network model follows the same pattern as creating a production network
model. ENS supports modeling either water or gas injection networks, but not multiphase injection
networks. The VFP tables associated with the network branches are entered using the VFPINJ keyword,
either in the main data file or using included files. The boundary conditions for a gas injection network are
specified using the NETSINKG keyword, and for a water injection network using the NETSINKW keyword.
The constant rate, injectivity index (II) and IPR based boundary conditions are available for injection
networks with IPR tables provided using either the NETIPRG or NETIPRW keywords. As with production
networks, the location of a wellhead choke can be specified in the sink boundary condition keywords and,
if present, the pressure drop at this location is adjusted to ensure that the pressure at the boundary node
does not exceed the maximum pressure in the associated IPR table.
Constraints can also be applied to injection networks using the NETCONG and NETCONW keywords,
including the option to use pressure assistance to attain the constraint value.
To solve an injection network, the NETSOLVE keyword is again used and modifications to the network can
be made before requesting further solves. The flow rates reported in the ENS print file have the convention
that positive values are taken as flows from the terminal node in the direction of the sink boundaries.

ENS network models

4
Intersect Eclipse Network Simulator user guide

4
Network solution method
ENS simultaneously solves the non-linear system of equations arising from the network. The governing
equations for the network are:
1. Pressure drop: The pressure drop along a branch is equal the pressure drop for the associated VFP
table, at the branch phase flow rates.
2. Phase conservation: The phase outflow of a node equals the sum of the phase inflow to that node.
The variables and their placement on the nodes and branches depend on whether the network is a dendritic
gathering tree or is a non-dendritic gathering structure that has loops.
For a dendritic network the variables are pressure and surface flow rates and in the differencing scheme
they are placed at each network node.
For a non-dendritic network, the node variables are pressure, a surface water flowing fraction and a surface
gas flowing fraction. A total surface volume rate variable is assigned to each of the branches. This split is
necessary to ensure that the correct upstream fluid (defined by the water and gas fractions at the appropriate
node) is advected by positive or negative flows in a branch. This flexibility is necessary as in looped
networks it cannot be assumed that all the branch flows are positive towards the sink terminal node for
production networks or negative away from source terminal node for injection networks.
In terms of aligning variables with equations, ENS always has a fixed pressure for the terminal node so for
a network of N nodes and N-1 branches, the pressure drop equation (1) generates N-1 equations for the
remaining N-1 pressure variables. For each phase, the conservation equation (2) generates N equations for
the N flow rate variables.
At the source and sink boundary nodes the conservation equation (2) is substituted for the boundary
condition equation. In the case of a constant rate boundary condition the node outflow is set equal to the
specified rates. For a PI, II or IPR boundary condition, the node outflow is computed as a function of the
node pressure. If the network solution is such that a source or sink cannot flow ENS indicates that this
boundary node has no operating point.
For models with constraints, an additional pressure drop term is added at the constrained node and this
extra degree of freedom is used to enforce the constraint. In the case of multiple constraints the limiting
constraint is identified and the extra degree of freedom is used to enforce this constraint.
The complete non-linear system is solved using a Newton iteration with analytical derivatives. The
convergence criteria for the Newton iteration is that the maximum pressure change between iterations for
all nodes is less than the tolerance specified by item 3 of the NETBALAN keyword. Item 2 of the
NETBALAN keyword specifies the maximum number of consecutive Newton iterations that ENS will

Network solution method

5
Intersect Eclipse Network Simulator user guide

perform before declaring the solution unconverged. Note however, ENS has an outer iteration during which
the active constraints and the ability of boundary nodes to flow is established, and hence the total number
of iterations reported by ENS can be higher than the maximum given in the NETBALAN keyword.
The complexity of a network largely depends on the nature of the VFP curves used since these introduce
the majority of the non-linearities in the system. These VFP tables should cover the range of operating
pressures and rates expected in the network since large scale extrapolation of the tables can be a source of
convergence issues. Note, if the flow in certain branches is expected to fall to zero due to a well dying in a
coupled simulation, then the associated VFP tables should also include low flow rates. If convergence
issues are experienced in ENS, the following checks should be made:
1. Ensure the network solution is within the extents of the VFP data so that extrapolations are not
occurring.
2. Ensure that the VFP data does not contain extreme values (sometimes added by the generating
package to indicate unphysical flow regimes). Even if the network solution does not enter this regime,
looking up points close to these extreme values can generate large pressure drops.
3. Plot the VFP curves in Petrel and assess the quality of the data. If acceptable, stabilize unstable curves.
(Refer to Well modeling in theIntersect Technical Description, in particular the Hydraulics tables
section, for a description of this stabilization.)
4. Negative pressures, whilst not physically meaningful, can be created in ENS since the pressure
differences along the branches are obtained purely from the VFP data. The presence of negative
pressures in the solution indicates that the VFP data is being used outside of its valid range.
5. If constraints have been placed on the network, investigate removing them.
6. If tubing head chokes have been used in the network, investigate removing them.
It is worth noting that if the network has branches that only meet at the terminal node then these branches
are all independent of each other and can be modelled as separate ENS networks if desired.

Network solution method

6
Intersect Eclipse Network Simulator user guide

5
Coupling with the Intersect
reservoir simulator
ENS can be coupled to the Intersect reservoir simulator through Intersect Field Management. There is no
additional functionality provided when running ENS in its coupled mode over that available in the
standalone version of ENS. The fundamental algorithm employed by Field Management for coupling to a
network simulator is to generate inflow performance relationship (IPR) tables for the coupled wells,
tabulating pressure versus phase flow rates in the interval between the maximum flowing rate due to any
constraints imposed on the wells such as BHP or flow rate limits, and the pressure at which the well cannot
flow. These IPR tables are then passed to ENS and are used as boundary conditions in a network solve.
Since Field Management will pass IPR tables to ENS the maximum dimension of an IPR table in ENS
should be consistent with the size of tables generated by Field Management. The maximum size of the IPR
table in ENS is set using the IPRDIMS keyword and a value at least two greater than the number of IPR
points requested in Field Management should be used since, when necessary, up to two extra no-flow or
zero-pressure points are inserted into the tables. Finally Field Management queries the ENS network and
uses it to control the coupled wells. You should consult the Field Management documentation, particularly
Surface networks in the Intersect User Guide for information as to how to construct coupled simulations in
Intersect.
To create a coupled simulation model, first an ENS model must be prepared. The ENS model should run
without errors in the standalone version of ENS. Once a valid ENS model has been built, it can be coupled
to Intersect by adding the ENS input file, along with the file path, to the Intersect AFI file. An example is
shown below:

SIMULATION IX "CASE" {
INCLUDE "CASE_ECL2IX.gsg"
INCLUDE "CASE_ECL2IX_IX.ixf"
INCLUDE "CASE_reservoir_edits.ixf"
}

SIMULATION FM {
INCLUDE "CASE_ECL2IX_FM.ixf"
INCLUDE "CASE_fm_edits.ixf"
}

SIMULATION ENS "ENS_NETWORK" {

INCLUDE ".\ens_network\ENS_NETWORK.DATA"
}

Multiple ENS models can be added to a simulation if required. More details can be found in Intersect input
format in the Intersect User Guide.

Coupling with the Intersect reservoir simulator

7
Intersect Eclipse Network Simulator user guide

Field Management will read and process the ENS model up to the end of the input file. The ENS network
will then remain active awaiting further instruction from Field Management. Within Field Management the
network is given the name specified in the AFI file (ENS_NETWORK in the preceding example). When
running in coupled mode ENS continues to generate a separate print file which has the file name root
generated from the name of the Intersect data file concatenated with an underscore and the name of the
ENS data file (CASE_ENS_NETWORK in the preceding example) to avoid any conflicts with other output
files. The ENS print file is generated in the same directory as the Intersect output files. In addition to the
ENS print file, Field Management can compile the network solutions into a summary file that can be
viewed in Petrel. Field Management enables many network properties to be output in the summary files
some of which, like fluid component properties and pump and compressor properties are not applicable to
the ENS model and are reported with zero values. Note also that in an injection network the flow
convention for ENS is that positive values imply flow from the terminal source to the well boundaries. In
order to fully utilize Petrel's network visualization functionality it is recommended to enable the
extended_report_names option using the following IXF content.

OptionManager {
set_int_option(name="extended_report_names" value=1)
}

For further details on the summary file reporting available with Field Management consult Reporting node
reference in the Intersect User Guide.
Once the ENS model has been loaded by Intersect, the Intersect representation of the network is created
after which the user can control aspects of the network through the Intersect IXF input language. However,
the topology of the network may not be altered during a simulation and none of the network junctions,
pipes and devices can be closed to flow. Details of the supported functionality is given in the next section.
If the network component of a coupled simulation needs further investigation or analysis then the logging
functionality can be used. To use this option the NETLOG keyword should be added to the start of the ENS
input file and the model ran in coupled mode. With the logging feature active a new input file will be
created including equivalent keywords for all the communications between Field Management and ENS.
This file can then be run in standalone mode and the behavior of the network studied further.

Note: When emulating the Eclipse network option with Intersect and ENS, the THP limits on the coupled
wells should be removed since, in the Eclipse implementation, these values are superseded by the network
solution, while in Intersect they will be applied in addition to the network solution and can cause wells to
shut in Intersect whilst remaining open in Eclipse.

Intersect supported functionality

The Intersect framework provides a common interface for network simulators through which the Field
Management can control supported network simulators. Since every network simulator differs to some
extent in functionality, the extent to which this interface is implemented differs for each network simulator.
In the following section the ENS functionality exposed via the Field Management interface is documented.
Firstly it is worth noting that the network simulator is responsible for constructing the network topology
from the following nodes. These nodes cannot be created by Field Management regardless of the network
simulator being used.

Node Description
Network Represents the surface network.

Coupling with the Intersect reservoir simulator

8
Intersect Eclipse Network Simulator user guide

Node Description
NetworkPipe Represents the pipes of the network connecting nodes and devices. A
network pipe is created for each branch defined in the BRANPROP
keyword.
NetworkJunction Represents the junctions or internal nodes within the network. A
network junction is created for each internal node defined in the
BRANPROP keyword.
NetworkSinkBoundary Represents the sink boundary node in a production network. A single
network sink boundary is created in a production network
corresponding to the terminal node specified in the BRANPROP
keyword.
NetworkSourceBoundary Represents the source boundary node in an injection network. A single
network source boundary is created in a injection network
corresponding to the terminal node specified in the BRANPROP
keyword.
NetworkWellBoundary Represents the well boundary in the network. A network well boundary
is created for every node defined in the NETSRCP, NETSINKG and
NETSINKW keywords for production, gas injection and water injection
networks respectively. Network well boundaries can be coupled to wells
in a reservoir simulation. Note however, network well boundaries are
not created for hanging nodes (nodes for which no boundary conditions
have been set) and therefore these nodes cannot be coupled to.
NetworkChoke Represents a device modeling a choke. A network choke is created if
the "use wellhead choke" is set by item 12 of the NETSRCP keyword,
and item 8 of the NETSINKG or NETSINKW keywords. The location of
the choke may also be altered to match the topology of the physical
network using item 13 of the NETSRCP keyword, and item 9 of the
NETSINKG or NETSINKW keywords.
NetworkCompressor Represents a device modeling a compressor. A network compressor is
created in a gas injection network when pressure assistance is available
for a given constraint via item 4 of the NETCONG keyword.
NetworkGasLift Represents a device modeling gas lift within the network. This type of
device is not supported in ENS.
NetworkPump Represents a device modeling a pump. A network pump is created in
production network or water injection network when pressure assistance
is available for a given constraint via item 7 of the NETCONP or item 4
of the NETCONW keyword respectively.
Table 5.1: Intersect Field Management Network
The following lists provide details of the currently supported fields on the network nodes.

Node Field Details

Network VerbosityLevel This field can be used to set the verbosity of output in
the ENS print file. Setting this field is equivalent to
setting item 1 of the keyword RPTNET.

Coupling with the Intersect reservoir simulator

9
Intersect Eclipse Network Simulator user guide

Node Field Details

NetworkPipe HydraulicsTable This field can be used to set the VFP table for a
branch. The name of the VFP table is either the
number of the VFP table or the name set in the
VFPALIAS keyword. This functionality is not
currently supported for branches that form loops in
the network.
GasLift This field can be used to set the artificial lift quantity
to be used in the VFP interpolation. Only the property
LIFT_GAS_INJECTION_RATE is supported by
Field Management. This functionality is not currently
supported for branches that form loops in the
network.
NetworkJunction Constraints This field can be used to set constraints on the
network.
For production networks this is equivalent to setting
items 2-6 in the NETCONP keyword and therefore the
following constraints are valid:
• MAX_GAS_FLOW_RATE
• MAX_LIQUID_FLOW_RATE
• MAX_OIL_FLOW_RATE
• MAX_WATER_FLOW_RATE
• MIN_PRESSURE
For gas injection networks this is equivalent to setting
items 2-3 of keyword NETCONG and therefore the
following constraints are valid:
• MAX_GAS_FLOW_RATE
• MAX_PRESSURE
For water injection networks this is equivalent to
setting items 2-3 of keyword NETCONW and therefore
the following constraints are valid:
• MAX_WATER_FLOW_RATE
• MAX_PRESSURE
NetworkSinkBoundary Model Only the CONSTANT_PRESSURE model can be
used with ENS.
Pressure The terminal pressure of the network. This is
equivalent to specifying the pressure using the
NETTPRES keyword.

Coupling with the Intersect reservoir simulator

10
Intersect Eclipse Network Simulator user guide

Node Field Details

NetworkSourceBoundary Model Only the CONSTANT_PRESSURE model can be
used with ENS.
Pressure The terminal pressure of the network. This is
equivalent to specifying the pressure using the
NETTPRES keyword.
NetworkWellBoundary Status The network well boundary status can be set to
OPEN or CLOSED. This is equivalent to setting item
2 of the NETSRCP, NETSINKG and NETSINKW
keywords. Note, setting the status of the network well
boundary will not affect the status of the coupled well
and if the intention is to shut both the well and the
network well boundary then the well should be closed
instead.
NetworkChoke IsActive This field can be used to set network chokes active or
inactive. This is equivalent to setting item 12 in the
NETSRCP keyword in production networks, item 8 in
the NETSINKG in gas injection networks and item 8
in the NETSINKW keyword in water injection
networks to YES or NO.
NetworkCompressor IsActive This field can be used to set network compressors
active or inactive. This is equivalent to setting item 5
of the NETCONG keyword to YES or NO.
NetworkPump IsActive This field can be used to set network pumps active or
inactive. This is equivalent to setting item 8 of the
NETCONP keyword in a production network or item 5
of the NETCONW keyword in a water injection
network to YES or NO.
Table 5.2: Supported Intersect Field Management nodes and fields
The following list provides details of the currently supported network actions.

Node Description
ConfigureNetworkPipeAction This action sets properties for a list of network pipes. It can
only be used to set the pipe hydraulics table and gas lift
value. The action cannot be used to change the status or
connectivity of the pipe.
ModifyNetworkChokeAction This action can be used to activate or deactivate a list of
network chokes. It cannot be used to adjust properties of
chokes such as choke diameter.
ModifyNetworkCompressorAction This action can be used to activate or deactivate a list of
network compressors. It cannot be used to adjust properties
of compressors such as compressor power.
ModifyNetworkPumpAction This action can be used to activate or deactivate a list of
network pumps. It cannot be used to adjust properties of
pumps such as pump power.
Table 5.3: Supported Intersect Field Management Network Actions

Coupling with the Intersect reservoir simulator

11
Intersect Eclipse Network Simulator user guide

More information on the use of networks in Intersect can be found in:

• Field Management Node Reference in the Intersect User Guide.
• Field Management in the Intersect Technical Description.

Example
The example below shows how a typical ENS production network is represented in Intersect. The ENS
keywords below describe a production network with thirteen branches, a single sink and five well
boundaries. The network structure is all defined in the keyword BRANPROP. The properties of the well
boundaries are defined in the NETSRCP keyword and use the default locations for the placement of the
wellhead chokes. The NETCONP defines pressure assistance to be available on the two nodes 'N2' and
'N5'.

BRANPROP
'N6' 'N5' 1 /
'N5' 'N4' 3 /
'N4' 'N3' 9999 /
'N3' 'N2' 9999 /
'N2' 'FIELD' 9999 /
'PL-A1' 'N7' 9999 /
'N7' 'N2' 1 /
'PL-A2' 'N3' 9999 /
'SC-B' 'N8' 9999 /
'N8' 'N4' 2 /
'SC-C1' 'N9' 9999 /
'N9' 'N5' 3 /
'SC-C2' 'N6' 9999 /
/

NETSRCP
'SC-C2' 'OPEN' 'PI' 3* 2000 15 12 1/
'SC-C1' 'OPEN' 'PI' 3* 2000 15 12 1/
'SC-B' 'OPEN' 'PI' 3* 2000 15 12 1/
'PL-A2' 'OPEN' 'PI' 3* 2000 15 12 1/
'PL-A1' 'OPEN' 'PI' 3* 2000 15 12 1/
/

NETCONP
'N2' 100000 4* YES NO /
'N5' 5* YES /
/

This network is shown in the print file of the ENS simulation as:

Production Network Hierarchical Structure

-----------------------------------------

FIELD
|
|---N2
|
|---N7
| |
| |---PL-A1
|
|---N3
|
|---PL-A2
|---N4
|
|---N8
| |
| |---SC-B
|

Coupling with the Intersect reservoir simulator

12
Intersect Eclipse Network Simulator user guide

|---N5
|
|---N9
| |
| |---SC-C1
|
|---N6
|
|---SC-C2

Node Details and Gas/Water Removal Settings

-------------------------------------------
+------------------------------------------------------------------+
| Node : Node : Gas Rate : Gas Frac : Water Rate : Water Frac |
| Name : Type : MSCF/DAY : : STB/DAY : |
+------------------------------------------------------------------+
| FIELD : TERMINAL : : : : |
| N2 : : : : : |
| N7 : : : : : |
| PL-A1 : SOURCE : : : : |
| N3 : : : : : |
| PL-A2 : SOURCE : : : : |
| N4 : : : : : |
| N8 : : : : : |
| SC-B : SOURCE : : : : |
| N5 : : : : : |
| N9 : : : : : |
| SC-C1 : SOURCE : : : : |
| N6 : : : : : |
| SC-C2 : SOURCE : : : : |
+------------------------------------------------------------------+

This network is shown in the print file of the Intersect-ENS coupled simulation as:

REPORT Properties of FM network ENS_NETWORK:

Coupling with the Intersect reservoir simulator

13
Intersect Eclipse Network Simulator user guide

| Junction | N2 N3 N4 N5 N6 N7 N8 N9 |
+--------------------------------------------------+

REPORT Connection info of FM network ENS_NETWORK devices:

Note that network chokes have been added at the wellheads and pumps have been added at nodes 'N2'
and 'N5' as they have pressure assistance available.

Coupling with the Intersect reservoir simulator

14
Intersect Eclipse Network Simulator user guide

6
Keywords

Keywords
15
Intersect Eclipse Network Simulator user guide

BRANPROP Defines the network branches

ENS
This keyword specifies the topology of the network by specifying the branches between nodes.
RUNSPEC The network does not have to be a dendritic (gathering tree) structure, but it must terminate at a single
x SCHEDULE node. If two or more branches share the same node as defined in item 1, the first branch will be considered
as a dendritic branch with all subsequent branches being non-dendritic, forming loops in the network. This
convention only matters if constraints are defined on the flows in the network as these only apply to
dendritic branch flows and not flows in any non-dendritic branches. (See the NETCONP, NETCONG and
NETCONW keywords.)
This keyword is followed by any number of records, each containing the following items of data and
terminated with a slash (/). The set of records must end with a blank record, containing only a slash (/).
1. Name of the branch's downtree node (up to 32 characters).
This is the node that is nearer to the wells and further from the terminal node at the top of the tree. In a
production network it is the branch's inlet node; in an injection network it is the branch's outlet node.
2. Name of the branch's uptree node (up to 32 characters).
This is the node that is nearer to the terminal node at the top of the tree. In a production network it is
the branch's outlet node; in an injection network it is the branch's inlet node.
3. VFP table number for the branch.
In a production network this should be a production VFP table number corresponding to a table
supplied with the VFPPROD keyword. In an injection network this should be an injection VFP table
number corresponding to a table supplied with the VFPINJ keyword.
Two or more network pipelines may share the same VFP table if they have similar pressure loss
characteristics.
A value of 9999 can be entered to indicate that there is no pressure loss in the network branch defined
by items 1 and 2.
4. Artificial Lift Quantity (ALQ) used in the pressure loss calculations for the branch.
This quantity is used as a look-up parameter for the VFP table in item 3. It may be regarded as the
pump or compressor power, for example, according to the definition used in the construction of the
table.
UNITS: These depend on what the ALQ was meant to represent when the table was created.
DEFAULT: 0
5. Pressure adjustment made to the branch pressure loss.
Refer to item 3 of VFPOPTNS for the ways in which this adjustment can be applied.
UNITS: bars (METRIC), psi (FIELD), atm (LAB), atm (PVT-M)
DEFAULT: 0.0
6. Branch pressure loss scaling factor.
DEFAULT: 1.0
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.

Keywords
16
Intersect Eclipse Network Simulator user guide

Example
Specify a network with VFP table numbers between 1 and 6 and culminating in them terminal node
'FIELD'.

BRANPROP
GB2 N4 3 /
GA2 N3 2 /
GB1 N2 1 /
GA1 N1 9999 /
N4 N3 4 /
N3 N2 4 /
N2 N1 5 /
N1 FIELD 6 100 /
/

Keywords
17
Intersect Eclipse Network Simulator user guide

END Logical end of the input file

ENS
This keyword marks the end of the input file and keywords beyond it are not processed. The keyword is
only required if the user wishes to stop the simulation before the end of the input file.
x RUNSPEC
x SCHEDULE This keyword has no arguments.
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.

Example
END

Keywords
18
Intersect Eclipse Network Simulator user guide

ENDINC Logical end of include file

ENS
This keyword terminates the input of data from an INCLUDE file, returning control to the reading of the
main file.
x RUNSPEC
x SCHEDULE This keyword should not normally be entered, as an ENDINC is generated automatically at the end of the
included file. It may, however, be used to end the reading of an included file before the actual end of file.
This keyword has no arguments.
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.

Example
ENDINC

Keywords
19
Intersect Eclipse Network Simulator user guide

ENSVER ENS minimum version

ENS
This keyword specifies the earliest version of ENS for which the model is designed for. If the model is ran
in an earlier version of ENS an error will be given.
x RUNSPEC
SCHEDULE The data must be terminated by a slash (/).
1. Minimum version.
DEFAULT: 2014.1

Example
Specify that the model will run in all versions after and including 2014.1.

ENSVER
2014.1 /

Keywords
20
Intersect Eclipse Network Simulator user guide

FIELD Field units are to be used

ENS
This keyword indicates that field units are to be used. Note, the default unit convention is METRIC.
x RUNSPEC This keyword has no arguments.
SCHEDULE
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.

Example
FIELD

Keywords
21
Intersect Eclipse Network Simulator user guide

FILEUNIT Confirms units of a data set

ENS
This keyword should be followed by an item, which specifies the units being used. The data should be
terminated by a slash (/).
x RUNSPEC
x SCHEDULE The possible values of the option are:

METRIC The data is specified using the same unit system as for the METRIC keyword.

FIELD The data is specified using the same unit system as for the FIELD keyword.

LAB The data is specified using the same unit system as for the LAB keyword.

PVT-M The data is specified using the same unit system as for the PVT-M keyword.

There is no default value.

This keyword does not provide unit conversion between different unit systems. It is intended to facilitate
checking where, for instance, a data set may contain several sections in separate files which were created
by different programs possibly using different units. All occurrences of FILEUNIT in a data set have to
match.
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.

Example
FILEUNIT
METRIC /

Keywords
22
Intersect Eclipse Network Simulator user guide

INCLUDE Include the contents of another named file

ENS
This keyword should be followed by the name of a file from which input is to be taken. This file will be
opened, and read to the end of the file unless an ENDINC keyword is encountered. The file is then closed,
x RUNSPEC
and input resumed from the main file, starting from the next keyword after the INCLUDE keyword.
x SCHEDULE
The INCLUDE file name may have up to 132 characters. File names are case sensitive on the Linux
operating system.
The data should be terminated by a slash (/).
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.

Example
INCLUDE
BRANCH_1.VFP /

Keywords
23
Intersect Eclipse Network Simulator user guide

IPRDIMS IPR table dimensions

ENS
This keyword describes the dimensions of the IPR tables that can be used in the definition of network
sources and sinks.
x RUNSPEC
SCHEDULE The data must be terminated by a slash (/).
1. The maximum number of points in any IPR table.
DEFAULT: 15

Example
Allocate sufficient storage for all IPR tables to have up to 15 points.

IPRDIMS
15 /

Keywords
24
Intersect Eclipse Network Simulator user guide

IPROPTNS IPR table usage options

ENS
This keyword controls a set of options that apply to the use of inflow performance relationship tables for
source and sink boundary conditions. It is followed by a single record terminated by a slash (/). The record
RUNSPEC
consists of two items of data:
x SCHEDULE
1. Restriction placed on the pressure column of IPR tables. Note that if this item is set, this keyword
should be placed before the IPR table keywords that it relates to.
INC_MONOTONIC The values in the pressure column must increase monotonically down the rows
of IPR tables. If it does not, an error message is issued and the network
simulation stops.

NONE No restriction is placed on the values in the pressure column. This triggers a
different method of finding the solution between the inflow curve defined by an
IPR and the outflow curve defined by the first network pipe encountered with a
VFP table. Non-monotonic IPRs can result in multiple solutions and the one
with the highest rate is always selected. The local stability of solutions is tested
and any unstable solutions are reported in a warning message.

DEFAULT: INC_MONOTONIC
2. Control on how IPR tables are extrapolated for rates if look-up pressures fall outside the range of the
pressure column in IPR tables.
CONST Constant value extrapolation is used for table rates. If the overall slope (∆Pressure/∆Rate)
of an IPR table is negative, a look-up pressure below the pressure range of a table returns
the maximum table phase rates. If the look-up pressure is above the table range, the
minimum table phase rates are returned. The reverse is true if the overall slope of the IPR
table is positive.
If the IPR table is built so that the maximum IPR table rates reflect the well's limiting
constraint, then constant value extrapolation can be used to impose the well's limits on a
source or sink node.

LINEAR Linear extrapolation is used for the table rates if the look-up pressure falls outside the
table's pressure column range.

DEFAULT: CONST
End data record with a slash (/).

Example
IPROPTNS
NONE CONST
/

Keywords
25
Intersect Eclipse Network Simulator user guide

LAB Lab units are to be used

ENS
This keyword indicates that lab units are to be used. Note, the default unit convention is METRIC.
x RUNSPEC This keyword has no arguments.
SCHEDULE
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.

Example
LAB

Keywords
26
Intersect Eclipse Network Simulator user guide

METRIC Metric units are to be used

ENS
This keyword indicates that metric units are to be used. Note, this is the default unit convention.
x RUNSPEC This keyword has no arguments.
SCHEDULE
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.

Example
METRIC

Keywords
27
Intersect Eclipse Network Simulator user guide

NETBALAN Network balancing parameters

ENS
This keyword specifies the convergence tolerance of the network and the iteration limit for the network
solve. The keyword does not affect convergence criteria of the coupling between ENS and a reservoir
RUNSPEC
simulator when used in a coupled solution.
x SCHEDULE
The keyword should be followed by a line containing the following data items, ending with a slash (/).
1. Not used.
2. Convergence tolerance for network nodal pressures.
UNITS: bars (METRIC), psi (FIELD), (FIELD), atm (LAB), atm (PVT-M)
DEFAULT: 1E-5 bars (METRIC), 1.45E-4 psi (FIELD), (FIELD), 9.869E-6 atm (LAB, PVT-M)
3. Maximum number of consecutive iterations allowed in the network balancing calculation.
DEFAULT: 20
4. The variable set used for the network solve.
1 Set 1 has flows and pressures at each network node. It is only suitable for dendritic, gathering tree
networks. If the network contains non-dendritic, loop-forming branches, the variables will be
automatically switched to set 2.

2 Set 2 has an overall flow on each network branch, and flowing fractions and pressures on the
nodes. It can be used for dendritic and non-dendritic networks.

DEFAULT: 1
5. The initial state of the network variables before the solve.
ESTIMATE The network pressures are set to the terminal node pressure and the flows are added
up through the gathering tree from the source nodes.

LAST_SOLVE The solve starts from the state of the last solve if the network structure has not been
changed between solves. If this is the case, the solve starts from the estimate
described above.

DEND_SOLVE For non-dendritic networks with loop-forming branches, the full solve starts from a
dendritic solve of this network with the loop-forming branches being ignored.

DEFAULT: ESTIMATE

Example
Specify a stricter tolerance, increase the maximum number of iterations that the can be taken during the
network solve, use variable set 2 and start the solve from the state of the last solve.

NETBALAN
1* 1e-6 30 2 'LAST_SOLVE' /

Keywords
28
Intersect Eclipse Network Simulator user guide

NETCONG Gas injection network constraints

ENS
This keyword specifies constraints on nodes in a gas injection network. The network will be constrained so
that the gas flow rates is less than or equal to the value specified, and that the pressure is also less than or
RUNSPEC
equal to the value specified. Note, the network can only be constrained if its capacity exceeds the values
x SCHEDULE
specified. If the network cannot attain the constraints then pressure assistance can be activated which
emulates the behavior of a compressor of the required power such that the most limiting constraint is
attained.
Values of zero correspond to the quantity being unconstrained and all the constraints on a node can be
removed by specifying only the node name and defaulting the remaining items. Re-specifying a node will
overwrite any existing constraints associated with the node.
Constraints in non-dendritic, looped networks are not currently supported.
The keyword consists of any number of records, each containing the following items. Terminate each
record with a slash. The set of records should be terminated with a blank record containing just a slash.
1. Node name
2. Maximum gas rate

UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0
3. Maximum pressure
UNITS: barsa (METRIC), psia (FIELD), (FIELD), atma (LAB), atma (PVT-M)
DEFAULT: 0.0
4. Pressure assistance available
NO Pressure assistance is not available for this node.

YES Pressure assistance is available for this node and may be activated for a subsequent solve.

DEFAULT: NO
5. Pressure assistance active
NO Pressure assistance not active.

YES Pressure assistance active.

DEFAULT: NO

Example
NETCONG
PL-A2 1* 1000 /
SC-C2 20000 1* YES YES /
/

Keywords
29
Intersect Eclipse Network Simulator user guide

NETCONP Production network constraints

ENS
This keyword specifies constraints on nodes in a production network. The network will be constrained so
that all the flow rates are less than or equal to the values specified, and that the pressure is greater or equal
RUNSPEC
to the value specified. Note, the network can only be constrained if its capacity exceeds the values
x SCHEDULE
specified. If the network cannot attain the constraints then pressure assistance can be activated which
emulates the behavior of a pump of the required power such that the most limiting constraint is attained.
Values of zero correspond to the quantity being unconstrained and all the constraints on a node can be
removed by specifying only the node name and defaulting the remaining items. Re-specifying a node will
overwrite any existing constraints associated with the node.
Constraints in non-dendritic, looped networks are not currently supported.
The keyword consists of any number of records, each containing the following items. Terminate each
record with a slash. The set of records should be terminated with a blank record containing just a slash.
1. Node name
2. Maximum oil rate

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0
3. Maximum gas rate

UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0
4. Maximum water rate

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0
5. Minimum pressure
UNITS: barsa (METRIC), psia (FIELD), (FIELD), atma (LAB), atma (PVT-M)
DEFAULT: 0.0
6. Maximum liquid rate

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0
7. Pressure assistance available
NO Pressure assistance is not available for this node.

YES Pressure assistance is available for this node and may be activated for a subsequent solve.

DEFAULT: NO
8. Pressure assistance active
NO Pressure assistance not active.

Keywords
30
Intersect Eclipse Network Simulator user guide

YES Pressure assistance active.

DEFAULT: NO

Example
Constrain the oil and water rates at the node PL-A2 and use pressure assistance to achieve the target gas
rate on node SC-C2.

NETCONP
PL-A2 1050 1* 300 /
SC-C2 1* 20000 3* YES YES /
/

Keywords
31
Intersect Eclipse Network Simulator user guide

NETCONW Water injection network constraints

ENS
This keyword specifies constraints on nodes in a water injection network. The network will be constrained
so that the water flow rates is less than or equal to the value specified, and that the pressure is also less than
RUNSPEC
or equal to the value specified. Note, the network can only be constrained if its capacity exceeds the values
x SCHEDULE
specified. If the network cannot attain the constraints then pressure assistance can be activated which
emulates the behavior of a pump of the required power such that the most limiting constraint is attained.
Values of zero correspond to the quantity being unconstrained and all the constraints on a node can be
removed by specifying only the node name and defaulting the remaining items. Re-specifying a node will
overwrite any existing constraints associated with the node.
Constraints in non-dendritic, looped networks are not currently supported.
The keyword consists of any number of records, each containing the following items. Terminate each
record with a slash. The set of records should be terminated with a blank record containing just a slash.
1. Node name
2. Maximum water rate

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

YES Pressure assistance is available for this node and may be activated for a subsequent solve.

DEFAULT: NO
5. Pressure assistance active
NO Pressure assistance not active.

YES Pressure assistance active.

DEFAULT: NO

Example
Constrain the pressure at the node PL-A2 and use pressure assistance to achieve the target water rate on
node SC-C2.

NETCONW
PL-A2 1* 1500 /
SC-C2 3000 1* YES YES /
/

Keywords
32
Intersect Eclipse Network Simulator user guide

NETIPRG Gas injection IPR table

ENS
This keyword specifies an inflow performance relationship table for a sink boundary condition. If the
pressure is outside the range of the table then constant extrapolation is applied to the rates.
RUNSPEC
x SCHEDULE The maximum number of lines of IPR table data is specified in the IPRDIMS keyword. Each record is
terminated with a slash (/).
1. Record 1: IPR table number
Table number
2. Record 2: IPR table data
Pressure The pressure values in the table must increase monotonically down the table (unless
item 1 of IPROPTNS is set to NONE).
UNITS: barsa (METRIC), psia (FIELD), (FIELD), atma (LAB), atma (PVT-M)
DEFAULT: 0.0

Gas The gas injection rates in the table must be nonnegative and should increase
injection monotonically down the table.
rate
UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)
DEFAULT: 0.0

Example
Example specifying IPR table number 2.

NETIPRG
2 /
400 0
800 30000
1200 50000
/

Keywords
33
Intersect Eclipse Network Simulator user guide

NETIPRP Production IPR table

ENS
This keyword specifies an inflow performance relationship table for a source boundary condition. If the
pressure is outside the range of the table then constant extrapolation is applied to the rates.
RUNSPEC
x SCHEDULE The maximum number of lines of IPR table data is specified in the IPRDIMS keyword. Each record is
terminated with a slash (/).
1. Record 1: IPR table number
Table number
2. Record 2: IPR table data
Pressure The pressure values in the table must increase monotonically down the table (unless
item 1 of IPROPTNS is set to NONE).
UNITS: barsa (METRIC), psia (FIELD), (FIELD), atma (LAB), atma (PVT-M)
DEFAULT: 0.0

Oil production The oil production rates in the table must be nonnegative and should decrease
rate monotonically down the table.

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0

Gas production The gas production rates in the table must be non-negative and should decrease
rate monotonically down the table.

UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0

Water The water production rates in the table must be non-negative and should decrease
production rate monotonically down the table.

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0

Example
Example specifying IPR table number 3.

NETIPRP
3 /
1000 12000 11000 6000
1500 7000 6000 3500
2000 0 0 0
/

Keywords
34
Intersect Eclipse Network Simulator user guide

NETIPRW Water injection IPR table

Water The water injection rates in the table must be non-negative and should increase
injection monotonically down the table.
rate
UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)
DEFAULT: 0.0

Example
Example specifying IPR table number 1.

NETIPRW
1 /
400 0
800 2000
1200 3000
/

Keywords
35
Intersect Eclipse Network Simulator user guide

NETLOG Logs all keywords and communications in a

simulation
ENS
This keyword logs all the input to the model supplied either using keywords or using the coupling with
Intersect. When ran in this mode ENS creates an additional output file with the same root name as the print
x RUNSPEC
file but with _LOG appended and the extension .DATA. This data file can then be run again in the
x SCHEDULE
standalone version of ENS.
The keyword has no associated data.

Example
Log the model, including the data supplied by the keywords.

-- start of input deck

NETLOG

-- start of keywords
RUNSPEC

METRIC

-- model description

END

Keywords
36
Intersect Eclipse Network Simulator user guide

NETSINKG Sink boundary conditions for gas injection

networks
ENS
This keyword specifies a sink boundary condition for a gas injection network.
RUNSPEC The keyword consists of any number of records, each containing the following items. Terminate each
x SCHEDULE record with a slash. The set of records should be terminated with a blank record containing just a slash (/).
1. Node name
2. Status
OPEN The boundary condition is open.

SHUT The boundary condition is shut and no fluid will enter the network from this boundary node.
However the following items of data must still be entered.

DEFAULT: OPEN
3. Source type
RATE Constant rate boundary condition, with the phase rates specified by items 3.

II Injectivity index boundary condition, with the no-flow pressure specified by item 4 and the
injectivity index specified by items 5. The gas phase flow rate is calculated as the pressure
difference between the network node and the no-flow pressure, multiplied by the phase index.
If the node pressure is less than the no-flow pressure a zero rate is applied and the sink does
not reverse flow.

IPR Inflow Performance Relationship table boundary condition, with the table number specified
by item 6. The table is specified with the NETIPRG keyword. If the node pressure lies outside
of the range of the associated IPR table constant extrapolation of the phase flow rate is
performed.

DEFAULT: RATE
4. Gas rate

UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0
5. Pressure
UNITS: barsa (METRIC), psia (FIELD), (FIELD), atma (LAB), atma (PVT-M)
DEFAULT: 0.0
6. Gas injectivity index

UNITS: sm3/day/bars (METRIC), Mscf/day/psi (FIELD), scc/hr/atm (LAB), sm3/day/atm (PVT-M)

DEFAULT: 0.0
7. IPR table number.
DEFAULT: 0
8. Use wellhead choke

Keywords
37
Intersect Eclipse Network Simulator user guide

YES The pressure at the boundary node is constrained to be less than or equal to the maximum
pressure in the corresponding IPR table by adjusting the pressure drop over the node specified
in item 9.

NO The pressure at the boundary node is not constrained.

DEFAULT: YES
9. Wellhead choke node
The node at which the choke is placed in order to limit the pressure to the maximum pressure in the
IPR table. If the network conceptually starts at tubing head then choke node is likely to be the same as
source node. If the network starts at bottom hole then the choke node is likely to be a different node
further up the network towards the terminal node. The node must lie between the boundary node and
the point at which other flow paths join this one
DEFAULT: The node specified in item 1

Example
Example specifying a constant outflow from the node PL-A2 and a productivity index based sink for node
SC-C2.

NETSINKG
PL-A2 OPEN RATE 10000 /
SC-C2 OPEN II 1* 1100 12.1 /
/

Keywords
38
Intersect Eclipse Network Simulator user guide

NETSINKW Sink boundary conditions for water injection

networks
ENS
This keyword specifies a sink boundary condition for a water injection network.
RUNSPEC The keyword consists of any number of records, each containing the following items. Terminate each
x SCHEDULE record with a slash. The set of records should be terminated with a blank record containing just a slash (/).
1. Node name
2. Status
OPEN The boundary condition is open.

SHUT The boundary condition is shut and no fluid will enter the network from this boundary node.
However the following items of data must still be entered.

DEFAULT: OPEN
3. Source type
RATE Constant rate boundary condition, with the phase rates specified by items 3.

II Injectivity index boundary condition, with the no-flow pressure specified by item 4 and the
injectivity index specified by items 5. The water phase flow rate is calculated as the pressure
difference between the network node and the no-flow pressure, multiplied by the phase index.
If the node pressure is less than the no-flow pressure a zero rate is applied and the sink does
not reverse flow.

IPR Inflow Performance Relationship table boundary condition, with the table number specified
by item 6. The table is specified with the NETIPRW keyword. If the node pressure lies outside
of the range of the associated IPR table constant extrapolation of the phase flow rate is
performed.

DEFAULT: RATE
4. Water rate

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0
5. Pressure
UNITS: barsa (METRIC), psia (FIELD), (FIELD), atma (LAB), atma (PVT-M)
DEFAULT: 0.0
6. Water injectivity index

UNITS: sm3/day/bars (METRIC), stb/day/psi (FIELD), scc/hr/atm (LAB), sm3/day/atm (PVT-M)

DEFAULT: 0.0
7. IPR table number.
DEFAULT: 0
8. Use wellhead choke

Keywords
39
Intersect Eclipse Network Simulator user guide

YES The pressure at the boundary node is constrained to be less than or equal to the maximum
pressure in the corresponding IPR table by adjusting the pressure drop over the node specified
in item 9.

NO The pressure at the boundary node is not constrained.

Example
Example specifying a constant outflow from the node PL-A2 and a productivity index based sink for node
SC-C2.

NETSINKW
PL-A2 OPEN RATE 5000 /
SC-C2 OPEN II 1* 1200 11.1 /
/

Keywords
40
Intersect Eclipse Network Simulator user guide

NETSOLVE Solves the network model

ENS
This keyword instructs the simulator to solve the network model with the current topology, boundary
conditions and any constraints specified.
RUNSPEC
x SCHEDULE This keyword has no arguments.

Example
NETSOLVE

Keywords
41
Intersect Eclipse Network Simulator user guide

NETSRCP Source boundary conditions for production

networks
ENS
This keyword specifies a source boundary condition for a production network.
RUNSPEC The keyword consists of any number of records, each containing the following items. Terminate each
x SCHEDULE record with a slash. The set of records should be terminated with a blank record containing just a slash (/).
1. Node name
2. Status
OPEN The boundary condition is open.

SHUT The boundary condition is shut and no fluid will enter the network from this boundary node.
However the following items of data must still be entered.

DEFAULT: OPEN
3. Source type
IPR Inflow Performance Relationship table boundary condition, with the table number specified
by item 11. The table is specified with the NETIPRP keyword. If the node pressure lies
outside of the range of the associated IPR table constant extrapolation of the phase flow rates
is performed.

PI Productivity index boundary condition, with the no-flow pressure specified by item 7 and the
phase indices specified by items 8, 9 and 10. The phase flow rates are calculated as the
pressure difference between the network node and the no-flow pressure, multiplied by the
phase indices If the node pressure is greater than the no-flow pressure a zero rate is applied
and the source does not reverse flow.

RATE Constant rate boundary condition, with the phase rates specified by items 3, 4 and 5.

DEFAULT: RATE
4. Oil rate

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0
5. Gas rate

UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0
6. Water rate

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0
7. Pressure
UNITS: barsa (METRIC), psia (FIELD), (FIELD), atma (LAB), atma (PVT-M)

Keywords
42
Intersect Eclipse Network Simulator user guide

DEFAULT: 0.0
8. Oil productivity index

UNITS: sm3/day/bars (METRIC), stb/day/psi (FIELD), scc/hr/atm (LAB), sm3/day/atm (PVT-M)

DEFAULT: 0.0
9. Gas productivity index

UNITS: sm3/day/bars (METRIC), Mscf/day/psi (FIELD), scc/hr/atm (LAB), sm3/day/atm (PVT-M)

DEFAULT: 0.0
10. Water productivity index

UNITS: sm3/day/bars (METRIC), stb/day/psi (FIELD), scc/hr/atm (LAB), sm3/day/atm (PVT-M)

DEFAULT: 0.0
11. IPR table number.
DEFAULT: 0
12. Use wellhead choke
YES The pressure at the boundary node is constrained to be greater or equal to the minimum
pressure in the corresponding IPR table by adjusting the pressure drop over the node specified
in item 13.

NO The pressure at the boundary node is not constrained.

DEFAULT: YES
13. Wellhead choke node
The node at which the choke is placed in order to limit the pressure to the minimum pressure in the
IPR table. If the network conceptually starts at tubing head then choke node is likely to be the same as
source node. If the network starts at bottom hole then the choke node is likely to be a different node
further up the network towards the terminal node. The node must lie between the boundary node and
the point at which other flow paths join this one
DEFAULT: The node specified in item 1
14. Lift gas rate.

UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: 0.0
15. Flag indicating how lift gas (item 14) associated with this source is to be modeled in a production
network.
NO No lift gas flows from this source into the network, only formation gas.

FLO Both lift gas and formation gas flow from this source into the network.

ALQ Lift gas is treated as an ALQ value in the VFP tables used to calculate the pressure drop across
the pipe attached to this source node.

Keywords
43
Intersect Eclipse Network Simulator user guide

Note: Lift gas from this source is only modeled in the network if the source type (item 3) is IPR or PI.
It is not accounted for if the type is RATE.

DEFAULT: NO

Example
Example specifying a constant source of gas and water into node PL-A2 and a productivity index based
source for node SC-C2.

NETSRCP
PL-A2 OPEN RATE 1* 47000 110 /
SC-C2 OPEN PI 3* 2201 13.5 5.0 1.3 /
/

Keywords
44
Intersect Eclipse Network Simulator user guide

NETTPRES Terminal node pressure

ENS
This keyword specifies the pressure at the terminal node. A network can only have one terminal node hence
only one line of data is required.
RUNSPEC
x SCHEDULE Terminate each record with a slash. The set of records should be terminated with a blank record containing
just a slash (/).
1. Node name
2. Pressure
UNITS: barsa (METRIC), psia (FIELD), (FIELD), atma (LAB), atma (PVT-M)
DEFAULT: 0.0

Example
Example specifying a terminal pressure for the terminal node FIELD.

NETTPRES
FIELD 500 /
/

Keywords
45
Intersect Eclipse Network Simulator user guide

NETTYPE Specify the type of network

ENS
This keyword specifies whether a production or injection network is being modeled. The keyword consists
of a single argument proceeded with a slash (/).
x RUNSPEC
SCHEDULE 1. Network type
PROD A three-phase production network.

WINJ A water injection network.

GINJ A gas injection network.

Example
Specify a production network

NETTYPE
PROD /

Keywords
46
Intersect Eclipse Network Simulator user guide

NETWORK Sets dimensions for extended network model

ENS
This keyword specifies the maximum dimensions of the network.
x RUNSPEC The data must be terminated by a slash (/).
SCHEDULE
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.
1. The maximum number of nodes in the network model.
DEFAULT: 20
2. The maximum number of branches in the network model.
DEFAULT: 20
3. The maximum number of branches connected to any one node in the network model.
DEFAULT: 20
The minimum dimensions required for a model are reported by ENS in the print file at the end of a
successful simulation.

Example
Specify a network with 12 nodes, 11 branches at a maximum number of 5 connections per node.

NETWORK
12 11 5 /

Keywords
47
Intersect Eclipse Network Simulator user guide

NGASREM Removes gas from a node in the network

ENS
This keyword can be used to remove gas from the network at a specified node in a production network. The
amount of gas to be removed can be expressed as either a constant rate or a fraction of the rate flowing
RUNSPEC
through that node. The removal of gas affects the pressure loss in the downstream network branches as their
x SCHEDULE
VFP tables are looked up with a smaller gas fraction.
The keyword is followed by any number of records, each containing the following items of data, and each
terminated with a slash (/).
The set of records must end with a blank record, containing only a slash (/).
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.
1. Node name
2. Maximum rate of gas removal from the node.
The specified rate of gas will be removed, subject to a maximum fraction of the node's gas flow
entered in item 3.

UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: Infinity
3. Maximum fraction of the node's gas flow to be removed .
The specified fraction of the node's gas flow is removed, subject to a maximum rate entered in item 2.
DEFAULT: 1.0

Examples
Example 1
Remove 20000 units/day of gas from the node. Item 3 defaults to 1.0 to ensure that the gas removal rate
does not exceed the flow rate of gas through the node.

NGASREM
NODE-5 20000 /
/

Example 2
Remove one tenth of the gas that flows through the node. Item 2 defaults to infinity so that there is no other
limit on the removal rate.

NGASREM
NODE-5 1* 0.1 /
/

Keywords
48
Intersect Eclipse Network Simulator user guide

NOILREM Removes oil from a node in the network

ENS
This keyword can be used to remove oil from the network at a specified node in a production network. The
amount of oil to be removed can be expressed as either a constant rate or a fraction of the rate flowing
RUNSPEC
through that node. The removal of oil affects the pressure loss in the downstream network branches as their
x SCHEDULE
VFP tables are looked up with changed water and gas fractions, and a changed flow rate for oil or liquid
rate-based tables.
The keyword is followed by any number of records, each containing the following items of data, and each
terminated with a slash (/).
The set of records must end with a blank record, containing only a slash (/).
1. Node name
2. Maximum rate of oil removal from the node.
The specified rate of oil will be removed, subject to a maximum fraction of the node's oil flow entered
in item 3.

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: Infinity
3. Maximum fraction of the node's oil flow to be removed .
The specified fraction of the node's oil flow is removed, subject to a maximum rate entered in item 2.
DEFAULT: 1.0

Example
Remove from node ND-2 either 10,000 units/day of oil or half the node’s oil inflow depending on which is
the lesser.

NOILREM
ND-2 10000 0.5 /
/

Keywords
49
Intersect Eclipse Network Simulator user guide

NWATREM Removes water from a node in the extended

network
ENS
This keyword can be used to remove water from the network at a specified node in a production network.
The amount of water to be removed can be expressed as either a constant rate or a fraction of the rate
RUNSPEC
flowing through that node. The removal of water affects the pressure loss in the downstream network
x SCHEDULE
branches as their VFP tables are looked up with a smaller water fraction
The keyword is followed by any number of records, each containing the following items of data, and each
terminated with a slash (/).
The set of records must end with a blank record, containing only a slash (/).
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.
1. Node name
2. Maximum rate of water removal from the node.
The specified rate of water is removed, subject to a maximum fraction of the node’s water flow
entered in item 3.

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

DEFAULT: Infinity
3. Maximum fraction of the node’s water flow to be removed
The specified fraction of the node’s water flow is removed, subject to a maximum rate entered in item
2.
DEFAULT: 1.0

Examples
Example 1
Remove 20,000 units/day of water from the node. Item 3 defaults to 1.0 to ensure that the water removal
rate does not exceed the flow rate of water through the node.

NWATREM
NODE-5 20000 /
/

Example 2
Remove half of the water that flows through the node. Item 2 defaults to infinity so that there is no other
limit on the removal rate.

NWATREM
NODE-5 1* 0.5 /

Keywords
50
Intersect Eclipse Network Simulator user guide

PVT-M PVT-metric units are to be used

ENS
This keyword indicates that PVT-metric units are to be used. These are essentially the same as METRIC
units, but with pressures measured in atmospheres. Note, the default unit convention is METRIC.
x RUNSPEC
SCHEDULE This keyword has no arguments.
This keyword has the same syntax as in Eclipse 300.

Example
PVT-M

Keywords
51
Intersect Eclipse Network Simulator user guide

RPTNET Reporting controls for the network

ENS
This keyword controls the output written to the ENS print file only. When running in standalone mode the
default verbosity level is set to the maximum however when ENS is performing coupled network solves the
x RUNSPEC
verbosity level is reduced in order to avoid generating huge print files. This default behavior can be
x SCHEDULE
modified by including the RPTNET keyword in the input model, in which case the verbosity level specified
will also apply to the coupled solution. Alternatively the verbosity of a coupled simulation can be
controlled from Intersect.
1. Reporting verbosity.
1 Only messages and titles are written to the print file.

2 The network solution is reported in addition to the items above.

3 The boundary conditions and constraint details are reported in addition to the items above.

4 The IPR tables are reported in addition to the items above.

DEFAULT: 4 for standalone mode, 2 for coupled network solves.

2. Number of decimal places in reported values.
DEFAULT: 1

Example
Limit the output to just the network solution, messages and titles but increase the precision of the reports to
4 decimal places

RPTNET
2 4 /

Keywords
52
Intersect Eclipse Network Simulator user guide

TITLE Specifies a Title for the Simulation

ENS
This keyword specifies a title for the simulation which is included in the print file headers. The syntax is
rather different from that of other keywords, the line after the TITLE keyword being read directly.
x RUNSPEC
x SCHEDULE No quotes or slash characters are required.
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.

Example
TITLE
Example Network Deck

Keywords
53
Intersect Eclipse Network Simulator user guide

VFPALIAS Aliases for VFP table numbers

ENS
This keyword specifies named aliases for the VFP tables. This keyword is only used in coupled simulation
in which Intersect Field Management can reference VFP tables using their aliases instead of the table
RUNSPEC
numbers.
x SCHEDULE
The keyword consists of any number of records, each containing the following items. Terminate each
record with a slash. The set of records should be terminated with a blank record containing just a slash.
1. Alias
Alias names can consist of up to 128 characters.
2. VFP table number

Example
Associate VFP table 1 with the alias "PUMP_ON" and VFP table 2 with the alias "PUMP_OFF".

VFPALIAS
PUMP_ON 1 /
PUMP_OFF 2 /
/

Keywords
54
Intersect Eclipse Network Simulator user guide

VFPIDIMS Injection network VFP table dimensions

ENS
This keyword specifies the dimensions of the vertical flow performance tables to be used within the
branches of a injection network.
x RUNSPEC
SCHEDULE The data must be terminated by a slash (/).
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.
1. The maximum number of flow values per table.
DEFAULT: 1
2. The maximum number of tubing head pressure values per table.
DEFAULT: 1
3. The maximum number of injection VFP tables.
DEFAULT: 1
The minimum dimensions required for a model are reported by ENS in the print file at the end of a
successful simulation.

Example
Allocate sufficient storage for 3 injection VFP tables, each with at most 10 flow values and 5 THP values
per table.

VFPIDIMS
10 5 3 /

Keywords
55
Intersect Eclipse Network Simulator user guide

VFPINJ Inputs a VFP table for injection wells

ENS
This keyword specifies a table of BHP versus FLO and versus THP. The VFPINJ keyword can only enter
one table at a time, so if there is more than one table, each table must be entered under a separate VFPINJ
RUNSPEC
keyword.
x SCHEDULE
The maximum dimensions of the tables must be set in the RUNSPEC section keyword VFPIDIMS.
The table consists of the following records of data, each record terminated with a slash (/).

Note: If the actual simulation conditions fall outside the range given in this table, linear extrapolation is
used. This can produce unrealistic results and should be avoided (by ensuring that the VFP table covers all
conditions that will arise during the simulation).

Record 1: Basic data for table

The last three items may be defaulted, for back-compatibility with earlier versions.
1. Table number
An integer between 1 and the maximum number of injection well VFP tables specified by the third
item of the VFPIDIMS keyword.
2. Bottom hole datum depth for table.
This item is ignored by ENS.
UNITS: m (METRIC), ft (FIELD), cm (LAB), m (PVT-M)
3. Definition of the flow rate variable FLO.
OIL oil injection rate

WAT water injection rate

GAS gas injection rate

4. Definition of the fixed pressure values given in "Record 3:THP values".

THP Tubing head pressure
This is interpreted as the branch inlet pressure in ENS.

DEFAULT: THP
5. Unit convention of the VFP table.
METRIC, FIELD, LAB If this item is present, ENS checks that the VFP table has the same unit
or PVT-M convention as the run and issues an error message if they are not the same.

DEFAULT: The same unit convention as the ENS run.

6. Definition of the tabulated quantity in the body of the table, records 4 onwards.
BHP Bottom hole pressure

Keywords
56
Intersect Eclipse Network Simulator user guide

This is interpreted as the branch outlet pressure in ENS.

DEFAULT: BHP

Record 2:FLO (flow rate) values

Enter in ascending order, terminated with a slash (/).
The number of values, NFLO, must be between 2 and the value specified in the first item of the VFPIDIMS
keyword.

Volume rate: UNITS: sm3/day (METRIC), stb/day for oil or liquid (FIELD), Mscf/day for gas (FIELD),
scc/hr (LAB), sm3/day (PVT-M)

Record 3:THP values

Enter in ascending order, terminated with a slash (/).
The number of values, NTHP, must be between 1 and the value specified by the second item of the
VFPIDIMS keyword. If only one value is entered, the derivative of the BHP with respect to the THP is
treated as unity.
UNITS: barsa (METRIC), psia (FIELD), atma (LAB), atma (PVT-M)

Records 4 to NTHP+3
NTHP successive records each containing the following items, and each terminated with a slash (/).

1. NT (THP value number).

2. BHP at 1st FLO value and NTth THP value.

3. BHP at 2nd FLO value and NTth THP value.

.... ...

NFLO +1 BHP at last FLO value and NTth THP value.

All combinations of NF = 1 to NFLO and NT = 1 to NTHP must be covered.

UNITS: barsa (METRIC), psia (FIELD), atma (LAB), atma (PVT-M)

Examples
Example 1
VFP table for water injector, NFLO =5, NTHP =1:

VFPINJ
1 7.00000E+03 WAT THP FIELD BHP /
1.00000E+00 3.00000E+02 7.00000E+02 1.00000E+03
2.00000E+03 /

Keywords
57
Intersect Eclipse Network Simulator user guide

1.00000E+03 /
1 4.03999E+03 4.03423E+03 4.01346E+03 3.98903E+03
3.85537E+03
/

Example 2
VFP table for gas injector, NFLO =5, NTHP =3:

VFPINJ
2 7.00000E+03 GAS THP FIELD BHP /
1.00000E+00 3.00000E+02 7.00000E+02 1.00000E+03
2.00000E+03
/
1.00000E+03 2.00000E+03 3.00000E+03
/
1 1.32484E+03 1.32300E+03 1.31556E+03 1.30626E+03
1.25098E+03
/
2 2.74881E+03 2.74801E+03 2.74490E+03 2.74110E+03
2.71934E+03
/
3 3.94062E+03 3.94000E+03 3.93761E+03 3.93471E+03
3.91830E+03
/

Keywords
58
Intersect Eclipse Network Simulator user guide

VFPOPTNS VFP table usage options

ENS
This keyword controls how VFP tables are interrogated for pressure drops across the branches of a
network. It is followed by a single record terminated by a slash (/). The record consists of one item of data:
RUNSPEC
x SCHEDULE 1. Control on how production VFP tables are extrapolated for THP, water fraction, and gas fraction
values that fall outside the range of values in the table.
VFP tables for production networks are constructed with a range of values for flow, THP, water
fraction, gas fraction, and ALQ. If the table is queried with a value that falls outside its table range,
then in the case of flow and ALQ the table is linearly extrapolated in this value. For water fraction and
gas fraction values, linear extrapolation can result in non-monotonic or non-U shaped VFP curves,
which may cause convergence problems. This item enables you to restrict the extrapolation in these
quantities together with THP.
This item has no effect on VFP table usage in injection networks.

LINEAR Linear extrapolation is used for water fraction, gas fraction, and THP values that fall
outside the bounding values in the VFP table.

CONST Constant value extrapolation is used for water fraction, gas fraction, and THP values in
VFP table look-ups. So, for example, if a VFP table is queried with a gas fraction that is
greater than the maximum value in the table, the look-up will be made at the table's
maximum gas fraction.

DEFAULT: LINEAR
2. Procedure for calculating pressure drops when flows cross zero in non-dendritic networks.
REVERSE Reverse the flows and the pressure drop from the table.
This procedure should only be used for horizontal pipes or with friction-only VFP tables
in which the table’s pressure drop has no hydrostatic component. In these cases, the
pressure drop can simply be reversed when the flow reverses.

SPLIT Splits the pressure drop into a hydrostatic component that is deemed unaffected by flow
reversal and a friction component that reserves if the flows do.
This option should be used for non-horizontal pipes. It can also be used for horizontal
pipes as behaves in the same way as the REVERSE procedure.
The split between these two components is approximated by extrapolating the VFP table
to zero flow and treating this pressure drop as hydrostatic; during flow reversal this is
unchanged while the remaining part of the pressure drop at non-zero reverse flows is
deemed to be frictional and is reversed.

DEFAULT: SPLIT
3. Control of how the pressure adjustment defined in item 5 of BRANPROP is applied to the branch
pressure drop.
BEFORE_LOOKUP The pressure adjustment reduces the input pressure used by the VFP table
lookup for the branch pressure drop.
This option can be considered as a head correction allowing branches that are
similar in every way except depth to use the same VFP table.

Keywords
59
Intersect Eclipse Network Simulator user guide

BEFORE_SCALING The pressure adjustment reduces the branch pressure drop before the scaling
factor defined in item 6 of BRANPROP has been applied to this pressure drop.

AFTER_SCALING The pressure adjustment reduces the branch pressure drop after the scaling
factor defined in item 6 of BRANPROP has been applied to this pressure drop.

DEFAULT: AFTER_SCALING
End data record with a slash (/).

Example
VFPOPTNS
'CONST' 'SPLIT' 'BEFORE_SCALING'
/

Keywords
60
Intersect Eclipse Network Simulator user guide

VFPPDIMS Production network VFP table dimensions

ENS
This keyword specifies the dimensions of the vertical flow performance tables to be used within the
branches of a production network.
x RUNSPEC
SCHEDULE The data must be terminated by a slash (/).
This keyword has the same syntax as in Eclipse 100 and Eclipse 300.
1. The maximum number of flow values per table.
DEFAULT: 1
2. The maximum number of tubing head pressure values per table.
DEFAULT: 1
3. The maximum number of water fraction values per table.
DEFAULT: 1
4. The maximum number of gas fraction values per table.
DEFAULT: 1
5. The maximum number of Artificial Lift Quantities per table.
DEFAULT: 1
6. The maximum number of production VFP tables.
DEFAULT: 1
The minimum dimensions required for a model are reported by ENS in the print file at the end of a
successful simulation.

Example
Allocate sufficient storage for 3 production VFP tables, each with at most 6 flow values and 3 THP values,
3 water fraction values, 4 gas fraction values and 1 ALQ value per table.

VFPPDIMS
6 3 3 4 1 3 /

Keywords
61
Intersect Eclipse Network Simulator user guide

VFPPROD Inputs a VFP table for production wells

ENS
This keyword specifies a table of BHP versus FLO, THP, WFR, GFR and ALQ, where:
RUNSPEC FLO is the oil, liquid or gas production rate.
x SCHEDULE
WFR is the water-oil ratio, water cut or water-gas ratio.

GFR is the gas-oil ratio, gas-liquid ratio or oil-gas ratio.

ALQ is a 5th variable that can be used to incorporate an additional look-up parameter, such as the level of
artificial lift.

Any combination of these variable definitions can be used, as long as they do not become infinite during
the simulation.
At least one table is needed if any of the production wells require THP calculations. The VFPPROD
keyword can only enter one table at a time, so if there is more than one table, each table must be entered
under a separate VFPPROD keyword.

The maximum dimensions of the tables must be set in the RUNSPEC section keyword VFPPDIMS.
The table consists of seven records of data, each record terminated with a slash (/).

Record 1: Basic data for table

The last four items may be defaulted, for back-compatibility with earlier versions.
1. Table number
An integer between 1 and the maximum number of production VFP tables specified by item 6 of the
VFPPDIMS keyword.
Each production VFP table must have a unique table number irrespective of whether the body of the
table holds pressures or temperatures.
2. Bottom hole datum depth for table.
This item is not used by ENS.
3. Definition of the flow rate variable FLO in record 2.
OIL Oil production rate

LIQ Liquid (oil + water) production rate

GAS Gas production rate

4. Definition of the water fraction variable WFR in record 4.

WOR Water-oil ratio

Keywords
62
Intersect Eclipse Network Simulator user guide

WCT Water cut (water-liquid ratio)

WGR Water-gas ratio

5. Definition of the gas fraction variable GFR in record 5.

GOR Gas-oil ratio

GLR Gas-liquid ratio

OGR Oil-gas ratio

6. Definition of the fixed pressure values given in record 3.

THP Tubing head pressure
This is interpreted as the outlet pressure if the table is used to determine production network
branch pressure drops in the network option, or segment pressure drops in the multisegment
well model.
ENS will not accept anything other than THP.

DEFAULT: THP
7. Definition of the artificial lift quantity (ALQ) in record 6
GRAT Lift gas injection rate (for gas lift)

IGLR Injection gas-liquid ratio (for gas lift)

TGLR Total gas-liquid ratio (for gas lift)

PUMP Pump rating (for pump)

COMP Compressor power (for compressor)

DENO Surface density of oil.

DENG Surface density of gas.

BEAN Choke diameter (multisegment wells)

' ' Undefined.

This item informs ENS of the ALQ definition that was used to generate the VFP table (for example by
VFP i). However, in general ENS uses the ALQ only as a look-up parameter to interpolate the table,
and attaches no physical significance to its definition.
8. Unit convention of the VFP table.
METRIC, FIELD, LAB or PVT-M
If this item is present, ENS checks that the VFP table has the same unit convention as the run and
issues an error message if they are not the same.
DEFAULT: The same unit convention as the ENS run.

Keywords
63
Intersect Eclipse Network Simulator user guide

9. Definition of the tabulated quantity in the body of the table, record 7 onwards.
BHP Bottom hole pressure
In ENS the BHP is interpreted as the inlet pressure for the network branch.

Record 2: FLO (flow rate) values

Enter in ascending order, terminated with a slash (/).
The number of values, NFLO, must be between 2 and the value specified by item 1 of the VFPPDIMS
keyword.

Volume rate: UNITS: sm3/day (METRIC), stb/day for oil or liquid (FIELD), Mscf/day for gas (FIELD),
scc/hr (LAB), sm3/day (PVT-M)

Record 3: THP values

Enter in ascending order, terminated with a slash (/).
The number of values, NTHP, must be between 1 and the value specified by item 2 of the VFPPDIMS
keyword. If only one value is entered, the derivative of the BHP with respect to the THP is treated as unity.
UNITS: barsa (METRIC), psia (FIELD), atma (LAB), atma (PVT-M)

Record 4: WFR values

Enter in ascending order, terminated with a slash (/).
The number of values, NWFR, must be between 1 and the value specified by item 3 of the VFPPDIMS
keyword. If only one value is entered, the BHP is treated as independent of the water fraction.

For WOR or WCT: UNITS: sm3/sm3 (METRIC), stb/stb (FIELD), scc/scc (LAB), sm3/sm3 (PVT-M)

For WGR: UNITS: sm3/sm3 (METRIC), stb/Mscf (FIELD), scc/scc (LAB), sm3/sm3 (PVT-M)

Record 5: GFR values

Enter in ascending order, terminated with a slash (/).
The number of values, NGFR, must be between 1 and the value specified by item 4 of the VFPPDIMS
keyword. If only one value is entered, the BHP is treated as independent of the gas fraction.

For GOR or GLR: UNITS: sm3/sm3 (METRIC), Mscf/stb (FIELD), scc/scc (LAB), sm3/sm3 (PVT-M)

For OGR: UNITS: sm3/sm3 (METRIC), stb/Mscf (FIELD), scc/scc (LAB), sm3/sm3 (PVT-M)

Record 6: ALQ values

Enter in ascending order, terminated with a slash (/).

Keywords
64
Intersect Eclipse Network Simulator user guide

The number of values, NALQ, must be between 1 and the value specified by item 5 of the VFPPDIMS
keyword. If only one value is entered, the BHP is treated as independent of the artificial lift quantity.

When ALQ = GRAT: UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day
(PVT-M)

When ALQ = IGLR or TGLR: UNITS: sm3/sm3 (METRIC), Mscf/stb (FIELD), scc/scc (LAB), sm3/sm3
(PVT-M)

Eclipse 100 only When ALQ = DENO or DENG: UNITS: kg/m3 (METRIC), lb/ft3 (FIELD), gm/cc (LAB), kg/m3 (PVT-M)

When ALQ = BEAN: UNITS: mm (METRIC), 1/64ths in (FIELD)

The units for PUMP or COMP depend on the definition of the pump rating or compressor power used in the
construction of the VFP table.
(See item 7 of Record 1.)

Records 7 to NTHP*NWFR*NGFR*NALQ+6
NTHP*NWFR*NGFR*NALQ successive records each containing the following items, and each terminated
with a slash (/).
1. NT (THP value number).
2. NW (WFR value number)
3. NG (GFR value number)
4. NA (ALQ value number)
5. BHP or THT at

1st FLO value

NTth THP value

NWth WFR value

NGth GFR value

NAth ALQ value

6. BHP or THT at

2nd FLO value

NTth THP value

NWth WFR value

NGth GFR value

NAth ALQ value

.......................................

NFLO+4 BHP or THT at last FLO value

Keywords
65
Intersect Eclipse Network Simulator user guide

NTth THP value

NWth WFR value

NGth GFR value

NAth ALQ value

All combinations of
NF = 1 to NFLO
NT = 1 to NTHP
NW = 1 to NWFR
NG = 1 to NGFR
NA = 1 to NALQ must be covered.
For BHP:
UNITS: barsa (METRIC), psia (FIELD), atma (LAB), atma (PVT-M)

Example
VFP table for producer, NFLO=5, NTHP=2, NWFR=1, NGFR=3, NALQ=1:

VFPPROD
1 7.00000E+03 LIQ WCT GOR THP ' ' FIELD BHP / Basic data
1.00000E+01 3.00000E+02 7.00000E+02 1.00000E+03
2.00000E+03 / 5 flow vals
2.00000E+02 1.00000E+03 / 2 THP values
0.0 / 1 WFR value
1.00000E+00 2.00000E+00 4.00000E+00 / 3 GFR values
0.0 / 1 ALQ value
1 1 1 1 1.93199E+03 1.36585E+03 6.77031E+02 7.15261E+02
8.62436E+02 /
2 1 1 1 2.73663E+03 2.73303E+03 2.75085E+03 2.77323E+03
2.90209E+03 /
1 1 2 1 1.77471E+03 4.33035E+02 5.38422E+02 6.30479E+02
9.39472E+02 /
2 1 2 1 2.51228E+03 2.38072E+03 2.35995E+03 2.26536E+03
2.28849E+03 /
1 1 3 1 1.64735E+03 4.41989E+02 6.95286E+02 8.81634E+02
1.41797E+03 /
2 1 3 1 2.46600E+03 1.78161E+03 1.80525E+03 1.85156E+03
2.04484E+03 /

Keywords
66

Common questions

In both standalone and coupled modes, ENS generates print files. For standalone mode, the output files document network topology and the solutions achieved in simulations without time consideration. In coupled mode, ENS generates print files and Field Management can compile network solutions into summary files viewed in Petrel, with additional properties output though many, like fluid components, are not relevant for ENS and result in zero values outputted .

The Eclipse Network Simulator (ENS) operates in two primary modes: standalone mode and coupled mode. In standalone mode, ENS allows modeling and testing of network scenarios with various boundary conditions and constraints without time-dependent interactions; it operates in a steady-state environment where each solve is independent. In contrast, the coupled mode integrates ENS with the Intersect reservoir simulator, enabling dynamic simulation scenarios where Field Management handles adjustments in response to changing conditions during the simulation timeline. This coupling allows for more complex modeling scenarios but requires correct alignment between ENS and the Intersect inputs .

IPR tables in ENS define the relationship between pressure and phase flow rates for coupled wells, setting the boundary conditions in simulations. The IPR tables are utilized in coupled mode to account for variable well constraints and guide the pressure and flow dynamics at network boundaries. This setup allows the network simulator to adjust flow characteristics within the constraints provided by the IPR tables .

Field Management plays a crucial role in coordinating simulations when ENS is coupled with Intersect. It constructs IPR tables based on well constraints and manages the simulation timeline, ensuring that any required modifications within the network are issued appropriately. It also compiles network solutions, thereby enabling a comprehensive analysis and generating summary files compatible with tools like Petrel .

ENS does not undertake fluid modeling, meaning it does not account for compositional effects in its simulations. The network models use vertical flow performance (VFP) tables based on surface phase flow rates or ratios, but cannot capture changes in fluid properties that might occur during passage due to compositional variations .

The IPRDIMS keyword is crucial in ensuring that the ENS model can accommodate the maximum size of IPR tables generated by Field Management. It specifies the allowed dimensions for these tables in the simulation, essential to prevent data truncation and to maintain compatibility between coupled components, ensuring that network simulations are accurately aligned with the well performance profiles defined by Field Management .

The logging functionality in a coupled simulation of ENS with Intersect allows for detailed examination of network behavior by recording all communications between Field Management and ENS. This option is activated by including the NETLOG keyword in the ENS input file. Doing so generates an equivalent input file that can be analyzed in standalone mode, aiding in debugging or further analysis of network components during the simulation .

In ENS, the pressures over chokes and pumps are calculated to ensure that specified network constraints are honored. Users do not directly control these components; rather, the ENS algorithm determines the appropriate pressure drops to maintain the desired operational constraints at various nodes in the network, such as pressure or flow rate limits .

In an ENS injection network model, positive flow values are defined as moving from the terminal source towards well boundaries, indicating the convention for flow direction. This setup ensures that flow directions are consistently interpreted in simulations, providing clarity in the modeling of fluid dynamics within the network .

Not removing Tubing Head Pressure (THP) limits when emulating the Eclipse network option with Intersect and ENS can cause discrepancies: in the Eclipse implementation, these limits are superseded by the network solution. However, in Intersect, they are applied in addition to the network solution, which may result in wells shutting in Intersect when they would remain open in Eclipse, hence potentially invalidating simulation results .

Rele Notes 2010.1
No ratings yet
Rele Notes 2010.1
66 pages
Eclipse Development History
No ratings yet
Eclipse Development History
111 pages
Release Notes
No ratings yet
Release Notes
31 pages
Simulación de Modelos ECLIPSE 300
No ratings yet
Simulación de Modelos ECLIPSE 300
28 pages
RUNSPEC Setup for ECLIPSE Simulation
No ratings yet
RUNSPEC Setup for ECLIPSE Simulation
13 pages
ECLIPSE Reservoir Simulation Training
No ratings yet
ECLIPSE Reservoir Simulation Training
7 pages
Summary Section
No ratings yet
Summary Section
71 pages
PVTsim Tutorial: Fluid Preparation Guide
No ratings yet
PVTsim Tutorial: Fluid Preparation Guide
9 pages
Merak Peep Ps PDF
No ratings yet
Merak Peep Ps PDF
2 pages
Oil Reservoir Modeling with MBAL Techniques
No ratings yet
Oil Reservoir Modeling with MBAL Techniques
33 pages
INTERRA ECLIPSE 100 and 300 TECHNICAL COURSE MATERIALS - 10 PDF
No ratings yet
INTERRA ECLIPSE 100 and 300 TECHNICAL COURSE MATERIALS - 10 PDF
21 pages
Parallel Reservoir Simulation: User Course
No ratings yet
Parallel Reservoir Simulation: User Course
54 pages
Whitson PVT Formulas and Definitions
No ratings yet
Whitson PVT Formulas and Definitions
21 pages
Eclipse Manual 2012.1
No ratings yet
Eclipse Manual 2012.1
1 page
Eclipse and Front Sim Datasets
No ratings yet
Eclipse and Front Sim Datasets
19 pages
c2 Modeling Fracture Geometry PDF
No ratings yet
c2 Modeling Fracture Geometry PDF
31 pages
CMG IMEX Overview and Applications
100% (1)
CMG IMEX Overview and Applications
55 pages
Nodal Analysis for Oil Production
No ratings yet
Nodal Analysis for Oil Production
19 pages
Interra Eclipse 100 and 300 Technical Course Materials - 10
No ratings yet
Interra Eclipse 100 and 300 Technical Course Materials - 10
24 pages
File 000004
No ratings yet
File 000004
291 pages
KAPPA Rubis Tutorial
100% (1)
KAPPA Rubis Tutorial
22 pages
Speeding Up ECLIPSE Simulations
No ratings yet
Speeding Up ECLIPSE Simulations
54 pages
RTA (Rate Transient Analysis) Fact Sheet
No ratings yet
RTA (Rate Transient Analysis) Fact Sheet
2 pages
GRID Section Overview for ECLIPSE
No ratings yet
GRID Section Overview for ECLIPSE
37 pages
Reservoir Modeling Project 1 Guidelines
100% (1)
Reservoir Modeling Project 1 Guidelines
7 pages
Reservoir Fluid Properties Explained
No ratings yet
Reservoir Fluid Properties Explained
97 pages
Schedule Section for Eclipse Simulation
No ratings yet
Schedule Section for Eclipse Simulation
70 pages
Petroleum Experts RESOLVE User Guide
No ratings yet
Petroleum Experts RESOLVE User Guide
49 pages
INTERSECT 2017.1 Release Highlights
No ratings yet
INTERSECT 2017.1 Release Highlights
21 pages
Eclipse Reference Manual
No ratings yet
Eclipse Reference Manual
3 pages
Reservoir Pressure Calculation Guide
100% (1)
Reservoir Pressure Calculation Guide
4 pages
PVT Correlations for Crude Oil Properties
No ratings yet
PVT Correlations for Crude Oil Properties
30 pages
User's Guide: Merak Fiscal Model Library For World Peep
No ratings yet
User's Guide: Merak Fiscal Model Library For World Peep
61 pages
Using Geology for Porosity Analysis
No ratings yet
Using Geology for Porosity Analysis
28 pages
OFM 2014.1 Course Overview and Schedule
No ratings yet
OFM 2014.1 Course Overview and Schedule
7 pages
PVT Correlations and Applicability
No ratings yet
PVT Correlations and Applicability
20 pages
ECLIPSE 3D Two-Phase Reservoir Tutorial
No ratings yet
ECLIPSE 3D Two-Phase Reservoir Tutorial
5 pages
Horizontal Well Drainage Area Calculation
100% (2)
Horizontal Well Drainage Area Calculation
19 pages
Compositional Simulation in Reservoir Engineering
No ratings yet
Compositional Simulation in Reservoir Engineering
7 pages
Drilling Cost Breakdown and Estimation
100% (1)
Drilling Cost Breakdown and Estimation
2 pages
Petrophysical Analysis of Niger Delta
No ratings yet
Petrophysical Analysis of Niger Delta
128 pages
FrontSim for Waterflood Management
100% (1)
FrontSim for Waterflood Management
26 pages
History Match
100% (1)
History Match
78 pages
ECLIPSE Reservoir Simulation Overview
100% (1)
ECLIPSE Reservoir Simulation Overview
16 pages
X10 Reservoir Performance Evaluation
No ratings yet
X10 Reservoir Performance Evaluation
42 pages
MBAL User Guide for Reservoir Engineering
No ratings yet
MBAL User Guide for Reservoir Engineering
46 pages
Prosper Choke Sense
No ratings yet
Prosper Choke Sense
16 pages
Fit Chan Plot
100% (1)
Fit Chan Plot
6 pages
Future Performance Prediction Strategies
No ratings yet
Future Performance Prediction Strategies
29 pages
TempestMOREHelp PDF
No ratings yet
TempestMOREHelp PDF
1,807 pages
Uncertainty Analysis in Reservoir Modeling
No ratings yet
Uncertainty Analysis in Reservoir Modeling
16 pages
Interdisciplinary Reservoir Management Guide
No ratings yet
Interdisciplinary Reservoir Management Guide
34 pages
Reservoir Modeling with Petrel Software
No ratings yet
Reservoir Modeling with Petrel Software
2 pages
Paper Black Oil
No ratings yet
Paper Black Oil
20 pages
Eclipse 3D Reservoir Simulation Guide
75% (4)
Eclipse 3D Reservoir Simulation Guide
7 pages
Water Production Problems in Gas Reservoirs PDF
No ratings yet
Water Production Problems in Gas Reservoirs PDF
24 pages
Migrator User Guide
No ratings yet
Migrator User Guide
103 pages
Installation and Deployment Guide
No ratings yet
Installation and Deployment Guide
19 pages
INTERSECT 2021.2 Installation Guide
No ratings yet
INTERSECT 2021.2 Installation Guide
19 pages
ECLIPSE Reservoir Simulation Exercises
No ratings yet
ECLIPSE Reservoir Simulation Exercises
4 pages
Norne Full Field Model Update 2012
No ratings yet
Norne Full Field Model Update 2012
53 pages
Petrel Geology & Modeling
No ratings yet
Petrel Geology & Modeling
2 pages
Material Balance in Reservoir Engineering
No ratings yet
Material Balance in Reservoir Engineering
205 pages
March 25 - Negative Pressures and Cavitation
No ratings yet
March 25 - Negative Pressures and Cavitation
33 pages
1800C-HC Service Regulators Overview
No ratings yet
1800C-HC Service Regulators Overview
4 pages
Aerodynamics of A Formula One Car Front Cascade Wing During Cornering
No ratings yet
Aerodynamics of A Formula One Car Front Cascade Wing During Cornering
8 pages
Design Factors for Thermoplastic Pipe
No ratings yet
Design Factors for Thermoplastic Pipe
12 pages
Fluid Mechanics Exam Paper 2021-22
No ratings yet
Fluid Mechanics Exam Paper 2021-22
3 pages
Fluid Mechanics Problem Set Overview
No ratings yet
Fluid Mechanics Problem Set Overview
3 pages
Fluid Pressure Practice Questions
No ratings yet
Fluid Pressure Practice Questions
4 pages
Ethiopian Maritime Entrance Test Q-22
No ratings yet
Ethiopian Maritime Entrance Test Q-22
5 pages
Indian Boiler Act 1923 Overview
No ratings yet
Indian Boiler Act 1923 Overview
2 pages
Process Isolation Techniques in Oil & Gas
No ratings yet
Process Isolation Techniques in Oil & Gas
18 pages
DPT Mod
No ratings yet
DPT Mod
2 pages
Dietz Shape Factor in Gas Well IPR
100% (1)
Dietz Shape Factor in Gas Well IPR
28 pages
Hydraulic Data For Pump Application
100% (2)
Hydraulic Data For Pump Application
28 pages
Pharma Differential Pressure Quote
No ratings yet
Pharma Differential Pressure Quote
1 page
Optimizing Downhole Pressure Sensor Placement
No ratings yet
Optimizing Downhole Pressure Sensor Placement
9 pages
Automatic Copper Wire Cutting Machine
100% (2)
Automatic Copper Wire Cutting Machine
79 pages
Electron Speed Near Charge Calculation
100% (2)
Electron Speed Near Charge Calculation
199 pages
Flow Recorder Calibration Procedures
No ratings yet
Flow Recorder Calibration Procedures
10 pages
Applied Thermodynamics Overview
No ratings yet
Applied Thermodynamics Overview
20 pages
Torque in Hand Flour Grinder Mechanics
No ratings yet
Torque in Hand Flour Grinder Mechanics
12 pages
Laporan Siasatan Kemalangan Kilang
No ratings yet
Laporan Siasatan Kemalangan Kilang
22 pages
Impact of Blast Loading on Structures
No ratings yet
Impact of Blast Loading on Structures
19 pages
Gas Laws: Boyle's, Charles', Pressure Law
No ratings yet
Gas Laws: Boyle's, Charles', Pressure Law
6 pages
XMO2-IDM User Manual Overview
No ratings yet
XMO2-IDM User Manual Overview
88 pages
Moon and Earth Motion Physics Exam
No ratings yet
Moon and Earth Motion Physics Exam
18 pages
Weight Calculations on Mars and Moon
No ratings yet
Weight Calculations on Mars and Moon
4 pages
Molar Volume of Oxygen from Reactions
No ratings yet
Molar Volume of Oxygen from Reactions
2 pages
Fluid Statics Assignment Solutions
No ratings yet
Fluid Statics Assignment Solutions
4 pages
Properties of Gases and Energy Concepts
No ratings yet
Properties of Gases and Energy Concepts
102 pages
Heat Capacity Correlations in Thermodynamics
No ratings yet
Heat Capacity Correlations in Thermodynamics
2 pages

Intersect Eclipse Simulator User Guide

Uploaded by

Intersect Eclipse Simulator User Guide

Uploaded by

Intersect

High-resolution reservoir simulator

Eclipse Network Simulator user guide

Trademarks & Service Marks

Eclipse® is a mark of SLB.

Product Name License String Functionality

Installation and licensing

ENS network models

ENS network models

Network solution method

Network solution method

SIMULATION ENS "ENS_NETWORK" {

Coupling with the Intersect reservoir simulator

Intersect supported functionality

Coupling with the Intersect reservoir simulator

Node Field Details

Coupling with the Intersect reservoir simulator

Node Field Details

Coupling with the Intersect reservoir simulator

Node Field Details

Coupling with the Intersect reservoir simulator

More information on the use of networks in Intersect can be found in:

Production Network Hierarchical Structure

Coupling with the Intersect reservoir simulator

Node Details and Gas/Water Removal Settings

REPORT Flow entity count for Network:ENS_NETWORK:

REPORT Properties of FM network ENS_NETWORK:

Coupling with the Intersect reservoir simulator

REPORT Connection info of FM network ENS_NETWORK devices:

Coupling with the Intersect reservoir simulator

BRANPROP Defines the network branches

END Logical end of the input file

ENDINC Logical end of include file

ENSVER ENS minimum version

FIELD Field units are to be used

FILEUNIT Confirms units of a data set

There is no default value.

INCLUDE Include the contents of another named file

IPRDIMS IPR table dimensions

IPROPTNS IPR table usage options

LAB Lab units are to be used

METRIC Metric units are to be used

NETBALAN Network balancing parameters

NETCONG Gas injection network constraints

UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

YES Pressure assistance active.

NETCONP Production network constraints

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

YES Pressure assistance active.

NETCONW Water injection network constraints

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

YES Pressure assistance active.

NETIPRG Gas injection IPR table

NETIPRP Production IPR table

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

NETIPRW Water injection IPR table

NETLOG Logs all keywords and communications in a

-- start of input deck

NETSINKG Sink boundary conditions for gas injection

UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

UNITS: sm3/day/bars (METRIC), Mscf/day/psi (FIELD), scc/hr/atm (LAB), sm3/day/atm (PVT-M)

NO The pressure at the boundary node is not constrained.

NETSINKW Sink boundary conditions for water injection

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

UNITS: sm3/day/bars (METRIC), stb/day/psi (FIELD), scc/hr/atm (LAB), sm3/day/atm (PVT-M)

NO The pressure at the boundary node is not constrained.

NETSOLVE Solves the network model

NETSRCP Source boundary conditions for production

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

UNITS: sm3/day (METRIC), Mscf/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)

UNITS: sm3/day (METRIC), stb/day (FIELD), scc/hr (LAB), sm3/day (PVT-M)