Intersect

High-resolution reservoir simulator

Migrator user guide

Version 2024.3
Intersect Migrator user guide

Proprietary notice

Copyright © 2024 SLB. All rights reserved.

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.

Intersect ® is a mark of SLB. Intersect software is a joint product collaboration of Chevron, TotalEnergies
and 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 Migrator user guide

Table of Contents
1 Migrator overview ....................................................................................................... 1
Supported simulators ......................................................................................................................... 1
Run an Eclipse dataset in Intersect ................................................................................................... 2
Run the Migrator on an Eclipse dataset ............................................................................................ 2
Run Intersect ..................................................................................................................................... 2
Migration reports ................................................................................................................................. 2
PRT file .............................................................................................................................................. 2
Optionally write Eclipse property names ........................................................................................... 3
Filtered output dataset ....................................................................................................................... 3
Other output ....................................................................................................................................... 4
Export a list of supported keywords ................................................................................................. 4
Key workflows ..................................................................................................................................... 4
Keywords only ................................................................................................................................... 4
Default: Migrate grid edits .................................................................................................................. 4
Option: Process grid edits ................................................................................................................. 5
Restarting an Intersect simulation ..................................................................................................... 5
Automatic output of data using the RPTRST keyword ...................................................................... 5
Output of Restart data on demand using the SAVE keyword ............................................................ 5
Reloading a restart ............................................................................................................................ 6
Run parallel simulations ..................................................................................................................... 6
Thermal ................................................................................................................................................ 6
Intersect or Field Management specific functionality ..................................................................... 6
Always start a keyword in the first column ...................................................................................... 6
Validate user-defined IXF with the Migrator ..................................................................................... 7
Supported platforms ........................................................................................................................... 7

2 RUNSPEC .................................................................................................................... 8
RUNSPEC Fully supported keywords ............................................................................................... 8
RUNSPEC Partially supported keywords ......................................................................................... 9
RUNSPEC keywords requiring special description ......................................................................... 9
BRINE, ECLMC ................................................................................................................................. 9
COAL ................................................................................................................................................. 9
ENDSCALE ....................................................................................................................................... 9
GASSOL ............................................................................................................................................ 9
NUPCOL .......................................................................................................................................... 10
NOMIX ............................................................................................................................................. 10
POLYMER ....................................................................................................................................... 10

i
Intersect Migrator user guide

3 GRID ........................................................................................................................... 11
GRID Fully supported keywords ...................................................................................................... 11
GRID Partially supported keywords ................................................................................................ 12
GRID keywords requiring special description ............................................................................... 12
AQUCT, AQUFET, AQUFETP ........................................................................................................ 12
AQUANCON .................................................................................................................................... 12
COARSEN ....................................................................................................................................... 12
GDFILE ............................................................................................................................................ 12
INIT .................................................................................................................................................. 12
IONROCK ........................................................................................................................................ 13
JFUNC ............................................................................................................................................. 13
MULTFLT ........................................................................................................................................ 13
MULTREGT ..................................................................................................................................... 13
NNCGEN ......................................................................................................................................... 13
PINCH ............................................................................................................................................. 13
PINCHNUM ..................................................................................................................................... 13
PINCHREG ...................................................................................................................................... 13
RESVNUM ....................................................................................................................................... 13
ROCKCON ...................................................................................................................................... 14
ROCKCONL .................................................................................................................................... 14
GRID handling ................................................................................................................................... 14
Grid geometry .................................................................................................................................. 14
Cell properties ................................................................................................................................. 14
Dual porosity .................................................................................................................................... 15
Transmissibilities ............................................................................................................................. 15
Thermal ........................................................................................................................................... 16
Grid export ....................................................................................................................................... 16
Non-neighbor connections export .................................................................................................... 16

4 EDIT ............................................................................................................................ 17
EDIT Fully supported keywords ...................................................................................................... 17
EDIT keywords requiring special description ................................................................................ 17
EDITNNC ......................................................................................................................................... 17
EDITNNCR ...................................................................................................................................... 17
MULTFLT ........................................................................................................................................ 18
MULTREGT ..................................................................................................................................... 18
Pore volume .................................................................................................................................... 18

5 PROPS ....................................................................................................................... 19
PROPS Fully supported keywords .................................................................................................. 19
PROPS Partially supported keywords ............................................................................................ 20
PROPS keywords requiring special description ............................................................................ 20
Equation of state keywords ............................................................................................................. 21
AMFVD ............................................................................................................................................ 21

ii
Intersect Migrator user guide

CVTYPE, CVTYPES ....................................................................................................................... 21

DENAQA, VISCAQA ....................................................................................................................... 21
IONXROCK ..................................................................................................................................... 21
KVCR, KVCRS ................................................................................................................................ 21
LANGMUIR, LANGMEXT ................................................................................................................ 22
PVTW, WATERTAB ........................................................................................................................ 22
PVTWSALT, BDENSITY ................................................................................................................. 22
ROCKOPTS .................................................................................................................................... 22
RSWVD ........................................................................................................................................... 22
RTEMP, TEMPVD ........................................................................................................................... 22
SOLUAQA ....................................................................................................................................... 23
SOLUBILI ........................................................................................................................................ 23
TCRIT. TCRITS ............................................................................................................................... 23
TRACER .......................................................................................................................................... 23
VCRITVIS ........................................................................................................................................ 23
ZCRITVIS ........................................................................................................................................ 23
ZFACT1 ........................................................................................................................................... 23
Behavior of temperature keywords ................................................................................................. 24
Enumeration .................................................................................................................................... 24
Equilibration ..................................................................................................................................... 24
Thermal ........................................................................................................................................... 24
Multiple-component brine ................................................................................................................ 24
Concentrations ................................................................................................................................ 24
Example ....................................................................................................................................... 25

Saturation functions ......................................................................................................................... 25

6 REGIONS ................................................................................................................... 26
REGIONS Fully supported keywords .............................................................................................. 26
REGIONS keywords requiring special description ........................................................................ 26
EOSNUM, PVTNUM ........................................................................................................................ 26
EQLNUM ......................................................................................................................................... 27
SATNUM, IMBNUM, PVTNUM, ROCKNUM ................................................................................... 27
TNUM .............................................................................................................................................. 27

7 SOLUTION ................................................................................................................. 28
SOLUTION Fully supported keywords ............................................................................................ 28
SOLUTION Partially supported keywords ...................................................................................... 28
SOLUTION keywords requiring special description ...................................................................... 29
AMF ................................................................................................................................................. 29
EQLDIMS ........................................................................................................................................ 29
EQUIL .............................................................................................................................................. 29
EQUIL in black oil models ............................................................................................................ 29
EQUIL in compositional models ................................................................................................... 30
OPERATE, OPERATER .................................................................................................................. 30

iii
Intersect Migrator user guide

PRESSURE, PRVD ......................................................................................................................... 31

RPTRST .......................................................................................................................................... 31
3D property reports ...................................................................................................................... 31
Intersect restart files ..................................................................................................................... 31
RSW ................................................................................................................................................ 31
RTEMP, TEMPVD ........................................................................................................................... 31
SALT, SALTVD ................................................................................................................................ 31
SOIL, SGAS, SWAT ........................................................................................................................ 32
TBLK, TVDP .................................................................................................................................... 32
XMF ................................................................................................................................................. 32

8 SUMMARY ................................................................................................................. 33
SUMMARY Fully supported keywords ............................................................................................ 33
SUMMARY keywords requiring special description ...................................................................... 37
FSGR ............................................................................................................................................... 38
STEPTYPE ...................................................................................................................................... 38
WBP ................................................................................................................................................ 38
WPI .................................................................................................................................................. 38
WTEMP ........................................................................................................................................... 39
Ion rates ........................................................................................................................................... 39
Guide rates ...................................................................................................................................... 39
Potential rates .................................................................................................................................. 39

9 SCHEDULE ................................................................................................................ 40
SCHEDULE Fully supported keywords ........................................................................................... 40
SCHEDULE Partially supported keywords ..................................................................................... 41
SCHEDULE keywords requiring special description ..................................................................... 42
ACTION keywords ........................................................................................................................... 42
AQUCT, AQUFETP, AQUFLUX ...................................................................................................... 43
CECON ............................................................................................................................................ 43
Completion index usage within keywords ........................................................................................ 43
COMPDAT, COMPDATL ................................................................................................................. 43
COMPSEGS, COMPSEGL ............................................................................................................. 44
DATES ............................................................................................................................................. 44
FBHPDEF ........................................................................................................................................ 44
GCONINJE ...................................................................................................................................... 44
GCONPRI ........................................................................................................................................ 44
GCONPROD ................................................................................................................................... 44
GCONSALE ..................................................................................................................................... 45
GCONTOL ....................................................................................................................................... 45
GECON ........................................................................................................................................... 45
GINJGAS, WINJGAS ...................................................................................................................... 45
GPMAINT ........................................................................................................................................ 45
HEATER .......................................................................................................................................... 46
Drilling keywords ............................................................................................................................. 46

iv
Intersect Migrator user guide

RPTRST .......................................................................................................................................... 46
SAVE ............................................................................................................................................... 46
WCONHIST, WCONINJH ................................................................................................................ 47
WCONINJE, GCONINJE ................................................................................................................. 47
WCONPROD ................................................................................................................................... 47
WCONPROD, GCONPROD ............................................................................................................ 47
WCYCLE ......................................................................................................................................... 47
WEFAC ............................................................................................................................................ 47
WELLWAG ...................................................................................................................................... 47
WELOPEN, WELOPENL ................................................................................................................. 48
WELSEGS ....................................................................................................................................... 48
WELSPECS, WELSPECL ............................................................................................................... 48
WELTARG ....................................................................................................................................... 48
WINJMIX ......................................................................................................................................... 48
WINJTEMP ...................................................................................................................................... 48
WPAVE, WWPAVE, WPAVEDEP ................................................................................................... 48
WPIMULT, WPIMULTL ................................................................................................................... 49
WREGROUP ................................................................................................................................... 49
WSEGHEAT .................................................................................................................................... 49
WSEGTABL ..................................................................................................................................... 49
WSEPCOND ................................................................................................................................... 49
WTEST ............................................................................................................................................ 49
WTRACER ...................................................................................................................................... 49
WVFPEXP ....................................................................................................................................... 49
Use VFP files ..................................................................................................................................... 50
Naming restrictions .......................................................................................................................... 50
Wildcard well and group names ...................................................................................................... 50
Restrictions on node names ............................................................................................................ 51

10 Multiple-section keywords ....................................................................................... 52

11 GRID EDIT processing options ................................................................................ 54
Migrate grid edits default ................................................................................................................. 54
Process grid edits option ................................................................................................................. 54
Workflow differences ........................................................................................................................ 55
Run using the default migrate grid edits option ............................................................................ 56
Run using the process grid edits option ........................................................................................ 57
Limitations ......................................................................................................................................... 57
Data handling and transfer ............................................................................................................... 57
Keywords requiring special description ......................................................................................... 61
BOX, ENDBOX ................................................................................................................................ 61
MINPVV ........................................................................................................................................... 61
MULTFLT ........................................................................................................................................ 61
MULTREGT ..................................................................................................................................... 62

v
Intersect Migrator user guide

MULTSIGV ...................................................................................................................................... 62
MULTX/Y/Z ...................................................................................................................................... 62
REFINE, ENDFIN ............................................................................................................................ 62
RPTGRID ........................................................................................................................................ 62
Difference in supported keywords for classic workflow ............................................................... 62

12 Integration with Petrel .............................................................................................. 64

Development strategies .................................................................................................................... 64
Well folder names ............................................................................................................................. 64
Petrel interface .................................................................................................................................. 64
Other Petrel considerations ............................................................................................................. 65

A Supported development strategy rules .................................................................. 66

B Eclipse keywords versus Intersect nodes .............................................................. 68
C Intersect and Eclipse feature compatibility ............................................................ 85
The Eclipse to Intersect Migrator .................................................................................................... 85
Gridding and parallel simulation ..................................................................................................... 86
Equilibration ...................................................................................................................................... 86
Fluid modeling ................................................................................................................................... 86
Rock physics ..................................................................................................................................... 87
Well modeling .................................................................................................................................... 87
Reporting ........................................................................................................................................... 88
Fault and aquifer connections ......................................................................................................... 88
Coal Seam Gas .................................................................................................................................. 88

D Support for E100 defaults ........................................................................................ 91

RUNSPEC ........................................................................................................................................... 91
GRID ................................................................................................................................................... 91
EDIT .................................................................................................................................................... 91
PROPS ................................................................................................................................................ 91
REGIONS ............................................................................................................................................ 92
SOLUTION .......................................................................................................................................... 92
SUMMARY .......................................................................................................................................... 92
SCHEDULE ........................................................................................................................................ 92
Configuring Intersect nodes for E100 compatibility ...................................................................... 92
Configuring Intersect nodes for E300 compatibility ...................................................................... 93
E100 defaults requiring special description ................................................................................... 94
WCONPROD ................................................................................................................................... 94

Glossary ........................................................................................................................... 95

vi
Intersect Migrator user guide

1
Migrator overview
The Migrator converts Eclipse datasets into a format that can be run in Intersect, allowing an Eclipse dataset to be used
to perform a full Intersect simulation. Intersect cannot directly run an Eclipse dataset; it must first be converted into the
AFI format. Running an Eclipse dataset in Intersect is a two-step process.
• The Migrator reads an Eclipse dataset and writes an AFI file (which has the extension .afi).
• Intersect reads the AFI file and performs the simulation as requested by the AFI file.
The AFI file points to various other files that together form the input to Intersect. One of these files is the GSG file, which
is used to store the grid block properties used by Intersect.
The Migrator generates the AFI file by taking each Eclipse keyword in the dataset, and where possible, converting the
keyword into the AFI format. The Migrator produces detailed reports on what is and is not migrated to Intersect.
After running Intersect on the AFI file generated by the Migrator, and analyzing the Intersect results, you may decide you
need to change the input dataset. If you change the Eclipse dataset you need to rerun the Migrator to generate a new
AFI file.
The Migrator can use input Eclipse datasets, which load data from restarts, as long as the restart data has been
generated by Intersect. The Migrator does not support restarting from Eclipse-generated restart output.
By default, the custom_scripts extension is added to all migrated models. This makes it more convenient if you
want to add your own Python scripts to the Intersect model.
Further information: Restarting an Intersect simulation

Supported simulators
The Migrator supports a core set of keywords from both Eclipse 300 and Eclipse 100, but where there is a behavioral
difference between the Eclipse 300 and Eclipse 100 versions of the keyword, the Migrator has implemented the
Eclipse 300 behavior – unless otherwise stated. This may mean that certain Eclipse 100 keywords will need to be
converted into their Eclipse 300 form before running the Migrator.
Default values for Eclipse keywords vary between Eclipse 300 and Eclipse 100. See the Eclipse Reference Manual. The
Migrator will use different defaulting behavior depending on the setting of the --preferred-defaults Migrator
command line option (although not all keyword defaults are affected by this option currently). If no option is specified,
then Intersect legacy defaulting is used. Alternative options are Eclipse 100 defaulting (--preferred-
defaults=E100) or Eclipse 300 defaulting (--preferred-defaults=E300).
Further information: Support for E100 behavior.
The Migrator will run any valid Eclipse dataset. If the Migrator detects errors in the dataset they will be reported and no
simulation will be run. Error detection in the Migrator is not yet as extensive as that in the Eclipse simulators so running

Migrator overview | Supported simulators

1
Intersect Migrator user guide

Eclipse on the dataset can assist in locating data errors. Eclipse need only be run in NOSIM mode (data checking and
initialization only) to do this.

Run an Eclipse dataset in Intersect

The separate steps are described below.

Run the Migrator on an Eclipse dataset

You can run the Migrator using ECLRUN. This is a utility provided with Intersect.
• To run the Migrator use the following command: eclrun ecl2ix basename where basename is the root
name of the input dataset.
This command generates the AFI file but does not run Intersect on it.
• To find details of the command line options used by the Migrator, use the following command: eclrun --exe-
args="-h" ecl2ix basename

Run Intersect
• To run a simulation using the AFI file, use the following command: eclrun ix basename.
Intersect reads the AFI file and runs the simulation.
If the input Eclipse dataset is altered, the AFI file has to be regenerated from the dataset by rerunning the Migrator.
An AFI model consists of the file basename.afi, its associated files: basename_ECL2IX.gsg,
basename_ECL2IX_IX.ixf, and basename_ECL2IX_FM.ixf, and associated data folders.

Migration reports
This topic outlines the various reports the Migrator can give on the conversion process.

PRT file
The Migrator writes out a PRT file called basename_ECL2IX_MAKEAFI.PRT where basename is the root name of
the input dataset. This lists each keyword in the dataset and details how much of the keyword was converted to Intersect.
The migration status for a keyword is contextual for that instance of the keyword in the dataset. The Migrator classifies
the keyword conversion into four types:
FULLY_MIGRATED
all the keyword data was converted to Intersect. Every parameter supplied to the keyword was supported.
PARTIALLY_MIGRATED
not all the data for this keyword was migrated to Intersect. There will be a comment that explains what was and
was not migrated.
NOT_MIGRATED
the keyword was not migrated to Intersect because either the Migrator has not implemented the conversion or
Intersect does not yet have support for this feature.
IGNORED
the keyword is not relevant to Intersect. For example, OIL, VAPOIL, DISGAS, GAS or WATER in RUNSPEC.
They are also reported as Fully Supported Keywords in the rest of this User Guide.

Migrator overview | Migration reports | PRT file

2
Intersect Migrator user guide

Note: It is recommended that the PARTIALLY_MIGRATED and NOT_MIGRATED keywords are carefully reviewed.
This is because Intersect may produce significantly different results to Eclipse due to this data not being migrated.

Optionally write Eclipse property names

Many of the property identifiers used in the Intersect reservoir simulator and its Field Management system have shorter
Eclipse property names (see Appendix A.1 of the Intersect User Guide for a complete list). You can choose to write these
shorter property names to the IXF files using a command line option. This reduces the file size and may be helpful for
users who are more familiar with Eclipse.
By default, the migrated models use the Intersect property names. To use the equivalent Eclipse property names, add
this Migrator command line option:

--use-eclipse-prop-names=1

To revert to the default option, add:

--use-eclipse-prop-names=0

Note: If an Intersect qualified property name does not have an equivalent Eclipse property name, the Migrator writes the
Intersect property name.

Filtered output dataset

The Migrator is able to produce a "filtered" copy of the input dataset. This is an altered Eclipse dataset that captures only
the data used by Intersect. The filtered dataset may be simulated with Eclipse 300 or Eclipse 100 but it is not guaranteed
to run as any keywords needed by Eclipse but not Intersect may have been commented out. Where it does run, you may
find this useful in comparing the Intersect simulation results with Eclipse.
This modified dataset retains all the original keywords with added comments about their conversion status. Any
keywords with conversion status "NOT_MIGRATED" are annotated with "Not supported" and commented out.
Keywords whose status is IGNORED are left in the dataset.
• To switch on the output of this filtered dataset, the ECLRUN command line needs to be changed to pass an option to
the Migrator: eclrun --exe-args="-o yes" ecl2ix basename
This causes the filtered dataset called basename_ECL2IX.data to be created once the Migrator has completed its
processing.
There are additional options to control the format and name of the output file, as follows:

-o 1 These options are equivalent and produce the default non-uniform output.
-o yes
-o true
-o UNIFOUT Force output to be unified instead of generating include files.
-o SUFFIX="_my_file" Add _my_file to the output filename, that is
basename_my_file.data.
-o UNIFOUT,SUFFIX="_new_name" Both options together; produces unified output with filename suffix.

Migrator overview | Migration reports | Filtered output dataset

3
Intersect Migrator user guide

Other output
Where there are problems with the migration, the Migrator will provide as much information as possible, including the
name and location of the keyword that it was currently processing.

Export a list of supported keywords

The -k (or --export-supported-keywords) command line parameter requests the Migrator writes out the list of
fully and partially migrated keywords that the Migrator supports. It is written to a file called
supported_keywords_ECL2IX.xml.
• To do this from ECLRUN, use the following command: eclrun --exe-args="-k" ecl2ix basename

Key workflows
There are two main workflows:
• Keywords only – uses an Eclipse dataset to perform a simulation.
• Restarts – restarts a simulation using the Intersect restart facility.

Keywords only
The normal workflow is to run the Migrator using an Eclipse keyword file (a DATA file with keywords) possibly augmented
with a grid geometry file. This is termed the keywords-only option. The preferred choice of grid geometry file is EGRID,
which can be generated by Eclipse to describe the corner-point geometry, including LGRs if present.

Note: Only corner point geometry is supported; radial and unstructured are not.

A number of workflows exist that allow conversion of block-centered geometry keywords into data are usable by the
Migrator, but these are not recommended as they are prone to errors in transmissibility calculations and non-neighbor
connection handling. If you wish to run a model currently only available in block-centered geometry form, it is
recommended that you regenerate a corner-point model from your geological models.
This workflow has two options for handling GRID and EDIT section keywords:
Default: Migrate grid edits
This is the new workflow where GRID and EDIT section geometry and property editing keywords are migrated
to Intersect input for subsequent processing within Intersect. This enables grid property editing within the
Intersect input file
Option: Process grid edits
This is the original workflow where GRID and EDIT section keywords are mainly processed in the Migrator.
Further information: GRID EDIT processing options

Default: Migrate grid edits

The default option for GRID and EDIT section keyword handling is for the Migrator to transfer the geometry and initial
property arrays in the Eclipse file to the Intersect GSG file and migrate small property edits to an equivalent IXF file. This
information will be processed inside Intersect to generate the final transmissibility and pore volumes. You can edit the
grid properties in the IXF file before simulation without running the Migrator again.

Migrator overview | Key workflows | Default: Migrate grid edits

4
Intersect Migrator user guide

Option: Process grid edits

You can still choose to use the original Migrator GRID and EDIT section processing by using the command line
parameter: --process-grid-edits. An example is:

eclrun ecl2ix basename --exe-args="--process-grid-edits"

With this option, the geometry and initial properties are read from Eclipse keywords or grid geometry files, and the
transmissibilities and grid block properties are then generated and stored in a separate (GSG) file. When a GRID section
is processed that includes a grid geometry file, the grid geometry file takes precedence over any grid geometry keywords
in the main data file. As the generated GSG file does not include grid geometry, any modification of grid properties will
need to be made in the Eclipse EDIT section and then the Migrator will have to be run again.

Restarting an Intersect simulation

Intersect has the capability to save data at any point during a run for the purposes of initializing a subsequent run from
this information. The format of this data is not compatible with Eclipse and cannot be used for any purpose other than
restarting Intersect. Eclipse keywords can be used to instruct Intersect to write an Intersect restart and to restart from it.
Intersect can automatically generate restart information (using the RPTRST command) or on demand using the SAVE
keyword. Both SAVE and RPTRST commands can be used within the same time step but only one set of Intersect
restart files will be generated. The RPTRST keyword can also be used with the BASIC=0 option to prevent the saving of
Intersect restart files. Restart files can be explicitly saved whenever required by using the SAVE keyword at any required
time step; note that the SAVE keyword overrides the RPTRST keyword and will always generate Intersect restart files.
The Intersect data used for restart purposes is actually a directory containing many files, instead of a single file as is the
case for Eclipse.

Automatic output of data using the RPTRST keyword

The RPTRST keyword can be used to request Intersect restart files automatically by using the BASIC=3 option. In this
case, restart files are generated at the frequency specified by the FREQ option in the same way as Eclipse restart data
files are generated. The RPTRST keyword can be used in both the SOLUTION section and in the SCHEDULE section to
alter the behavior of future restart files.
Output of automatic restart files can be suppressed by including the NORST option to RPTRST. In this case no restart
information will be written until a further RPTRST or SAVE command is processed.

Output of Restart data on demand using the SAVE keyword

Outputting of data to be used to restart the simulator is requested using the SAVE keyword. The restart run is initiated
using the LOAD or RESTART keyword. To avoid confusion with Eclipse restart data or Intersect visualization restart
data, this data will be referred to as Intersect restart data or files. Saving restarts is done using the SAVE, AUTOSAVE
and MULTSAVE keywords. The Migrator will instruct Intersect to save the restart to a file called basename.nnnn,
where nnnn is the report step. The SAVE keyword is processed before any other keyword within the time step, hence
the Intersect restart may not contain restart data for the keywords after the TSTEP / DATES keywords but before the
SAVE keyword. In the example below the WCONPROD will not be included in the restart file created by the SAVE
keyword.

WCONPROD
'A*' 'OPEN' 'ORAT' 2000 4* 1000 9* /
/

SAVE

Migrator overview | Key workflows | Output of Restart data on demand using the SAVE keyword
5
Intersect Migrator user guide

If the SAVE keyword is not working as expected check if MULTSAVE is set to -1; this suppresses outputting of Intersect
restart files.
Intersect will output extra files when using the Eclipse options MULTSAVE set to 0 (or defaulted) and AUTOSAVE set to
1. The additional files represent previously saved time steps that Intersect is unable clean up. For workflows with very
large models these extra files may use significant extra space.

Reloading a restart
When restarting an Intersect simulation, make a copy of the original DATA file, modify this copy to be a restart
simulation, and run your Intersect restart simulation from this modified file. Using the original DATA file for restarting will
damage the Intersect restart data.
To load an Intersect restart file you need to add either the LOAD or RESTART keyword to a copy of the original data file
that was used to save the restart and specify the correct root name in item 1 and the report step to restart from in item 2.
It is very important that the entire dataset be the same as the original dataset, up to the point in the SCHEDULE section
where the restart was saved; this is quite different to the way restarts are loaded in Eclipse. You are free to modify or
extend the SCHEDULE section after the restart time (for example you could INCLUDE a particular prediction scenario in
a separate file).
Note that all time steps or dates that effectively occur before the restart time will be ignored. In this respect the resulting
behavior in Intersect is similar to that of an Eclipse restart run that uses the SKIPREST keyword. As this is the default
behavior in Intersect the Eclipse SKIPREST keyword is ignored by the Migrator.

Run parallel simulations

You can run Intersect in parallel mode. You need to use ECLRUN to launch a parallel run. When using ECLRUN, you
need to tell it how many processors to use by using the --np X command line parameter, where X is the number of
processors. An example is:
eclrun --np 2 ix basename

Thermal
Thermal models are supported. Review the supported keyword list to see which keywords are supported.

Intersect or Field Management specific functionality

To directly access Intersect or Intersect field management functionality, edit the basename_reservoir_edit.ixf
or basename_fm_edits.ixf.

Always start a keyword in the first column

In the dataset, always start a keyword at the beginning of the line. Keywords not started at the beginning of the line are
considered as the part of the last keyword's record and produce incorrect results or errors.

Important: The Migrator can only read the first 132 characters of any line in the DATA file and its included files. Any
characters after this will be ignored.
The line length restriction cannot be altered using the COLUMNS keyword as the Migrator does not support this keyword.

Migrator overview | Always start a keyword in the first column

6
Intersect Migrator user guide

Validate user-defined IXF with the Migrator

You can validate edited IXF files using the Migrator. This is a two-step process:
1. Run the Migrator to convert DATA file to AFI format, and then add your modifications/commands in the IXF file.
2. To validate the user-defined IXF with the Migrator, use the following command line: eclrun ecl2ix
basename.afi where basename.afi is the AFI file created in step 1 and includes the user-defined IXF.

Supported platforms
The Migrator runs on the same platforms as Intersect.

Migrator overview | Supported platforms

7
Intersect Migrator user guide

2
RUNSPEC
Many items in the RUNSPEC section are not relevant to Intersect. The keywords that are processed by the Migrator are
listed below. The grid size is taken from DIMENS and, for multiple reservoir grids, the number of reservoirs is taken from
NUMRES. Some dimensioning keywords, where the size can be deduced from the data, are ignored. For example, it is
not necessary to specify the number of LGRs or the maximum number of cells in any LGR with the LGR keyword, and
this keyword is ignored. Other important information from this section is the unit system (FIELD, METRIC, PVT-M or
LAB) and the simulation start date (START). Table dimensions (WELLDIMS, TABDIMS and so on) are used to set, for
example, the number of PVT tables, or numbers of regions. Whilst these numbers are not critical to the Migrator as they
are in Eclipse, many of them are used as hints when writing out the IXF, and they should therefore be left in or specified
where possible. If they are absent, the Migrator will try to deduce the correct values from data.
Keywords are considered partially supported where the Migrator cannot convert all parameters available in the Eclipse
keyword. The unsupported items for partially supported keywords are also listed. For detailed information on the
unsupported items in keywords see the Eclipse Reference Manual. Unsupported keywords are not included.
Further information:
• Fully supported RUNSPEC keywords
• Partially supported RUNSPEC keywords
• RUNSPEC keywords requiring special description
• Multiple selection keywords

RUNSPEC Fully supported keywords

AIM API AQUDIMS BLACKOIL BRINE CO2SOL COAL COMPS
DEADOIL DIMENS DISGAS DUALPERM DUALPORO ECLMC END ENDINC
ENDSCALE ENDSKIP EQLOPTS FAULTDIM FIELD FMTOUT FREEZEPC FULLIMP
GAS GASSOL GPTDIMS GRAVDR GRAVDRM GRIDOPTS H2SSOL HEATDIMS
IMPES IMPLICIT IMPSAT INCLUDE LAB LGRCOPY LOWSALT METRIC
MULTOUT MULTSAVE NODPPM NOMIX NOSIM NUMRES NUPCOL OIL
PATHS PETOPTS POLYMER REACTION RUNSPEC SATOPTS SAVE SKIP
SKIP100 SKIP300 SOLVENT START THERMAL TRACK UNIFOUT UNIFOUTS
VAPOIL VELDEP VFPIDIMS VFPPDIMS WATER WELLDIMS WELLOPTS

RUNSPEC | RUNSPEC Fully supported keywords

8
Intersect Migrator user guide

RUNSPEC Partially supported keywords

Keyword Unsupported Items, or Unsupported Choices (in brackets)
CBMOPTS Items: 1 (TIMEDEP, only supported for Coal Seam Gas), 2, 4, 5, 6, 7,
8, 9
EOS Item: 1 (ZJ)
EOSS Item: 1 (ZJ)
EQLDIMS Items: 4, 5
LOAD Items: 4, 5
MISCIBLE Items: 2, 3
REGDIMS Items: 2, 3, 8, 9, 10
ROCKCOMP Items: 1 (NONE, PALM-MAN, REVLIMIT, TPLM-MAN), 3, 4, 5
TABDIMS Items: 4, 6, 7, 8, 12, 16, 17, 18, 19, 20, 21, 22, 23
WSEGDIMS Items: 1, 3, 4

RUNSPEC keywords requiring special description

The following RUNSPEC keywords have additional restrictions.

BRINE, ECLMC
BRINE can be processed in either single-component or multi-component form.
If the BRINE keyword is present without the ECLMC keyword the single-component form will be used. Intersect will
assume the salt component to be NaCl, with the electroneutrality option turned off.
If ECLMC is present BRINE will be processed in multiple component form. In this case the Eclipse molecular salt
components will be split into ionic species and the electroneutrality option turned on.
Note that the Migrator only processes component salts defined in the BRINE keyword if the ECLMC keyword is present.
Further information: Multiple-component brine

COAL
In Intersect, the COAL keyword enables the Coal Bed Methane option or the Shale Gas option.

ENDSCALE
End-point scaling is automatically turned on when any end-point scaling keyword or the ENDSCALE keyword is present.
To turn off end-point scaling you will need to edit the IXF file to switch off vertical and horizontal end-point scaling.

GASSOL
GASSOL is restricted to only one component.

RUNSPEC | RUNSPEC keywords requiring special description | GASSOL

9
Intersect Migrator user guide

NUPCOL
In an Intersect restart simulation the NUPCOL keywords are ignored if encountered in the restart dataset.

NOMIX
The Migrator enables the oil and gas relative permeability interpolation near the critical point by default. This interpolation
is switched off if the NOMIX keyword is specified.

POLYMER
The formulation of polymer model in Intersect is different from the Eclipse model, and as none of the Eclipse polymer
option definition keywords are relevant they are not migrated. The sole exception to this is the POLYMER keyword itself,
which switches on the polymer modeling in Intersect.
The nodes required to define and operate the polymer model need to be manually added into the IXF files.

RUNSPEC | RUNSPEC keywords requiring special description | POLYMER

10
Intersect Migrator user guide

3
GRID
Keywords are considered partially supported where the Migrator cannot convert all parameters available in the Eclipse
keyword. The unsupported items for partially supported keywords are also listed. For detailed information on the
unsupported items in keywords see the Eclipse Reference Manual. Unsupported keywords are not included. Additional
information on some selected keywords is provided in and how grids are handled in the Migrator is also included.
Further information:
• Fully supported GRID keywords
• Partially supported GRID keywords
• GRID keywords requiring special description
• Grid handling
• Multiple selection keywords

GRID Fully supported keywords

ACTNUM ADD ADDREG AQUANCON AQUCT BOX CARFIN COALNUM
COARSEN COORD COPY CRNDENS DPGRID DPNUM DZMATRIX DZMTRX
DZMTRXV END ENDBOX ENDFIN ENDINC ENDSKIP EQUALREG EQUALS
FAULTS FLUXNUM GDFILE GRID GRIDFILE GRIDUNIT HEATCR HEATCRT
HXFIN HYFIN HZFIN INCLUDE INIT JFUNC JFUNCR LGRCOPY
MAPAXES MAPUNITS MAXVALUE MINPORV MINPV MINPVV MINROCKV MINRV
MINVALUE MULTFLT MULTIPLY MULTIREG MULTNUM MULTPV MULTREGP MULTREGT
MULTX MULTX- MULTY MULTY- MULTZ MULTZ- NODPPM NOGGF
NTG NXFIN NYFIN NZFIN OPERATE OPERATER OPERNUM PERMI
PERMJ PERMJFUN PERMK PERMX PERMY PERMZ PETGRID PINCH
PINCHNUM PINCHREG PORO REFINE RESVNUM ROCKCON ROCKCONL ROCKDEN
RPTGRID SIGMA SIGMAGD SIGMAGDV SIGMATH SIGMAV SKIP SKIP100
SKIP300 THCGAS THCOIL THCONMF THCONR THCONSF THCROCK THCWATER
THPRESFT ZCORN

GRID | GRID Fully supported keywords

11
Intersect Migrator user guide

GRID Partially supported keywords

Keyword Unsupported Items, or Unsupported Choices (in brackets)
AQUCON Items: 12, 13
AQUNUM Items: 11, 12
COORDSYS Items: 3 (COMP), 4 (JOIN), 5, 6
MINNNCT Items: 2, 3
NNC Items: 8, 9, 10, 11, 12, 13, 14, 16, 17
NNCGEN Item: 10
ROCKPROP Items: 5, 6 (B, N), 7

GRID keywords requiring special description

The following GRID keywords have additional restrictions

AQUCT, AQUFET, AQUFETP

AQUCT Item 10, AQUFET Item 6, AQUFETP Item 7: the water tables must be assigned to at least one active grid cell.
This is different behavior to Eclipse

AQUANCON
AQUANCON is supported in both the GRID and SOLUTION sections. The analytical aquifer must be declared (with
AQUCT, AQUFETP, AQUFLUX, or AQUFET) before AQUANCON is specified. That is, to migrate AQUANCON from GRID
section, the analytical aquifer needs to be declared in the GRID section as well. There is no such constraint in Eclipse.

COARSEN
The COARSEN keyword is not supported with the --process-grid-edits option.

GDFILE
Grids must be in the same unit system as the model, there is no unit conversion. Either the complete file name or just the
root name can be given.

INIT
If the INIT keyword is present, an Eclipse-format initial properties file will be produced. Note however that the region
properties PVTNUM, SATNUM and EQLNUM output, are the Intersect fluid region, rock region and equilibration region
properties. You will find the region mapping tables output to the print file useful for identifying the original Eclipse regions
to which the Intersect regions correspond .
Further information: PROPS

GRID | GRID keywords requiring special description | INIT

12
Intersect Migrator user guide

IONROCK
Intersect requires one cation exchange constant per rock region, but it is possible that the IONROCK property values
vary regionally but differently from the rock regions. The cation exchange constant for each rock region will be set equal
to the first value of the IONROCK property found in that region. If a rock region is found to span more than one
IONROCK value a warning will be issued.

JFUNC
J-Functions only work in the keywords-only workflow as it is only the presence of the JFUNC keyword that creates the
permeability direction property required by the simulator. This property cannot be manually created in the AFI file. You
can edit the J-Function parameters in the AFI once it has been created from a data set that contains the JFUNC
keyword.

MULTFLT
Item 3 of MULTFLT, diffusivity multiplier, is not supported by Intersect.

MULTREGT
Items 1 and 2 of MULTREGT cannot both be defaulted in the same record when used with the --process-grid-
edits option.

NNCGEN
The NNCGEN keyword is not supported with the --process-grid-edits option.

PINCH
In the PINCH keyword, Items 1 to 3 are interpreted in the same way as Eclipse 300. However, when NOGAP is specified
for item 2, then the method for calculating the thickness of a column of pinched out cells is that used by Eclipse 100, not
Eclipse 300.
In addition, Eclipse 100 items 4 and 5 are available.

PINCHNUM
The PINCHNUM keyword is only supported with the --process-grid-edits option.

PINCHREG
The PINCHREG keyword is only supported with the --process-grid-edits option.

RESVNUM
The RESVNUM keyword is only supported with the --process-grid-edits option.

GRID | GRID keywords requiring special description | RESVNUM

13
Intersect Migrator user guide

ROCKCON
ROCKCON in Eclipse 300 has a restriction that each rock can only be connected in one grid (the main grid or an LGR).
To have connections on multiple grids, you must specify a number of different rocks. Intersect does not have that
restriction.

ROCKCONL
ROCKCONL in Eclipse 300 has a restriction that each rock can only be connected in one grid (the main grid or an LGR).
To have connections on multiple grids, you must specify a number of different rocks. Intersect does not have that
restriction.

GRID handling
The following options are available for handling grids:
• Grid geometry.
• Cell properties.
• Dual porosity.
• Transmissibilities.
• Thermal.
• Grid export.
• NNC export.

Grid geometry
Only Cartesian corner point geometry is supported using the keywords-only workflow. Multiple reservoirs can be defined
(using COORDSYS) but they cannot be connected through cells; only through wells.
Cartesian local grid refinement (LGR) is supported. LGRs are implemented in Intersect by removing the host cells and
connecting the surrounding cells to the external LGR cells. There is no support in Intersect for local time stepping.
Touching LGRs are automatically identified; it is not necessary to use the AMALGAM keyword. LGRs can abut faults.
LGRs can connect through pinched out cells to the parent grid but cannot connect through pinched out parent cells to a
neighboring LGR. Nested LGRs are supported provided that they connect only to their immediate parent, that is there
must be a border of at least one parent cell around the LGR.

Note: Local grid coarsening (LGC) is not supported.

COORD and ZCORN can follow a BOX keyword to specify a restricted input box.

Cell properties
Cell properties are handled in the same way for all sections. Properties are introduced either directly by name or with one
of the following keywords:
• ADD
• COPY
• EQUALS
• MULTIPLY
The following keywords can be used to set or reset the current input box, or to switch between local and global grids:

GRID | GRID handling | Cell properties

14
Intersect Migrator user guide

• BOX
• ENDBOX
• REFINE
• ENDFIN
The following properties allow the Eclipse 100 behavior where only the top plane (K=1) need be specified completely,
with unspecified values in lower planes taking their values from the plane above:
• PERMX
• PERMY
• PERMZ
• PORO

Dual porosity
Dual porosity and single permeability and dual porosity and dual permeability systems are supported. In addition, single
porosity regions may be defined (for dual porosity and single permeability systems) with the DPNUM keyword.
Identical geometry must be used for both matrix and fracture cells. This is taken from matrix cells. Any geometry defined
on fracture cells is ignored.
DPNUM, DZMATRIX, SIGMAV properties should only be specified for matrix cells. For properties that should be defined
on both matrix and fracture cells, DPGRID can be used to copy values from matrix to fracture cells when only the matrix
cell values are specified. As with Eclipse, this only works for those grid properties listed under the DPGRID keyword in
the Eclipse Reference Manual.
In addition to the cell property keywords, the following dual porosity keywords are supported:
• DZMTRX
• NODPPM
• SIGMA
• SIGMAGD
• SIGMAGDV

Transmissibilities
The following keywords affect cell activity and transmissibility calculations:
• MINPORV
• PINCH
• PINCHOUT
Only NEWTRAN style transmissibility is supported. In addition to the MULTX/X-/Y/Y-/Z/Z- transmissibility
multipliers, the following keywords can be used:
• FAULTS
• MULTFLT
• MULTREGT

Note: Eclipse 300 treats transmissibility values less than a tolerance (1.0e-06) for non-neighbor connections as 0.
Intersect does not set them to 0. As a result, you can have flow across such cells in Intersect but not in Eclipse 300.

GRID | GRID handling | Transmissibilities

15
Intersect Migrator user guide

Thermal
The implementation of the functionality behind the THCOIL, THCGAS, THCWAT keywords is different in Intersect from
Eclipse. In Intersect it uses a simple volume weighting for each independent phase.

Grid export
When the Migrator is run with the keywords-only option, grid geometry files (GRID, EGRID and GSG) may be generated
for use by other applications. This is a Migrator rather than Intersect activity, and is controlled by the following keywords:
• GRIDFILE
• GRIDUNIT
• MAPAXES
• MAPUNITS
• NOGGF

Non-neighbor connections export

When working with single porosity, keywords only models, non-neighbor connections (NNCs) and their transmissibilities
are written into the NNC section of the GRID or EGRID files and the TRANNNC section of the INIT file.
These NNCs are generated by:
• Numerical aquifers
• Faults / displacements
• Explicit NNCs created using the NNC keyword.
If an NNC is explicitly declared using the NNC keyword between two cells that are natural neighbors in the grid, then the
transmissibility of the NNC will be added onto the appropriate TRANX, TRANY or TRANZ value in the INIT file.
If there are multiple connections between the same pair of cells the transmissibilities are added together. These are
written into the GRID, EGRID and INIT files, one connection will contain the sum of the transmissibilities and the
others will have a transmissibility value of 0.
NNCs and transmissibilities are not written out for amalgamated (neighboring) LGRs or for dual porosity.

GRID | GRID handling | Non-neighbor connections export

16
Intersect Migrator user guide

4
EDIT
Only a limited set of modifications is allowed in the EDIT section.
Further information:
• Fully supported EDIT keywords
• EDIT keywords requiring special description
• Multiple selection keywords

EDIT Fully supported keywords

ADD ADDREG BOX COPY DEPTH EDIT END ENDBOX
ENDFIN ENDINC ENDSKIP EQUALREG EQUALS HEATTR HEATTTHT HEATTX
HEATTY HEATTZ INCLUDE LGRCOPY MAXVALUE MINVALUE MULTFLT MULTIPLY
MULTIREG MULTPV MULTREGP MULTREGT MULTX MULTX- MULTY MULTY-
MULTZ MULTZ- OPERATE OPERATER PORV REFINE ROCKV SKIP
SKIP100 SKIP300 TRANX TRANY TRANZ

EDIT keywords requiring special description

The following EDIT keywords have additional restrictions.

EDITNNC
Connections to numerical aquifers and matrix-to-fracture cell connections cannot be specified.

EDITNNCR
The EDITNNCR keyword is not supported with the --process-grid-edits option.

EDIT | EDIT keywords requiring special description | EDITNNCR

17
Intersect Migrator user guide

MULTFLT
Item 3 of MULTFLT, diffusivity multiplier, is not supported by Intersect.

MULTREGT
When MULTREGT is specified in the EDIT section, Eclipse 300 applies region transmissibility multipliers from
MULTREGT after transmissibility overrides specified with TRANX/Y/Z. The behavior of the Migrator's default workflow
(grids processed in Intersect) is the same, but if the --process-grid-edits option is specified, the multipliers are
applied first, and the overrides afterwards.

Pore volume
Pore volumes calculated at the end of the GRID section can be modified in the EDIT topic. The final set of connections
across pinched out cells will be determined from cell activity based on the modified pore volumes.

EDIT | EDIT keywords requiring special description | Pore volume

18
Intersect Migrator user guide

5
PROPS
All the core black oil and compositional keywords are fully supported; both saturation function keyword families are
supported, apart from keywords introducing 2D tables of relative permeability, for example SOF32D.
PVT table validation differs between Intersect and Eclipse. For example, Intersect may warn about monotonicity
problems that Eclipse does not.
Keywords are considered partially supported if the Migrator cannot convert all the parameters available in the Eclipse
keyword. Those items which are unsupported are listed. For detailed information on these unsupported items see the
Eclipse Reference Manual. Unsupported keywords are not listed here. Additional information on temperature keywords
and multi-component brine is also included.
Further information:
• Fully supported PROPS keywords
• Partially supported PROPS keywords
• PROPS keywords requiring special description
• Behavior of temperature keywords
• Multiple-component brine
• Multiple selection keywords

PROPS Fully supported keywords

ACF ACFS ADD ADDREG AMFVD APIGROUP AQUTAB BDENSITY
BIC BICS BOX CGDTYPE CGVTYPE CNAMES CODTYPE COMPVD
COPY COVTYPE CREF CVTYPE CVTYPES DENAQA DENSITY DNGL
DREF DREFS DREFT END ENDBOX ENDFIN ENDINC ENDSKIP
ENKRVT ENPCVT ENPTVT EQLDKVCR EQLDREAC EQUALREG EQUALS FACTLI
GASVISCT GRAVITY HEATVAP HEATVAPE HEATVAPS IKRG IKRGR IKRO
IKRORG IKRORW IKRW IKRWH IKRWR IKRWRH INCLUDE IPCG
IPCW ISGCR ISGL ISGLPC ISGU ISOGCR ISOWCR ISWCR
ISWL ISWLPC ISWU KRG KRGR KRO* KRORG* KRORW*
KRW* KRWH* KRWR* KRWRH* KVAN KVCOMP KVCR KVCRS

PROPS | PROPS Fully supported keywords

19
Intersect Migrator user guide

KVMF KVTABC* KVTABLE KVTABT* KVTEMP LANGMEXT LANGMUIR LANGMULT

LBCCOEF LBCCOEFR LILIM LKRO LKRORG LKRORW LKRW LKRWR
LPCW LSALTFNC LSOGCR LSOWCR LSWCR LSWL LSWLPC LSWU
MAXVALUE MINVALUE MISCEXP MISCSTR MISCSTRR MULTIPLY MULTIREG MW
MWS NCOMPS OILCOMPR OILMW OILSPECH OILVINDX OILVISCT OILVTIM
OMEGAA OMEGAAS OMEGAB OMEGABS OPERATE OPERATER OVERBURD PARACHOR
PCG PCRIT PCRITS PCW PEDERSEN PEDTUNE PEDTUNER PMISC
PPCWMAX PRCORR PREF PREFS PREFT PROPS PVCDO PVCO
PVDG PVDO PVDS PVTG PVTO PVTW PVZG REACACT
REACCORD REACENTH REACPHA REACPORD REACRATE REFINE ROCK ROCKOPTS
ROCKTAB ROCKTABH RSCONST RSCONSTT RSWVD RTEMP RVCONST RVCONSTT
SCALECRS SDENSITY SGCR SGFN SGL SGLPC SGOF SGU
SKIP SKIP100 SKIP300 SLGOF SOF2 SOF3 SOGCR SOLUAQA
SOLUBILI SOMGAS SOMWAT SOR SOROPTS SOWCR SPECHA SPECHB
SPECHG SPECHH SSHIFT SSHIFTS STCOND STONE STONE1 STONE2
STOPROD STOREAC SWATINIT SWCR SWFN SWL SWLPC SWOF
SWU TCRIT TCRITS TEMPVD THERMEX1 TLMIXPAR TOLCRIT TREF
TREFS TREFT VCOMPACT VCRIT VCRITS VCRITVIS VDFLOW VDFLOWR
VDKRG VDKRGC VDKRO VISCAQA WAGHYSTR WATDENT WATERTAB WATVISCT
ZCRIT ZCRITS ZFACTOR ZFACTORS ZI ZMFVD

PROPS Partially supported keywords

Keyword Unsupported Items, or Unsupported Choices (in brackets)
DIFFCBM Only supported for Coal Seam Gas
DIFFCOAL Items 1, 2: only supported for Coal Seam Gas. Item 3: not supported.
EHYSTR Items: 6, 7, 8, 9, 10, 11, 12
EOS Item: 1 (ZJ)
EOSS Item: 1 (ZJ)
PMAX Items: 2, 3, 4
PVTWSALT Record 1 - Item: 2
RESORB Only supported for Coal Seam Gas
TRACER Items: 3, 4, 5, 6
VISCREF Items: 2, 3

PROPS keywords requiring special description

The following PROPS keywords have additional restrictions.

PROPS | PROPS keywords requiring special description

20
Intersect Migrator user guide

Equation of state keywords

The following equation-of-state keywords used to define reservoir models: ACF, MW, VCRIT, ZCRIT and PARACHOR ,
cannot be defaulted. If any values for these keywords are defaulted in the dataset the Migrator generates an error and no
simulation is run.
The following equation-of-state keywords used to define reservoir models do have defaults in Eclipse 300: PCRIT,
TCRIT, and SSHIFT. The same defaults are implemented by the Migrator but it is strongly recommended to not use
them.
However, all keywords used to define surface equations-of-state models, for example ACFS, BICS, MWS, can be
defaulted. If they are defaulted, they take their values from the reservoir equation-of-state with the same region index. If
there is no reservoir equation-of-state model with the same index, the values are copied from the previous surface
equation-of-state model.
When Intersect uses the reservoir and surface equation-of-state models it will associate each reservoir model with the
surface model with the same index. These defaulting rules ensure there will be one surface equation-of-state model
created for every reservoir equation-of-state model.
If however the surface keywords define more models than there are reservoir models, then the extra surface models will
be created but not associated with any reservoir equation-of-state, and will be unused by Intersect unless manually
selected (say for use by a well) in the user-edits ixf.

AMFVD
Eclipse 300 only uses the AMFVD keyword for THERMAL simulations together with CO2STORE. The Migrator allows
definition of initial aqueous phase compositions (mole fractions of the single dissolved component and water) versus
depth using this keyword.

CVTYPE, CVTYPES
The value of CVTYPE may cause other migrated values to be overwritten.
If the CVTYPE of a component is set to DEAD the critical temperature of that component will be reset to a large value
(Metric: 10000 K = 9726.85 C; Field: 10000 R = 9540.33 F), and the K-value correlation coefficients or tables will be
reset so they return a fixed value of 0.0.
If the CVTYPE of a component is set to GAS the critical temperature of that component will be reset to a small value
(Metric: 1 K = –272.15 C; Field: 1 R = –458.67 F), and the K-value correlation coefficients or tables will be reset so they
return a fixed value of 1.0e6
CVTYPES uses the same logic to modify the critical temperature of components in surface equation-of-state models.

DENAQA, VISCAQA
These keywords are restricted to one component. (To get similar results for the Aqua Density/Viscosity calculation using
Ezrokhi's correlation, use OPTION3 item 199 in Eclipse 300).

IONXROCK
Eclipse 100 associates the values of IONXROCK with Saturation function regions but Intersect associates these values
with Rock regions. The Migrator reassigns the values to the appropriate Rock region.

KVCR, KVCRS
The migrated Crookston coefficients may be overwritten depending on the value of CVTYPE (CVTYPES for surface
equations-of-state). See comments on CVTYPE above.

PROPS | PROPS keywords requiring special description | KVCR, KVCRS

21
Intersect Migrator user guide

LANGMUIR, LANGMEXT
Intersect includes a Shale Gas option using Langmuir isotherms, with assumed instant adsorption and single porosity.
There are two options available:
• Extended Langmuir Isotherm
• Tabular Adsorption Data Entry
This feature is similar to the Eclipse Coal Bed Methane option, when used with instant adsorption and single porosity.
However, in Intersect the extended Langmuir isotherm option is supported by both the black oil and compositional
models while Eclipse Black Oil does not allow you to use the LANGMEXT keyword.

Note: Use of Langmuir isotherms with dual porosity systems is currently not supported.

PVTW, WATERTAB
The Intersect fluid model describes both hydrocarbon and aqueous fluid properties, so the PVTW (or WATERTAB) data
must be associated with hydrocarbon properties (for example as specified by PVTO or EOS and so on).
For black oil models: PVTO tables and PVTW / WATERTAB tables are both indexed by the PVTNUM region property, so
PVTO table 1 is associated with PVTW / WATERTAB table 1 and so on
For compositional models, Eclipse 300 uses EOSNUM to define EOS regions but PVTNUM to define water (PVTW /
WATERTAB) regions. Therefore in order to construct the correct fluid model for Intersect, the Migrator must find all
combinations of EOSNUM and PVTNUM used in the model and create Intersect fluid models with these combinations of
EOS and water properties. The Intersect fluid models will be named PVTNUM_xxx_EOSNUM_yyy, where xxx and
yyy are the Eclipse PVT and EOS region numbers, respectively.

PVTWSALT, BDENSITY
Models containing the BRINE keyword define the water properties using PVTWSALT instead of PVTW.
The density of the brine is specified separately in the BDENSITY keyword.

ROCKOPTS
If item 3 of ROCKOPTS has the same value as ROCKNUM, the number of compaction tables is always taken from the
number specified in ROCKCOMP item 2, not item 13 of TABDIMS. If TABDIMS item 13 and ROCKCOMP item 2 are
inconsistent a warning is issued.

RSWVD
As only one soluble component is allowed you are restricted to defining only one component initial concentration in the
aqueous phase.

RTEMP, TEMPVD
The reservoir temperature profile can be defined for both enumeration cases and equilibration cases. It can be defined
as a separate (constant) temperature for each fluid region (RTEMP), varying differently with depth in each equilibration
region (TEMPVD) or explicitly in each grid cell (TEMPI). Note that RTEMPVD (SOLUTION) is not supported.
Further information: Behavior of temperature keywords.

PROPS | PROPS keywords requiring special description | RTEMP, TEMPVD

22
Intersect Migrator user guide

SOLUAQA
Restricted to only component.
If this keyword contains defaulted values the Migrator produces an error. This is because the Migrator cannot
automatically generate suitable values to be passed to Intersect. You need to replace any defaulted values with actual
values.
You can generate actual values from Eclipse by performing a NOSIM run in Eclipse 300 and requesting the default table
to be printed out in the PRT file using

RPTPROPS
SOLU /

SOLUBILI
If this keyword is omitted for CO2 a default table is generated. The Migrator uses the correlation of Chang, Coats and
Nolen for calculating the default values of the dissolved gas solution ratio at specific pressure, similar to Eclipse 300.
Instead of the values for formation volume factor, viscosity and compressibility the default Ezrokhi's coefficients are used
for calculating the aqueous viscosity and density. This is similar to setting OPTIONS3 item 164 and 165 active and
defining the default DENAQA and VISCAQA keywords in Eclipse 300.

TCRIT. TCRITS
The Migrator supports the defaulting of TCRITS but not TCRIT, for which values must be specified. See comments on
Equation of state keywords above.
Critical temperatures for a component may be reset if CVTYPE (or CVTYPES) is present. See comments on CVTYPE
above.

TRACER
The Eclipse 100 option to define the units of the tracer concentration is not supported by Intersect. Similarly Intersect
does not support partitioned tracers. This means that only the first two items of the TRACER keyword entries are
supported. These are the name of the tracer and the name of the fluid/hydrocarbon component that carries the tracer.

VCRITVIS
If the VCRITVIS keyword is defined but contains defaulted items, values for those items will be copied from the VCRIT
keyword.

ZCRITVIS
Critical Z-factors for viscosities are not supported by Intersect; use VCRITVIS instead, otherwise Intersect uses the
normal critical Z-factors defined by ZCRIT.

ZFACT1
The ZFACT1 keyword is not supported.

PROPS | PROPS keywords requiring special description | ZFACT1

23
Intersect Migrator user guide

Behavior of temperature keywords

The Migrator requires that the temperature is defined for enumeration and equilibration as explained below.

Enumeration
For enumeration the Migrator needs the temperature to be defined. If it is not defined an error is generated.
The temperature can be defined in one of three ways:
• In the PROPS section, define TEMPVD
• In the PROPS section, define RTEMP
• In the SOLUTION section, define TEMPI
The logic used is:
• TEMPI in the SOLUTION section takes precedence over any setting in the PROPS section.
• If TEMPI is not defined in the SOLUTION either TEMPVD or RTEMP must be defined in the PROPS section.
• If both TEMPVD and RTEMP are defined the TEMPVD keyword takes precedence.
• If there is more than one occurrence of TEMPVD or RTEMP the instance that occurs latest in the PROPS section is
used.
SOLUTION section keywords override the PROPS section keywords and a warning is logged.

Equilibration
The Migrator also needs the temperature to be defined for equilibration. If it is not defined an error is generated.
The temperature can be defined in one of two ways:
• In the PROPS section, define TEMPVD
• In the PROPS section, define RTEMP
The logic used is:
• If both TEMPVD and RTEMP are defined the TEMPVD keyword takes precedence.
• If there is more than one occurrence of TEMPVD or RTEMP the instance that occurs latest in the PROPS section is
used.

Thermal
Intersect uses different internal steam table data (IAPWS 97) from Eclipse. The closest match can be obtained by using
the THSTT97 keyword and using defaulted values for the PVTW, DENSITY or GRAVITY keywords. For water compare
the moles in place when reviewing the Intersect and Eclipse 300 fluids in place.

Multiple-component brine
When migrating multiple component brine models, the Migrator enables the electroneutrality option. This means that the
molecular salts defined in Eclipse will be split into ionic species.

Concentrations
The mass concentrations of whole salts defined in Eclipse are replaced with molar charge concentrations of each ionic
species encountered in the Eclipse salts.

PROPS | Multiple-component brine | Concentrations

24
Intersect Migrator user guide

The procedure used is:

• The mass concentration of each salt is converted to a molar concentration by dividing by the molecular weight of the
salt.
• The ions in the salt component are identified
• The molar concentration of charges for each ion in the salt are calculated by multiplying the molar concentration by
the number of electrical charges carried by these ions in one molecule of the salt.

Note: Concentrations of charges from sodium (Na+) ions will not be written out as sodium is the redundant electron
neutral ion; its concentrations can be deduced from the concentrations of the other species.

Example
Original Eclipse molecular salt component mass concentrations:
• 58.44 kg/m3 NaCl
• 11.098 kg/m3 CaCl2
Intermediate calculations:
• 58.44 kg/m3 NaCl = 1 kg-mole/m3 NaCl =1 kg-mole/m3 charges from Na+ ions + 1 kg-mole/m3 charges from Cl- ions.
• 11.098 kg/m3 CaCl2 = 0.1 kg-mole/m3 CaCl2 = 0.2 kg-mole/m3 charges from Ca2+ ions + 0.2 kg-mole/m3 charges
from Cl- ions
Resulting Intersect ionic species molar charge concentrations:
• 1 kg-mole/m3 charges from Na+ ions (will not be exported, see note above)
• 0.2 kg-mole/m3 charges from Ca2+ ions
• 1.2 kg-mole/m3 charges from Cl- ions

Saturation functions
When migrating saturation function tables, family (ii) saturation table keywords (SWFN, SGFN, SOF2 and SOF3) are
migrated to the single phase saturation function node in Intersect (SaturationFunction). Family (i) saturation table
keywords (SWOF, SGOF and SLGOF) are migrated to the two phase saturation function node in Intersect
(TwoPhaseSaturationFunction).
Although the gas-water saturation function keyword SGWFN is classified as a family (ii) keyword, this is still migrated to
the two phase saturation function node in Intersect because it has a structure that is similar to the two phase saturation
function keywords.
Intersect has a restriction that cases with solvent have to use the single phase saturation function node. As such,
saturation function tables for cases with the SOLVENT keyword are migrated to the SaturationFunction node
irrespective of whether family (i) or family (ii) saturation tables have been provided.

PROPS | Saturation functions

25
Intersect Migrator user guide

6
REGIONS
The keywords that are processed by the Migrator are listed below. Unsupported keywords are not included.
Further information:
• Fully supported REGIONS keywords
• REGIONS keywords requiring special description
• Multiple selection keywords

REGIONS Fully supported keywords

ADD ADDREG BOX COPY END ENDBOX ENDFIN ENDINC
ENDSKIP EOSNUM EQLNUM EQUALREG EQUALS FIP* FIPNUM IMBNUM
INCLUDE LSNUM LWSLTNUM MISCNUM MULTIPLY MULTIREG OPERATE OPERATER
OPERNUM PMANUM PVTNUM REFINE REGIONS ROCKNUM SATNUM SKIP
SKIP100 SKIP300 TNUM* TRACKREG WH2NUM WH3NUM

REGIONS keywords requiring special description

When the --process-grid-edits option is used, the Migrator has to transform the region data as Eclipse and
Intersect define regions differently. Some region properties are merged for example PVTNUM and EOSNUM, see below.
Eclipse tracer concentration regions may be defined differently depending on whether the model is compositional or
black oil. See TNUM below.

EOSNUM, PVTNUM
For compositional models, when the --process-grid-edits option is used, the Migrator combines EOSNUM and
PVTNUM into a single fluid region property called FLUIDMODEL_REGION. The Migrator generates a table showing the
mapping from the Eclipse region numbers to the Intersect fluid model names and numbers.

REGIONS | REGIONS keywords requiring special description | EOSNUM, PVTNUM

26
Intersect Migrator user guide

EQLNUM
This region property is migrated to Intersect, with the following exception. When the --process-grid-edits option
is used, the name of each equilibrium region, created by the Migrator, is prefixed with the name of the fluid model that
the equilibrium region belongs to, for example PVTNUM_1_EQLNUM_2).

SATNUM, IMBNUM, PVTNUM, ROCKNUM

When the --process-grid-edits option is used, the Migrator creates a single rock region property,
ROCKMODEL_REGION, based on the properties given in the SATNUM, IMBNUM, PVTNUM, and ROCKNUM keywords.
The Migrator then provides Intersect with a rock model definition table, detailing which drainage or imbibition function and
rock compressibility model to use for each region. The Migrator generates a table showing the mapping from the Eclipse
region numbers to the Intersect region names and numbers.

TNUM
Black oil Eclipse models may have separate tracer concentration region properties defined for a fluid phase if that phase
can exist in both free and solution states. In this case the free state tracer concentration region for a traced phase is used
as the tracer concentration region for the appropriate component. The solution state tracer concentration region is not
used.
For example if the input data included a tracer T1 attached to the gas phase, with TNUMFT1 and TNUMST1 used to
define the concentration region of the tracer for the free and solution states respectively, then TNUMFT1 would be
migrated to define the tracer concentration regions for the "GAS" component. TNUMST1 would not be migrated.
Tracer concentration regions defined from compositional models are migrated directly.

REGIONS | REGIONS keywords requiring special description | TNUM

27
Intersect Migrator user guide

7
SOLUTION
Model initialization is performed differently in Eclipse and Intersect, so results may not be identical. One of your first
quality checks should be to verify that initial conditions between Intersect and Eclipse are reasonably similar.
Keywords are considered partially supported if the Migrator cannot convert all parameters available in the Eclipse
keyword. Those items which are unsupported are listed. For detailed information on the unsupported items in keywords
see the Eclipse Reference Manual. Unsupported keywords are not listed here.
Further information:
• Fully supported SOLUTION keywords
• Partially supported SOLUTION keywords
• SOLUTION keywords requiring special description
• Multiple selection keywords

SOLUTION Fully supported keywords

ADD ADDREG AMF AMFVD APIVD AQANCONL AQUANCON AQUCT
AQUFET AQUFETP AQUFLUX BOX COPY DATUM DATUMR DATUMRX
END ENDBOX ENDFIN ENDINC ENDSKIP EQUALREG EQUALS GPTABLE
GPTABLE3 GPTABLEN INCLUDE MULTIPLY MULTIREG NEI OILAPI OPERATE
OPERATER OUTSOL PBUB PBVD PDEW PDVD PRESSURE PRVD
REFINE ROMF RPTRST RS RSVD RSW RSWVD RTEMP
RV RVVD SALT SALTVD SGAS SKIP SKIP100 SKIP300
SOIL SOILR SOLUTION SSOL SWAT TBLK* TEMP TEMPI
THPRES TVDP* XMF YMF ZMF

SOLUTION Partially supported keywords

Keyword Unsupported Items, or Unsupported Choices (in brackets)
FIELDSEP Items: 9, 10

SOLUTION | SOLUTION Partially supported keywords

28
Intersect Migrator user guide

Keyword Unsupported Items, or Unsupported Choices (in brackets)

FIPSEP Items: 10, 11
GASADCO Only supported for Coal Seam Gas
GASADEC Only supported for Coal Seam Gas
GASCONC Only supported for Coal Seam Gas
GASSATC Only supported for Coal Seam Gas

SOLUTION keywords requiring special description

The following SOLUTION keywords have additional restrictions.

AMF
Intersect only uses this keyword for equilibration. It does not use it for enumeration. By contrast, in Eclipse 300 this
keyword is only used for enumeration. The Migrator uses the data in this keyword to define the initial aqueous phase
composition (the mole fractions of the dissolved component and water) in each cell for Intersect's equilibration.

EQLDIMS
Item 2 in EQLDIMS defines the size of the internal pressure versus depth table created during equilibration. In Eclipse
this is the number of depth nodes in the table, however in Intersect this corresponds to the
PressureDepthTableIncrement field in the Equilibrium node, which is the depth difference between each node in the
table. So the Migrator sets this field to the (thickness of the equilibration region) / (the value of item 2 from the keyword).

EQUIL
The behavior of the keyword depends on whether it is defined in a blackoil or a compositional model.

EQUIL in black oil models

If the gas-oil contact depth (GOC) is within the equilibration region, and not equal to the water-oil contact depth (WOC),
the implication is that there is a gas-oil interface in the model, so the DataType field for the Equilibrium node is set
to DATUM_PLUS_GOC . This means Intersect honors the gas-oil contact depth, datum depth and pressure.
In all other situations it is set to DATUM_PLUS_COMP, so will honor the datum depth, pressure and composition.

Note: If the GOC is above the WOC (thus there is an oil phase present in the model), and the datum depth is not the
same as the GOC then initialization can only succeed if an RSVD table is present. If wet gas is also present in this
situation then an RVVD table is also required.

The FluidType field for the Equilibrium node is not set by default. The value is calculated by Intersect. If the --
process-grid-edits option is specified, FluidType is set to BUBBLE_POINT except for the following conditions:
• If there is gas in the model but no oil (GOC within equilibration region and equal to WOC) it is set to DEW_POINT.
• If there is only water in the model (GOC and WOC above the equilibration region), and RVVD has been defined but
not RSVD, it is set to DEW_POINT.
• If there is only water in the model (GOC and WOC above the equilibration region), and both RVVD and RSVD have
been defined and the datum depth is above the GOC, it is set to DEW_POINT.

SOLUTION | SOLUTION keywords requiring special description | EQUIL | EQUIL in black oil models
29
Intersect Migrator user guide

EQUIL in compositional models

The CompositionDepthTable node and DataType field for the Equilibrium node are set according to the
value of EQUIL items 10 and 11 as follows:
• If EQUIL item 10 is set to 1...
• The ZMFVD keyword must be provided and is copied to the TOTAL field of the CompositionDepthTable
node, in Intersect.
The DataType field for the Equilibrium node is set to DATUM_PLUS_COMP.
• If EQUIL item 10 is set to 2...
• If the ZMFVD keyword is provided, it is copied to the VAPOR field of the CompositionDepthTable node
but truncated below the GOC.
• Otherwise, the COMPVD keyword is split into the LIQUID and VAPOR fields of the
CompositionDepthTable node.
• If EQUIL item 11 is not set to 1, the DataType field for the Equilibrium node is set to GOC_PLUS_COMP. If
EQUIL item 11 is set to 1, the DataType field is set to DATUM_PLUS_GOC, which ensures that the datum
pressure is used.
• If EQUIL item 10 is set to 3...
• If the ZMFVD keyword is provided, it is copied to a LIQUID field for the CompositionDepthTable node but
truncated above the GOC.
• Otherwise, the COMPVD keyword is split into the LIQUID and VAPOR fields of the
CompositionDepthTable node.
• If EQUIL item 11 is not set to 1, the DataType field for the Equilibrium node is set to GOC_PLUS_COMP. If
EQUIL item 11 is set to 1, the DataType field is set to DATUM_PLUS_GOC, which ensures that the datum
pressure is used.
The FluidType for the Equilibrium node is set as below:
• If EQUIL item 10 is set to 1...
• If single phase oil (GOC above region top depth), BUBBLE_POINT is used.
• If single phase gas (GOC > region bottom depth) or condensate (GOC equals WOC), DEW_POINT is used.
• otherwise, CRITICAL will be used.
• If EQUIL item 10 is set to 2, DEW_POINT is used.
• If EQUIL item 10 is set to 3, BUBBLE_POINT is used.
Behavior of EQUIL items 7/8: if these are set to 0 the Migrator creates a constant Pb/Pd versus depth table (Intersect
nodes PBubDepthTable and PDewDepthTable) with Pb/Pd set to the datum pressure (that is the saturation
pressure equals pressure at GOC and GOC equals datum pressure). If it is set greater than 0 the Migrator uses the
corresponding RSVD or PBVD / RVVD or PDVD table.
For heavy oil and thermal cases it is recommended to set EQUIL option 10 to 3, (FluidType is set to BUBBLE_POINT).
If EQUIL item 11 is set to 1, then in addition to the switch from GOC_PLUS_COMP to DATUM_PLUS_GOC, the
PressureAtGOC field in the Equilibrium node is set to DATUM_PRESSURE. This will cause the pressure at the
datum depth to be recalculated; however the datum depth itself will not be changed.

OPERATE, OPERATER
The use of OPERATE and OPERATER in the SOLUTION section is restricted to models using enumeration initialization.
When using equilibration initialization, the arrays on which these keywords would operate are generated within Intersect,
and are unavailable to the Migrator.

SOLUTION | SOLUTION keywords requiring special description | OPERATE, OPERATER

30
Intersect Migrator user guide

Eclipse 300 allows these operations on a temperature array called TEMP. However, the Migrator and Intersect do not
use a TEMP array. OPERATE and OPERATER should operate on TEMPI to modify initial temperatures. If TEMP is
specified, these keywords will automatically translate this to TEMPI.

PRESSURE, PRVD
The use of PRESSURE and PRVD is now allowed with equilibration initialization, as well as enumeration. In equilibration
runs, the values supplied will override those calculated by the initializer.

RPTRST
This keyword is used to control generation by Intersect of the 3D property reports in Eclipse restart file format and is also
used to control the automatic output of Intersect restart files.

3D property reports
The parameters of this keyword are used to control what properties are reported, where they are supported or available
in Intersect. The BASIC option is partially supported; all except BASIC=1 is supported. When the BASIC option is
used the mnemonics PRESSURE, SOIL, SWAT, SGAS, CONFAC, and CONKH are automatically added to the list of
reported properties.
Some properties are defined as aliases of other mnemonics, for example PCOW is an alias of PCOG. The effect of this is
that when either is requested all aliases for that property will also be output to the 3D property report.

Intersect restart files

Intersect restart files will be output automatically only for the option BASIC=3. If this option is used then Intersect restart
files are output at every requested reporting step, which can be varied using the FREQ option.
Automatic output of Intersect restart files can optionally be disabled whilst still using BASIC=3 by using the NORST
option. This option is primarily intended to stop excessive generation of many large model files from Petrel RE workflows.

RSW
Intersect only uses this for equilibration. It does not use it for enumeration. By contrast, in Eclipse 300 this keyword is
only used for enumeration. The Migrator uses the data in this keyword to define the initial aqueous concentration of
dissolved gas in each cell for Intersect's equilibration.

RTEMP, TEMPVD
Unless TEMPVD is provided, RTEMP is converted to a constant TemperatureDepthTable. These can only be used in
conjunction with the EQUIL keyword.
Further information: Behavior of temperature keywords.

SALT, SALTVD
For multi-component brines, the concentrations of the Eclipse components defined here are converted to concentrations
of Intersect components.
Further information: Multiple-component brine.

SOLUTION | SOLUTION keywords requiring special description | SALT, SALTVD

31
Intersect Migrator user guide

SOIL, SGAS, SWAT

The use of SOIL, SGAS and SWAT is now allowed with equilibration initialization, as well as enumeration. In
equilibration runs, the values supplied will override those calculated by the initializer.

TBLK, TVDP
Black oil Eclipse models may have separate tracer concentration properties defined for a fluid phase if that phase can
exist in both free and solution states. In this case the free state tracer concentration for a traced phase is used as the
tracer concentration for the appropriate component. The solution state tracer concentration is not used.
For example if the input data included a tracer T1 attached to the gas phase, with TBLKFT1 and TBLKST1 used to
define the concentration of the tracer in the free and solution states respectively, then TBLKFT1 would be migrated to
define the tracer concentrations for the "GAS" component. TBLKST1 would not be migrated.
Similarly, if gas phase tracer T2 was defined using depth tables TVDPFT2 and TVDPST2, then TVDPFT2 would be
migrated to a depth table for use with the "GAS" component, and TVDPST2 would be ignored.
Tracer concentrations and depth tables defined from compositional models are migrated directly.

XMF
The use of XMF is now allowed with equilibration initialization, as well as enumeration. In equilibration runs, the values
supplied will override those calculated by the initializer.

SOLUTION | SOLUTION keywords requiring special description | XMF

32
Intersect Migrator user guide

8
SUMMARY
If the SUMMARY keyword is present then Intersect will be configured to generate Eclipse format summary files. The
Migrator treats the SUMMARY mnemonics as keywords and reports whether they were migrated or not. In the following
tables mnemonics ending with * represent a family of keywords beginning with that mnemonic.

Note: Wildcard handling for SUMMARY keywords in the Migrator is not the same as Eclipse. Well list templates are not
supported in the SUMMARY section.

Further information:
• Fully supported SUMMARY keywords
• SUMMARY keywords requiring special description
• Multiple Selection Keywords
• Further information about wildcard handling can be found in the Reporting node reference in the Intersect User
Guide.

SUMMARY Fully supported keywords

AACMR AACMT AAQENTH AAQER AAQET AAQP AAQPD AAQR
AAQT AAQTD AAQTEMP ANCMR ANCMT ANQP ANQR ANQT
BAMF BAPI BBFORG BBFORO BBGAS BBOIL BBTFORG BBTFORO
BBWAT BCCN BCIP BCOILR BDENG BDENO BDENW BEMVIS
BENERGY BEPVIS BESALPLY BEWKR BEWV_POL BEWV_SAL BFFORG BFFORO
BFLOGI BFLOGJ BFLOGK BFLOOI BFLOOJ BFLOOK BFLOWI BFLOWJ
BFLOWK BFMISC BGDEN BGIP BGIPG BGIPL BGKR BGPC
BGPR BGSAT BGSHY BGSTRP BGTPD BGTRP BGVIS BHGAS
BHOIL BHWAT BJV BKRG BKRGO BKRGW BKRO BKROG
BKROW BKRW BKRWG BKRWO BMLSC BMLST BMWAT BNKR
BNSAT BODEN BOIP BOIPG BOIPL BOKR BOSAT BOVIS
BPCG BPCO BPCW BPERMMOD BPOLY BPORV BPORVMOD BPPCG

SUMMARY | SUMMARY Fully supported keywords

33
Intersect Migrator user guide

BPPCW BPPG BPPO BPPW BPR* BPRESSUR BPR_X BPSAT

BPVDP BREAC BRK BRPV BRS BRSSAT BRTM BRV
BRVSAT BSCN BSCN_X BSGAS BSIP BSOIL BSOILM BSOILR
BSPENGAS BSPENOIL BSPENWAT BSTEN BSWAT BTCN* BTCNFANI BTCNFCAT
BTCNFHEA BTEMP BTIPT* BTIPTSUR BVGAS BVMF BVOIL BVPOLY
BVWAT BWDEN BWIP BWKR BWPC BWPR BWSAT BWSHY
BWSMA BWVIS BXMF BYMF CCFR CCIC CCIR CCIT
CCPC CCPR CCPT CDBF CDFAC CGFR CGFRL CGIR
CGIRL CGIT CGITL CGLR CGLRL CGOR CGORL CGPI
CGPP CGPR CGPRL CGPT CGPTL CKFR CKFRL CKFT
CKFTL CLFR CLFRL CNFR CNIT CNPT COFR COFRL
COGR COGRL COIT COITL COPI COPP COPR COPRL
COPT COPTL CPR CPRL CSFR CSIC CSIR CSIT
CSPC CSPR CSPT CTFAC CTFR* CTFRSUR CTIC* CTIR*
CTIT* CTITANI CTITCAT CTITSUR CTPC* CTPR* CTPT* CTPTANI
CTPTCAT CTPTSUR CVFR CVFRL CVIR CVIRL CVPR CVPRL
CWCT CWCTL CWFR CWFRL CWGR CWGRL CWIR CWIRL
CWIT CWITL CWPI CWPP CWPR CWPRL CWPT CWPTL
CZMF DATE ELAPSED END ENDINC ENDSKIP FAMF FAPI
FAQER FAQET FAQR FAQT FCAD FCGMR FCGMT FCGR*
FCHMR FCIC FCIP FCIR FCIT FCMIR FCMIT FCMPR
FCMPT FCNMR FCOMR FCOMT FCOR* FCPC FCPR FCPT
FCWGIR FCWGIT FCWGPR FCWGPT FEGR FEGT FEIR FEIT
FEPR FEPT FEXGR FEXGT FFGR FFGT FGCR FGCT
FGDEN FGDN FGIP FGIPG FGIPL FGIPR FGIR FGIRH
FGIT FGITH FGLIR FGLIT FGLR FGLRH FGMR FGOR
FGORH FGPI FGPP FGPR FGPR1 FGPR2 FGPRA FGPRB
FGPRF FGPRH FGPRS FGPT FGPT1 FGPT2 FGPTA FGPTB
FGPTH FGSAT FGSR FGST FGVIR FGVIS FGVIT FGVPR
FGVPT FHLR FHLT FHMIR FHMIT FHMPR FHMPT FHSRC
FHTR FHTT FLPR FLPRH FLPT FLPTH FMCTG FMCTP
FMCTW FMWDR FMWIA FMWIG FMWIN FMWIP FMWIS FMWIT
FMWIU FMWIV FMWPA FMWPG FMWPL FMWPO FMWPP FMWPR
FMWPS FMWPT FMWPU FMWPV FMWWO FNIP FNIR FNIT
FNLPR FNLPRH FNLPT FNLPTH FNPR FNPT FNQR FNQT
FODEN FODN FOE FOGR FOGRH FOIP FOIPG FOIPL
FOIPR FOIR FOIRH FOIT FOITH FOMR FOPI FOPP
FOPR FOPR1 FOPR2 FOPRA FOPRB FOPRF FOPRH FOPRS
FOPT FOPT1 FOPT2 FOPTA FOPTB FOPTH FOSAT FOSRC

SUMMARY | SUMMARY Fully supported keywords

34
Intersect Migrator user guide

FOVIR FOVIS FOVIT FOVPR FOVPT FPPG FPPO FPPW

FPR FPRH FPRP FREAC FREAT FRGR FRGT FRPV
FRS FRTM FRV FSGR FSGT FSHRC FSIC FSIP
FSIR FSIT FSORC FSPC FSPR FSPT FSTPR FSTPT
FTADSUR FTIC* FTIPT* FTIPTSUR FTIR* FTIRANI FTIRCAT FTIRHEA
FTIRSUR FTIT* FTITANI FTITCAT FTITHEA FTITSUR FTLM* FTMF*
FTML* FTMR* FTMT* FTMV* FTPC* FTPR* FTPRANI FTPRCAT
FTPRHEA FTPRSUR FTPT* FTPTANI FTPTCAT FTPTHEA FTPTSUR FTQR*
FTTL* FTTV* FTVL* FTVM* FTVV* FVIR FVIT FVPR
FVPT FWCT FWCTH FWDEN FWGIR FWGIT FWGPR FWGPT
FWGR FWGRH FWIP FWIPR FWIR FWIRH FWIT FWITH
FWMR FWPI FWPP FWPR FWPRH FWPT FWPTH FWSAT
FWVIR FWVIS FWVIT FWVPR FWVPT FXMF FXMF* FYMF
FYMF* FZMF GALQ GAMF GAPI GCGMR GCGMT GCGR*
GCHMR GCIC GCIR GCIT GCMIR GCMIT GCMPR GCMPT
GCNMR GCOMR GCOMT GCOR* GCPC GCPR GCPT GCWGIR
GCWGIT GCWGPR GCWGPT GEFF GEGR GEGT GEIR GEIT
GEPR GEPT GEXGR GEXGT GFGR GFGT GG*PR GG*PT
GGCR GGCT GGDN GGIGR GGIR GGIRH GGIT GGITH
GGLIR GGLIT GGLR GGLRH GGMR GGOR GGORH GGPGR
GGPI GGPP GGPR GGPR1 GGPR2 GGPRA GGPRB GGPRF
GGPRH GGPRS GGPT GGPT1 GGPT2 GGPTA GGPTB GGPTH
GGSR GGST GGVIR GGVPR GHMIR GHMIT GHMPR GHMPT
GHSRC GLPR GLPRH GLPT GLPTH GMCTG GMCTP GMCTW
GMWDR GMWIA GMWIG GMWIN GMWIP GMWIS GMWIT GMWIU
GMWIV GMWPA GMWPG GMWPL GMWPO GMWPP GMWPR GMWPS
GMWPT GMWPU GMWPV GMWWO GNIR GNIT GNLPR GNLPRH
GNLPT GNLPTH GNPR GNPT GO*PR GO*PT GODN GOGR
GOGRH GOIR GOIRH GOIT GOITH GOMR GOPGR GOPI
GOPP GOPR GOPR1 GOPR2 GOPRA GOPRB GOPRF GOPRH
GOPRS GOPT GOPT1 GOPT2 GOPTA GOPTB GOPTH GOSRC
GRGR GRGT GSGR GSGT GSHRC GSIC GSIR GSIT
GSORC GSPC GSPR GSPT GSTPR GSTPT GTIC* GTIR*
GTIRANI GTIRCAT GTIRHEA GTIRSUR GTIT* GTITANI GTITCAT GTITHEA
GTITSUR GTLM* GTMF* GTML* GTMR* GTMT* GTMV* GTPC*
GTPR* GTPRANI GTPRCAT GTPRHEA GTPRSUR GTPT* GTPTANI GTPTCAT
GTPTHEA GTPTSUR GTQR* GTTL* GTTV* GTVL* GTVM* GTVV*
GVIR GVIT GVPR GVPT GWCT GWCTH GWGIR GWGIT
GWGPR GWGPT GWGR GWGRH GWIGR GWIR GWIRH GWIT

SUMMARY | SUMMARY Fully supported keywords

35
Intersect Migrator user guide

GWITH GWMR GWPGR GWPI GWPP GWPR GWPRH GWPT

GWPTH GWVIR GXMF GXMF* GYMF GYMF* GZMF INCLUDE
LBAPI LBBGAS LBBOIL LBBWAT LBCCN LBCIP LBDENG LBDENO
LBDENW LBENERGY LBFMISC LBGDEN LBGIP LBGIPG LBGIPL LBGKR
LBGPC LBGPR LBGSAT LBGTPD LBGTRP LBGVIS LBHGAS LBHOIL
LBHWAT LBJV LBKRG LBKRGO LBKRGW LBKRO LBKROG LBKROW
LBKRW LBKRWG LBKRWO LBMLSC LBMLST LBMWAT LBNKR LBNSAT
LBODEN LBOIP LBOIPG LBOIPL LBOKR LBOSAT LBOVIS LBPCG
LBPCO LBPCW LBPORV LBPPG LBPPO LBPPW LBPR LBPRESSU
LBPSAT LBPVDP LBRPV LBRS LBRSSAT LBRV LBRVSAT LBSCN
LBSGAS LBSIP LBSOIL LBSPENGA LBSPENOI LBSPENWA LBSTEN LBSWAT
LBTCNFHE LBTEMP LBTIPT* LBTIPTSU LBVGAS LBVMF LBVOIL LBVWAT
LBWDEN LBWIP LBWKR LBWPC LBWPR LBWSAT LBWVIS LBXMF
LBYMF LCCFR LCCIT LCCPT LCDBF LCGFR LCGFRL LCGIR
LCGIT LCGITL LCGLR LCGLRL LCGOR LCGORL LCGPI LCGPP
LCGPR LCGPRL LCGPT LCGPTL LCKFRL LCKFTL LCLFR LCLFRL
LCNFR LCNIT LCNPT LCOFR LCOFRL LCOGR LCOGRL LCOIT
LCOITL LCOPI LCOPP LCOPR LCOPRL LCOPT LCOPTL LCPR
LCSFR LCSIT LCSPT LCTFAC LCTFR* LCTFRSUR LCTIT* LCTITSUR
LCTPT* LCTPTSUR LCWCT LCWCTL LCWFR LCWFRL LCWGR LCWGRL
LCWIR LCWIRL LCWIT LCWITL LCWPI LCWPP LCWPR LCWPRL
LCWPT LCWPTL MEMORYTS MLINEARS MSUMLINS MSUMNEWT NAIMFRAC NBAKFL
NEWTFL NEWTON NLINEARS NNUMFL NNUMST NTS RCAD* RCIP*
REFR* REFR+* REFR-* REFT* REFT+* REFT-* RGDEN* RGFR*
RGFR+* RGFR-* RGFT* RGFT+* RGFT-* RGIP* RGIPG* RGIPL*
RGIR* RGIT* RGPR* RGPT* RGSAT* RGVIS* RKFR RKFR+
RKFR- RKFT RKFT+ RKFT- RNFT* RNLFR* RNLFR+* RNLFR-*
RNLFT* RNLFT+* RNLFT-* RNIP* RODEN* ROE* ROFR* ROFR+*
ROFR-* ROFT* ROFT+* ROFT-* ROIP* ROIPG* ROIPL* ROIR*
ROIT* ROPR* ROPT* ROSAT* ROVIS* RPPG* RPPO* RPPW*
RPR* RPRH* RPRP* RPTONLY RRPV* RRS* RRTM* RRV*
RSFT* RSIP* RTADSUR RTIPT* RTIPTSUR RUNSUM RWDEN* RWFR*
RWFR+* RWFR-* RWFT* RWFT+* RWFT-* RWIP* RWIR* RWIT*
RWPR* RWPT* RWSAT* RWVIS* SAPI SCCN SCFR SCFR*
SCWGFR SDENM SENE SFOPN SGDEN SGFR SGFRF SGFRS
SGFV SGHF SGLPP SGLVD SGOR SGVIS SHFR SKIP
SKIP100 SKIP300 SMDEN SMVIS SODEN SOFR SOFRF SOFRS
SOFV SOGR SOHF SOVIS SOWPP SOWVD SPR SPRD
SPRDA SPRDF SPRDH SPSAT SSCN SSFR SSQU SSTR

SUMMARY | SUMMARY Fully supported keywords

36
Intersect Migrator user guide

STEM STEPTYPE STFC* STFR* SUMMARY SWCT SWDEN SWFR

SWFV SWGR SWHF SWVIS TCPU TCPUDAY TCPUTS TIMESTEP
WALQ WAMF WAPI WBGLR WBHP WBHPH WBP WCGMR
WCGMT WCGR* WCHMR WCIC WCIR WCIT WCMIR WCMIT
WCMPR WCMPT WCNMR WCOMR WCOMT WCOR* WCPC WCPR
WCPT WCWGIR WCWGIT WCWGPR WCWGPT WEFF WEFFG WEIR
WEIT WEPR WEPT WG*PR WG*PT WGDN WGFRL WGIGR
WGIP WGIR WGIRH WGIRL WGIRT WGIT WGITH WGITL
WGLIR WGLIT WGLR WGLRH WGLRL WGMR WGOR WGORH
WGORL WGPGR WGPI WGPP WGPR WGPR1 WGPR2 WGPRA
WGPRB WGPRF WGPRH WGPRL WGPRS WGPRT WGPT WGPT1
WGPT2 WGPTA WGPTB WGPTH WGPTL WGVIR WGVPR WHMIR
WHMIT WHMPR WHMPT WHTR WHTT WLFRL WLPR WLPRH
WLPRT WLPT WLPTH WMCON WMCTL WNIR WNIT WNLPR
WNLPRH WNLPRT WNLPT WNLPTH WNPR WNPT WO*PR WO*PT
WODN WOFRL WOGLR WOGR WOGRH WOGRL WOIR WOIRH
WOIRT WOIT WOITH WOITL WOMR WOPGR WOPI WOPP
WOPR WOPR1 WOPR2 WOPRA WOPRB WOPRF WOPRH WOPRL
WOPRS WOPRT WOPT WOPT1 WOPT2 WOPTA WOPTB WOPTH
WOPTL WPI1 WPIG WPIL WPIO WPIW WPOFF WSIC
WSIR WSIT WSPC WSPR WSPT WSQU WSTAT WSTPR
WSTPT WTEMP WTHP WTHPH WTHT WTIC* WTIR* WTIRANI
WTIRCAT WTIRHEA WTIRSUR WTIT* WTITANI WTITCAT WTITHEA WTITSUR
WTLM* WTMF* WTML* WTMR* WTMT* WTMV* WTOFF WTPC*
WTPR* WTPRANI WTPRCAT WTPRHEA WTPRSUR WTPT* WTPTANI WTPTCAT
WTPTHEA WTPTSUR WTQR* WTTL* WTTV* WTVL* WTVM* WTVV*
WVFRL WVIR WVIRL WVIRT WVIT WVPR WVPRL WVPRT
WVPT WWCT WWCTH WWCTL WWFRL WWGIR WWGIT WWGPR
WWGPRH WWGPT WWGR WWGRH WWGRL WWIGR WWIP WWIR
WWIRH WWIRL WWIRT WWIT WWITH WWITL WWMR WWPGR
WWPI WWPP WWPR WWPRH WWPRL WWPRT WWPT WWPTH
WWPTL WWVIR WXMF WXMF* WYMF WYMF* WZMF

SUMMARY keywords requiring special description

The following SUMMARY keywords have additional restrictions.

SUMMARY | SUMMARY keywords requiring special description

37
Intersect Migrator user guide

Note: Reference temperatures are processed differently in Intersect and Eclipse. This means that report properties (such
as energy and enthalpy) depending on reference temperatures are different from those reported by Eclipse 300. There is
currently no straightforward workaround.

FSGR
FSGR or FGSR or FGST or FSGT: the mnemonics FSGR and FGSR are aliases of each other. If the mnemonic for
example FSGR and its alias, FGSR, are present in the data set they will both be reported as fully migrated, but only the
last one encountered in the dataset will actually be written out to the results. The same is true for FGST and FSGT.

STEPTYPE
The STEPTYPE mnemonic is represented by the Intersect property identifier TIMESTEP_CONTROL_MODE. This
outputs an integer representing the reason for selecting the time step length. The codes output are designed to match
the Eclipse codes as much as possible but there are still some differences. The numeric codes output by Intersect and
their descriptions are listed in table 8.1.

Numeric code Code Description

1 Init The initial time step for a simulation run.
2 TTE Time step selected on time truncation error criteria.
3 MDF The maximum decrease factor between time steps.
4 MIF The maximum increase factor between time steps.
5 Min The minimum allowed time step.
6 Max The maximum allowed time step.
7 Rep Time step required to synchronize with a report date.
8 HRep Time step required to get half way to a report date.
9 Chop Time step chopped due to previous convergence problems.
16 SCT Time step selected on solution change criteria.
31 CFL Time step selected to maintain CFL stability.
32 Mn The time step specified was selected but was limited by minimum time step.
37 Mx The time step specified was selected but was limited by maximum time step.
Table 8.1: TIMESTEP_CONTROL_MODE codes and their descriptions

WBP
Well block average pressure is calculated differently in Intersect from Eclipse.
Further information: Compatibility with Eclipse in the Intersect Technical Description.

WPI
The mnemonic WPI is handled by treating it as the well productivity option for all phases rather than the current phase
that might change throughout the simulation. It is therefore equivalent to WPIO + WPIG + WPIW.

SUMMARY | SUMMARY keywords requiring special description | WPI

38
Intersect Migrator user guide

WTEMP
Intersect does not report a well temperature for wells which are shut (that is wells which have no open connections with
the reservoir). This is different to the behavior of Eclipse 300 which reports the well temperature as the field average
temperature if the well is shut. The Intersect behavior is considered to be more consistent with the reporting of well
bottom hole pressures where neither Intersect nor Eclipse report a value if the well is shut.

Ion rates
In Intersect, if the brine electroneutrality condition is active, reporting of ion production rates via the mnemonics
FTPRANI, FTPRCAT, GTPRANI, GTPRCAT, WTPRANI and WTPRCAT; and injection rates using the mnemonics
FTIRANI, FTIRCAT, GTIRANI, GTIRCAT, WTIRANI and WTIRCAT will use the electroneutrality condition to add
the rate of the untracked monovalent anion. This means that the anion rate will be equal to the cation rate thereby
satisfying the electroneutrality condition. This is different from Eclipse which does not include the untracked component.
Further information: Electroneutrality condition in the Intersect Technical Description.

Guide rates
The guide rate values for well and group production and injection (mnemonics: WOPGR, WGPGR, WWPGR, GOPGR,
GGPGR, GWPGR, WGIGR, WWIGR, GGIGR or GWIGR) are only reported from Intersect for the nominated phase of the
guide rate.
This differs from Eclipse, which reports guide rate values regardless of the nominated phase of the guide rate. Guide rate
values for groups are only reported from Intersect if the group is required to produce/inject a particular proportion of a
rate target applied to a superior group. When a group contains only one well, no flow rate apportioning is required and
hence guide rate values will not be reported.
Further information: GUIDERAT item 2 in the Eclipse Reference Manual

Potential rates
The potential rate values for well, group and field production and injection (mnemonics: WOPP, WGPP, WWPP, WOIP,
WGIP, WWIP, GOPP, GGPP, GWPP, GOIP, GGIP, GWIP, FOPP, FGPP, FWPP, FOIP, FGIP, or FWIP) are reported
from Intersect including values calculated for closed and surface shut-in wells (called shut and stopped wells respectively
in Eclipse).
This differs from Eclipse, which reports these potentials excluding shut and stopped wells. Note that Eclipse also has
separate potential rate reports that include values calculated on shut and stopped wells (mnemonics WOPP2, WGPP2,
WWPP2, WWIP2, WGIP2, WWIP2, GOPP2, GGPP2, GWPP2, GWIP2, GGIP2, GWIP2, FOPP2, FGPP2, FWPP2,
FWIP2, FGIP2, or FWIP2).

SUMMARY | SUMMARY keywords requiring special description | Potential rates

39
Intersect Migrator user guide

9
SCHEDULE
The Migrator converts SCHEDULE keywords into either Intersect well model or field management commands. Only a
core subset of SCHEDULE keywords and parameters are supported. The details are given in the migration report
generated for the model. Keywords that create wells, completions, connections, separators and hydraulic tables are
implemented using the Intersect well model, whereas keywords that set constraints or targets on wells and groups are
generally handled by Intersect field management.
Keywords are considered partially supported where the Migrator cannot convert all parameters available in the Eclipse
keyword. The unsupported items for partially supported keywords are also listed. Unsupported keywords are not
included. For detailed information on the unsupported items in keywords see the Eclipse Reference Manual.
Further information:
• Fully supported SCHEDULE keywords
• Partially supported SCHEDULE keywords
• SCHEDULE keywords requiring special description
• Restrictions on well and group and node names.
• Multiple selection keywords

SCHEDULE Fully supported keywords

AQUCT AQUFETP AQUFLUX AUTOSAVE BOX COMPINJK COMPKRI COMPKRIL
COMPLMPL COMPLUMP COMPMBIL COMPMOBI COMPORD COMPSEGL COMPSEGS DATES
DRSDT DRVDT END ENDACTIO ENDBOX ENDFIN ENDINC ENDSKIP
FBHPDEF GADVANCE GINJGAS GLIFTOPT GPTABLE GPTABLE3 GPTABLEN GRUPTREE
GSEPCOND HEATER HEATERL INCLUDE LIFTOPT MULTFLT MULTREGT MULTSIGV
MULTX MULTX- MULTY MULTY- MULTZ MULTZ- NOSIM NUPCOL
OUTSOL PSEUPRES QDRILL REFINE RPTONLY RPTRST SAVE SCHEDULE
SEPVALS SKIP SKIP100 SKIP300 TIME TSTEP VAPPARS VFPINJ
VFPPROD WALQCALC WAVAILIM WCONINJH WDFAC WDFACCOR WECONINJ WELDRAW
WELLOPTS WELLSTRE WELLWAG WELPI WHTEMP WINJGAS WINJMIX WINJORD
WINJTEMP WINJWAT WLIFT WLIFTOPT WLIST WPAVE WPAVEDEP WPIMULT
WPIMULTL WREGROUP WRFTPLT WSALT WSEGAICD WSEGDFMD WSEGDFPA WSEGFMOD

SCHEDULE | SCHEDULE Fully supported keywords

40
Intersect Migrator user guide

WSEGHEAT WSEGITER WSEGLINK WSEGSICD WSEGTABL WSEGVALV WSEPCOND WSOLVENT

WTAKEGAS WVFPDP WWPAVE

SCHEDULE Partially supported keywords

Keyword Unsupported Items, or Unsupported Choices (in brackets)
ACTION Item: 2 (FCNMR, FTPC, FTPR)
ACTIONW Items: 3 (WCNMR, WTPC, WTPR, WXMF_NN, WYMF_NN, WZMF_NN), 7
ACTIONX Only a limited version of ACTIONX is supported.
CECON Items: 9 (PLUG), 10 (NO), 13
COMPDAT Item: 13 (FX, FY)
COMPDATL Item: 14 (FX, FY)
COMPDATM Item: 14 (FX, FY)
COMPRP Items: 7, 8, 9, 10
COMPRPL Items: 8, 9, 10, 11
DRILPRI Items: 10, 11
GCONINJE Items: 2 (OIL), 3 (WGRA), 10 (NETV, VOID), 13
GCONPRI Items: 11, 14, 15, 16, 17
GCONPROD Items: 2 (CRAT, CVAL, FLD, PBGS, PBWS, PRBL), 7 (PLUG), 10 (COMB,
CVAL, FORM1, FORM2, FORM3, FORM4, FORM5, FORM6, FORM7, FORM8, FORM9,
INJV), 11 (PLUG), 12 (PLUG), 13 (PLUG), 15, 17, 18, 19, 20, 21
GCONSALE Items: 3, 4, 5
GCONSUMP Item: 4
GCONTOL Items: 3, 4
GECON Items: 7 (PLUG), 9
GEFAC Item: 3
GPMAINT Item: 2 (OINJ, OINS, WGIN)
GRUPFUEL Item: 4
GRUPLIM Items: 7 (PLUG), 9
GRUPSALE Item: 4
GRUPTARG Item: 2 (CRAT, CVAL, PBGS, PBWS, PRBL)
GSATCOMP Item: 4
GSATINJE Items: 4, 5
GSATPROD Items: 5, 7
GUIDERAT Items: 2 (COMB), 9, 11, 12
PICOND Items: 5, 6, 10, 11, 12
PRIORITY Item: 1
RPTSCHED Only WELLS mnemonic is supported. The output of WELLS mnemonic may also differ from Eclipse.
SEPCOND Items: 11, 12

SCHEDULE | SCHEDULE Partially supported keywords

41
Intersect Migrator user guide

Keyword Unsupported Items, or Unsupported Choices (in brackets)

WBHGLR Items: 5 (COMB), 7 (PLUG), 8
WBOREVOL Item: 3
WCONHIST Item: 3 (CRAT)
WCONINJE Items: 2 (MULTI), 10, 12, 13, 14
WCONPROD Items: 3 (CVAL), 18, 19
WCUTBACK Items: 7 (COMB, WGAS), 14
WCYCLE Items: 4, 5
WDRILPRI Item: 3
WDRILTIM Items: 3 (NO), 4
WECON Items: 7 (PLUG), 12 (+CON, CON, LAST, PLUG, WELL), 15, 16
WEFAC Item: 3
WELCNTL Item: 2 (CRAT, CVAL, REIN, WGRA)
WELLLIM Items: 7 (PLUG), 12 (+CON, CON, LAST, PLUG, WELL), 15, 16
WELOPEN Item: 2 (POPN)
WELOPENL Item: 3 (POPN)
WELSEGS Record 1 - Items: 8, 9
Record 2 - Items: 11, 12
WELSPECL Items: 4, 5, 9 (R-G), 17
WELSPECS Items: 3, 4, 8 (R-G), 16
WELTARG Item: 2 (CRAT, CVAL, GUID, REIN, WGRA)
WGRUPCON Item: 4 (COMB, CVAL, WGA)
WHISTCTL Item: 2
WPICOND Items: 7, 8, 12, 13, 14
WTADD Items: 2 (CRAT, GUID, CVAL), 4
WTEST Items: 3 (C, D), 5
WTMULT Items: 2 (CRAT, GUID, CVAL), 4
WTRACER Items: 4, 5
WVFPEXP Item: 4

SCHEDULE keywords requiring special description

The following SCHEDULE keywords have additional restrictions.

ACTION keywords
Only a limited version of ACTIONX is supported, that is:
• All wells, completions, groups and field quantities listed in Field, group, well and connection properties are supported
in the triggering condition of ACTIONX. Additionally, region properties listed in Region and grid cell properties are
supported.

SCHEDULE | SCHEDULE keywords requiring special description | ACTION keywords

42
Intersect Migrator user guide

• Keywords supported inside ACTION* block are: WELSPECS (Item 5 and 9), WELSPECL (Item 6 and 10),
WELOPEN, WELOPENL, WCONPROD, WCONINJE, WECON, WECONINJE, WEFAC, WELDRAW, WELLSTRE,
WGRUPCON, WINJTEMP, WPIMULT, WSOLVENT, WTAKEGAS, WTEST, WELTARG, GCONPROD, GCONINJE,
GECON, WINJGAS, GINJGAS, GRUPFUEL, GRUPSALE, GCONSALE, GCONSUMP, GADVANCE, GEFAC,
GPMAINT, GUIDERAT, QDRILL, DRILPRI, WDRILPRI, WDRILTIM.
• Time stepping keywords like TSTEP, DATES, DATE and END keywords are not allowed inside an ACTION* block.
• "Increment to triggering condition" is not supported.
• The use of nested ACTION* keywords is not supported.
• Wildcards in well or group names in the triggering condition are not supported.
• Comments in the ACTIONX triggering record are known to cause errors. It is recommended that the comments are
removed and that the Boolean expressions are complete.
• ACTION* keywords should generally be defined at an earlier timestep with an expression that determines when it
should be executed. Defining the ACTION* keyword for the same time as it will be executed, results in ACTION*
being ignored. In this case, the contents inside the ACTION* keyword can be specified directly without the
containing ACTION*/ENDACTIO keywords.
If the Migrator has problems with migrating the defaulted parameters within the ACTION block then try explicitly setting
all keyword items. You may need to do this when a keyword is used within an ACTION* block that has already been
used in the dataset.

AQUCT, AQUFETP, AQUFLUX

Analytical aquifer can only be updated in the SCHEDULE section if they have previously been defined in the GRID or
SOLUTION sections (depending on the type of aquifer).

CECON
The CECON keyword set up limits on connections, however Intersect works on completions. The simple case where each
connection is in its own completion can be fully supported. However, if the COMPLUMP keyword has been used to lump
several connections into the same completion there can be a mismatch. If a limit is set on a connection but that
connection is in a completion with another connection that does not have the same limit, then the connection cannot be
migrated. In other words, all connections in a completion must have the same limits in order for the completion to be
migrated.

Completion index usage within keywords

In Eclipse, the default completion indices ignore any connections to inactive cells, while in the Migrator and Intersect, the
default completion indices include connections to inactive cells. For this reason, care should be taken when using the
completion index within keywords (for example WPIMULT items 6 and 7) as they may behave differently in the two
simulators. You should either use the COMPLUMP keyword to explicitly set the completion indices for consistency, or
(where possible) use an alternative mechanism for specifying the required data (for example WPIMULT items 3, 4 and 5
which specify the I, J and K location of the connecting grid block and is guaranteed to have the same meaning in Eclipse
and Intersect).

COMPDAT, COMPDATL
Positive values of COMPDAT item 12 are not supported. Instead, use the WDFAC keyword. The same applies for
COMPDATL item 13.

SCHEDULE | SCHEDULE keywords requiring special description | COMPDAT, COMPDATL

43
Intersect Migrator user guide

COMPSEGS, COMPSEGL
Negative or zero values for COMPSEGS item 9 and COMPSEGL item 10 are accepted as valid connection depths.

DATES
Report dates should always be in increasing date order in the dataset.

FBHPDEF
The migration of FBHPDEF is handled differently depending upon whether or not it is the first instance of the keyword
with the deck. This impacts the handling of the BOTTOM_HOLE_PRESSURE constraint for the well control keywords;
WCONPROD, WCONINJE, WCONHIST and WCONINJH.
For the first instance of FBHPDEF, a BOTTOM_HOLE_PRESSURE constraint is not added for each of the wells. The
wells handled by the subsequent well control keywords are tagged to use the corresponding default BHP constraint
defined for field management.
For subsequent instances of FBHPDEF, a BOTTOM_HOLE_PRESSURE constraint is added for each of the wells
handled by the subsequent well control keywords. The corresponding default BHP constraint defined for field
management is ignored.

GCONINJE
Item 6, Reinjection fraction target, for gas is applied to the gas production rate of the named group and includes
allowances for fuel, sales and advance gas. In the case where sales or fuel are subtracted before reinjection, or advance
gas is supplied, results may differ from Eclipse, if the reinjection constraint becomes limiting.

GCONPRI
The Migrator uses the following ratios to determine worst offending well or connection when procedure for exceeding
maximum rate limit is used:
• OIL_GAS_RATIO (or OIL_WATER_RATIO if gas is not present in the run) when oil rate limit is exceeded.
• WATER_OIL_RATIO (or WATER_GAS_RATIO if oil is not present in the run) when water rate limit is exceeded.
• GAS_OIL_RATIO (or GAS_WATER_RATIO if oil is not present in the run) when gas rate limit is exceeded.
• LIQUID_OIL_RATIO (or LIQUID_GAS_RATIO if oil is not present in the run) when liquid rate limit is exceeded.
The Migrator ignores the WELSPECS item 6 'preferred phase' setting to determine the above ratios.

GCONPROD
The Migrator uses the following ratios to determine worst offending well or connection when procedure for exceeding
maximum rate limit is used in GCONPROD item 7:
• OIL_GAS_RATIO (or OIL_WATER_RATIO if gas is not present in the run) when production rate control mode in
item 2 is ORAT.
• WATER_OIL_RATIO (or WATER_GAS_RATIO if oil is not present in the run) when production rate control mode in
item 2 is WRAT.
• GAS_OIL_RATIO (or GAS_WATER_RATIO if oil is not present in the run) when production rate control mode in
item 2 is GRAT.
• LIQUID_OIL_RATIO (or LIQUID_GAS_RATIO if oil is not present in the run) when production rate control
mode in item 2 is LRAT.

SCHEDULE | SCHEDULE keywords requiring special description | GCONPROD

44
Intersect Migrator user guide

The Migrator ignores the WELSPECS item 6 'preferred phase' setting to determine the above ratios.

GCONSALE
In Intersect the reinjection fraction is taken to be a constant, this differs from Eclipse 100 where the target reinjection
fraction is dynamically recalculated to meet the GCONSALE target. Also, note that the gas reinjection formula differs from
that used in Eclipse 100.
Further information: Refer to the treatment of reinjection fraction in the GCONINJE keyword, .

GCONTOL
Items 1 and 2 of this keyword are supported. When GCONTOL is used, the Intersect field management solution scheme
is changed from the ITERATIVELY_LAGGED method to ADAPTIVE_ITERATIVELY_LAGGED. In this method if a group
target is not met and there is sufficient potential to meet the target, Intersect field management logic is executed until the
target group rates are met within the tolerance specified. However Intersect well model may perform flash calculations at
the converged time step and slight changes to the well rates could occur from the last Newton iteration, causing the
groups rates to drift from their targets, hence field management may not honor the targets exactly in this cases. This
differs from Eclipse solution, hence differences in results may be seen.

GECON
When item 8, the end run flag, is set to 'YES' the run will stop at the next simulation time step, rather than at the next
report step.

GINJGAS, WINJGAS
Whenever a well or group production stream is specified, the Migrator obtains a separator from Intersect by looking up
the defined well, or the first production well in the group, and instructs Field Management to use this. A message is
issued as to which separator is being used. This is different to Eclipse 300 behavior that allows wells in a Group to use
different separators.
Separator stage zero is the only stage currently supported for injection streams that is the vapor from the whole
separator (Item 5 = 0). When any other stage is specified, the Migrator uses stage 0 instead, and issues a warning.

GPMAINT
The Migrator can support both Eclipse 100 and Eclipse 300 usage of GPMAINT, allowing PMANUM, FIPNUM, user
defined FIP region families and the entire field to be used when defining pressure maintenance regions.
In some circumstances, as Eclipse 100 and Eclipse 300 interpret GPMAINT differently, the Migrator also needs to check
the TABDIMS keyword item 14 to determine which behavior to implement. Use the following guide to control the
Migrator's output.
To use the entire field for pressure maintenance:
• set item 3 to 0
To use a user defined FIP region for pressure maintenance:
• set item 3 to a valid FIP region number (greater than 0) or default (will use FIP region 1), and
• set item 4 to the name of the region family. It must not be left defaulted or blank.
To use a FIPNUM region for pressure maintenance:
• set item 4 to be defaulted or blank, and
• set item 3 to a valid FIPNUM region number (greater than 0), and

SCHEDULE | SCHEDULE keywords requiring special description | GPMAINT

45
Intersect Migrator user guide

• set TABDIMS item 14 to 0 or default.

To use a PMANUM region for pressure maintenance:
• set item 4 to be defaulted or blank, and
• either set item 3 to default (will use PMANUM region 1) or (set item 3 to a valid PMANUM region number and set
TABDIMS item 14 to the maximum number of PMANUM regions)

HEATER
Intersect models heaters differently from Eclipse 300, such that constraints placed on individual heater connections in
Eclipse 300 are used to form constraints on the overall heater for Intersect. For heaters connected to multiple cells, this
will lead to different results between Eclipse 300 and Intersect. A workaround for this is to create separate heaters for
each connection in the Eclipse 300 dataset.
Mode 2: Energy density dependent injection rate is not supported. If items 5 and 6 are specified, item 7 must be also
specified.

Drilling keywords
The drilling keywords, QDRILL and WDRILPRI, specify balancing drilling queues with sequential and priority ordering
respectively. These are implicit algorithms, based on the group control constraints and hierarchy, for determining when to
drill and which well(s) to drill. If a group cannot meet its target, the first suitable well in the queue is scheduled for drilling.
In Eclipse 100, groups are solved from the bottom up. In Eclipse 300, a more complex algorithm that performs multiple
passes through the group hierarchy is used to determine which well to drill. The field management implementation
follows the Eclipse 300 algorithm. This can lead to differences in the results between Eclipse 100 and Intersect.
QDRILL in WDRILTIM item 1 is not supported.

Note: Wells in any of the drilling queues will be treated as closed during drilling, that is WDRILTIM item 3 being set to
"NO" is not supported. If WDRILTIM item 3 is set to "YES", Eclipse will open the well with a zero efficiency factor
while it is being drilled; Field Management will not open the well until it is drilled. The results will be identical in terms of
total production, but the well will appear to be producing from an earlier time in an equivalent Eclipse run, on a well rate
plot. (In Field Management, if the drilling end time does not coincide with a time step, it is sometimes not possible to
insert the end drill time into the simulation time line. For instance, this will happen when the end drill time is within the
current time step and the solution algorithm is already carrying out the nonlinear iterations of the current time step. In this
situation Field Management will open the well at the beginning of the time step in which it is drilled, but with a temporary
modification to the well efficiency factor to reflect the fraction of the current time step that the well is actually open after it
has finished drilling).

As the Eclipse rig keyword GRUPRIG is not yet supported, then only one well can be drilled by the drilling queues at a
time. So while a well is being drilled by a drilling queue, no other wells can be drilled in the same, or any other, drilling
queue.

RPTRST
The restrictions on RPTRST in the SOLUTION section also apply here.
Further information: RPTRST.

SAVE
The SAVE keyword in the SCHEDULE section overrides the settings used in RPTRST and will cause Intersect restart
files to be generated.

SCHEDULE | SCHEDULE keywords requiring special description | SAVE

46
Intersect Migrator user guide

WCONHIST, WCONINJH
Wet gas production rates are not migrated; hence these values will not be reported in any output files. To switch a well
from history to prediction use WCONPROD or WCONINJE, otherwise historical constraints will not be removed.

WCONINJE, GCONINJE
No validation is performed to confirm all wells for which WCONINJE item 4 was specified as GRUP are actually
subordinate to groups for which group control allocation was specified with keyword GCONINJE. If such wells are
opened, they will flow (inject) according to any other constraints that may be specified on them, including, for gas
injectors, the surface volume availability of their assigned injection stream.

WCONPROD
The implementation of steam trap is different between Intersect and Eclipse 300. Intersect's results should be very
similar to those produced by Eclipse 300 with Intersect's results having generally fewer BHP oscillations than is the case
with Eclipse 300. Intersect always honors steam trap constraints whereas Eclipse 300 ignores them if this would result in
the well injecting.
Note: The default for Item 9 (BHP target) uses the Eclipse 300 value of 100 atma (=1470 psi). This differs from the
Eclipse 100 default of atmospheric pressure.

WCONPROD, GCONPROD
No validation is performed to confirm all wells for which WCONPROD item 3 was specified as GRUP are actually
subordinate to groups for which group control allocation was specified with keyword GCONPROD. If such wells are
opened, they will flow (produce) according to any other constraints that may be specified on them.

WCYCLE
In Eclipse 100 if a well is under cyclic well control and is closed for any other reason (for example due to exceeding an
economic limit), it remains closed until an action is taken to reopen it. Once it reopens it will resume cycling. In Intersect
wells that have been closed for any other reason are reopened when the next on period occurs.
In Eclipse 100 if a WCYCLE keyword is redefined for a specific well it will immediately stop its current cycle and then start
cycling using the redefined cyclic controls. In Intersect the well will finish its current cycle before proceeding to the next
cycle using the redefined cyclic controls.

WEFAC
If an efficiency factor is applied to a well that does not have any control data, the Migrator gives an error and stops.
Control data is normally provided by the WCONPROD, WCONHIST and WCONINJE keywords. To resolve this try moving
the WEFAC keyword to after the appropriate control data keyword. This behavior is different to Eclipse 300.
WEFAC item 3 (IncludeFactorInNetworkCalculations) is not supported. For models coupling to ENS, you can manually
set its behavior in Intersect by using the RateTypePassed field in the NetworkWellBoundary node.

WELLWAG
In Eclipse 300 if a WELLWAG keyword is redefined for a specific well it immediately stops its current cycle and then starts
cycling using the redefined cyclic controls. In Intersect the well will finish its current cycle before proceeding to the next
cycle using the redefined cyclic controls.

SCHEDULE | SCHEDULE keywords requiring special description | WELLWAG

47
Intersect Migrator user guide

WELOPEN, WELOPENL
The well and completion status part of WELOPEN / WELOPENL is handled by field management, and the connection
status part is handled by Intersect well model. As a result, the Migrator does not support i, j, k locations of connections
and completions range in one WELOPEN / WELOPENL record if WELOPEN / WELOPENL is nested within ACTION
keywords. Ensure that the connection locations and completions numbers specified in these keywords are valid.

WELSEGS
The Migrator always uses default of 0.0 for record 1 item 3 and default of 1.0E-5 for record 1 item 4 when these items
are defaulted. Unlike E300, it does not retain the values of item 3 or 4, if defaulted, from previous occurrences of
WELSEGS.

WELSPECS, WELSPECL
If the well model closes a well because it cannot flow (for example, if the reservoir pressure is below the minimum BHP
limit for a producer), it will shut the well along with all its connections irrespective of the setting of WELSPECS item 9 or
WELSPECL item 10 (instructions for automatic shut-in). However WELSPECS item 9 and WELSPECL item 10 is honored
by Intersect field management when it decides to close a well.
WELSPECS item 11 and WELSPECL Item 12: the wellbore fluid model must be assigned to at least one active grid cell.
This is different behavior to Eclipse.

WELTARG
WELTARG can only be used to reset a target or limit for wells whose control data has been specified earlier in the run
using the WCONPROD keyword. It cannot be used for wells whose control data has not been specified. This is because
the Migrator must know which constraint (production or injection) is being reset using WELTARG. The Migrator also
supports migration of WELTARG item-(3) when left defaulted, which results in the use of the flowing value at the current
step as the constraint.

WINJMIX
Intersect expects that the sum of the fractions of the fluid in the mixture to be unity. Eclipse and the Migrator instead
normalizes the fractions to 1.0 for computing the total composition of the fluid.

WINJTEMP
Enthalpy is a property of the source of a fluid stream in Intersect field management. If the enthalpy of injected fluid is
changed for a well using WINJTEMP keyword then the same enthalpy is used by all the wells and groups that share the
same source of injection stream. As a result, WINJTEMP should be carefully used with WINJGAS, GINJGAS,
GADVANCE and GCONSUMP keywords.
Eclipse 300 calculates injection temperatures at field reference pressure where as Intersect calculates injection
temperature at BHP. This causes difference when reporting well temperature.

WPAVE, WWPAVE, WPAVEDEP

Well block average pressure is calculated differently in Intersect from Eclipse.
Further information: Compatibility with Eclipse in the Intersect Technical Description.

SCHEDULE | SCHEDULE keywords requiring special description | WPAVE, WWPAVE, WPAVEDEP

48
Intersect Migrator user guide

WPIMULT, WPIMULTL
The behavior of these keywords differs between Eclipse 100 and Eclipse 300. If the WPIMULT (WPIMULTL) keyword is
used more than once for all the connections in a well without time stepping keywords in between, in Eclipse 100, only the
last value is applied. However, in Eclipse 300, the effect for this case is cumulative, that is the multiplying factor is
applied each time the keyword is entered. The Migrator is compliant with Eclipse 300 behavior.
When used under ACTIONX, the WPIMULT keyword can only be used to set the multiplier at the well and completion
levels. Note that WPIMULTL is not supported under ACTIONX.

WREGROUP
E100 does not allow the use of groups with subordinates, but E300 does. Intersect currently supports the use of groups
with subordinates, just like E300.
The target groups specified by either item 3 or item 5 cannot be defaulted.

WSEGHEAT
If item 4 is SEG and items 2, 3 and 6 specify the same segments as previously defined in WELSEGS record 2, then the
WSEGHEAT heat parameters are used and the WELSEGS heat parameters are ignored.
If item 4 is NONE, the specified segments are no longer used in the calculation of the heat transfer, even if the segments
have been previously defined in either WSEGHEAT or WELSEGS.

WSEGTABL
WSEGTABL item 5 is a property of the VFP table and not the segments. As a result, all the segments using the same
VFP table will use the same setting of item 5.

WSEPCOND
Separators explicitly defined using SEPCOND or FIELDSEP keywords can be used with WSEPCOND.

WTEST
WTEST (periodic testing of closed wells) is partially supported. Closure reasons P(hysical), E(conomic) and G(roup) are
supported; D(esign THP limit) and C(ompletion) are not. The startup time is instantaneous (item 5 default only
supported). The well is opened if it has been closed for one of the reasons specified. If all the completions are shut, then
any completion closed by any one of the same reasons will be opened. The completions and/or well may shut-in again
immediately if any of the current economic limits are exceeded.

WTRACER
WTRACER is partially supported. The well name and tracer name items (1 and 2) are supported. Numeric tracer
concentrations in item 3 are also supported, but the use of user-defined quantities in this field is not. Defining tracer
concentrations as a function of the cumulative injection (item 4) is not supported; nor is the ability to reuse produced
tracer concentrations from a group (item 5).

WVFPEXP
WVFPEXP is partially supported. Item 4 has no effect.

SCHEDULE | SCHEDULE keywords requiring special description | WVFPEXP

49
Intersect Migrator user guide

If item 3 is defaulted and either --preferred-defaults=E100 or --preferred-defaults=E300 is used,

the default setting of the well's CloseWellInStabilizedRegion field is ignored and reset to NONE to match
Eclipse behavior.
If item 5 is defaulted and the --preferred-defaults=E100 option is used, the default keyword setting is ignored
and Intersect is set to use LINEAR extrapolation as in Eclipse 100.

Use VFP files

VFP tables can sometimes be very large, which has an impact on the readability of IXF files. To improve this, the
Migrator can now export VFP tables into separate VFP files. The --export-vfp command line generates VFP files
from VFPPROD or VFPINJ keywords in the dataset. These VFP files are then directly included in the AFI file and are
read by the simulator using the VFP plugin.
The VFP files also aid in sharing of VFP tables with applications such as Petrel and VFPi. VFP files exported by Petrel or
VFPi can be added directly in an existing AFI file and passed on to Intersect without having to remigrate the Intersect
model.
To do this, add lines such as the following to the AFI file:

INCLUDE "MyProductionTable1.VFP" { reservoir="reservoir_name" simulation="IX"

type="VFP" }
INCLUDE "MyInjectionTable1.VFP" { reservoir="reservoir_name" simulation="IX"
type="VFP" }

The VFP tables from these VFP files can then be associated with wells in IXF using the root of the VFP filename. An
example for this is illustrated below:

Well "PROD" {
TubingHydraulicsTableDevice {
Name="MyProductionTable1"
}
}

Well "WINJ" {
TubingHydraulicsTableDevice {
Name="MyInjectionTable1"
}
}

Naming restrictions

Wildcard well and group names

The rules governing well (and group) names are almost identical to Eclipse. Well names can be one of the following
types:
Simple
For example, WELL1
Templated
For example, WELL*, WELL?, W*L* or \*1
List
For example, *LIST1

SCHEDULE | Naming restrictions | Wildcard well and group names

50
Intersect Migrator user guide

Templated list
For example, *LIST*, *LIST? or **1
Well names are up to a maximum of eight characters. Well names can contain any ASCII printable characters apart from
the dot (.) character. Eclipse well names are case insensitive (they are converted to uppercase during the load of the
deck).
The asterisk (*) and question mark (?) characters have special meaning.
• The asterisk (*) character at the start of the name implies the name is a list, for example *LIST1.
• The asterisk (*) character used elsewhere in the name is used to match zero or more characters, for example: W*
matches W, W1, W12, W123 and so on.
• If an asterisk wildcard is required at the start of a name it should be escaped (\) in order to differentiate it from a list,
for example: '\*123' matches W123, P123, I123, WELL123. The exception to this rule is a single asterisk
(*) that matches all wells and does not need to be escaped.
• The question mark (?) character is used to match exactly one character; for example: W? matches W1 or W2 and so
on but does not match W or WWW
The expansion of wild-carded well names for example "W*" is evaluated at the end of the time/report period and the
same expansion is applied to all uses of the expansion in the time period regardless of when new wells have been
defined in that period. For example in the following keyword sequence the first use of "A*" will include the well A1 even
though the well A1 is defined after the WCONPROD keyword. This is different to the Eclipse behavior.

TSTEP ...

WCONPROD
'A*' 'OPEN' 'ORAT' 2000 /
/

WELSPECS
'A1' ... /
/

COMPDAT
'A1' 1* 1* 2 6 ... /
/

WPIMULT
'A*' 0.9 /
/
TSTEP...

Wild-carded group names are also expanded similarly.

Restrictions on node names

Intersect does not allow a node to contain other nodes with same name even if they are of different types. For example, it
is not allowed to have a well and an injection stream with same name because they are both nodes of the well model
manager even though they are of different types. The Migrator will give the appropriate error message if the same name
is used for a well, injection stream or heater.

SCHEDULE | Naming restrictions | Restrictions on node names

51
Intersect Migrator user guide

10
Multiple-section keywords
Keyword Sections in which the keyword is supported
ADD GRID, EDIT, PROPS, REGIONS, SOLUTION
ADDREG GRID, EDIT, PROPS, REGIONS, SOLUTION
AMFVD PROPS, SOLUTION
AQUANCON GRID, SOLUTION
AQUCT GRID, SOLUTION, SCHEDULE
AQUFETP SOLUTION, SCHEDULE
AQUFLUX SOLUTION, SCHEDULE
BOX GRID, EDIT, PROPS, REGIONS, SOLUTION, SCHEDULE
COPY GRID, EDIT, PROPS, REGIONS, SOLUTION
END RUNSPEC, GRID, EDIT, PROPS, REGIONS, SOLUTION, SUMMARY, SCHEDULE
ENDBOX GRID, EDIT, PROPS, REGIONS, SOLUTION, SCHEDULE
ENDFIN GRID, EDIT, PROPS, REGIONS, SOLUTION, SCHEDULE
ENDINC RUNSPEC, GRID, EDIT, PROPS, REGIONS, SOLUTION, SUMMARY, SCHEDULE
ENDSKIP RUNSPEC, GRID, EDIT, PROPS, REGIONS, SOLUTION, SUMMARY, SCHEDULE
EOS RUNSPEC, PROPS
EQUALREG GRID, EDIT, PROPS, REGIONS, SOLUTION
EQUALS GRID, EDIT, PROPS, REGIONS, SOLUTION
GPTABLE SOLUTION, SCHEDULE
GPTABLE3 SOLUTION, SCHEDULE
GPTABLEN SOLUTION, SCHEDULE
INCLUDE RUNSPEC, GRID, EDIT, PROPS, REGIONS, SOLUTION, SUMMARY, SCHEDULE
LGRCOPY RUNSPEC, GRID, EDIT
MAXVALUE GRID, EDIT, PROPS
MINVALUE GRID, EDIT, PROPS
MULTFLT GRID, EDIT, SCHEDULE
MULTIPLY GRID, EDIT, PROPS, REGIONS, SOLUTION

Multiple-section keywords
52
Intersect Migrator user guide

Keyword Sections in which the keyword is supported

MULTIREG GRID, EDIT, PROPS, REGIONS, SOLUTION
MULTPV GRID, EDIT
MULTREGP GRID, EDIT
MULTREGT GRID, EDIT, SCHEDULE
MULTX GRID, EDIT, SCHEDULE
MULTX- GRID, EDIT, SCHEDULE
MULTY GRID, EDIT, SCHEDULE
MULTY- GRID, EDIT, SCHEDULE
MULTZ GRID, EDIT, SCHEDULE
MULTZ- GRID, EDIT, SCHEDULE
NODPPM RUNSPEC, GRID
NOSIM RUNSPEC, SCHEDULE
NUPCOL RUNSPEC, SCHEDULE
OPERATE GRID, EDIT, PROPS, REGIONS, SOLUTION
OPERATER GRID, EDIT, PROPS, REGIONS, SOLUTION
OPERNUM GRID, REGIONS
OUTSOL SOLUTION, SCHEDULE
REFINE GRID, EDIT, PROPS, REGIONS, SOLUTION, SCHEDULE
RPTONLY SUMMARY, SCHEDULE
RPTRST SOLUTION, SCHEDULE
RSWVD PROPS, SOLUTION
RTEMP PROPS, SOLUTION
SAVE RUNSPEC, SCHEDULE
SKIP RUNSPEC, GRID, EDIT, PROPS, REGIONS, SOLUTION, SUMMARY, SCHEDULE
SKIP100 RUNSPEC, GRID, EDIT, PROPS, REGIONS, SOLUTION, SUMMARY, SCHEDULE
SKIP300 RUNSPEC, GRID, EDIT, PROPS, REGIONS, SOLUTION, SUMMARY, SCHEDULE
WELLOPTS RUNSPEC, SCHEDULE

Multiple-section keywords
53
Intersect Migrator user guide

11
GRID EDIT processing options
The default workflow is to migrate the GRID and EDIT section keywords to equivalent Intersect input. Compared to the
original workflow that processed these keywords internally, this reduces the amount of grid property pre-processing that
takes place within the Migrator and moves this into Intersect. The aim of the new workflow is to remove the Migrator from
the history matching cycle, speeding up the history matching process. It does this by allowing grid properties to be edited
via IXF, after the Migration step. Furthermore, in this workflow the pre-processing of grid properties and calculation of
pore volumes and transmissibilities is done in Intersect, taking advantage of the parallel execution architecture. Both of
these advantages combine to greatly reduce the time required to produce a history match.
The original workflow, that processes the majority of Eclipse GRID and EDIT section keywords internally, is still
available as an option. The processing within the Migrator matches that within Eclipse. Grid cell volume and pore volume
are calculated from geometry, porosity and NTG (net-to-gross). Then the active cell set is determined, allowing
transmissibility to be calculated from permeability, NTG and corner point geometry. The final transmissibility, pore
volumes, depths and other properties are transferred to Intersect as large binary arrays within the GSG file. Property edits
in the Eclipse EDIT section are applied by the Migrator to the input properties before pore volume and transmissibility
are calculated. Any modification of properties, such as for history matching, requires that the Migrator be run again.
Further information: Grid property edits in the Intersect Technical Description

Migrate grid edits default

The migration of GRID and EDIT section keywords to equivalent Intersect input is now the default workflow and
requires no command line switch. This option was enabled in previous releases using the deprecated command line
switch:
--ix-grid-geometry
This disables the transmissibility calculation within the Migrator, and causes the original corner point geometry and
primary properties, such as permeability, porosity and net-to-gross, to be transferred to Intersect where they are
processed.

Process grid edits option

The original Migrator GRID and EDIT section processing logic is enabled with the following Migrator command line
switch:
--process-grid-edits
When specified, this enables the transmissibility calculation within the Migrator, and causes transmissibility, pore
volumes and final properties (with edits applied) to be passed to Intersect. The Intersect transmissibility calculation is
then disabled.

GRID EDIT processing options | Process grid edits option

54
Intersect Migrator user guide

Workflow differences
A summary of the differences that the new default (migrate grid edits) workflow has compared to the old (process grid
edits) workflow follows.
Petrel Intersect workflow
Whenever possible Petrel exports a GSG file and IXF files which are consumed directly by Intersect. This does
not involve the Migrator.
Aquifers
When migrating a keywords deck (as opposed to a model exported from Petrel) all aquifer parameters for all
aquifer types are migrated to the IXF files. Previously, aquifer connections and numerical aquifer parameters
were in the GSG file. Aquifer connections defined in the matrix part of a dual-porosity grid will be accepted and
will not be replicated in the fracture part of the grid, unless explicitly specified as such.
The AQUCON keyword is supported in the GRID and SOLUTION sections in grid edits workflow. In the old
workflow it is only supported in the GRID section. The AQUCT keyword, supported in the sections GRID ,
SOLUTION , and SCHEDULE sections in the old workflow, is additionally supported in the PROPS section in
the grid edits workflow.
Cell properties
Cell properties as defined in the deck are exported to the GSG file unaltered by any modifier keyword (such as
EQUALS or MULTIPLY). Optional properties which override calculated values or defaults, such as PORV,
TRANX, MULTPV and MULTX, are written to the GSG file, and have a corresponding entry in the IXF file. The
IXF entry can be removed to disable the loading of this property data.
Cell property edits
Property edits (such as defined by the EQUALS or MULTIPLY keywords or similar) are now migrated to IXF,
where they can be included, excluded or modified further as the user wishes. These modifications are then
applied within Intersect.
Coarsening
The COARSEN keyword is only supported in the default migrate grid edits workflow and not in the process-grid-
edits workflow.
Faults
Fault connections defined in the matrix part of a dual-porosity grid will be replicated in the fracture part of the
grid. This is different behavior from the old workflow, and from Eclipse.
Fault multipliers
The MULTFLT keyword is migrated to the IXF files. Fault locations are still migrated in the GSG file.
MULTFLT is supported in the SCHEDULE section in the new migrate grid edits workflow.
Grids
These keywords are supported in the SCHEDULE section in the new migrate grid edits workflow but not in the
old process grid edits workflow: BOX, ENDBOX, REFINE, ENDFIN, MULTFLT, MULTREGT,
MULTSIGV, MULTX, MULTY, MULTZ, MULTX-, MULTY-, MULTZ-.
Inter-region transmissibility multipliers
The MULTREGT keyword is migrated to the IXF files. MULTREGT is supported in the SCHEDULE section in
the new migrate grid edits workflow.
Non-Neighbor Connections
The NNC, NNCGEN, EDITNNC and EDITNNCR keywords are migrated to the IXF files. NNCGEN is
supported in the new migrate grid edits workflow.
Pinchout
The PINCH keywords are migrated to the IXF files.

GRID EDIT processing options | Workflow differences

55
Intersect Migrator user guide

Region mapping
Eclipse style regions such as EQUNUM, SATNUM, PVTNUM, COALNUM, EOSNUM and IMBNUM are now
transferred to Intersect which then combines them to form the standard Intersect rock and fluid regions.
Depending on the --region-mapping command line switch, this will either use the old region mapping
extension (--region-mapping=0), or the new family of nodes (--region-mapping=1, set by default):
FluidModelDefinition, RockRegionMapping, EquilibriumRegionMapping,
FluidRegionMapping. This allows the Eclipse style region edits to be migrated to equivalent IXF and then
further edited within Intersect before mapping to the Intersect style regions. Region data will be migrated to the
IXF files for all regions defined in the REGDIMS and TABDIMS keywords even if they are not used in any cell
of the grid.
Region pore volume multipliers
The MULTREGP keyword is migrated to the IXF files.
Thermal boundaries
The ROCKCON and ROCKCONL keywords are migrated to the IXF files.
Transmissibility multipliers
The MULTX/Y/Z keywords are transferred using the GSG file but applied, using IXF edits, at the correct point
in the simulation timeline. Note that in the new migrate grid edits workflow, they are now supported in the
SCHEDULE section. Transmissibility multipliers remain unsupported in the SCHEDULE section in the old
process grid edits workflow.
Volume threshold keywords
The MINPORV, MINPV and MINROCKV keywords are migrated to the IXF files. MINPVV is migrated to the
GSG file but applied within Intersect.
Further information:
• Data handling and transfer
• For a full description, refer to the Region mapping section in the Intersect Technical Description.

Run using the default migrate grid edits option

The new Migrator workflow that migrates GRID and EDIT keywords to equivalent Intersect input requires no extra
command line options. The --ix-grid-geometry command line switch used in previous releases is deprecated.
To run the simulation using the AFI file, use the following command:
eclrun ix basename
Intersect reads the AFI file and runs the simulation.
Note that the AFI has the following structure

SIMULATION ix "basename" {
INCLUDE "basename.gsg" { gsg_type="geom_and_props" }
INCLUDE "basename_ECL2IX_IX.ixf"
INCLUDE "basename_reservoir_edits.ixf" { preserve="True" }
}
SIMULATION fm {
INCLUDE "basename_ECL2IX_FM.ixf"
INCLUDE "basename_fm_edits.ixf" { preserve="True" }
}

The GSG file contains geometry and bulk property data. The file _ECL2IX_IX.ixf contains the migrated GRID and
EDIT section keywords.
Region mapping in Intersect maps models to regions in the grid and takes advantage of the flexibility provided by Eclipse
region assignments.

GRID EDIT processing options | Run using the default migrate grid edits option
56
Intersect Migrator user guide

There are two region mapping options available:

--region-mapping = 0 Old region mapping (option)

--region-mapping = 1 New region mapping (default)

Run using the process grid edits option

The old Migrator workflow that processes GRID and EDIT keywords internally within the Migrator is activated by adding
the --process-grid-edits command line switch. So an example command might be:
eclrun ecl2ix basename --exe-args="--process-grid-edits"
where basename is the root name of the input dataset.
To run the simulation using the AFI file, use the following command:
eclrun ix basename
Intersect reads the AFI file and runs the simulation.
Note that the AFI file contains the line

SIMULATION ix "basename" {
INCLUDE "basename_ECL2IX.gsg"
INCLUDE "basename_ECL2IX_IX.ixf"
INCLUDE "basename_reservoir_edits.ixf" { preserve="True" }
}
SIMULATION fm {
INCLUDE "basename_ECL2IX_FM.ixf"
INCLUDE "basename_fm_edits.ixf" { preserve="True" }
}

The GSG file contains bulk grid properties and no geometry. The Eclipse style fluid and rock model regions are translated
into Intersect style regions within the Migrator based on the final edited grid properties.

Limitations
When the new migrate grid edits workflow is run, some features are not supported that are supported in the old workflow.
The details of the unsupported keywords are given in the migration report.
Unsupported keywords
PINCHREG, PINCHNUM, RESVNUM.
Further information: Editing properties in the Intersect Technical Description
Relevant nodes:
• CellPropertyEdit
• BoxPropertyEdit

Data handling and transfer

The following table describes the handling of each item of input data in the new default migrate grid edits workflow as
compared to the old workflow. In particular the table states whether they are transferred as IXF data (and so readily
editable at the Intersect level) or in the GSG file. Any current limitations are also given.
The main difference with the new migrate grid edits workflow is that, where possible, Eclipse GRID and EDIT keywords
are processed using IXF within Intersect. This data was previously processed in the Migrator and rolled into the large

GRID EDIT processing options | Data handling and transfer

57
Intersect Migrator user guide

bulk properties in the GSG file. Note that even with the migrate grid edits workflow, large bulk data, such as enumerated
grid cell properties and fault connections are still transferred using the GSG file. However, the use of this data (for
example for box property edits and fault transmissibility multipliers) is now explicitly controlled via IXF and processed
within Intersect. In this way Eclipse GRID and EDIT keywords to be migrated to equivalent IXF and further edited within
Intersect without returning to the Migrator. The main difference is that bulk data used in these edits is transferred
separately via the binary GSG file.

Data Eclipse Old 'process grid edits' Default 'migrate grid edits' workflow
keywords workflow
Corner-point grid COORD, Processed within the Migrator Equivalent pillar grid geometry written to the GSG
geometry ZCORN and not passed to Intersect file. Corner point geometry still written to an
(except in certain cases such EGRID file for results visualization.
as fine scale equilibration).
Written to an EGRID file for
results visualization.
LGRs CARFIN, Processed within the Migrator. LGR cell geometry written to the GSG file. Still also
HXFIN, Written to an EGRID file for written to an EGRID file for results visualization.
HYFIN, results visualization. REFINE and ENDFIN are now supported in the
HZFIN SCHEDULE section.
Transmissibility TRANX, Written to the GSG file as If not present, calculated within Intersect from
TRANY, connection list. geometry and edited permeability. If present, in
TRANZ the GSG file and applied as box edits in the IXF
file.
Porosity PORO In the GSG file but only used In the GSG file and now editable using the IXF
for echo to INIT file. file.
Permeability PERMX, In the GSG file but only used In the GSG file and now editable using the IXF
PERMY, for echo to INIT file. file.
PERMZ
Net-to-gross NTG In the GSG file but only used In the GSG file and now editable using the IXF
for echo to INIT file. file.
Thermal THCONR, In the GSG file but only used In the GSG file and now editable using the IXF
conductivity THCROCK, for echo to INIT file. file.
THCWATER,
THCOIL,
THCGAS,
THCONSF
Depth DEPTH In the GSG file. Calculated within Intersect from geometry.
Pore and rock PORV, ROCKV In the GSG file. If not present, calculated within Intersect from
volume geometry and edited porosity. If present, in the
GSG file and applied as box edits in the IXF file.
Cell activity MINPV, Applied to pore volume and The information from the MINPV, MINPORV,
MINPORV, exported using the GSG file. MINRV, and MINROCKV keywords is now in the
MINPVV, IXF file. The MINPVV keyword data is in the GSG
MINRV, file but applied in Intersect.
MINROCKV
Pinchout PINCHOUT, Applied to pore volume and The PINCHOUT keyword data is in the IXF file
PINCH, transmissibility and written to and applied within Intersect. The PINCHNUM,
PINCHREG, the GSG file. The PINCHXY PINCHREG and PINCHXY keywords are not
PINCHXY keyword is not supported. supported.

GRID EDIT processing options | Data handling and transfer

58
Intersect Migrator user guide

Data Eclipse Old 'process grid edits' Default 'migrate grid edits' workflow
keywords workflow
Numerical AQUNUM Some data items supported in In the IXF file.
aquifers IXF, some included in
transmissibility in the GSG file.
Numerical AQUCON Included in transmissibility in In the IXF file.
aquifer the GSG file.
connections
Analytical AQUCT, In the IXF file. In the IXF file.
aquifers AQUFET,
AQUFETP,
AQUFLUX,
AQUTAB
Analytical aquifer AQUANCON Processed as the connected In the IXF file.
connections cell list and areas in the GSG
file.
LGR analytical AQANCONL Not supported In the IXF file.
aquifer
connections
Faults FAULTS In the GSG file. Data used for In the GSG file.
fault threshold pressure and
fault transmissibility
multipliers.
Fault MULTFLT Applied in the Migrator and In the IXF file and applied in Intersect. Now
transmissibility included in the transmissibility supported in the SCHEDULE section.
multipliers data in the GSG file.
Inter-region MULTREGT Applied in the Migrator and In the IXF file and applied in Intersect. Now
transmissibility included in the transmissibility supported in the SCHEDULE section.
multipliers data in the GSG file.
Cell based MULTX/Y/Z Applied in the Migrator and In the GSG file and applied in Intersect as box
transmissibility included in the transmissibility edits in the IXF file. Supported in the SCHEDULE
multipliers data in the GSG file. section.
Non-neighbor NNC, Applied in the Migrator and In the IXF file and applied in Intersect after the
connections EDITNNC included in the transmissibility transmissibility and pore volume calculation.
data in the GSG file.
Non-neighbor NNCGEN, Not supported. In the IXF file and applied in Intersect after the
connections EDITNNCR transmissibility and pore volume calculation.
Dual porosity DUALPERM, Applied in the Migrator and DPNUM in the GSG file. The rest in the IXF file
and dual DUALPORO, included in the transmissibility and applied in Intersect.
permeability DPGRID, data and properties in the
DPNUM GSG file.
Coarsening COARSEN Not supported In the IXF file.
Pore volume MULTPV Applied in the Migrator and In the GSG file and applied in Intersect as box
multiplier included in pore volume data edits in the IXF file.
within the GSG file.
Pore volume MULTREGP Applied in the Migrator and In the IXF file and applied in Intersect.
region multiplier included in pore volume data
within the GSG file.
Region FIPNUM, In the GSG file but only used In the GSG file and now editable using the IXF
properties FIP*, for echo to INIT file. file.

GRID EDIT processing options | Data handling and transfer

59
Intersect Migrator user guide

Data Eclipse Old 'process grid edits' Default 'migrate grid edits' workflow
keywords workflow
FLUXNUM,
MULTNUM,
OPERNUM,
EQUNUM,
SATNUM,
PVTNUM,
COALNUM,
EOSNUM,
IMBNUM.
GRID section ADD, ADDREG, Applied in the Migrator and In the IXF file and applied in Intersect.
editing keywords COPY, the edited properties written to
EQUALS, the GSG file.
EQUALREG,
MAXVALUE,
MINVALUE,
MULTIPLY,
MULTIREG,
OPERATE,
OPERATER
EDIT section ADD, ADDREG, Applied in the Migrator and In the IXF file and applied in Intersect.
editing keywords COPY, the edited properties written to
EQUALS, the GSG file.
EQUALREG,
MAXVALUE,
MINVALUE,
MULTIPLY,
MULTIREG,
OPERATE,
OPERATER
PROPS section ADD, ADDREG, Applied in the Migrator and In the IXF file and applied in Intersect.
editing keywords COPY, the edited properties written to
EQUALS, the GSG file.
EQUALREG,
MAXVALUE,
MINVALUE,
MULTIPLY,
MULTIREG,
OPERATE,
OPERATER
REGIONS ADD, ADDREG, Applied in the Migrator and In the IXF file and applied in Intersect.
section editing COPY, the edited properties written to
keywords EQUALS, the GSG file.
EQUALREG,
MAXVALUE,
MINVALUE,
MULTIPLY,
MULTIREG,
OPERATE,
OPERATER

GRID EDIT processing options | Data handling and transfer

60
Intersect Migrator user guide

Data Eclipse Old 'process grid edits' Default 'migrate grid edits' workflow
keywords workflow
SOLUTION ADD, ADDREG, Applied in the Migrator and In the IXF file and applied in Intersect.
section editing COPY, the edited properties written to
keywords EQUALS, the GSG file.
EQUALREG,
MAXVALUE,
MINVALUE,
MULTIPLY,
MULTIREG,
OPERATE,
OPERATER
Well connections COMPDAT Connection factor, kH and The IXF file will contain information from the
related data are calculated in COMPDAT keyword data. If the connection factor
the Migrator from the is not specified, it is calculated within Intersect.
geometry, permeability and Two treatments of NTG are available for
skin, and written into the IXF connection factor calculation, using the
file. WellConnectionNTGTreatment field in the
WellCalculationOptions node. The IXF
file only contains data, such as kH, if it is specified
in the COMPDAT keyword. Skin is also processed
within Intersect.
J-functions JFUNC, In the IXF file except for item In the IXF file and applied in Intersect.
JFUNCR 6, the permeability to use.
This is transferred as
JFUNCTION_PERM in the
GSG file.

Further information: Editing properties in the Intersect Technical Description.

Relevant nodes:
• CellPropertyEdit
• BoxPropertyEdit
• WellCalculationOptions

Keywords requiring special description

The following keywords have additional restrictions.

BOX, ENDBOX
These keywords are supported in the SCHEDULE section in the migrate grid edits workflow only.

MINPVV
If MINPVV is used to make all cells within an LGR inactive the coarse grid cells replaced by the LGR will remain inactive.
This differs from the E300 behavior where the coarse grid cells would become active.

MULTFLT
This keyword is supported in the SCHEDULE section in the migrate grid edits workflow only.

GRID EDIT processing options | Keywords requiring special description | MULTFLT

61
Intersect Migrator user guide

MULTREGT
This keyword is supported in the SCHEDULE section in the migrate grid edits workflow only.

MULTSIGV
This keyword is supported in the SCHEDULE section in the migrate grid edits workflow only.

MULTX/Y/Z
The transmissibility multiplier keywords, MULTX, MULTY, MULTZ, MULTX-, MULTY- and MULTZ- are supported in the
SCHEDULE section. Transmissibility multipliers remain unsupported in the SCHEDULE section in the old process grid
edits workflow.

REFINE, ENDFIN
These keywords are supported in the SCHEDULE section in the migrate grid edits workflow only.

RPTGRID
This keyword, in combination with the ALLNNC option, is supported in both the migrate grid edits workflow and process
grid edits workflow.

Difference in supported keywords for classic workflow

GRID

Keyword Support Support for Items and Choices (in brackets)

MULTREGT Partially Supported Unsupported Items (Choices): 5 (NNC, NONNC)

EDIT

Keyword Support Support for Items and Choices (in brackets)

MULTREGT Partially Supported Unsupported Items (Choices): 5 (NNC, NONNC)

SOLUTION

Keyword Support Support for Items and Choices (in brackets)

AQANCONL Not Supported

SCHEDULE

Keyword Support Support for Items and Choices (in brackets)

BOX Not Supported
ENDBOX Not Supported
ENDFIN Not Supported
MULTFLT Not Supported
MULTREGT Partially Supported Unsupported Items (Choices): 5 (NNC, NONNC)

GRID EDIT processing options | Difference in supported keywords for classic workflow
62
Intersect Migrator user guide

Keyword Support Support for Items and Choices (in brackets)

MULTSIGV Not Supported
MULTX Not Supported
MULTX- Not Supported
MULTY Not Supported
MULTY- Not Supported
MULTZ Not Supported
MULTZ- Not Supported
REFINE Not Supported

GRID EDIT processing options | Difference in supported keywords for classic workflow
63
Intersect Migrator user guide

12
Integration with Petrel
Development strategies
"Make development strategy" WELL_DRAWDOWN rule
Petrel RE allows the WELL_DRAWDOWN (drawdown control) rule to be applied to injectors and producers. The
Migrator does not support the WELL_DRAWDOWN rule on injectors. Applying the WELL_DRAWDOWN rule to
injectors may lead to incorrect results.
Differences in Bottom Hole Pressure limit defaults
When a development strategy is built using Petrel's Make development strategy process, the bottom hole
pressure limits for the producers and injectors are not automatically set by the development strategy. For
Intersect they have to be explicitly specified using either, for producers, a Well pressure production control
rule or for injectors, the appropriate well injection control rules. If the bottom hole pressures are not set, then
Intersect's defaults are used. The default values used in Intersect are different to those used in Eclipse 100
and Eclipse 300. If the bottom hole pressure limits are not explicitly set, then the results from the different
simulators are very likely to be different.
Changes in well type
For models exported from Petrel there is a difference in behavior between Eclipse and Intersect for wells that
switch from injector to producer and vice versa, or wells that switch from history to prediction. The difference is
that for the Eclipse simulations the affected wells are automatically opened even if you have not requested this.
For Intersect the well does not automatically open that is the well type change is honored without affecting the
well status.

Well folder names

For development strategies used in Intersect simulation cases, you cannot have wells and well folders with same names.
The Migrator issues an error message for this in Petrel simulation export step. Renaming wells or well folders such that
they have different names will fix this issue.

Petrel interface
Wells and fluid reports
The Wells and Fluids in place settings on the Results tab of the Define Simulation Case process do not
control the Migrator's reporting.
Intra-day restarts
Petrel does not support intra-day restarts for Intersect that is you are only allowed one restart per day.

Integration with Petrel | Petrel interface

64
Intersect Migrator user guide

Other Petrel considerations

Eclipse cases exported by Petrel
The migrator supports the migration of Eclipse GSG files, which are exported by PETREL for Eclipse
simulation cases when the "GSG" option is selected for the grid files. Alternatively, you can create an EGRID
or GRDECL grid file for the Eclipse data set before migration.
Editing the Petrel exported Intersect case
The keywords in the DATA and INC files exported by Petrel for Petrel-Intersect cases should not be edited.
This may lead to undesired results. The changes should instead be done in Petrel model itself or directly in IXF
using the IXF editor provided by Petrel.
Aquifers
The 3D properties AQUIFERA and AQUIFERN in the INIT file show for each cell which aquifers are
connected to it. Cells which form part of an aquifer are given a value of -1. Petrel cannot display these negative
values in the 3D window. These are displayed as 0, the same value as a cell which is not connected to any
aquifers.
Completion ordering
When exporting a model from Petrel to run in Intersect, only INPUT completion ordering is supported. The
default completion ordering changes from TRACK to INPUT. See the COMPORD keyword for more information.
Simulation results
The 3D properties generated from a Petrel simulation case exported for and run with Intersect, can only be
viewed in Petrel. Eclipse pre- and post-applications cannot be used to view the 3D simulation results
generated for these cases. In addition, RFT/PLT results generated for Intersect simulation case having LGRs
cannot be displayed in Petrel.
Using entity names in user edits
When applying user edits to Petrel Development strategy case, ensure that the names of entities used in edits
IXF file matches exactly as it appears in the Development Strategy UI. Even changing the capitalization, for
example ‘PROD1’ written as ‘prod1’ in the edits file, may cause results not being loaded correctly to original
well ‘PROD1’ in Petrel.
Specifying injection mixtures through user edits
Intersect expects that the sum of the fractions of the fluid in the mixture to be unity. Eclipse and the Migrator
instead normalizes the fractions to 1.0 for computing the total composition of the fluid. If user wants to replicate
Eclipse behavior without using the Migrator (e.g. Petrel workflows), they will have to normalize the fractions
manually before setting it through user edits.

Integration with Petrel | Other Petrel considerations

65
Intersect Migrator user guide

A
Supported development strategy
rules
Below is the list of Petrel Development Strategy rules that are supported by the Petrel Intersect workflow.
• Comment
• Drilling priority formula
• Gas usage order
• Production guide rate formula
• Reporting frequency
• Schedule keywords
• Value aperture
• Group efficiency factor
• Group gas usage
• Group injection guide rate
• Group injection rate
• Group injection stream
• Group maximum ratio
• Group minimum production rate
• Group production guide rate
• Group rate production control
• Group region pressure maintenance
• Group reinjection
• Group reservoir volume injection rate
• Group shut consequences
• Group voidage replacement injection
• Drilling queue
• Well automatic cycling control
• Well constraint reset
• Well revival testing
• Well drawdown

Supported development strategy rules

66
Intersect Migrator user guide

• Well efficiency factor

• Well gas injection control
• Well guide rate
• Well injection stream
• Well maximum ratio
• Well minimum injection rate
• Well minimum production rate
• Well Preferred phase
• Well pressure production control
• Well rate production control
• Well separator
• Well shut consequences
• Well model options
• Well status
• Well steam-gas injection control
• Well thermal injection fluid properties
• Well thermal production control
• Well WAG injections control
• Well water cut
• Well water injection control
• History pressure limit
• History pressure report
• History rate control

Supported development strategy rules

67
Intersect Migrator user guide

B
Eclipse keywords versus Intersect
nodes
This appendix lists the Eclipse keywords that map to Intersect nodes.

Note: Not all keywords listed here are supported by Migrator even though Intersect may support that functionality. See
Multiple-section keywords (p.52) for keywords supported by the Migrator.

ACF API
ComponentProperties VariableAPI
ACTION APIGROUP
Instruction VariableAPI
ACTIONW APIVD
Instruction OilAPIDepthTable
ACTIONX AQANCONL
Expression AnalyticalAquiferIJKConnections
Instruction AQUANCON
ADD AnalyticalAquiferIJKConnections
CellPropertyEdit AQUCHGAS
AIM ConstantPressureGas
TimeStepSolution AQUCHWAT
AIMCON ConstantPressure
AimCriteria AQUCON
ALL NumericalAquiferIJKConnections
XYPlotSummaryReport AQUCT
AMFVD CarterTracy
CompositionDepthTable

Eclipse keywords versus Intersect nodes

68
Intersect Migrator user guide

AQUFET CO2STORE
Fetkovich SpycherPruessSolubility
AQUFETP COARSEN
Fetkovich GridCoarsening
AQUFLUX CODTYPE
ConstantFlux DensityLiquid
AQUNUM COMPDAT
NumericalAquifer CloseCompletionAction
AQUTAB Completion
CarterTracyInfluenceFunctionTable ModificationLogicTemplate
AUTOSAVE OpenCompletionAction
FieldManagement WellToCellConnections
Simulation COMPDATL
BIC CloseCompletionAction
BinaryInteractionCoef Completion
BRINE OpenCompletionAction
BrineFluidModel WellToCellConnections
CARFIN COMPINJK
StructuredInfo InjectionMobilityCalculation
CECON COMPKRI
CloseCompletionAction InjectionMobilityCalculation
EconomicLogicTemplate COMPLMPL
CECONT WellToCellConnections
EconomicLogicTemplate COMPLUMP
CGDTYPE WellToCellConnections
DensityVapor COMPMBIL
CGVTYPE InjectionMobilityCalculation
CompositionalFluidModel COMPMOBI
CNAMES InjectionMobilityCalculation
ComponentProperties COMPORD
CO2SOL WellToCellConnections
ComponentSolubilityTables COMPRP
WellSaturationFunctions

Eclipse keywords versus Intersect nodes

69
Intersect Migrator user guide

COMPS DENAQA
CompositionalFluidModel WaterDensityEzrokhi
COMPSEGL DGRDT
SegmentConductiveHeatTransfer GuideRate
WellToCellConnections DIFFCGAS
COMPSEGS MassTransferData
SegmentConductiveHeatTransfer DIFFCOIL
WellToCellConnections MassTransferData
COMPVD DIFFCWAT
CompositionDepthTable MassTransferData
COPY DIMENS
CellPropertyEdit StructuredInfo
COVTYPE DNGL
CompositionalFluidModel SeparatorMgr
CREF DREF
AqueousCompressibility AqueousCompressibility

LiquidCompressibility LiquidCompressibility

CRNDENS DREFT
AdsorptionTables AqueousCompressibility

ExtendedLangmuirIsotherm LiquidCompressibility

CSKIN DRILPRI
ModificationLogicTemplate DrillingQueue
CVCRIT RigResource
AllWellCalculationOptions DRSDT
Convergence RsControls
LinearControls DRVDT
WellCalculationOptions RvControls

DATES DUALPORO
FieldManagement DualPorosity

Reservoir
EDITNNC
ConnectionSet
Simulation
EDITNNCR
DATUM
ConnectionSet
Reservoir
Simulation

Eclipse keywords versus Intersect nodes

70
Intersect Migrator user guide

EHYSTR EQLNUM
CarlsonRelPermHysteresis EquilibriumRegionMapping
KilloughCapPressureHysteresis ModelToRegionMapping
KilloughRelPermHysteresis RegionFamily
RelPermHysteresis EQLOPTS
END ConstantThresholdPressure
FieldManagement FaultThresholdPressures
Reservoir FineScale
Simulation RegionThresholdPressure
StopRunAction VariableThresholdPressure
ENDACTIO EQUALS
Instruction CellPropertyEdit
ENKRVT EQUIL
RelPermEndPoints Equilibrium
ENPCVT FineScale
CapPressureEndPoints FAULTS
ENPTVT FaultDefinition
SaturationEndPoints FaultIJKBoxDefinition
EOSNUM Faults
FluidRegionMapping FBHPDEF
EPSDBGS ModificationLogicTemplate
EndPointsTemperatureFunction FIELD
EPSDEBUG Units
EndPointsTemperatureFunction FIELDSEP
EQLDIMS Separator
Equilibrium SeparatorMgr
EQLDKVCR SeparatorStage
EquilibriumReactionTerm
StageOutlet
KValueEquilibrium
FIP*
EQLDREAC RegionFamily
EquilibriumReactionTerm FIPNUM
RegionFamily

Eclipse keywords versus Intersect nodes

71
Intersect Migrator user guide

FIPSEP GCONPROD
Separator CloseCompletionAction
SeparatorStage CloseWellAction
StageOutlet EconomicLogicTemplate
FMTOUT GuideRate
Initial3DReport GuideRateBalanceAction
Recurrent3DReport GCONSALE
RFTPLTReport FluidStream
XYPlotSummaryReport GCONSUMP
FULLIMP FluidStream
TimeStepSolution GCONTOL
GADVANCE CouplingProperties
Group GECON
GASSOL CloseCompletionAction
ComponentSolubilityTables CloseWellAction
GASVISCT EconomicLogicTemplate
ViscosityTemperatureTable GECONT
GASWAT EconomicLogicTemplate
ComponentSolubilityTables GEFAC
GCONCAL Group
GuideRateBalanceAction ModificationLogicTemplate
GCONENG GINJGAS
GuideRateBalanceAction FluidSourceExternal
GCONINJE FluidSourceInternal
CloseWellAction FluidStream
GuideRate Group
GuideRateBalanceAction ModificationLogicTemplate
GCONPRI GLIFTOPT
EconomicLogicTemplate GroupLiftOpt
PrioritizedBalanceAction GMFVD
OilDensityDelumping
GPMAINT
PIDControl

Eclipse keywords versus Intersect nodes

72
Intersect Migrator user guide

GPTABLE GUIDERAT
GasPlantTable GuideRate
RecoveryFractions H2SSOL
GPTABLE3 ComponentSolubilityTables
RecoveryFractions HEATER
GPTABLEN Heater
RecoveryFractions HeaterDef
GRAVDRM HEATERL
AlternativeGravityDrainage Heater
GRAVITY HeaterDef
BlackOilFluidModel HEATVAP
GRUPRIG EnthalpyLiquidHeatCapacity
RigLogicTemplate EnthalpyVaporHeatCapacity
RigResource HEATVAPE
GRUPTARG EnthalpyLiquidHeatCapacity
GuideRate EnthalpyVaporHeatCapacity
GuideRateBalanceAction HEATVAPS
GRUPTREE EnthalpyVaporLiquidHeatCapacity
Group IMPES
GroupMgr TimeStepSolution
GSATCOMP IMPLICIT
FluidSourceExternal TimeStepSolution
GSATINJE IMPSAT
FluidSourceExternal TimeStepSolution
GSATPROD INIT
FluidSourceExternal Initial3DReport
GTADD JFUNC
ModifyConstraintAction JFunction
GTMULT JFunctionScaling
ModifyConstraintAction JFUNCR
GUIDECAL JFunctionScaling
GuideRate KVAN
KValueCrookston

Eclipse keywords versus Intersect nodes

73
Intersect Migrator user guide

KVCOMP LIFTOPT
KValueTables GasLiftOptimizationAction
KVCR LILIM
KValueCrookston CriticalMixingLimits
KVMF LOAD
KValueTables FieldManagement
KVTABCn Reservoir
KValuePressureTable Simulation
KVTABLE LSALTFNC
KValuePressureTable LowSaltWeightingTable
KVTABTn MAXVALUE
KValuePressureTable CellPropertyEdit
KVTEMP METRIC
KValueTables Units
KWTABTn MINVALUE
KValuePressureTableAqueous CellPropertyEdit
KValueTablesAqueous MISCEXP
KWTEMP MiscibleSurfaceTension
KValuePressureTableAqueous MISCIBLE
KValueTablesAqueous MiscibleFluidModel
LAB MISCNUM
Units RegionFamily
LANGMEXT MISCSTR
ExtendedLangmuirIsotherm MiscibleSurfaceTension
LANGMUIR MISCSTRR
AdsorptionMoleFractionTable MiscibleSurfaceTension
AdsorptionPressureTable MULTIPLY
AdsorptionTables CellPropertyEdit
LBCCOEF MULTOUT
ViscosityLBC Recurrent3DReport

ViscosityLBCExponential XYPlotSummaryReport

LBCCOEFR MULTREGT
ViscosityLBC RegionBoundaryPropertyEdit

ViscosityLBCExponential

Eclipse keywords versus Intersect nodes

74
Intersect Migrator user guide

MULTSAVE PARACHOR
FieldManagement ComponentProperties
Simulation PBVD
MW PBubDepthTable
ComponentProperties PCRIT
NCOMPS ComponentProperties
ComponentProperties PDVD
NEI PDewDepthTable
CompositionDepthTable PEDERSEN
NNC ViscosityPedersen
ConnectionSet PEDTUNE
NNCGEN ViscosityPedersen
ConnectionSet PEDTUNER
NOSIM ViscosityPedersen
FieldManagement PERFORMA
Simulation XYPlotSummaryReport
NUPCOL PICOND
CouplingProperties AllWellPseudoPressureOptions
OILVINDX PseudoPressureOptions
ViscosityMixingRule PIMULTAB
OILVISCT WellPIControl
ViscosityTemperatureTable PMANUM
OILVTIM RegionFamily
ViscosityMixingRule PMISC
OMFVD MiscibilityTable
OilDensityDelumping POLYMER
OPERATE PolymerFluidModel
BoxPropertyEdit PolymerModel
OPERATER PPCWMAX
CellPropertyEdit MaxWaterOilCapPressure
OVERBURD PREF
OverburdenPressureTable AqueousCompressibility
OverburdenPressureTableTrans LiquidCompressibility

Eclipse keywords versus Intersect nodes

75
Intersect Migrator user guide

PREFT QDRILL
AqueousCompressibility DrillingQueue
LiquidCompressibility RigResource
PRIORITY REACACT
PrioritizedBalanceAction Reaction
PSEUPRES REACCORD
WellDef Reaction
PVCDO REACENTH
DeadOilCompressibilities Reaction
PVCO REACPHA
OilTableUndersaturatedCompressibilities Reaction
ViscosityTemperatureTable REACPORD
PVDG Reaction
UndersaturatedGasTable REACRATE
PVDO Reaction
DeadOilTable REACSORD
PVDS Reaction
SolventTable REFINE
PVTG CellPropertyEdit
GasTable REGDIMS
PVTNUM TrackingOptions
FluidRegionMapping RESTART
ModelToRegionMapping FieldManagement
RegionFamily Reservoir
PVTO Simulation
OilTable ROCK
PVTW RockCompressibility
WaterCompressibilities ROCKCOMP
PVTWSALT DilationTable
BrineComponentCompressibilities RockTableHysteresis
PVZG ROCKCON
UndersaturatedGasTable HeatLossIJKConnections

Eclipse keywords versus Intersect nodes

76
Intersect Migrator user guide

ROCKNUM RPTSOL
RockRegionMapping Initial3DReport
ROCKOPTS Recurrent3DReport
OverburdenPressureTable RSVD
OverburdenPressureTableTrans SolutionGORDepthTable
ROCKPROP RSWVD
HeatLossVinsomeWesterveld SolutionGWRDepthTable
ROCKTAB RTEMP
CompactionMultiplierTable ComponentSolubilityInWater
CompactionTable TemperatureDepthTable
DilationMultiplierTable RTEMPVD
DilationTable TemperatureDepthTable
ElasticMultiplierTable RUNSUM
ROCKTABH XYPlotSummaryReport
CompactionMultiplierTable RVVD
CompactionTable VaporOGRDepthTable
DilationMultiplierTable SALTVD
DilationTable BrineConcentrationDepthTable

ElasticMultiplierTable SATNUM
RPTGRID ModelToRegionMapping

NNCReport RegionFamily

RPTONLY RockRegionMapping

XYPlotSummaryReport SAVE
RPTONLYO FieldManagement
XYPlotSummaryReport Simulation
RPTPRINT SCREF
FieldManagementStandardReport SolidCompressibility
ReservoirStandardReport SDENSITY
RPTRST MiscibleFluidModel
FieldManagement SDREF
Recurrent3DReport SolidCompressibility

Reservoir SEPARATE
RPTSCHED XYPlotSummaryReport

FieldManagementStandardReport
Recurrent3DReport

Eclipse keywords versus Intersect nodes

77
Intersect Migrator user guide

SEPCOND SOROPTS
Group ResidualOilSaturationModel
Separator SPECHA
SeparatorStage EnthalpyLiquidHeatCapacity
StageOutlet EnthalpyVaporLiquidHeatCapacity
SEPVALS SPECHB
BlackOilBubblePointConditions EnthalpyLiquidHeatCapacity
SGFN EnthalpyVaporLiquidHeatCapacity
CapPressure SPECHG
GasOilFunction EnthalpyVaporHeatCapacity
GasWaterFunction EnthalpyVaporLiquidHeatCapacity
JFunction SPECHH
JFunctionScaling EnthalpyVaporHeatCapacity
SGOF EnthalpyVaporLiquidHeatCapacity
GasOilFunction SPECHS
JFunction EnthalpySolidHeatCapacity
JFunctionScaling SPECHT
SGWFN EnthalpySolidHeatCapacity
GasWaterFunction SPECHW1
SLGOF EnthalpyAqueousHeatCapacity
GasOilFunction SPECHW2
JFunction EnthalpyAqueousHeatCapacity
JFunctionScaling SPREF
OilWaterFunction SolidCompressibility

SOLUAQA START
ComponentSolubilityTable FieldManagement

SOLUBILI Simulation

ComponentSolubilityTable STCOND
SOLUBILS EnthalpyLiquidHeatCapacity
ComponentSolubilityTable EnthalpyVaporHeatCapacity
SOLUBILT EnthalpyVaporLiquidHeatCapacity
ComponentSolubilityTable SeparatorMgr
SOLVENT STHERMEX1
MiscibleFluidModel SolidCompressibility

Eclipse keywords versus Intersect nodes

78
Intersect Migrator user guide

STOPROD THERMEX1
Reaction AqueousCompressibility
STOREAC LiquidCompressibility
Reaction THPRES
STREF RegionThresholdPressure
SolidCompressibility THPRESFT
SUMMARY ConstantThresholdPressure
XYPlotSummaryReport FaultThresholdPressures
SWFN VariableThresholdPressure
CapPressure TLMIXPAR
GasWaterFunction MiscibleFluidModel
JFunction TRACERS
JFunctionScaling TracerConcentrationDepthTable
OilWaterFunction TracerConcentrationDepthTables
SWOF TRACK
JFunction TrackingOptions
JFunctionScaling TRACKREG
OilWaterFunction TrackingOptions
TCRIT TREF
ComponentProperties AqueousCompressibility
TEMPVD LiquidCompressibility
TemperatureDepthTable TREFT
THCGAS AqueousCompressibility
SimpleVolumeWeightedHeatConductivity LiquidCompressibility
THCOIL TSCRIT
SimpleVolumeWeightedHeatConductivity AllWellCalculationOptions
THCONR WellCalculationOptions
GasSaturationDependentHeatConductivity TSTEP
THCONSF FieldManagement
GasSaturationDependentHeatConductivity
Reservoir
THCROCK
Simulation
SimpleVolumeWeightedHeatConductivity
THCWATER
SimpleVolumeWeightedHeatConductivity

Eclipse keywords versus Intersect nodes

79
Intersect Migrator user guide

TUNING VFPPROD
AllWellCalculationOptions DependentVariables
Convergence HydraulicsTable
LinearControls IndependentVariables
TimeStepSizingControls TubingHydraulicsTableDevice
WellCalculationOptions VISCAQA
UDQ ViscosityAqueousEzrokhi
Expression WaterViscosityEzrokhi
UNIFOUT VISCREF
Recurrent3DReport ViscosityTemperatureTable
XYPlotSummaryReport WAGHYSTR
VAPPARS WAGHysteresis
RsControls WALQCALC
RvControls TubingHeadPressureCalculationOptions
VCOMPACT WATDENT
ViscosityLBCExponential WaterExpansivitiesThermal
VCRIT WATVISCT
ComponentProperties ViscosityTemperatureTable
VCRITVIS WAVAILIM
ViscosityLBC ModificationLogicTemplate
ViscosityPedersen Well
VDKRG WBHGLR
HendersonVelocityDependentRelPerm ModifyConstraintAction
VDKRGC WBOREVOL
WhitsonGasCondensate SegmentPipes
VDKRO WCONHIST
HendersonVelocityDependentRelPerm CloseWellAction
VFPINJ OpenWellAction
DependentVariables RemoveConstraintAction
HydraulicsTable SetConstraintAction
IndependentVariables TubingHydraulicsTableDeviceDef
InjectionTubingHydraulicsTableDevice Well
TubingHydraulicsTableDevice

Eclipse keywords versus Intersect nodes

80
Intersect Migrator user guide

WCONINJE WDFAC
CloseWellAction ModificationLogicTemplate
ConstraintDevice WellDef
DrillingQueue WellToCellConnections
InjectionTubingHydraulicsTableDevice WDFACCOR
ModificationLogicTemplate DFactorModel
OpenWellAction ModificationLogicTemplate
RemoveConstraintAction WDRILPRI
SetConstraintAction DrillingQueue
TubingHydraulicsTableDevice RigResource
TubingHydraulicsTableDeviceDef WDRILTIM
Well DrillingQueue
WCONINJH RigLogicTemplate
CloseWellAction RigUsage
OpenWellAction WECON
RemoveConstraintAction CloseCompletionAction
SetConstraintAction CloseWellAction
TubingHydraulicsTableDeviceDef EconomicLogicTemplate
Well ModificationLogicTemplate
WCONPROD WECONCMF
CloseWellAction CloseCompletionAction
ConstraintDevice CloseWellAction
DrillingQueue EconomicLogicTemplate
ModificationLogicTemplate WECONINJ
OpenWellAction CloseCompletionAction
RemoveConstraintAction CloseWellAction
SetConstraintAction WECONT
TubingHydraulicsTableDevice EconomicLogicTemplate
TubingHydraulicsTableDeviceDef WEFAC
Well ConfigureWellAction
WCUTBACK ModificationLogicTemplate
ModificationLogicTemplate Well
ModifyConstraintAction WELCNTL
WCYCLE RemoveConstraintAction
CyclicWellControl SetConstraintAction
ModificationLogicTemplate
WellControlCycle

Eclipse keywords versus Intersect nodes

81
Intersect Migrator user guide

WELCTNL WELSEGS
ModificationLogicTemplate DriftFlux
WELDRAW SegmentConductiveHeatTransfer
AllWellDrawdownLimitOptions SegmentNodes
DrawdownLimitOptions SegmentPipes
RemoveConstraintAction WellDef
SetConstraintAction WELSPECL
WELLDIMS ResVolConditions
EclReports Well
WELLINJE WellDef
ModificationLogicTemplate WELSPECS
WELLPROD ConfigureWellAction
ModificationLogicTemplate ModificationLogicTemplate
WELLSTRE ResVolConditions
FluidSourceExternal Well
FluidSourceInternal WellDef
WELLWAG WELTARG
ModificationLogicTemplate ModificationLogicTemplate
WellControlCycle RemoveConstraintAction
WELOPEN SetConstraintAction
CloseWellAction WGRUPCON
ModificationLogicTemplate GuideRate
OpenCompletionAction WHISTCTL
OpenWellAction RemoveConstraintAction
WellToCellConnections SetConstraintAction
WELOPENL WHTEMP
OpenCompletionAction InjectionTubingHydraulicsTableDevice
OpenWellAction TubingHydraulicsTableDevice
WellToCellConnections WINJGAS
WELPI FluidSourceExternal
WellDef FluidSourceInternal
FluidStream
ModificationLogicTemplate

Eclipse keywords versus Intersect nodes

82
Intersect Migrator user guide

WINJMIX WRFTPLT
FluidSourceExternal RFTPLTReport
FluidSourceInternal WSALT
FluidStream FluidSourceExternal
WINJORD WSEGAICD
FluidSourceExternal FlowControlDeviceDef
FluidSourceInternal ModificationLogicTemplate
FluidStream WSEGDFMD
WLIFT DriftFlux
TubingHydraulicsTableDevice WSEGDFPA
WLIFTOPT DriftFlux
WellLiftOpt WSEGFLIM
WLIST ModificationLogicTemplate
StaticList WSEGFMOD
WLISTDYN DriftFlux
DynamicList SegmentPipes
WORKLIM WSEGHEAT
RigUsage SegmentConductiveHeatTransfer
WPAVE WSEGITER
AllWellBlockAveragePressureCalculation AllWellIterationSequenceControl
WPAVEDEP WellIterationSequenceControl
WellBlockAveragePressureCalculation WSEGLABY
WPIMULT FlowControlDeviceDef
ModificationLogicTemplate ModificationLogicTemplate
WellToCellConnections WSEGLINK
WPIMULTL SegmentPipes
WellToCellConnections WSEGSICD
WPITAB FlowControlDeviceDef
WellPIControl ModificationLogicTemplate
WPOLYRED WSEGSOLV
AllWellShearThinningOptions WellLinearControls
ShearThinningOptions
WRFT
RFTPLTReport

Eclipse keywords versus Intersect nodes

83
Intersect Migrator user guide

WSEGTABL ZCRIT
HydraulicsTable ComponentProperties
HydraulicsTableDevice ZFACTOR
HydraulicsTableDeviceDef VaporZFactor
WSEGVALV ZI
FlowControlDevice CompositionDepthTable
FlowControlDeviceDef ZMFVD
ModificationLogicTemplate CompositionDepthTable

WSEPCOND
ModificationLogicTemplate
Well
WSOLVENT
FluidSourceExternal
Well
WTADD
ModificationLogicTemplate
ModifyConstraintAction
WTEST
TestWellAction
WTMULT
ModificationLogicTemplate
ModifyConstraintAction
WTRACER
FluidStream
WVFPDP
TubingHydraulicsTableDeviceDef
WVFPEXP
TubingHeadPressureCalculationOptions
WWPAVE
WellBlockAveragePressureCalculation
XMFVP
SaturationPressureDelumping
YMFVP
SaturationPressureDelumping

Eclipse keywords versus Intersect nodes

84
Intersect Migrator user guide

C
Intersect and Eclipse feature
compatibility
This section provides information that may be useful when comparing the results of Intersect with other simulators. It
contains information that helps you to match the behavior of Intersect with the Eclipse simulators more closely, where
possible, if this is required. It also highlights areas where the behavior of Intersect differs from the Eclipse simulators and
the reasons why this happens.

The Eclipse to Intersect Migrator

• To match the energy quantities between Eclipse Compositional and Intersect Thermal simulations, you must set the
STCOND keyword in the Eclipse Compositional simulation model to the values below (depending on the unit system):
a. Temperature 63.33 Fahrenheit (FIELD) or 17.406 Celsius (METRIC and LAB).
b. Pressure 14.696 psi (FIELD), 1 bar (METRIC) or 0.98692 atm (LAB).
If hydrocarbon fluids are present, in the Eclipse data set you must set the TREF and PREF keywords and remove
the PVTW keyword.
• The Migrator may ignore some keywords if they do not follow the correct syntax. For example, keywords whose
names do not start from the beginning of the line, or where the keyword name is commented out but the data is not,
will be ignored. The Migrator may not report any error or warnings for such keywords, whereas Eclipse may report
such keywords as spurious data.
• Eclipse Compositional AIM/IMPES simulations use a default feature, the DPCDT keyword, to stabilize the run. This
feature is not included in Intersect. Adding the keyword NODPCDT in the Eclipse Compositional dataset disables this
feature. This means that the behavior of the Eclipse Compositional simulator should match the behavior of the
Intersect simulator more closely.
• When exporting a model from Petrel to Intersect, completion ordering other than INPUT is not supported, and the
default completion ordering changes from TRACK to INPUT. The connections are ordered in the sequence that they
are first declared in the COMPDAT or COMPDATL keywords. Refer to the COMPORD keyword for more information.
There is no such restriction for the keyword workflow.
• Prior to 2014.1, the Migrator would migrate Eclipse tuning keywords (for example LSCRIT, TSCRIT, CVCRIT,
TUNING, AIMCON, NSTACK) but Intersect did not react to any tuning related input that appeared after the
MODEL_DEFINITION section in an IXF file. This behavior was changed at 2014.1: the Migrator no longer migrates
those Eclipse tuning keywords (giving a prominent warning to that effect) and Intersect does respond to all tuning
related input regardless of its location. This may cause differences in behavior if you use 2014.1 Intersect to run a
model that was migrated with a pre-2014.1 Migrator. To avoid this migrate your model again using the 2014.1
Migrator. Only models with bespoke tuning should experience any change in behavior.

Intersect and Eclipse feature compatibility | The Eclipse to Intersect Migrator

85
Intersect Migrator user guide

Gridding and parallel simulation

• Unlike Eclipse, the Intersect simulator has no restrictions on forming a 1D or 2D cartesian partitioning of the grid into
domains to be simulated by separate processor in a parallel simulation. By default the simulator treats all grids as
unstructured and hence its parallel partitioning algorithm is completely automatic. The parallel partitions can be
viewed in a 3D viewer by selecting the grid property "PART". The partitioning may be complicated with
unstructured grids or grids with (possibly nested) local grid refinements.
• Traditional Cartesian partitioning is not recommended but you can enable it by first specifying the structure of the grid
and then the IJK cuts.
Relevant nodes, for more information on enabling traditional Cartesian partitioning refer to:
• StructuredInfo
• CartesianPartition

Equilibration
• When comparing Intersect simulation results with those from other simulators you must compare the initial fluid in
place calculated by the simulator with the reference simulator before the dynamic simulation is started. If there are
differences then candidates for investigation include rock compaction, end-point scaling, capillary pressures, initial
fluid compositions, pressures and temperatures.
• Critical fluid initialization is not currently supported when the COMPVD keyword is present. The COMPVD keyword is
however supported for bubble-point and dew-point fluid initialization. For critical fluid initialization the PSAT property
is reported as zero.
• More detailed information on the Intersect initialization and equilibration may be output from the simulator by
increasing the verbosity level of the Equilibrium Manager.
• Some differences with Eclipse may be observed in the initialization of models using the brine option. This is because
the underlying formulation in Intersect is based on mole fraction rather than concentration variables and a non-linear
conversion is required from the input concentration values.
Relevant node: EquilibriumMgr

Fluid modeling
• The treatment of black oil PVT calculations for pressures outside the range of the tabulated values in the input model
is different in Intersect compared to that in Eclipse. If you wish to reduce this difference between the simulators, then
black oil tables should be extended to cover the entire range of pressures used in the simulation; that is from the
highest pressure found in the reservoir or BHP used in injection down to the lowest pressure encountered in a
surface separator.
• The method for property value interpolation in black oil fluid property tables may differ from other simulators. For
example, the simulator interpolates directly between values of the oil viscosity, whereas other simulators may
interpolate on the reciprocal or the logarithm of the viscosity. The impact on simulation results should normally be
insignificant unless very large pressure increments are used in the input tables.
• Some of the algorithms for calculating thermal properties differ from those used in Eclipse Thermal. To obtain a
closer match in results set the ThermalProperties field on the FluidMgr node to "ECLIPSE" or
"ECLIPSE_IAPWS97".
• The second order term of the fluid enthalpy equations is different between Intersect and Eclipse. It affects the
simulation results only if the coefficients are non-zero.
• The reduced phase formulation cannot currently be used with the variable API black oil fluid model. A validation error
will occur if you try to use these features together.
Further information: Thermal Simulation in the Intersect Technical Description.

Intersect and Eclipse feature compatibility | Fluid modeling

86
Intersect Migrator user guide

Relevant node: FluidMgr

Rock physics
• Intersect supports both the Killough and Carlson relative permeability hysteresis methods, but not that of Jargon,
which is available in Eclipse 300.
• To increase simulator stability a validation check has been added to ensure that critical and maximum saturations for
each cell in the simulation grid are separated by at least 1E-06.
• A validation check ensures that saturation end-points are defined in the correct order: S(connate) < S(critical) <
S(maximum) This validation may not be present in other simulators. In addition a check is made that the relative
permeability at the maximum saturation is above that at the critical saturation.
• The definition and calculation method for capillary number may differ from other simulators, depending on the feature
in which it is used. For models other than the Whitson gas condensate capillary number dependent relative
permeability model, Intersect does not scale the capillary number by porosity, saturation or immiscible relative
permeability.
• The precise way in which end-point scaling is implemented in Intersect may differ from other simulators. For example
Eclipse uses a special treatment of each of the intervals between the connate, critical, associated critical and
maximum saturations, which is not implemented in Intersect.
• When obtaining the transmissibility multiplier from rock compaction tables, Eclipse 100 uses an explicit value of the
grid block pressure (or the explicit minimum pressure if the process is irreversible). This is different from Eclipse 300
and Intersect which both use the implicit value of the pressure. This can cause differences between Intersect and
Eclipse 100 results as these multipliers can be significantly different when the pressure is changing rapidly in a
region of the table with big changes in the transmissibility multiplier.

Well modeling
• When the simulator cannot find a valid flowing solution for a well (for example, if the reservoir pressure is below the
minimum BHP limit for a producer), it will shut the well along with all its connections irrespective of the setting item 9
in the WELSPECS keyword. This differs from Eclipse, which will perform a surface shut-in under these circumstances
if item 9 in the WELSPECS keyword is set to STOP.
• Intersect reports the actual steam quality (WSQU) at the bottom hole depth in the well while Eclipse Thermal reports
the user-specified value. The actual steam quality will be slightly different depending, for example, on well pressure
and crossflow.
• The calculation of voidage rate is performed by transforming the wellstream fluid to the average conditions over the
field or a specified region. In black oil simulations this calculation differs between Eclipse 300 and Eclipse 100. In
Eclipse 300 the fluid properties are calculated at the average hydrocarbon pressure in the field or region. However, in
Eclipse 100 the solution gas-oil ratio (Rs) of the oil phase is also capped so as not to exceed the average Rs of the
field or region. The calculation in Intersect follows the Eclipse 300 method, and may therefore give different voidage
rates to Eclipse 100 when the oil in the field or region is significantly undersaturated and the wellstream gas-oil ratio
is significantly higher than the average field or region Rs.
• When a negative bottom hole reference depth (for example, item 5 in WELSPECS) is specified in Eclipse 100, the
behavior depends on whether there are any grid cells above sea level. Because the grid processing is done within
the simulator, the Migrator does not know the grid cells heights, so the it treats such negative bottom hole reference
depth values as having their typical meaning in both Eclipse 100 and Eclipse 300 which is “default this quantity”.
Hence the Migrator generally does not migrate negative bottom hole reference depth values and leaves them unset,
and the bottom hole reference depth is calculated appropriately within the simulator. If you want such negative
values migrated, you should set the --honor-negative-bhp-ref-depth Migrator command line option.
• When the simulator is coupled to a network model the pressures at the well network boundaries act as additional
constraints when these coupled wells are solved for their deliverability and operating rates. By default these
pressures do not however act as additional constraints for potential rate solves and this means that the network does
not influence group balancing using guide rates that are based on well potential rates. This differs from Eclipse

Intersect and Eclipse feature compatibility | Well modeling

87
Intersect Migrator user guide

because network pressures do influence coupled well potential rate solves. This difference can be removed by
setting the WellMgr node NetworkPressuresLimitWellPotentials field to TRUE.

Reporting
• Intersect uses a different method than Eclipse for calculating inter-region phase flows for reporting purposes. It takes
the molar rates for all components and feeds them to the configured separator for the fluid in place report. This may
give different results from Eclipse.
• For consistency with pressure reporting, Intersect calculates well TEMPERATURE as the (pore volume weighted)
average of connected cell temperatures on all wells (regardless of whether they are injector or producer, open or
shut). This differs from Eclipse 300 which generally reports WTEMP as
• flowing bottom hole temperature for flowing wells,
• average reservoir temperature for non-flowing producers,
• injected fluid temperature for non-flowing injectors.
Note that Intersect also reports BOTTOM_HOLE_TEMPERATURE for flowing wells.

Fault and aquifer connections

• In the Intersect migrate grid edits workflow (the default behavior), fault connections defined in the matrix part of a
dual-porosity grid will be replicated in the fracture part of the grid. This is different behavior from the old process grid
edits workflow, and from Eclipse.
• In the Intersect migrate grid edits workflow (the default behavior), aquifer connections defined in the matrix part of a
dual-porosity grid will be accepted and will not be replicated in the fracture part of the grid, unless explicitly specified
as such.

Coal Seam Gas

• Coal Seam Gas (CSG), or Time-Dependent Coal Bed Methane, cases are now migrated. The physics of these cases
is similar to shale gas, but instead of the adsorbed gas and the pore space gas being in instantaneous equilibrium
through the adsorption tables or extended Langmuir isotherm, there is now a time-dependent diffusive process
whereby gas diffuses between the organic matter and the pore space when they are not in equilibrium with each
other.
• There is no separate schema node in Intersect for CSG. Instead, information on the use of time-dependent
adsorption on the organic matter is encapsulated in the descriptions for the adsorption: node AdsorptionTables and
node ExtendedLangmuirIsotherm both now have a data entry DiffusionType which should be set to
TIME_DEPENDENT (overriding the default INSTANTANEOUS for shale gas). Likewise there is no single keyword
activation of CSG in either E100 or E300. The keyword CBMOPTS is available in E300 and setting its first item to
TIMEDEP will activate CSG. However, while this keyword is available in E100, this is not usual, and may cause
other problems with the input. Consequently the migrator infers CSG from the simultaneous presence of the
keywords DUALPORO, COAL, and either of the two diffusion coefficient keywords DIFFCOAL (E100) or DIFFCBM
(E300). The two diffusion coefficient keywords are migrated to data fields in the adsorption nodes: either the
DiffusionCoefficient item in the AdsorptionPressureTable node of AdsorptionTables for the relevant component, or in
the ExtendedLangmuirIsotherm node as a list of coefficients corresponding to the list of component names.
DIFFCBM contains only the diffusion coefficients; the corresponding readsorption coefficients from keyword
RESORB are migrated to the ReadsorptionCoefficient item of the respective nodes. DIFFCOAL contains both
diffusion and readsorption coefficients and both are migrated, but its solvent diffusion coefficient is not migrated.
• The rock and bulk grain densities defined in the AdsorptionTables and ExtendedLangmuirIsotherm nodes are not
used in CSG, and the user should provide ROCKDEN input for migration as described below.

Intersect and Eclipse feature compatibility | Coal Seam Gas

88
Intersect Migrator user guide

• CSG has a different grid representation in Intersect from its representation in Eclipse. Eclipse uses a dual porosity
grid, where the fracture grid represents the pore space, and the matrix represents the coal, or organic matter. In
Intersect, this is simplified to a single porosity representation, where the single grid represents the pore space, and
additional quantities are introduced to represent the organic matter features. This allows many physical quantities
which do not have a meaning in the organic matter, such as permeability, and hence which occupy unnecessary
memory, to be discarded. For such cases, the migrator also performs a conversion from dual porosity to single
porosity grid in addition to converting the data to Intersect form. This means that the DualPorosity node is not present
in the migrator output and is not used to flag the use of CSG.
• The migrator takes the grid structure, as represented by the ZCORN array, from the matrix grid; if fracture values are
permitted in dual porosity (which may not be the case) they are discarded. Cell activity, coming from the ACTNUM
array, is also by default taken from the matrix grid, but may optionally be taken instead from the fracture if the
command line option “--dopt=csg_actnum_fracture” is supplied. Grid locations for well connections and aquifers are
usually taken from the fracture and migrated to the equivalent single-porosity grid positions (what would be the matrix
positions in the original dual porosity grid.) COMPDAT, COMPLUMP, WPIMULT, AQUANCON, AQUCON, AQUNUM are
all migrated in this way.
• LGRS are consistently migrated in this way, and boxes are honored in this process, both for explicit BOX keywords
and for data initialization using EQUALS, COPY and OPERATE, along with arithmetic operations using ADD,
MULTIPLY etc. The LGR equivalents of the well and aquifer connection keywords, COMPDATL, COMPLMPL,
WPIMULTL, AQANCONL are also migrated in this way. COARSEN ings are also migrated.
• Most physical quantities are migrated from the fracture data, and any matrix values supplied are discarded. However,
the following keywords represent the state of the organic matter and are taken from the matrix:
a. The keyword SIGMAV represents in CSG the geometric part of the transmissibility per unit volume between the
organic matter volume and the pore volume. It is migrated to the Intersect property
ORGANIC_MATTER_FRACTURE_COUPLING. The corresponding single-value keyword SIGMA is also
migrated to ORGANIC_MATTER_FRACTURE_COUPLING.
b. The keyword ROCKDEN represents for CSG the organic matter mass density, and is migrated to the Intersect
property ORGANIC_MATTER_DENSITY. When loading from data in a GSG file, it is labeled by the internal
keyword COALDEN to distinguish it from non-CSG uses of ROCKDEN.
c. The keyword COALNUM represents the coal region for the organic matter properties and is migrated to the
Intersect property COAL_REGION.
d. The keyword ROCKFRAC will be treated as equivalent to the matrix values of PORO as described below, and
migrated in the same way.
• For the adsorbed gas concentration on the organic matter, Intersect adopts a compositional representation, and
migrates E100 cases into this representation using a single gas species “GAS” (numerical label 1). The keywords for
initializing these quantities are also taken from the matrix part of the data:
Keywords GASCONC and GASADCO initialize the adsorbed concentration of gas on the organic matter, for the E100
gas species, and for the E300 compositional gas species respectively. They are migrated to the Intersect property
ADSORBED_GAS_INIT_CONC for the requisite number of species. The corresponding keywords GASSATC and
GASADEC, for E100 and E300 respectively, also initialize the adsorbed concentration, and in this case adjust the
Langmuir multiplier to make the initialized values an equilibrium adsorption. The multiplier cannot be input
separately. In this case both keywords are migrated to the Intersect property ADSORBED_GAS_EQUIL_CONC with
the same compositional representation as ADSORBED_GAS_INIT_CONC. As usual, GASCONC and GASADCO can
be specified later to override the initialization once the multiplier has been calculated.
• Four keywords have definitions which differ for CSG between the matrix and the fracture, and their matrix and
fracture values are both migrated, but to different Intersect properties. They are:
a. YMF. This continues to represent the initial gas composition of the pore space in the fracture. In the matrix it
represents the initial composition of the gas adsorbed on the organic matter and is migrated to the Intersect
property ORGANIC_MATTER_GAS_MOLE_FRACTION.
b. PORO. In the fracture, this continues to represent the volumetric fraction of the cell occupied by the pore space of
the fractures, i.e. the pore space porosity. In the matrix it represents the volumetric fraction of the cell occupied

Intersect and Eclipse feature compatibility | Coal Seam Gas

89
Intersect Migrator user guide

by the organic matter, and is migrated to the Intersect property ORGANIC_MATTER_GROSS_FRACTION.

When loading from data in a GSG file, it is labeled by the internal keyword COALFRAC.
c. NTG. In the fracture, this continues to represent the usual net-to-gross definition of the pore space. In the matrix
it represents the equivalent net-to-gross value of the organic matter. It is migrated to the Intersect property
ORGANIC_MATTER_NET_TO_GROSS and for GSG data loads is labeled by the internal keyword NTGCOAL.
d. MULTPV. In the fracture this continues to represent the porosity multiplier for the fracture pore space porosity. In
the matrix this is a multiplier for the organic matter volumetric fraction, i.e. a multiplier on the Intersect property
ORGANIC_MATTER_GROSS_FRACTION. It is migrated to the Intersect property
ORGANIC_MATTER_VOLUME_MULTIPLIER.
• Certain keywords are mandatory on migration, although Eclipse could default them. These are COALNUM, and PORO
or ROCKFRAC in the matrix.

Intersect and Eclipse feature compatibility | Coal Seam Gas

90
Intersect Migrator user guide

D
Support for E100 defaults
The E100 defaults supported by --preferred-defaults=E100 command line option are:

RUNSPEC
Keyword Items with supported E100 defaults (field unit system)
EQLDIMS Items: 2(100 ), 3(20 ), 5(20 )
START Items: 3(1983 )
VFPIDIMS Items: 1(0 ), 2(0 ), 3(0 )
VFPPDIMS Items: 1(0 ), 2(0 ), 3(0 ), 4(0 ), 5(0 ), 6(0 )
WELLDIMS Items: 1(0 ), 3(0 ), 4(0 )

GRID
Keyword Items with supported E100 defaults (field unit system)
AQUCT Items: 5(no default )

EDIT
Keyword Items with supported E100 defaults (field unit system)

PROPS
Keyword Items with supported E100 defaults (field unit system)
DENSITY Items: 1(no default ), 2(no default ), 3(no default )
EHYSTR Items: 2(0 )
PVTW Items: 1(no default ), 3( 0.0000000E+00 1/psi), 4( 5.0000000E-01 cP)
ROCK Items: 2( 0.0000000E+00 1/psi)

Support for E100 defaults | PROPS

91
Intersect Migrator user guide

Keyword Items with supported E100 defaults (field unit system)

RTEMP Items: 1( 6.0008000E+01 degF)
TOLCRIT Items: 1( 1.0000000E-06 )

REGIONS
Keyword Items with supported E100 defaults (field unit system)

SOLUTION
Keyword Items with supported E100 defaults (field unit system)
AQUCT Items: 5(no default )
EQUIL Items: 9(calculated )
RTEMP Items: 1( 6.0008000E+01 degF)

SUMMARY
Keyword Items with supported E100 defaults (field unit system)

SCHEDULE
Keyword Items with supported E100 defaults (field unit system)
AQUCT Items: 5(no default )
COMPDAT Items: 9(no default )
COMPDATL Items: 10(no default )
COMPDATM Items: 10(no default )
PICOND Items: 2( 0.0000000E+00 psi)
VFPPROD Items: 2( 0.0000000E+00 ft), 3(no default ), 4(no default )
WCONINJE Items: 7( 9.9976540E+04 psi)
WCONPROD Items: 9( 1.4695949E+01 psi)
WELSPECL Items: 2(no default )
WELSPECS Items: 2(no default )

Configuring Intersect nodes for E100 compatibility

The Intersect nodes that are configured by --preferred-defaults=E100 command line option are:

Support for E100 defaults | Configuring Intersect nodes for E100 compatibility
92
Intersect Migrator user guide

Intersect node Intersect field E100

keyword
CellActivity GlobalMinPVForTopLevelGrids = False
FaultPropertyEdit PostTransOverride = True MULTFLT
RegionBoundaryPropertyEdit PostTransOverride = True MULTREGT
FluidMgr OverrideBlackOilHydrocarbonMolecularWeight = True
OilTable CalculationMethod = ECLIPSE_100 PVTO
GasTable CalculationMethod = ECLIPSE_100 PVTG
OilTableUndersaturatedCompressibilities CalculationMethod = ECLIPSE_100 PVCO
DeadOilTable CalculationMethod = ECLIPSE_100 PVDO
UndersaturatedGasTable CalculationMethod = ECLIPSE_100 PVDG, PVZG
MiscibleFluidModel.SolventTable CalculationMethod = ECLIPSE_100 PVDS
BrineFluidModel. CalculationMethod = ECLIPSE_100 PVTWSALT
BrineComponentCompressibilities
Equilibrium SolutionDepthTableCalculationMethod = ECLIPSE_100
AllWellCalculationOptions WellConnectionNTGTreatment = SCALE_KH_AND_R0
AllWellCalculationOptions MaxItersRevival = 3
TubingHeadPressureCalculationOptions FlowRatioExtrapolationMethod = LINEAR
TubingHeadPressureCalculationOptions HydrostaticHeadCorrectionMethod =
TOP_CONNECTION_DENSITY, (if using Segmented
Head Density calculations)
WellDef.ResVolConditions LimitByAverageRsRv = True
RockMgr.RockOptions PrevalentRelPermEndPoint = IGNORE_CRITICAL
CarterTracy FluxEquation = ECLIPSE
CarterTracy InitialPressureCalculation = EQUILIBRIUM
CarterTracy UseNetToGrossMultiplier = TRUE
Fetkovich InitialPressureCalculation = EQUILIBRIUM
Fetkovich UseNetToGrossMultiplier = TRUE

Configuring Intersect nodes for E300 compatibility

Although Intersect default behavior is normally similar to E300, there are some exceptions. In these cases, the --
preferred-defaults=E300 option can be used to generate behavior that is more similar to E300. The Intersect
nodes that are configured by the --preferred-defaults=E300 command line option are:

Intersect node Intersect field E300

keyword
CellActivity GlobalMinPVForTopLevelGrids = True
FluidMgr OverrideBlackOilHydrocarbonMolecularWeight = True
FluidMgr ThermalProperties = ECLIPSE THERMAL
AllWellCalculationOptions MaxItersRevival = min(3,NUPCOL) General,
NUPCOL

Support for E100 defaults | Configuring Intersect nodes for E300 compatibility
93
Intersect Migrator user guide

Intersect node Intersect field E300

keyword
TubingHeadPressureCalculationOptions HydrostaticHeadCorrectionMethod =
TOP_CONNECTION_DENSITY, (if using Segmented Head
Density calculations)
RockMgr.RockOptions MaxSaturationCalculation =
ASSOCIATED_CONNATE_SATURATION
CarterTracy FluxEquation = ECLIPSE
CarterTracy InitialPressureCalculation = AVERAGE
CarterTracy UseNetToGrossMultiplier = TRUE
Fetkovich InitialPressureCalculation = AVERAGE
Fetkovich UseNetToGrossMultiplier = TRUE

E100 defaults requiring special description

WCONPROD
Intersect with E100 defaults interprets zero rate limits as zero constraints on well. Intersect default behavior is similar to
E300 where zero rate limits (applied to any item that is not the control mode's target) are treated as default,inactive limits.

Support for E100 defaults | E100 defaults requiring special description | WCONPROD
94
Intersect Migrator user guide

Glossary
AIM Adaptive Implicit solution option
Discretization Calculation of pore volumes and transmissibilities
E100 Refers to SLB's Eclipse black oil simulator
E300 Refers to SLB's Eclipse compositional simulator
HGC Heuristic Group Control for well rate allocation
IMPES Implicit Pressure Explicit Saturation solution option
IMPSAT Implicit Pressure and Saturation, Explicit Compositions solution option
Initialization Calculation of the initial solution state
LGC Local grid coarsening
LGR Local grid refinement
Petrel SLB's seismic-to-simulation software

Glossary
95