T Nav User Manual English

Reservoir Simulator
tNavigator
version 4.2
User Manual
Moscow, 2016
tNavigator-4.2
Reservoir Simulator tNavigator (version 4.2). User Manual. Moscow, 2016. 2176 pp.
The information contained in this document is subject to change without notice and should
not be construed as a commitment by RFDynamics. RFDynamics assumes no responsibility to
any error that may appear in this manual. Some states or jurisdictions do not allow disclaimer
of expressed or implied warranties in certain transactions; therefore, this statement may not
apply to you.
RFDynamics, 2004-2016
2
CONTENTS tNavigator-4.2
Press to open User Guide

Contents
Contents 3
1 Introduction 41
2 Physical model 43
2.1 Differential equations for black-oil model . . . . . . . . . . . . . . . . . . . . 43
2.2 Boundary conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.3 Initial conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.4 Permeability tensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.5 Porosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.6 Phase relative permeability . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.6.1 Linear Baker model . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.6.2 The first Stones model . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.6.3 The second Stones model . . . . . . . . . . . . . . . . . . . . . . . . 48
2.6.4 End-point scaling, two-point method . . . . . . . . . . . . . . . . . . 49
Saturations scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Relative permeabilities scaling . . . . . . . . . . . . . . . . . . . . . . 51
2.6.5 End-point scaling, three-point method . . . . . . . . . . . . . . . . . . 52
Saturations scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Relative permeabilities scaling . . . . . . . . . . . . . . . . . . . . . . 54
2.6.6 Directional and irreversible RP . . . . . . . . . . . . . . . . . . . . . 54
2.6.7 RP at dual porosity runs. . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.6.8 User-defined relative permeability of the injected phase . . . . . . . . 55
2.6.9 Corey correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.6.10 LET correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
2.6.11 Hysteresis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.6.12 Surface tension effects . . . . . . . . . . . . . . . . . . . . . . . . . . 67
2.7 Equation of state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
2.8 Phase viscosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
2.9 Phase formation volume factor . . . . . . . . . . . . . . . . . . . . . . . . . . 70
2.10 API tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
2.11 Oil Standings correlations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2.11.1 2-phase water-oil model. Dead Oil . . . . . . . . . . . . . . . . . . . 72
2.11.2 3-phase model. Dead Oil . . . . . . . . . . . . . . . . . . . . . . . . . 72
Gas saturated (below bubble point pressure) . . . . . . . . . . . . . . 72
Undersaturated (above bubble point pressure) . . . . . . . . . . . . . 73
2.12 Gas Standings correlations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.12.1 Gas Formation Volume Factor . . . . . . . . . . . . . . . . . . . . . . 74
2.12.2 Gas Viscosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.13 Phase molar density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
CONTENTS 3
2.14 Phase mass density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

2.15 Capillary pressures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
2.15.1 Oil-gas capillary pressure . . . . . . . . . . . . . . . . . . . . . . . . 76
2.15.2 Oil-water capillary pressure . . . . . . . . . . . . . . . . . . . . . . . 77
2.15.3 Capillary pressure end-point scaling . . . . . . . . . . . . . . . . . . . 77
2.15.4 Capillary pressure calculation according to Leverett J-function . . . . 78
2.16 Solubility of gas component into oil phase . . . . . . . . . . . . . . . . . . . 79
2.17 Vaporisation of oil component into gas phase . . . . . . . . . . . . . . . . . . 80
2.18 Inflow from aquifer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
2.19 Well . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
2.19.1 Well approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
2.19.2 Group control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
2.19.3 Separators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
2.19.4 Multisegment well . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
2.19.5 MULTIphase injection . . . . . . . . . . . . . . . . . . . . . . . . . 87
2.19.6 WAG injection mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
2.19.7 DCQ. Gas Field Model . . . . . . . . . . . . . . . . . . . . . . . . . . 87
2.19.8 Gas Lift Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . 88
2.19.9 Standard network option . . . . . . . . . . . . . . . . . . . . . . . . . 89
2.19.10 NETWORK option. Automatic chokes. Compressors . . . . . . . . . 89
2.19.11 Well prioritization option . . . . . . . . . . . . . . . . . . . . . . . . . 91
2.19.12 Prioritized drilling queue. Sequential drilling queue . . . . . . . . . . 92
2.20 Polymer Flood . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
2.20.1 Polymer Flood option POLYMER . . . . . . . . . . . . . . . . . . . . 93
2.20.2 Polymer flooding based on BrightWater technology . . . . . . . . . . 94
2.20.3 Polymer flood in IMEX format . . . . . . . . . . . . . . . . . . . . . 96
Polymer flood models: differences in E100 and IMEX formulation. . 96
Polymer adsorption modelling. . . . . . . . . . . . . . . . . . . . . . 97
Water viscosity calculation. . . . . . . . . . . . . . . . . . . . . . . . 97
2.21 Foam modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
2.22 Residual oil modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
2.23 Asphaltene modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
2.24 Alkaline flooding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
2.25 Surfactant injection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
2.25.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
2.26 Waters with different salinities . . . . . . . . . . . . . . . . . . . . . . . . . . 103
2.26.1 Fresh water injection into the saline reservoir . . . . . . . . . . . . . 104
2.26.2 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
2.26.3 Low salinity option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
2.27 Scale deposition model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
2.28 Dual porosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
2.28.1 RP at dual porosity runs. . . . . . . . . . . . . . . . . . . . . . . . . . 109
2.28.2 Gravity drainage option . . . . . . . . . . . . . . . . . . . . . . . . . 109
CONTENTS 4
2.29 Coal Bed Methane Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

2.30 Temperature option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
2.31 Geomechanical model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
2.31.1 Description of Geomechanical model . . . . . . . . . . . . . . . . . . 114
2.31.2 Mixture K f . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
2.31.3 The calculation of the diagonal elements of the tensor of mechanical
stress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
2.31.4 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3 Compositional model 117

3.1 Equations of state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
3.1.1 EOS in reservoir and surface conditions . . . . . . . . . . . . . . . . 118
3.2 Density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
3.3 Viscosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
3.3.1 Lohrenz-Bray-Clark Correlation . . . . . . . . . . . . . . . . . . . . . 119
3.3.2 Pedersen Correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
4 Compositional thermal model with chemical reactions 121

4.1 Basic volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
4.2 Saturations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
4.3 Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
4.4 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
4.5 Mass and molar water density . . . . . . . . . . . . . . . . . . . . . . . . . . 124
4.6 Mass and molar liquid density . . . . . . . . . . . . . . . . . . . . . . . . . . 126
4.7 Molar and mass gas density . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
4.8 Molar solid density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
4.9 Thermodynamic equilibrium condition . . . . . . . . . . . . . . . . . . . . . 129
4.10 Phase saturations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
4.11 Water viscosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
4.12 Oil viscosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
4.13 Gas viscosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
4.14 Enthalpy and heat capacity of the components . . . . . . . . . . . . . . . . . 133
4.15 Enthalpy and internal energy of the phases . . . . . . . . . . . . . . . . . . . 133
4.16 Water enthalpy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
4.17 Liquid enthalpy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
4.18 Vaporization enthalpy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
4.19 Gas phase enthalpy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
4.20 Solid phase enthalpy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
4.21 Rock enthalpy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
4.22 Default enthalpy values for stars format models . . . . . . . . . . . . . . . . 137
4.23 Block internal energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
4.24 Porosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
4.25 Pore volume of grid block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
4.26 Bulk volume of grid block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
CONTENTS 5
4.27 Bulk volume of rock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

4.28 Thermal conductivity of the grid block . . . . . . . . . . . . . . . . . . . . . 143
4.29 Chemical reactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
4.30 The heat loss between the reservoir and surroundings . . . . . . . . . . . . . 146
4.31 Heater simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
4.31.1 Heater with constant energy injection rate . . . . . . . . . . . . . . . 148
4.31.2 Heater with energy density dependent injection rate . . . . . . . . . . 148
4.31.3 Selecting of the heater operating mode depending on the defined prop-
erties E300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
4.31.4 Temperature difference dependent injection rate . . . . . . . . . . . . 149
4.31.5 Flags of automatic heating or cooling (stars) . . . . . . . . . . . . . . 149
4.32 Phase flow rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
4.33 Mass conservation equation . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
4.34 Energy conservation equation . . . . . . . . . . . . . . . . . . . . . . . . . . 150
4.35 Phase relative permeabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
4.35.1 Phase relative permeability for two-phase systems . . . . . . . . . . . 152
4.35.2 Phase relative permeabilities scaling . . . . . . . . . . . . . . . . . . . 152
Two-point phase relative permeability scaling . . . . . . . . . . . . . 153
Phase relative permeabilities free-point scaling . . . . . . . . . . . . . 156
4.35.3 Phase relative permeabilities for free-phase systems . . . . . . . . . . 159
Linear Beykers model. . . . . . . . . . . . . . . . . . . . . . . . . . 160
First Stones model. . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Second Stones model. . . . . . . . . . . . . . . . . . . . . . . . . . . 161
4.36 Calculation of the phase composition . . . . . . . . . . . . . . . . . . . . . . 161
4.36.1 Statement of the problem . . . . . . . . . . . . . . . . . . . . . . . . 161
4.37.1 Explicit specification of initial conditions . . . . . . . . . . . . . . . . 162
4.37.2 Calculations of initial conditions from hydrostatic and thermodynamic
equilibrium conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 164
5 Mathematical model 166

5.1 Space approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
5.2 Solution algorithm for time step problem . . . . . . . . . . . . . . . . . . . . 166
5.3 Time approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
5.4 Transition from physical model to system of equations . . . . . . . . . . . . . 167
5.5 Model geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5.5.1 Transmissibility calculation . . . . . . . . . . . . . . . . . . . . . . . 169
5.6 LGR Local Grid Refinement . . . . . . . . . . . . . . . . . . . . . . . . . . 170
5.7 Well Approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.7.1 Well Inflow Performance . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.7.2 Connection transmissibility calculation (CF and Kh) . . . . . . . . . . 172
5.7.3 Average permeability calculation . . . . . . . . . . . . . . . . . . . . 173
5.7.4 Pressure equivalent radius calculation . . . . . . . . . . . . . . . . . . 174
5.7.5 Mobility calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
CONTENTS 6
5.7.6 Average well bore density and connection pressure calculation . . . . 175
5.7.7 Well potential calculations . . . . . . . . . . . . . . . . . . . . . . . . 176
5.8 Modified well model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
5.8.1 Well model with generalized connections . . . . . . . . . . . . . . . . 177
5.8.2 Hydraulic fracture data . . . . . . . . . . . . . . . . . . . . . . . . . . 178
5.8.3 Hydraulic fractures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
5.8.4 Flow rate along the fracture . . . . . . . . . . . . . . . . . . . . . . . 180
5.8.5 Calculation of the inflow to the fracture from the grid block . . . . . 181
5.8.6 Total inflow from the hydraulic fracture to the well connection . . . . 182
5.8.7 Description of simulation of large amount of hydraulic fractures . . . 182
5.8.8 Fracture keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5.8.9 Simulation of plugging of well bottom zone . . . . . . . . . . . . . . 186
5.8.10 Simulation of well bottom zone dynamics: processing acids, surfactants 186
5.8.11 Well bottom zone keywords . . . . . . . . . . . . . . . . . . . . . . . 187
5.9 ASP model description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
5.9.1 Water relative permeability calculations . . . . . . . . . . . . . . . . . 189
5.9.2 Water viscosity calculations . . . . . . . . . . . . . . . . . . . . . . . 190
5.9.3 Water viscosity calculations without salt . . . . . . . . . . . . . . . . 190
5.9.4 Capillary pressure in water-oil system . . . . . . . . . . . . . . . . . . 191
5.9.5 Water mass density calculations . . . . . . . . . . . . . . . . . . . . . 191
5.10 Drainage matrix calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
5.10.1 Description of Drainage matrix . . . . . . . . . . . . . . . . . . . . . 192
5.10.2 Parameters that affect drainage matrix . . . . . . . . . . . . . . . . . . 195
5.11 Oil and gas in-place . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
5.11.1 Resources density and concentration . . . . . . . . . . . . . . . . . . 199
5.11.2 Oil and gas in-place via separators . . . . . . . . . . . . . . . . . . . 199
5.12 Phase potentials calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
5.13 2D maps for Saturation Ternary Diagram . . . . . . . . . . . . . . . . . . . . 201
5.14 Split and merge of the model . . . . . . . . . . . . . . . . . . . . . . . . . . 202
5.14.1 Special features for wells . . . . . . . . . . . . . . . . . . . . . . . . 203
5.14.2 Splitting a model in the GUI . . . . . . . . . . . . . . . . . . . . . . . 204
5.15 Reservoir Coupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
6 VFP tables generation 208

6.1 Problem decription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
6.1.1 Problem decription . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
6.2 Single Phase Flow Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
6.2.1 Friction pressure loss . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
6.2.2 Single-Phase Friction Factor (f) . . . . . . . . . . . . . . . . . . . . . 209
6.2.3 The Single Phase hydrostatic pressure drop . . . . . . . . . . . . . . . 210
6.3 Multiphase Flow Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
6.3.1 Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
6.3.2 The Griffith Correlation . . . . . . . . . . . . . . . . . . . . . . . . . 215
6.3.3 Petalas & Aziz correlation . . . . . . . . . . . . . . . . . . . . . . . . 217
CONTENTS 7
6.3.4 Beggs & Brill correlation . . . . . . . . . . . . . . . . . . . . . . . . 229

6.3.5 Orkiszewski method . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
6.3.6 Gray correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
6.3.7 Aziz, Govier and Fogarasi correlation . . . . . . . . . . . . . . . . . . 238
6.3.8 Mukherjee & Brill correlation . . . . . . . . . . . . . . . . . . . . . . 241
7 FAQ 246
7.1 Reasons for the difference in calculation results . . . . . . . . . . . . . . . . 246
7.2 The correct answer in dynamic modelling . . . . . . . . . . . . . . . . . . 250
7.2.1 Problem discretization and solution . . . . . . . . . . . . . . . . . . . 250
7.2.2 Influence of the number of cores . . . . . . . . . . . . . . . . . . . . 252
7.2.3 Influence of timestep . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
7.2.4 What can we do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
7.3 How to speed-up model calculation without its simplification . . . . . . . . . 258
7.3.1 Problem statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
7.3.2 Flow through the block . . . . . . . . . . . . . . . . . . . . . . . . . 259
7.3.3 Grid connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
7.3.4 Grid stratification factor . . . . . . . . . . . . . . . . . . . . . . . . . 263
7.3.5 Influence of smoothness of the data . . . . . . . . . . . . . . . . . . . 264
7.3.6 Influence of end-points match . . . . . . . . . . . . . . . . . . . . . . 267
7.3.7 Conservation equation . . . . . . . . . . . . . . . . . . . . . . . . . . 268
7.3.8 VFP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
8 tNavigator Console version 270

8.1 License for console tNavigator . . . . . . . . . . . . . . . . . . . . . . . . . . 270
8.2 Console version options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
9 Data files 279

9.1 Results of tNavigator calculation . . . . . . . . . . . . . . . . . . . . . . . . . 279
9.2 USER folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
9.3 Log-file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
9.4 Loadable file formats. Export file formats . . . . . . . . . . . . . . . . . . . . 283
9.4.1 Load Well Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
9.4.2 Maps. Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
9.4.3 Maps. Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
10 Units 299
11 Input data format 301

11.1 Input formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
11.2 tNavigator format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
11.3 Hybrid format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
11.3.1 Restart for hybrid models . . . . . . . . . . . . . . . . . . . . . . . . 306
11.3.2 Split and merge of hybrid models . . . . . . . . . . . . . . . . . . . . 306
CONTENTS 8
11.4 Keywords syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
12 Keywords compatible with tNavigator and E100, E300 308

12.1 Definition section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
12.1.1 RUNSPEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
12.1.2 TITLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
12.1.3 REPORTFILE / REPORTSCREEN . . . . . . . . . . . . . . . . . . . 312
12.1.4 TNAVCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
12.1.5 AIMCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
12.1.6 FLASHCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
12.1.7 VELDEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
12.1.8 TFORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
12.1.9 RPTRST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
12.1.10 OUTSOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
12.1.11 UNIFOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
12.1.12 MULTOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
12.1.13 START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
12.1.14 RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
12.1.15 RESTARTDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
12.1.16 METRIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
12.1.17 FIELD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
12.1.18 LAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
12.1.19 LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
12.1.20 BLACKOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
12.1.21 DEFINES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
12.1.22 VDEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
12.1.23 PREDEFINES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
12.1.24 OPEN_BASE_MODEL . . . . . . . . . . . . . . . . . . . . . . . . . 354
12.1.25 DIMENS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
12.1.26 TABDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
12.1.27 EQLDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
12.1.28 ACTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
12.1.29 REGDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
12.1.30 VFPIDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
12.1.31 VFPPDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
12.1.32 GPTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
12.1.33 PIMTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
12.1.34 ROCKCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
12.1.35 ROCKDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
12.1.36 WELLDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
12.1.37 FAULTDIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
12.1.38 WSEGDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
12.1.39 HEATDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
12.1.40 UDQDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
CONTENTS 9
12.1.41 UDQPARAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

12.1.42 UDADIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
12.1.43 UDTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
12.1.44 TRACERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
12.1.45 NONNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
12.1.46 SURFACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
12.1.47 SURFACTW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
12.1.48 POLYMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
12.1.49 ALKALINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
12.1.50 THERMAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
12.1.51 REACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
12.1.52 OIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
12.1.53 GAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
12.1.54 WATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
12.1.55 VAPOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
12.1.56 DISGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
12.1.57 SOLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
12.1.58 BRINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
12.1.59 LOWSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
12.1.60 TEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
12.1.61 TEMPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
12.1.62 API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
12.1.63 ASPHALTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
12.1.64 FOAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
12.1.65 MISCIBLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
12.1.66 DIFFUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
12.1.67 CART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
12.1.68 SATOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
12.1.69 NUMRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
12.1.70 KVALUES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
12.1.71 ISGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
12.1.72 NOMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
12.1.73 INCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
12.1.74 PATHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
12.1.75 IMPLICIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
12.1.76 DUALPORO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
12.1.77 DUALPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
12.1.78 COAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
12.1.79 GRAVDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
12.1.80 GRAVDRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
12.1.81 LGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
12.1.82 VISCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
12.1.83 NODPPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
CONTENTS 10
12.1.84 NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

12.1.85 CO2SOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
12.1.86 EQLOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
12.1.87 GRIDOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
12.1.88 FORMOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
12.1.89 NOSIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
12.1.90 GASFIELD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
12.1.91 GEOMECH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
12.1.92 RFD_WFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
12.1.93 AIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
12.1.94 AIMFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
12.1.95 ECHO / NOECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
12.1.96 FULLIMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
12.1.97 IMPES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
12.1.98 HWELLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
12.1.99 PETOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
12.1.100 PARALLEL / PARAOPTS . . . . . . . . . . . . . . . . . . . . . . . . 435
12.1.101 NPROCX / NPROCKY . . . . . . . . . . . . . . . . . . . . . . . . . 436
12.1.102 MESSAGE / MESSAGES / MSGFILE . . . . . . . . . . . . . . . . . 437
12.1.103 WARN / NOWARN / NOWARNEP . . . . . . . . . . . . . . . . . . . 438
12.1.104 END . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
12.1.105 ECINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
12.1.106 ECDATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
12.1.107 ECVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
12.1.108 SCDPDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
12.1.109 LGRCOPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
12.1.110 BIGMODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
12.1.111 JALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
12.1.112 SKIPSTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
12.1.113 LICENSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
12.1.114 MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
12.1.115 FMTIN/ FMTSAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
12.1.116 MULTIN/ MULTSAVE . . . . . . . . . . . . . . . . . . . . . . . . . 453
12.1.117 MONITOR/ NOMONITO . . . . . . . . . . . . . . . . . . . . . . . . 454
12.1.118 PSPLITX/ PSPLITY/ PSPLITZ . . . . . . . . . . . . . . . . . . . . . 455
12.1.119 RPTHMD/ RPTHMG/ RPTHMW . . . . . . . . . . . . . . . . . . . . 456
12.1.120 RPTISOL/ RPTPROPS/ RPTREGS/ RPTRUNSP/ RPTSCHED/
RPTSMRY/ RPTSOL . . . . . . . . . . . . . . . . . . . . . . . . . . 457
12.1.121 UNIFIN/ UNIFSAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
12.1.122 PVTGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
12.1.123 CBMOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
12.1.124 DPCDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
12.2 Grid section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
CONTENTS 11
12.2.1 GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463

12.2.2 DX / DY / DZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
12.2.3 DXV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
12.2.4 DYV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
12.2.5 DZV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
12.2.6 TOPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
12.2.7 MIDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
12.2.8 COORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
12.2.9 ZCORN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
12.2.10 ADDZCORN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
12.2.11 OLDTRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
12.2.12 NEWTRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
12.2.13 PERMX / PERMY / PERMZ . . . . . . . . . . . . . . . . . . . . . . 477
12.2.14 PERMMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
12.2.15 MULTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
12.2.16 MULTX- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
12.2.17 MULTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
12.2.18 MULTY- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
12.2.19 MULTZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
12.2.20 MULTZ- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
12.2.21 HMMLTPX / HMMLTPY / HMMLTPZ / HMMLTPXY . . . . . . . . 487
12.2.22 HMMULTX / HMMULTY / HMMULTZ / HMMLTXY / HMMULTPV488
12.2.23 HMMULTX- / HMMULTY- / HMMULTZ- . . . . . . . . . . . . . . 489
12.2.24 PORO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
12.2.25 NTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
12.2.26 DZNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
12.2.27 PORV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
12.2.28 MULTPV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
12.2.29 ACTNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
12.2.30 MINPV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
12.2.31 MINPORV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
12.2.32 MINPVV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
12.2.33 MINDZNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
12.2.34 MINROCKV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
12.2.35 MINRV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
12.2.36 PERMAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
12.2.37 FAULTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
12.2.38 MULTFLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
12.2.39 THPRESFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
12.2.40 USEFLUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
12.2.41 DUMPFLUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
12.2.42 FLUXREG / FLUXTYPE . . . . . . . . . . . . . . . . . . . . . . . . 513
12.2.43 DOMAINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
CONTENTS 12
12.2.44 SOLVDIRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515

12.2.45 RESVNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
12.2.46 COORDSYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
12.2.47 GDFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
12.2.48 NNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
12.2.49 EDITNNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
12.2.50 NNCGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
12.2.51 TRANX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
12.2.52 TRANY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
12.2.53 TRANZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
12.2.54 PINCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
12.2.55 PINCHOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
12.2.56 PINCHREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
12.2.57 PINCHNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
12.2.58 JFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
12.2.59 JFUNCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
12.2.60 JFPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
12.2.61 GRIDUNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
12.2.62 MAPAXES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
12.2.63 MAPUNITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
12.2.64 LX / LY / LZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
12.2.65 DPNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
12.2.66 DPGRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
12.2.67 SIGMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
12.2.68 SIGMAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
12.2.69 LTOSIGMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
12.2.70 SIGMAGD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
12.2.71 SIGMAGDV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
12.2.72 THCONMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
12.2.73 MULTMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
12.2.74 DZMTRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
12.2.75 DZMATRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
12.2.76 DZMTRXV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
12.2.77 MULTREGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
12.2.78 ROCKPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
12.2.79 ROCKCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
12.2.80 ROCKCONT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
12.2.81 THCGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
12.2.82 THCOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
12.2.83 THCWATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
12.2.84 THCSOLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
12.2.85 THCROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
12.2.86 SPECGRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
CONTENTS 13
12.2.87 CARFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575

12.2.88 REFINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
12.2.89 ENDFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
12.2.90 NXFIN / NYFIN / NZFIN . . . . . . . . . . . . . . . . . . . . . . . . 581
12.2.91 HXFIN / HYFIN / HZFIN . . . . . . . . . . . . . . . . . . . . . . . . 583
12.2.92 AMALGAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
12.2.93 COARSEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
12.2.94 GRIDFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
12.2.95 PLMIXNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
12.2.96 ROCKDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
12.2.97 IMPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
12.2.98 VISGRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
12.2.99 DIFFMMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
12.2.100 INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
12.2.101 RPTGRID/ RPTGRIDL . . . . . . . . . . . . . . . . . . . . . . . . . 595
12.2.102 CORNERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
12.2.103 DEACDEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
12.3 Arithmetic section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
12.3.1 EDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
12.3.2 ARITHMETIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
12.3.3 BOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
12.3.4 ENDBOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
12.3.5 ARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
12.3.6 WORK/IWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
12.3.7 IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
12.3.8 IF-THEN-ELSE-ENDIF . . . . . . . . . . . . . . . . . . . . . . . . . 616
12.3.9 BLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
12.3.10 STORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
12.3.11 SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
12.3.12 INTERPOLATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
12.3.13 MULTIPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
12.3.14 MULTIREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
12.3.15 MULTREGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
12.3.16 COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
12.3.17 COPYBOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
12.3.18 COPYREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
12.3.19 EQUALREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
12.3.20 ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
12.3.21 ADDREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
12.3.22 EQUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
12.3.23 MAXVALUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
12.3.24 MINVALUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
12.3.25 OPERATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
CONTENTS 14
12.3.26 OPERATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648

12.3.27 DEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
12.4 Region section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
12.4.1 REGIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
12.4.2 PVTNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
12.4.3 SATNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
12.4.4 SURFNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
12.4.5 SURFWNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
12.4.6 LWSLTNUM / LSNUM . . . . . . . . . . . . . . . . . . . . . . . . . 657
12.4.7 IMBNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
12.4.8 MISCNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
12.4.9 EQLNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
12.4.10 FIPNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
12.4.11 FIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
12.4.12 FIPOWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
12.4.13 FIPPATT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
12.4.14 ROCKNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
12.4.15 COALNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
12.4.16 PMANUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
12.4.17 ENDNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
12.4.18 FLUXNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
12.4.19 BNDNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
12.4.20 VISCNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
12.4.21 EOSNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
12.4.22 OPERNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
12.4.23 MULTNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
12.4.24 KRNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
12.4.25 KRNUMMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
12.4.26 IMBNUMMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
12.4.27 WH2NUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
12.4.28 WH3NUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
12.4.29 ZONES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
12.5 PVT Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
12.5.1 PROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
12.5.2 PVDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
12.5.3 PVCDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
12.5.4 PVTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
12.5.5 PVTW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
12.5.6 PVCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
12.5.7 PVDG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
12.5.8 PVTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
12.5.9 PVZG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
12.5.10 STANDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
CONTENTS 15
12.5.11 STANDG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700

12.5.12 RSCONST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
12.5.13 RSCONSTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
12.5.14 RVCONST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
12.5.15 RVCONSTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
12.5.16 ROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
12.5.17 RKTRMDIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
12.5.18 ROCKTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
12.5.19 ROCKAXES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
12.5.20 ROCKSTRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
12.5.21 ROCKOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
12.5.22 OVERBURD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
12.5.23 DENSITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
12.5.24 GRAVITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
12.5.25 APIGROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
12.6 Relative permeabilities and capillary pressures . . . . . . . . . . . . . . . . . 720
12.6.1 SWOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
12.6.2 SGOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
12.6.3 COREYWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
12.6.4 COREYGO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
12.6.5 COREYWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
12.6.6 COREYWOMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
12.6.7 COREYGOMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
12.6.8 LETWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
12.6.9 LETGO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
12.6.10 LETWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
12.6.11 SLGOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
12.6.12 SOF2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
12.6.13 SWFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
12.6.14 SGFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
12.6.15 SOF3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
12.6.16 SGWFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
12.6.17 SOMWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
12.6.18 SOMGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
12.6.19 TOLCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
12.6.20 STONE1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
12.6.21 STONE2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
12.6.22 STONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
12.6.23 STONEPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764
12.6.24 ENDSCALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
12.6.25 TZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
12.6.26 SCALECRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
12.6.27 SWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
CONTENTS 16
12.6.28 SWLPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770

12.6.29 SGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
12.6.30 SWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
12.6.31 SGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
12.6.32 SOWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
12.6.33 SOGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
12.6.34 SWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776
12.6.35 SGU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
12.6.36 ISGL, ISGCR, ISGU, ISWL, ISWLPC, ISWCR, ISWU, ISOGCR,
ISOWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
12.6.37 SCALELIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
12.6.38 ENPTVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
12.6.39 ENKRVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
12.6.40 ENPCVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
12.6.41 ENPTRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
12.6.42 KRO, KRORW, KRORG . . . . . . . . . . . . . . . . . . . . . . . . 787
12.6.43 KRW, KRWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
12.6.44 KRG, KRGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
12.6.45 IKRG, IKRGR, IKRW, IKRWR, IKRO, IKRORW, IKRORG . . . . . 790
12.6.46 PCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
12.6.47 PCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
12.6.48 SWATINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
12.6.49 PPCWMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
12.6.50 EHYSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796
12.6.51 EHYSTRR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
12.6.52 DRAINAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
12.6.53 MISCSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
12.6.54 MISCSTRR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
12.6.55 MISCEXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
12.6.56 PARACHOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
12.6.57 STOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
12.6.58 STOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
12.6.59 KRSMOOTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
12.7 Salts and tracers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
12.7.1 TRACER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
12.7.2 TRACERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
12.7.3 TRACEROPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
12.7.4 SALTPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
12.7.5 SALTTRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
12.7.6 SALTNODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
12.7.7 ESSNODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
12.7.8 PLYVISCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
12.7.9 BDENSITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
CONTENTS 17
12.7.10 TRMMULTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818

12.7.11 TRMMULTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
12.7.12 TRMTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
12.7.13 TRDCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
12.7.14 PVTWSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
12.7.15 LSALTFNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
12.8 EOR: Enhanced Oil Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . 826
12.8.1 NPROPANTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
12.8.2 PROPANTNAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
12.8.3 PROPANTTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
12.8.4 FLOWFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
12.8.5 NFLOWFTB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
12.8.6 FLOWFNAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
12.8.7 FLOWFTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
12.8.8 SURFADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
12.8.9 SURFST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
12.8.10 SURFVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
12.8.11 SURFCAPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
12.8.12 SURFROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
12.8.13 SURFADDW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
12.8.14 SURFDW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
12.8.15 SURFSTES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
12.8.16 PLYVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
12.8.17 PLYADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
12.8.18 PLYMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
12.8.19 PLMIXPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
12.8.20 PLYROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
12.8.21 PLYSHEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
12.8.22 PLYSHLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
12.8.23 ALSURFST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
12.8.24 ALSURFAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
12.8.25 ALPOLADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
12.8.26 ALKADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
12.8.27 ALKROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
12.8.28 STVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
12.8.29 WAGHYSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
12.9 Coal Bed Methane properties . . . . . . . . . . . . . . . . . . . . . . . . . . 863
12.9.1 DIFFCOAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
12.9.2 LANGMUIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
12.9.3 LANGMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
12.9.4 LANGMEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
12.9.5 DIFFCBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
12.9.6 RESORB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
CONTENTS 18
12.10Asphaltene properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871

12.10.1 ASPP1P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
12.10.2 ASPREWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
12.10.3 ASPP2P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
12.10.4 ASPPW2D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
12.10.5 ASPFLRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
12.10.6 ASPVISO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
12.10.7 CATYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878
12.11Foam properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
12.11.1 FOAMADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
12.11.2 FOAMOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881
12.11.3 FOAMROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882
12.11.4 FOAMDCYW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883
12.11.5 FOAMDCYO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884
12.11.6 FOAMMOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
12.11.7 FOAMMOBP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886
12.11.8 FOAMMOBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
12.12Residual oil properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
12.12.1 SOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
12.12.2 SOROPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890
12.13Compositional properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
12.13.1 Default component properties for compositional model. Part 1 . . . . 893
12.13.2 Default component properties for compositional model. Part 2 . . . . 894
12.13.3 COMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
12.13.4 CNAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
12.13.5 EOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
12.13.6 EOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
12.13.7 RTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
12.13.8 STCOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
12.13.9 WATERTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
12.13.10 ZI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902
12.13.11 COMPVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
12.13.12 XMFVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
12.13.13 YMFVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
12.13.14 ZMFVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907
12.13.15 NEI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
12.13.16 KVTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
12.13.17 TCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
12.13.18 TCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913
12.13.19 PCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
12.13.20 PCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
12.13.21 VCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
12.13.22 VCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
CONTENTS 19
12.13.23 VCRITVIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920

12.13.24 ZCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
12.13.25 ZCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
12.13.26 ZCRITVIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
12.13.27 MW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924
12.13.28 MWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
12.13.29 MWW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927
12.13.30 ACF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928
12.13.31 ACFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
12.13.32 BIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
12.13.33 BICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
12.13.34 OMEGAA / OMEGAB . . . . . . . . . . . . . . . . . . . . . . . . . 935
12.13.35 OMEGAAS / OMEGABS . . . . . . . . . . . . . . . . . . . . . . . . 936
12.13.36 LBCCOEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
12.13.37 LBCCOEFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
12.13.38 FACTLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
12.13.39 LILIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 940
12.13.40 PRCORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942
12.13.41 SSHIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943
12.13.42 SSHIFTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
12.13.43 EPSCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945
12.13.44 ENKRVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946
12.13.45 ENPCVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
12.13.46 ENPTVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
12.13.47 DIFFCGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 951
12.13.48 DIFFCOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
12.13.49 VDKRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953
12.13.50 VDKRGC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955
12.13.51 VDKRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
12.13.52 PEDERSEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958
12.13.53 PEDTUNE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
12.13.54 PEDTUNER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
12.13.55 NCOMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962
12.13.56 DNGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
12.13.57 SOLUBILI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
12.13.58 RSWVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965
12.14Thermal properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
12.14.1 CVTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
12.14.2 WATDENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968
12.14.3 THANALB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
12.14.4 KVCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
12.14.5 KVCRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
12.14.6 KVTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
CONTENTS 20
12.14.7 KVTABTn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975

12.14.8 KVTABLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
12.14.9 KVWI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
12.14.10 HEATCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
12.14.11 HEATCRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
12.14.12 HEATTCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
12.14.13 HEATVAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
12.14.14 HEATVAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
12.14.15 THCONR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
12.14.16 THCONSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
12.14.17 ROCKT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
12.14.18 THCONT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
12.14.19 THCONMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
12.14.20 STHERMX1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
12.14.21 STHERMX2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
12.14.22 SDREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
12.14.23 SPREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
12.14.24 SCREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999
12.14.25 STREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
12.14.26 THERMEX1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
12.14.27 THERMEX2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
12.14.28 THERMEX3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
12.14.29 PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
12.14.30 PREFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
12.14.31 CREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009
12.14.32 TREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010
12.14.33 TREFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011
12.14.34 DREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
12.14.35 DREFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
12.14.36 ZFACTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
12.14.37 ZFACT1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
12.14.38 VISCREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
12.14.39 WATVISCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019
12.14.40 OILVISCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
12.14.41 OILVISCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
12.14.42 OILVINDX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
12.14.43 OILVINDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026
12.14.44 GASVISCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
12.14.45 GASVISCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
12.14.46 REACRATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
12.14.47 REACACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035
12.14.48 REACCORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
12.14.49 REACLIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040
CONTENTS 21
12.14.50 REACCONC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043

12.14.51 REACPORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045
12.14.52 STOPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046
12.14.53 STOREAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047
12.14.54 REACPHA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
12.14.55 REACSORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
12.14.56 REACENTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051
12.14.57 SPECHA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052
12.14.58 SPECHB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
12.14.59 SPECHC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054
12.14.60 SPECHD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056
12.14.61 SPECHG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057
12.14.62 SPECHH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058
12.14.63 SPECHI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059
12.14.64 SPECHJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1060
12.14.65 HEATVAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1061
12.14.66 SPECHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062
12.14.67 SPECHT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063
12.14.68 TEMPVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1064
12.14.69 ENPTVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065
12.14.70 ENKRVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1066
12.14.71 ENPCVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067
12.14.72 ROCKV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068
12.14.73 THSVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1069
12.14.74 THWVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070
12.14.75 SPECROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071
12.14.76 SPECHEAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1072
12.14.77 CALVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073
12.14.78 CALVALR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074
12.15Initialization section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075
12.15.1 SOLUTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1076
12.15.2 EQUIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077
12.15.3 RSVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1080
12.15.4 PBVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
12.15.5 RVVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083
12.15.6 PDVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085
12.15.7 THPRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086
12.15.8 PRESSURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087
12.15.9 PRVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1089
12.15.10 SWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1090
12.15.11 SGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1092
12.15.12 SOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094
12.15.13 SSOLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096
CONTENTS 22
12.15.14 APIVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097

12.15.15 OILAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1098
12.15.16 SMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1099
12.15.17 XMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1100
12.15.18 YMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1101
12.15.19 ZMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1102
12.15.20 FIELDSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104
12.15.21 FIPSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1106
12.15.22 GPTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108
12.15.23 GPTABLEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1110
12.15.24 GPTABLE3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112
12.15.25 RECOVERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114
12.15.26 TEMPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115
12.15.27 RTEMPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1116
12.15.28 RTEMPVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117
12.15.29 WTEMPDEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1118
12.15.30 PBUB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119
12.15.31 RS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121
12.15.32 RV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123
12.15.33 PDEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125
12.15.34 DATUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126
12.15.35 DATUMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127
12.15.36 DATUMRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1128
12.15.37 TBLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1129
12.15.38 TNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131
12.15.39 TVDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133
12.15.40 ROCKSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135
12.15.41 SALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1136
12.15.42 SALTVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137
12.15.43 SRSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138
12.15.44 SURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1139
12.15.45 SPOLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1140
12.15.46 GASCONC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1141
12.15.47 GASSATC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142
12.15.48 GASCCMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143
12.15.49 RPTMAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144
12.15.50 RSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145
12.15.51 SFOAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146
12.15.52 SOILR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1147
12.15.53 ROMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1148
12.16Inflow from aquifer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1149
12.16.1 AQUDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1150
12.16.2 AQUFLUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152
CONTENTS 23
12.16.3 AQUCHWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153

12.16.4 AQUFET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155
12.16.5 AQUOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157
12.16.6 AQUFETP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1159
12.16.7 AQANTRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1161
12.16.8 AQUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1162
12.16.9 AQUTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164
12.16.10 AQUANCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165
12.16.11 AQUNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167
12.16.12 AQUCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169
12.16.13 AQUGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172
12.16.14 HMMLCTAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174
12.16.15 HMMLFTAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1175
12.17Data output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1176
12.17.1 SUMMARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177
12.17.2 RPTMAPD/RPTGRAPHD . . . . . . . . . . . . . . . . . . . . . . . . 1189
12.17.3 RPTMAPT/RPTGRAPHT . . . . . . . . . . . . . . . . . . . . . . . . 1191
12.17.4 RPTMAPL/RPTGRAPHL . . . . . . . . . . . . . . . . . . . . . . . . 1193
12.17.5 RPTONLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194
12.17.6 DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1195
12.17.7 SEPARATE / RUNSUM . . . . . . . . . . . . . . . . . . . . . . . . . 1196
12.18Schedule section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1197
12.18.1 SCHEDULE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1200
12.18.2 WELSOMIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201
12.18.3 WELSPECS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1202
12.18.4 WELSPECL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205
12.18.5 WELLSPEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1208
12.18.6 COMPDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1209
12.18.7 COMPDATL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1212
12.18.8 COMPDATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215
12.18.9 WELLTRACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1216
12.18.10 COMPDATMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1218
12.18.11 WELSEGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1221
12.18.12 WSEGTABL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1225
12.18.13 WSEGVALV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1227
12.18.14 WSEGAICD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1230
12.18.15 WSEGEXSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1233
12.18.16 WSEGFLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235
12.18.17 WFRICTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237
12.18.18 WFRICTNL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1240
12.18.19 WFRICSEG / WFRICSGL . . . . . . . . . . . . . . . . . . . . . . . . 1242
12.18.20 COMPSEGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1243
12.18.21 COMPSEGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246
CONTENTS 24
12.18.22 COMPLUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247

12.18.23 COMPLMPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1249
12.18.24 COMPORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1251
12.18.25 COMPINJK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253
12.18.26 WLIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255
12.18.27 WLISTDYN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1257
12.18.28 WPIMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1259
12.18.29 WPIMULTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1262
12.18.30 WPITAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1265
12.18.31 PIMULTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1266
12.18.32 COMPRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1267
12.18.33 WINJMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269
12.18.34 WCONPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1271
12.18.35 WCONHIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1275
12.18.36 WCONINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1278
12.18.37 WCONINJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281
12.18.38 WCONINJP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283
12.18.39 WCONINJH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1286
12.18.40 WELLINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1289
12.18.41 GRUPINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1292
12.18.42 WCYCLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1295
12.18.43 WELLWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1297
12.18.44 WWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299
12.18.45 WHISTCTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1303
12.18.46 WCUTBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304
12.18.47 GCUTBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306
12.18.48 WBHGLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1308
12.18.49 WTMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1310
12.18.50 WTADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1312
12.18.51 WELTARG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1313
12.18.52 WELLTARG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315
12.18.53 WELCNTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1316
12.18.54 GRUPTARG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317
12.18.55 WELPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1318
12.18.56 VFPINJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1319
12.18.57 VFPPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1322
12.18.58 VFPCHK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1326
12.18.59 VFPTABL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1327
12.18.60 WVFPEXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1328
12.18.61 VFPCORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1330
12.18.62 WECON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1333
12.18.63 WECONX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337
12.18.64 WECONCMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1339
CONTENTS 25
12.18.65 WGORPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1340

12.18.66 WELLLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1342
12.18.67 CECON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1343
12.18.68 WECONINJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1345
12.18.69 WEFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346
12.18.70 GEFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1347
12.18.71 WORKTHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1348
12.18.72 GCONPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1349
12.18.73 GUIDERAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1353
12.18.74 WREGROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1356
12.18.75 GCONPRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1358
12.18.76 GPMAINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1361
12.18.77 GPMAINT3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1363
12.18.78 PRIORITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1366
12.18.79 WELPRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368
12.18.80 WGRUPCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1370
12.18.81 GCONINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1372
12.18.82 GCONSUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1375
12.18.83 GSATPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1376
12.18.84 GSATINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1378
12.18.85 GRUPTREE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1380
12.18.86 DGRDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1381
12.18.87 BRANPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1382
12.18.88 NODEPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384
12.18.89 NCONSUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387
12.18.90 GNETDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1388
12.18.91 GNETINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1390
12.18.92 NETCOMPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1392
12.18.93 COMPOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1395
12.18.94 NWATREM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1396
12.18.95 GNETPUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1398
12.18.96 GRUPNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1399
12.18.97 DRSDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1401
12.18.98 DRSDTVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1402
12.18.99 DRSDTVPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1403
12.18.100DRVDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404
12.18.101COMPENSATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1405
12.18.102GECON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1406
12.18.103GRUPLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1408
12.18.104WELDRAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1409
12.18.105DATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1412
12.18.106TSTEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1415
12.18.107WELOPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1416
CONTENTS 26
12.18.108WELOPENL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1418
12.18.109WELLOPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1420
12.18.110CVCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421
12.18.111MATCORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1422
12.18.112NETBALAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1423
12.18.113WSEGITER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1424
12.18.114TUNING / TUNINGDP / TUNINGL / TUNINGS . . . . . . . . . . . 1425
12.18.115TIGHTENP / TSCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . 1426
12.18.116ZIPPY2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1427
12.18.117NEXTSTEP / NSTACK . . . . . . . . . . . . . . . . . . . . . . . . . 1428
12.18.118LGRLOCK / LGRFREE . . . . . . . . . . . . . . . . . . . . . . . . . 1429
12.18.119RUNCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1430
12.18.120MULTSIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1439
12.18.121MULTSIGV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1440
12.18.122WFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1441
12.18.123WFRACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444
12.18.124WFRACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1447
12.18.125WFRACPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1456
12.18.126COMPFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1460
12.18.127COMPFRACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1463
12.18.128WPIFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1466
12.18.129WSKFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468
12.18.130WBHZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1470
12.18.131ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1472
12.18.132ACTIONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1474
12.18.133ACTIONR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1477
12.18.134ACTIONW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1479
12.18.135ACTIONX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1482
12.18.136DELAYACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1488
12.18.137ENDACTIO / ENDACTION . . . . . . . . . . . . . . . . . . . . . . 1490
12.18.138UDQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1491
12.18.139UDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1495
12.18.140ACTIONC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1498
12.18.141WLIMTOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1503
12.18.142SEPVALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1504
12.18.143GSEPCOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506
12.18.144SEPCOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1507
12.18.145WSEPCOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1509
12.18.146WDFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1510
12.18.147WDFACCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1511
12.18.148WTRACER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1513
12.18.149WSURFACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1514
12.18.150WALKALIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1515
CONTENTS 27
12.18.151WPOLYMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1516
12.18.152WSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517
12.18.153WTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1518
12.18.154WHTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1519
12.18.155WINJTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1520
12.18.156WINJWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1521
12.18.157HEATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1522
12.18.158WTEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1523
12.18.159WELLSTRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1525
12.18.160COMPMOBI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1526
12.18.161COMPMBIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1528
12.18.162WINJMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1530
12.18.163WINJORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1532
12.18.164WINJGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1534
12.18.165GINJGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1536
12.18.166GADVANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1538
12.18.167GRUPSALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1539
12.18.168GCONSALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1540
12.18.169GRUPFUEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1542
12.18.170WTAKEGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1543
12.18.171WAVAILIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1544
12.18.172SWINGFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1545
12.18.173GSWINGF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1547
12.18.174GDCQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549
12.18.175GASYEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1551
12.18.176GASPERIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1554
12.18.177DCQDEFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1557
12.18.178GDCQECON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558
12.18.179GASBEGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559
12.18.180GASEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1561
12.18.181GASMONTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1562
12.18.182WGASPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1563
12.18.183GASFTARG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1564
12.18.184GASFDECR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1565
12.18.185GASFCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1566
12.18.186WVFPDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1567
12.18.187PICOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1569
12.18.188WPAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1571
12.18.189WPAVEDEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1575
12.18.190WRFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1576
12.18.191WRFTPLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1577
12.18.192SKIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1579
12.18.193SKIPREST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1580
CONTENTS 28
12.18.194SKIP100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1581
12.18.195SKIP300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1582
12.18.196SKIPTNAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1583
12.18.197SKIPOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1584
12.18.198SKIPON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1586
12.18.199ENDSKIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1587
12.18.200DRILPRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1588
12.18.201WDRILPRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1590
12.18.202WDRILTIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1591
12.18.203QDRILL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1592
12.18.204GDRILPOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1593
12.18.205WDRILRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1594
12.18.206WORKLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1595
12.18.207GRUPRIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1596
12.18.208NUPCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1598
12.18.209WELLOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1599
12.18.210GCONTOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1600
12.18.211WLIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1601
12.18.212PRORDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1604
12.18.213LIFTOPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1606
12.18.214GLIFTLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1607
12.18.215GLIFTOPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1608
12.18.216WLIFTOPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609
12.18.217OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1611
12.18.218RECU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614
12.18.219USERFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1616
12.18.220COMPVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1617
12.18.221COMPVALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1618
12.18.222WNETDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1620
12.18.223WELLPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1621
12.18.224GRUPPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1624
12.18.225WELLCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1626
12.18.226TRANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1628
12.18.227SCDPTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1629
12.18.228SCDPTRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1630
12.18.229SCDATAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1631
12.18.230WSCTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1632
12.18.231WSEGCNTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1633
12.18.232PSEUPRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1634
12.18.233GWRATMUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1635
12.18.234APILIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1636
12.18.235AUTOSAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1637
12.18.236WELLGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1638
CONTENTS 29
12.18.237SLAVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1640
12.18.238GRUPMAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1641
12.18.239GRUPSLAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1643
12.18.240CSKIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1645
12.18.241WFOAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1646
13 Keywords compatible with tNavigator and IMEX, STARS, GEM 1647

13.1 Data entry system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1648
13.1.1 MATRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1649
13.1.2 FRACTURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1650
13.1.3 CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1651
13.1.4 IVAR / JVAR / KVAR . . . . . . . . . . . . . . . . . . . . . . . . . . 1652
13.2 Input/Output Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1653
13.2.1 TITLE1 / TITLE2 / TITLE3 . . . . . . . . . . . . . . . . . . . . . . . 1654
13.2.2 INUNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1655
13.3 Reservoir description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1656
13.3.1 GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1657
13.3.2 DI / DJ / DK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1658
13.3.3 ZCORN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1659
13.3.4 COORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1660
13.3.5 DUALPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1661
13.3.6 SHAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1662
13.3.7 DIFRAC / DJFRAC / DKFRAC . . . . . . . . . . . . . . . . . . . . . 1663
13.3.8 NULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1664
13.3.9 POR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1665
13.3.10 PERMI / PERMJ / PERMK . . . . . . . . . . . . . . . . . . . . . . . 1666
13.3.11 NETGROSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1667
13.3.12 PINCHOUTARRAY . . . . . . . . . . . . . . . . . . . . . . . . . . . 1668
13.3.13 VOLMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1669
13.3.14 NETPAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1670
13.3.15 AQLEAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1671
13.3.16 AQMETHOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1672
13.3.17 AQVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1673
13.3.18 AQPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1674
13.3.19 AQUIFER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676
13.3.20 AQFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1677
13.3.21 DUALPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1678
13.3.22 CORNERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1679
13.3.23 CROCKTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1681
13.3.24 CTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1682
13.3.25 CCPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1683
13.3.26 CROCKTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1684
13.3.27 TRANSI / TRANSJ / TRANSK . . . . . . . . . . . . . . . . . . . . . 1685
13.3.28 TRANLI / TRANLJ / TRANLK . . . . . . . . . . . . . . . . . . . . . 1686
CONTENTS 30
13.3.29 TRANSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1687

13.3.30 FRFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1688
13.3.31 FORMINFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1689
13.3.32 SECTORARRAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1690
13.3.33 DEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1691
13.3.34 DTOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1692
13.3.35 PVCUTOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1693
13.3.36 REFINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1694
13.3.37 SCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1695
13.4 Other Reservoir Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1696
13.4.1 ROCKTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1697
13.4.2 THTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1698
13.4.3 ROCKCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1699
13.4.4 PRPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1700
13.4.5 CPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1701
13.4.6 CTPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1702
13.4.7 CPTPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1703
13.4.8 THCONR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704
13.4.9 THCONW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1705
13.4.10 THCONO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1706
13.4.11 THCONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1707
13.4.12 THCONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1708
13.4.13 THCONMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1709
13.4.14 HLOSST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711
13.4.15 HLOSSTDIFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1712
13.4.16 HLOSSPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1713
13.4.17 CPORPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1714
13.4.18 PORMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1715
13.4.19 PBASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1716
13.4.20 CPEPAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1717
13.4.21 PDILA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1718
13.4.22 CRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1719
13.4.23 PORRATMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1720
13.4.24 PPACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1721
13.4.25 FR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1722
13.4.26 CTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1723
13.4.27 CTPPAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1724
13.4.28 DILATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1725
13.5 Component properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1726
13.5.1 K_SURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1727
13.5.2 SURFLASH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1728
13.5.3 MOLVOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1729
13.5.4 MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1730
CONTENTS 31
13.5.5 PVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1732

13.5.6 DENSITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1734
13.5.7 BWI / CW / REFPW / CVW / VWI . . . . . . . . . . . . . . . . . . 1735
13.5.8 PTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1736
13.5.9 COMPNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1737
13.5.10 PRSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1738
13.5.11 TEMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1739
13.5.12 PSURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1740
13.5.13 TSURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1741
13.5.14 MOLDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1742
13.5.15 MASSDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1743
13.5.16 CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744
13.5.17 CT1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1745
13.5.18 CT2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1746
13.5.19 CPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1747
13.5.20 PCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1748
13.5.21 TCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1749
13.5.22 SOLID_DEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1750
13.5.23 SOLID_CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751
13.5.24 KVTABLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1752
13.5.25 KVTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1753
13.5.26 KV1 / KV2 / KV3 / KV4 / KV5 . . . . . . . . . . . . . . . . . . . . 1754
13.5.27 CPL1 / CPL2 / CPL3 / CPL4 . . . . . . . . . . . . . . . . . . . . . . 1755
13.5.28 CPG1 / CPG2 / CPG3 / CPG4 . . . . . . . . . . . . . . . . . . . . . 1756
13.5.29 HVAPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1758
13.5.30 HVR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1759
13.5.31 EV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1760
13.5.32 STOREAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1761
13.5.33 STOPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1762
13.5.34 FREQFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1763
13.5.35 FREQFACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1764
13.5.36 EACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1765
13.5.37 EACT_TAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1766
13.5.38 RENTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1767
13.5.39 RORDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1768
13.5.40 RPHASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1769
13.5.41 RTEMUPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1770
13.5.42 RTEMLOWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1771
13.5.43 RXCRITCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1772
13.5.44 O2PP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1773
13.5.45 VSTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1774
13.5.46 VISCTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1775
13.5.47 VISCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1776
CONTENTS 32
13.5.48 VISVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1777

13.5.49 VISCOEFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1778
13.5.50 MIXVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1779
13.5.51 AVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1780
13.5.52 BVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1781
13.5.53 VISCTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1782
13.5.54 VSMIXCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1784
13.5.55 VSMIXENDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1785
13.5.56 VSMIXFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1786
13.5.57 AVG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1787
13.5.58 BVG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1788
13.5.59 CMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1789
13.5.60 GASD-ZCOEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1790
13.5.61 GASLIQKV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1791
13.5.62 COT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1792
13.5.63 CO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1793
13.5.64 BOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1794
13.5.65 CVO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1795
13.5.66 VOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1796
13.5.67 IDEALGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1797
13.5.68 EOSSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1798
13.5.69 EOSTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1799
13.5.70 BIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1800
13.5.71 PCHOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1801
13.5.72 AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1802
13.5.73 OMEGA / OMEGB . . . . . . . . . . . . . . . . . . . . . . . . . . . 1803
13.5.74 VSHIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1804
13.5.75 VGUST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1805
13.5.76 PADSORP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1806
13.5.77 PPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1807
13.5.78 PMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1808
13.5.79 PREFCONC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1809
13.5.80 PVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1810
13.5.81 INCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1811
13.6 Rock-Fluid data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1812
13.6.1 ROCKFLUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1813
13.6.2 RPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1814
13.6.3 SWT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1815
13.6.4 SLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1816
13.6.5 SGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1818
13.6.6 RTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1820
13.6.7 KRTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1821
13.6.8 KRTEMTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1822
CONTENTS 33
13.6.9 SWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1824

13.6.10 BSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1825
13.6.11 SWCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1826
13.6.12 BSWCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1827
13.6.13 SOIRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1828
13.6.14 BSOIRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1829
13.6.15 SGCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1830
13.6.16 BSGCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1831
13.6.17 SGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1832
13.6.18 BSGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1833
13.6.19 SOIRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1834
13.6.20 BSOIRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1835
13.6.21 SORW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1836
13.6.22 BSORW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1837
13.6.23 SORG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1838
13.6.24 BSORG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1839
13.6.25 KRWIRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1840
13.6.26 BKRWIRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1841
13.6.27 KRGCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1842
13.6.28 BKRGCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1843
13.6.29 KROCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1844
13.6.30 BKROCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1845
13.6.31 PCGEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1846
13.6.32 BPCGMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1847
13.6.33 PCWEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1848
13.6.34 BPCWMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1849
13.6.35 PTHRESHI / PTHRESHJ / PTHRESHK . . . . . . . . . . . . . . . . 1850
13.7.1 INITIAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1852
13.7.2 VERTICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1853
13.7.3 SWINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1854
13.7.4 PB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1855
13.7.5 DATUMDEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1856
13.7.6 INITREGION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1857
13.7.7 INTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1858
13.7.8 REFPRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1859
13.7.9 REFDEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1860
13.7.10 DWOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1861
13.7.11 DGOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1862
13.7.12 WOC_SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1863
13.7.13 SO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1864
13.7.14 SG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1865
13.7.15 SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1866
CONTENTS 34
13.7.16 PRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1867

13.7.17 TEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1868
13.7.18 CONC_SLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1869
13.7.19 MFRAC_OIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1870
13.7.20 MFRAC_GAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1871
13.7.21 PBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1872
13.7.22 SEPARATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1873
13.8 Numerical methods control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1875
13.8.1 NUMERICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1876
13.8.2 TFORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1877
13.8.3 ISOTHERMAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1878
13.8.4 MINTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1879
13.8.5 MAXTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1880
13.9 Well and recurrent data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1881
13.9.1 HEATR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1882
13.9.2 TMPSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1883
13.9.3 UHTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1884
13.9.4 RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1885
13.9.5 DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1886
13.9.6 WELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1887
13.9.7 PRODUCER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1888
13.9.8 INJECTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1889
13.9.9 SHUTIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1890
13.9.10 OPERATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1891
13.9.11 ALTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1893
13.9.12 GEOMETRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1894
13.9.13 PERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1896
13.9.14 LAYERXYZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1898
13.9.15 TINJW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1900
13.9.16 QUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1901
13.9.17 WTMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1902
13.9.18 ON-TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1903
13.9.19 STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1904
13.9.20 HTWELL / HTWRATE / HTWRATEPL / HTWTEMP / HTWI . . . 1905
13.9.21 WELSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1906
13.9.22 TRIGGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1907
14 Keywords compatible with tNavigator and MORE 1912

14.1 INPUt Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1913
14.1.1 INPUt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1914
14.1.2 TITLe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1915
14.1.3 PRINt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1916
14.1.4 UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1917
14.1.5 IDATe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1918
CONTENTS 35
14.1.6 SDATe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1919

14.1.7 CNAMe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1920
14.1.8 IMPLicit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1921
14.1.9 INCLude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1922
14.1.10 SCMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1923
14.1.11 DPORo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1924
14.1.12 EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1925
14.1.13 EPSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1926
14.1.14 DWPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1927
14.1.15 OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1928
14.1.16 ETUNe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1929
14.1.17 GPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1930
14.1.18 MPGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1931
14.1.19 RG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1932
14.2 FLUId Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1933
14.2.1 FLUId . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1934
14.2.2 WATR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935
14.2.3 BASIc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1936
14.2.4 TEMPerature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1937
14.2.5 OPVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1938
14.2.6 GPVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1939
14.2.7 EQUA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1940
14.2.8 KVSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1941
14.2.9 KVPX / KVPY / KVPZ . . . . . . . . . . . . . . . . . . . . . . . . . 1942
14.2.10 OPVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1943
14.2.11 OMGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1944
14.2.12 OMGB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945
14.2.13 VOLU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1946
14.2.14 SDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1947
14.2.15 VCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1948
14.2.16 F(DE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1949
14.2.17 INTE (FLUID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1950
14.2.18 PROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1951
14.2.19 TRAC (FLUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1952
14.3 RELAtive Permeability Data Section . . . . . . . . . . . . . . . . . . . . . . 1953
14.3.1 RELA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1954
14.3.2 WETT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955
14.3.3 KRWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1956
14.3.4 KRGO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1957
14.4 GRID Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1958
14.4.1 GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1959
14.4.2 VERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1960
14.4.3 HORI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1961
CONTENTS 36
14.4.4 SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1962

14.4.5 DATUm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1963
14.4.6 X-DIrection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1964
14.4.7 Y-DIrection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965
14.4.8 DEPTh / ZGRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1966
14.4.9 THICkness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1967
14.4.10 POROsity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1968
14.4.11 MINPv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1969
14.4.12 K_X / K_Y / K_Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1970
14.4.13 CROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1971
14.4.14 REFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1972
14.4.15 ACTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1973
14.4.16 COORd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1974
14.4.17 FIPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975
14.4.18 SATNum / ROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1976
14.4.19 AQCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1977
14.4.20 AQCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1978
14.4.21 AQCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1979
14.4.22 AQFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1981
14.4.23 AQUW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1982
14.4.24 CONS (GRID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1983
14.4.25 DEFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1984
14.4.26 DPSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1985
14.4.27 FSAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1986
14.4.28 FSWA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987
14.4.29 FPVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1988
14.4.30 PVTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1989
14.4.31 DZMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1990
14.4.32 EQUI / EQLN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1991
14.4.33 F(PO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1992
14.4.34 FAUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1993
14.4.35 FMUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1994
14.4.36 FCRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1995
14.4.37 FKX / FKY / FKZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1996
14.4.38 FMLX / FMLY / FMLZ . . . . . . . . . . . . . . . . . . . . . . . . . 1997
14.4.39 FEQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1998
14.4.40 FPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1999
14.4.41 FREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2000
14.4.42 IEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2001
14.4.43 INTE (GRID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2002
14.4.44 KPTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2004
14.4.45 LAYE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2005
14.4.46 LEVJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2006
CONTENTS 37
14.4.47 LGRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2007

14.4.48 MINDznet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2008
14.4.49 MODI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2009
14.4.50 MULX / MULY / MULZ (MX / MY / MZ, M_X / M_Y / M_Z, M-X
/ M-Y / M-Z, MULTX / MULTY / MULTZ) . . . . . . . . . . . . . . 2011
14.4.51 PINCh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2012
14.4.52 PORV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2013
14.4.53 PVOL / RVOL / PVR . . . . . . . . . . . . . . . . . . . . . . . . . . 2014
14.4.54 T_X / T_Y / T_Z (TX / TY / TZ, T-X / T-Y / T-Z) . . . . . . . . . . 2016
14.4.55 VARI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2018
14.4.56 NNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2019
14.4.57 NTG / NTOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2020
14.4.58 REPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2021
14.4.59 SGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2022
14.4.60 SGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2023
14.4.61 SGU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2024
14.4.62 SOGC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2025
14.4.63 SOWC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2026
14.4.64 SWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2027
14.4.65 SWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2028
14.4.66 SWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2029
14.4.67 XKRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2030
14.4.68 XKRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2031
14.4.69 XKRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2032
14.4.70 XPCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2033
14.4.71 XPCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2034
14.4.72 YKRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2035
14.4.73 ZCORn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2036
14.4.74 ZVAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2037
14.4.75 TSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2038
14.5 INIT Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2040
14.5.1 INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2041
14.5.2 PBVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2042
14.5.3 RSVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2043
14.5.4 EQUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2044
14.5.5 RVVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2045
14.5.6 CONS (INIT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2046
14.5.7 GOCX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2048
14.5.8 GOCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2049
14.5.9 SEPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2050
14.6 RECUrrent Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2051
14.6.1 RECU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2052
14.6.2 RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2053
CONTENTS 38
14.6.3 EFILe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2054

14.6.4 TFIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2056
14.6.5 ETAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2058
14.6.6 TTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2062
14.6.7 ENDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2063
14.6.8 ENDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2064
14.6.9 HFILe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2065
14.6.10 HTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2067
14.6.11 ENDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2068
14.6.12 EFORm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2069
14.6.13 HFORm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2071
14.6.14 EUNIts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2073
14.6.15 HUNIts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2074
14.6.16 PERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2075
14.6.17 SQUEeze . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2077
14.6.18 PROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2079
14.6.19 INJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2080
14.6.20 LTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2081
14.6.21 PREX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2082
14.6.22 P-RE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2083
14.6.23 WELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2084
14.6.24 WWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2086
14.6.25 WFRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2087
14.6.26 WFRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2089
14.6.27 SHUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2093
14.6.28 STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2094
14.6.29 HOIL / HGAS / HWAT / HLIQ / HRES / HBHP / HTHP / HWEF . . 2095
14.6.30 TUBI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2096
14.6.31 FLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2099
14.6.32 THP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2101
14.6.33 RATI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2102
14.6.34 BHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2103
14.6.35 OPEN (RECU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2104
14.6.36 DREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2105
14.6.37 XFLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2106
14.6.38 BHPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2107
14.6.39 THPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2108
14.6.40 OPT / WPT / GPT / LPT / VPT . . . . . . . . . . . . . . . . . . . . . 2109
14.6.41 OIT / GIT / WIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2110
14.6.42 WEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2111
14.6.43 STRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2112
14.6.44 GOPT / GGPT / GWPT / GLPT . . . . . . . . . . . . . . . . . . . . 2113
14.6.45 HOURS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2114
CONTENTS 39
14.6.46 DATE / READ / TIME . . . . . . . . . . . . . . . . . . . . . . . . . 2115

14.6.47 GROU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2116
14.6.48 DRAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2117
14.6.49 VREP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2118
14.6.50 RECY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2119
14.6.51 GGRT / GWRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2120
14.6.52 CWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2121
14.6.53 KMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2122
14.6.54 PARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2123
14.6.55 PCSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2124
14.6.56 GVRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2125
14.6.57 PLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2126
14.6.58 CIJK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2127
14.6.59 ARRAy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2129
14.6.60 FREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2130
14.6.61 DELTa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2131
14.6.62 COMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2132
14.6.63 BRANch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2134
14.6.64 TRAC (RECU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2135
14.6.65 WGPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2136
14.6.66 WMPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2137
14.6.67 WRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2138
15 Keyword definitions index E100, E300 2139
16 Keyword definitions index IMEX, STARS, GEM 2158
17 Keyword definitions index RFD 2165
18 Keyword definitions index MORE 2169
19 The bibliography 2175
CONTENTS 40
1. Introduction tNavigator-4.2
1 Introduction
Simulator tNavigator can be used for numerical solution of three phase three (or multi)
component filtration problems:
isothermic systems (black-oil or compositional) section 2;
temperature option, to allow the modeling of the temperature effects of cold water
injection section 2.30;
thermal compositional model with chemical reactions section 4.
List of supported operating systems: Windows, Linux (32-bit and 64-bit versions).
Note. In Windows systems family it is recommended to turn off antivirus on user folder
to increase performance. In Windows systems version 8 and above antivirus is turned on by
default.
Requirements for RAM per core.

We have no minimal requirements for RAM per core. Everything depends on model. We use
3kB RAM per active grid block for black-oil models.
An example for cluster with the following configuration: Xeon 5650 node, 12 cores,
24Gb.
One node simulation. We can run 24000k/3k=8million active grid blocks. We have
run successfully the real model 6.5 million blocks on cluster with this configuration.
MPI-version. Simulation on several nodes. For MPI run maximal size of the model
multiplies by number of nodes per run. For the cluster with this configuration we can
run model with 12 million active grid blocks using 2 nodes and 23 million active with
4 nodes (there is small overhead for domains overlapping in MPI run so maximal size
is less than theoretical maximum).
Simulator uses finite volume approximation on rectangular block centered mesh with re-
spect to space. For approximation with respect to time Fully Implicit method or Adaptive
Implicit (AIM) are used.
Hydrodynamic simulator tNavigator is recommended for calculation of oil and gas field
development plan projects.
This User Manual describes physical model, mathematical model and the keywords.
The description of tNavigatoruser graphical interface: graphs, maps visualization and edit-
ing, model calculation, is in the document User Guide.
For best adaptation of user experience the keyword notations are chosen to be close as
much as possible to the most common simulators:
1. Introduction 41
1. Introduction tNavigator-4.2
Eclipse (c) Schlumberger,
IMEX, STARS, GEM (c) Computer Modelling Group Ltd,
MORE (c) Roxar.
tNavigator reads keyword notations of these simulators and converts them into its inner
data notations.
This User Manual describes all keywords which can be used in tNavigator:
tNavigator keywords;
E100 keywords;
E300 keywords;
CMG IMEX keywords;
CMG STARS keywords;
CMG GEM keywords;
MORE keywords.
In the description of each keyword in the table the boxes are checked corresponding fo
model formats in which the keyword can be used.
E100, E300 format keywords are red. For example: TABDIMS (see 12.1.26). Index of
Eclipse format keywords 15.
IMEX, STARS, GEM format keywords are pink. For example: TEMR (see 13.5.11). Index
of CMG format keywords 16.
MORE format keywords are green. For example: IDATe (see 14.1.5). Index of MORE
format keywords 18.
The keywords that can be used only in tNavigator are blue. For example: REACCONC
(see 12.14.50). Index of RFD format keywords 17.
This description pointed out if there are parameters of the keyword which are ignored by
tNavigator or which use is different from other simulators: Eclipse, IMEX, STARS, GEM,
MORE).
tNavigator simulator is subject to future development. Any feedback is appreciated.
1. Introduction 42
2.1. Differential equations for black-oil model tNavigator-4.2
2 Physical model
Simulator uses standard three phase three component isothermal black-oil model and compo-
sitional model. The description of thermal compositional model with chemical reactions is in
the section 4.
2.1 Differential equations for black-oil model

Standard black-oil equations with standard assumptions:
k
rP
( Nc ) = div xc,P P k (pP P D) + qc , c = 1, . . . , nc (2.1)
t P=O,W,G P
pO pG = PcOG , (2.2)
pO pW = PcOW , (2.3)
SW + SO + SG = 1. (2.4)
Here functions:
Nc = Nc (t, x, y, z) (unknown) c = 1, . . . , nc overall molar density of any component.

For black oil model components are water, oil and gas, and
SW SO SG SG SO
Nw = W,SC ; No = O,SC ( + RO,G ); Ng = G,SC ( + RG,O )
BW BO BG BG BO
SP = SP (t, x, y, z) (unknown) phase P, P = O, G,W saturation,
RG,O = RG,O (pO ) solubility of gas component into oil phase (known function)
(see 2.16),
RO,G = RO,G (pO ) vaporisation of oil component into gas phase (known function)
(see 2.17),
BP = BP (pP ) phase formation volume factor (known function) (see 2.9),
P = (pP , x, y, z) porosity (known functions) (see 2.5),
pW = pW (t, x, y, z) (unknown) water phase pressure,
pO = pO (t, x, y, z) (unknown) oil phase pressure,
pG = pG (t, x, y, z) (unknown) gas phase pressure,
xc,P = xc,P (p, N) (known function) moles of component c per mole of phase P,
P = P (p, N) phase molar density (known function), see section 2.13,
k = k(pW , pO , pG , x, y, z) permeability tensor (known function) (see 2.4),
2. Physical model 43
2.2. Boundary conditions tNavigator-4.2
krP = krP (SW , SG ) phase relative permeability (known function) (see 2.6),
P = P (pP ) phase viscosity (known function) (see 2.8),
P = P g vertical pressure gradient (known relation),
D = D(x, y, z) vertical depth vector (up-down oriented) (known coordinate functions),
P = P (pP ) phase mass density (known function) (see 2.14),
PcOG = PcOG (SG ) oil-gas capillary pressure (known function) (see 2.15.1),
PcOW = PcOW (SW ) oil-water capillary pressure (known function) (see 2.15.2),
qc = qc (p, N,t, x, y, z) source of component (known function) (see 2.19.1)
and constant(s):
g = const known constant
The detailed description of transition from physical model to non-linear and then linear
equations is written in the section Mathematical model 5.
The keyword RUNCTRL (see 12.18.119) controls the solution algorithms and the param-
eters of iteration process.
Let us define the ways of known data input.
2.2 Boundary conditions

The standard constant pressure (Dirichlet)
pP = constP (2.5)
boundary conditions or standard no flow (Neumann)
pP
= P (pP P D), n = 0 (2.6)
N
krP
boundary conditions are used on outer reservoir boundary. Here P = k .
BP P
2.2. Boundary conditions 44

2.6. Phase relative permeability tNavigator-4.2
2.3 Initial conditions

Initial conditions may either all known values for pP , SP (from previous run of the model)
or values for pP , SP may be computed from hydrostatic equilibrium conditions:
k
rP
div xc,P P k (pP P D) = 0 (2.7)
P=O,W,G P
pO pG = PcOG (2.8)
pO pW = PcOW (2.9)
SW + SO + SG = 1 (2.10)
with boundary conditions from 2.2.

EQUIL (see 12.15.2) specifies initial values for pP , SP (PRESSURE (see 12.15.8), SGAS
(see 12.15.11), SWAT (see 12.15.10), SOIL (see 12.15.12), SWATINIT (see 12.6.48)).
2.4 Permeability tensor

Absolute permeability tensor k = k(pW , pO , pG , x, y, z) is user input data array function defined
in all reservoir points. PERMX / PERMY / PERMZ (see 12.2.13) On default dependence
of k on pressure is omitted. One can specify this dependence using the keyword ROCKTAB
(see 12.5.18).
2.5 Porosity
Porosity = (p, x, y, z) is user input data function defined in all reservoir points. Usually it
is represented in the following form:
(p, x, y, z) = (x, y, z) (x, y, z)(1 + c(p pref ) + c2 (p pref )2 /2)
where
(x, y, z) net to gross (user input data array defined in all reservoir points, NTG (see
12.2.25) or DZNET (see 12.2.26))
(x, y, z) porosity at pressure pref (user input data array defined in all reservoir
points, PORO (see 12.2.24))
c compressibility (user input data, ROCK (see 12.5.16) or ROCKTAB (see 12.5.18))
pref reference pressure (user input data, ROCK (see 12.5.16))
2.6 Phase relative permeability

Calculation of phase relative permeabilities contains the following stages:
1. Permeabilities and capillary pressure are calculated for two-phase systems wateroil
and gasoil.
2.3. Initial conditions 45

2. Relative permeabilities (and capillary pressure) scaling for two-phase systems.
3. Oil relative permeability krO is calculated using the first or the second Stones model
or linear Bakers model (default model).
Phase relative permeability krP = krP (SW , SG ) are defined by experimental data. The usual
assumptions are:
krW = krW (SW ) (2.11)

krG = krG (SG ) (2.12)
krO = krO (SW , SG ) (2.13)
User specifies two sets of relative permeabilities function pairs:
krWO = krWO (SW ), krOW = krOW (SW ) for water-oil two phase system,
krGO = krGO (SG ), krOG = krOG (SG ) for gas-oil two phase system
(SWOF (see 12.6.1) for first pair, SGOF (see 12.6.2), SLGOF (see 12.6.11) for second
pair). These functions may be obtained by laboratory measurements or may be approximated
by analytical functions based on the following user input data:
SWC connate water saturation
SOrW residual oil saturation to waterflooding
SGr critical gas saturation
SOrG residual oil saturation to gasflooding
krW rO water relative permeability at residual oil and SG = 0
krOcW oil relative permeability at SWC and SGr
krGcW gas relative permeability at SWC and SO = 0
nW , nOW , nG , nOG constant function parameters
2.6. Phase relative permeability 46

Then we can define analytical approximations for the listed above functions:

0 nW if SW SWC
krWO (SW ) = SW SWC
krW rO otherwise
1 SWC SOrW

0 nOW if 1 SW SOrW < 0
krOW (SW ) = 1 SW SOrW
krOcW otherwise
1 SWC SOrW

0 nG if SG < SGr
krGO (SG ) = S G S Gr
krGcW otherwise
1 SGr Swr

0 if 1 SG SW c SOrG < 0
1 SG SW c SOrG nOG

krOG (SG ) =
krOcW otherwise
1 SW c SOrG
Then we define:
krW (SW ) = krWO (SW ), (2.14)

krG (SG ) = krGO (SG ). (2.15)
At present two options for krO calculations are available: first (STONE1 (see 12.6.20)) and
second STONE2 (see 12.6.21) Stone models. By default the linear Baker model is used.
2.6.1 Linear Baker model

This model is used in tNavigator as default model (if the following keywords are not speci-
fied: STONE1 (see 12.6.20), STONE2 (see 12.6.21)).
Let ( small parameter):

krOG (SG + SW SW c ) SW SW c <

k (S + SW ) SG <

rOW G

krO (SW , SG ) = SG krOG (SG + SW SW c ) (2.16)
+
SG + (SW SW c )

(S SW c ) krOW (SG + SW )

+ W

else
SG + (SW SW c )
2.6.2 The first Stones model

The keyword STONE1 (see 12.6.20) is used to specify this model.
Let us define the following constants:
2.6.1. Linear Baker model 47

SW c connate water saturation, which is the minimal admissible value of SW for

water-oil two phase system
krOcW = krOW (SW c ) relative permeability to oil at connate water
SW r residual water saturation, which is the largest value of SW , where krW (SW ) =
krWO (SW ) = 0
SOrW water saturation at residual oil, which is the largest value of SW , where
krOW (SW ) = 0
SOrG gas saturation at residual oil, which is the largest value of SG , where
krOG (SG ) = 0.
The tables that specify minimum oil saturation (that is used in 3-phase model STONE1
(see 12.6.20)), as a function of gas saturation can be entered via SOMWAT (see 12.6.17),
SOMGAS (see 12.6.18).
Then
SG
(SG ) = 1 ,
1 SW c SOrG
Som (SG ) = (SG )SOrW + (1 (SG ))SOrG ,

SO Som (SG )
, if SO Som (SG )

SO (SO , SG ) = 1 SW c Som (SG ) ,
0, otherwise

SW SW c
, if SW SW c

SW (SW , SG ) = 1 SW c Som (SG ) ,
0, otherwise
SG
SG (SG ) = , (2.17)
1 SW c Som (SG )
and (S , S )
SO O G krOW (SW ) krOG (SG )
krO = krO (SO , SW , SG ) = (S ) . (2.18)
krOcW 1 SW (SW , SG ) 1 SG G
2.6.3 The second Stones model

The keyword STONE2 (see 12.6.21) is used to specify this model.
Using the same constants as defined in the previous paragraph:

SW c connate water saturation, which is the minimal admissible value of SW for
water-oil two phase system
2.6.3. The second Stones model 48

krOcW = krOW (SW c ) relative permeability to oil at connate water
we get the following expression for oil relative permeability in case of Stone 2:

krOW (SW ) krOG (SG )
krO (SO , SW , SG ) = krOcW + krW (SW ) + krG (SG ) (2.19)
krOcW krOcW
krOcW (krW (SW ) + krG (SG ))
2.6.4 End-point scaling, two-point method

Phase permeability scaling. Specification of critical saturation end-points can be done using
one of the following ways (they are not compatible by default):
Specification of critical saturation end-points for each grid block (keywords SWL (see
12.6.27), SWCR (see 12.6.30), ..., KRW (see 12.6.43), ...).
Specification of critical saturation end-points as depth function (keywords ENPTVD

(see 12.6.38), ENKRVD (see 12.6.39)).
Specification of critical saturation end-points as temperature function (keywords

ENPTVT (see 12.14.69), ENKRVT (see 12.14.70)) - only for thermo-compositional
model.
Specification of critical saturation end-points as composition function (ENPTVC (see

12.13.46), ENKRVC (see 12.13.44)) - only for compositional model.
Specification of critical saturation end-points as tracer concentration function (salt,

surfactant) (keyword can only be used in tNavigator ENPTRC (see 12.6.41)).
Possible combinations can be specified using 5-th parameter of the keyword ENDSCALE
(see 12.6.24).
The keyword ENDSCALE (see 12.6.24) indicates that end-point scaling of relative perme-
abilities and capillary pressures will be used. Table end-points can then be entered cell by cell
(SWL (see 12.6.27), SWCR (see 12.6.30), SWU (see 12.6.34), KRW (see 12.6.43), PCW
(see 12.6.46)) or with respect to depth (ENPTVD (see 12.6.38), ENKRVD (see 12.6.39),
ENPCVD (see 12.6.40)).
If end-point scaling option is selected (ENDSCALE (see 12.6.24)), saturations and relative
permeabilities are renormalized according to formulas below.
Saturations scaling
First introduce notations
SW , SG are block water and gas saturations,
2.6.4. End-point scaling, two-point method 49

SW cr , SGcr are critical water and gas saturations, i.e. maximal water (gas) saturation in
SWOF (see 12.6.1) (SGOF (see 12.6.2)), for which krW = 0 (krG = 0),
If TOLCRIT (see 12.6.19) isnt specified the critical water saturation SW cr is equal
to SW in the last table entry (SWOF (see 12.6.1), SWFN (see 12.6.13)) for krW ,
for which krW 1.0 106 in e100 models (krW 1.0 1020 in e300 models)
(finding the last zero relative permeability value while accounting for machine zero).
If TOLCRIT (see 12.6.19) is specified, the critical water saturation is equal to SW in
the last table entry, for krW T OLCRIT (analogously SGcr , SOW cr , SOGcr ).
SW max , SGmax are maximal values of water (and gas) saturation in SWOF (see 12.6.1)
(SGOF (see 12.6.2)),
SWCR (see 12.6.30), SGCR (see 12.6.31) are user defined values of critical water
(and gas) saturation in current block,
SWU (see 12.6.34), SGU (see 12.6.35) are user defined values of maximal water (and
gas) saturation in current block,
SW , SG are scaled block water and gas saturations,
krWO , krGO are water and gas relative permeabilities defined by SWOF (see 12.6.1)
(SGOF (see 12.6.2)) tables,
krW max (table), krG max (table) are maximum entry of water (gas) relative permeability
in SWOF (see 12.6.1) (SGOF (see 12.6.2)) table.
(SW SWCR)(SW max SW cr )

SW = SW cr + (2.20)
SWU SWCR
(SG SGCR)(SGmax SGcr )
SG = SGcr +
SGU SGCR
The keyword TZONE (see 12.6.25) controls the transition zone option. If the parameter
is set true to a phase, then the critical saturations for that phase will be modified to be the
initial immobile saturation in regions where the saturation is below the input critical value.
1. the parameter is set true to oil phase SOWCR (see 12.6.32) will be modified for
oil-water runs or oil-water-miscible gas runs, SOGCR (see 12.6.33) will be modified
only for oil-gas runs;
2. the parameter is set true to water phase, SWCR (see 12.6.30) will be modified;
3. the parameter is set true to gas phase, SGCR (see 12.6.31) will be modified for
gas-water runs and oil-gas runs.

Appropriate relative permeabilities are calculated as

0 SW SWCR
krW (SW ) = krWO (SW ) SWCR < SW < SWU (2.21)
krW max (table) SW SWU

0 SG SGCR
krG (SG ) = krGO (SG ) SGCR < SG < SGU (2.22)
krG max (table) SG SGU

Oil relative permeabilities are calculated in analogous way.
Relative permeabilities scaling
If at least one of the following arrays KRO (see 12.6.42), KRW (see 12.6.43), KRG
(see 12.6.44), KRORW (see 12.6.42), KRORG (see 12.6.42), KRWR (see 12.6.43), KRGR
(see 12.6.44) is set, relative permeabilities are additionally scaled according to following
formulas.
Water:
If only KRW is set

scaled KRW
krW (SW ) = krW (SW ) (2.23)
krW max (table)
If both KRW and KRWR are set
scaled KRW R
SW <= SR krW (SW ) = krW (SW ) (2.24)
krW (SR)
scaled
SW > SR krW (SW ) = KRW R + (2.25)
KRW KRW R
+ (krW (SW ) krW (SR))
krW max (table) krW (SR)
In 2-point scaling saturations are scaled via points SWCR and SWU. So if KRWR is
set, SR is taken as a simply scaled value of the following table value:
SR(table) = 1.0 SOWCR(table) SGCO(table) 3-phase case (2.26)
SR(table) = 1.0 SGCR(table) gas-water case (2.27)
Gas:
If only KRG is set

scaled KRG
krG (SG ) = krG (SG ) (2.28)
krG max (table)

If both KRG and KRGR are set
scaled KRGR
SG <= SR krG (SG ) = krG (SG ) (2.29)
krG (SR)
scaled
SG > SR krG (SG ) = KRGR + (2.30)
KRG KRGR
+ (krG (SG ) krG (SR))
krG max (table) krG (SR)
Oil: here P stands to water or gas phase
If only KRO is set

scaled KRO
krOP (SP ) = krOP (SP ) (2.31)
krOP max (table)
If both KRO and KRORP are set
scaled KRORP
SP <= SPCR krOP (SP ) = krOP (SP ) (2.32)
krOP (SPCR)
scaled
SP > SPCR krOP (SP ) = KRORP +
KRO KRORP
+ (krOP (SP ) krOP (SPCR))
krOP max (table) krOP (SPCR)
2.6.5 End-point scaling, three-point method

If in addition to ENDSCALE (see 12.6.24) three point scaling method for relative perme-
abilities is selected (SCALECRS (see 12.6.26)), phase permeabilities are recalculated in the
following manner.
Saturations scaling
As for two-point case, first introduce notations
SW co , SG co are connate water and gas saturations, i.e. minimal water (gas) saturation
in SWOF (see 12.6.1) (SGOF (see 12.6.2)),
SW cr , SGcr are critical water and gas saturations, i.e. maximal water (gas) saturation in
SWOF (see 12.6.1) (SGOF (see 12.6.2)), for which krW = 0 (krG = 0),
SOW cr , SOGcr are critical oil-to-water and oil-to-gas saturations, i.e. maximal oil satura-
tion in SWOF (see 12.6.1) (SGOF (see 12.6.2)), for which the oil relative permeability
is zero: krOW = 0 (krOG = 0),
(SGOF (see 12.6.2)),
2.6.5. End-point scaling, three-point method 52

SWL (see 12.6.27), SGL (see 12.6.29) are user defined values of connate water (and
SWCR (see 12.6.30), SGCR (see 12.6.31) are user defined values of critical water
(and gas) saturation in current block,
SOWCR (see 12.6.32), SOGCR (see 12.6.33) are user defined values of critical
oil-to-water (and oil-to-gas) saturation in current block,
SW , SG are scaled block water and gas saturations.
1. Water function rescaling

Denote
in 3phase systems SR = 1 SOWCR SGL, Sr = 1 SOW cr SG co
in oil-water systems SR = 1 SOWCR, Sr = 1 SOW cr
Then water saturation is rescaled according to formula
(
SW cr + (SW SWCR)(S
SRSWCR
r SW cr )
SWCR < SW < SR
SW = (SW SR)(SW max Sr ) (2.33)
Sr + SWUSR SR < SW < SWU
Relative permeability is calculated as in (2.21).

2. Gas function rescaling
Denote
in 3phase systems SR = 1 SOGCR SW L, Sr = 1 Sogcr SW co
in gas-water systems SR = 1 SWCR, Sr = 1 SW cr
Then gas saturation is rescaled according to formula
(
SGcr + (SG SGCR)(S
SRSGCR
r SGcr )
SGCR < SG < SR
SG = (SG SR)(SGmax Sr ) (2.34)
Sr + SGUSR SR < SG < SGU
Relative permeability is calculated as in (2.22).
The keyword TZONE (see 12.6.25) controls the transition zone option. If the parameter
is set true to a phase, then the critical saturations for that phase will be modified to be the
initial immobile saturation in regions where the saturation is below the input critical value.
2.6.5. End-point scaling, three-point method 53

Relative permeabilities scaling

If at least one of the following arrays KRO (see 12.6.42), KRW (see 12.6.43), KRG (see
12.6.44), KRORW (see 12.6.42), KRORG (see 12.6.42), KRWR (see 12.6.43), KRGR (see
12.6.44) is set, relative permeabilities are additionally scaled according to formulas, the same
as for two-point scaling case, see (2.23) - (2.32). The only difference is that now SR and
SPCR are defined properly.
2.6.6 Directional and irreversible RP

Directional and irreversible relative permeabilities can be used if the corresponding options
are specified in SATOPTS (see 12.1.68):
DIRECT directional relative permeabilities. In this case directional saturation tables are
used (flow in I, J, K directions uses different tables, the number of tables are specified
via KRNUMX (see 12.4.24), KRNUMY (see 12.4.24), KRNUMZ (see 12.4.24)). If
DIRECT is used without IRREVERS, then only three tables should be specified, because
the same table is used for the flow from I to I-1, and from I to I+1;
IRREVERS irreversible directional relative permeabilities. Different tables are used

for flow direction from I to I-1 or from I to I+1. (in this case DIRECT must also
be defined). Six tables should be specified via the keywords KRNUMX (see 12.4.24),
KRNUMX- (see 12.4.24), KRNUMY (see 12.4.24), KRNUMY- (see 12.4.24), KRNUMZ
(see 12.4.24) and KRNUMZ- (see 12.4.24).
If hysteresis is used (option HYSTER in SATOPTS (see 12.1.68)) then the Directional
and irreversible relative permeabilities can be used for imbibition. The following options
should be specified in the keyword SATOPTS (see 12.1.68):
via IMBNUMX (see 12.4.7), IMBNUMY (see 12.4.7), IMBNUMZ (see 12.4.7)). If

be defined). Six tables should be specified via the keywords IMBNUMX (see 12.4.7),
IMBNUMX- (see 12.4.7), IMBNUMY (see 12.4.7), IMBNUMY- (see 12.4.7), IMBNUMZ
(see 12.4.7) and IMBNUMZ- (see 12.4.7).
2.6.6. Directional and irreversible RP 54

2.6.7 RP at dual porosity runs.

KRNUMMF (see 12.4.25) This keyword specifies the number of matrix-fracture saturation
table regions for each grid block. The keyword can be used for dual porosity runs DUAL-
PORO (see 12.1.76) and dual permeability DUALPERM (see 12.1.77).
In accordance with the grid specification for dual porosity models (upper part the matrix,
the lower fracture) the flow from the fracture to the matrix uses a saturation table for
matrix, the flow from the fracture to the matrix uses a saturation table for fracture.
IMBNUMMF (see 12.4.26) This keyword specifies the number of matrix-fracture imbibi-
tion regions for each grid block. The keyword can be used for dual porosity runs DUALPORO
(see 12.1.76) and dual permeability DUALPERM (see 12.1.77) in case when hysteresis op-
tion is used (parameter HYSTER of the keyword SATOPTS (see 12.1.68)).
the lower fracture) the flow from the fracture to the matrix uses an imbibition table for
matrix, the flow from the fracture to the matrix uses an imbibition table for fracture.
2.6.8 User-defined relative permeability of the injected phase

For injecting well connections the mobility of the injected phase is varied as the total fluid
mobility in the grid block:
kr (O, j) r (W, j) kr (G, j)
(O, j) + k(W, j) + (G, j)
M(P, j) =
B(P, j)
where:
(P, j) phase P viscosity,
B(P, j) phase P formation volume factor,
kr (P, j) relative phase P permeability.
If gas or water is injected into a grid block (which contains oil), this relationship causes
wells injectivity to vary until the grid block will be full of injected phase. In real field most
of the pressure drop is over a region near the well, and when this region is full of injected
phase the injectivity stays constant. In case when this region size is smaller than the grid
block size, the calculated injectivity might be incorrect until the whole grid block will be full
of injected phase.
When the keyword COMPINJK (see 12.18.25) is used the well injects the fluid whose mo-
bility is different from mobility of the fluid initially in the block, and grid blocks (containing
the well) are large.
Injected phase mobility:
kr (P, )
M(P, j) =
(P, j)B(P, j)
where:
2.6.7. RP at dual porosity runs. 55

kr (P, ) relative permeability of the injected phase (a constant value specified via the
keyword COMPINJK (see 12.18.25)) (relative permeability in the region that is full of
injected phase);
relative permeabilities of other phases are zero.
2.6.9 Corey correlation

The keywords COREYWO (see 12.6.3), COREYGO (see 12.6.4) and COREYWG (see 12.6.5)
approximate relative permeability and capillary pressure functions for water-oil, gas-oil and
water-gas systems using formulas below.
Note. In tNavigator there is a possibility to use Corey (LET) correlation only for RP and
define capillary pressure via table (in this case one should enter 0 in parameter 12 (power) of
the keyword COREYWO, COREYGO (LETWO, LETGO) and define tables SWOF, SGOF
or other. Values for capillary pressure will be taken from tables and RP will be calculated
using Corey (LET) correlation.
Keyword COREYWO (see 12.6.3) (The picture of relative permeabilities for water-oil
system with points 1):
Denote:
SW SWCR
SW n = SW n (SW ) =
1 SWCR SOWCR SGL

WCR SW

krORW + (krOLW krORW ) SSWCR SW L SW L SW < SWCR

krOW (SW ) = krORW (1 SW n )nOW SWCR SW 1 SOWCR SGL (2.35)

1 SOWCR SGL < SW SWU

0

0 SW L SW < SWCR

krW (SW ) = krW R (SW n )NW SWCR SW 1 SOWCR SGL

SWU SW

rWU (krWU krW R ) SOWCR +SGL +SWU 1 1 SOWCR SGL < SW SWU

k
(2.36)
S pcO SW N p
h i
p
cOW (SWCR ) S pcO SWCR SW L SW S pcO
pcOW (SW ) = (2.37)
0 S pcO < SW SWU

Modified formulas for RP approximation (the keyword COREYWOMOD (see 12.6.6)):
2.6.9. Corey correlation 56

Figure 1: Relative permeabilities for water-oil system
Denote:
SW SWCR
SW n = SW n (SW ) =
1 SWCR SGL
(for krW calculation)
SW SWCR
SW n = SW n (SW ) =
1 SWCR SOWCR SGL
(for krOW calculation)

WCR SW


krOW (SW ) = krORW (1 SW n )nOW SWCR SW 1 SOWCR SGL (2.38)


0


0 SW L SW < SWCR

krW (SW ) = krW R (SW n )NW SWCR SW 1 SGL (2.39)

SWU SW

rWU (krWU krW R ) SGL +SWU 1 1 SGL < SW SWU

k
S pcO SW N p
h i
p
cOW (SWCR ) S pcO SWCR SW L SW S pcO
pcOW (SW ) = (2.40)
0 S pcO < SW SWU

Keyword COREYGO (see 12.6.4) (The picture of relative permeabilities for gas-oil sys-
tem with points 2):
Figure 2: Relative permeabilities for gas-oil system
Denote:
SG SGCR
SGn = SGn (SG ) =
1 SGCR SOGCR SW L


GCR SG

krORG + (krOLG krORG ) SSGCR SGL SGL SG < SGCR

krOG (SG ) = krORG (1 SGn )nOG SGCR SG 1 SOGCR SW L (2.41)

1 SOGCR SW L < SG SGU

0

0 SGL SG < SGCR

krG (SG ) = krGR (SGn )NG SGCR SG 1 SOGCR SW L (2.42)

SGU SG

rGU (krGU krGR ) SOGCR +SW L +SGU 1 1 SOGCR SW L < SG SGU

k

0
SGL SG < S pcG
pcOG (SG ) = h
SG S pcG
iNpG (2.43)
pcOG (1 SOGCR SW L )

1S pcG SOGCR SW L S pcG SG SGU
Modified formulas for RP approximation (the keyword COREYGOMOD (see 12.6.7)):

Denote:
SG SGCR
SGn = SGn (SG ) =
1 SGCR SW L
(for krG calculation)
SG SGCR
SGn = SGn (SG ) =
1 SGCR SOGCR SW L
(for krOG calculation)

GCR SG


krOG (SG ) = krORG (1 SGn )nOG SGCR SG 1 SOGCR SW L (2.44)


0

0 SGL SG < SGCR

krG (SG ) = krGR (SGn )NG SGCR SG 1 SW L (2.45)

SGU SG

rGU (krGU krGR ) SW L +SGU 1 1 SW L < SG SGU

k

0
SGL SG < S pcG
pcOG (SG ) = h
SG S pcG
iNpG (2.46)
pcOG (1 SOGCR SW L )

1S pcG SOGCR SW L S pcG SG SGU

Figure 3: Relative permeabilities for water-gas system
Keyword COREYWG (see 12.6.5) (The picture of relative permeabilities for water-gas
system 3):
Denote:
SG SGCR
SGn = SGn (SG ) = ,
1 SWCR SGCR
SW SWCR
SW n = SW n (SW ) = .
1 SWCR SGCR
Then:

0 SW L SW < SWCR

krW (SW ) = krW R (SW n )NW SWCR SW 1 SGCR (2.47)

SWU SW

rWU (krWU krW R ) SOWCR +SGL +SWU 1 1 SGCR < SW SWU

k


0 SGL SG < SGCR

krG (SG ) = krGR (SGn )NG SGCR SG 1 SWCR (2.48)

SGU SG

rGU (krGU krGR ) SOGCR +SW L +SGU 1 1 SWCR < SG SGU

k
S pcO SW N p
h i
p
cW G (SWCR ) S pcO SWCR SW L SW S pcO
pcW G (SW ) = (2.49)
0 S pcO < SW SWU

2.6.10 LET correlation

The keywords LETWO (see 12.6.8), LETGO (see 12.6.9) and LETWG (see 12.6.10) approxi-
mates relative permeability for water-oil, gas-oil and water-gas systems using formulas below.
For water-oil system (keyword LETWO (see 12.6.8)) (the picture 4):
Denote:
SW SWCR
SW n = SW n (SW ) =
1 SWCR SOWCR SGL

WCR SW

n
krORW (1SW n ) OW
krOW (SW ) = TO SWCR SW 1 SOWCR SGL (2.50)

(1SW n )nOW +E O SW n

0 1 SOWCR SGL < SW SWU

0 SW L SW < SWCR

N

krW (SW ) = krW R SWWn
NW SWCR SW 1 SOWCR SGL

SW n +EW (1SW n )TW
WU SW
krWU (krWU krW R ) SOWCRS+S


GL +SWU 1
(2.51)
Formulas for capillary pressure are the same as in section Corey correlation 2.6.9.
Description of parameters:
N describes the lower part of the curve (the same way as N in Corey correlation).
2.6.10. LET correlation 61

Figure 4: LET correlation for water-oil system
T describes the upper part (or the top part) of the curve.
E describes the position of the slope (or the elevation) of the curve. E = 1 is a neutral
value, the position of the slope is governed by N and T . Increasing E value pushes
the slope towards the high end of the curve. Decreasing E value pushes the slope
towards the lower end of the curve.
The reasonable ranges for the parameters N , E , and T are: N 1, E > 0 and T 0.5.
For the gas-oil system (keyword LETGO (see 12.6.9)) (the picture 5):
Denote:
SG SGCR
SGn = SGn (SG ) =
1 SGCR SOGCR SW L

GCR SG

n
krORG (1SGn ) OG
krOG (SG ) = TG SGCR SG 1 SOGCR SW L (2.52)

(1SGn )nOG +EG SGn

0 1 SOGCR SW L < SG SGU

Figure 5: LET correlation for gas-oil system

0 SGL SG < SGCR

N

krGR SGnG
krG (SG ) = N SGCR SG 1 SOGCR SW L (2.53)
S G +EG (1SGn )TG
Gn

GU SG
krGU (krGU krGR ) SOGCR S+S

W L +SGU 1
For the water-gas systems (keyword LETWG (see 12.6.10)) (picture 6):
Denote:
SW SWCR
SW n = SW n (SW ) =
1 SWCR SOWCR SGL
SG SGCR
SGn = SGn (SG ) =
1 SGCR SOGCR SW L
Then:

Figure 6: LET correlation for water-gas system

0 SGL SG < SGCR

N

krGR SGnG
krG (SG ) = NG SGCR SG 1 SWCR (2.54)

SGn +EG (1SGn )TG
GU SG
krGU (krGU krGR ) SOGCR S+S

1 SWCR < SG SGU

W L +SGU 1

0 SW L SW < SWCR

N

krW (SW ) = krW R SWWn (2.55)
NW SWCR SW 1 SSGCR

SW n +EW (1SW n )TW
WU SW
krWU (krWU krW R ) SOWCRS+S

1 SSGCR < SW SWU

GL +SWU 1
Formulas for capillary pressure are the same as in section Corey correlation 2.6.9.
2.6.11 Hysteresis
Hysteresis option allows to specify different saturation functions for drainage (decreasing
wetting phase saturation) and imbibition (increasing wetting phase saturation) processes.
Hysteresis option is specified via keyword SATOPTS (see 12.1.68) (parameter HYSTER).
2.6.11. Hysteresis 64
For each grid block two saturation function table numbers should be specified:
1. SATNUM (see 12.4.3) specifies the table number of primary drainage curve;
2. IMBNUM (see 12.4.7) specifies the table number of pendular imbibition curve.
If these table numbers are equal for the block, there will be no hysteresis in this block.
If these table numbers are different, hysteresis will be applied according to the model speci-
fied via the keyword EHYSTR (see 12.6.50).
tNavigator supports the following water wet hysteresis models:

0 Carlsons Hysteresis Model used for the non-wetting phase(s), drainage (SATNUM
(see 12.4.3)) curve used for the wetting phase.
1 Carlsons Hysteresis Model used for the non-wetting phase(s), imbibition (IMBNUM
2 Killoughs Hysteresis Model used for the non-wetting phase(s), drainage (SATNUM
3 Killoughs Hysteresis Model used for the non-wetting phase(s), imbibition (IMB-
NUM (see 12.4.7)) curve used for the wetting phase.
4 Killoughs hysteresis model used for both wetting and non-wetting phases.
5 Carlsons non-wetting model for gas and water phases, drainage (SATNUM (see
12.4.3)) curve used for the wetting phase.
6 Killoughs non-wetting model for the gas and water phases, drainage (SATNUM
7 Killoughs Hysteresis Model used for the non-wetting gas and water phases and
the wetting oil phase.
8 Jargons Hysteresis Model used for the non-wetting phase, drainage (SATNUM (see
12.4.3)) curve used for the wetting phase.
9 Jargons Hysteresis Model used for the non-wetting phase, imbibition (IMBNUM
-1 Only equilibration option. If this option is used then the model is equilibrated using
the drainage curve (SATNUM (see 12.4.3)) but the simulation uses the imbibition curve
(IMBNUM (see 12.4.7)).
Hysteresis curvature parameters for saturation regions (SATNUM (see 12.4.3)) can be set
via the keyword EHYSTRR (see 12.6.51).
If hysteresis is used (option HYSTER in SATOPTS (see 12.1.68)) then the Directional
and irreversible relative permeabilities can be used for imbibition. The following options
should be specified in the keyword SATOPTS (see 12.1.68):

for flow direction from I to I-1 ot from I to I+1. (in this case DIRECT must also
(see 12.4.7) and IMBNUMZ- (see 12.4.7).
End-points scaling for hysteresis option.

Relative permeabilities and saturations end-points should be specified separately for drainage
and imbibition process.
For imbibition process RP end-points:
IKRG maximal gas relative permeability (for drainage process this value is specified
via the keyword KRG (see 12.6.44));
IKRGR gas relative permeability at the residual oil (of residual water in gas-water sys-
tem) (for drainage process this value is specified via the keyword KRGR (see 12.6.44));
IKRW maximal water relative permeability (for drainage process this value is specified
via the keyword KRW (see 12.6.43));
IKRWR water relative permeability at the residual oil (of residual gas in gas-water
system) (for drainage process this value is specified via the keyword KRWR (see
12.6.43));
IKRO maximal oil relative permeability (for drainage process this value is specified
via the keyword KRO (see 12.6.42));
IKRORG oil relative permeability at the critical gas saturation (for drainage process
this value is specified via the keyword KRORG (see 12.6.42));
IKRORW oil relative permeability at the critical water saturation (for drainage process
this value is specified via the keyword KRORW (see 12.6.42)).
For imbibition process saturations end-points:
ISGL (see 12.6.36) minimal (connate) gas saturation (for drainage process this value
is specified via the keyword SGL (see 12.6.29));
ISGCR (see 12.6.36) critical gas saturation (for drainage process this value is speci-
fied via the keyword SGCR (see 12.6.31));
ISGU (see 12.6.36) maximal gas saturation (for drainage process this value is
specified via the keyword SGU (see 12.6.35));
ISWL (see 12.6.36) minimal (connate) water saturation (for drainage process this
value is specified via the keyword SWL (see 12.6.27));
ISWLPC (see 12.6.36) minimal (connate) water saturation for capillary pressure Pc
curve scaling only (for drainage process this value is specified via the keyword SWLPC
(see 12.6.28));
ISWCR (see 12.6.36) critical water saturation (for drainage process this value is
specified via the keyword SWCR (see 12.6.30));
ISWU (see 12.6.36) maximal water saturation (for drainage process this value is
specified via the keyword SWU (see 12.6.34));
ISOGCR (see 12.6.36) critical oil saturation in oil-gas system (for drainage process
this value is specified via the keyword SOGCR (see 12.6.33));
ISOWCR (see 12.6.36) critical oil saturation in oil-water system (for drainage process
this value is specified via the keyword SOWCR (see 12.6.32)).
Drainage option (DRAINAGE (see 12.6.52)) can be used in hysteresis K r values
obtained in the hysteresis option should lie on or below drainage curve.
2.6.12 Surface tension effects

To take into account a surface tension effect the following keywords can be used:
MISCIBLE (see 12.1.65) enables an option of surface tension effect on properties;
MISCNUM (see 12.4.8) specifies miscibility region number for each grid block;
MISCSTR (see 12.6.53) specifies reference surface tension (one should use the
keyword MISCSTRR (see 12.6.54) to set the miscibility reference surface tension for
each saturation region);
MISCEXP (see 12.6.55) specifies miscibility exponent (exponent of the surface
tension ratio);
PARACHOR (see 12.6.56) specifies component parachors.
Interpolation factor that is used in miscibility:
N
F =( )
0
0 reference surface tension (specified via MISCSTR (see 12.6.53)).
N an exponent (specified via MISCEXP (see 12.6.55)).
2.6.12. Surface tension effects 67

2.7. Equation of state tNavigator-4.2
F is used to calculate a weighted average of miscible and immiscible hydrocarbon relative

permeabilities :
immiscibility miscibility
Kro = FKro + (1 F)Kro
Reference surface tension, specified via this keyword the surface tension at which the im-
miscible relative permeability curves are measured.
2.7 Equation of state

In case of compositional run oil and gas properties are calculated from equation of state
(EOS (see 12.13.5)):
Z 3 + E2 Z 2 + E1 Z + E0 = 0 (2.56)
Maximal positive root of equation (2.56) is equal to vapor Z-factor (correspondingly,

minimal positive root for liquid phase Z-factor).
Equation (2.56) coefficients are calculated as follows.
For every component (CNAMES (see 12.13.4)) user defines
Tci - component i critical temperature, TCRIT (see 12.13.17),
pci - component i critical pressure, PCRIT (see 12.13.19),
i - component i acentric factor, ACF (see 12.13.30),
ci j - binary interaction coefficients, BIC (see 12.13.32).
Next, coefficients m1 , m2 , a0 , b are taken from table according to equation of state

type:
EOS m1 m2 a0 b
RK 0 1 0.4274802 0.08664035
SRK 0 1 0.4274802 0.08664035
PR 1+ 2 1 2 0.457235529 0.07796074
Then basing on current temperature and pressure p, T reduced values are calculated for
each component:
pri = p/pci , Tri = T /Tci . (2.57)
Depending on EOS type, a is taken as:
RK
a (T, i) = a0 Tri0.5 (2.58)
2.7. Equation of state 68

2.8. Phase viscosity tNavigator-4.2
SRK
2
a (T, i) = a0 1 + (0.48 + 1.574i 0.176i2 )(1 Tri0.5 ) (2.59)
PR
2
a (T, i) = a0 1 + (0.37464 + 1.54226i 0.26992i2 )(1 Tri0.5 ) (2.60)
Next, the simulator calculates

pri pri
Ai = a (T, i) 2 , Bi = b , A jk = (1 c jk )(A j Ak )0.5 . (2.61)
Tri Tri
Now EOS coefficients can be calculated:
N n N
A = y j yk A jk , B = y jB j (2.62)
j=1 k=1 j=1
E2 = (m1 + m2 1)B 1, (2.63)

E1 = A (2(m1 + m2 ) 1)B2 (m1 + m2 )B,
E0 = AB + m1 m2 B2 (B + 1)

2.8 Phase viscosity

Black oil: Phase viscosity P = P (pP ) is user specified function. For oil and gas phases it
is specified in a number of points pP and is interpolated for other points (PVDO (see
12.5.2), PVTO (see 12.5.4), PVCDO (see 12.5.3), PVCO (see 12.5.6) for oil phase and
PVDG (see 12.5.7), PVTG (see 12.5.8), PVZG (see 12.5.9) for gas phase). For water
phase it is specified in a single point accompanied by pressure derivative (PVTW (see
12.5.5)). In case of absence of laboratory measurements the approximations obtained
from PVT properties by correlation analysis may be used (Standing correlations 2.11,
2.12).
Compositional: For water phase viscosity is constant (PVTW (see 12.5.5)). For hydrocarbon
phases we use Lohrenz-Bray-Clark correlation
1/4
(P P ) + 104 2
= a1 + a2 rP + a3 rP 3
+ a4 rP 4
+ a5 rP (2.64)
Here rP = P /c , coefficients ai are equal to
a1 = 0.1023000, a2 = 0.0233640, a3 = 0.0585330, (2.65)
a4 = 0.0407580, a5 = 0.0093324.
and
!1/6 !1/2 !2/3
N N N
= ziTci ziMwi zi pci . (2.66)
i=1 i=1 i=1
2.8. Phase viscosity 69

2.10. API tracking tNavigator-4.2
Critical temperatures Tci (TCRIT (see 12.13.17)), critical pressures pci (PCRIT (see
12.13.19)) and molecular weights Mwi (MW (see 12.13.27), MWW (see 12.13.29))
are user defined.
Phase molar density is P is defined in 2.13. Critical density c could be found from
user entered critical volumes Vci , VCRIT (see 12.13.21):
!1
N
c = ziVci . (2.67)
i=1
Dilute gas mixture viscosity is calculated from

! !1
N N
1/2 1/2
= zi i Mwi zi Mwi . (2.68)
i=1 i=1
where dilute gas viscosities for individual component i, i , are defined as
34 105 Tri0.94 /i , Tri 1.5

(

i = (2.69)
17.78 105 (4.58Tri 1.67)0.625 /i , Tri > 1.5
and
1/6 1/2 2/3
i = Tci Mwi pci . (2.70)
2.9 Phase formation volume factor

Phase formation volume factor BP = BP (pP ) is user specified function. For oil and gas
phases it is specified in a number of points pP and is interpolated for other points (PVDO
(see 12.5.2),PVTO (see 12.5.4), PVCDO (see 12.5.3), PVCO (see 12.5.6) for oil phase
and PVDG (see 12.5.7), PVTG (see 12.5.8), PVZG (see 12.5.9) for gas phase). For water
phase it is a single point accompanied by pressure derivative (compressibility) (PVTW (see
12.5.5)). In case of absence of laboratory measurements the approximations obtained from
PVT properties by correlation analysis may be used (Standing correlations 2.11, 2.12).
2.10 API tracking

This option gives a possibility to simulate the mixing of different types of oil, with different
surface densities and PVT properties.
In this case PVT tables, that specify oil properties are selected at each time step correspond-
ing to average oil API density in this grid block.
Supported keywords:
Option is enable if the keyword API (see 12.1.62) is used.
2.9. Phase formation volume factor 70

2.11. Oil Standings correlations tNavigator-4.2
PVT properties are specified via ordinary keywords (PVTO (see 12.5.4), PVCO (see
12.5.6), etc).
The values of oil API gravity is specified via the keyword GRAVITY (see 12.5.24) (or
is calculated from the density specified in DENSITY (see 12.5.23)).
Maximum number of oil PVT tables groups if an option API tracking is enable
APIGROUP (see 12.5.25).
APIVD (see 12.15.14) specifies tables of oil API density versus depth for each equi-
librium region.
OILAPI (see 12.15.15) specifies initial oil API values in each grid block (when initial
conditions are set via enumeration via the keywords SWAT (see 12.15.10), PRESSURE
(see 12.15.8) etc.).
Fully implicit method is used for API calculation by default. It can be changed to explicit
via the keyword TRACEROPTS (see 12.7.3).
2.11 Oil Standings correlations

Bubble-Point Pressure (1981, [7, p. 87], [8, p. 8-9]):
Rsb
pb = 1.2548[( )0.83 10(0.00091(9/5(T +273.5)459.67)0.0125API) 1.4] (2.71)
0.1781 G
Solution Gas-Oil-Ratio (GOR) (1981, [7, p. 78-79], [8, p. 8-9]):
Rs = 0.1781 G [(0.7971 p + 1.4) 10(0.0125API0.00091(9/5(T +273.5)459.67)) ]1.2048 (2.72)
where
141.5
API = 131.5
O
Parameters:
pb bubble-point pressure (barsa);
p system pressure (barsa);
Rs gas solubility (sm3 /sm3 );
Rsb gas solubility at bubble point (sm3 /sm3 );
T system temperature ( C );
G solution gas specific gravity (is taken from the keyword GRAVITY (see 12.5.24)
or is calculated from the keyword DENSITY (see 12.5.23));
2.11. Oil Standings correlations 71

O specific gravity of the stock-tank oil (is taken from the keyword GRAVITY (see
12.5.24) or is calculated from the keyword DENSITY (see 12.5.23)).
Standings correlation should be used with caution if nonhydrocarbon components are

known to be present in the system.
It should be noted that Standings equation is valid for applications at and below the
bubble-point pressure of the crude oil.
2.11.1 2-phase water-oil model. Dead Oil

The case where options WATER (see 12.1.54) and OIL (see 12.1.52) are used.
Viscosity Of The Dead Oil ([7, p. 116]).

Od viscosity of the dead oil as measured at 1 bar (14.7 psia) and reservoir temperature
(cp) is calculated the following way:
a
1.8 107

360
Od = 0.32 + (2.73)
API4.53 9/5 (T + 273.5) 260
with
a = 10(0.43+8.33/API)
2.11.2 3-phase model. Dead Oil

The case where options WATER (see 12.1.54), OIL (see 12.1.52), GAS (see 12.1.53),
DISGAS (see 12.1.56) are used.
There is no Standings correlations for VAPOIL (see 12.1.55) case.
Gas saturated (below bubble point pressure) The keyword STANDO (see 12.5.10) spec-
ifies the following parameters: Rsb or pb , T .
The following data is calculated: Rsb , pb , Rs , BO oil formation volume factor (rm3 /sm3 ),
O viscosity of the oil (cp).
Oil Formation Volume Factor: (1981, [7, p. 94])

" 0.5 #1.2
G
BO = 0.9759 + 0.000120 5.614583 Rs + 1.25 (9/5 (T + 273.5) 459.67)
O
(2.74)
Viscosity: ([7, p. 117-118])
O = (10)a (Od )b (2.75)

with
2.11.1. 2-phase water-oil model. Dead Oil 72

a = 5.614583 Rs [2.2 107 5.614583 Rs 7.4 104 ]
0.68 0.25 0.062

b= + d +
10c 10 10e
c = 8.62 105 5.614583 Rs

d = 1.1 103 5.614583 Rs
e = 3.74 103 5.614583 Rs
The experimental data used by Chew and Connally to develop their correlation encom-
passed the following ranges of values for the independent variables:
Pressure: 9.1-0.39 bar (132-5,645 psia).
Temperature: 22.22-144.44 C (72-292 F ).
Gas solubility: 9.5625-0.6645 sm3 /sm3 (51-3,544 sc f /ST B).
Dead oil viscosity: 0.377-50 cp.
Undersaturated (above bubble point pressure) The keyword STANDO (see 12.5.10)
specifies the following parameters: Rsb or pb , T , [cO ] isothermal compressibility coeffi-
cient.
The following data is calculated: Rsb , pb , Rs , BO oil formation volume factor (rm3 /sm3 ),
O oil viscosity (cp).
Oil Formation Volume Factor: ([7, p. 104])
BO = BOb exp(cO (pb p)) (2.76)
where
BO oil formation volume factor at the pressure of interest (rm3 /sm3 );
BOb oil formation volume factor at the bubble-point pressure (rm3 /sm3 ) (is calculated
according to the formula 2.74);
p pressure of interest (barsa).

Replacing cO with the Petrosky-Farshad expression and integrating gives: ([7, p. 105])
BO = BOb exp [A 14.50377 (p0.4094 p0.4094

b )] (2.77)
with the correlating parameter A as defined by ([7, p. 105]):
A = 4.1646 (107 ) (5.614583 Rsb )0.69357 g0.1885 (API)0.3272 (9/5 (T + 273.5) 459.67)0.6729
(2.78)
2.11.2. 3-phase model. Dead Oil 73

2.12. Gas Standings correlations tNavigator-4.2
Viscosity: ([9, p. 241])
1.6 0.56
O = Ob + 0.001 14.50377 (p pb ) [0.024Ob + 0.038Ob ] (2.79)
where
O undersaturated oil viscosity (cp);
Ob viscosity of the oil at the bubble-point pressure (cp) (is calculated according to
the formula 2.75).
2.12 Gas Standings correlations

The keyword STANDG (see 12.5.11) specifies the following parameters: z gas compress-
ibility factor, T ( C).
The following data is calculated: BG gas formation volume factor (rm3 /sm3 ), G gas
viscosity (cp).
2.12.1 Gas Formation Volume Factor

([7, p. 65-66])
z (9/5 (T + 273.5))
BG = 0.02827
14.50377 p
where p initial reservoir pressure (Barsa).
2.12.2 Gas Viscosity

([7, p. 73-74])
Lee, Gonzalez, and Eakin (1966) presented a semi-empirical relationship for calculating
the viscosity of natural gases. The authors expressed the gas viscosity in terms of the reservoir
temperature, gas density, and the molecular weight of the gas. Their proposed equation is
given by:
" Y #
0.06243745G
G = 104 K exp X
62.43
with
(9.379 + 0.0160Ma ) (9/5 (T + 273.5))1.5

K=
209.2 + 19.26Ma + 9/5 (T + 273.5)
986.4
X = 3.448 + + 0.01009 Ma
9/5 (T + 273.5)
2.12. Gas Standings correlations 74

2.13. Phase molar density tNavigator-4.2
Y = 2.4 0.2 X
where
G gas density at reservoir pressure and temperature (kg/m3 );
Ma apparent molecular weight of the gas mixture;
and
1 0.0689 p Ma
G =
0.06243745 10.73z 9/5 (T + 273.5)
Ma = 28.96G
The proposed correlation can predict viscosity values with a standard deviation of 2.7%
and a maximum deviation of 8.99%. The correlation is less accurate for gases with higher
specific gravities. The authors pointed out that the method cannot be used for sour gases.
2.13 Phase molar density

Black oil: Phase molar density is always function of BP - formation volume factor. For
water component it is calculated as
W,SC
W = (2.80)
BW
Here BW = BW (pW ) formation volume factor for water, user specified function. For
water user specifies formation volume factor at reference pressure and compressibility
that is defined as:
1 BW
cW = (2.81)
BW p
For oil and gas phases molar density in black oil assumptions is calculated as
RG,O G,SC + O,SC RO,G O,SC + G,SC
O = , G = (2.82)
BO BG
Here P,SC is molar density of phase P in standard conditions.
Compositional: Water molar density is calculated as in black oil case. For RK, SRK and
non-shifted PR EOS (EOS (see 12.13.5)) phase molar density is found from equation
p
P = (2.83)
ZRT
Critical Z -factor is taken from solution of (2.56) for corresponding phase.
In case of shifted PR EOS formula (2.84)
!
n
ZRT
P = 1/ xiP bi si (2.84)
p i=1
2.13. Phase molar density 75

2.15. Capillary pressures tNavigator-4.2
is used for liquid phase. Here si are shift parameters, bi are taken from
RTci
bi = b , (2.85)
pci
(see section 2.7 for b definition), and xiP are molar fractions of component i in phase
P.
2.14 Phase mass density

Black oil: Phase mass density P is obtained by user input data. Usually user specifies
P,SC phase mass density at surface condition. In case of absence of laboratory
measurements the approximations obtained from PVT properties by correlation analysis
may be used.
Very often the following constants are known (user input, DENSITY (see 12.5.23)):
O,SC oil density at surface condition
G,SC gas density at surface condition
W,SC water density at surface condition
Then the following functions by analogy with phase molar density are used as P (pP )
in black oil model:
W,SC
W = (2.86)
BW
RG,O G,SC + O,SC
O = (2.87)
BO
RO,G O,SC + G,SC
G = (2.88)
BG
Compositional: Mass density of water is calculated as in black oil case. Mass density of
hydrocarbon component is calculated from molar density (see 2.13) as
P = P MwP , (2.89)
where MwP is average molecular weight for phase P,
N N
MwO = Mwi xiO , MwG = Mwi xiG (2.90)
i=1 i=1
Mwi are component molecular weights, MW (see 12.13.27), MWW (see 12.13.29) and
xiP are concentrations of component i in phase P.
2.15 Capillary pressures

2.15.1 Oil-gas capillary pressure
Oil-gas capillary pressure PcOG = PcOG (SG ) is user input data array defined in a number of
SG points and interpolated for other points (SGOF (see 12.6.2)).
2.14. Phase mass density 76

2.15.2 Oil-water capillary pressure

Oil-water capillary pressure PcOW = PcOW (SW ) is user input data array defined in a number
of SW points and interpolated for other points (SWOF (see 12.6.1)).
2.15.3 Capillary pressure end-point scaling

Capillary pressure scaling. Specification of critical saturation end-points can be done using
one of the following ways (they are not compatible by default):
Specification of critical saturation end-points for each grid block (keywords PCW (see
12.6.46), PCG (see 12.6.47)).
Specification of critical saturation end-points as depth function (keywords ENPCVD

(see 12.6.40)).
Specification of critical saturation end-points as temperature function (keywords EN-

PCVT (see 12.14.71) - only for thermo-compositional model.
Specification of critical saturation end-points as composition function (ENPCVC (see

12.13.45) - only for compositional model.
(see 12.6.24).
If end-point scaling is selected by ENDSCALE (see 12.6.24), capillary pressures are

scaled with accordance to user defined arrays of minimal and maximal saturations. Capillary
pressures are scaled by two-point method, saturations are renormalized according to formulas
below.
Lets first introduce notations
SW co , SG co are connate water and gas saturations, i.e. minimal water (gas) saturation
in SWOF (see 12.6.1) (SGOF (see 12.6.2)),
(SGOF (see 12.6.2)),
SWL (see 12.6.27), SGL (see 12.6.29) are user defined values of connate water (and
PCW (see 12.6.46), PCG (see 12.6.47) are user defined arrays of maximum capillary
pressures,
2.15.2. Oil-water capillary pressure 77

PcOW max (table), PcOG max (table) are maximum capillary pressures from table SWOF
(see 12.6.1) (SGOF (see 12.6.2)) (values at connate water and gas saturations)
SW , SG are scaled block water and gas saturations.

Saturations are scaled as
(SW SW L)(SW max SW co )
SW = SW co + (2.91)
SWU SW L
(SG SGL)(SGmax SG co )
SG = SG co +
SGU SGL
Appropriate capillary pressures are calculated as
PCW
PcOW (SW ) = PcOW (SW )(table) (2.92)
PcOW max (table)
PCG
PcOG (SG ) = PcOG (SG )(table) (2.93)
PcOG max (table)
2.15.4 Capillary pressure calculation according to Leverett J-function

If end-point scaling is selected by ENDSCALE (see 12.6.24), capillary pressures may be
calculated according to Leverett J-function model. Phase capillary pressures are scaled if
first argument of JFUNC (see 12.2.58) indicates scaling is to be performed. (This keyword
defines parameters for whole reservoir. The keyword JFUNCR (see 12.2.59) can be used to
specify data separetely for each saturation region.)
Scaling formulas are the following:
PcOW (SW ) = JW (SW )(table) Jmult W (2.94)

PcOG (SG ) = JG (SG )(table) Jmult G (2.95)
Here JW , JG are input in the fourth column of SWOF (see 12.6.1) and SGOF (see 12.6.2)
keywords, as functions of saturations, in place of phase capillary pressures. Multipliers are
calculated as
Jmult W = STW ( i, j,k ) /(K i, j,k ) 0.318316 (2.96)

i, j,k i, j,k
Jmult G = STG ( ) /(K ) 0.318316
where
STW oil-water surface tension, second argument of keyword JFUNC (see 12.2.58);
STG oil-gas surface tension, third argument of keyword JFUNC (see 12.2.58);
i, j,k porosity in grid block;
K i, j,k permeability, calculated according to one of the following methods
2.15.4. Capillary pressure calculation according to Leverett J-function 78

2.16. Solubility of gas component into oil phase tNavigator-4.2
i, j,k i, j,k
XY: K i, j,k = (kxx + kyy )/2
i, j,k
X: K i, j,k = kxx
i, j,k
Y: K i, j,k = kyy
i, j,k
Z: K i, j,k = kzz ;
the method is selected by 6-th parameter of keyword JFUNC (see 12.2.58).

Or instead of this parameter one can specify the special permeability value used for
J-function computation (JFPERM (see 12.2.60)). If this keyword is specified then per-
meability direction (the 6-th parameter of JFUNC (see 12.2.58) is ignored).
power for porosity, fourth argument of keyword JFUNC (see 12.2.58);
power for permeability, fifth argument of keyword JFUNC (see 12.2.58).
2.16 Solubility of gas component into oil phase

Solubility of gas component into oil phase RG,O = RG,O (pO ) (gas-oil ratio) is user input data
array defined in a number of pO points and interpolated for other points (PVTO (see 12.5.4),
PVCO (see 12.5.6)).
The keyword DRSDT (see 12.18.97) sets maximum rate of increase of solution gas-oil
ratio (sm3 /sm3 /day).
For black-oil models the followinf extanesions of the keyword DRSDT (see 12.18.97)
can be used:
1. Set maximum rate of increase of solution gas-oil ratio as a function of pressure

(keyword DRSDTVP (see 12.18.98)).
In tNavigator one can set maximum rate of increase of solution gas-oil ratio D as a
function of pressure via the dimensionless parameter (p):
Rn+1
s D(p)t + Rns
where
pO pmin
(p) =
pb (Rsmax ) pmin
pO current pressure in oil phase;
pmin minimum pressure in the grid block that was reached in a previous pressure
reduction with gas emission;
pb (Rsmax ) equilibrium saturation pressure (according to the initial table) corre-
sponding gas-oil ratio Rsmax ;
Rsmax gas-oil ration that would be achieved in the block when all free gas will
be dissolved in the oil.
2.16. Solubility of gas component into oil phase 79

2.18. Inflow from aquifer tNavigator-4.2
Selecting of the parameter p in dimensionless form allows to take into account the
relative deviation of the current pressure to saturation pressure independently from
flows between blocks.
2. An alternative model of gas dissolution that takes into account the exponential
nature of the system relaxation (keyword DRSDTVPE (see 12.18.99)).
The relaxation process of the physical value f in the first approximation can be
described by the equation
df
= ( f f0 )
dt
where relaxation parameter, f0 equilibrium value of f .
The solution of this equation corresponds to the typical exponential relaxation dynam-
ics.
Analogously for Rs relaxation equation is:
dRs
= D(p)(Rs Rs (p))
dt
D parameter characterizing the relaxation rate of the gas-oil ratio in relative
units,
Rs equilibrium value of gas-oil ratio.
2.17 Vaporisation of oil component into gas phase

Vaporisation of oil component in gas phase RO,G = RO,G (pG ) is user input data array defined
in a number of pG points and interpolated for other points (PVTG (see 12.5.8)).
The keyword DRVDT (see 12.18.100) sets maximum rate of increase of vapor oilgas ratio.
2.18 Inflow from aquifer

tNavigator 4.2 supports the following type of aquifers:
numerical aquifer.
Is set via the keywords AQUCON (see 12.16.12), AQUNUM (see 12.16.11);
constant-flux aquifer (analytic aquifer).

Is set via the keywords AQUFLUX (see 12.16.2), AQUANCON (see 12.16.10);
A water flow rate from aquifer is calculating the following way:
Qai = Fa Ai m (2.97)
where:
Qai - inflow rate from the aquifer to block i;
2.17. Vaporisation of oil component into gas phase 80

Fa - the aquifer constant flux, entered by the user (parameter 2 of AQUFLUX

(see 12.16.2));
Ai - the area of the connection of block i;
m - influx multiplier (parameter 10 of the keyword AQUANCON (see 12.16.10)).
Fetkovich aquifer (analytic aquifer).

Is set via the keywords AQUFETP (see 12.16.6), AQUANCON (see 12.16.10),
AQUFET (see 12.16.4);
A water flow rate from aquifer is calculating the following way:
d
Qai = (Wai ) = Ji (pa + pc pi + g(di da )) (2.98)
dt
where:
Qai - inflow rate from the aquifer to block i;

Wai - total influx from the aquifer to block i;
J - Productivity Index of the aquifer;
i - aquifer connection area to block i;
pa - pressure in the aquifer;
pc - water pressure in block i;
pi - capillary pressure;
- water density in the aquifer;
di - depth of block i;
da - aquifer datum depth.
mi Ai
i is defined the following way: i = mi Ai
where:
Ai - area of the block connected to the aquifer;

mi - aquifer influx coefficient multiplier.
Carter-Tracy aquifer (analytic aquifer).

Is set via the keywords AQUTAB (see 12.16.9), AQUANCON (see 12.16.10), AQUCT
(see 12.16.8);
The average inflow rate from the aquifer to a grid block i for timestep t is calculated
by the following formula:
Qai = i (a bp) (2.99)
where:
p - change of pressure p for timestep p: p(t + t) p(t);

i - is the area fraction for each connection block;
2.18. Inflow from aquifer 81

mi Ai
i = mi A i
The number a is calculated by the following formula:
pai Wa (t)PID0 (t + t)D

1
a= (2.100)
Tc PID (t + t)D tD PID0 (t + t)D
The number b is calculated by the following formula:

b= (2.101)
TC (PID (t + t)D tD PID0 (t + t)D )
where:
pai - change of pressure pa0 + g(di da ) pi (t + t);

PID0 - derivative of PID by tD ;
PID - pressure influence function (dimensionless);
t
tD = Tc .
Time constant Tc is defined by the following way:
W Ct ro2
Tc = (2.102)
ka c1
where:
ka - aquifer permeability;
- aquifer porosity;
W - water viscosity in the aquifer;
Ct - total compressibility (rock + water);
ro - aquifer inner radius;
c1 - constant which is equal to 0.008527 (METRIC) or 0.006328 (FIELD).
The aquifer influx constant is defined by the following way:
= c2 hCt ro2 (2.103)
where:
c2 - constant which is equal to 6,283 (METRIC) or 1,1191 (FIELD);

h - aquifer thickness;
- angle subtended by the aquifer boundary from the center of the reservoir,
divided by 360 ( ).

Wa (t) - total aquifer influx.

Pressure drop at the aquifer boundary is calculated by the following way:
Qa
pa0 p = PID (tD ) (2.104)

where:
pa0 - initial pressure of water in the aquifer;

p - average water pressure on the aquifer boundary;
Qa - aquifer inflow rate.
constant head/pressure water aquifer.

Is set via the keywords AQUCHWAT (see 12.16.3), AQUANCON (see 12.16.10).
The water flow rate into a grid block from aquifer is calculated using the formula:
d
Qai = (Gai ) = Ji [pa + pc pi + g(di da )] (2.105)
dt
where:
Qai water flow rate into a grid block i from aquifer;

Gai cumulative influx from the aquifer to grid block i;
J aquifer productivity index;
i area fraction for the connection to grid block i;
pa pressure in aquifer;
pc capillary pressure;
pi the pressure in a connecting grid block i;
water density in the aquifer;
di grid block depth;
da datum depth for aquifer.
dimensions for aquifers should be specified via AQUDIMS (see 12.16.1).
Brine option is supported for aquifers (BRINE (see 12.1.58)) (salt concentration is set via
keywords AQUFETP (see 12.16.6), AQUFET (see 12.16.4), AQUCT (see 12.16.8)).
AQANTRC (see 12.16.7) the keyword specifies initial tracer concentrations for analytic
aquifers (keywords AQUFET (see 12.16.4), AQUFETP (see 12.16.6), AQUCT (see 12.16.8),
AQUFLUX (see 12.16.2)).

2.19. Well tNavigator-4.2
2.19 Well
2.19.1 Well approximation
Well is approximated differently depending on computation mesh. Let us consider source
of phase QP = QP (pP , N,t) in block l in the case of uniform computation mesh and finite
difference approximation. We define QP on surface of cylinder of radius rw with perforated
well region as its axis as
QP (pP , N,t) = T (t) MP (pP , SW , SG )(pP pBH (t) av (p, N)g(D DBH )) (2.106)
where
MP (pP , SW , SG ) phase mobility, known, will be defined below, see section 5.7.5,
pBH (t) bottom hole pressure, known or calculated from the value q(t) of user
defined well rate,
av (p, N) average wellbore density, depends on discrete approximation chosen for
the equations (2.1)(2.4), and will be defined below, see section 5.7.6 (known)
D, g = const have been defined before,
DBH bottom hole depth (known)
T (t) well productivity index (known), may be defined by user (COMPDAT (see
2Kmult (t)c Kh
12.18.6)), otherwise calculated according to T = , see section 5.7.2.
(ln(r0 /rw ) + s)
Here
Kmult (t) multiplier (known, WPIMULT (see 12.18.28))
c = const units conversion factor (known)
Kh (known) may be defined by user (COMPDAT (see 12.18.6)) or calculated
as product of h = const, well perforated interval height (known), and K perme-
ability in plane perpendicular to well axis, depends on the discrete approximation
chosen for the equations (2.1)(2.4), and will be defined below, see section 5.7.3
(known)
r0 is pressure equivalent radius, may be defined by user, COMPDAT (see
12.18.6), otherwise its approximation depends on the discrete approximation cho-
sen for the equations (2.1)(2.4), and will be defined below, see section 5.7.4.
rw = dw /2 = const well radius (known, COMPDAT (see 12.18.6))
s = s(x, y, z,t) skin effect term (known, COMPDAT (see 12.18.6))
In this case source of component c will be equal to
qc = xc,P P QP (p, N) (2.107)
P
where
2.19. Well 84
xc,P = xc,P (p, N) moles of component c per mole of phase P,

P = P (p, N) phase molar density, see 2.13,
QP (p, N) phase rate in reservoir conditions, calculated in (2.106).
The keyword WRFT (see 12.18.190) sets output of well RFT data. The following data
will be written to RFT file: pressure, saturation and depth for each grid block in which a
well has a connection.
The detailed description of well mathematical model is in the section 5.7.
2.19.2 Group control

tNavigator supports the following possibilities to specify group control:
GRUPTREE (see 12.18.85) the keyword sets tree structure for multi-level group
control. The tree can consist of an arbitrary number of levels. The field FIELD occupies
the top of this tree. Groups that have other groups as children cannot have wells.
(Wells are assigned to groups in the keyword WELSPECS (see 12.18.3)). Thus a
group either contains wells (that is a well-group) or has other groups as children (that
is a node-group). Groups without a parent group will have a parent group FIELD.
GCONPROD (see 12.18.72) group control for producers.
GCONINJE (see 12.18.81) group control for injectors.
GCONSUMP (see 12.18.82) gas consumption and import rates for groups.
GUIDERAT (see 12.18.73) The keyword specifies a general formula for calculating
production guide rates (for group control, keyword GCONPROD (see 12.18.72)).
Group flow rate targets are distributed among the wells in proportion to their guide
rates.
Default: wells guide rate is equal to its potential flow rate at the beginning of each
time step (description of wells potential flow rate is in the section 5.7.7).
This keyword provides a means of automatically weighting production well guide rates
to take account of their production ratios. Because it could be advantageous to weight
the guide rates to discriminate against wells with high gas-oil ration or water cut.
WGRUPCON (see 12.18.80) specifies well guide rates for group control.
GSATPROD (see 12.18.83) specifies production rate for satellite groups.
GSATINJE (see 12.18.84) specifies injection rate for satellite groups.
keywords GRUPSALE (see 12.18.167) and GCONSALE (see 12.18.168) specify the
group gas sales rate.
GRUPFUEL (see 12.18.169) specifies the group gas fuel rate.
2.19.2. Group control 85

2.19.3 Separators
For black oil model (E100 data type):
SEPVALS (see 12.18.142) This keyword defines the initial separator conditions (first use
of the keyword) and changes them during the simulation (next uses of the keyword). The first
SEPVALS must be followed by the keyword GSEPCOND (see 12.18.143), which allocates
well groups to separators. If the separator corresponds to a group, all wells of this group use
this separator.
For compositional models (E300 data type):

FIELDSEP (see 12.15.20) This keyword specifies field separator. All the wells use this
separator for default. To specify different separator for one well or for well group one should
use the keywords SEPCOND (see 12.18.144), WSEPCOND (see 12.18.145).
SEPCOND (see 12.18.144) This keyword specifies separator conditions (the first us-
age of this keyword) or re-specifies separator conditions (the nest usages of this keyword).
The separator conditions are associated with the well via the keyword WSEPCOND (see
12.18.145).
2.19.4 Multisegment well

The structure of multisegment well is specified via the keyword WELSEGS (see 12.18.11).
WSEGDIMS (see 12.1.38) dimensions of data for multisegment well (not necessarily key-
word, tNavigator allocates memory dynamically). WSEGTABL (see 12.18.12) specifies
calculation of segment pressure drops from VFP tables.
WSEGVALV (see 12.18.13) specifies calculation of segment pressure drops for sub-critical
valve.
Definition of location of completions in a multisegment well COMPSEGS (see 12.18.20)
(COMPSEGL (see 12.18.21) for LGR case).
Adding or removing fluids to or from a segment in a multisegment well WSEGEXSS

(see 12.18.15). Adding or removing fluid depends on a specified rate or segments pressure.
The source or sink for this fluid is external.
WFRICSEG (see 12.18.19) (WFRICSGL (see 12.18.19) in LGR case) this keyword
is used to define the segment structure and the connection locations of a multisegment
well via parameters of the keyword WFRICTN (see 12.18.17) (WFRICTN (see 12.18.17)
in LGR case). WFRICSEG (WFRICSGL (see 12.18.19)) provides an easy way of transfor-
mating a friction well into a multisegment well by changing the keyword name to WFRICSEG.
WSEGFLIM (see 12.18.16) defines segment of multisegment well as a flow limiting

valve.
2.19.3. Separators 86
WSEGAICD (see 12.18.14) designates a segment of multisegment well as an autonomous

inflow control device.
2.19.5 MULTIphase injection

The keywords that can be used for multi-phase injection:
2-nd parameter of the keyword WCONINJE (see 12.18.36) should be set to MULTI
(multi-phase injection). The preferred phase of the well will be injected (specified via
WELSPECS (see 12.18.3));
5-th parameter of WCONINJE (see 12.18.36) specifies the surface flow rate of the
preferred phase;
parameters 12-14 of WCONINJE (see 12.18.36) specify surface volume proportion of

phases in a multi-phase injector;
the same way multi-phase injection MULTI can be used in the keywords WCONINJH
(see 12.18.39), WCONINJP (see 12.18.38), WWAG (see 12.18.44).
2.19.6 WAG injection mode

The keywords to simulate water-gas injection mode: WCYCLE (see 12.18.42), WELLWAG
(see 12.18.43), WWAG (see 12.18.44).
2.19.7 DCQ. Gas Field Model

tNavigator support the following operations in Gas Field Model:
Specification of swing and profile factors for FIELD SWINGFAC (see 12.18.172).
The required rate of gas production has a seasonality profile. One should specify
an annual profile monthly multipliers to the mean rate or DCQ (Daily Contracted
Quantity). For each month: target gas production rate for FIELD is equal to the DCQ
multiplied by the months profile factor.
Seasonality profile for groups GSWINGF (see 12.18.173). The keyword GASFIELD
(see 12.1.90) sets if multiple contract groups are required.
Each contract group has its name, swing and profile factors.
Target gas production monthly rate for FIELD for the second pass the keyword GAS-
FTARG (see 12.18.183). Decrement values for these rates the keyword GASFDECR
(see 12.18.184).
The keywords GASYEAR (see 12.18.175) and GASPERIO (see 12.18.176) sets con-
tract periods. These keywords should be used instead of DATES (see 12.18.105),
TSTEP (see 12.18.106). GASPERIO (see 12.18.176) should be used if the length of
the contract period is less than a year.
2.19.5. MULTIphase injection 87

Well operations and reports during the contract period should be entered between
the keywords GASBEGIN (see 12.18.179) and GASEND (see 12.18.180). Time in
the contract period (when the operation should take place) should be specified via
GASMONTH (see 12.18.181).
Initial DCQ (Daily Contracted Quantity) for each well should be specified via GDCQ
(see 12.18.174).
GDCQECON (see 12.18.178) minimum economic value of DCQ for each contract
group. If DCQ falls below this value, then all producers in this group will be shut or
stopped. If the contract group is FIELD, then the calculation will be terminated.
GASFCOMP (see 12.18.185) the using of compressors in models with standard

network option (see section 2.19.9).
2.19.8 Gas Lift Optimization

The keywords that can be used in Gas Lift Optimization option: LIFTOPT (see 12.18.213),
GLIFTOPT (see 12.18.215), WLIFTOPT (see 12.18.216), GLIFTLIM (see 12.18.214).
This option is used to allocate the lift gas to each well to meet well, group or field
production targets. If production targets cannot be met, this option calculates how to use the
existing lift gas resources the best way: how to allocate lift gas to the wells that lead to the
best results of oil production.
Description of gas lift optimization option:
Gas lift is simulated via VFP tables (VFPPROD (see 12.18.57), VFPCORR
(see 12.18.61)).
An increment size for lift gas injection rate is specified (METRIC: sm3 /day, FIELD:
Msc f /day) (1-st parameter of LIFTOPT (see 12.18.213)). The lift gas resources are
divided in discrete increments of uniform size.
The minimum economic gradient (2-nd parameter of LIFTOPT (see 12.18.213)) of im-
provement in oil production rate for increase in lift gas injection rate by one increment
is specified (METRIC: m3 /sm3 , FIELD: stb/Msc f ). This minimum economic gradient
corresponds to the moment when the cost of the extra amount of oil produced via an
increase in the lift gas injection rate is equal to the cost of supplying the extra amount
of lift gas.
Gas Lift optimization option finds out, if the lift gas increment must be added to
each well injection rate or subtracted from it. For each well the value Winc (weighted
incremental gradient) is calculated the increment of field oil production rate (due to
increment in the gas lift at one increment value) multiplied by wells weighting factor
and divided by value of increment in the gas lift. If the result value is less than the
2.19.8. Gas Lift Optimization 88

minimum economic gradient, then the next lift gas increment is not allocated to this
well.
Formula of Winc :
fw TO
Winc =
GLinc
where:
fw wells weighting factor (4-th parameter of WLIFTOPT (see 12.18.216));
TO increment (or decrement) in field oil production rate;
GLinc increment (or decrement) in the gas lift.
Formula of Winc in case if the 6-th parameter of the keyword WLIFTOPT (see
12.18.216) is specified):
fw TO
Winc =
GLinc + fG TG
where:
fG gas production rate weighting factor (6-th parameter of WLIFTOPT (see
12.18.216));
TG increment (or decrement) in field gas production rate.
For groups lift gas increments are allocated in turn to the well that has the largest
weighted incremental gradient Winc .
Additional group parameters are specified using the keywords GLIFTOPT (see
12.18.215), GLIFTLIM (see 12.18.214).
2.19.9 Standard network option

Standard network structure is the same as the hierarchy specified in GRUPTREE (see
12.18.85). If the network should have a structure different from standard group hierarchy
then one should use an extended network option 2.19.10 (the keyword NETWORK (see
12.1.84)).
Production network is specified via GRUPNET (see 12.18.96). Pumps and compressors
GNETPUMP (see 12.18.95), GASFCOMP (see 12.18.185). Automatic compressors also
supported.
2.19.10 NETWORK option. Automatic chokes. Compressors

NETWORK option is specified via the keyword NETWORK (see 12.1.84). The keyword
sets dimensions for extended network model. The extended network model is specified via
keywords NODEPROP (see 12.18.88), BRANPROP (see 12.18.87).
Injection network could be specified via the keyword GNETINJE (see 12.18.91).
2.19.9. Standard network option 89

NETWORK option is used to provide variable THP limits to groups of wells, which de-
pend on the groups flow rates according to a set of pipeline pressure loss relationships. If
NETWORK option is used well THP limits will be calculated dynamically by balancing the
flow rates and pressure losses in the network.
NETBALAN (see 12.18.112) sets network calculation parameters (convergence tolerance,

maximum number of iterations in the network balancing calculation etc.).
Tree-structure for groups should be defined.
GRUPTREE (see 12.18.85) sets tree structure for multi-level group control. The tree
can consist of an arbitrary number of levels. The field FIELD occupies the top of this tree.
Groups that have other groups as children cannot have wells. (Wells are assigned to groups
in the keyword WELSPECS (see 12.18.3)). Thus a group either contains wells (that is a
wellgroup) or has other groups as children (that is a node-group).
In case of extended network model group structure can be different from the structure
specified by GRUPTREE (see 12.18.85) (the bottom nodes in the tree should be the same
(i.e. well groups)). BRANPROP (see 12.18.87) specifies branch properties. NODEPROP (see
12.18.88) specifies node properties. The top node should have a fixed pressure. WNETDP
(see 12.18.222) sets fixed pressure drop value between a wells tubing head pressure and its
groups corresponding node in the network.
The network can consist of two or more separate trees. Each tree should have its own
fixed pressure terminal node at the top. Child groups also can be nodes with fixed pressure
(so pressures in sub-networks are independent of the main network but flows of sub-networks
will be added into main network flow).
NWATREM (see 12.18.94) removes water from a node in the extended network.
NCONSUMP (see 12.18.89) sets a gas consumption rate at a specified node in the
extended network.
Automatic chokes.
An automatic choke can adjust the pressure loss across a choke in a designated network
branch to meet a groups production rate target.
A branch is set as a choke via a flag YES in parameter 3 of the keyword NODEPROP
(see 12.18.88) for the inlet node of the choke. The branch should have a number 9999 as a
corresponding VFP table number (in the keyword BRANPROP (see 12.18.87)).
NWATREM (see 12.18.94) removes water from a node in the extended network.
2.19.10. NETWORK option. Automatic chokes. Compressors 90

Automatic compressors (pumps).
Compressors are specified via the keyword NETCOMPA (see 12.18.92). Compressors
(pumps) are turned on if a nominated group cannot meet its production rate target (which
is specified with keyword GCONPROD (see 12.18.72)). Multi-level compressors can be
specified (compression is increased one level at a time until the nominated group can meet
its production target.
Automatic compressors in the network can be switched off via the keyword COMPOFF (see
12.18.93) (except for compressors defined to stay permanently 9-th parameter PERM of
NETCOMPA (see 12.18.92)).
2.19.11 Well prioritization option

Keywords PRIORITY (see 12.18.78), GCONPRI (see 12.18.75) set the group control option
with well prioritization.
This option is alternative to the method of distribution group production rates among
wells according to their guide rates (is this case groups are specified via GCONPROD (see
12.18.72)).
Well prioritization option description.
Wells priorities are calculated according to formula specified in PRIORITY (see

12.18.78).
Wells are turned on in decreasing order of their priority (well with the highest priority
is the first).
Wells are turned on until groups production rate limit is exceeded.
A rate of well, which exceeds the groups limit, is cut to meet the limit (in spite of its
own limits WCONPROD (see 12.18.34)).
Wells with low priority are closed until they are selected to produce.
Wells, which violate economic limits, and are closed manually cant be selected to
produce.
2 priority formulas can be specified and they can be used as PRI and PR2 in GCONPRI
(see 12.18.75)).
If 2 limits that have different priority formulas are exceeded, then to close the well
with the lowest priority the formula is chosen for which limit is exceeded more (in
percentage terms).
2.19.11. Well prioritization option 91

Priorities are calculated for the well at each Newton iteration of time step for first
NUPCOL (see 12.18.208) iterations via the formula (coefficients are specified in
PRIORITY (see 12.18.78)):
A + BPO +CPW + DPG
PRIORITY =
E + FPO + GPW + HPG
where:
Pp potential well rate for the phase p (description of wells potential flow rate
is in the section 5.7.7);
A, B, C , D, E , F , G, H coefficient from PRIORITY (see 12.18.78).
Wells priorities calculated via formulas PRIORITY (see 12.18.78) can be overriden
via numbers specified directly in the keyword WELPRI (see 12.18.79);
In group hierarchy both methods of potential guide rates GCONPROD (see 12.18.72)
and well prioritization GCONPRI (see 12.18.75) can be used at the same time, except
for the case when the group uses guide rate method and this group is subgroup of the
group that uses well prioritization.
When 2 methods are used at the same time, then first prioritization groups are solved,
and then the producers in the remaining part of group hierarchy that use guide rates.
2.19.12 Prioritized drilling queue. Sequential drilling queue

tNavigator supports creation of well drilling queue. The well from queue will be opened in
decreasing order of their drilling priority if it is needed to maintain a group rate target under
group control by guide rate (GCONPROD (see 12.18.72), GCONINJE (see 12.18.81)).
If a group cannot provide its production volume, the producer with the highest drilling priority
(that belongs to that group, and doesnt belong to any other group under the same production
control) will be opened automatically. If a group cannot provide its injection volume, the
injector with the highest drilling priority (that belongs to that group, and doesnt belong to
any other group under injection control for the same phase) will be opened automatically.
There are two drilling queue types:
1. sequential drilling queue, specified via the keyword QDRILL (see 12.18.203). Wells
from sequential queue are opened in the sequence in which they are placed in the
queue;
2. prioritized drilling queue, specified via the keyword WDRILPRI (see 12.18.201). Wells
from prioritized queue are opened in decreasing order of their drilling priority. The key-
word DRILPRI (see 12.18.200) specifies the default priority formula for the prioritized
drilling queue.
2.19.12. Prioritized drilling queue. Sequential drilling queue 92

2.20. Polymer Flood tNavigator-4.2
At any run time only one type of drilling queue may exist (two types of queue cannot work
together).
Time taken to drill the well is specified via the keyword WDRILTIM (see 12.18.202).
The keyword WDRILRES (see 12.18.205) prevents from drilling two wells in one grid
block.
2.20 Polymer Flood

In tNavigator the following options are supported to model polymer flood:
Polymer flood option POLYMER (see 12.1.48) (formats E100, E300).
To enhance the polymer action it may be injected together with the alkaline (Alkaline
flooding section 2.24) and surfactant (section 2.25).
Alkaline-Surfactant-Polymer Flooding ASP model. Full description of ASP mathe-

matical model is in the section 5.9.
Special option of Polymer flooding based on BrightWater technology section 2.20.2).
If mixing of waters with different salinities is used (BRINE (see 12.1.58)), then poly-
mer solution viscosity can be set as function of salt concentration. The keywords
SALTNODE (see 12.7.6) and PLYVISCS (see 12.7.8) should be specified.
Polymer flood in IMEX format see the section 2.20.3.
2.20.1 Polymer Flood option POLYMER

tNavigator has a Polymer Flood option initialized via the keyword POLYMER (see 12.1.48).
The following keywords can be used to Polymer flood simulation:
2.20. Polymer Flood 93

Keyword section Description

POLYMER (see 12.1.48) RUNSPEC Indicates that Polymer Food model is used
PLYADS (see 12.8.17) PROPS Polymer adsorption function
PLYMAX (see 12.8.18) PROPS Polymer and salt concentration for mixing cal-
culations
PLMIXPAR (see 12.8.19) PROPS Specifies Polymer Todd-Longstaff mixing pa-
rameter
PLYROCK (see 12.8.20) PROPS Specifies the rock properties for Polymer flood
PLYVISC (see 12.8.16) PROPS Specifies solution viscosity multiplier as a
function of polymer concentration
PLYSHEAR (see 12.8.21) PROPS Polymer solution viscosity multiplier in the
case of shear thinning
PLYSHLOG (see 12.8.22) PROPS Polymer solution shear multiplier (logarithmic
formula)
SALTNODE (see 12.7.6) PROPS Sets the data to calculate polymer solution vis-
cosity as a function of salt concentration
PLYVISCS (see 12.7.8) PROPS Sets the data to calculate polymer solution vis-
cosity as a function of salt concentration
WPOLYMER (see 12.18.151) SCHEDULE Specifies polymer concentration in the wells
injection stream
2.20.2 Polymer flooding based on BrightWater technology

Flow deflecting technologies is a way to increase efficiency of reservoir development.
For example these technologies can base on nanopolymer flooding. BrightWater technology
(developed by companies BP, Chevron and Nalco) consists in nanopolymer injection into
the formation. Particles of nanopolymers increase theirs volume (average in 10 times) at
hydrolysis or heating. The main idea is that small granules (average size 100 nm) are
injected into the formation with water phase.
Granule size is considerably smaller than pore size at 500 mD (or more) permeability.
Particles of polymers expand in formation pores in the direction from producers to injectors.
Pores in zones of active filtration are blocked and water is forced out to the zones with low
permeability. This process is called activation of nanopolymer.
In tNavigator there is nanopolymer flooding option. The following physical effects are
taken into consideration:
hydrolysis swelling rate,
nanopolymer type.
Simulator uses standard isothermal black-oil model (2.1)(2.4), nanopolymer is considered
as an admixture to water phase, that changes filtration-capacity formation properties.
Polymer can be specified via the keyword TRACERM (see 12.7.2) (the tracer for which
the holding time in the reservoir will be calculated). Polymer injection can be defined using
the keyword WTRACER (see 12.18.148).
2.20.2. Polymer flooding based on BrightWater technology 94

Let C pol and t pol nanopolymer concentration in water phase and nanopolymer holding
time in the formation. Within the bounds of this BrightWater model we consider that absolute
permeability is: k = kmult (C pol ,t pol )k0 , where k0 initial absolute permeability (that was in
the model before nanopolymer flooding), kmult (C pol ,t pol ) can be presented the following
way:
kmult (C pol ,t pol ) = 1 (1 kconc (C pol ))(1 ktime (t pol )),
where kconc (C pol ) and ktime (t pol ) are defined via tables TRMMULTC (see 12.7.10), TRM-
MULTT (see 12.7.11).
In the mathematical model the following assumption is used: permeability multiplier can
only decrease (when the polymer is injected), but not to increase (when there is the formation
washing after polymer injection). So a minimum value of permeability multiplier is taken
from all the time steps.
Temperature option and polymer flooding

Temperature option is supported for polymer flooding models (TEMP (see 12.1.60)). In
this case absolute permeability multiplier depends on the temperature.
kmult (C pol ,t pol , Tpol ) = 1 (1 kconc (C pol ))(1 ktime (t pol ))(1 ktemp (Tpol )),
where Tpol - polymer temperature. kconc (C pol ) and ktime (t pol ) are defined via tables TRM-
MULTC (see 12.7.10), TRMMULTT (see 12.7.11). ktemp (Tpol ) - the function depending on the
factor of absolute permeability on the temperature, defined via table TRMTEMP (see 12.7.12).
If any table of these three is not specified, then the corresponding value k is set to 0.
In the mathematical model the following assumption is used: permeability multiplier can
only decrease (when the polymer is injected), but not to increase (when there is the formation
washing after polymer injection). So a minimum value of permeability multiplier is taken
from all the time steps.
Keywords
2.20.2. Polymer flooding based on BrightWater technology 95

Keyword Section Description

TEMP (see 12.1.60) RUNSPEC Specifies temperature option
TRACERM (see 12.7.2) PROPS Specifies tracer list for which the holding time
in the reservoir will be calculated
TRMMULTC (see 12.7.10) PROPS Specifies the dependence between absolute
permeability multiplier and tracer concentra-
tion
TRMMULTT (see 12.7.11) PROPS Specifies the dependence between absolute
permeability multiplier and holding time in the
reservoir
TRMTEMP (see 12.7.12) PROPS Specifies the dependence between absolute
permeability multiplier and temperature
WTRACER (see 12.18.148) SCHEDULE Specifies the value of tracer concentration in
the injection stream
2.20.3 Polymer flood in IMEX format

Polymer flood models: differences in E100 and IMEX formulation.
Dead pore space (not invaded by polymer) depends on absolute permeability, not on
saturation region as in E100 format;
Polymer speed is the same as water speed (no Bvisc
poly );
Several polymer models available.

Polymer flood model in IMEX format is specifying by parameter POLY of the keyword
MODEL (see 13.5.4). Concentration of injecting polymer (kg/sm3 ) is specified by parameter
WATER of the keyword INCOMP (see 13.5.81).
System of maintenance equations:
asp
krW
UW = c k asp (p + PcW W gd)
W

C poly ads
C poly
S pv Nw sc + A poly = div W UW sc + Q poly ,
t W t W
where:
C poly concentration of dissolved polymer in water (kg/sm3 )

sc mass water density in surface conditions (kg/sm3 )
W
asp
krW water RP after ASP flooding (see below),
asp
W water viscosity after ASP flooding (see below),
Aads 3

poly adsorptional polymer potential (kg/sm ), defined as a function C poly in the
keyword PADSORP (see 13.5.76),
2.20.3. Polymer flood in IMEX format 96

Q poly mass polymer flow from external sources (kg/day)
S pv pore volume fraction which is available for polymer; it is set by the keyword
PPERM (see 13.5.77) as a function of absolute permeability
Polymer adsorption modelling. Adsorption parameters are set via the keywords PAD-
SORP (see 13.5.76) and PPERM (see 13.5.77).
PADSORP (see 13.5.76) contains two columns: the first one is polymer concentration
(kg/sm3 ), the second one is adsorptional potential Aads 3 ads
poly (kg/m ). A poly normalized by
maximal value in PADSORP (see 13.5.76) to use it in maintenance equation.
Keyword PPERM (see 13.5.77) sets a table of polymer properties dependence on absolute
RP. Properties are the following:
Ad,max maximal adsorption potential (kg/sm3 );
Ad,res residual adsorption potential (kg/sm3 );
S pv pore volume fraction which is available for polymer;
Krr f residual resistance factor.
To get real adsorptional potential Aads

poly from normalized it is multiplied by Ad,max from
the keyword PPERM (see 13.5.77).
Lets denote Ad = Aads 3
poly Ad,max , (kg/sm ). For Ad,max interpolation we use maximal per-
meability in one of the directions (i.e. max(PERMI (see 13.3.10), PERMJ (see 13.3.10),
PERMK (see 13.3.10))).
Then we put correction for adsorption using Ad,res . If Ad < Ad,res , then:
if on the previous step Ad prev > Ad,res , then on the current Ad = max(Ad,res , Ad);
if Ad prev < Ad,res , then Ad = max(Ad prev , Ad).
Water viscosity calculation. Lets denote W (p) usual viscosity, which is calculated via
VWI (see 13.5.7), CVW (see 13.5.7).
Also denote:
re f
C poly reference polymer concentration (kg/sm3 ) which is set in PREFCONC (see
13.5.79);
re f
poly reference polymer viscosity which is set in PVISC (see 13.5.80);
Polymer and water solution is considered uniform (i.e. water and polymer velocities are
equal). Viscosity model is set by the keyword PMIX (see 13.5.78) and one of its options:
2.20.3. Polymer flood in IMEX format 97

2.21. Foam modeling tNavigator-4.2
LINEAR linear model.

asp re f
W = poly + (1 )W (p) (2.108)
where is a relative polymer concentration:

C poly
= re f
(2.109)
C poly
NONLINEAR non-linear model.

asp re f
W = ( poly ) (W (p))(1) (2.110)
TABLE viscosity is set by a table as a function of polymer concentration. The first

re f
column of it is relative polymer concentration (i.e. ratio C poly /C poly ), the second one
is ratio of polymer viscosity to water viscosity.
Then we put correction for relative permeability during polymer solution mobility calcu-
lation:
asp krW
krW = (2.111)
Rk
where Rk is given by:
Ad
Rk = 1 + (Krr f 1) (2.112)
Ad,max
So, for polymer solution mobility wasp is:
asp
krW krW
wasp = asp = . (2.113)
W Ad asp
1 + (Krr f 1) Ad,max W
2.21 Foam modeling

Supported keywords:
FOAM (see 12.1.64) activates foam option in E100 models;
FOAMOPTS (see 12.11.2) sets foam modeling preferences;
FOAMADS (see 12.11.1) defines functions of foam adsorption by the rock formation;
FOAMROCK (see 12.11.3) sets rock properties;
FOAMDCYW (see 12.11.4) sets foam decay dependence on water saturation;
FOAMDCYO (see 12.11.5) sets foam decay dependence on oil saturation;
FOAMMOB (see 12.11.6) sets dependences of the gas phase mobility factor on foam
concentration;
2.21. Foam modeling 98

2.23. Asphaltene modeling tNavigator-4.2
FOAMMOBP (see 12.11.7) sets dependence of the foam mobility factor on oil
pressure;
FOAMMOBS (see 12.11.8) sets dependence of the shear on foam mobility;
SFOAM (see 12.15.51) sets initial foam concentration in grid blocks;
WFOAM (see 12.18.241) sets foam concentration in injecting stream;
TNAVCTRL (see 12.1.4) option DECAY_MODEL control of foam decay process (ad-
sorped, desorped foam participation in decay process).
2.22 Residual oil modeling

Supported keywords:
SOR (see 12.12.1) activates residual oil modeling option and sets residual oil satu-
ration values in each SATNUM (see 12.4.3) region;
SOILR (see 12.15.52) initial residual oil saturation values in each grid block;
ROMF (see 12.15.53) initial composition of residual oil in each grid block;
SOROPTS (see 12.12.2) compressibility model of residual oil.
2.23 Asphaltene modeling

Supported keywords:
ASPHALTE (see 12.1.63) activates option of asphaltene precipitation modeling and
sets oil viscosity change model type;
ASPFLRT (see 12.10.5) sets the kinetic reaction rates for the flocculation and
dissociation processes for each component;
ASPVISO (see 12.10.6) sets parameters of oil viscosity change model;
CATYPE (see 12.10.7) sets asphaltene properties for each model component;
ASPP1P (see 12.10.1) sets variable of asphaltene precipitation function. The keyword
ASPREWG (see 12.10.2) should be used in conjunction with this one. In this case
asphaltene precipitation function will depend on one variable. Two-variable function is
set by keywords ASPP2P (see 12.10.3) and ASPPW2D (see 12.10.4);
ASPREWG (see 12.10.2) defines one-variable asphaltene precipitation function;
ASPP2P (see 12.10.3) sets variables of asphaltene precipitation function. The key-
word ASPPW2D (see 12.10.4) should be used in conjunction with this one. In this case
asphaltene precipitation function will depend on one variable. Two-variable function is
set by keywords ASPP1P (see 12.10.1) and ASPREWG (see 12.10.2);
2.22. Residual oil modeling 99

2.24. Alkaline flooding tNavigator-4.2
ASPPW2D (see 12.10.4) defines two-variable asphaltene precipitation function.
2.24 Alkaline flooding

Alkaline flooding is performed via alkaline chemicals injection (high pH). Alkaline flooding
can be done simultaneously with surfactant (Surfactant injection section 2.25) and polymer
(section 2.20).
Alkaline-Surfactant-Polymer Flooding ASP model.

Full description of ASP mathematical model is in the section 5.9.
Alkaline reduces surfactant and polymer adsorption and enhance their effectiveness this
way. Alkaline also affects on water-oil surface tension.
The option switches on with the keyword ALKALINE (see 12.1.49). Alkaline concentra-
tion in the well injection steam is set via WALKALIN (see 12.18.150).
All the supported features are described below.
Alkaline adsorption.
Alkaline adsorption is calculated at each time step. The table of alkaline adsorption as a
function of its concentration is specified via the keyword ALKADS (see 12.8.26).
Desorption can be prevented (1-st parameter of ALKROCK (see 12.8.27)), then the concen-
tration of adsorbed alkaline can not decrease.
Effect on water-oil surface tension.

Alkaline affects on water-oil surface tension in combination with surfactant:
WO = WO (Csur f )Ast (Calkl )
where:
WO surface tension;
WO (Csur f ) surface tension at surfactant concentration and zero alkaline concentration
(specified via the keyword SURFST (see 12.8.9));
Ast (Calkl ) surface tension multiplier, that depends on alkaline concentration (specified
via the keyword ALSURFST (see 12.8.23)).
Effect on surfactant and polymer adsorption.
Alkaline reduces surfactant and polymer adsorption on the rock and enhance their effective-
ness this way. Mass of adsorbed surfactant and polymer is calculated via the formula:
1
Porv Mrock Cads Aad (Calkl )

where:
2.24. Alkaline flooding 100

2.25. Surfactant injection tNavigator-4.2
Porv block pore volume;
Mrock rock mass density (specified via SURFROCK (see 12.8.12), PLYROCK (see
12.8.20));
Cads concentration of adsorbed surfactant and polymer (from the keywords SUR-
FADS (see 12.8.8), PLYADS (see 12.8.17);
porosity;
Aad (Calkl ) adsorption multiplier that depends on the alkaline concentration (specified
via ALSURFAD (see 12.8.24), ALPOLADS (see 12.8.25)).
In case if the alkaline desorption is prevented then it affects on the surfactant and polymer
irreversible. Mass of adsorbed surfactant and polymer in this case is calculated via the
formula:
1
Porv Mrock Cads max
Aad (Calkl )

where:

max maximum alkaline concentration, that was reached in the block during the
Calkl
calculated period.
2.25 Surfactant injection

tNavigator has an option of Surfactant injection simulation (and solvents injection). This op-
tion is based on tracers simulation technology.

The keyword SURFACT (see 12.1.46) indicates the Surfactant option.
These chemical agents are injected to the formation as an admixture to the phase (water
in case of surfactants, oil in case of solvents) and they change the oil-water surface tension.
In tNavigator admixture influence to surface tension can be simulated using relative phase
permeability scaling ENPTRC (see 12.6.41).
Surfactant adsorption.
Surfactant adsorption is a function of surfactant concentration and is specified via the keyword
SURFADS (see 12.8.8). Mass of adsorbed surfactant (MadsSURF ) is calculated by the formula:
1
MadsSURF = Porv Mrock FA(CadsSURF )

where:
2.25. Surfactant injection 101

2.25. Surfactant injection tNavigator-4.2
Porv block pore volume;

porosity;
Mrock mass density of the rock (specified via the keyword SURFROCK (see
12.8.12));
FA(CadsSURF ) surfactant adsorption function from a local surfactant concentration
(specified via the keyword SURFADS (see 12.8.8)).
The following adsorption model is supported: each grid block retraces the adsorption
function as the surfactant concentration falls in the cell. De-adsorption is possible.
The change of wettability.

tNavigator simulates the changes to wettability of the rock that is provided by the accumula-
tion of surfactant.
the keyword SATNUM (see 12.4.3) specifies saturation function regions for oil-wettability
(properties are specified via keywords SWFN (see 12.6.13), SOF2 (see 12.6.12), SOF3 (see
12.6.15), SWOF (see 12.6.1)), also these keywords specify additional saturation functions
which are used for water-wettability case.
The keyword SURFWNUM (see 12.4.5) sets the number for every grid block specifying the
saturation function region to which it belongs for water-wettability case.
Calculating of the immiscible RP and capillary pressure. First, the water-wettability and
oil-wettability endpoints are interpolated and the curves scaled to honor these points. Second,
a weighted average of the oil-wettability value and of the water-wettability value is used.
Formula for calculation:
kr = F(kr )ow + (1 F)(kr )ww
where:
F ratio, specified via SURFADDW (see 12.8.13) (F function of adsorbed surfactant
concentration);
(kr )ow the scaled oil-wettability value of kr , specified via SATNUM (see 12.4.3);
(kr )ww the scaled water-wettability value of kr , specified via SURFWNUM (see
12.4.5).
The keyword SURFDW (see 12.8.14) can be used instead of the keyword SURFADDW
(see 12.8.13). In the keyword SURFDW (see 12.8.14): F function of the concentration of
dissolved (in the water) surfactant in grid block.
In SURFADDW (see 12.8.13): F function of adsorbed surfactant concentration in grid
block.
In case of table SURFDW (see 12.8.14) interpolation occurs only water RP (surfactant dis-
solved in water affects only water RP but not on oil and gas RP). In the case of table
SURFADDW (see 12.8.13) adsorbed surfactant affects all three phases RP.
2.25. Surfactant injection 102

2.26. Waters with different salinities tNavigator-4.2
2.25.1 Keywords

SURFACT (see 12.1.46) RUNSPEC Defines that surfactants will be used in the
model
SURFACTW (see 12.1.47) RUNSPEC Defines that surfactants will be used in the
model, the change of wettability will be simu-
lated
SURFADS (see 12.8.8) PROPS Specifies surfactant adsorption functions
SURFADDW (see 12.8.13) PROPS Coefficient is used to simulate the change to
wettability due to adsorbed surfactant concen-
tration
SURFDW (see 12.8.14) PROPS Coefficient is used to simulate the change to
wettability due to dissolved surfactant concen-
tration in grid block
SURFCAPD (see 12.8.11) PROPS Surfactant capillary de-saturation functions
SURFST (see 12.8.9) PROPS Water-oil surface tension as a function of sur-
factant concentration
SURFVISC (see 12.8.10) PROPS Viscosity of water solution as a function of
surfactant concentration
SURFROCK (see 12.8.12) PROPS Specifies surfactant-rock properties
ENPTRC (see 12.6.41) PROPS In tNavigator admixture influence to surface
tension is simulated using relative phase per-
meability scaling
SURFNUM (see 12.4.4) REGIONS Surfactant miscible region number
SURFWNUM (see 12.4.5) REGIONS Saturation function region number in water-
wettability case
WSURFACT (see 12.18.149) SCHEDULE Specifies the concentration of surfactant in the
injection stream
2.26 Waters with different salinities

tNavigator supports the following options to simulate waters with different salinities:
BRINE (see 12.1.58) option this keywords sets that mixing of waters with different
salinities will be used.
Additional option to BRINE (see 12.1.58) Fresh water injection into the saline
reservoir. Reservoir salt is dissolved that leads to formation porosity changes and to
increasing of salt concentration in the water, water density and viscosity increase too
section 2.26.1.
Low salinity water simulation LOWSALT (see 12.1.59). In this case the following
effect is simulated: salinity dependence of the oil and water relative permeabilities and
the water-oil capillary pressure as functions of the salt concentration 2.26.3.
2.25.1. Keywords 103

2.26.1 Fresh water injection into the saline reservoir

Salination of reservoir production layers is the way to localize residual reserves of hydro-
carbons, determine the efficiency of reservoir development, determine oil
Flooding efficiency depends on pore filling of salt and depends on salt solubility in the
fresh water.
tNavigator has an option simulation of fresh water injection into the saline reservoir.
Option BRINE (see 12.1.58) This keyword indicates that the Brine Tracking option is
enable, to allow the modeling of waters with different salinities.
Salt washing-out with fresh water is simulated the following way:
ROCKSALT (see 12.15.40) (mass of reservoir salt that can be dissolved kg);
initial reservoir salt concentration can be specified through its saturation SRSALT
(see 12.15.43);
spreading of injected water is calculated (water salinity is specified via WSALT (see
12.18.152));
reservoir salt is dissolved that leads to formation porosity changes and to increas-
ing of salt concentration in the water, water density and viscosity increase too (see
PVTWSALT (see 12.7.14)) (The keyword BDENSITY (see 12.7.9) specifies the brine
surface density variation with the salt concentration);
oil viscosity and water viscosity are equalized that leads to improvement of oil forcing
out;
ultimate concentration of dissolved (in the water) salt SALTPROP (see 12.7.4);
reservoir salt dissolution rate is directly proportional to difference of salt solution
(current and saturated).
The keyword SALTTRM (see 12.7.5) sets the dependence between permeability and
amount of dissolved reservoir salt. SALTTRM (see 12.7.5) and SALTPROP (see 12.7.4)
can be specified for different PVT regions.
In tNavigator admixture influence to surface tension is simulated using relative phase

permeability scaling ENPTRC (see 12.6.41).
The initial salt concentration (kg/m3 ) can be specify via the keyword SALT (see
12.15.41). The keyword should be used when the initial state has been set by enumera-
tion (keywords PRESSURE (see 12.15.8), RS (see 12.15.31), RV (see 12.15.32), SGAS
(see 12.15.11) and SWAT (see 12.15.10)). For a run initialized by equilibration EQUIL
(see 12.15.2), the keyword SALTVD (see 12.15.42) should be used instead of SALT (see
12.15.41) (salt concentration versus depth for equilibration).
2.26.1. Fresh water injection into the saline reservoir 104

2.26.2 Keywords

BRINE (see 12.1.58) RUNSPEC This keyword indicates that the Brine Track-
ing option is enable, to allow the modeling of
waters with different salinities
PVTWSALT (see 12.7.14) PROPS Specifies water PVT data for runs in which the
Brine option is active
BDENSITY (see 12.7.9) PROPS Specifies the brine surface density variation
with the salt concentration
SALTPROP (see 12.7.4) PROPS Specifies properties of dissolved and reservoir
salt: concentration of saturated salt solution,
density of reservoir salt, solution rate constant
of reservoir salt
SALTTRM (see 12.7.5) PROPS Specifies the dependence between permeabil-
ity and amount of dissolved reservoir salt
ENPTRC (see 12.6.41) PROPS In tNavigator admixture influence to surface
tension is simulated using relative phase per-
meability scaling
SALT (see 12.15.41) SOLUTION Specifies initial salt concentration for each grid
block
SALTVD (see 12.15.42) SOLUTION Specifies initial salt concentration versus depth
for equilibration
ROCKSALT (see 12.15.40) SOLUTION Specifies initial mass of reservoir salt for each
grid block
SRSALT (see 12.15.43) SOLUTION Specifies initial reservoir salt concentration
through its saturation
WSALT (see 12.18.152) SCHEDULE Specifies the concentration of salt in the well
injection stream
2.26.3 Low salinity option

This option is activated via the keyword LOWSALT (see 12.1.59). (this keyword automat-
ically turns on the option BRINE (see 12.1.58) simulation of waters with different salinities
section 2.26.1.)
If the option LOWSALT is used then the oil and water RP and the water-oil capillary
pressure are functions of the salt concentration.
High and low salinity saturation regions are set via the keywords SATNUM (see 12.4.3)
and LWSLTNUM (see 12.4.6) (or LSNUM (see 12.4.6) analogue of LWSLTNUM).
Then oil and water table saturation end points are interpolated (index i) via the formulas
using high (index h) and low (index l ) salinity tables saturation end-points:
2.26.2. Keywords 105

2.27. Scale deposition model tNavigator-4.2

i = F Sl + (1 F )Sh (minimum water saturation (connate))
SW c 1 Wc 1 Wc
i l h
SW cr = F1 SW cr + (1 F1 )SW cr (critical water saturation)
i l h
SW max = F1 SW max + (1 F1 )SW max (maximum water saturation)
i l h
SOW cr = F1 SOW cr + (1 F1 )SOW cr (residual oil saturation in water-oil system)

i
SOGcr l
= F1 SOGcr h
+ (1 F1 )SOGcr (residual oil saturation in gas-oil system)
F1 is a function of the salt concentration (set via the keyword LSALTFNC (see 12.7.15)).
Then RP and capillary pressures are calculated the following way:

i = F kl + (1 F )kh
krW 1 rW 1 rW

i
krOW l
= F1 krOW h
+ (1 F1 )krOW

i
krOG l
= F1 krOG h
+ (1 F1 )krOG
picOW = F2 plcOW + (1 F2 )phcOW
Where:
F2 is a function of the salt concentration (set via the keyword LSALTFNC (see 12.7.15)).
The high and low water and oil RP and capillary pressures are calculated from the high
and low salinity saturation tables by applying two-point saturation end-point scaling.
h = f (S , Si i h
krW W W cr ), SW max , krW max
l = f (S , Si i l
krW W W cr ), SW max , krW max
analogously for krOW , krOG , pcOW .
2.27 Scale deposition model

The cumulative effects of scale deposited around the well connections and the resulting
degradation of the productivity index due to sea water injection are supported in tNavigator
via the following keywords:
SCDATAB (see 12.18.229) set the reduction coefficient for the productivity index
of each connection in a well dependence of the current amount of scale deposited per
unit length of perforated interval as a table;
SCDPTAB (see 12.18.227) defines total rate of scale deposition per unit flow rate
of water into a well connection dependence of the fraction of sea water present in the
water flowing through this connection as a table;
SCDPDIMS (see 12.1.108) set the dependences number;
2.27. Scale deposition model 106

2.28. Dual porosity tNavigator-4.2
WSCTAB (see 12.18.230) assign tables to individual wells;
SCDPTRAC (see 12.18.228) note tracer name, which concentration represents the
fraction of sea water present in the water flowing into a well.
2.28 Dual porosity

Dual porosity is specifying by the keyword DUALPORO (see 12.1.76).
Dual permeability DUALPERM (see 12.1.77).
Dual porosity. In a reservoir with the dual porosity there are two systems: rock matrix
(the biggest part of the reservoir) and fractures (which have high permeability).
Dual porosity single permeability: fluid flow between matrix cells is possible only us-
ing fractures. Fluid flow through the reservoir is possible only in fractures.
Dual porosity dual permeability: fluid flow between neighboring matrix cells is possible.
If these options are used, for every geometric grid block we consider two cells: the
matrix part and the fracture part of this block. One can specify their properties (porosity,
permeability etc.) independently.
If the keyword DUALPORO (see 12.1.76) or DUALPERM (see 12.1.77) is used, the
number of layers in the Z-direction should be even (this number is entered by the third
parameter of the keyword DIMENS (see 12.1.25) (NZ). The first half of the grid blocks
corresponds to the matrix cells, and the second half fracture cells. tNavigator automatically
create non-neighbor connections which correspond to the matrix-fracture flows.
The keyword PERMMF (see 12.2.14) sets permeability for matrix-fracture blocks.
The keyword NODPPM (see 12.1.83) cancels a multiplication of permeability (for the
fracture blocks) by porosity (fracture blocks) during the dual porosity run. Since this mul-
tiplication is used to obtain a net bulk fracture permeability one have to enter this value
manually if NODPPM is enable.
DPNUM (see 12.2.65) specifies reservoir fields that should be considered as single
porosity fields.
DPGRID (see 12.2.66) if the keyword is enable one should specify grid data only for
matrix blocks (NX * NY * (NZ/2)); values for fracture blocks will be obtained (copied) from
corresponding matrix blocks.
This operation is applied for the values specified by following keywords: DX (see 12.2.2),
DY (see 12.2.2), DZ (see 12.2.2), PERMX (see 12.2.13), PERMY (see 12.2.13), PERMZ
(see 12.2.13), PORO (see 12.2.24), TOPS (see 12.2.6), NTG (see 12.2.25), DZNET (see
12.2.26), ZCORN (see 12.2.9), DEPTH (see 12.3.27). This operation is applied only for
2.28. Dual porosity 107

fracture blocks which dont have manually input grid data.
THCONMF (see 12.2.72) specifies the matrix to fracture thermal conductivity value for
each matrix block in dual porosity run (2.28) with THERMAL (see 12.1.50) option.
Transmissibility calculations in dual porosity runs. Matrix-fracture transmissibility is

calculated via the formula:
Tr = CDARCY K V
where K X-direction permeability of the matrix blocks X,
V matrix cell bulk volume,
sigma-factor.
sigma-factor can be specified for whole reservoir SIGMA (see 12.2.67) or different
values for different grid blocks can be entered SIGMAV (see 12.2.68).
Sigma-factor is related to the distances between fractures (matrix block sizes) in X, Y
and Z directions:
1 1 1
= 4( 2 + 2 + 2 ),
lx ly lz
lx , ly and lz the distances between fractures (matrix block sizes) in X, Y and Z directions.
(These distances are not the dimensions DX (see 12.2.2), DY (see 12.2.2), DZ (see 12.2.2).)
Default. If no one of the keywords SIGMA, SIGMAV (see 12.2.68), LTOSIGMA (see
12.2.69) is specified, sigma-factor will be considered as zero.
Viscous Displacement.
VISCD (see 12.1.82) the keyword sets that the Viscous displacement option will be
used in the dual porosity run.
If this option is used, one should specify the distances between fractures (matrix block sizes)
in X, Y and Z directions using keywords LX (see 12.2.64), LY (see 12.2.64), LZ (see
12.2.64).
Viscous displacement fluid flow under the influence of pressure gradient. One can
observe a pressure gradient in the dual porosity system. This gradient moves the fluid in the
fracture towards the production well. If this gradient is small and fracture permeability is
high, the matrix-fracture viscous displacement under the influence of pressure gradient isnt
considered. Nevertheless, if fractions have small permeability then the matrix-fracture viscous
displacement under the influence of pressure gradient can be very important in production.
tNavigator can compute a factor using keywords LX (see 12.2.64), LY (see 12.2.64),
LZ (see 12.2.64) and LTOSIGMA (see 12.2.69). If tNavigator compute , any manually
input of this parameter (SIGMA (see 12.2.67)) in data file will be ignored.
LTOSIGMA (see 12.2.69) this keyword can be used in dual porosity run, if the option
Viscous displacement is enable (VISCD (see 12.1.82)). Using the keyword LTOSIGMA (see
12.2.69) sigma-factor multiplier can be obtained from the distances between fractures (matrix
block sizes).
2.28. Dual porosity 108


and Z directions:
fx fy fz
= 2 + 2 + 2,
lx ly lz
The values of lx , ly, lz that arent specified or are equal to zero will not be used in
calculations.
LTOSIGMA (see 12.2.69) defines f x , f y, f z.
Multipliers for sigma-factor.

Sigma-factor (defined via SIGMA (see 12.2.67), SIGMAV (see 12.2.68)) is multiplied by
the multiplier MULTSIG (see 12.18.120) (the same multiplier for whole reservoir) or differ-
ent multipliers for grid blocks can be entered using the keyword MULTSIGV (see 12.18.121).
MULTMF (see 12.2.73) the keyword specifies multiplier which is used to calculate the
matrix-fracture flows.
2.28.1 RP at dual porosity runs.

KRNUMMF (see 12.4.25) This keyword specifies the number of matrix-fracture saturation
table regions for each grid block. The keyword can be used for dual porosity runs DUAL-
PORO (see 12.1.76) and dual permeability DUALPERM (see 12.1.77).
the lower fracture) the flow from the fracture to the matrix uses a saturation table for
IMBNUMMF (see 12.4.26) This keyword specifies the number of matrix-fracture imbibi-
tion regions for each grid block. The keyword can be used for dual porosity runs DUALPORO
(see 12.1.76) and dual permeability DUALPERM (see 12.1.77) in case when hysteresis op-
tion is used (parameter HYSTER of the keyword SATOPTS (see 12.1.68)).
the lower fracture) the flow from the fracture to the matrix uses an imbibition table for
matrix, the flow from the fracture to the matrix uses an imbibition table for fracture.
2.28.2 Gravity drainage option

The following keywords are supported:
GRAVDR (see 12.1.79) This keyword switches on an option of gravity drainage

between matrix and fracture cells for dual porosity models;
2.28.1. RP at dual porosity runs. 109

2.29. Coal Bed Methane Model tNavigator-4.2
GRAVDRM (see 12.1.80) This keyword switches on an option of alternative gravity

drainage between matrix and fracture cells for dual porosity models;
DZMTRX (see 12.2.74) This keyword sets the vertical size of a block of matrix
material in dual porosity run with gravity imbibition option. One value is specified for
all grid blocks;
DZMTRXV (see 12.2.76) This keyword sets the vertical size of a block of matrix
material in dual porosity run with gravity imbibition option. Different values can be
specified for different grid blocks;
DZMATRIX (see 12.2.75) analogue to DZMTRX (see 12.2.74);
SIGMAGD (see 12.2.70) The keyword sets a sigma-factor for oil-gas system that is
used in alternative matrix-fracture coupling for matrix blocks in which the production
mechanism is gravity drainage due to the presence of gas in the fractures. One value
is specified for all grid blocks;
SIGMAGDV (see 12.2.71) The keyword sets a sigma-factor for oil-gas system that is
used in alternative matrix-fracture coupling for matrix blocks in which the production
mechanism is gravity drainage due to the presence of gas in the fractures. Different
values can be specified for different grid blocks.
2.29 Coal Bed Methane Model

Coal Bed Methane (CBM) Model can be activated COAL (see 12.1.78).
Coal Bed Methane Model is simulated via dual porosity model (2.28, DUALPORO (see
12.1.76): coal matrix and the permeable rock fractures.
Adsorption model is set by the keyword CBMOPTS (see 12.1.123).
Gas is adsorbed into the coal matrix. First de-watering of the fractures is done, then (due
to pressure drop) there is gas desorption from the surface of the coal to the fracture.
Adsorption and diffusion.

The diffusive flow of gas from the coal matrix to fracture is calculated via the following
formula:
Fg = DIFFMF Dc (GCb GCs )
where:
Fg gas flow;
Dc diffusion coefficient (DIFFCOAL (see 12.9.1));
GCb bulk gas concentration;
2.29. Coal Bed Methane Model 110

GCs surface gas concentration (function of fracture pressure, specified via LANG-
MUIR (see 12.9.2)). In different CBM regions different properties can be specified
(CBM regions COALNUM (see 12.4.15)). Multipliers for concentration values are
set via the keyword LANGMULT (see 12.9.3).;
DIFFMF diffusivity: DIFFMF = DIFFMMF Vol ;
DIFFMMF multiplier specified via the keyword DIFFMMF (see 12.2.99);
Vol block coal volume;
multiplier that can be specified for the whole field (SIGMA (see 12.2.67)) or for
each grid block (SIGMAV (see 12.2.68)).
In case if the surface gas concentration is greater than the bulk gas concentration, gas
may be readsorbed into the coal.
Fg = DIFFMF Dc SG RF (GCb GCs )
where:
SG gas saturation in the fracture;
RF re-adsorption factor (DIFFCOAL (see 12.9.1)). If RF = 0 re-adsorption is pre-

vented.
Initial coal gas concentration can be set via GASCONC (see 12.15.46).
Initial saturated coal gas concentration can be set via GASSATC (see 12.15.47).
Note GASCONC: for compositional model in E300 format the keyword GASCONC
can set the initial coal gas concentration for one component defined via GASCCMP (see
12.15.48).
Note 1 GASSATC: for the model in the format E100 the keyword GASSATC (see
12.15.47) is used for the Langmuir isotherm scaling LANGMUIR (see 12.9.2) at the ini-
tial reservoir pressure. In case if the keyword GASCONC is not specified, LANGMUIR (see
12.9.2) data will be used without scaling.
Note 2 GASSATC: for compositional model in E300 format the keyword GASSATC (see
12.15.47) is used for the Langmuir isotherm scaling (LANGMUIR (see 12.9.2) or LANG-
MEXT (see 12.9.4)) at the initial reservoir pressure and composition in the reservoir for
one component. The component is defined via the keyword GASCCMP (see 12.15.48). This
scaling factor is used for other components.
Extended Langmuir isotherm.

Extended Langmuir isotherm specifies the coal sorption for components via LANGMEXT (see
12.9.4).

For each component two parameters should be specified: Vi Langmuir volume constant, pi
Langmuir pressure constant.
Different isotherms can be used for different CBM regions COALNUM (see 12.4.15).
For each component we calculate:

ps yi ppi
L(p, y1 , y2 , ...)i = (Vi p )
RTs 1 + nc
j=1 y j p j
where:
scaling factor;
ps pressure at standard conditions;
R universal gas constant;
Ts temperature at standard conditions;
Vi Langmuir volume constant for component i (specified via LANGMEXT (see
12.9.4));
pi Langmuir pressure constant for component i (specified via LANGMEXT (see
12.9.4));
yi hydro carbon mole fraction in gas phase for component i;
p pressure.
Time dependent diffusion for compositional models.
The diffusive flow for component i from the coal matrix to fracture is calculated via the
following formula:
Fi = DIFFMF Dc,i Sg RFi (mi c Li )
where:
mi molar density in the matrix coal;
Dc,i diffusion coefficient for component i (DIFFCBM (see 12.9.5));
c coal density (ROCKDEN (see 12.2.96));
RFi readsorption factor for component i (RESORB (see 12.9.6));
Sg gas saturation ;
DIFFMF diffusivity: DIFFMF = 1 Vol ;
Vol block coal volume;
multiplier that can be specified for the whole field (SIGMA (see 12.2.67)) or for
each grid block (SIGMAV (see 12.2.68)).

2.30. Temperature option tNavigator-4.2
2.30 Temperature option

For temperature option tNavigator supports the following keywords:
TEMP (see 12.1.60) indicates that the temperature option is enable, to allow the
modeling of the temperature effects of cold water injection;
TEMPR (see 12.1.61) indicates that the temperature option is enable. This keyword
is different from the keyword TEMP (see 12.1.60) the following way: grid blocks with
zero pore volume are used in simulation (if they are not dis-activated via ACTNUM
(see 12.2.29)). There is no filtration in these blocks, but their heat capacity will be
taken into account in temperature calculations.
SPECROCK (see 12.14.75) specifies the volume specific heat of rock as a function
of temperature;
SPECHEAT (see 12.14.76) specifies the volume specific heat of oil, gas, water as a
function of temperature;
OILVISCT (see 12.14.40) sets the table of oil viscosity as a function of temperature
for each PVT region;
WATVISCT (see 12.14.39) sets the table of water viscosity as a function of temper-
ature for each PVT region;
VISCREF (see 12.14.38) sets reference pressure and reference dissolved gas concen-
tration for each PVT region;
THCONR (see 12.14.15) sets the rock thermal conductivity;
RTEMPA (see 12.15.27) specifies initial reservoir temperature;
RTEMPVD (see 12.15.28) specifies the dependence between initial reservoir temper-
ature and depth;
WTEMP (see 12.18.153) specifies the temperature of injected water;
WTEMPDEF (see 12.15.29) default water temperature for injectors is case if the
keyword WTEMP (see 12.18.153) is not defined;
TRMTEMP (see 12.7.12) the function depending on the factor of absolute permeability
on the temperature (for polymer flooding models 2.20.2);
ROCKCONT (see 12.2.80) specifies the connection between the reservoir and cap and
base rocks, initial temperature, volumetric heat capacity, rock conductivity of reservoir
surroundings and minimal difference between temperatures, which will be used to
model the heat exchange between the reservoir and surroundings.
2.30. Temperature option 113

2.31. Geomechanical model tNavigator-4.2
Water and oil viscosity calculations.
Viscosity dependence on pressure can be specified:
W0 (p)
W (p, T ) = W (T ) 0 (p )
W re f
where
W (T ) water viscosity (at reference pressure), specified via WATVISCT (see

12.14.39) (depends on temperature);

0 (p) water viscosity as a function of pressure (specified using PVTW (see 12.5.5));
W
pre f reference pressure (specified using VISCREF (see 12.14.38)).
Oil viscosity at the prevailing pressure and Rs is calculated the following way:
p (p, Rs )
O = T (T )
p (pre f , Rsre f )
where
T viscosity from the keyword OILVISCT (see 12.14.40) (assumed to be at the

reference pressure and Rs , specified via VISCREF (see 12.14.38));
p viscosity from PVCO (see 12.5.6) (or PVDO (see 12.5.2));
pre f reference pressure, specified via VISCREF (see 12.14.38);
Rsre f reference Rs , specified via VISCREF (see 12.14.38).
2.31 Geomechanical model

2.31.1 Description of Geomechanical model
In tNavigator the following keywords can be used:
GEOMECH (see 12.1.91) this keyword in RUNSPEC section means that will be used
geomechanical model describing the elastic deformation of the rock;
ROCKSTRE (see 12.5.20) sets the diagonal elements of the stress tensor (the regional
stress);
ROCKAXES (see 12.5.19) sets the azimuth and zenith angle of the regional stress;
ROCK (see 12.5.16) - defined by the following elastic properties of rocks:
1. pre f - reference pressure;
2.31. Geomechanical model 114

2. C pp - rock compressibility;
3. CR - compressibility of the rock matrix, CR = KS1 ;
1
4. Cbc = - block compressibility (block that contains mixture), Cbc = K 1 ;
Kbulk
5. porosity value 0 at reference pressure pre f , if CR is not specified or Cbc ;
6. the value of Poisson coefficient 0 at reference pressure pre f , if Cbc is not
specified;
Parameters CR and Cbc (if they are not specified) are calculated the following way:
1. if rock compressibility Cbc is not specified, but CR , 0 , C = C pp are specified,

then:
Cbc = 0C pp + (1 + 0 )CR (2.114)
2. if compressibility of the rock matrix CR is not specified, but 0 , C = C pp are

specified:
Cbc
CR = (2.115)
3(1 0 )0
1+
2(1 20 )(1 0 )
3. if the value of Poisson coefficient is not specified 0 :
Cbc
CR = (2.116)
30
1+
2(1 0 )
4. if C pp is not specified, the default value will be used C pp = 0.00005bars1

5. if 0 is not specified, the default value will be used 0 = 0.33;
The following relation id used for calculating the constant Bio in each block based on
rock properties, specified in the keyword ROCK (see 12.5.16):
Kbulk CR
= 1 = 1 . (2.117)
KS Cbc
Calculation of azimuth angle of hydraulic fracture.
Default values of azimuth and zenith angle (8-th and 9-th parameters of the keyword
WFRACP (see 12.18.124)) and GEOMECH (see 12.1.91) option provide calculation of az-
imuthal angle according to the elastic state of the cells belonging to the fracture and to the
well (example is in the description of the keyword WFRACP (see 12.18.124)), zenith angle
is 0 ;
2.31.1. Description of Geomechanical model 115

2.31.2 Mixture K f
The following relationship for K f estimation is used
1 So Sw Sg
= + + , (2.118)
Kf Ko Kw Kg
SP - phase concentration, P = W, O, G,
KP - the coefficient of uniform phase compression, P = W, O, G.
1 BP
1/KP = CP = , (2.119)
BP p
CP - phase compressibility P = W, O, G;
BP - Formation Volume Factor P = W, O, G.
2.31.3 The calculation of the diagonal elements of the tensor of mechanical stress
Using the dependence = (p, T ) and the calculation results of the hydrodynamic simu-
lation, at each time step we update the values of the diagonal elements of the tensor of
mechanical stress:

n+1 n Kbulk 1 1
ii = ii + p 1 + , i = 1, 2, 3. (2.120)
C pp KS C pp K f
Where f = f (T n+1 , pn+1 ) f (T n , pn ), where f = f (T, p).
2.31.4 Keywords
GEOMECH (see 12.1.91) RUNSPEC Specifies geomechanical model describing the
elastic deformation of the rock
ROCKSTRE (see 12.5.20) PROPS Specifies the diagonal elements of the stress
tensor (the regional stress)
ROCKAXES (see 12.5.19) PROPS Specifies the azimuth and zenith angle of the
regional stress
ROCK (see 12.5.16) PROPS Specifies elastic properties of rocks
2.31.2. Mixture K f 116

3.1. Equations of state tNavigator-4.2
3 Compositional model
3.1 Equations of state
The following equations of state are considered
RT a
p= . (3.1)
v b (v + m1 b)(v + m2 b)
tNavigator supports the following equation types: Redlich-Kwong (RK), Soave-Redlich-

Kwong (SRK), Peng-Robinson (PR). The default values are:
EOS m1 m2 a0 b0
RK, SRK 0 1 0.4274802 0.08664035
PR 1+ 2 1 2 0.457235529 0.077796074
Default values of parameters a0 and b0 can be overrided via the keywords OMEGAA (see
12.13.34) and OMEGAB (see 12.13.34).
The equation (3.1) devided by p is:

1 A
= 1, (3.2)
Z B (Z + m1 B)(Z + m2 B)
where
pa pb pv
A= , B= , Z= .
(RT )2 RT RT
Z is called the supercompressibility factor.
Coefficients a, b and A, B uniform forms of the second and first degree of the molar
concentrations of the components ci :
A = Ai j ci c j , B = Bi ci . (3.3)
i, j i
Forms coefficients are calculated via the following way

pri pri
Ai j = (1 i j )(Ai A j )0.5 , Ai = a (T, i) , Bi = b (T, i) .
Tri2 Tri
where
pri = p/pci , Tri = T /Tci ,
pci and Tci component critical pressure and temperature (PCRIT (see 12.13.19), TCRIT
(see 12.13.17)), i j pair interaction coefficients of components (BIC (see 12.13.32)), a
3. Compositional model 117

3.2. Density tNavigator-4.2
and b depends on the Equation of state:

RK : a (T, i) = a0 Tri0.5 ,
b (T, i) = b0 ,
2
SRK : a (T, i) = a0 1 + (0.48 + 1.574i 0.176i2 )(1 Tri0.5 ) ,
b (T, i) = b0 ,
2
2 0.5
PR : a (T, i) = a0 1 + (0.37464 + 1.54226i 0.26992i )(1 Tri ) ,
b (T, i) = b0 ,
2
PR : a (T, i) = a0 1 + (0.379642 + 1.48503i 0.164423i2 + 0.016666i3 )(1 Tri0.5 ) ,
if i > 0.49.
Where i acentric factor of the component (ACF (see 12.13.30)), Modification of Peng-
Robinson equation PR is used if the keyword PRCORR (see 12.13.40) is specified. Tem-
perature T is fixed and it is specified via the keywords RTEMP (see 12.13.7) or TEMPVD
(see 12.14.68).
3.1.1 EOS in reservoir and surface conditions

Two different sets of data can be used for equations of state for the reservoir and surface
conditions.
The following keywors are used for EOS in surface conditions: ACFS (see 12.13.31),
BICS (see 12.13.33), OMEGAAS (see 12.13.35), OMEGABS (see 12.13.35), MWS (see
12.13.28), PCRITS (see 12.13.20), SSHIFTS (see 12.13.42), TCRITS (see 12.13.18),
VCRITS (see 12.13.22), ZCRITS (see 12.13.25).
The following keywors are used for EOS in reservoir conditions: ACF (see 12.13.30), BIC
(see 12.13.32), OMEGAA (see 12.13.34), OMEGAB (see 12.13.34), MW (see 12.13.27),
MWW (see 12.13.29), PCRIT (see 12.13.19), SSHIFT (see 12.13.41), TCRIT (see 12.13.17),
VCRIT (see 12.13.21), ZCRIT (see 12.13.24).
If any (or all) keywords for surface EOS are not specified then these parameters are taken
from reservoir condition keywords by defaul.
A different EOS to use in surface conditions can be specified using the keyword EOSS
(see 12.13.6).
3.2 Density
For equation of state phase molar density is defined by formula
p
P = . (3.4)
ZRT
3.1.1. EOS in reservoir and surface conditions 118

3.3. Viscosity tNavigator-4.2
Three parameter equation of state with shifts

!
n
ZRT
P = 1/ zi bi si , (3.5)
p i=1
where P phase,
zi component in oil phase xi or in gas phase yi
si shift parameter of the component i, specified via the keyword SSHIFT (see 12.13.41)
bi = b RT ci
pci
Phase mass density is calculated by the formula
P = P MwP , (3.6)
where MwP average molecular weight of phase P,

N
MwP = Mwi ci , (3.7)
i=1
Mwi molecular weight of component i.
3.3 Viscosity
For default the method Lohrenz-Bray-Clark Correlation is used (see section 3.3.1).
PEDERSEN (see 12.13.52) keyword specifies that viscosities will be calculated via Peder-
sons method (see section Pedersen Correlation).
3.3.1 Lohrenz-Bray-Clark Correlation

In viscosity calculation of P the correlation Lohrenz-Bray-Clark is used
1/4
(P P ) + 104 2
= a1 + a2 rP + a3 rP 3
+ a4 rP 4
+ a5 rP . (3.8)
Where:
rP = P /c .
a1 = 0.1023000, a2 = 0.0233640, a3 = 0.0585330, a4 = 0.0407580, a5 = 0.0093324.

These coefficients can be overrided via the keyword LBCCOEF (see 12.13.36). One
should use the keyword LBCCOEFR (see 12.13.37) to set different coefficients for
each equation of state region.
- function of molecular weights, critical temperature and critical pressure.
3.3. Viscosity 119

3.3. Viscosity tNavigator-4.2
Critical moler density c is calculated via the following formula

!1
N
c = ciVci , (3.9)
i=1
where Vci critical molar volume of the component i, specified by user (keywords VCRIT
(see 12.13.21), VCRITVIS (see 12.13.23)) or calculated from critical Z-factors (keyword
ZCRIT (see 12.13.24), ZCRITVIS (see 12.13.26)).
3.3.2 Pedersen Correlation

Detailed description of Pedersen correlation is in [23]. It sets via the keyword PEDERSEN
(see 12.13.52).
User parameters for Pedersen correlation can be set via the keywords PEDTUNE (see
12.13.53), PEDTUNER (see 12.13.54).
3.3.2. Pedersen Correlation 120

4.1. Basic volumes tNavigator-4.2
4 Compositional thermal model with chemical reactions

Lets consider a compositional thermal model with chemical reactions which is used in
tNavigator. There are three (four) phases and three (four) or more components:
water phase (water) doesnt mix with hydrocarbon phases, consists of one component
water;
liquid hydrocarbon phase (oil) consists of a mixture of hydrocarbon components,

at certain pressure, temperature and with a certain concentration of components in the
liquid phase;
gas hydrocarbon phase (gas) consists of a mixture of hydrocarbon components,

oxygen-component, water-component, at certain pressure, temperature and with a
certain concentration of components in the gas phase.
solid phase (coke) consists of one component coke.
The following phase changes are supported:
water gas vaporization

gas water condensation
gas oil solution
oil gas oil evaporation
oil coke carbonization
oil, gas gas, water burning
coke, gas gas, water burning
The solid phase is specified using the keyword SOLID (see 12.1.57) in e300 data format;
MODEL (see 13.5.4) in stars data format. Component volatility type is specified using
CVTYPE (see 12.14.1) in e300; MODEL (see 13.5.4).
4.1 Basic volumes

The unit grid block volume Vb is
Vb = VR +Vp , Vp = VS +V f , V f = VW +VO +VG
where
VR rock volume (is used in the description of thermal properties),
Vp pore volume, V f "mobile" volume,
VS solid phase volume (solid phase),
VP , P = W, O, G water, oil, gas phase volume.
4. Compositional thermal model with chemical reactions 121

4.3. Phases tNavigator-4.2
Porosity the volume which can be filled with a mixture:

Vp VS +V f VS +V f
= = =
Vb Vb VR +VS +V f
"Mobile" porosity f the volume, which can be filled with a mobile mixture:
V f +VS VS

Vf VS VS VS
f = = = = 1 = 1
Vb Vb Vb V f +VS Vp
4.2 Saturations
The saturation SP of liquid phase (P = W, O, G) a part of volume of porous medium
(which can be filled with liquid phases), which is filled with this phase:
VP VP
SP = = , P = W, O, G, SW + SO + Sg = 1 (4.1)
Vf VW +VO +VG
The saturation SbS of solid phase is

VS
SbS =
Vp
so
f = 1 SbS (4.2)
and modified saturations SbP of liquid phases (P = W, O, G)

SbP = 1 SbS SP , P = W, O, G
so
SbW + SbO + SbG + SbS = 1
4.3 Phases
Each phase P, P = W, O, G, S (Water, Oil, Gas, Solid) has the following parameters (un-
known, these parameters are calculated during the run):
T = T (t, x, y, z) phase temperature (all phases are in the thermodynamic equilibrium,

therefore all phases have the same temperature at one place);
pP = pP (t, x, y, z) pressure of phase P;
SP = SP (t, x, y, z) (P = W, O, G), SbS = SbS (t, x, y, z) saturation of phase P.
4.2. Saturations 122

4.4. Components tNavigator-4.2
The following equations are used to reduce the number of unknowns:

pO pG = PcOG ,
pO pW = PcOW ,
SW + SO + SG = 1.
where PcOG = PcOG (Sg ) capillary pressure in the system oil-gas, PcOW = PcOW (Sw )
capillary pressure in the system water-oil (known functions).
From here "pressure" is "pressure of oil phase" p = pO . PcP = PcOP , where PcOO = 0,
PcOS = 0 and pP = p + PcP .
4.4 Components
All phases P, P = W, O, G, S = 1, . . . , nP can be divided into two groups: "mobile" phases
(water, oil, gas) P = W, O, G = 1, . . . , n0P , n0P = nP 1 and solid phase P = S = nP . All
components c, c = 1, . . . , nc can be divided into two groups:
c = 1, . . . , n0c the components which can be only in "mobile" phases;
c = n0c + 1, . . . , nc the components which can be only in the solid phase.
Let:
Nc = Nc (t, x, y, z) molar density of the component c, c = 1, . . . , n0c in the "mobile"
volume (mol/m3 ), then Nc V f = Nc f Vb the quantity of the component c in the
volume Vb (mol );
Nc = Nc (t, x, y, z) molar density of the component c, c = n0c + 1, . . . , nc in the pore
volume (mol/m3 ), then Nc Vp = Nc Vb the quantity of the component c in the
volume Vb (mol ).
Component distribution in different phases is set via nc nP concentration matrix
xc,P = xc,P (pP , N), N = (N1 , . . . , Nnc ):
n0P
xc,PPSP = Nc, c {1, . . . , n0c }, xc,S S SbS = Nc , c {n0c + 1, . . . , nc }.
P=1
where P = P (pP , N) the molar density of the phase P.

The number of hydrocarbon components is specified using the keyword COMPS (see
12.13.3) in e300 data format.
Total number of components and the number of components in water, oil and gas phases are
set using the keyword MODEL (see 13.5.4) in stars data format.
Since
nc
xc,P = 1, P {1, . . . , nP }, xc,S = 0, c {1, . . . , n0c }, (4.3)
c=1
xc,P = 0, c {n0c + 1, . . . , nc }, P {1, . . . , n0P }, xc,W = 0, c {2, . . . , nc },
4.4. Components 123

4.5. Mass and molar water density tNavigator-4.2
hence (SS = SbS ):

nP
xc,PPSP = Nc, c {1, . . . , nc },
P=1
and
nc
Nc
c=n0c +1 Nc
SbS = , xc,S = nc c {n0c + 1, . . . , nc }. (4.4)
S
Nk
k=n0c +1
If the keyword CVTYPE (see 12.14.1) (MODEL (see 13.5.4)) specifies that c-component
cant be in the phase P, then the properties of the component c for the phase P may not be
entered.
4.5 Mass and molar water density

In e300 data format the mass density and the molar water density on default (or if the
keyword THANALB (see 12.14.3) is present) are calculated
A0 + A1 T + A2 T 2 + A3 T 3 + A4 T 4 + A5 T 5 cw,p (pA7 ) 1
W = e , W = W , (4.5)
1 + A6 T MWW
where
A0 = 9998.3952 A1 = 169.55176
A2 = 7.987 102 A3 = 46.170461 105
A4 = 105.56302 108 A5 = 280.54353 1011
A6 = 16.87985 102 A7 = 102
If the keyword WATDENT (see 12.14.2) is enable, then
w,re f 1
W = , W = W
(1 cw,p (p pw,re f ))(1 + cw,1,T (T Tw,re f ) + cw,2,T (T Tw,re f )2 ) MWW
(4.6)
where
w,re f = W,SC /BW (pre f ) (kg/m3 )
W,SC is set via DENSITY (see 12.5.23)
cw,p , pw,re f , BW (pre f ), is set via PVTW (see 12.5.5)
cw,1,T , cw,2,T , Tw,re f , is set via WATDENT (see 12.14.2)
MWW water molar weight
4.5. Mass and molar water density 124

4.5. Mass and molar water density tNavigator-4.2
In stars data format the mass density and the molar water density are calculated
!
T 2 Tre2 f
W = w,re f exp cw,p (p pre f ) cw,1,T (T Tre f ) cw,2,T + cw,pT (p pre f )(T Tre f )
2
W = W MWW
(4.7)
where
pre f reference pressure PRSR (see 13.5.10)
Tre f reference temperature TEMR (see 13.5.11)
w,re f component density w from MOLDEN (see 13.5.14) (mol/m3 )
ck,p , ck,1,T , ck,2,T , ck,pT the properties of component w specified via CP (see
13.5.16), CT1 (see 13.5.17), CT2 (see 13.5.18), CPT (see 13.5.19).
If for the component w CP (see 13.5.16) = 0,CT1 (see 13.5.17) = 0,CT2 (see 13.5.18) =
0,CPT (see 13.5.19) = 0 and MOLDEN (see 13.5.14) = 0 or MOLVOL (see 13.5.3) = 0,
then the default formula is used:
if T < Tw,crit
W = c (1 + ) exp (cw,p (p pbub )) ,
(4.8)
W = W MWW ,
if T Tw,crit
W = c exp cw,p (p psat ) cw,1,T (T Tw,crit ) cw,2,T (T 2 Tw,crit

2

) ,
(4.9)
W = W MWW ,
where
c = 17.88888kgmol/m3 - critical density,

1 2 5 16 43 110
= 1.99206 3 +1.10123 3 0.512506 3 +1.75263 3 45.4485 3 675615 3 ,
T
= 1 Tw,crit ,
cw,p = 4.57 105 1.076823 108 (pre f 1.01325)1/bar ,
cw,1,T = 1.9095 103 1/K ,
cw,2,T = 7.296 106 1/K 2 .
4.5. Mass and molar water density 125

4.6. Mass and molar liquid density tNavigator-4.2
4.6 Mass and molar liquid density

The molar density and mass liquid density are calculated as

n0c MWk n0c 1
O = 1 k=2 xk,O O = 1 k=2 xk,O (in e300)
k,O k,O
(4.10)
n0c 1 n0c MWk
O = 1 k=2 xk,O O = 1 k=2 xk,O (in stars)
k,O k,O
In stars data format component liquid density k,O (p, T ) (mol/m3 ) is calculated as
T 2 Tre2 f
k,O = k,re f exp ck,p (p pre f ) ck,1,T (T Tre f ) ck,2,T + ck,pT (p pre f )(T Tre f )
2
(4.11)
where
1. pre f reference pressure (PRSR (see 13.5.10))
2. Tre f reference temperature (TEMR (see 13.5.11))
3. k,re f density of component k at reference pressure and reference temperature
(MOLDEN (see 13.5.14))
4. ck,p , ck,1,T , ck,2,T , ck,pT properties of component k in the liquid phase:
ck,p (CP) component k compressibility k ,
ck,1,T (CT1) the first thermal expansion coefficient for component k (for this
parameter tNavigator uses this keyword THERMEX1 (see 12.14.26)),
ck,2,T (CT2) the second thermal expansion coefficient for component k (for this
parameter tNavigator uses the keyword THERMEX2 (see 12.14.27)); total thermal
expansion coefficient is equal to ck,1,T + T ck,2,T ,
ck,pT (CPT) the coefficient of density dependence on temperature and pressure
(for this parameter tNavigator uses the keyword THERMEX3 (see 12.14.28))
In e300 data format component liquid density k,O (p, T ) (kg/m3 ) is calculated as
.
k,O = k,re f (1 ck,p (p pk,re f ))(1 + ck,T (T Tk,re f )) (4.12)
where
1. pk,re f reference pressure for component k (PREF (see 12.14.29))
2. Tk,re f reference temperature for component k (TREF (see 12.14.32))
3. k,re f density of component k at reference pressure and reference temperature (DREF
(see 12.14.34))
4. ck,p component k compressibility (CREF (see 12.14.31)),
5. ck,T thermal expansion coefficient for component k (THERMEX1 (see 12.14.26))
4.6. Mass and molar liquid density 126

4.7. Molar and mass gas density tNavigator-4.2
4.7 Molar and mass gas density

In e300 data format the molar and the gas mass density are calculated as
n0c
, !
MWw Zk,0 RT
G = 1 xw,G + xk,G Zk,1
w k=2 p
,
n0c ! (4.13)
xw,G xk,G Zk,0 RT
G = 1 + Zk,1
w k=2 MWk p
The component water density (water vapor) w (p, T ) in the gas phase
!
5
j Tb
w = exp C j TbK (4.14)
j=0 T
where Tb the boiling temperature C , TbK = Tb + 273.15 the boiling temperature K ,
Tb = a (p/10)b , a = 180.89 b = 0.2350
C0 = 93.7072 C1 = 0.833941 C2 = 0.003208
C3 = 6.57652 106 C4 = 6.93747 109 C5 = 2.97203 1012
The coefficients Zk,0 , Zk,1 are specified using the keywords ZFACTOR (see 12.14.36),
ZFACT1 (see 12.14.37).
Zk,0 default value is 0.96.
m3 bar J Pa
Gas constant R in (4.13) is equal to 0.083143 = 8.3143 , i.e. R =
K kg mol K mol
0.083143 for the unit of pressure bar , and the unit amount of fluid kg mol .
In stars data format the molar and the gas mass density are calculated
n0c
p
G = , G = G xk,G MWk (4.15)
ZRT k=1
where Z the root of the equation of state Redlich-Kwong with zero coefficients of pair-wise
interaction. Lets specify i = 1, . . . , n0c
pri pri T p
Ai = 0.4274802 , Bi = 0.08664035 , A jk = (A j Ak )0.5 , pri = ,, Tri =
Tri2.5 Tri pci
Tci
(4.16)
where the critical temperature Tci is set using TCRIT (see 13.5.21), the critical pressure pci
is set using PCRIT (see 13.5.20). Then
n0c n0c n0c
A= x j,Gxk,GA jk , B= x j,GB j (4.17)
j=1 k=1 j=1
Z the maximal root (> 0) of the equation

Z 3 Z 2 + (A B2 B)Z AB = 0 (4.18)
Z is calculated in every grid block at every time step of Newton iteration. Usually
Z [0.3, 1.2].
4.7. Molar and mass gas density 127

4.8. Molar solid density tNavigator-4.2
4.8 Molar solid density

Molar solid density (coke) is calculated as
, !
nc
1
S = 1 0 xk,S k (4.19)
k=n +1
c
In e300 data format component solid density k (p, T ) (kg mol/m3 ) is calculated as

k = k,re f MWk (1 ck,p (p pk,re f ))(1 + ck,T (T Tk,re f ))
where
1. MWk component k molecular weight specified via MW (see 12.13.27) (CMM (see
13.5.59))
2. pk,re f reference pressure for component k (SPREF (see 12.14.23))
3. Tk,re f reference temperature for component k (STREF (see 12.14.25))
(SDREF (see 12.14.22))
5. ck,p component k compressibility (SCREF (see 12.14.24))
6. ck,T thermal expansion coefficient for component k (is specified using the keyword
STHERMX1 (see 12.14.20))
In stars data format component solid density k (p, T ) (kg mol/m3 ) is calculated as
k,re f
k = exp ck,p (p pre f ) ck,T (T Tre f ) + ck,pT (p pre f )(T Tre f )
MWk
where
(SOLID_DEN (see 13.5.22))
4. ck,p , ck,T , ck,pT properties of component k in the solid phase (SOLID_DEN (see
13.5.22)):
ck,p component k compressibility,
ck,T thermal expansion coefficient for component k (for this parameter tNavi-
gator uses the keyword STHERMX1 (see 12.14.20)),
ck,pT the coefficient of density dependence on temperature and pressure (for
this parameter tNavigator uses the keyword STHERMX2 (see 12.14.21))
Mass solid density isnt used in the calculations.
4.8. Molar solid density 128

4.9. Thermodynamic equilibrium condition tNavigator-4.2
4.9 Thermodynamic equilibrium condition

MP - the number of moles in the "mobile" phase P, P = W, O, G, in the unit volume.
Obviously
n0P n0c
MP = Ntot = Nc.
P=1 c=1
MP
Let RP = the part of "mobile" component mixture in the phase P, concerning the
Ntot
total amount of the mixture. Then
n0P
MP = RP Ntot , RP = 1. (4.20)
P=1
Let Mc,P = xc,P MP the number of moles of the component c, c = 1, . . . , n0c , in the phase
P, P = W, O, G, in the unit volume. Then
n0P n0P
Nc = MP xc,P, = Ntot RP xc,P, c = 1, . . . , n0c .
P=1 P=1
Since water component isnt present in the oil phase and hydrocarbon components are not
present in the water phase, then
n0c
x1,O xw,O = 0, xc,W = 0, c {2, . . . , n0c }, xw,W = 1 (from xc,P = 1 for P = W )
c=1
Let zc = Nc /Ntot , c = 1, . . . , n0c , then

zw = RW xw,W + RG xw,G , zc = RO xc,O + RG xc,G , c {2, . . . , n0c }, (4.21)
User specifies the functions Kc = Kc (p, T ), c {1, . . . , n0c }:
xw,G = Kw (p, T )xw,W , xc,G = Kc (p, T )xc,O , c {2, . . . , n0c }
From the equations (4.21) we obtain for each c {2, . . . , n0c }:
1 Kc
xw,G = Kw , xc,O = zc , xc,G = zc ,
RO + Kc RG RO + Kc RG
From the equilibrium conditions:
n0P n0c
RP = 1, xc,P = 1
P=1 c=1
we obtain
RW = zw RG Kw RO = (1 zw ) RG (1 Kw ) xw,G = Kw , (4.22)
1 Kc
xc,O = zc , xc,G = zc , (4.23)
(1 zw ) + RG (Kc + Kw 1) (1 zw ) + RG (Kc + Kw 1)
4.9. Thermodynamic equilibrium condition 129

4.10. Phase saturations tNavigator-4.2
and RG [0, 1] is the solution of the equation

n0c
zc (Kc + Kw 1)
F(RG ) = 0, F(RG ) = (1 zw) + RG(Kc + Kw 1)
c=2
The values Ki = Ki (p, T ) can be specified via the tables KVTEMP (see 12.14.6),
KVTABTn (see 12.14.7), KVTABLIM (see 12.14.8) in e300 (KVTABLIM (see 13.5.24),
KVTABLE (see 12.13.16) in stars), or via the correlation formula:
Ki (p, T ) = (Ai + Bi /p +Ci p) eDi /(T Ei ) (4.24)
where the coefficients Ai , Bi , Ci , Di , Ei are set using the keywords KVCR (see 12.14.4) in
e300 (KV1 / KV2 / KV3 / KV4 / KV5 (see 13.5.26) in stars).
In stars data format this formula is also used for water if the not zero coefficients Ai ,
Bi , Ci , Di , Ei are specified. In another case the correlation is used:
b
1 TF
Kw (p psi , TF ) = , a = 115.1, b = 4.44444. (4.25)
p psi a
In e300 data format the following correlation is used
10 TC 1/b

Kw (p, T ) = , a = 180.89, b = 0.2350, TC (C) = T ( K) 273.15 (4.26)
p a
It is very difficult to choose many parameters in (4.24) (Ki (p, T ) should be positive and in-
creasing in conjunction with T ). In e300 data format the correlation (Wilson) for hydrocarbon
components can be used KVWI (see 12.14.9):
pci 5.372697(1+Ai )(1Tci /T )
Ki (p, T ) = e (4.27)
p
where
Tci component critical temperature TCRIT (see 12.13.17);
pci component critical pressure PCRIT (see 12.13.19);
Ai component acentric factor ACF (see 12.13.30).
4.10 Phase saturations

Since (4.20) the number of moles of the "mobile" phases in the volume V f is MP V f , and
their volume is equal to MP V f /P . From the equation (4.1) we obtain SP = VP /V f = MP /P
or
Ntot RP
SP = , P = 1, . . . , n0P (4.28)
P
The description of calculations of the solid phase saturation is in the section (4.4).
4.10. Phase saturations 130

4.12. Oil viscosity tNavigator-4.2
4.11 Water viscosity

Water viscosity can be specified as a function of temperature using the tables WATVISCT
(see 12.14.39) (e300 data format), VISCTABLE (see 13.5.53) (stars data format), or via
correlations. In e300 the following correlation is used (Grabovski):
W (T ) = 1 AW + BW TC +CW TC2 , AW = 0.1323, BW = 0.03333, CW = 7.643 106

(4.29)

where TC the temperature C . In stars the following correlation is used:

W (T ) = AW exp BW /T (4.30)
where T the temperature K , the coefficients AW , BW are set via the keywords AVISC
(see 13.5.51), BVISC (see 13.5.52).
Multiple viscosity regions can be specified via VSTYPE (see 13.5.45), VISCTYPE (see
13.5.46) (stars). tNavigator also uses the keyword (VISCNUM (see 12.4.20)).
In e300 data format the viscosity dependence on pressure can be specified:
W0 (p)
W (p, T ) = W (T ) 0 (p ) (4.31)
W re f
where
W (T ) water viscosity (depends on temperature) is calculated above;

W
4.12 Oil viscosity

Oil viscosity is calculated using the formula
n0c
O (T ) = (k,O ) fk (xk,O ) (4.32)
k=2
where oil component viscosity k,O (T ) can be specified as a function of temperature using
the tables of this keyword OILVISCT (see 12.14.40) (in e300 data format), VISCTABLE (see
13.5.53) (stars), or using correlation (OILVISCC (see 12.14.41)).
fk (x) (default: fk (x) = x ) are specified using OILVINDX (see 12.14.42) (in e300 data format)
or VSMIXCOMP (see 13.5.54), VSMIXENDP (see 13.5.55), VSMIXFUNC (see 13.5.56)
(stars). tNavigator also uses the keyword OILVINDT (see 12.14.43).
In e300 data format the following correlations can be used to calculate k,O (specified
using this keyword OILVISCC):
4.11. Water viscosity 131

4.13. Gas viscosity tNavigator-4.2
Name Formula Name Formula

ASTM log10 (k,O + Ak ) = Bk T Ck Vogel log10 (k,O ) = Ak + Bk /(T +Ck )
Andrade log10 (k,O ) = Ak + Bk /T logarithmic log10 (k,O ) = Ak + Bk log10 (T )
In stars data format Andrade correlation is used with parameters Ak = log10 A0k , Bk =
B0k log10 e, where A0k , B0k are specified using keywords AVISC (see 13.5.51), BVISC (see
13.5.52).
In e300 data format pressure dependence can be set:
O0 (p)
O (p, T ) = O (T ) (4.33)
O0 (pre f )
where
O (T ) oil viscosity (depends on temperature);
O0 (p) oil viscosity as a function of pressure (specified using PVCO (see 12.5.6));
4.13 Gas viscosity

In e300 data format gas viscosity is calculated
n0c
G (p, T ) = xk,G k,G (4.34)
k=1
component water viscosity (water vapor) 1,G (p, T ) in the gas phase
1,G (p, T ) = Ag + Bg TC +Cg (p/10)Dg , TC = T 273.15

Ag = 4.9402 103 , Bg = 5.0956 105 , Cg = 2.9223 106 , Dg = 2.5077
hydrocarbon component viscosity k,G (T ) in the gas phase can be specified as a function
of temperature using the tables of this keyword GASVISCT (see 12.14.44), or using the
correlation formula with the coefficients GASVISCF (see 12.14.45):
k,G (T ) = Ak T Bk (4.35)
In stars data format gas viscosity is calculated as

n0c n0c
!, !
p p
G (T ) = k,G xk,G MWk xk,G MWk (4.36)
k=1 k=1
4.13. Gas viscosity 132

4.15. Enthalpy and internal energy of the phases tNavigator-4.2
where MWk molecular weight of the component k (specified using CMM (see 13.5.59)),
component viscosities are set via correlation (4.35) with the coefficients AVG (see 13.5.57),
BVG (see 13.5.58). If gas viscosity isnt specified by user then in stars data format it is
calculated as
G (T ) = 0.0136 + 3.8 105 TC , TC = T 273.15
4.14 Enthalpy and heat capacity of the components

Thermodynamic properties of the component c = 1, . . . , nc in the phases P = W, O, G, S :
Hc,P (T ) enthalpy of the component c in the phase P;
CPc,P = dHc,P (T )/dT heat capacity of the component c in the phase P;
HVc vaporization enthalpy of the component c (from liquid phase to the gas phase).
The following equations take place:
HVc = Hc,G (Hc,W + Hc,O ) (4.37)
so only 2 (of 3) sets of data should be specified Hc,O (or Hc,W ), Hc,G , HVc . For each
component only one parameter of Hc,O or Hc,W isnt zero, because there are no components
which can be in the water and the oil phase at the same time.
Component enthalpy is specified via the heat capacity.
In e300 data format: CPc,P (kJ/kg/C ). In stars data format: CPc,P (J/mol/C ).
4.15 Enthalpy and internal energy of the phases

Enthalpy of the phase HP (T ) (for one mole, kJ/mol ):
nc nc
HP (p, T ) = xc,P (p, T )Hc,P MWc (in e300) or HP (p, T ) = xc,P (p, T )Hc,P (in stars)
c=1 c=1
(4.38)
where MWc molecular weight given by the keyword MW (see 12.13.27) (kg/mol ). In
e300 data format the gas phase component enthalpies include both a temperature dependent
term and a pressure dependent term (Joule-Thomson) (see (4.48), (4.49)).
The internal energy of the phases (for unit volume, kJ/m3 ) for "mobile" phases:
UP (p, T ) = P (p, T )(HP (T ) pPp /P ) = P (p, T ) HP (T ) pPp
where pPp the partial pressure of the phase P, P = W, O, G. Then the internal energy
(for unit volume, kJ/m3 ) of the pore volume:
n0P
U f (p, T ) = P(p, T ) HP(T ) p (4.39)
P=1
4.14. Enthalpy and heat capacity of the components 133

4.17. Liquid enthalpy tNavigator-4.2
The internal energy (for unit volume, kJ/m3 ) of the volume which is filled with the solid
phase:
US (p, T ) = S (p, T ) HS (T ) (4.40)
4.16 Water enthalpy

In e300 data format the enthalpy, the water vaporization enthalpy are taken from the
internal tables (see [19]). These enthalpies are the functions of pressure and temperature. In
stars data format the enthalpy, the water vaporization enthalpy are also taken from the
internal tables.
In [20] there is a following formula for water enthalpy:
h f = hc 1 + (1 Tr ) A + BTr +CTr2 + DTr3 + ETr4 + F(1 Tr ) ,

(4.41)
T
where Tr = and
TC
= 0.2968, hc = 2086kJ/kg, TC = 647.126K,

A = 1.365233, B = 1.502294, C = 3.941123,
D = 4.647609, E = 2.312461, F = 0.3898396.
4.17 Liquid enthalpy

In e300 data format the component liquid enthalpy is calculated as
1
Hc,O (T ) = CP1,c (T Tre f ) + CP2,c (T Tre f )2 (4.42)
2
where the coefficients CP1,c (kJ/kg/C ), CP2,c are specified using the keywords SPECHA
(see 12.14.57), SPECHB (see 12.14.58) (default: 0), Tre f is specified using STCOND (see
12.13.8).
In stars data format the component liquid enthalpy is calculated as
4
1
Hc,O (T ) = CPi,c (T Tre f )i (4.43)
i=1 i
where the coefficients CPi,c , i = 1, . . . , 4 are specified using the keywords CPL1 / CPL2 /
CPL3 / CPL4 (see 13.5.27).
tNavigator also uses the keywords CP3,c = SPECHC (see 12.14.59), CP4,c = SPECHD
(see 12.14.60).
Default values: CP1,c = 0.5Btu/lbmol/F = 0.51.05506/0.4535921.8kJ/mol/C = 2.0934kJ/mol/C ,
the other coefficients: 0, Tre f is specified using TEMR (see 13.5.11).
Then the liquid phase enthalpy is calculated according to (4.38).
4.16. Water enthalpy 134

4.19. Gas phase enthalpy tNavigator-4.2
4.18 Vaporization enthalpy

The enthalpy of a gaseous oil component is calculated as
HVc (T ) = Ac (1 T /Tc,crit )Bc = A0c (Tc,crit T )Bc , A0c = Ac /Tc,crit

Bc
(4.44)
where:
In e300 data format Ac is specified using the keyword HEATVAP (see 12.14.13) (default: 0
kJ/kg).
In stars data format A0c is specified using the keyword HVR (see 13.5.30) (default:
0.25Btu/lbmol/F = 0.25 1.05506/0.453592 1.8kJ/mol/C = 1.0467kJ/mol/C ).
Bc (default: 0.38) is specified using the keyword HEATVAPE (see 12.14.14) (e300), EV
(see 13.5.31) (stars).
Critical temperature of the component Tc,crit is specified using the keyword TCRIT (see
12.13.17) (e300), TCRIT (see 13.5.21) (stars).
If T Tc,crit then HVc (T ) = 0.
If the component enthalpy in the liquid phase and vaporization enthalpy is specified then
the gas phase enthalpy is calculated from the equation (4.37).
If the component enthalpy in the gas phase and vaporization enthalpy is specified then
the oil phase enthalpy is calculated from the equation (4.37).
4.19 Gas phase enthalpy

In e300 data format water enthalpy in the gas phase is calculated as

H1,G (T ) = hc + RTc (1 Tr )(A + BTr ) +C(1 Tr ) + D(1 Tr )2 , (4.45)
T
where Tr = and
Tc
= 0.2866, = 3.140, Tc = 647.126K,
R = 0.461522kJ/kgK, hc = 2086kJ/kg, A = 7.818955,
B = 3.977657, C = 2.665298, D = 4.754665,
If c > 2 (enthalpy of hydrocarbon components)
1
Hc,G (T ) = hc,G +CP1,c (T Tre f ) + CP2,c (T Tre f )2 , (4.46)
2
where the coefficients hc,G (kJ/kg), CP1,c (kJ/kg/C ), CP2,c (kJ/kg/C/C ), are specified
using the keywords HEATVAPS (see 12.14.65), SPECHG (see 12.14.61), SPECHH (see
12.14.62) (default: 0), Tre f is specified using STCOND (see 12.13.8).
In stars data format the component gas phase enthalpy is calculated as
4
1
Hc,G (T ) = hc,G + CPi,c (T Tre f )i (4.47)
i=1 i
4.18. Vaporization enthalpy 135

4.21. Rock enthalpy tNavigator-4.2
where the coefficients hc,G , CPi,c , i = 1, . . . , 4 are specified using the keywords HVAPR (see
13.5.29), CPG1 / CPG2 / CPG3 / CPG4 (see 13.5.28).
tNavigator also uses the keywords CP3,c = SPECHI (see 12.14.63), CP4,c = SPECHJ
(see 12.14.64). Default values: hc,G = 0.25Btu/lb/F = 0.251.05506/0.4535921.8kJ/kg/C =
1.0467kJ/kg/C , CP1,c = 0.25Btu/lb/F = 1.0467kJ/kg/C , the other coefficients: 0, Tre f is
specified using TEMR (see 13.5.11).
Then the gas phase enthalpy is calculated according to (4.38).

If the vaporization enthalpy isnt specified, then during e300 data format instead of (4.38)
is used:
nc
HG (p, T ) = xc,G (p, T ) Hc,G (T ) MWc + HJT,c (p) (4.48)
c=1
where (Joule-Thomson)
HJT,c (p) = 102 Zc,1 (p pre f ) (4.49)
The coefficient Zk,1 is set via ZFACT1 (see 12.14.37), pre f STCOND (see 12.13.8).
Multiplier 102 (4.49) results from units transformation: Zk,1 m3 /kg mol , so Zc,1 (p
pre f ) m3 /kg mol bar = 105 m3 Pa/kg mol = 102 kJ/kg mol .
4.20 Solid phase enthalpy

The component solid phase enthalpy (for one mole, kJ/kg mol ) is calculated as

1 2
Hc,S (T ) = CP1,c (T Tre f ) + CP2,c (T Tre f ) MWc (E300) or
2 (4.50)
1 2
Hc,S (T ) = CP1,c (T Tre f ) + CP2,c (T Tre f ) (stars)
2
where
in e300 data format the coefficients CP1,c (kJ/kg/C ), CP2,c are specified using the
keywords SPECHS (see 12.14.66), SPECHT (see 12.14.67) (default: 0), Tre f is
specified using the keyword STCOND (see 12.13.8).
in stars data format the coefficients CP1,c , CP2,c are specified using the keywords
SOLID_CP (see 13.5.23) (default: CP1,c = 17kJ/mol/C , CP2,c = 0), Tre f is specified
using the keyword TEMR (see 13.5.11).
Then the solid phase enthalpy is calculated according to (4.38).
4.21 Rock enthalpy

Rock enthalpy (for unit volume, kJ/m3 ) is calculated as
1
HR (T ) = (CP1 (T Tre f ) + CP2 (T Tre f )2 ) (4.51)
2
where
4.20. Solid phase enthalpy 136

4.23. Block internal energy tNavigator-4.2
in e300 data format the coefficients CP1 (kJ/m3 /C ), CP2 are set via HEATCR (see
12.14.10), HEATCRT (see 12.14.11) (default: 0), Tre f is specified using STCOND (see
12.13.8).
in stars data format the coefficients CP1 , CP2 are set via ROCKCP (see 13.4.3),
(default CP1 = 2347kJ/m3 , CP2 = 0), Tre f is specified using TEMR (see 13.5.11).
In tNavigator the coefficients CP1 , CP2 can be specified via the keyword HEATTCR
(see 12.14.12).
Internal rock energy (for unit volume, kJ/m3 ):
UR (T ) = HR (T ) (4.52)
4.22 Default enthalpy values for stars format models

For stars format models there are 3 types of enthalpy specification:
1) Oil enthalpy (CPL1 / CPL2 / CPL3 / CPL4 (see 13.5.27)) and vaporization enthalpy
(HVR (see 13.5.30), EV (see 13.5.31)) are entered.
2) Gas enthalpy (CPG1 / CPG2 / CPG3 / CPG4 (see 13.5.28)) and vaporization
enthalpy (HVR (see 13.5.30), EV (see 13.5.31)) are entered.
3) Oil enthalpy (CPL1 / CPL2 / CPL3 / CPL4 (see 13.5.27)), gas enthalpy (CPG1 /
CPG2 / CPG3 / CPG4 (see 13.5.28)) and the value of vaporization enthalpy at the
point Tre f (HVAPR (see 13.5.29)) are entered.
If in the model only the vaporization enthalpy is entered, then the type 1 is used with the
coefficient CPL1 (see 13.5.27) = 0.5 Btu/lb-F = 2.0934 kJ/kg-C.
If in the model only the gas enthalpy is entered, then the type 2 is used with zero
vaporization enthalpy (i.e. oil enthalpy is equal to gas enthalpy).
If in the model only the oil enthalpy is entered, then the type 1 is used with zero
vaporization enthalpy (i.e. oil enthalpy is equal to gas enthalpy).
If in the model no one of the properties above are entered, then the type 1 is used with the
coefficient CPL1 (see 13.5.27) = 0.5 Btu/lb-F = 2.0934 kJ/kg-C and vaporization enthalpy,
specified via the formula Hvap = A(Tcrit T )0.38 . If Tre f Tcrit , then the coefficient A is
calculated from: Hvap (Tre f ) = C (Tcrit Tre f ), where C = 0.6579 Btu/lb-F = 2,7538 kJ/kg-C,
else A = 0.
4.23 Block internal energy

Block internal energy (kJ ) is calculated: the internal energies of the "mobile" phases (4.39),
solid phase (4.40) and rock (4.52), (in the unit volume) are multiplied by the volume (see
4.22. Default enthalpy values for stars format models 137

4.24. Porosity tNavigator-4.2
121 and (4.2)):
Ub (p, T ) = U f (p, T ) V f +US (p, T ) VS +UR (T ) VR

n0P
!

= Vb 1 SbS P(p, T ) HP(T ) p
P=1
+Vb SbS S (p, T ) HS (T ) +Vb (1 ) HR (T ) (4.53)
4.24 Porosity
In e300 data format the porosity = (p, x, y, z) is
(p, x, y, z) = (x, y, z) (x, y, z)(1 + c(p pre f ) + c2 (p pre f )2 /2) (4.54)
where
(x, y, z) net to gross values (NTG (see 12.2.25));
(x, y, z) porosity at the pressure pre f (PORO (see 12.2.24));
c compressibility (ROCK (see 12.5.16)) (default: in e100 = 0, in e300 = 4.934

105 /Bar );
pref reference pressure for (x, y, z) (ROCK (see 12.5.16)) (default 1.0132Bar ).
In stars data format the porosity = (p, T, x, y, z) is calculated according one of the
following models:
1. Linear Elastic Model

(p, T, x, y, z) = re f (x, y, z) exp min pormax, c p (p pre f ) cT (T Tre f ) (4.55)
where
re f (x, y, z) porosity at the pressure pre f (POR (see 13.3.9));

c p compressibility factor (1/Bar) (CPOR (see 13.4.5); default 0);
cT effective thermal expansion coefficient of the formation (1/C) (CTPOR (see
13.4.6), default 0);
pref reference pressure for (x, y, z) (PRPOR (see 13.4.4)) (default pressure
in the first active grid block).
Tre f reference temperature, defined via TEMR (see 13.5.11).
pormax maximal fractional increase in porosity due to pressure (PORMAX (see
13.4.18)). The value pormax should be in the range from 0 to 1. If the keyword
PORMAX (see 13.4.18) is not defined, then the value of pormax is considered
as infinite.
4.24. Porosity 138

2. Nonlinear Elastic Model

(p, T, x, y, z) = re f (x, y, z) exp min pormax, c p (p pre f ) + cporpd cT (T Tre f )
(4.56)
where
cporpd = A [D (p pre f ) + ln(B/C)]
A = (c p2 c p )/2
B = 1 + exp [D (pav p)]

C = 1 + exp D (pav pre f )
D = 10/(ppr2 ppr1)
pav = (ppr1 + ppr2)/2
ppr1, ppr2 lower and upper reference pressures ( ppr2 > ppr1)
c p2 effective formation compressibility (1/Bar) near the value ppr2.
ppr1, ppr2 and c p2 are specified via CPORPD (see 13.4.17)
re f (x, y, z), c p , cT , pref , Tre f , pormax - are defined analogously to Linear
Elastic model.
3. P-T Cross-Term Model
(p, T, x, y, z) = re f (x, y, z)

exp min pormax, c p (p pre f ) + c pT (p pre f )(T Tre f ) cT (T Tre f )
(4.57)
where
c pT pressure-temperature cross-term coefficient of the formation effective poros-
ity (1/Bar/C) (CPTPOR (see 13.4.7), default 0);
re f (x, y, z), c p , cT , pref , Tre f , pormax - are defined analogously to Linear
Elastic model.
4. Dilation-Recompaction Model
This model describes the hysteresis variation of porosity (C.I.Beattie, T.C.Boberg,
G.S.McNab "Reservoir Simulation of Cyclic Steam Stimulation in the Cold Lake Oil
Sands", SPE Reservoir Engineering, May, 1991). This option is activated via the key-
word DILATION (see 13.4.28).
The dependence between porosity and pressure is calculated via the formula

(p, x, y, z) = re f (x, y, z) exp c p (p pre f ) (4.58)
where pre f reference pressure, re f porosity at reference pressure pre f and com-
pressibility c p are different for different regions.
The dilation-recompaction process (pic. 7), consists of 4 phases:
4.24. Porosity 139

Figure 7: Dilation-Recompaction Model
I. Elastic: reversible elastic expansion with a reference pressure pbase (PBASE (see
13.4.19), by default it is equal the value PRPOR (see 13.4.4)), reference porosity
base (POR (see 13.3.9)) and with the pore volume compressibility value cpepac
(1/Bar ) (CPEPAC (see 13.4.20), by default is equal to the value from CPOR
(see 13.4.5))
II. Dilation: when the pressure exceeds the value pdila (PDILA (see 13.4.21), by
default 0). Rock compressibility coefficient at dilation crd (1/Bar ) is set using
CRD (see 13.4.22) (by default 0), the values pdila and (pdila) are taken as pre f
and re f correspondingly. The value crd is greater then cpepac, which provides
a more rapid increase of porosity. The Dilation continues until the moment when
the pressure begins to decrease again, or until the maximum porosity is reached
max . Maximum porosity is defined using reference porosity and the coefficient
PORRATMAX (see 13.4.23) (by default - 1), that sets the coefficient of maximal
porosity increasing over reference porosity.
III. Elastic Compaction: with the initial pore volume compressibility value cpepac,
no recovery after dilation. In this case tNavigator takes maximum values that were
4.24. Porosity 140

4.25. Pore volume of grid block tNavigator-4.2
reached in dilation as re f and pre f .

IV. Recompaction: when the pressure falls below the value p pact (PPACT (see
13.4.24), by default - 0) the recompaction phase is started with with the increase
in the coefficient of compressibility cpact . During this phase there is a partial
recovery after dilatation. During this phase pre f = p pact and re f = (p pact ). The
residual fraction of dilation, that is not reversed in compression, is defined using
the parameter f r (FR (see 13.4.25), 0 fr 1, by default 0). Using f r and
historical maximum porosity, that is reached during dilation, tNavigator calculates
min1 - porosity at p = 0 - via the formula
min = A f r + base (4.59)
After the calculation of min it is possible to calculate compressibility factor cpact

via the formula (4.58):
1 min
min = (p pact ) exp (cpact p pact cpact = ln (4.60)
p pact (p pact )
If after recompaction according the curve (IV ) the pressure starts to increase again,
then a new cycle is started. First there is a reversible elastic expansion of the formation
with base compressibility factor cpepac, until the dilation curve will be reached.
Further Dilation and compaction occur as described above. If after pressure increasing
it decreases (but the dilation curve is not reached), then the reversible compaction
takes place until the moment when the curve (IV ) is reached. the picture below shows
the formation deformation during 3 cycles. During the 2-nd cycle porosity at dilation
process increased more then in 1-st cycle, and in the 3-rd cycle the dilation curve was
not reached so porosity decreased back on the elastic curve.
Temperature effect can be taken into account for Dilation-Recompaction model. the
formula (4.58) is corrected the following way

(p, x, y, z) = re f (x, y, z) exp c p (p pre f ) cT T Tre f (4.61)
where cT effective thermal expansion coefficient of the formation (1/C), set by

CTPOR (see 13.4.6) for elastic curves (I) and (III), CTD (see 13.4.26) for dilation
curve (II) and CTPPAC (see 13.4.27) for recompaction curve (IV ). It is important
to consider that the effect of temperature on the change in porosity is much less
significant than the effect of pressure, so that the coefficients of thermal expansion
must be considerably less than the corresponding coefficient of compressibility.
4.25 Pore volume of grid block

In e300 data format pore volume Vp,re f at reference pressure pref (see 4.24) is:
If PORV (see 12.2.27) is specified, then Vp,re f = PORV (see 12.2.27)
4.25. Pore volume of grid block 141

4.25. Pore volume of grid block tNavigator-4.2
Figure 8: Dilation-Recompaction. Porosity variation during 3 cycles
Else
Vp,re f (x, y, z) = (x, y, z)(x, y, z) (x, y, z)Vgeom (4.62)
where a multiplier (x, y, z) (default: 1) is specified via MULTPV (see 12.2.28), Vgeom
geometric block volume.
Then pore volume
Vp (x, y, z) = Vp,re f (x, y, z)(1 + c(p pre f ) + c2 (p pre f )2 /2) (4.63)
see 4.24.
In stars data format pore volume Vp,re f at reference pressure pref and temperature Tre f
(see 4.24) is calculated via formula (4.62), where multiplier (x, y, z) (default: 1) is set via
VOLMOD (see 13.3.13). Then pore volume
Vp (x, y, z) = Vp,re f (x, y, z)(1 + c p (p pre f ) cT (T Tre f ) + c pT (p pre f )(T Tre f )) (4.64)
see 4.24.
4.25. Pore volume of grid block 142

4.28. Thermal conductivity of the grid block tNavigator-4.2
4.26 Bulk volume of grid block

In e300 data format bulk volume of grid block Vb :
Tf ROCKV (see 12.14.72) is specified, then Vb = Vp,re f + ROCKV (see 12.14.72).
Else Vb = max{Vgeom ,Vp,re f }.
In stars data format bulk volume of grid block Vb = max{ Vgeom ,Vp,re f } where a
multiplier (default: 1) is specified via VOLMOD (see 13.3.13).
4.27 Bulk volume of rock

Bulk volume of rock VR :
VR = max{Vb Vp , 0}.
4.28 Thermal conductivity of the grid block

In e300 data format thermal conductivity of the grid block is
Kb = (1 SG ) kR (4.65)
where
kR rock thermal conductivity (THCONR (see 12.14.15)) (kJ/m/day/C );
is set via THCONSF (see 12.14.16), [0, 1] (default: 0);
SG gas saturation.
In stars data format thermal conductivity of the grid block is specified using the
keyword THCONMIX (see 13.4.13) option SIMPLE

Kb = 1 SbS (kW SW + kO SO + kG SG ) + kS SbS + (1 ) kR (4.66)
where
kP , P = W, O, G, S phase thermal conductivity (THCONW (see 13.4.9), THCONO

(see 13.4.10), THCONG (see 13.4.11), THCONS (see 13.4.12)) (default THCONS
(see 13.4.12) = THCONR (see 13.4.8));
SP , P = W, O, G phase saturation, SbS solid phase saturation;
kR rock thermal conductivity (THCONR (see 13.4.8)) (default 149.6kJ/m/day/C );
porosity.
4.26. Bulk volume of grid block 143

4.29. Chemical reactions tNavigator-4.2
tNavigator also uses the keyword THCONT (see 12.14.18) to specify the parameters kP ,
P = W, O, G, S and kR .
In stars data format isothermal part of the block thermal conductivity specified using
the keyword THCONMIX (see 13.4.13) option COMPLEX

0
p kR p kR
Kb = 1 SW + SO kG F + SW + SO kL F
kG kL
where
kW SW + KO SO
F(x) = exp 0.28 0.32876 log f 0.024755 log x log x , KL =
SW + SO
where
f "mobile" porosity.
The dependence between the block thermal conductivity and the temperature
Kb = Kb0 1.7524 105(T Tre f ) (Kb0 119616)

0
0.64 0 3
(3.6784106 Kb0 )
Kb Kb 1.8 10 T + 110644.8
where Tre f is given by the keyword TEMR (see 13.5.11).
4.29 Chemical reactions

Lets consider nr chemical reactions. For each r , r = 1, . . . , nr there are:
SRr = (SRri )i=1,...,nc stoichiometric coefficients for reactants of the reaction number
r , are specified using STOREAC (see 12.14.53) in e300; STOREAC (see 13.5.32) in
stars;
SPr = (SPri )i=1,...,nc stoichiometric coefficients for products of the reaction number
r , are specified using STOPROD (see 12.14.52) in e300; STOPROD (see 13.5.33) in
stars;
Ar reaction rate of the reaction number r , are specified using REACRATE (see
12.14.46) in e300; FREQFAC (see 13.5.34) in stars;
Er activation energy in chemical reaction rates of the reaction number r , are

specified using REACACT (see 12.14.47) in e300; EACT (see 13.5.36) in stars;
Hr reaction enthalpy of the reaction number r , are specified using REACENTH (see
12.14.56) in e300; RENTH (see 13.5.38) in stars;
Nr = (nri )i=1,...,nc order of component terms, in chemical reaction r rate, (for non
reactants can be > 0 (for catalyst), < 0 (for inhibitor)), are specified using REACCORD
(see 12.14.48), REACSORD (see 12.14.55) in e300; RORDER (see 13.5.39) in stars.
4.29. Chemical reactions 144

4.29. Chemical reactions tNavigator-4.2
For example, for nc = 5, components C12 H26 , C3 H8 , O2 , CO2 , H2 O and nr = 2 reac-

tions:
C12 H26 + 18.5O2 12CO2 + 13H2 O
C12 H26 C3 H8 O2 CO2 H2 O
SRr 1 0 18.5 0 0
SPr 0 0 0 12 13
Nr 1 0 1 0 0
C3 H8 + 5O2 3CO2 + 4H2 O

C12 H26 C3 H8 O2 CO2 H2 O
SRr 0 1 5 0 0
SPr 0 0 0 3 4
Nr 0 1 1 0 0
Reaction rate of the reaction number r , r = 1, . . . , nr (kg mol/day) for the volume Vb
is
nc
0
Rr = Vb Ar eEr /(RT ) (c0ri )nri (4.67)
i=1
kJ
where R = 8.3143 , component concentration (since (4.4)):
K kg mol

1 SS O SO xiO if the reactant i is in the oil phase
b

1 bS G SG xiG if the reactant i is in the gas phase
S

cri = 1 bS W SW xiW if the reactant i is in the water phase
S (4.68)

SbS S xiS = Ni if the reactant i is in the solid phase

N
i if the reactant i is in all phases
(
cri if it isnt gas and not REACPHA (see 12.14.54) with GPP (there is no O2PP (see 13.5.44
c0ri =
p0 xi,G else (for gas)
(4.69)
where temperature, pressure and order are:

T
u if T > T u pu if p > pu
(
if c0ri > Cri

0 0 nri
T = Tl if T < Tl p = pl if p < pl n0ri = (4.70)
1 else
T else p else

where
Tu is specified using RTEMUPR (see 13.5.41) (REACLIMS (see 12.14.49) in e300

data format),
4.29. Chemical reactions 145

4.30. The heat loss between the reservoir and surroundings tNavigator-4.2
Tl RTEMLOWR (see 13.5.42) (REACLIMS (see 12.14.49) in e300 data format),
Cri RXCRITCON (see 13.5.43) (there is no analogue in e300 (n0ri = nri ); tNavigator
uses the keyword Cri = REACCONC (see 12.14.50)),
pu , pl is specified using REACLIMS (see 12.14.49) (there is no analogue in stars

( p0 = p)).
O2PP (see 13.5.44) is used for components in gas phase and is the default value for oxygen.
The component phase in the chemical reaction i (see the description of cri above),
is set via REACPHA (see 12.14.54) in e300, RPHASE (see 13.5.40) in stars. In e300
data format the "mobile" component can be specified in all phases, then cri = Ni . This
is a default value. In stars data format the default value is calculated using the data of the
keyword MODEL (see 13.5.4).
The reaction rate (4.67) can depend on pore volume Vp = Vb :

0
Rr = Vp nr,p Ar eEr /(RT ) (cri )nri (p0 xi,G )nri (4.71)
iFr i6Fr
where nr,p = nri 1, indices Fr :

iFr
Fr = i {1, . . . , nc : if i is no gas and there is no REACPHA (see 12.14.54) with GPP (no O2PP (see 13.
In e300 data format another value nr,p can be specified for each reaction using REACPORD
(see 12.14.51). The reaction rate can be independent of pore volume (nr,p = 0).
The additional component flow i, i = 1, . . . , nc , appears via the chemical reactions:

nr
QRi = (SPri SRri)Rr . (4.72)
r=1
The additional energy flow, appears via the chemical reactions:

nr
QRe = Hr Rr . (4.73)
r=1
4.30 The heat loss between the reservoir and surroundings

In e300 and stars data format there is the same modelling of the heat loss between the
reservoir and surroundings: "A Simple Method for Predicting Cap and Base Rock Heat
Losses in Thermal Reservoir Simulators", Vinsome, P.K.W., Westerveld, J.D., The Journal of
Canadian Petroleum Technology (JCPT), (Montreal), July-September 1980, Volume 19, No.
3, 87-90.
The following parameters are to be specified:
4.30. The heat loss between the reservoir and surroundings 146
4.31. Heater simulation tNavigator-4.2
The connection between the reservoir and cap and base rocks. In e300 data format
the complicated form of connection can be specified via the keyword ROCKCON
(see 12.2.79), in stars the connection can be: the entire surface of the rock region
(THTYPE (see 13.4.2), ROCKTYPE (see 13.4.1)) in the given direction, specified
via the keyword HLOSSPROP (see 13.4.16). tNavigator also uses the keyword ROCK-
CONT (see 12.2.80), which specifies the heat loss directions, volumetric heat capacity
and rock conductivity.
The number of types of cap and base rocks with different properties, which will be
used to model the heat loss between the reservoir and surroundings in e300 is set via
ROCKDIMS (see 12.1.35), in stars is specified at the same time with the description
of the geometry.
Volumetric heat capacity (kJ/m3 /C ) ROCKPROP (see 12.2.78) (e300),

HLOSSPROP (see 13.4.16) (stars), ROCKCONT (see 12.2.80).
Rock conductivity (kJ/m/day/C ) ROCKPROP (see 12.2.78) (e300), HLOSSPROP

(see 13.4.16) (stars), ROCKCONT (see 12.2.80).
Initial temperature (C ) ROCKPROP (see 12.2.78) (e300), HLOSST (see 13.4.14)

(stars), ROCKCONT (see 12.2.80).
Temperature-dependent coefficient of the volumetric heat capacity of the rock

(kJ/m3 /C2 ) ROCKPROP (see 12.2.78) in e300 (is not defined in stars).
Minimal difference between temperatures when the calculations of the heat loss should
start (C ) HLOSSTDIFF (see 13.4.15) in stars, ROCKCONT (see 12.2.80) (default
0) (is missing in e300).
Using these parameters tNavigator calculates for each grid block the value QL the
energy of heat loss between the reservoir and surroundings (QL = 0 if the block isnt
situated on the the reservoir boundary).
4.31 Heater simulation

Lets consider 3 heater models:
I. constant energy injection rate;
II. energy density dependent injection rate (energy rate depends on energy density changing
with the time);
III. temperature difference dependent injection rate (the heater that provides the energy
rate proportionally to the difference between the current temperature in the block and
maximum temperature).
The following parameters should be specified via the keywords:
4.31. Heater simulation 147

4.31. Heater simulation tNavigator-4.2
1. heater name (for E300 format models);
2. I,J,K-coordinates of the heater connection;
3. maximum heat injection rate, Hmax ;

in E300 data format Hmax has units METRIC: kJ/day, FIELD: Btu/day;
units in stars format SI: J/day, FIELD: Btu/day;
4. maximum temperature in the block where heater is connected (METRIC (SI): C ,

FIELD: F );
5. temperature-dependent heat injection rate (proportional heat transfer coefficient be-

tween heat rate and the difference between current block temperature and maximum
temperature), R;
in E300 format R has units METRIC: kJ/day/K , FIELD: Btu/day/R ;
units in stars format SI: J/day C , FIELD: Btu/day F .
4.31.1 Heater with constant energy injection rate

One should enter the following properties to specify the heater for model I: 1-3 (in stars
format parameter 1 shouldnt be specified). In E300 format parameters 1-3 are specified via
the keyword HEATER (see 12.18.157). In stars format parameters 2-3 are specified via the
keyword HEATR (see 13.9.1).
For this heater model the heat will be injected at a constant rate to the grid block:
H = Hmax . (4.74)
4.31.2 Heater with energy density dependent injection rate

One should enter the following properties to specify the heater for model III: 1-5 (in stars
format parameter 1 shouldnt be specified). In E300 format parameters 1-5 are specified via
the keyword HEATER (see 12.18.157). In stars format parameters 2-3 are specified via
the keyword HEATR (see 13.9.1), parameter 4 via the keyword TMPSET (see 13.9.2),
parameter 5 UHTR (see 13.9.3).
In E300 for this heater model the heat rate to the grid block is:
H = min((Tmax T )R, Hmax ), (4.75)
where T current temperature in the grid block. In stars the heat rate to the grid block (for
the linear model) depends on R sign:
(
min((Tmax T )R, 0), R > 0,
H= (4.76)
min((T Tmax )|R|, 0), R < 0.
4.31.1. Heater with constant energy injection rate 148

4.32. Phase flow rate tNavigator-4.2
4.31.3 Selecting of the heater operating mode depending on the defined properties
E300
Hmax Tmax R Model I Model II Model III Off.
default default +
is specified default +
is specified Tmax < 1.0E10 +
is specified Tmax > 1.0E10 +
is specified Tmax < 1.0E10 is specified +
Hmax > 0 is specified R = .0 +
4.31.4 Temperature difference dependent injection rate

In E300, if we enter the heater properties 1-4, the value of energy rate in grid block depend
on changing with time of the energy density in the block:
i1
Etot (Tmax ) Etot
H = min(V , Hmax ), (4.77)
dt
where V - block volume, Etot (Tmax ) - density of the full energy in the block at maximum
i1
temperature, specified via 4, Etot - density of the full energy at the previous time step, dt -
the length of the last time step.
4.31.5 Flags of automatic heating or cooling (stars)

In stars for the block to which the heater is connected, one could specify an option of
automatic switching of heater operation mode (R > 0):
(
min((Tmax T )R, Hmax ), T < Tmax ,
H= (4.78)
0, T Tmax .
The same way the operation mode of cooling element can be switched automatically
(R < 0):
(
min((T Tmax )R, Hmax ), T > Tmax ,
H= (4.79)
0, T Tmax .
4.32 Phase flow rate

k
rP
u p = c k (p + PcP P gd) (4.80)
P
where
c the constant value, g gravitation constant,
krP = krP (SW , SG ) phase relative permeability,
d = d(x, y, z) depth (top-down).
4.31.3. Selecting of the heater operating mode depending on the defined properties E300149
4.34. Energy conservation equation tNavigator-4.2
4.33 Mass conservation equation

Mass conservation equation (moles) for each component:
nP 0

(1 SS )Nc = div xc,P PUP + Qc + QRc , c = 1, . . . , n0c
b (4.81)
t P=1

( Nc ) = QRc , c = n0c + 1, . . . , nc (4.82)
t
where
UP = UP (p, N) velocity vector (4.80) of phase flow P, P = 1, . . . , n0P ;
Qc = nw=1 qc total rate of all sources and flows; -Dirack function, on the

trajectory of source (flow) number , qc rate (negative for flows and positive for
sources), nw total number of sources and flows;
QRc component c flow, appears via the chemical reactions (4.72);
SbS solid phase saturation (4.4);
n0P , n0c see page 123.

Sources and flows injectors and producers and aquifers.
4.34 Energy conservation equation

Energy conservation equation:

(Ub ) = Fe +Ce + QRe + Qwell
e QL (4.83)
t
where
internal block energy (kJ ) Ub specified via (4.53);
convection enthalpy flow from (in) neighbouring surrounding points

n0P
Fe = div HPPUP
P=1
where phase enthalpy HP specified via (4.38), UP = UP (p, N) velocity vector

(4.80) of phase flow;
energy flow due to conductivity
Ce = div(Kb T ),
where Kb block thermal conductivity (kJ/m/day/C ), see page 143;
4.33. Mass conservation equation 150

4.35. Phase relative permeabilities tNavigator-4.2
energy flow due to chemical reactions QRe see (4.73);
energy flow from the well

n0P
Qwell
e = HP P QP, (4.84)
P=1
where QP rate of phase P for connection in the grid block, phase enthalpy HP
specified via (4.38);
QL energy flow due to heat loss with surrounding, see page 146.
Total energy conservation equation for block Vb :

! 0
n0c
! ! !
nP nc

t
Vp 1 SbS Nc (RP HP) 102 p +Vp Nc Hc,S (T ) +VR HR
c=1 P=1 c=n0c +1
Z 0 nP
! Z
= HPPUP ds + Kb T ds + QRe + Qwell
e QL .
P=1
Vb Vb
Where VR = max{Vb Vp , 0}.
In the equations above (mass conservation equation for components and energy conserva-
tion equation) the primary variables are p, Nc and T (parameter ZT in the keyword TFORM
(see 12.1.8)). In case if the primary variables are p, Nc and Etot system fluid enthalpy
(parameter ZH in the keyword TFORM (see 12.1.8)).
In this case the form of mass conservation equation doesnt change (4.81) but the energy
conservation equation will be the following:
n0P
! Z
! Z

t
Vb Etot = HPPUP ds + KbT ds + QRe + Qwell e QL .
P=1
Vb Vb
4.35 Phase relative permeabilities

Calculation of phase relative permeabilities contains the following stages:
1. Permeabilities and capillary pressure are calculated for two-phase systems wateroil
and gasoil (see the table 1).
2. Relative permeabilities (and capillary pressure) scaling for two-phase systems (see
4.35.2, see the table 3).
3. Oil relative permeability krO is calculated using the first or the second Stones model.
4.35. Phase relative permeabilities 151

Phase permeability scaling. Specification of critical saturations can be done using one
of the following ways (they are not compatible):
Specification of critical saturations for each grid block (keywords SWL (see 12.6.27),
SWCR (see 12.6.30), ..., KRW (see 12.6.43), ...).
Specification of critical saturations as depth function (keywords ENPTVD (see 12.6.38),

ENKRVD (see 12.6.39)).
Specification of critical saturations as temperature function (keywords ENPTVT (see

12.14.69), ENKRVT (see 12.14.70)) - only for thermo-compositional model.
Specification of critical saturations as tracer concentration function (salt, surfactant)

(keyword can only be used in tNavigator ENPTRC (see 12.6.41)).
4.35.1 Phase relative permeability for two-phase systems

Specification of phase relative permeabilities is in the table 1.
Value e300 data format CMG data format Value description

krW (SW ), SWOF (see 12.6.1) SWT (see 13.6.3) relative permeability for
krOW (SW ) two-phase system wateroil
krG (SG ), krOG (SG ) SGOF (see 12.6.2) SLT (see 13.6.4) relative permeability for
two-phase system gasoil
PcOW (SW ) SWOF (see 12.6.1) SWT (see 13.6.3) capillary pressure
two-phase system wateroil
PcOG (SG ) SGOF (see 12.6.2) SLT (see 13.6.4) capillary pressure
two-phase system gasoil
Table 1: Phase relative permeabilities
Phase relative permeabilities can be specified for different saturation regions (Saturation
regions are specified via SATNUM (see 12.4.3) (e300), KRTYPE (see 13.6.7) (CMG)). I
- saturation region number for current block i. From the table 1 we take functions for I
and enter for them constants from the table 2. We suppose that at initialization stage the
following condition is checked
max krOW = max krOG
SW SG
4.35.2 Phase relative permeabilities scaling

Each constant in the table 2 can be changed,
via phase permeabilities scaling;
these constants can be specified as temperature dependent constants;
4.35.1. Phase relative permeability for two-phase systems 152

Value Value description

SW L minimal value of SW in table for water
SWCR maximal value of SW in table for water, for which krW (SW ) = 0
SWU maximal value of SW in table for water
SGL minimal value of SG in table for gas
SGCR maximal value of SG in table for gas, for which krG (SG ) = 0
SGU maximal value of SG in table for gas
SOWCR maximal value of SO = 1SW SGL in table for water, for which krOW (SW ) = 0
SOGCR maximal value of SO = 1 SG SW L in table for gas, for which krOG (SG ) = 0
krW max maximal value of function krW (SW )
krGmax maximal value of function krG (SG )
krOmax maximal value of function krOW (SW ) and krOG (SG )
krW R krW (1 SOWCR SGL )
krGR krG (1 SOGCR SW L )
krORG krOG (SGCR )
krORW krOW (SWCR )
PCGmax maximal value of function PcOG (SG )
PCW max maximal value of function PcOW (SW )
Table 2: Phase relative permeability constants
see the table 3.

Phase relative permeability scaling is switched on using the keyword ENDSCALE (see
12.6.24) (e300 data format run).
In CMG data format initial conditions can be specified as constants in saturation regions
(for example SWR (see 13.6.9) etc.) and as constants in each grid block (for example
BSWR (see 13.6.10) etc.), in e300 data format constant should be specified for each grid
block. tNavigator supports all keyword from the table 3.
Calculated values should satisfy the following conditions:
0
1. SGU 0
6 1 SW L
0 6 1 S0
2. SGL WU
0
3. SOWCR 0
+ SWCR <1
0
4. SOGCR 0
+ SGCR 0
+ SW L<1
Two-point phase relative permeability scaling keeps permeability values (from tables) in
two points:
Permeability Point 1 Point 2

krW 0
SWCR 0
SWU
krG 0
SGCR 0
SGU
krOW 0
SW 0
1 SOWCR 0
SGL
L
krOG 0
SGL 0 0
1 SOGCR SW L
4.35.2. Phase relative permeabilities scaling 153

Value Number e300 (replace "Number") CMG (replace "Number")

0
SW L SW L SWL (see 12.6.27) BSWR (see 13.6.10)
ENPTVT (see 12.14.69), parameter 2 SWR (see 13.6.9)
KRTEMTAB (see 13.6.8)
0
SWCR SWCR SWCR (see 12.6.30) BSWCRIT (see 13.6.12)
ENPTVT (see 12.14.69), parameter 3 SWCRIT (see 13.6.11)
0
SWU SWU SWU (see 12.6.34) 1 BSOIRW (see 13.6.14)
ENPTVT (see 12.14.69), parameter 4 1 SOIRW (see 13.6.13)
1 KRTEMTAB (see 13.6.8)
0
SGL SGL SGL (see 12.6.29) BSGCON (see 13.6.16)
ENPTVT (see 12.14.69), parameter 5 SGCON (see 13.6.15)
0
SGCR SGCR SGCR (see 12.6.31) BSGR (see 13.6.18)
ENPTVT (see 12.14.69), parameter 6 SGR (see 13.6.17)
0
SGU SGU SGU (see 12.6.35) 1 BSOIRG (see 13.6.20)
ENPTVT (see 12.14.69), parameter 7 1 SOIRG (see 13.6.19)
1 KRTEMTAB (see 13.6.8)
0
SOWCR SOWCR SOWCR (see 12.6.32) BSORW (see 13.6.22)
ENPTVT (see 12.14.69), parameter 8 SORW (see 13.6.21)
0
SOGCR SOGCR SOGCR (see 12.6.33) BSORG (see 13.6.24)
ENPTVT (see 12.14.69), parameter 9 SORG (see 13.6.23)
0
krW max krW max KRW (see 12.6.43) BKRWIRO (see 13.6.26)
ENKRVT (see 12.14.70), parameter 2 KRWIRO (see 13.6.25)
0
krGmax krGmax KRG (see 12.6.44) BKRGCW (see 13.6.28)
ENKRVT (see 12.14.70), parameter 3 KRGCW (see 13.6.27)
0
krOmax krOmax KRO (see 12.6.42) BKROCW (see 13.6.30)
ENKRVT (see 12.14.70), parameter 4 KROCW (see 13.6.29)
0
krW R krW R KRWR (see 12.6.43)
ENKRVT (see 12.14.70), parameter 5
0
krGR krGR KRGR (see 12.6.44)
0
krORG krORG KRORG (see 12.6.42)
0
krORW krORW KRORW (see 12.6.42)
0
PCGmax PCGmax PCG (see 12.6.47) BPCGMAX (see 13.6.32)
ENPCVT (see 12.14.71), parameter 2 PCGEND (see 13.6.31)
0
PCW max PCW max PCW (see 12.6.46) BPCWMAX (see 13.6.34)
ENPCVT (see 12.14.71), parameter 3 PCWEND (see 13.6.33)
Table 3: Phase relative permeability scaling

For the given SW , T :

0 0 (T )

SW SWCR (T ) > SWU

SWCR

0
SW < SWCR (T )
0
SW (SW , T ) = 0 (T )
(4.85)

SWU SW > SWU
SWU SWCR

0
SWCR + (SW SWCR

(T )) else
0 0
SWU (T ) SWCR (T )
0
0 krW max (T ) 0
krW (SW , T ) = krW (SW (SW , T )) (4.86)
krW max
If there is an oil phase in the model, the following parameters are calculated

0 (T ) > 1 S0 0
SW SW L OWCR (T ) SGL (T )

0 (T )

SW L SW < SW L

0 0 0 (T )
SOW (SW , T ) = 1 SOWCR SGL SW > 1 SOWCR (T ) SGL
0 (T ))

SW L + (SW SW

L

1 SOWCR SGL SW L
0 (T ) S0 (T ) else

0
1 SOWCR (T ) SGL WL
(4.87)
k 0 (T )
0 0
krOW (SW , T ) = rOmax krOW (SOW (SW , T )) (4.88)
krOmax
0 (T ) > S0 (T )

SW SW L WU

SW L

0 (T )
SW < SW L
0
ScOW (SW , T ) = 0 (T )
(4.89)

SWU SW > SWU
SWU SW L

0 (T ))
SW L + (SW SW else
L 0 0 (T )
SWU (T ) SW L
0
0 PCW max (T ) 0
PcOW (SW , T ) = PcOW (ScOW (SW , T )) (4.90)
PCW max
If there is gas phase in the model, for the given SG , T :
0 0 (T )

SG SGCR (T ) > SGU

SGCR

0
SG < SGCR (T )
0
SG (SG , T ) = 0 (T )
(4.91)

SGU SG > SGU
SGU SGCR

SGCR + (SG SGCR

0 (T )) 0 else
0
SGU (T ) SGCR (T )
k 0 (T )
0 0
krG (SG , T ) = rGmax krG (SG (SG , T )) (4.92)
krGmax

If there is an oil phase in the model, the following parameters are calculated

0 (T ) > 1 S0 0
SG SGL OGCR (T ) SW L (T )

0 (T )

SGL SG < SGL

0 0 0 (T )
SOG (SG , T ) = 1 SOGCR SW L SG > 1 SOGCR (T ) SW L
0 (T ))

S + (S S

GL G

GL

1 SOGCR SW L SGL
0 (T ) S0 (T ) else

0
1 SOGCR (T ) SW L GL
(4.93)
k 0 (T )
0 0
krOG (SG , T ) = rOmax krOG (SOG (SG , T )) (4.94)
krOmax
0 (T ) > S0 (T )

SG SGL GU

SGL

0 (T )
SG < SGL
0
ScOG (SG , T ) = 0 (T )
(4.95)

SGU SG > SGU
SGU SGL

0 (T ))
SGL + (SG SGL else
0 0 (T )
SGU (T ) SGL
0
PCGmax (T )
0 0
PcOG (SG , T ) = PcOG (ScOG (SG , T )) (4.96)
PCGmax
Phase relative permeabilities free-point scaling is enable in e300 data format (see the
keyword SCALECRS (see 12.6.26)). This method keeps permeability values in free points
in the table below (additional point SW r (SGr )).
Permeability Point 1 Point 2 Point 3

krW 0
SWCR 0
1 SOWCR 0
SGL 0
SWU
krG 0
SGCR 0 0
1 SOGCR SW L 0
SGU
krOW 0
SW 0
SWCR 0
1 SOWCR 0
SGL
L
krOG 0
SGL 0
SGCR 0
1 SOGCR 0
SW L
For the given SW , T the following parameters are calculated:

(
0
1 SOWCR 0 (T ) if oil phase is enable
(T ) SGL
0
SW r (T ) = 0
1 SGCR (T ) else
(
1 SOWCR SGL if oil phase is enable
SW r =
1 SGCR else

If calculated value SW 0 (T ) is not in an interval [S0 0 0 0

r WCR (T ), SWU (T )] or SWCR (T ) > SWU (T ),
then SW 0 (S , T ) is calculated via formula (4.85), else:
W

SWCR 0
SW < SWCR (T )

0 SW r SWCR 0 0 (T )
SWCR + (SW SWCR (T )) 0 SWCR (T ) 6 SW < SW

0
SW r (T ) SWCR (T ) r
0
SW (SW , T ) =
0 (T )) SWU SW r 0 (T ) 6 S < S0 (T )
SW r + (SW SW SW

W

r
S 0 (T ) S 0 (T ) r WU

WU W r
0 (T )

S
WU SW > SWU
(4.97)
Note that SW 0 (S0 (T ), T ) = S .
Wr Wr
If the keyword KRWR (see 12.6.43) is not specified or krW (SW r ) > krW max , then
0 (S , T ) is calculated via formula (4.86), else:
krW W
0
krW R (T ) 0 0 (T )

krW (SW (SW , T )) SW < SW r
krW (SW r )

0 0 0
krW (SW , T ) = k0 (T ) + krW max (T ) krW R (T ) (4.98)
rW R
krW max krW (SW r )

0 0 (T )
(krW (SW (SW , T )) krW (SW r )) SW > SW r
0 (S0 (T ), T ) = k0
Note that krW Wr rW R (T ).
0 (S , T ), k0
If oil phase is present then SOW W rOW (SW , T ) also are calculated. For the given
SW , T the following parameters are calculated:
0 0
SOW r (T ) = SWCR (T ), SOW r = SWCR .
0 0 0 0
If calculated value SOW r (T ) is not in the interval [SW L (T ), 1 SOWCR (T ) SGL (T )] or
0 (T ) > 1 S0 0 0
SW L OWCR (T ) SGL (T ), then SOW (SW , T ) is calculated via formula (4.87), else
0
SOW (SW , T ) =
0 (T )

SW L SW < SW L

0 (T )) SOW r SW L 0 (T ) 6 S < S0

SW L + (SW SW L 0 0 (T ) SW L W OW r (T )
SOW r (T ) SW

L
= S 0
OW r + (SW SOW r (T ))
1 SOWCR SGL SOW r

0 0 0
SOW r (T ) 6 SW < 1 SOWCR (T ) SGL (T )

0 0 (T ) S0

1 SOWCR (T ) SGL OW r (T )

1 SOWCR SGL 0
SW > 1 SOWCR 0 (T )
(T ) SGL
(4.99)
0 (S0
Note that SOW OW r (T ), T ) = SOW r .

If the keyword KRORW (see 12.6.42) is not specified or krOW (SOW r ) > krOmax , then
0
krOW (SW , T )is calculated via formula (4.88), else
0
krOmax 0
(T ) krORW (T )

0
krORW (T ) +
krOmax krOW (SOW r )

0 0 (S , T )) k 0
krOW (SW , T ) = (krOW (SOW W rOW (SOW r )) SW < SOW r (T ) (4.100)
k0 (T )

rORW
0 0
krOW (SOW (SW , T )) SW > SOW r (T )
krOW (SOW r )
0
Note that krOW 0
(SOW 0
r (T ), T ) = krORW (T ).
If gas phase is present then for the given SG , T the following parameters are calculated:
(
0
1 SOGCR 0 (T ) if oil phase is present
(T ) SW
0 L
SGr (T ) = 0
1 SWCR (T ) else
(
1 SOGCR SW L if oil phase is present
SGr =
1 SWCR else
If the calculated value SGr 0 (T ) is not in the interval [S0 0 0 0

GCR (T ), SGU (T )] or SGCR (T ) > SGU (T ),
then SG 0 (S , T ) is calculated via formula (4.91), else
G

SGCR 0
SG < SGCR (T )

0 SGr SGCR 0 0 (T )
SGCR + (SG SGCR (T )) 0 SGCR (T ) 6 SG < SGr

SGr (T ) SGCR0 (T )
0
SG (SG , T ) =
0 (T )) SGU SGr 0 (T ) 6 S < S0 (T )
SGr + (SG SGr SGr

G

S 0 (T ) S 0 (T ) GU

GU Gr
0 (T )

S
GU SG > SGU
(4.101)
Note that SG 0 (S0 (T ), T ) = S .
Gr Gr
If the keyword KRGR (see 12.6.44) is not specified or krG (SGr ) > krGmax , then krG 0 (S , T )
G
is calculated via formula (4.92), else
0
krGR (T ) 0 0 (T )

krG (SG (SG , T )) SG < SGr
krG (SGr )

0 0
krGmax (T ) krGR0 (T )
krG (SG , T ) = 0 (4.102)
k rGR (T ) +
k k (S )

rGmax rG Gr

(krG (SG 0 (S , T )) k (S )) 0 (T )
SG > SGr
G rG Gr
0 (S0 (T ), T ) = k0
Note that krG Gr rGR (T ).
If oil phase is present then SOG0 (S , T ), k0
G rOG (SG , T ) also are calculated. For the given
SG , T the following parameters are calculated:
0 0
SOGr (T ) = SGCR (T ), SOGr = SGCR .

0 0 (T ), 1 S0 0
If calculated value SOGr (T ) is not in the interval [SGL OGCR (T ) SW L (T )] or
0 (T ) > 1 S0 0 0
SGL OGCR (T ) SW L (T ), then SOG (SG , T ) is calculated via formula (4.93), else
0
SOG (SG , T ) =
0 (T )

SGL SG < SGL

0 (T )) SOGr SGL 0 (T ) 6 S < S0

S GL + (S G S GL 0 0 (T ) SGL G OGr (T )
SOGr (T ) SGL

= S 0
OGr + (SG SOGr (T ))
1 SOGCR SW L SOGr

0
SOGr 0
(T ) 6 SG < 1 SOGCR 0 (T )
(T ) SW
0 0 (T ) S0 L

1 SOGCR (T ) SW OGr (T )

L

1 SOGCR SW L 0
SG > 1 SOGCR 0 (T )
(T ) SW L
(4.103)
Note that SOG 0 (S0

OGr (T ), T ) = SOGr .
If the keyword KRORG (see 12.6.42) is not specified or krOG (SOGr ) > krOmax , then
0
krOG (SG , T ) is calculated via formula (4.94), else
0
krOmax 0
(T ) krORG (T )
k 0 (T ) +
rORG

krOmax krOG (SOGr )

0 0 (S , T )) k 0
krOG (SG , T ) = (krOG (SOG G rOG (SOGr )) SG < SOGr (T ) (4.104)
k0 (T )

rORG
0 0
krOG (SOG (SG , T )) SG > SOGr (T )
krOG (SOGr )
0
Note that krOG 0
(SOGr 0
(T ), T ) = krORG (T ).
4.35.3 Phase relative permeabilities for free-phase systems

If oil phase is present in the model, then oil relative permeability krO should be calculated.
Lets consider models from the table 4.
Name e300 data format CMG data format

Linear model (see [21]) default RPT (see 13.6.2)
(default)
Stone I model(standard) STONE1 (see can not be defined
12.6.20)
Stone I model(modified) (see [22]) can not be defined RPT (see 13.6.2)
(STONE1)
Stone II model(modified) STONE2 (see default, RPT (see
12.6.21) 13.6.2) (STONE2)
Table 4: Phase relative permeabilities for free-phase systems
4.35.3. Phase relative permeabilities for free-phase systems 159

Linear Beykers model. Let ( small parameter):

0 0 (T ), T ) 0 (T ) <

krOG (SG + SW SW L SW SW L

k0 (SG + SW , T )

SG <
rOW

0
krO (SW , SG , T ) = SG k0 (SG + SW S0 (T ), T ) (4.105)
rOG WL

0 (T )) +

S G + (SW SW L
0 (T )) k0

(S SW rOW (SG + SW , T )

+ W

L

0 (T )) else
SG + (SW SW L
First Stones model. Lets consider SOm (SG , T ):

for standard first Stones model:
0 0
SOm (T ) = min(SOWCR (T ), SOGCR (T ))
for modified first Stones model:

0 0
SOm (SG , T ) = (SG , T )SOWCR (T ) + (1 (SG , T ))SOGCR (T ),
where
SG
(SG , T ) = 1 0 0 .
1 SW L (T ) SOGCR (T )
Let
0 0
SW (SW , T ) = max(SW , SW L (T )).
Lets denote as SO (S , S , T ), S (S , S , T ), S (S , T ) the following values:
W G W W G G G
0
1 SW (SW , T ) SG SOm (SG , T ) if 1 S0 (S , T ) S > S (S , T )

0 (T ) S (S , T ) W W G Om G
SO (SW , SG , T ) = 1 SW L Om G
0 else

0 (S , T ) S0 (T )
SW
W WL
SW (SW , SG , T ) = 0 (T ) S (S , T )
1 SW L Om G
S G
SG (SG , T ) = 0 (T ) S (S , T )
1 SW L Om G
Then
0
krOW (SW , T ) 0
krOG (SG , T )
0 0 0
krO (SW , SG , T ) = krOW (SW L (T ), T ) 0 0 0 0
krOW (SW L (T ), T ) krOG (SGL (T ), T )
(S , S , T )
SO W G
(S , T )) (4.106)
(1 SW (SW , SG , T ))(1 SG G
Since krOW (SW L , T ) = krOG (SGL , T ) maximal value in the table, this formula provides
krO (SW L , SG , T ) = krOG (SG , T ) and krO (SW , SGL , T ) = krOW (SW , T ).
4.35.3. Phase relative permeabilities for free-phase systems 160

4.36. Calculation of the phase composition tNavigator-4.2
Second Stones model. Lets consider the following functions:

0
krGmax (T )

0 if KRG (see 12.6.44) and KRW (see 12.6.43) are specified
krW (T )

max
krW max

0 if only KRW (see 12.6.43) is specified
(T ) = krW max (T )

0
krGmax (T )
if only KRG (see 12.6.44) is specified

krW max

1 else

0 (4.107)
krW max (T )

0 if KRG (see 12.6.44) and KRW (see 12.6.43) are specified
krGmax (T )

0
krW max (T )

if only KRW (see 12.6.43) is specified
(T ) = krGmax
k
0 rGmax

if only KRG (see 12.6.44) is specified

krGmax (T )
1 else

(4.108)
Then
k0 (S , T )
0 0 0 rOW W 0
krO (SW , SG , T ) = krOW (SW L (T ), T ) 0 0 (T ), T ) + (T )krW (SW , T )
krOW (SW L
0
k (SG , T ) 0 0 0

0 rOG0 + (T )krG (SG , T ) ((T )krW (SW , T ) + (T )krG (SG , T )) (4.109)
krOG (SGL (T ), T )
If krO (SW , SG , T ) < 0, then krO (SW , SG , T ) = 0 is considered. Since krOW (SW L , T ) =
krOG (SGL , T ) maximal value in the table, this formula provides krO (SW L , SG , T ) =
krOG (SG , T ) and krO (SW , SGL , T ) = krOW (SW , T ).
4.36 Calculation of the phase composition

Calculation of the phase composition of the mixture from pressure, component molar
densities and total molar enthalpy of the mixture.
We consider the problem of calculation of the phase composition and temperature of the mix-
ture in a situation where the primary variables of filtration equations and energy conservation
equation are pressure, molar density of the components, and a volumetric energy density of
the block.
4.36.1 Statement of the problem

We have the notations introduced earlier. Thus, suppose there is a mixture consisting from
0
nc components, first nc components are movable. We assume that the following values are
known: pressure p, molar densities of the components Nc , c = 1, . . . , nc , and a volumetric
4.36. Calculation of the phase composition 161

4.37. Initial conditions tNavigator-4.2
energy density Etot . According to this data it is necessary to calculate the phase mixture com-
position (RP , P = O,W, G), temperature (T ), and the concentrations of movable components
0
in the phases (xc,P , c = 1, . . . , nc ).
There is a system of algebraic equations:
0
zc = xc,P RP c = 1, . . . , nc
P=O,W,G
xc,G
= Kc (p, T ) c,G > 0, c,L > 0, where L {O,W }
x
c,L
0
nc
xc,P = 1 P = O,W, G
c=1 !
nc
e f f (1 SbS ) Ntot RP HP 102 p + e f f , Nc Hc,S +
P=O,W,G c=nc
+(1 e f f )HR = Etot ,
(4.110)
0
nc
where e f f = Vp /Vb effective porosity, Ntot = Nc . Note, then the number of equations
c=1
0 00 00
and the number of variables in (4.110) are equal (and equal to 4 + nc + nc , here nc the
number of components, for which c,G > 0, c,L > 0, where as in (4.110) L {O,W }).

For the equations (4.81), (4.83) one should specify initial p, Nc , T . tNavigator uses two
variants of specification of initial conditions:
explicit specification of initial conditions;
initial conditions are calculated from hydrostatic and thermodynamic equilibrium con-
ditions.
4.37.1 Explicit specification of initial conditions

In this case the following parameters are always specified explicitly:
pressure p via PRESSURE (see 12.15.8) (PRES (see 13.7.16));
temperature T via TEMPI (see 12.15.26) (TEMP (see 13.7.17)).
For solid phase always
in e300 data format one should specify explicitly solid phase saturation SbS and
component distribution xc,S (see (4.4) via SSOLID (see 12.15.13) and SMF (see
12.15.16); then molar density of solid phase is calculated (4.19) and molar densities
Nc , c = n0c + 1, . . . , nc ;
in stars data format one should specify explicitly molar densities Nc , c = n0c +1, . . . , nc
of components, which are present in solid phase, via CONC_SLD (see 13.7.18).

Phase and component composition of mobile phases and components can be specified
several ways.
tNavigator (this option is missing in stars and e300 data formats) allows to specify
n0c
explicitly values zc = Nc /Ntot , c = 1, . . . , n0c , Ntot = Nc via ZMF (see 12.15.19). So
c=1
initialization algorithm is the following:
calculation of Ki = Ki (p, T ) using pressure and temperature from (4.24), (4.26),

(4.27)
calculation of the solution of equation (4.21) and values RP , xc,P
calculation of molar phase densities of mobile phases P , P = 1, . . . , n0P from
(4.5), (4.7), (4.10), (4.13), (4.14), (4.15)
calculation of Ntot
calculation of molar densities of mobile components Nc = zc Ntot , c = 1, . . . , n0c .
In e300 data format (this option is missing in stars) value of z0c = Nc /Ntot
0 , c=
n0c
2, . . . , n0c , 0
Ntot = Nc is specified explicitly via ZMF (see 12.15.19), water saturation
c=2
SW is set via SWAT (see 12.15.10). Free gas is not defined: SG = 0, SO = 1 SW , two
keywords SOIL (see 12.15.12) and SGAS (see 12.15.11) are ignored. Initialization
algorithm is the following:
calculation of the matrix xc,P :
xw,W = 1, xc,W = 0, xw,O = 0, xc,O = z0c xw,G = 0, xc,G = 0, c = 1, . . . , n0c ;
calculation of molar densities W , O ;

calculation of the values Nc :
Nw = W SW , Nc = xc,O O SO = z0c O SO , c = 2, . . . , n0c .
Saturation of mobile phases SP is specified explicitly using SWAT (see 12.15.10)

(SW (see 13.7.15)), SOIL (see 12.15.12) (SO (see 13.7.13)), SGAS (see 12.15.11)
(SG (see 13.7.14)). Concentration matrix xc,P c = 1, . . . , n0c , P = O, G (for P =
W ) using XMF (see 12.15.17) (MFRAC_OIL (see 13.7.19)), YMF (see 12.15.18)
(MFRAC_GAS (see 13.7.20)). Since (4.1) one can specify only several saturations
(not all), see a table below. Swc critical water saturation, which is calculated from
the table of relative permeabilities at the given temperature.
Then the initialization algorithm is the following:
calculation of molar densities of mobile phases P , P = 1, . . . , n0P from (4.5),

(4.7), (4.10), (4.13), (4.14), (4.15)
calculation of molar densities of mobile components Nc , c = 1, . . . , n0c .
4.37.1. Explicit specification of initial conditions 163

N SW SO SG E300 format stars format Calculations

1

2 SG = 1 SW SO

3 SO = 1 SW SG

4 SW = 1 SO SG

5 SO = 1 SW , SG = 0

6 SW = 1 SO , SG = 0

7 SW = Swc , SO = 1 SW SG

8 SW = Swc , SG = 0, SO = 1 SW
In e300 and stars data formats initial conditions are specified in each grid block.
Pressure PRESSURE (see 12.15.8), PRES (see 13.7.16).
Temperature TEMPI (see 12.15.26), TEMP (see 13.7.17).
Solid phase SSOLID (see 12.15.13), SMF (see 12.15.16), CONC_SLD (see 13.7.18).
Mobile phases ZMF (see 12.15.19), SWAT (see 12.15.10), SOIL (see 12.15.12),
SGAS (see 12.15.11), XMF (see 12.15.17), YMF (see 12.15.18), SW (see 13.7.15),
SO (see 13.7.13), SG (see 13.7.14), MFRAC_OIL (see 13.7.19), MFRAC_GAS (see
13.7.20).
4.37.2 Calculations of initial conditions from hydrostatic and thermodynamic equilib-

rium conditions
Solid phase saturation is specified explicitly, see 4.37.1.
Temperature T distribution:
in e300 data format depends on depth TEMPVD (see 12.14.68);
in stars data format is specified implicitly via TEMP (see 13.7.17).
In black oil case the pressure p and saturation of mobile phases are calculated from
hydrostatic equilibrium conditions EQUIL (see 12.15.2) (VERTICAL (see 13.7.2)).
In these calculations phase mass density should be calculated. In black oil case one
should specify PVT tables and the distribution of boiling points (dew points) versus depth.
In compositional run component composition of mixture should be specified in order
to calculate phase mass densities. Stars supports only explicit specification of concentra-
tion matrix xc,P c = 1, . . . , n0c , P = O, G in each block via MFRAC_OIL (see 13.7.19),
MFRAC_GAS (see 13.7.20), see 4.37.1.
In e300 data format there are several ways to specify component composition of mixture
versus depth.
4.37.2. Calculations of initial conditions from hydrostatic and thermodynamic equilibrium conditions164
n0c
Distribution of values zc = Nc /Ntot , c = 1, . . . , n0c , Ntot = Nc versus depth is spec-
c=1
ified via ZMFVD (see 12.13.14). Then mass density is calculated via the following
algorithm:
values Ki = Ki (p, T ) are calculated from pressure and temperature at selected

depth (4.24), (4.26), (4.27);
solution of equations (4.21) and calculate the values RP , xc,P ;
calculation of mobile phases mass densities P , P = 1, . . . , n0P from (4.5), (4.7),
(4.10), (4.13), (4.14), (4.15).
At the end of calculations:
calculated values zc in grid blocks are saved in an array ZMF (see 12.15.19);
calculation of Ntot ;
calculation of mobile components molar densities Nc = zc Ntot , c = 1, . . . , n0c .
Distribution of concentration matrix xc,P c = 1, . . . , n0c , P = O, G (for P = W ) versus

pressure is set via XMFVP (see 12.13.12), YMFVP (see 12.13.13).
Hence this initialization can lead to thermodynamic non-equilibrium distribution. There-
fore only one xc,P (of the phase which saturation is > 0; priority is O, G) is used. The
second xc,P is calculated.
if SO > 0, then xc,O = XMF, xc,G = Kc (p, T )xc,O , c = 2, . . . , n0c ;

if SG > 0, then xc,G = YMF, xc,O = xc,G /Kc (p, T ), c = 2, . . . , n0c .
Mobile phases mass densities P , P = 1, . . . , n0P are calculated from (4.5), (4.7),
(4.10), (4.13), (4.14), (4.15).
At the end of calculations:
calculated values xc,P in grid blocks are saved in arrays XMF (see 12.15.17),
YMF (see 12.15.18);
calculation of mobile phases molar densities P , P = 1, . . . , n0P from (4.5), (4.7),
(4.10), (4.13), (4.14), (4.15)
calculation of mobile components molar densities Nc , c = 1, . . . , n0c .
4.37.2. Calculations of initial conditions from hydrostatic and thermodynamic equilibrium conditions165
5.3. Time approximation tNavigator-4.2
5 Mathematical model
Simulator uses usual finite difference approximation with respect to space and time variables
to obtain discretization of physical model equations.
The detailed description of transition from physical model to non-linear and then linear
equations is written in the section 5.4.
5.1 Space approximation

Simulator uses standard finite difference approximation with respect to space variables on
rectangular block centered mesh. The standard upstream approximation is used for computa-
tion of coefficients of equations depending on saturations.
5.2 Solution algorithm for time step problem

Simulator has to solve system of linear equations for pressure on each time step. The pre-
conditioned biconjugate gradient method is used with modified incomplete LU factorization
(MILU(0)) as preconditioner. Time step is chosen to satisfy constraints posed on maximal
variation of saturation, pressure and pore volume in each grid block.
5.3 Time approximation

For approximation with respect to time simulator uses Fully Implicit method by default for
black-oil models.
In this case both pressures and component molar densities are regarded as unknowns and
all coefficients are calculated from their current values. This leads to system of non-linear
equations to be solved. For solution standard Newton method is used.
Time step is chosen automatically to provide method convergence.
AIM (adaptive implicit) is used by default for compositional models.

In black-oil models fully implicit is used by default. To use AIM in black-oil one need to set
AIM parameter of the keyword RUNCTRL (see 12.18.119) or specify the keyword AIM (see
12.1.93).
Settings of AIM can be changed in the keyword AIMCTRL (see 12.1.5).
5. Mathematical model 166

5.4. Transition from physical model to system of equations tNavigator-4.2
5.4 Transition from physical model to system of equations

The first equation 2.1 (c = 1) is replaced by the sum of all equations for all variables c, as
follows (we use for the summation xc,P = 1):
c
k
r,P

Nc = div P k (p P P gD) + qc (5.1)
t c P=O,W,G P c
Via Fully Implicit method (time approximation) and finite volume method (space approx-
imation) the problem come to the system of non-linear equations.
F(x) = F(p, N1 , . . . Nnc ) = 0,

where p = (pi ), Nc = (Nci ) - pressure and molar densities in grid blocks.
Newton method is used to solve this system of equations:

1
F(xm )

m+1 m
x =x F(xm ).
x
where x = (p, N1 , . . . Nnc ).

F(xm )/ x - matrix Rnc (K+J) Rnc (K+J) Rnc (K+J) , K - number of grid blocks, J -
number of wells.
Newton iteration is finished if:

|F(x)| < 1
(1 can be set via T OLNEW T in the keyword RUNCTRL (see 12.18.119)).
The limit of main variables variation (for which Newton iteration is finished):
||xm xm+1 || < 2
(2 can be set via T OLVARNEW T in the keyword RUNCTRL (see 12.18.119)).
At each step of Newton method the system with matrix F(xm )/ x is solved, the problem
come to the system of linear equations:
Ax = b,
A - Jacobian from Newton method. Matrix A can be considered as a matrix, that has ele-
ments - blocks with size (nc ) (nc ). Number nc depends on problem type (from 2 to 21).
The preconditioned biconjugate gradient method is used to solve the system of linear
equations with modified incomplete LU factorization (MILU(0)) as preconditioner.
5.4. Transition from physical model to system of equations 167

5.5. Model geometry tNavigator-4.2
At iterations of linear system we have Axm = bm .

Linear iteration is finished if
|bm |
< 3
|b0 |
(3 can be set via T OLLIN in the keyword RUNCTRL (see 12.18.119)).
5.5 Model geometry

tNavigator supports three types of grid cell geometry:
block-centered geometry: keywords DX (see 12.2.2) (or DXV (see 12.2.3)), DY (see
12.2.2) (or DYV (see 12.2.4)), DZ (see 12.2.2) (or DZV (see 12.2.5)) and TOPS (see
12.2.6).
For this type of geometry transmissibilities are calculated by default using OLDTRAN
(see 12.2.11) method;
corner-point geometry: keywords COORD (see 12.2.8) and ZCORN (see 12.2.9).
For this type of geometry transmissibilities are calculated by default using NEWTRAN
(see 12.2.12) method;
specifying grid via blocks tops keyword CORNERS (see 12.2.102).
In block-centered geometry grid blocks are rectangular with horizontal upper and lower
surfaces and vertical sides. In corner-point geometry grid blocks can have various shapes,
that helps to model the complex geological structures such as faults and pinchouts.
Additional options.
Grid can be included to the model using the following keywords:
IMPORT (see 12.2.97) The keyword imports cubes into a model. Cubes should be
specified in binary format.
VISGRID (see 12.2.98) The keyword is used to specify file of .EGRID format to
visualize grid. This keyword is used in models with unstructured grid.
Y-pillar grid format can be used in the model without modifications. This format
is converted to the keyword CORNERS (see 12.2.102). The example of Y-pillar grid
format is available in the description of the keyword CORNERS (see 12.2.102).
5.5. Model geometry 168

5.5. Model geometry tNavigator-4.2
5.5.1 Transmissibility calculation

Transmissibility can be specified via the keywords TRANX (see 12.2.51), TRANY (see
12.2.52), TRANZ (see 12.2.53).
If these keywords are not specified, transmissibility will be calculated via the formula
below.
1. in case OLDTRAN (see 12.2.11) run transmissibility value is calculated via the follow-
ing formula:
CDARCY T MULT Xi A DIPC
T RANXi = ,
B
where:
CDARCY - Darcys constant (METRIC: 0, 00852702, FIELD: 0, 00112712).
T MULT Xi - transmissibility multiplier fot i-th cell;

DXi DYi DZi RNT Gi +DX j DY j DZ j RNT G j
A= DXi +DX j - interface area between cell i and j
DHS
DIPC = - dip correction.
DHS+DV S
DXi +DX j 2

DHS = 2 ;
DV S = (DEPT Hi DEPT H j )2 ;
DXi +DX j
B= 2PERMXav ;
Wi = DXi ;
W j = DX j ;
The expression for the Y -transmissibility value is analogous to the above, with the
appropriate permutations of X , Y and Z . For Z -transmissibility NT Gi , NT G j and
DIPC are equal to 1.
2. in case NEWTRAN (see 12.2.12) run transmissibility value is calculated via the fol-
lowing formula:
CDARCY T MULT Xi
T RANXi = 1 1
,
Ti + T j
where:
(ADi )
Ti = PERMXi RNT Gi (D i Di )
;
1 (ADi )

Wi = RNT Gi (D i Di )
;
1 (AD )

Wj = RNT G j (D j Dj j ) .
5.5.1. Transmissibility calculation 169

5.6. LGR Local Grid Refinement tNavigator-4.2
(A Di ) is scalar production. For Z -transmissibility RNT Gi is equal to 1.
The keyword PERMAVE (see 12.2.36) sets value of parameter p in formula for calcula-
tion permeability averages for transmissibility:
!1
Wi PERMXip +W j PERMX jp p
PERMXav = .
Wi +W j
5.6 LGR Local Grid Refinement

In tNavigator local grid refinements can be specified.
The following keywords are supported:
LGR (see 12.1.81) (RUNSPEC section) set options and dimensions for local grid
refinement.
LGRCOPY (see 12.1.109) (RUNSPEC section) this option allows blocks of refined
grid to inherit formation properties from parent grid host blocks.
CARFIN (see 12.2.87) (GRID section) specifies a Cartesian local grid refinement
(LGR). CARFIN (see 12.2.87) specifies a cell or a box of cells identified by its global
grid coordinates I1-I2, J1-J2, K1-K2, to be replaced by refined cells. CARFIN (see
12.2.87) can be followed by keywords that describe properties in LGR, if they are
different from the properties in parent grid. These keywords should be terminated with
the keyword ENDFIN (see 12.2.89), which terminates data for a local grid refinement.
REFINE (see 12.2.88) initiates data input for a named local grid (LGR). The keyword
should be followed by name of local grid refinement the data for which is entered. The
data should be terminated with the keyword ENDFIN (see 12.2.89), which terminates
data for a local grid refinement. REFINE can be used in GRID, EDIT, PROPS, REGIONS,
SOLUTION and SCHEDULE section.
ENDFIN (see 12.2.89) terminates data for a local grid refinement.
NXFIN / NYFIN / NZFIN (see 12.2.90) (GRID section) These keywords can be used
to specify number of local cells in each global cell of an LGR (NXFIN in X direction,
NYFIN in Y direction, NZFIN in Z direction).
HXFIN / HYFIN / HZFIN (see 12.2.91) (GRID section) These keywords can be used
to specify the size ratios of each cell in a local grid refinement (LGR) (HXFIN in X
direction, HYFIN in Y direction, HZFIN in Z direction).
WELSPECL (see 12.18.4) (SCHEDULE section) introduces a new well, defining

information on its name and coordinates in local grids (LGR). WELSPECL must be
used in place of WELSPECS (see 12.18.3) to set the general specification data for
wells in local refined grids.
5.6. LGR Local Grid Refinement 170

5.7. Well Approximation tNavigator-4.2
COMPDATL (see 12.18.7) (SCHEDULE section) defines well completions in local

grids (LGR).
COMPDATL (see 12.18.7) must be used in place of COMPDAT (see 12.18.6) to
specify the connection data for wells in local refined grids.
COMPLMPL (see 12.18.23) (SCHEDULE section) lumps connections together into

completions to provide realization of simultaneous actions for wells in local grids
(LGR).
COMPLMPL (see 12.18.23) must be used in place of COMPLUMP (see 12.18.22)
to lump connections together into completions to provide realization of simultaneous
actions for wells in local refined grids.
WPIMULTL (see 12.18.29) (SCHEDULE section) multiplies well connection trans-

missibility factors by specified value for wells in local grids (LGR).
WPIMULTL (see 12.18.29) must be used in place of WPIMULT (see 12.18.28) to
multiply well connection transmissibility factors by specified value for wells in local
refined grids.
WFRACL (see 12.18.123) (SCHEDULE section) specifies the hydraulic fracture for
wells in local refined grids (LGR). WFRACL (see 12.18.123) must be used in place
of WFRAC (see 12.18.122) to specify the hydraulic fracture for wells in local refined
grids.
WFRACPL (see 12.18.125) (SCHEDULE section) specifies the hydraulic fracture for
wells in local refined grids (LGR) in graphical interface. WFRACPL (see 12.18.125)
must be used in place of WFRACP (see 12.18.124) to specify the hydraulic fracture for
wells in local refined grids in graphical interface.
COMPFRACL (see 12.18.127) (SCHEDULE section) specifies the hydraulic fracture

for connection in the grid layer for wells in local refined grids (LGR). COMPFRACL
(see 12.18.127) must be used in place of COMPFRAC (see 12.18.126) to specify the
hydraulic fracture for connection in the grid layer for wells in local refined grids.
5.7 Well Approximation

After discretization of equations for each grid block penetrated by the well the relationship
between the flow rate of each phase, pressure in the well bore and grid block pressure
should be established. This relationship is called Inflow performance relationship". This
relationship is used to calculate bottom hole pressure if user specifies rate control for injection
or production well or to calculate rate if user specifies bottom hole pressure control for a
well (WCONPROD (see 12.18.34), WCONINJE (see 12.18.36)).
5.7. Well Approximation 171

5.7.1 Well Inflow Performance

The term connection" denotes the flow path between the well bore and a single reservoir grid
block. While calculating inflow performance relationship for each connection the following
assumptions are made:
The well is assumed to penetrate the full thickness of the block, through its center,
perpendicularly to two of its faces.
For any calculation time step density of fluid within the well bore does not vary with
depth.
Friction effects in the well bore are neglected.
Capillary pressure is neglected when calculating inflow performance relationship; oil

phase pressure is used.
After discretization of equation (2.106) we get the following inflow performance relationship
for each well connection l with coordinates (i, j, k), written in terms of the volumetric phase
flow rate (P = {W, O, G}, i.e. Water, Oil, Gas):
QlP (pl , N l ,t) = T l (t) MP (pl , SW

l l
, SG )(pl plcon (t)) (5.2)
where
QlP = QlP (pl , N l ,t) volumetric flow rate of phase P through connection l in reservoir
conditions;
T l (t) connection productivity index, defined below, see section 5.7.2;
MP = MP (pl , SW
l , Sl ) the total phase mobility at connection l , defined below, see
G
section 5.7.5;
pl , SW
l , Sl nodal pressure and saturations in the grid block, containing connection;
G
Nc component molar densities in block l ;
plcon (t) the connection l pressure, see section 5.7.6;
5.7.2 Connection transmissibility calculation (CF and Kh)

Connection productivity index T l (t) may be defined by user, COMPDAT (see 12.18.6).
Otherwise it is calculated according to formula
l
2Kmult (t)c (Kh)l
T l (t) = . (5.3)
(ln(rol /rwl ) + sl )
Here

l
Kmult (t) KH multiplier for connection l , COMPDAT (see 12.18.6));
5.7.1. Well Inflow Performance 172

c the unit conversion factor, see section 10;
(Kh)l may be explicitly defined by user, COMPDAT (see 12.18.6); otherwise it is

calculated as product of K l average permeability in plane perpendicular to well axis,
see section 5.7.3, and hl , the size of the grid block in the direction of perforation
penetration;
rol pressure equivalent radius, defined below, see section 5.7.4;
rwl = dwl /2 the radius of the well bore at the connection l ;
sl the skin factor at the connection l .
Note.
The well trajectories and all well parameters (Kh, CF, etc.) are calculated in local block
coordinates.
For each block, in each direction (X, Y, Z), a set of directing vectors is calculated. These
vectors connect centers of opposite faces (in corresponding directions). These vectors form a
basis. The trajectory part inside the block is represented in coordinates of the block. These
coordinates are used to calculate Connection factor (CF) and Kh ([18]).
First, these parameters are calculated along directions (Khx , Khy , Khz ; CFx , CFy , CFz ).
Then, depending on model type (E100, E300, MORE, hybrid model) the resulting value will
be equal either to the sum or the square root of sum of squares.
In models with MORE format and hybrid models:

Kh = Khx + Khy + Khz
CF = CFx +CFy +CFz
This logic is also used in Load well data from graphical interface.
models with E100, E300 format:

Inp
Kh = p(Khx )2 + (Khy )2 + (Khz )2
CF = (CFx )2 + (CFy )2 + (CFz )2
In tNavigator a special keyword ETUNe (see 14.1.16) is supported, this keyword can be
used for hybrid and MORE models, to set up CF calculation like in E100, E300 format. It
should be used after trajectories.
5.7.3 Average permeability calculation

Average permeability K l for diagonal permeability tensor is calculated as geometric average
of two orthogonal component of tensor. That is,
for Z -directed well K l could be calculated as K l = (kxl kyl )1/2
for X -directed well K l could be calculated as K l = (kyl kzl )1/2
5.7.3. Average permeability calculation 173

for Y -directed well K l could be calculated as K l = (kxl kzl )1/2
Here kxl , kyl , kzl are elements of permeability tensor corresponding to block l .
5.7.4 Pressure equivalent radius calculation

The pressure equivalent radius rol is defined as the distance from the well at which the
pressure, calculated using (5.2) is equal to the pressure of the block, containing the connec-
tion. In a Cartesian grid the Peacemans formula is used, which is applicable to rectangular
grid blocks in case of permeability anisotropy. As mentioned above, the well is assumed
to penetrate the full thickness of the block, through its center, perpendicularly to two of its
faces.
The pressure equivalent radius for the connection l is calculated as follows:
l 1/2 l 1/2 1/2
l 2 k2 l 2 k
D1 k l + D2 k1l
1 2
rol = 0.28 l 1/4 l 1/4 (5.4)
k2 k1
k1l
+ k2l
where
Dl1 and Dl2 are the sizes of the grid block, containing connection, in the dimensions
perpendicular to well penetration;
k1l and k2l are the permeabilities of the grid block, containing connection, in the
dimensions perpendicular to well penetration.
If the block sizes in two directions are equal D1 = D2 , and permeabilities are equal
k1 = k2 , equivalent radius for the connection l is calculated
rol = 0.198Dl1
. (for vertical well Dx = Dy , kx = ky , equivalent radius rol = 0.198Dlx .)
5.7.5 Mobility calculation

Mobility calculations are different for production well connections and injection well con-
nections. For production well connections, the mobility depends on the conditions in the grid
block containing the connection. For injection well connections we use downstream approxi-
mation as a standard practice to calculate phase mobility. It results in injection phase mobility
being equal to sum of all three phases mobilities.
For production wells phase mobility is calculated as:
l , Sl )
krP (SW
MP (pl , SW
l l
, SG )= G
(5.5)
P (pl )
5.7.4. Pressure equivalent radius calculation 174

For injection wells phase mobility is calculated as:

l l l l
krO (SW ) + krW (SW , SG ) + krG (SG ) , for injected phase

MP (pl , SW
l l
, SG )= O (pl ) W (pl ) G (pl ) (5.6)

0, for other two phases
where

l , Sl ) is phase relative permeability evaluated at grid block saturations;
krP = krP (SW G
P = P (pl ) is phase viscosity evaluated at grid block conditions;
5.7.6 Average well bore density and connection pressure calculation

Friction effects are usually small within the well bore at formation level, and they are
neglected. We assume Darcy flow. The average well bore density is assumed to be constant
at each calculation time step and equal to:
O,SC qlO + W,SC qW

l + l l l
G,SC (qG + RG,O (p )qO )
l
av = l l
(5.7)
BO (pav )qO + Bw (pav )qW + BG (pav )(qlG + (RG,O (pl ) RG,O (pav ))qlO )
l
where
P,SC is the density of phase P at standard conditions;
BP = BP (pav ) is the phase formation volume factor evaluated at well bore conditions;
pav is average well bore pressure;
qlP = qlP (pl , SW

l , Sl ,t) is the well phase volumetric flow rate into connection l at
G
standard conditions;
In this case connection pressure plcon (t) is calculated as
plcon (t) = pBH (t) + av (t)g(Dl DBH ) (5.8)
here
pBH (t) is bottom hole pressure of the well, user specified or calculated from (2.106),
WCONPROD (see 12.18.34), WCONINJE (see 12.18.36);
DBH is bottom hole depth;
g is gravity constant;
Dl is depth of connection l ,
average wellbore density av (t) is calculated according to (5.7).
5.7.6. Average well bore density and connection pressure calculation 175
5.7.7 Well potential calculations

Well potential is well flow rate (production or injection rate) in the absence of any rate
constraints and at the current grid block conditions. Well potential is calculated with the
following constraints: BHP limit, THP limit (VFP tables are used) and drawdown limit (if it
is specified in 4-th parameter of WELDRAW (see 12.18.104)).
Field (or group) potential is a sum of all wells potentials (or all wells in the group).
Wells potentials are used in the following cases:
Group control. Wells potentials values are used as guide rates for wells, if their guide
rates are not specified via WGRUPCON (see 12.18.80). Well (and group) guide rates
can be specified according to their potentials (GUIDERAT (see 12.18.73)).
PRIORITY (see 12.18.78) prioritization group control, one can set well priorities
according to their potentials;
DRILPRI (see 12.18.200) prioritized drilling queue, one can set well drilling priorities
according to their potentials.
5.7.7. Well potential calculations 176

5.8. Modified well model tNavigator-4.2
5.8 Modified well model

Lets consider modified well model. Modifications help to describe hydraulic fracture simu-
lation.
5.8.1 Well model with generalized connections

For each connection located in grid block l , the following data is specified:
Numbers of grid blocks from which the connection produces (or injects):
l0 , l1 , . . . , lml
where l0 = l .
Resistance (connection effective multipliers) between the connection and corresponding

blocks (from which this connection produces or injects):
0l , 1l , . . . , ml l
where 0 = 1.
Threshold pressures. If these values are exceeded the flow from corresponding blocks
to connection starts (or the flow from connection into corresponding grid blocks):
pl0 , pl1 , . . . , plml
where p0 = 0.
For each grid block which is connected to the well connection we assume:
Pressure in connection is calculating via the same formulae
Connection productivity index between blocks l = l0 and li is calculated via formula

without the skin factor but with the multiplier il :
w,li w,li hw,li
w,li l 2Kmult c K
= i
b
w,li w,li
= il w,li , (5.9)
log(r0 /rw )
The inflow performance relationship for the well connection l from the grid block ll,i
(when pli > pw,l ) is specified with the replacement of the multiplier (pli pw,l ) (if
li 6= 0) by (pli pw,l , plli ), where

x y if x > y
(x, y) = x + y if x < y
0 else

5.8. Modified well model 177

The injection from the connection l to the block ll,i (when pli < pw,l ) is specified with
the replacement of multiplier (pli pw,l ) (if li 6= 0) by (pli pw,l , plli ).
Thus, the total inflow (outflow) of the component c in (from) the connection l is:
n0P
!
qlc = il w,li (pli pw,l , plli ) xc,P(pli , N li , T li ) P(pli , N li , T li ) MP(pli , N li , T li )
i : pli >pw,l P=1
n0P
!
qw
wc il w,li (pli pw,l , plli ) avg (pl , qw , T l ) MP(pli , N li , T li )
qtot P=1
i : pli <pw,l
5.8.2 Hydraulic fracture data

For the hydraulic fracture simulation the following parameters should be specified:
well name and date;
proppant properties (dependence between proppant permeability and the pressure)
(number of proppants NPROPANTS (see 12.8.1), proppant names PROPANT-
NAMES (see 12.8.2), the table of relation between pressure and proppant permeability
PROPANTTABLE (see 12.8.3)). If proppant name is not defined there is infinite
permeability along the fracture (pipe);
azimuth angle of hydraulic fracture;
half of fracture length;
fracture width;
fracture height (numbers of first and last connection);
zenith angle;
function f (s) dependence between permeability and phase or time dependence (see
5.8.7); (the number of tabular functions is specified via the keyword NFLOWFTB
(see 12.8.5), tabular function names FLOWFNAMES (see 12.8.6)), function, linear of
exponential, coefficients FLOWFUNC (see 12.8.4), tabular function FLOWFNAMES
(see 12.8.6).
If function is not specified there is no phase flow or time dependence.
hydraulic fracture could be specified via the keywords WFRAC (see 12.18.122),
WFRACP (see 12.18.124), COMPFRAC (see 12.18.126) (LGR case WFRACL
(see 12.18.123), WFRACPL (see 12.18.125), COMPFRACL (see 12.18.127)).
For MORE format models and hybrid models (section 11.3) the keywords WFRA
(see 14.6.25) and WFRP (see 14.6.26) can be used (WFRP (see 14.6.26) is an ana-
logue of WFRACP (see 12.18.124)).
Fracture passes through the inactive blocks until it reaches its half-length. Thus, the
flow through inactive blocks is possible.
5.8.2. Hydraulic fracture data 178

if fractures should be opened automatically if a specified condition is satisfied for

the block with connection (for example to create fractures for injectors when block
pressure is greater than a specified value) then one can use the keyword ACTIONC
(see 12.18.140).
Fracture geometry (half-lenght, width, angle) can be specified directly or can be calculated
by tNavigator using injected proppant volume (25-th parameter of the keyword WFRACP
(see 12.18.124) (or 26-th parameter of WFRACPL (see 12.18.125))).
In case if injected proppant volume is specified, tNavigator calculates fracture geometry

(the formula is taken based on the article [10]):
s
k
w = C f DV (5.10)
hk f
kf w
CfD = (5.11)
kx f
where:
C f D number in tNavigator 1.6 (at this value optimal configuration of fracture is specified
based on the article [10])),
V injected proppant volume,
h fracture height (from first to last specified connection (12 and 13 parameters of the
keyword WFRACP (see 12.18.124) are ignored if they are not zero)); if first and last fracture
connections are defaulted, then first and last fracture connections are taken,
k f fracture permeability (from the table of permeability dependence on pressure for prop-
pant PROPANTTABLE (see 12.8.3)),
w fracture width,
k formation permeability,
x f fracture half-length;
to calculate the geometry of the fracture width should be specified or fracture per-
meability (permeability dependence on pressure for proppant PROPANTTABLE
(see 12.8.3));
azimuth angle is calculated as orthogonal to the minimum permeability;
fracture left half-length and right half-length are equal;
if fracture width is specified it is used to calculate half-length via equation 5.11;
if fracture width is 0, then it is calculated via equation 5.10. Then fracture half-length
is calculated via 5.11;
if calculated width beyond the boundaries of the interval [0.01, 0.2], then the boundary
value will be taken - 0.01m or 0.2m (respectively, less than the calculated width of
0.01 or greater than 0.2).
5.8.2. Hydraulic fracture data 179

5.8.3 Hydraulic fractures

To calculate the flow in the reservoir after the hydraulic fracture the trajectory of hydraulic
fracture should be specified. There are the following ways:
Manually input of additional links between several well connections and grid blocks
(because of hydraulic fracture).
Automatic creation of links between the given connection and all grid blocks in the
parallelepiped (specified by azimuth angle, half of fracture length, fracture width and
height).
In mathematical model we should describe:
links between connections and grid blocks (because of hydraulic fracture);
flow along hydraulic fracture;
total inflow to hydraulic fracture.
5.8.4 Flow rate along the fracture

Let for every connection l , linked (because of hydraulic fracture) with block i (index j
include only blocks with numbers between blocks l and i):
Ml
il = (5.12)
l
1
Kj
j=i
where K j permeability coefficient along the fracture in block j . These formulae are
analogues to the calculation of grid blocks transmissibility coefficient and provide:
zero value il = 0, if permeability coefficient K j of at least one fracture part between

parts l and i is zero;
accumulated resistance to flow between l and i because of length and permeability

of path between them.
To simulate the dependence between hydraulic fracture and permeability, proppant

washout, fracture plugging and pressure K j can depend on:
fracture area and proppant properties;
pressure in the block, through which the fracture goes;
phase flow through blocks with fracture;
time.
5.8.3. Hydraulic fractures 180

-
X PERMZ
?
Z ?
PERMX
'$
#
?
PERMX PERMX
- =
"!
&%
d -
h
w
Figure 9: Calculation of equivalent inflow to the fracture
5.8.5 Calculation of the inflow to the fracture from the grid block
Let us consider the following scheme. The fracture in the block j is replaced by the virtual
connection with the following conditions:
perimeter of well bore cross-section is equal to fracture perimeter (that provides the
formula to calculate well diameter);
length of perforated interval is equal to the well bore length in the block;
the inflow to the well connection is calculated using block permeability in the direction,
which is orthogonal to fracture border with maximal area.
Via this data we can calculate permeability multiplier of this virtual connection ( w, j ), and
then calculate the inflow via common formula.
On the picture 9 there is a fracture which goes along Y -axis, height h and width
w (less then h). Inflow to this fracture is equal to the inflow to the well with diameter
d = 2(w + h)/ , Y -orientation and which is situated in the grid block. X and Z permeability
of this block is equal to X permeability of the block with fracture. So we obtain
w, j 2c K w, j hw, j
= w, j w, j
, rww, j = (w + h)/,
log(r0 /rw )
p
w, j
r0 = 0.14 DX2 + DZ2 , K w, j = PERMX, hw, j = DY
where DX, DY, DZ geometric sizes of block through which the fracture goes.
5.8.5. Calculation of the inflow to the fracture from the grid block 181
5.8.6 Total inflow from the hydraulic fracture to the well connection
li stands for numbers of grid blocks which are connected to the well connection l . Then
total inflow (outflow) of component c to the well connection l from hydraulic fracture:
0 nP
!
qlc = il w,li (pli pw,l , pl ) xc,P(pli , N li , T li ) P(pli , N li , T li ) MP(pli , N li , T li )
i6=l : pli >pw,l P=1
n0P
!
qw
wc il w,li (pli pw,l , pl ) avg (pli , qw , T li ) MP(pli , N li , T li )
qtot P=1
i6=l : pli <pw,l
This value should be added to the common inflow to the connection (or to the inflow which
is calculated using behind-the-casing flow).
5.8.7 Description of simulation of large amount of hydraulic fractures

If fracture height and length are big numbers (see the description of fracture in the section
5.8.2) then the model of fracture as linked blocks is not effective because of complicated
calculations. So we consider the hydraulic fracture the following way: there is a virtual
connection in each block through which the fracture goes. For this virtual connection we
describe inflow formula and formula of its transportation to the well bore. An advantage of
this method is simplification of calculations, and a disadvantage its impossible to divide
an inflow to the fracture among well connections (i.e. inflow is calculated as inflow from
fracture to well, not to specific well connection).
The fracture is specified according to the sections 5.8.2, 5.8.3. l1 , . . . , lL stand for the
blocks through which the fracture goes, average fracture perimeter in the block li li ,
average fracture length in the block li Lli , area of fracture cross-section in the block li
Sli , the distance from block li to the well bore Dli . For simplification of designation let
consider fracture plane as vertical plane and quasi orthogonal to OX , see the picture pic. 9.
To other location of fracture calculations are similar. To calculate inflow from block li to the
fracture we use the formula from the section 5.8.5:
2c PERMX Lli
w,li = p ,
log 0.28 DX2 + DZ2 /Sli
To calculate flow along the fracture we should approximate an expression (5.12 efficiency
of flow along fracture) (in fact it is the multiplier to w,li ). Proppant properties for the fracture
should be specified:
proppant permeability (mD, using PROPANTTABLE (see 12.8.3)) K(p) is the func-
tion of pressure in the block; if this function is not specified then K = ;
dependence between permeability and flow of phase or liquid; This dependence is

specified flow function f of dimensionless flow s (total phase flow divided by total
pore volume of this block):
5.8.6. Total inflow from the hydraulic fracture to the well connection 182
1. f (0) = 1;
2. f (s) 0 for all s.
There are the following types of this function:
1. Exponential: f (s) = k + (1 k) exp(a s), Parameters: k 0, a > 0 are spec-
ified via FLOWFUNC (see 12.8.4) (function type EXP).
2. Linear: f (s) = max{1 + (k 1) a s, 0}, Parameters: k 0, a > 0 are specified
via FLOWFUNC (see 12.8.4) (function type LIN).
3. Tabular: the table (s, f (s)) is specified via keyword FLOWFTAB (see 12.8.7) (the
number of tabular functions is specified via the keyword NFLOWFTB (see 12.8.5),
tabular function names FLOWFNAMES (see 12.8.6)).
If function is not specified, then f (s) = 1.
Resultant effective permeability of proppant in the block li with the area of cross-section Sli
(m2 ) is equal to
Kli (pli , s) = K(pli )C Sli f (s).
Function Kli (pli , s) is dimensionless.
K(pli ) function for propant (permeability (mDarcy) dependence on pressure) (PROPANT-
TABLE (see 12.8.3)).
C = m14 transition coefficient.
Flow efficiency along the fracture from block li to the well li (see (5.12)) is such that:
1. li is the function only of Dli if K(p) = , li = 1 if K(p) = and Dli = 0, this
corresponds to block drainage (the well goes through this block);
2. li = 0 if K(p) = 0;
3. li = 0 if s = .
Lets consider the following function:
Kli (p, s) 1
li (pli , s) = . (5.13)
1 + Kli (p, s) 1 + Dli /Lli
li (pli , s) is dimensionless.
Since the rate of virtual perforations doesnt correspond to specific connection, then we
take bottom hole pressure pw for the pressure in the well and use the function with
threshold value pbw , which is the same for all fracture blocks (default value is 0). So we
have:
0 nP
!
qlc = li w,li (pli pw , pbw ) xc,P(pli , N li , T li ) P(pli , N li , T li ) MP(pli , N li , T li )
i6=l : pli >pw P=1
n0P
!
qw
wc li w,li (pli pw , pbw ) avg (pli , qw , T li ) MP(pli , N li , T li )
qtot P=1
i6=l : pli <pw
5.8.7. Description of simulation of large amount of hydraulic fractures 183

This value should be added to the common inflow to the well (or to the inflow which is
calculated using behind-the-casing flow).
To calculate li = li (pli , s) we take total flow s and pressure pli in block li at previous
time step (to minimize additional nonlinearity). Pore volume of block (during the calculation
of dimensionless flow s) is calculated once when hydraulic fracture is created.
5.8.8 Fracture keywords

FLOWFUNC (see 12.8.4) PROPS Specifies coefficients of linear or exponential
flow function (the dependence between per-
meability and flow (or time)). I.e. this func-
tion sets the duration of the effect of hydraulic
fracture
FLOWFTAB (see 12.8.7) PROPS Specifies tabular flow functions
FLOWFNAMES (see 12.8.6) PROPS Specifies tabular flow functions names
NFLOWFTB (see 12.8.5) PROPS Specifies number of tabular flow functions
NPROPANTS (see 12.8.1) PROPS Specifies number of proppant types
PROPANTNAMES (see 12.8.2) PROPS Specifies proppant names
PROPANTTABLE (see 12.8.3) PROPS Specifies the table of relation between pressure
and proppant permeability
5.8.8. Fracture keywords 184


WFRAC (see 12.18.122) SCHEDULE Specifies the hydraulic fracture
WFRACL (see 12.18.123) SCHEDULE Specifies the hydraulic fracture in LGR-case
COMPFRAC (see 12.18.126) SCHEDULE Specifies the hydraulic fracture for one layer
(fracture height is equal to the block height, in
which fracture goes in this layer)
COMPFRACL (see 12.18.127) SCHEDULE Specifies the hydraulic fracture for one layer
(fracture height is equal to the block height, in
which fracture goes in this layer) in LGR case
WFRACP (see 12.18.124) SCHEDULE Specifies the hydraulic fracture; using this key-
word fracture geometry can be calculated by
tNavigator from injected proppant volume
WFRACPL (see 12.18.125) SCHEDULE Specifies the hydraulic fracture; using this
keyword fracture geometry can be calculated
by tNavigator from injected proppant volume;
LGR case
ACTIONC (see 12.18.140) SCHEDULE Sets the automatic opening of fractures at an
event in a block (for example, the creation of
fractures on the injection wells at excess pres-
sure in the block a certain value)
WFRP (see 14.6.26) RECU Specifies the hydraulic fracture for MORE for-
mat models and hybrid models.
WFRA (see 14.6.25) RECU Specifies the hydraulic fracture for MORE for-
mat models and hybrid models.
Keywords to specify hydraulic fractures: WFRAC (see 12.18.122), WFRACP

(see 12.18.124), COMPFRAC (see 12.18.126). An in local grid refinements LGR: WFR-
ACL (see 12.18.123), WFRACPL (see 12.18.125), COMPFRACL (see 12.18.127). Fracture,
specified via all these keywords passes through the inactive blocks until it reaches its half-
length. Thus, the flow through inactive blocks is possible.
The keyword with the greatest functionality is WFRACP (see 12.18.124) (WFRACPL
(see 12.18.125)).
WFRAC (see 12.18.122) and COMPFRAC (see 12.18.126) are its are its reductions. The
differences between COMPFRAC (see 12.18.126) and WFRAC (see 12.18.122):
the fracture is created only in the layer k , fracture height is equal to the block height,
in which fracture goes in this layer;
fracture length and width are calculated as the projection of layer k to the plane OXY,
i.e. Z coordinate is not taken into consideration;
inflow to the hydraulic fracture belongs to inflow to connection i, j , k .
5.8.8. Fracture keywords 185

5.8.9 Simulation of plugging of well bottom zone

w,l
To simulate plugging of well bottom zone the effectivity multiplier Kmult is usually used
WPIMULT (see 12.18.28). We add the function which depends of dimensionless flow s (see
the description in the section 5.8.7):
w,l 2 f pw,l (s)Kmult

w,l
c K w,l hw,l
= , (5.14)
log(r0w,l /rww,l ) + sw,l
where the type of f pw,l (s) is specified via FLOWFUNC (see 12.8.4) (function type EXP or
LIN), FLOWFTAB (see 12.8.7), and for the well connection it is specified via WPIFUNC
(see 12.18.128), which is analogous to WPIMULT (see 12.18.28).
After an operation of cleaning of well bottom zone one should specify WPIMULT (see
12.18.28) again, this will set to zero value accumulated dimensionless flow. Specification of
other parameters of the function f pw,l (s) or specification of new type of function will also set
to zero accumulated dimensionless flow.
In classical way of hydraulic fracture simulation via skin-factor sw,l in (5.14) one can
also specify its dependence on dimensionless flow s (see the section 5.8.7):
w,l 2 f pw,l (s)Kmult

w,l
c K w,l hw,l
= , (5.15)
log(r0w,l /rww,l ) + fsw,l (s) sw,l
where fsw,l (s) type is specified via FLOWFUNC (see 12.8.4) (function type EXP or
LIN), FLOWFTAB (see 12.8.7), and for the well connection is specified via WSKFUNC
(see 12.18.129), analogous to WPIFUNC (see 12.18.128).
After an operation of cleaning of well bottom zone or creation a new fracture one should
specify the value of skin-factor sw,l in COMPDAT (see 12.18.6) again. This will set to
zero value accumulated dimensionless flow. Specification of other parameters of the func-
tion fsw,l (s) or specification of new type of function will also set to zero accumulated
dimensionless flow.
5.8.10 Simulation of well bottom zone dynamics: processing acids, surfactants

After processing acids, surfactants etc. around the well there will be a zone with radius rbhz
and permeability Kbhz . Modified formula of inflow (5.15), included this zone, will be the
following:
w,l
w,l

w,l
K w,l Kbhz
= 2 f pw,l (s)Kmult c hw,l w,l w,l
,
K w,l log(rbhz /rw ) + Kbhz log(r0w,l /rbhz
w,l
) + fsw,l (s) sw,l
(5.16)
w,l w,l
where parameters rbhz , Kbhz for the well connection are set via WBHZONE (see 12.18.130).
5.8.9. Simulation of plugging of well bottom zone 186

5.9. ASP model description tNavigator-4.2
5.8.11 Well bottom zone keywords

FLOWFUNC (see 12.8.4) PROPS Specifies coefficients of linear or exponential
flow function (the dependence between perme-
ability and flow (or time)). I.e. this function
sets the duration of the effect of well bottom-
hole zone treatment
FLOWFTAB (see 12.8.7) PROPS Specifies tabular flow functions
FLOWFNAMES (see 12.8.6) PROPS Specifies tabular flow functions names
NFLOWFTB (see 12.8.5) PROPS Specifies number of tabular flow functions
WBHZONE (see 12.18.130) SCHEDULE Specifies the well bottomhole zone treatment
5.9 ASP model description

The model of ASP injection (Alkaline, Surfactant, Polymer) (water salinity can optionally be
taken into account).
In the black-oil and compositional model (excluding CO2 dissolution) the mass conser-
vation equation for each component (4.81) is:

( Nw ) = div (W UW ) + Qw
t
(because there is no solid phase in these models, and xw,P = 1 only for P = W ). Here Qw is
mass water inflow from all the sources (wells, aquifers).
We denote
Csalt the concentration of dissolved salt in water (kg/kg);
Calkl the concentration of dissolved alkaline in water (kg/kg);
Csur f the concentration of dissolved surfactant in water (kg/kg);
C poly the concentration of dissolved polymer in water (kg/kg).
The option activation is done via the following keywords in the RUNSPEC (see 12.1.1)
section:
for salt: BRINE (see 12.1.58)
for alkaline: ALKALINE (see 12.1.49)
for surfactant: SURFACT (see 12.1.46)
for polymer: POLYMER (see 12.1.48)
Initial values are specified via:
5.8.11. Well bottom zone keywords 187

Agent Equilibrium initialization Non-equilibrium initialization

Salts SALTVD (see 12.15.42) SALT (see 12.15.41)
Alkaline 0 0
Surfactant 0 SURF (see 12.15.44)
Polymer 0 SPOLY (see 12.15.45)
In all initial conditions concentrations are in units kg/sm3 , so the units kg/kg are obtained
when there is a division of these values by water density at surface conditions W sc (specified
via DENSITY (see 12.5.23)).

The system of conservation equations:
asp
krW asp asp
UW = c k asp (p + PcW W gd) (5.17)
W

( Nw Csalt ) = div (W UW Csalt ) + Qsalt ,(5.18)
t
ads

( Nw Calkl ) + (1 )rock Calkl = div (W UW Calkl ) + Qalkl ,(5.19)
t t

(1 )rock Aalkl ads

Nw Csur f + C
sur f sur f = div W UW C sur f + Qsur f (5.20)
,
t t

(1 Sd pv ) Nw C poly + (1 )rock Aalkl C ads
poly poly = div U
W W B visc C
poly poly + Q poly (5.21)
,
t t
Where:
asp
krW water relative permeability with ASP in it (see below),
asp
W water viscosity with ASP in it ASP (see below),
asp
Bvisc
poly polymer viscosity multiplier (dimensionless) (see below for W ),
asp
PcW water-oil capillary pressure with ASP in the water (see below),
asp
W water mass density with ASP in it (see below),
ads concentration of adsorbed alkaline (kg/kg), as a function of C 3
Calkl alkl (kg/sm ) in
ALKADS (see 12.8.26).
ads concentration of adsorbed surfactant (kg/kg), as a function of C 3
Csur f sur f (kg/sm )
in SURFADS (see 12.8.8).
Cads
poly concentration of adsorbed polymer (kg/kg), as a function of adsorbed Csur f
(kg/sm3 ) in PLYADS (see 12.8.17).
Aalkl 3

sur f surfactant adsorption multiplier (dimensionless), as a function Calkl (kg/sm )
in ALSURFAD (see 12.8.24).
Aalkl 3

poly polymer adsorption multiplier (dimensionless), as a function Calkl (kg/sm ) in
ALPOLADS (see 12.8.25).
5.9. ASP model description 188

rock rock molar density. In black-oil models (E100) the rock mass density is used,
in compositional models (E300) the rock mass density divided by water molecular
weight MWW is used. Rock mass density is specified via 3-rd parameter of the keyword
PLYROCK (see 12.8.20) (if there are polymers then the 2-nd parameter of SURFROCK
(see 12.8.12) is ignored), or via the 2-nd parameter of SURFROCK (see 12.8.12).
Sd pv dead pore space, specified via 1-st parameter of PLYROCK (see 12.8.20).
Qsalt salt sources (wells, aquifers). The keywords WSALT (see 12.18.152), 12-th
parameter of AQUCT (see 12.16.8), 8-th parameter of AQUFETP (see 12.16.6), 3-rd
parameter of AQUFLUX (see 12.16.2), 7-th parameter of AQUCHWAT (see 12.16.3).
In all data concentrations are in units kg/sm3 , so the units kg/kg are obtained when
sc (specified
there is a division of these values by water density at surface conditions W
via DENSITY (see 12.5.23)).
Qalkl alkaline sources (wells). Keyword WALKALIN (see 12.18.150). In all data
concentrations are in units kg/sm3 , so the units kg/kg are obtained when there is
sc (specified via
a division of these values by water density at surface conditions W
DENSITY (see 12.5.23)).
Qsur f surfactant sources (wells). Keyword WSURFACT (see 12.18.149). In all data
sc (specified via
Q poly polymer sources (wells). Keyword WPOLYMER (see 12.18.151). In all data
sc (specified via
5.9.1 Water relative permeability calculations

asp
Lets consider the calculation of krW .
Capillary number Kc :

kkpk 20
Kc = min log10 Cunit + 10 , 20
Aalkl
st (Calkl )sur f (Csur f )
where
sur f (Csur f ) surface tension (N/m), specified as function of Csur f (kg/sm3 ) in

SURFST (see 12.8.9);
Aalkl 3
st (Calkl ) surface tension multiplier, specified as function of Csur f (kg/sm ) in
ALSURFST (see 12.8.23);
Cunit = 9.869234E 11 multiplier, that depends on units system.
5.9.1. Water relative permeability calculations 189

Denote (see the tables 1 and 3) with

imm (S ), kimm (S ) user data for immiscible conditions, that are specified via
krW W rOW W
number of table SATNUM (see 12.4.3) and scaling arrays SWL (see 12.6.27), SWCR
(see 12.6.30), SWU (see 12.6.34), SOWCR (see 12.6.32), KRW (see 12.6.43), KRO
(see 12.6.42), KRORW (see 12.6.42);

mis (S ), kmis (S ) user data for miscible conditions, that are specified via number
krW W rOW W
of table SURFNUM (see 12.4.4) and scaling arrays SWL (see 12.6.27), SWU (see
12.6.34), KRW (see 12.6.43), KRO (see 12.6.42), KRORW (see 12.6.42);
The scaled relative permeabilities (calculated according to 4.35.2) we denote as

0imm (S ), k0imm (S ), k0mis (S ), k0mis (S )
krW W rOW W rW W rOW W
Then phase relative permeabilities in water-oil system if the surfactant is present are:
0 0imm 0mis
krW (SW ) = Fcapd (Kc )krW (SW ) + (1 Fcapd (Kc ))krW (SW )
0 0imm 0mis
krOW (SW ) = Fcapd (Kc )krOW (SW ) + (1 Fcapd (Kc ))krOW (SW )
where the function Fcapd (Kc ) is set in the keyword SURFCAPD (see 12.8.11) as the function
of capillary number Kc . This function should be equal 0 for immiscible conditions and 1
miscible conditions.
Functions krG (SG ), krOG (SG ) are always taken for immiscible conditions (from SATNUM
0 (S ),
(see 12.4.3)); using these functions the corresponding phase relative permeabilities krG G
0
krOG (SG ) are calculated according to the section 4.35.2.
Oil relative permeability krO in three-phase system is calculated from krW 0 (S ),
W
0 0 0
krOW (SW ), krG (SG ), krOG (SG ) according to the section 4.35.3.
5.9.2 Water viscosity calculations

asp
Lets consider the calculation of W and Bvisc
poly .
The keywords, that specify the data for these calculations, differ depending whether there
is a salt in the model (keyword BRINE (see 12.1.58)) or not.
5.9.3 Water viscosity calculations without salt

Lets denote as W (p) the "standard" viscosity, calculated from PVTW (see 12.5.5), and
pre f reference pressure, specified in PVTW (see 12.5.5).
Viscosity in the case with the surfactant:
sur f W (p)
W (p,Csur f ) = sur f (Csur f )
W (pre f )
where the function sur f of Csur f (kg/sm3 ) is specified in SURFVISC (see 12.8.10).
Lets denote
poly (C poly ) function (dimensionless), specified in PLYVISC (see 12.8.16);
5.9.2. Water viscosity calculations 190

Cmax 3

poly maximal polymer concentration (kg/sm ), specified in the 1-st parameter of
PLYMAX (see 12.8.18);
parameter, specified in PLMIXPAR (see 12.8.19),
Krr f parameter (residual resistance factor), specified via 2-nd parameter of PLYROCK
(see 12.8.20),
Cads,max
poly maximal adsorbed polymer concentration (kg/sm3 ), specified in 5-th pa-
rameter of PLYROCK (see 12.8.20).
asp asp
Then the water viscosity W = W (p,Csur f ,C poly ,Cads
poly ) (in case of surfactant and polymer
in it):
1 Cads,max
poly 1
asp =
W Cads,max
poly + (Krr f 1)Cads
poly
( poly (C poly ))
!
1 min{C poly /Cmax
poly , 1} min{C poly /Cmax
poly , 1}
sur f
+
(W (p,Csur f ))(1) ( poly (Cmax
poly ))
(1)
Polymer viscosity multiplier (dimensionless) Bvisc visc

poly = B poly (p,Csur f ,C poly )
!(1) 1
poly (Cmax
poly )
Bvisc max max
poly = min{C poly /C poly , 1} + (1 min{C poly /C poly , 1})

sur f

W (p,Csur f )
asp
Using this notation, the expression for the water viscosity W can be rewritten as
1 Cads,max
poly 1 1 1
asp = visc
W Cads,max + (Krr f 1)Cads ( poly (C poly )) ( poly (Cmax
poly ))
(1) B
poly
poly poly
5.9.4 Capillary pressure in water-oil system

asp
The calculation of PcW :
asp sur f (Csur f )
PcW = PcW
sur f (0)
where
PcW capillary pressure, calculated via "standard" method,
sur f (Csur f ) surface tension (N/m), specified as the function of Csur f (kg/sm3 ) in
SURFST (see 12.8.9).
5.9.5 Water mass density calculations

asp
Water mass density W depends only on Csalt and it is calculated from the keywords
PVTWSALT (see 12.7.14) and BDENSITY (see 12.7.9).
5.9.4. Capillary pressure in water-oil system 191

5.10. Drainage matrix calculation tNavigator-4.2
Injector Responding producers

Well Liquid Oil Well Liquid Oil
rm3 sm3 rm3 sm3
Reservoir 720.0 203.0 101 204.0 80.0
102 516.0 123.0
201 323.0 124.0 Reservoir 117.0
102 193.0 120.0
103 13.0 4.0
Table 5: Drainage table, grouped by Injectors
5.10 Drainage matrix calculation

Drainage matrix is a tool for numerical evaluation of injector-producer interactions and
crossflows due to streamlines.
5.10.1 Description of Drainage matrix

In GUI drainage matrix can be visualized as table, graph and matrix. There is a description
of the table form below. The table can be grouped by Producers or Injectors. Lets start with
the table, grouped by Injectors (table 5).
Columns:
Liquid (injector) liquid, injected by injector. In the table 5:
The well 201 injected 323.0 rm3 of liquid (in reservoir conditions).
Oil (injector) the volume of oil produced from the responding producers due to
the injection of this injector. In the table 5:
The value 124.0 sm3 is the volume of oil, produced due to the injection of well
201.
Liquid (responding producer) liquid volume, produced by this producer due to
injection of this injector. In the table 5:
The well 102 produced 193.0 rm3 (in reservoir conditions) due to injection of the
well 201.
Oil (responding producer) oil volume, produced by this producer due to injection
of this injector. In the table 5:
The value 120.0 sm3 is the volume of oil, produced by the well 102 due to
injection of the well 201.
If the reservoir is set as the injector, then the fluid produced will equal the fluid
produced from the reservoir without injectors influence. In the table 5:
5.10. Drainage matrix calculation 192

Total fluid production is 720.0 rm3 (in reservoir conditions) without injectors
influence.
Total oil production is 203.0 sm3 3 without injectors influence.
The well 101 produced 204.0 rm3 (in reservoir conditions) without injectors
influence.
The well 101 produced 80.0 sm3 of oil without injectors influence.
If the reservoir is set as the producer, then the liquid volume will equal the volume of
water that has been injected by the well but not influenced the producers production
volumes. In the table 5:
The well 201 injected 117.0 rm3 (in reservoir conditions), that not influenced the
producers production volumes.
Note, that the values in the left columns are equal to the sum of the values in the right
columns. In the table 5:
For the reservoir:
Liquid: 720.0 = 204.0 + 516.0

Oil: 203.0 = 80.0 + 123.0
For the well 201:
Liquid: 323.0 = 117.0 + 193.0 + 13.0

Oil: 124.0 = 120.0 + 4.0
You can also get a drainage table relative form: values in the right columns are represented
as percentages of the corresponding values in the left columns.
The table can be sorted by the column Oil (injector). In this case we have on the top
of the table the most effective injection wells, excluding economy, because the amount of
injected water is not taken into account. Most effective wells (economically) are those with
the lowest ratio of injected water to the produced oil, therefore it is necessary to consider the
second column. At the bottom of the table at this sorting there are the least effective wells.
To the right of them we can see the producers that are affected by shutting of ineffective
injectors.
Below there is a description of the Drainage table grouped be producers. The table 6
corresponds to the same drainage matrix as the table 5, but it has different grouping.
Columns:
Liquid (producer) fluid volume, produced by this producer. In the table 6:
The well 102 produced 709.0 rm3 (in reservoir conditions).
Oil (producer) oil volume, produced by this producer. In the table 6:
5.10.1. Description of Drainage matrix 193

Producer Injectors influence

Well Liquid Oil Well Liquid Oil
rm3 sm3 rm3 sm3
Reservoir 117.0 201 117.0
101 204.0 80.0 Reservoir 204.0 80.0
102 709.0 243.0 Reservoir 516.0 123.0
201 193.0 120.0
103 13.0 4.0 Reservoir 0.0 0.0
201 13.0 4.0
Table 6: Drainage table, grouped by Producers
The well 102 produced 243.0 sm3 of oil.
Liquid (Injectors influence) fluid volume, produced by this producer due to in-
jection of this injector. In the table 6:
The well 102 produced 193.0 rm3 (in reservoir conditions) due to injection of the
well 201.
Oil (Injectors influence) the volume of oil produced by this producer due to the
injection of this injector. In the table 6:
The value 120.0 sm3 is the volume of oil, produced by the well 102 due to the
injection of the well 201.
If the reservoir is set as the injector the fluid volume will equal the volume of fluid
produced without the injectors influence. In the table 6:
The well 102 produced 516.0 rm3 (in reservoir conditions) without the injectors
influence.
The well 102 produced 123.0 sm3 of oil 3 without the injectors influence.
If the reservoir is set as the producer, then the liquid volume will equal the volume of
water that has been injected by this well but not influenced the producers production
volumes. In the table 6:
The well 201 injected 117.0 rm3 (in reservoir conditions), that not influenced the
producers production volumes.
Note, that the values in the left columns are equal to the sum of the values in the right
columns. In the table 6:
For the reservoir:
Liquid: 117.0 = 117.0
5.10.1. Description of Drainage matrix 194

For the well 101:

Liquid: 204.0 = 204.0
Oil: 80.0 = 80.0
For the well 102:
Liquid: 709.0 = 516.0 + 193.0
Oil: 243.0 = 123.0 + 120.0
For the well 103:
Liquid: 13.0 = 13.0
Oil: 4.0 = 4.0
You can also get a drainage table relative form: values in the right columns are represented
as percentages of the corresponding values in the left columns.
The table can be sorted by the column Oil (producer). In this case we have on the top
of the table the most effective producers. At the right part of the table there are wells that
provide reservoir pressure support for the selected producer. The the bottom of the table there
are wells that can be candidates to switch for injection.
5.10.2 Parameters that affect drainage matrix

Drainage matrix calculations depends on several parameters:
Streamline density
Each streamline corresponds to the specified fluid volume, this value is its density.
The default streamline density is 5.0 rm3 for one streamline. At a reasonable density
decrease, the accuracy of their construction increases, but the calculation time also
increases. The best settings should be selected depending on the well rates: the smaller
well rate, the smaller the density of streamlines to obtain an accurate picture.
The wells to trace streamlines from (producers or injectors)
The streamlines can be traced from producers or injectors. The resulting pictures can be
different, while at tracing from producers it more accurately reflects the flow closer to
the producers and vice versa. This option should be selected on the basis of data to be
used: in the analysis of producers trace from producers, in the analysis of injectors
trace from injectors.
Phases that are taken into account in streamline calculations
In the settings you can specify a set of phases, which are used in streamline calculations.
It can be any combination of water, oil and gas. For waterflood it is recommended to
use the default (water and oil). For example, if you select only one of the phases the
streamline will stop if it enters the block with the saturation of this phase equal to the
residual saturation (minimal saturation).
5.10.2. Parameters that affect drainage matrix 195

5.11. Oil and gas in-place tNavigator-4.2
5.11 Oil and gas in-place

In tNavigator in the map tree Resources the following maps are available:
Oil in place (oip) (METRIC: sm3 , FIELD: stb);
Oil in place (Mass) (oipm) (METRIC: ton, FIELD: lb);
Mobile oil in place (moip) (METRIC: sm3 , FIELD: stb);
Mobile oil in place (Mass) (moipm) (METRIC: ton, FIELD: lb);
Gas in place (gip) (METRIC: sm3 , FIELD: stb);
Gas in place (Mass) (gipm) (METRIC: ton, FIELD: lb);
Mobile gas in place (mgip) (METRIC: sm3 , FIELD: stb).
These maps can be used in User Arithmetic in User Maps. Their names in brackets should
be entered in the Map Arithmetic Command Line.
If there is vaporized oil in gas additional maps will be visualized:
Free oil in place (METRIC: sm3 , FIELD: stb);
Mobile Free oil in place (METRIC: sm3 , FIELD: stb);
Vaporized oil in place (METRIC: sm3 , FIELD: stb);
Mobile Vaporized oil in place (METRIC: sm3 , FIELD: stb).
If there is dissolved gas in oil additional maps will be visualized:
Free gas in place (METRIC: sm3 , FIELD: stb);
Mobile Free gas in place (METRIC: sm3 , FIELD: stb);
Dissolved gas in place (METRIC: sm3 , FIELD: stb);
Mobile Dissolved gas in place (METRIC: sm3 , FIELD: stb).
These maps are calculated in each grid block via the formulas (description of all param-
eters is below):
If there is no vaporized oil in gas:
1. Oil in place oip = porv soil ibo;
2. Oil in place (Mass) oipm = rho oip = soil porv ibo rho;
5.11. Oil and gas in-place 196

3. Mobile oil in place

moip = IF((soil sowcr) >= 0, (soil sowcr) porv ibo, 0) (see the description of
the function IF (see 12.3.7));
4. Mobile oil in place (Mass) moipm = moip rho.
If there is vaporized oil in gas:
1. Oil in place oip = porv (soil ibo + sgas ibg rv);
2. Oil in place (Mass) oipm = rho oip = rho porv (soil ibo + sgas ibg rv);
3. Mobile oil in place moip = porv ((soil sowcr) ibo + (sgas sgcr) ibg rv) for the
case (soil sowcr) 0 and (sgas sgcr) 0.
If (soil sowcr) < 0 or (sgas sgcr) < 0, then resources are considered immobile and
corresponding part of the formula is set equal to zero (negative values dont sum in
this formula).
4. Mobile oil in place (Mass) moipm = moip rho;
5. Free oil in place porv soil ibo;
6. Mobile Free oil in place

IF((soil sowcr) 0, porv (soil sowcr) ibo, 0);
7. Vaporized oil in place porv sgas ibg rv;
8. Mobile Vaporized oil in place

IF((sgas sgcr) 0, porv (sgas sgcr) ibg rv, 0).
If there is no dissolved gas in oil:
1. Gas in place gip = porv sgas ibg;
2. Gas in place (Mass) gipm = sgas porv ibg rhg;
3. Mobile gas in place mgip = IF((sgas sgcr) 0, (sgas sgcr) porv ibg, 0).
If there is dissolved gas in oil:
1. Gas in place gip = porv (sgas ibg + soil ibo rs);
2. Gas in place (Mass) gipm = gip rhg = porv rhg (sgas ibg + soil ibo rs);
3. Mobile gas in place mgip = porv rhg ((sgas sgcr) ibg + (soil sowcr) ibo rs)
for the case (soil sowcr) 0 or (sgas sgcr) 0.
If (soil sowcr) < 0 or (sgas sgcr) < 0, then resources are considered immobile and
corresponding part of the formula is set equal to zero (negative values dont sum in
this formula).

4. Free gas in place porv sgas ibg;
5. Mobile Free gas in place

IF((sgas sgcr) 0, (sgas sgcr) porv ibg, 0);
6. Dissolved gas in place porv soil ibo rs;
7. Mobile Dissolved gas in place

IF((soil sowcr) 0, (soil sowcr) porv ibo rs, 0).
If the blocks oil saturation (soil ) is below the critical oil saturation (sowcr ), the oil is
considered immobile.
If the blocks gas saturation (sgas) is below the critical gas saturation (sgcr ), the gas is
considered immobile.
where:
soil - oil saturation in this grid block;
sowcr - residual oil saturation in the cell taking into account the permeabilities scaling;
sgas - gas saturation in this grid block;
sgcr - residual gas saturation in the cell taking into account the permeabilities scaling;
porv - pore volume of the grid block at current pressure. Its calculation depends of
rock properties specification, the keyword ROCK (see 12.5.16) (Eclipse or CROC,
REFE in MORE) or the keyword ROCKTAB (see 12.5.18) (Eclipse or KVSP in
MORE). If the keyword ROCK is used, then
porv = (1 +C (p PREF) +C C (p PREF) (p PREF)/2) V PORO NT G
where p - pressure, C and PREF are specified in the keyword ROCK (see 12.5.16), V
- geometric volume of the cell (is not equal to DX*DY*DZ for non-uniform rectangular
grid), PORO (see 12.2.24) are NTG (see 12.2.25) specified via the corresponding
keywords.
ibo - inverse value to the oil volume ratio at the current pressure and composition of
the cell;
rho - oil density at surface conditions is specified via the keyword DENSITY (see
12.5.23) (Eclipse or DENSITY/BASIC in MORE).
ibg - inverse value to the gas volume ratio at the current pressure and composition of
the cell;
rhg - gas density at surface conditions is specified via the keyword DENSITY (see
12.5.23) (Eclipse or DENSITY/BASIC in MORE).

5.11.1 Resources density and concentration

For 3D map one can choose 2D density map via the formula:
k dz(i, j, k)
density(map, i, j) = ( map(i, j, k))
k k Vb (i, j, k)
where
map(i, j, k) - value of map in the block (i, j, k);
k - sum of the vertical column for (i, j). If Cut is enable then the sum will include
blocks for which this cut is true;
dz(i, j, k) - value DZ in the block (i, j, k);
Vb (i, j, k) - volume of the block (i, j, k) at current pressure.
If we choose the map moipm, end set the Cut an expression k > 26&k < 85, then
density of mass mobile oil resources for layers from 27 to 84.
tNavigator formula of mass mobile oil resources has the following features:
formula of vertical averaging is adapted to heterogeneous vertical cells, since the ex-
k Vb (i, j,k)
pression
dz(i, j,k)
is an average column (i, j) area;
k
the formula depends on real block pore volume.
For map one also can choose 2D concentration map via the formula:
k map(i, j, k)
concentration(map, i, j) =
k (Vb (i, j, k) ntg(i, j, k))
where
Vb (i, j, k) - volume of the block (i, j, k);
ntg - is specified via the corresponding keyword NTG (see 12.2.25) (Vb ntg - collector
formula).
5.11.2 Oil and gas in-place via separators

In compositional case (E300 data format) calculations of oil and gas in-place volumes can
be done using separators. Separator for all field is specified via the keyword FIELDSEP (see
12.15.20). This separator is used to calculated oil and gas in-place volumes for field.
To calculate oil and gas in-place volumes for different FIP regions with different separa-
tors one should specify the keyword FIPSEP (see 12.15.21).
Sum of oil and gas in-place for FIP region (FIPSEP) can be not equal to oil and gas in-place
5.11.1. Resources density and concentration 199

5.12. Phase potentials calculations tNavigator-4.2
for field calculated via FIELDSEP (see 12.15.20).
Equation of state is used for default to convert flow rates in surface conditions. Instead of
equation of state gas plant table can be used. In this case gas plant table should be specified
via the keywords GPTABLE (see 12.15.22), GPTABLE3 (see 12.15.24) or GPTABLEN (see
12.15.23).
5.12 Phase potentials calculations

Oil (gas, water) potential oil (gas, water) phase pressure, corrected to a datum depth.
Calculations of phase potentials of a grid block:
POTO = pO O g(D Ddat )
POTG = pG G g(D Ddat )

POTW = pW W g(D Ddat )
where:
POTO , POTG , POTW oil, gas, water potentials;
pO , pG , pW oil, gas, water phase pressures;
O , G , W , oil, gas, water average density in PVT region;
g gravity acceleration;
D block depth;
Ddat reference depth. Reference depth can be specified via the keyword DATUM (see
12.15.34) or it can be taken from the 1-st equilibration region reference depth, specified
via EQUIL (see 12.15.2). If keywords DATUM (see 12.15.34), EQUIL (see 12.15.2)
are not specified, then reference depth is set to zero. One can specify reference depth
different for different fluid-in-place regions (FIPNUM (see 12.4.10)) via the keyword
DATUMR (see 12.15.35). One can specify reference depth different for different fluid-
in-place regions (FIP (see 12.4.11)) via the keyword DATUMRX (see 12.15.36).
Field oil potential (FPPO in section SUMMARY (see 12.17.1)) is specified one of the
following ways:
default
POTO SO Porv
FPPO =
SO Porv
where POTO oil potential of a block (summation is over all blocks), SO oil
saturation; Porv block pore volume;
5.12. Phase potentials calculations 200

5.13. 2D maps for Saturation Ternary Diagram tNavigator-4.2
in the case that the value of 31-th parameter of OPTIONS (see 12.18.217) is even
POTO Porv
FPPO =
Porv
5.13 2D maps for Saturation Ternary Diagram

Saturation Ternary Diagram: block colour depends on oil saturation (Soil ), water saturation
(Swat ), or gas saturation (Sgas ) in this block.
2D maps Concentration, Density, Rms, Sum are visualized for oil saturation.
2D maps Maximum, Minimum are visualized the following way: blocks (from block
column) with minimum (maximum) oil saturation is taken.
k
Soil = min Soil
k=0,...,NZ
Water saturation (Swat ) and gas saturation (Sgas ) for this block are taken (the block with
minimum (maximum) oil saturation).
2D map Average (Avg) is calculated the following way:

NZ NZ
k V k k V k
Soil collector Sgas collector
k=0 k=0
Soil = NZ
, Sgas = NZ
k
Vcollector k
Vcollector
k=0 k=0
NZ
k V k
Swat collector
k=0
Swat = NZ
k
Vcollector
k=0
where:
The summation is over the layers in the vertical direction (from 0 to NZ );

k
Vcollector = V k ntgk ;
V k block volume;
ntg is specified via the corresponding keyword NTG (see 12.2.25).
5.13. 2D maps for Saturation Ternary Diagram 201

5.14. Split and merge of the model tNavigator-4.2
5.14 Split and merge of the model

In tNavigator approach to splitting is different from Eclipse, so the keywords DUMPFLUX
(see 12.2.41), FLUXNUM (see 12.4.18), FLUXREG (see 12.2.42) are ignored.
Detail description and examples of model split and merge see please in the training course
7-1_HowToSplitAndMergeModel.
In tNavigator, you can work with a model as described here below:

1. Split a model into several parts (in case of a huge model you will need a high-power
computer to compute the entire model once, in order to save the model pieces boundary
conditions (cross-boundary flows)).
2. Provide the model to the engineers in pieces. It is possible to use model pieces as
separate models in moderate-memory computers. It is possible to modify model pieces
(add wells, modify phase curves, permeability multipliers, plan well work jobs).
3. Put model pieces together into a large model, with the modifications made in the pieces.
Recompute a shared model file using a high-power computer to update model pieces
boundary conditions.
4. Continue working with model pieces.
In tNavigator during splitting new models are created parts of initial model. In the direc-
tory with model will be created the new directory MODEL NAME_PATTERNS, which con-
sists of splitted parts as independent models (MODEL NAME_PATTERNS_PATTERN001_1,
MODEL NAME_PATTERNS_PATTERN001_2, etc.) and common file .patterns.
.patterns-file contains all information about splitted parts. The calculation of this file cre-
ates .flux-files (flow files .flux), which contain the boundary conditions. Splitted parts of the
model are considered with these boundary conditions.
We recommend splitting the model so that the boundaries run through minimum cross-
flows areas. Cumulative water, oil, and gas cross-flow maps can be assigned prior to a model
computation via the keyword RPTMAPS (see 12.15.49).
Model splitting is only possible in two ways:

1. In graphical interface.
Splitting can be done via user Map or user Cut. Button: Split model. After splitting
the original model should be closed. Open the file .patterns. Run calculations of this
file .patterns. The boundary conditions are written in .flux-files, splitted pieces of the
model are ready for use.
2. Via console version of tNavigator.
Add a keyword FIPPATT (see 12.4.13) indicating splitted parts of the model. Run the
console version of tNavigator with the option --split. The boundary conditions are
written in .flux-files, splitted pieces of the model are ready for use.
5.14. Split and merge of the model 202

Then, to calculate the splitted parts with the boundary conditions, you just need to open
them and run the console or GUI version. To update the boundary conditions - re-compute
.patterns-file (console or GUI version).
Keywords.
FIPPATT (see 12.4.13) defines to which splitted region each block belongs to.
USEFLUX (see 12.2.40) defines .flux-file name which is used in splitted part.
Split and merge of hybrid models Eclipse and More.
Automatic split and merge can be used for hybrid models the same way as for models of
standard types.
After splitting in model parts there are the following keywords:
Example
SKIP
SKIPOFF
RECUMESH
SKIPON
ENDSKIP
You shouldnt delete these keywords! .patterns - file (whole model file) can not work
correct without them!
Features of splitting a model with wells.
5.14.1 Special features for wells

Group controls handling during model splitting.
1. The .flux-file of the region (the boundary conditions of the piece cut out) will have the
data listed here below recorded for all the groups with group control in the region and
with wells outside the region, excluding the wells within the region:
water production rate;

oil production rate;
gas production rate;
fluid production rate under the reservoir conditions;
5.14.1. Special features for wells 203

water injection;
gas injection;
water injection under the reservoir conditions;
gas injection under the reservoir conditions.
2. When the regions data are computed, the rate data from the file .flux are subtracted
from the group limit.
3. The following controls are supported:
GCONPROD (see 12.18.72) (ORAT, WRAT, GRAT, LRAT, RESV);

GCONINJE (see 12.18.81) (RATE, REIN, VREP, FLD);
GECON (see 12.18.102) (the minimum rate).
Wells located in more than one model piece.

If splitting places a well in a number of split-out pieces of the model, then splitting map
automatically adjusts itself in a way that the whole well should go to the piece of the map
where its wellhead projection on the tip layer of the model lies. All cells through which the
well passes add to this split-out piece. Thus, if in a data file of the model WELSPECS (see
12.18.3) keyword specifies [i,j] coordinates of perforation interval the well will go to the
same piece that the [i,j,1] block occupies when splitting the model. At that a status bar in the
lower part of the screen will indicate a notice as follows (as an example):
Well PROD21 is located in more than one region! [8, 20, 2] Perforation interval is in region
1, and [8, 20, 3] - in 2. Notice: The map for model cutting is adjusted automatically, as a
number of wells found belonging to several regions!
5.14.2 Splitting a model in the GUI

1. Open a model (but do not run a computation).
2. Create a Map or a User Cut to assign the regions the model is to be split into. You can
split a model using any Cut or any User Map, you can cut out a FIP region.
3. The button Split model (select Cut or Map split option).
4. After splitting, close the source model and open the file .patterns. Compute the file
.patterns. The boundary conditions are recorded in .flux files, model pieces cut out are
ready to use.
5. All the model pieces can be opened as separate models and computed. Also, the pieces
can be modified (wells added, phase curves modified, an aquifer added).
6. In order to compute the pieces with the boundary conditions, just open them and have
them computed in the console version or in the GUI version.
5.14.2. Splitting a model in the GUI 204

5.15. Reservoir Coupling tNavigator-4.2
7. Merge model pieces. Re-compute the file .patterns U this will include all the modifi-
cations into the model. To update the boundary conditions (.flux files) in the model
pieces, the file .patterns must be re-computed.
5.15 Reservoir Coupling

tNavigator support an option Reservoir Coupling to combine calculations of different models.
The following keywords can be used: SLAVES (see 12.18.237), GRUPMAST (see
12.18.238), GRUPSLAV (see 12.18.239).
Several SLAVEs (subordinate) models are calculated sharing the groups controls. One
principal model MASTER controls simulation.
Stick please to the following instructions specifying principal and subordinate models:
SLAVE models are full-featured models in these possible formats: E100, E300, MORE,
IMEX, STARS, GEM.
MASTER model must be in E100 format or E300 (in case if at least one of SLAVE
models is compositional or thermal). It can be full-featured model or simple fake model
with one active grid block.
If at least one of SLAVE models is compositional or thermal, then the components with
the same names from different model are comsidered in MASTER as the same compo-
nent and component production rates on them will be summarized. In not compositional
models we asume that components have names WATER, OIL, GAS. Components in
the MASTER model should be the union of component in SLAVE models, containing
also names OIL, GAS, if there are not compositional SLAVE models.
Number of SLAVE models is limited only with the number of available tNavigator
licenses, there are no any other limits on slaves number.
Reporting time steps in SLAVEs and MASTER can be different.
Starting dates in SLAVEs should not be earlier as in MASTER model.
Ending dates in SLAVEs should not be later then in MASTER model.
SLAVE models can be 2 or 3 phase. In different models different number of phases

can be used.
In MASTER model the number of phases shouldnt be less then this number in each
SLAVE.
Group limits that are set in MASTER, work with phase rates in surface conditions.
For each model production rate calculation to surface conditions is based on phase
properties that are set in the model.
5.15. Reservoir Coupling 205

The possibility to couple models with common surface network is available (keywords
for Standard network option are available GRUPNET (see 12.18.96), GRUPINJE (see
12.18.41), GNETINJE (see 12.18.91) etc).
There is fully implicit model calculation. Equations from all models are combined to
one common system of equations that describes the whole integrated reservoir.
Subordinate models are set via the keyword SLAVES (see 12.18.237). Well group in the
SLAVE model should be the child of the group in MASTER model (keywords GRUPMAST
(see 12.18.238), GRUPSLAV (see 12.18.239)).
Then all group limits (that are set in MASTER model) act on groups/wells in SLAVE models
using the extend group tree (set via GRUPTREE (see 12.18.85)).
tNavigator checks the pairs of principal-subordinate groups, set using the keywords
GRUPMAST (see 12.18.238) and GRUPSLAV (see 12.18.239). Two options are possi-
ble. If in MASTER model we have GRUPMAST (see 12.18.238) for the group G in the
model SLAVE1, and in the model SLAVE1:
the corresponding GRUPSLAV (see 12.18.239) is not specified, then the group limits
set in SLAVE1 continue to act on group G (option BOTH);
the corresponding GRUPSLAV (see 12.18.239) is specified, then its parameters 3-9
define if the group limits (specified in SLAVE1) will affect on the group G. In particular
if parameters 3-9 are not specified then GCONPROD (see 12.18.72), GCONINJE (see
12.18.81) specified in SLAVE model for SLAVE group will be ignored (option MAST).
An example and the picture of MASTER-SLAVES scheme is in the description of the
keyword GRUPMAST (see 12.18.238).
Reservoir couping using surface network.

In MASTER and SLAVE models standard network (GRUPNET (see 12.18.96),
GRUPINJE (see 12.18.41), GNETINJE (see 12.18.91)) and extended network (NET-
WORK (see 12.1.84)) can not be used simultaneously.
If there is a connection between the group in MASTER model and the group in SLAVE
model specified via GRUPMAST (see 12.18.238), GRUPSLAV (see 12.18.239), and
there are corresponding network nodes with the same names, then they will be con-
nected without pressure loss (analogue to defaulted VFP table for network node).
Network node in SLAVE model that is connected to the network node in the MASTER
model, should be defined in SLAVE model as a node eith fixed pressure.
The calculation of surface network is done explicitly for all models. VFP tables from
the corresponding models are used for network branches in these models; there is no
pressure loss for branches between models. Phase rates in surface conditions are used;
calculation to surface conditions are done according to the properties specified in the
models (for the group limits also).

The are the following limits in Reservoir Coupling option in current version of tNavigator:
The following features are not supported in SLAVE and MASTER models: Gas lift
optimization (2.19.8), Gas field operations model DCQ (2.19.7).
The only link between SLAVE and MASTER models is the extend group tree in
MASTER model and group limits. The only one possibility to link to the well/group
names in other models is via the keywords GRUPMAST (see 12.18.238), GRUPSLAV
(see 12.18.239). So in this version, for example, reinjection from one model to another
is impossible.
Wells/groups with the same names can be specified in different SLAVE models, but
this wells/groups will be considered as different.
SLAVE and MASTER models can not use RESTART (see 12.1.14).

6.2. Single Phase Flow Theory tNavigator-4.2
6 VFP tables generation

Tubing hole pressure is one of the main parameters of well condition control in simula-
tion of mixture flow in the well bore. Tubing hole pressure value is measured during wells
work. This parameter is is important for surface networks. In hydrodynamic modeling it is
necessary to correct tubing hole pressures to perforation pressures to calculate flow volume
into wellbore. This is a difficult problem, and there are several ways to calculate correla-
tions, which accounts different regimes of mixture flow in wellbore. tNavigator supports the
following correlations: Petalas & Aziz, Hagedorn-Brown, Beggs & Brill, Orkiszewski, Gray,
Aziz, Govier & Fogarasi, Mukherjee & Brill.
VFP tables can be created via correlations using the keyword VFPCORR (see 12.18.61).
Comparison of correlations is below.
6.1 Problem decription

6.1.1 Problem decription
Liquid in wellbore suffers pressure loss. Pressure loss can be divided into three components:
hydrostatic pressure loss;
pressure loss due to friction;
kinetic pressure loss.
Kinetic pressure loss is very small usually, and its influence can be ignored. So, equation
which expresses pressure loss can be written as follows:
PTotal = PHydro + PFrictional
6.2 Single Phase Flow Theory

6.2.1 Friction pressure loss
This type of correlation is based on the definition of the Fanning friction factor and is given
by the Fanning equation
2 f v2 L
Pf = ,
gc D
where:
Pf pressure loss due to friction effects (psia);
f Fanning friction factor (function of Reynolds number);
density (lb/ft 3 );
v average velocity (ft/s);
6. VFP tables generation 208

6.2. Single Phase Flow Theory tNavigator-4.2
L length of pipe section (ft);
gc = 32.2 gravitational constant;
D inside diameter of pipe (ft).
This correlation can be used either for single-phase gas (Fanning Gas) or for single-phase
liquid (Fanning Liquid).
6.2.2 Single-Phase Friction Factor (f)

The single-phase friction factor can be obtained from the following equation:
" 1.1098 !#
1 k 5.0452 k 5.8506
= 4.0log 0.2698 log 0.3539 + 0.8981 ,
f D Re D Re
where:
f friction factor;
k absolute roughness (in);
k/D relative roughness (unitless);
Re Reynolds number.
The single-phase friction factor clearly depends on the Reynolds number, which is a
function of the fluid density, viscosity, velocity and pipe diameter:
1488vD
Re = ,

where:
density (lb/ft 3 );
v velocity (ft/s);
D diameter (ft);
viscosity (cP).
6.2.2. Single-Phase Friction Factor (f) 209

6.3. Multiphase Flow Theory tNavigator-4.2
6.2.3 The Single Phase hydrostatic pressure drop

The hydrostatic pressure drop (PH ) is defined as follows:
PH = gh,
where:
density of the fluid;
g acceleration of gravity
h vertical elevation (can be positive or negative).
For a liquid, the density (()) is constant, and the above equation is easily evaluated.
For a gas, the density varies with pressure. Therefore, to evaluate the hydrostatic pressure
loss/gain, the pipe (or wellbore) is subdivided into a sufficient number of segments, such that
the density in each segment can be assumed to be constant.
6.3 Multiphase Flow Theory

The presence of multiple phases greatly complicates pressure drop calculations. This is due
to the fact that the properties of each fluid present must be taken into account. Also, the
interactions between each phase have to be considered. Mixture properties must be used,
and therefore the gas and liquid in-situ volume fractions throughout the pipe need to be
determined. In general, all multiphase correlations are essentially two phase and not three
phase. Accordingly, the oil and water phases are combined, and treated as a pseudo single
liquid phase, while gas is considered a separate phase.
The friction pressure loss is modified in several ways, by adjusting the friction factor
( f ), the density () and velocity (v) to account for multiphase mixture properties.
The hydrostatic pressure difference calculation is modified by defining a mixture density.
This is determined by a calculation of in-situ liquid holdup. Some correlations determine
holdup based on defined flow patterns.
6.3.1 Nomenclature
Superficial velocities.
The superficial velocity of each phase is defined as the volumetric flow rate of the phase
divided by the cross-sectional area of the pipe (as though that phase alone was flowing
through the pipe):
QL
vsL = ;
R2
Q0 BG
vsG = G 2 .
R
6.2.3. The Single Phase hydrostatic pressure drop 210

Since the liquid phase accounts for both oil and water (QL = QO BO + (QW xwG QG )BW ),
and the gas phase accounts for the solution gas going in and out of the oil as a function of
pressure (Q0G = QG QO RS ), the superficial velocities can be rewritten as:
QO BO + (QW xwG QG )BW

vsL = ;
R2
(QG QO RS )BG
vsG = ,
R2
where:
QP phase P flow rate (at stock tank conditions);
BP phase P volume factor;
RS solution gas/oil ratio;
xwG water of condensation (water content of natural gas, Bbl/MMscf);
R pipe radius.
Mixture Velocity.
Mixture Velocity is another parameter often used in multiphase flow correlations. The
mixture velocity is given by:
vm = vsL + vsG ,
where:
vm mixture velocity;
vsL superficial liquid velocity;
vsG superficial gas velocity.
Mixture Viscosity.
The mixture viscosity is a measure of the in-situ viscosity of the mixture and can be
defined in several different ways. In general, unless otherwise specified, is defined as follows:
m = L EL + G (1 EL ),
where:
EL in-situ liquid volume fraction (liquid holdup);
m mixture viscosity;
L liquid viscosity;
G gas viscosity.
6.3.1. Nomenclature 211

Mixture Density.
The mixture density is a measure of the in-situ density of the mixture, and is defined as
follows:
m = L EL + G (1 EL ),
where:
EL in-situ liquid volume fraction (liquid holdup);
m mixture density;
L liquid density;
G gas density.
Liquid density and viscosity.
To calculate liquid density (L ) and viscosity (L ) we will apply the following formulas:
O RO + W RW
L = ;
RO + RW
1 1
1 O RO + W RW
= ,
L RO + RW
where:
P phase P density (P = W, O, G);
P phase P viscosity;
RP phase P molar fractures.

Input Volume Fraction.
The input volume fractions are defined as:
QL
CL = ;
QL + QG BG
QG BG
CG = .
QL + QG BG
We can also write this as:
vsL
CL = ;
vm
vsG
CG = ,
vm
where:
CP phase P input gas volume fraction;
QP phase P flow rate (at stock tank conditions);

BP phase P volume factor;

vsG superficial gas velocity;
vsL superficial liquid velocity;
vm mixture velocity (vsL + vsG ).
No-Slip Density.
The no-slip density is the density that is calculated with the assumption that both phases
are moving at the same in-situ velocity. The no-slip density is therefore defined as follows:
NS = LCL + G (1 CL ),
where:
CP phase P input volume fraction;
NS no-slip density;
L liquid density;
G gas density.
No-Slip Viscosity.
The no-slip viscosity is the viscosity that is calculated with the assumption that both
phases are moving at the same in-situ velocity. There are several definitions of no-slip
viscosity. In general, unless otherwise specified, (NS ) is defined as follows:
NS = LCL + G (1 CL ),
aaa:
CP phase P input volume fraction;
NS no-slip viscosity;
L liquid viscosity;
G gas viscosity.
Surface Tension.
The surface tension between the gas and liquid phases has very little effect on two-
phase pressure drop calculations. However, a value is required for use in calculating certain
dimensionless numbers used in some of the pressure drop correlations. Empirical relationships
for estimating the gas/oil surface tension and the gas/water surface tension are represented
there.
Gas/Oil Interfacial Tension.
The dead oil interfacial tension at temperatures of 68 F and 100 F is given by:
68 = 39 0.2571(API)
100 = 37.5 0.2571(API)
where:

68 interfacial tension at 68 F;
100 interfacial tension at 100 F;
API gravity of stock tank oil.
If the temperature is greater than 100 F, the value at 100 F is used. If the temperature is
less than 68 F, the value at 68 F is used. For intermediate temperatures, linear interpolation
is used.
(T 68)(68 100 )
T = 68
32
As pressure is increased and gas goes into solution, the gas/oil interfacial tension is
reduced. The dead oil interfacial tension is corrected for this by multiplying by a correction
factor.
C = 1.0 0.024 p0.45
where:
p pressure;
Interfacial tension at any pressure can be get from expression
= CT
Gas/Water Interfacial Tension.

The gas/water interfacial tension at temperatures of 74 F and 280 F is given by:
w(74) = 75 1.108 p0.349
w(280) = 53 1.1048 p0.637

where:
w(74) interfacial tension at 74 F;
w(280) interfacial tension at 280 F;
p pressure.
If the temperature is greater than 280 F, the value at 280 F is used. If the temperature is
less than 74 F, the value at 74 F is used. For intermediate temperatures, linear interpolation
is used.
(T 74)(w(74) w(280) )
w(T ) = w(74)
206

6.3.2 The Griffith Correlation

This type of correlation is a modification to the Hagedorn and Brown ([13]) Correlation. We
have:
PT H tubing hole pressure;

j
QP phase P volume rate at surface conditions (P = 1, . . . , nP );
j
BP phase P volume fracture;
P phase P viscosity;
P phase P density;
z elevation change;
L length of calculation segment;
D inside pipe diameter;
g gravitational acceleration;
k relative pipe roughness;
RS dissolved gas/oil factor;
xwG vaporized water fracture.
Gas (VsG ) and liquid (VsL ) velocities are given by:
QO BO + (QW xwG QG )BW

VsL = ;
/4D2
(QG QO RS )BG
VsG = .
/4D2
Mixture velocity (vm ) is given by:
vm = vsL + vsG .
Liquid density (L ) and viscosity (L ) are given by:

O RO + W RW
L = ;
RO + RW
1 1
1 O RO + W RW
= .
L RO + RW
6.3.2. The Griffith Correlation 215

In the Griffith correlation the liquid holdup is given by:

s
2
1 vm vm vsG
EL = 1 1 + 1+ 4 .
2 vs vs vs
Griffith suggested a constant value of vs = 0.8 f t/s as a good average value, which is the
one considered in our calculations.
The hydrostatic head is calculated by the standard equation:
m gsin()
PH = ,
144gc
where:
m = L EL + G (1 EL ).
The in-situ liquid velocity is given by:
vsL
vL = .
EL
Define Reynolds number ReL , which is given by:
1488L vL D
ReL = .
L
It is suggested, if Re < Re1 = 2000 then there is a Poiseuilles laminar flow in pipe, if
Re > Re2 = 4000, then there is turbulent flow in pipe, if 2000 = Re1 < Re < Re2 = 4000 then
there is a transitional flow. In laminar flow
16
flow (Re) = .
Re
In turbulent flow Fannings friction factor is given by:
" 1.1098 !#!2
1 k 5.0452 k 5.8506
fup (Re) = log10 0.2698 log10 0.3539 + 0.8981 .
16 D Re D Re
Then
f (Re) Re < 2000;
low

flow (4000 Re) + fup (Re 2000)
f= 2000 6 Re 6 4000;

2000
fup (Re) Re > 4000.

Pressure loss due to friction is calculated by Hagedorn-Brown correlation:
2 f L v2L
Pf = .
144gc D
6.3.2. The Griffith Correlation 216

6.3.3 Petalas & Aziz correlation

The Petalas and Aziz ([16]) correlation is capable of handling flow in all directions: horizon-
tal, inclined and vertical flow. The Petalas and Aziz multiphase correlation accounts for both
frictional pressure loss and hydrostatic pressure differences. Each particular combination of
gas and liquid rates are characterized by the following flow regimes:
Dispersed Bubble Flow;
Stratified Flow;
Annular-mist Flow;
Bubble Flow;
Intermittent Flow.
Flow Pattern Determination.
The Petalas and Aziz model for multiphase flow requires that a flow pattern be deter-
mined. Five flow patterns are defined in this model and the transition zones for this correlation
are given below:
Dispersed Bubble Flow

Dispersed bubble flow exists if:
1
ELs = < 0.48,
vm 1.39

1+ 8.66
where vm mixture velocity:

vm = vsG + vsL .
A transition from dispersed bubble flow to froth flow can also occur when the maximum
volumetric packing density of the dispersed gas bubbles is exceeded:
vsG
CG = 0.52.
vm
Stratified Flow.
Determining the stability of the stratified flow regime requires the calculation of the liquid
height, hL , which can be obtained by writing the momentum balance equations for the gas
and the liquid phases as was done by Taitel and Dukler:

dp g
AL wL SL + i Si L AL sin = 0,
dL gc

dp g
AG wG SG i Si G AG sin = 0.
dL gc
Transverse section area of liquid (AL ) and gas (AG ) can be calculated from geometrical
considerations. Lets suggest that gas in the upper section of pipe, and liquid is in the lower
one.
6.3.3. Petalas & Aziz correlation 217

AG
A D
R O
AL
hL
R is a pipe radius. Point O is a circle (pipe) center. Chord AD is a boundary between

gas and liquid. Lets denote an angle which subtends arc AD. Then unknown areas will
be expressed as follows:
R2
S= = R2 ,
2 2
1
S4ADO = R2 sin.
2
Then we can calculate unknown areas and liquid height (hL ):
R2
AG = ( sin);
2

2 2 sin
AL = R AG = R + ;
2 2

hL = R + R cos = R (1 + cos ) = 2R cos2 .
2 2 4
It is left to express perimeters of boundaries between gas and liquid (Si ), gas and pipe (SG ),
and liquid and pipe (SL ).
SG = R ;
SL = (2 )R;

Si = 2R sin .
2
The shear stresses are given by the following relationships:
fG G v2G
wG = ;
2gc
fL L v2L
wL = ;
2gc
fi G vi |vi |
i = .
2gc
Friction factor on boundary between gas and pipe can be found the way which is analogous
to the one. which is used for one-phase flow with account pipe roughness and the following
Reynolds number:
DG G vG
ReG = ,
G

where DG is a hydraulic diameter of gas phase:

4AG
DG = .
SG + Si
The way which is analogous to one in one-phase case is inconvenient for boundary between
liquid and pipe. It is used the following empirical expression for liquid/pipe friction factor
instead of it:
0.731
fL = 0.452 fSL .
The friction factor, fSL , is obtained from standard methods using pipe roughness and
Reynolds number, Rem :
D L vSL
ReSL = .
L
When flow downhills, more solid phase can flow faster than more light. Then phase-to-
phase shift calculation is based on value vi = vG vL , which can be negative due to some
conditions. Phase-to-phase friction factor is given by empirical dependence:

6 1.335 L Dg
fi = (0.004 + 0.5 10 ReSL )FrL .
G v2G
Froude number is given by:

vL
FrL = .
ghL
Dimensionless liquid height:
hL
hL = = cos2 .
D 4
The following is necessary to multi-phase flow to exist:
s
(L G )gAG cos
vG (1 hL ) ;
G dA L
dhL
(if cos 0.02, cos = 0.02 here)

s
gD(1 hL )cos
vL .
fL
To distinguish between stratified smooth and stratified wavy flow regimes: stratified smooth
flow exists if: s
4L (L G )gcos
vG ;
sL G vL
vL
Fr = 1.4.
ghL
Else multi-phase flow is implemented.

Annular-mist Flow.
Use momentum balance on the liquid film and gas core with liquid droplets:

dp g
A f wL SL + i Si L A f sin = 0;
dL gc

dp g
Ac i Si c Ac sin = 0.
dL gc
The geometric parameters can be expressed in terms of the dimensionless liquid film thick-
ness:
L = L /D.
Lets denote pipe radius as R. Point O is a circle (pipe) center. Liquid film thickness L .
L O
Expression of areas to be determined:

2
Ac = (R L )2 = D (1 2L )2 ;
4

A f = 2 R2 (R L )2 = D2 1 (1 2L )2 .
4
It is left to express perimeters of boundaries between gas and liquid (Si ), and liquid and pipe
(SL ):
SL = 2R = D;
Si = 2(R L ) = D(1 2L ).
Parameter k :
Af
= k.
Ac
Expression for k of L :
2RL L2
k= ;
(R L )2
L2 (k + 1) 2RL (k + 1) + kR2 = 0;
4L2 (k + 1) 4L (k + 1) + k = 0;
D = 16k + 16;
1 1
L = ;
2 2 k+1

1
k= 1.
(2L 1)2
The liquid fraction in the film is given by:
Af Af 1 k
Ef = = = 1
= =
A A f + Ac 1 + k k+1

2 1
= (2L 1) 1 = 1 (2L 1)2 ;
(2L 1)2
Af
Ef = = 4L (1 L ).
A
The shear stresses are given by:
f f L v2f
wL = ;
2gc
fi c (vc v f )|vc v f |
i = .
2gc
Gas cores and the liquid film velocities is given by:
A vsL (1 FE)
v f = vsL (1 FE) = ;
Af 4L (1 L )
A (vsG + vsL FE)

vc = (vsG + vsL FE) = .
Ac (1 2L )2
The friction factor for the liquid film is computed using any of the standard correlations with
the pipe roughness and the film Reynolds number as expressed by:
D f L v f
Re f = ;
L
D f = 4L (1 L )D.
Friction factor fc is calculated using standard formulas of pipe roughness and the following
Reynolds number definition:
Dc c vc
Rec = ;
c
Dc = D(1 2L );
c = Ec L + (1 Ec )G ;
c = Ec L + (1 Ec )G ;
vsL FE
Ec = .
vsG + vsL FE

In order to solve these equations, two additional quantities need to be determined: the in-
terfacial friction factor, fi , and the liquid fraction entrained, FE . These are determined
empirically and are given by:
0.2
FE 0.074 vsG
= 0.735NB ;
1 FE vsL
0.085
fi
= 0.24 Re0.305
f ,
fc c v2c Dc
where the dimensionless number, NB , is defined as:
L2 v2sG G
NB = .
2 L
L can be found using an iterative procedure to obtain the liquid film height at which the
minimum shear stress occurs. Annular flow instability occurs when the supply of liquid in
the film is sufficient to cause blockage of the gas core by bridging the pipe.
Hence, the transition from annular flow occurs when
vsG
EL = 1 (1 2L )2
vsG + FE vsL
and
EL 0.24.
Bubble Flow.
When the liquid fraction in the slug is greater than 0.48:
1
ELs = > 0.48
vm 1.39

1+ 8.66
and the stratified, annular and dispersed bubble flow regimes have been eliminated, the
flow will either be intermittent, froth or bubble flow. Bubble flow is encountered in steeply
inclined pipes and is characterized by a continuous liquid phase containing a dispersed phase
of mostly spherical gas bubbles. It can exist if both of the following conditions are satisfied:
1. Large diameter pipes when
(L G ) 1/2

D > 19 ;
gL2
2. The angle of inclination is large enough to prevent migration of bubbles to the top wall
of the pipe:
3 2 Ct 2

cos vb ,
4 2 g db
The lift coefficient, Ct , ranges from 0.4 to 1.2, the bubble distortion (from spherical) coeffi-
cient, , ranges from 1.1 to 1.5 and a bubble size, db , between 4 and 10 mm. We take for
this model:
Ct = 0.8, = 1.3, db = 7 mm.

The bubble swarm rise velocity in a stagnant liquid, vb , is given by:

1/4
g(L G )
vb = 1.41 sin.
L2
When both of the above conditions are satisfied, bubble flow is observed even at low liquid
rates where turbulence does not cause bubble breakup.
The transition to bubble flow from intermittent flow occurs when the gas void fraction
(during slug flow) drops below the critical value of 0.25:
EL > 0.25,
where
ELs vt + vGdb (1 ELs ) vsG
EL = .
vt
Intermittent Flow.
The intermittent flow model used here includes Slug and Elongated Bubble flow regimes.
Intermittent flow exists if:
EL 0.24,
where
EL =
vt
(Note: if EL > 1, then EL = vsL /vm .);
1
ELs = ;
vm 1.39

1+ 8.66
vm = vsG + vsL .
where vGdb represents the velocity of the dispersed bubbles vt is the translational velocity
of the slug, and ELs is the volume fraction liquid in the slug body. The translational velocity
of the elongated bubbles is given by
vt = C0 vm + vd .
The parameter C0 is a distribution coefficient, which determined from the following empiri-
cally derived correlation:
C0 = (1.64 + 0.12sin)Re0.031
mL .
The modified Reynolds number in the given equation is based on the mixture velocity and
liquid properties:
L vm D
RemL = .
L
The elongated bubble drift velocity, vd can be calculated by:
vd = fm vd ,


where fm = 0.316 Re for fm < 1, otherwise fm = 1, and
L vd D
Re = .
2L
The elongated bubble drift velocity at high Reynolds numbers as:
vd = vdh cos + vdv sin.
The drift velocity of elongated bubbles in a horizontal system at high Reynolds numbers
is given by:
s
1.76 gD(L G )
vdh = 0.54 0.56 .
Bo L
The Bond number, Bo = (L

G)
gD2 .
The drift velocity of elongated bubbles in a vertical system at high Reynolds numbers is
given by: s
gD(L G )
vdv = 0.345(1 e ) .
L
The coefficient, , is given by:
= Bo e(3.2781.424 ln(Bo))
.
Finally, the liquid volume fraction can be calculated once the velocity of the dispersed bubbles
in the liquid slug is obtained from:
vGdb = C0 vm + vb .
(Note: if vGdb < 0, then vGdb = 0). The rise velocity of the dispersed bubbles is calculated
from:
g(L G ) 1/4

vb = 1.53 sin.
L2
Froth Flow.
If none of the transition criteria for intermittent flow are met, the flow pattern is then
designated as Froth. Froth flow implies a transitional state between the other flow regimes.
Hydrostatic Pressure Difference.
Once the flow type has been determined then the liquid holdup can be calculated. There
is a separate calculation of liquid holdup EL for each flow type.
Dispersed Bubble Flow.
Lets determine superficial gas (vsG ) and liquid (vsL ) velocities. Mixture velocity (vm ) is
given by:
vm = vsL + vsG .
Then gas velocity (with dispersed bubbles) determined from:
vGdb = C0 vm + vb ,

where C0 is determined from the empirical correlation:

C0 = (1.64 + 0.12sin)Re0.031
mL ,
L vm D
RemL = .
L
And vb (the rise velocity of the dispersed bubbles) determined from:
g(L g ) 1/4

vb = 1.53 sin.
L2
Now, (EL ) is given by:
vsG
EL = 1 .
vGdb
If vGdb 0, then EL is given by:
vsG
EL = 1 .
c0 vm
Once the liquid holdup (EL ) has been calculated, it is then used to calculate the mixture
density (m ):
m = L EL + G (1 EL ).
The mixture density can now be used to calculate the pressure change due to the hydrostatic
head for the segment of pipe being investigated.
g
PH = m h sin.
gc
Stratified Flow.
Liquid volume fraction (EL liquidholdup) is given by:
AL
EL = ,
A
where:
AL area of transverse section of liquid phase;
A area of transverse section.
The PH is then calculated from the hydrostatic portion of the gas and liquid phase momen-
tum balance equations:
g
PH = L h sin;
gc
g
PH = G h sin.
gc
Annular-mist Flow.
Liquid volume fraction (EL liquidholdup) is determined using geometric considerations
and a known liquid thickness, by the following equation:
vcG
EL = 1 (1 2L )2 .
vsG + FEvsL

The PH is then calculated from the hydrostatic portion of the gas and liquid phase momen-
tum balance equations.
g
PH = L h sin;
gc
g
PH = G h sin.
gc
Bubble Flow.
The bubble flow volumetric gas fraction is given by:
vsG
EG = ,
vt
where (vt ) is the translational bubble velocity:
vt = c0 vm + vb .
With C0 assumed to be 1.2 and vb given by the equation below:
g(L g ) 1/4

vb = 1.41 sin.
L2
The value of EG is characterized by the range where:
vsG
0 EG CG = .
vm
Once the volumetric gas fraction (EG ) has been calculated, it is then used to calculate the
mixture density (m ):
m = L (1 EG ) + G EG .
head for the segment of pipe being investigated:
g
PH = m h sin.
gc
Intermittent Flow.
Liquid volume fraction (EL ) is given by:
EL = .
vt
density (m ):
m = L EL + G (1 EL ).
head for the segment of pipe being investigated:
g
PH = m h sin.
gc

Friction Pressure Loss.

The frictional portion of the overall pressure gradient is determined based on pipe geom-
etry and flow distribution. Each flow type has a separate calculation used to determine the
pressure losses due to friction. The details of these calculations are summarized here.
Dispersed Bubble Flow.
The first step to determine the frictional pressure loss is to obtain a friction factor, fm . The
friction factor is obtained from standard methods using pipe roughness and Reynolds number,
Rem :
Dm vm
Rem = ,
m
where mixture density (m ) and mixture viscosity (m ) are calculated from:
m = EL L + EG G ;
m = L EL + G EG .
The expression for the pressure loss due to friction is:
2 fm v2m m
PF = .
D
Stratified Flow.
The expression for the pressure loss due to friction is determined from a portion of the
momentum balance equations:
wL SL + i Si
PF = ;
AL
wG SG i Si
PF = .
AG
All these variables were defined earlier during flow type definition.
Annular-mist Flow.
The expression for the pressure loss due to friction is determined from a portion of the
momentum balance equations:
wL SL + i Si
PF = ;
AL
i Si
PF = .
AC
Bubble Flow.
The friction factor for bubble flow, fmL is obtained from standard methods using pipe
roughness and the following definition of Reynolds number:
DL vm
RemL = .
L
Now, the expression for the pressure loss due to friction is:
2 fmL v2m m
PF = .
gc D

Intermittent Flow.
The frictional pressure loss for intermittent flow is taken from the momentum balance written
for a slug-bubble unit:

1 Ls D L f SL f + Gdb SGdb
PF = Ls +Lf .
Lu A A
There is no reliable method to determine the slug length, Ls , the length of the bubble region,
L f , of the frictional pressure loss in the gas bubble. Therefore, the following simplified
approach is adopted given the stated uncertainties.

dp dp dp
= + (1 ) .
dL dL f rSL dL f rAM
Where is a weighting factor determined empirically relation the slug length to the total
slug unit length Ls /Lu :
(0.75EL )
= CL
Where 1.0.
Now the frictional pressure gradient for the slug portion is obtained from:
fmL v2m m

dp
=2 .
dL f rSL gD

dp
The frictional pressure gradient for the annular-mist flow portion, dL , is calculated as
f rAM
in case of annular-mist flow. To calculate film height the following formula is used:
s
1 (EFvsL + vsG )
L = 1 (1 EL ) .
2 vsG
The annular-mist frictional pressure gradient is calculated from:

dp 4wL
= .
dL f rAM D
When the calculated film height L is less than 1 104 , the frictional pressure gradient for
the annular-mist flow portion, is obtained from:
2 fm v2m m

dp
= .
dL f rAM gc D

6.3.4 Beggs & Brill correlation

The Beggs and Brill multiphase correlation ([14]) deals with both the friction pressure loss
and the hydrostatic pressure difference. First the appropriate flow regime for the particular
combination of gas and liquid rates (segregated, intermittent or distributed) is determined.
The liquid holdup, and hence, the in-situ density of the gas-liquid mixture is then calculated
according to the appropriate flow regime, to obtain the hydrostatic pressure difference. A
two-phase friction factor is calculated based on the input gas-liquid ratio and the Fanning
friction factor.
Flow Pattern Map.
To generate flow pattern map the Beggs and Brill correlation requires that a flow pattern
be grouped the following way: segregated (stratified, wavy and annular flows), intermittent
(plug and slug flow), distributed (bubble and mist flows) and transition. The transition lines
for the modified correlation are defined as follows:
L1 = 316 CL0.302
L2 = 0.0009252 CL2.4684
L3 = 0.1 CL1.4516
L4 = 0.5 CL6.738
The Froude number is a dimensionless number which relates the inertia with respect to the
gravitational forces. For a mixture, it can be obtained by:
v2m
Frm =
gD
Once the input liquid content CL and Froude number of the mixture (Frm ) are determined,
the corresponding flow pattern is identified when the following inequalities are satisfied:
Segregated flow.
If
CL < 0.01 and Frm < L1
or
CL 0.01 and Frm < L2
6.3.4. Beggs & Brill correlation 229

Intermittent flow.
If
0.01 CL < 0.4 and L3 < Frm L1
or
CL 0.4 and L3 < Frm < L4
Distributed flow.
If
CL < 0.4 and Frm L1
or
CL 0.4 and Frm > L4
Transition flow.
If
CL 0.01 and L2 < Frm < L3
Once the flow type has been determined then the liquid holdup can be calculated. Beggs
and Brill divided the liquid holdup calculation into two parts. First the liquid holdup for
horizontal flow, EL (0), is determined, and then this holdup is modified for inclined flow.
Afterwards, this horizontal holdup is corrected for inclined flow to obtain the actual holdup,
EL (). The horizontal holdup must be EL (0) CL . Therefore, in the event that EL (0) < CL ,
the horizontal holdup is set to EL (0) = CL . The expression used to calculate the horizontal
holdup changes per flow pattern group as follows:
Segregated.
0.98 CL0.4846
EL (0) = 0.0868
Frm

Intermittent.
0.845 CL0.5351
EL (0) = 0.0173
Frm
Distributed.
1.065 CL0.5824
EL (0) = 0.0609
Frm
Transition.
EL (0)transition = A EL (0)segregated + B EL (0)intermittent

where:
L3 Frm
A= and B = 1A
L3 L2
Once the horizontal in situ liquid volume fraction is determined, the actual liquid volume
fraction is obtained by multiplying EL (0) by an inclination factor B():
EL () = B()EL (0)
where:
1 3
B() = 1 + sin(1.8 ) sin (1.8 )
3
is a function of flow type, the direction of inclination of the pipe (uphill flow or downhill
flow), the liquid velocity number (NvL ) and the mixture Froude Number (Frm ). And
1/4
L
NvL = 1.938vsL
g
For UPHILL flow:

Segregated:
0.011 N 3.539

= (1 CL ) ln 3.768 vL1.614
CL Frm
Intermittent
2.96 CL0.305 Frm0.0978

= (1 CL ) ln 0.4473
NvL
Distributed
=0
For DOWNHILL flow:

ALL flow types:
0.011 N 0.1244

= (1 CL ) ln 0.3692 vL0.5056
CL Frm
Note: must always be 0. Therefore, if a negative value is calculated for , = 0.
Once the liquid holdup (EL ()) is calculated, it is used to calculate the mixture density
(m ). The mixture density is, in turn, used to calculate the pressure change due to the
hydrostatic head of the vertical component of the pipe or well.
m gz
PH =
144gc
The first step to calculating the pressure drop due to friction is to calculate the empirical
parameter S :
if 1 < y < 1.2, then
S = ln(2.2y 1.2)
otherwise,
y
S=
0.0523 + 3.18y 0.872y2 + 0.01853y4
where:
CL
y = ln
EL2
A ratio of friction factors is then defined as follows:
ft p
= es
fNS
fNS is the no-slip friction factor. We use the Fanning friction factor, calculated using the
Chen equation. The no-slip Reynolds Number is also used, and it is defined as follows:
NS vm D
ReNS =
NS
Finally, the expression for the pressure loss due to friction is:
2 ft p v2m NS L
Pf =
144gc D
6.3.5 Orkiszewski method

Orkiszewski ([12]) distinguished four types of flow patterns:
Bubble Flow;
Slug Flow;
6.3.5. Orkiszewski method 232

Transition Flow;
Mist Flow.
For each one he developed some relations to establish the hydrostatic and the friction losses
Flow pattern determination.
It is necessary to determine flow regime for Orkiszewski method for multi-phase flow.
To determine flow regime one of the following conditions should be satisfied:
Bubble Flow:
vsG
< Lb ;
vm
Slug Flow:
vsG
> Lb , NvG < Ls ;
vm
Transition Flow:
Lm > NvG > Ls ;
Mist Flow.
NvG > Lm .
Where:
v2m
Lb = 1.071 (0.2218 ) but 0.13;
d
NvG vsL
Ls = 50 + 36 ;
vsG
NvG vsL 0.75

Lm = 75 + 84 ,
vsG
and: 0.25
L
NvG = vsG .
g
Dependence of pressure loss calculation of flow pattern.
Bubble Flow.
Liquid holdup (EL liquid holdup) is determined by:
s
2
1 vm vm vsG
EL = 1 1 + 1+ 4 ,
2 vs vs vs
where (vs ) is the slip velocity and is considered constant with a value 0.8 ft/s. Mixture
density is calculated as:
m = L EL + G (1 EL ).

Having obtained the mixture density, the hydrostatic head component of the total pressure
gradient is:
g
PH = m sin.
gc
The friction factor f for bubble flow is obtained from standard methods using pipe roughness
and Reynolds number, Rem :
1488L DvsL
Re = .
L EL
Pressure loss due to friction is calculated as:
2
vsL
f L EL
PF = .
2gc D
Slug Flow. Mixture density is expressed as:
L (vsL + vs ) + G vsG
m = + L ,
vm + vs
where vs is bubble rise velocity, and given by:
p
vs = C1C2 gD
where C1 is a function of the Reynolds number ReS and C2 is a function of Reynolds

number ReL . These variables can be expressed as:
1488L vs D
ReS = ;
L
1488L vm D
ReL = .
L
Because of relation between vs and ReS it is necessary iterational procedure to calculate vs .
The following are the steps to calculate vs :

1. Assume that vs = 0.5 gD;
2. Determine ReS using current vs ;
3. Calculate vs from equations (1) (3);
4. Compare vs assumed and vs calculated. If they are not close enough repeat steps 2
4.
If ReS 3000:
vs = (0.546 + 8.74 106 ReL ) gD
p
(1)
If ReS 8000:
vs = (0.35 + 8.74 106 ReL ) gD
p
(2)

If 3000 < ReS < 8000:

s !
13.59L
vs = 0.5 + 2 + (3)
L D
= (0.251 + 8.74 106 ReL ) gD.

p
can be determined from the following equations according to some conditions. Contin-
uous phase-oil:
If vm < 10:
ln(L + 1)
= 0.0127 0.284 + 0.167 lnvm + 0.113 lnD.
D1.415
If vm 10:
ln(L + 1)
= 0.0274 + 0.161 + 0.5699 lnD + X;
D1.371
where
ln(L + 1)
X = lnvm 0.01 + 0.397 + 0.63 lnD .
D1.571
Continuous liquid phase-oil:
If vm < 10:
lnL
= 0.013 1.38 0.681 + 0.232 lnvm 0.428 lnD.
D
If vm 10:
lnL
= 0.045 0.799 0.709 0.162 lnvm 0.888 lnD.
D
The value of is restricted by the following limits:
If vm < 10:
0.065vm .
If vm > 10:
vs m
1 .
vm + vs L
Pressure change due to the hydrostatic head:
g
PH = m sin.
gc
Pressure loss due to friction is given by:
f L v2m

vsL + vs
PF = + .
2gc D vm + vs
Transition Flow.
In transition flow regime pressure gradient is given by linear interpolation between limits of
bubble flow and mist flow regimes. Pressure gradient in transition flow is given by:
P = Mslug + (1 M)mist ,

where
Lm NvG
M= .
Lm Ls
Mist Flow.
Gas phase is continuous in this flow regime. It is assumed that slip velocity is 0, that is we
have homogenous flow. Mixture density is given by:
vsL vsG
m = L + G .
vm vm
Mixture density can be used now to calculate pressure change due to the hydrostatic head:
g
PH = m sin.
gc
Pressure loss due to friction is given by:
f G v2sG
PF = .
2gc D
Friction factor f is determined using Reynolds number:
1488G vsG D
Re = .
G
6.3.6 Gray correlation

Although Gray correlation was developed for vertical flow ([17]), we have implemented it
in both vertical and inclined pipe pressure drop calculations. To correct the pressure drop
for situations with a horizontal component, the hydrostatic head has only been applied to the
vertical component of the pipe while friction is applied to the entire length of pipe.
The Gray correlation uses three dimensionless numbers:
2 v4
NS m
N1 = ;
g (L G )
gD2 (L G )
N2 = ;

730Rv
N3 = 0.0814 1 0.0554 ln 1 + ,
Rv + 1
where:
vsL
Rv = .
vsG
And surface tension is given by:
QO O + 0.617QW W
= ,
QO + 0.617QW
6.3.6. Gray correlation 236

where O and W surface tension between gas/oil phases and gas/water correspondingly.
The liquid holdup is calculated as follows:
EL = 1 (1 CL ) (1 exp( f1 )),
where:
205 N3

f1 = 2.314 N1 1 + .
N2
Once the liquid holdup (EL ) is calculated it is used to calculate the mixture density (m ):
m = EL L + (1 EL )G .
The mixture density is, in turn, used to calculate the pressure change due to the hydrostatic
head of the vertical component of the pipe or well:
m g sin()
PH = .
144gc
The Gray Correlation assumes that the effective roughness of the pipe (ke ) is dependent
on the value of (Rv ) and k is absolute pipe roughness. The conditions are as follows:
if Rv 0.007, then
ke = k0 ;
if Rv < 0.007, then
k0 k

ke = k + Rv ,
0.007
where:
28.5
k0 = ;
NS v2m
vsL
Rv = .
vsG
The effective roughness, ke , must be larger than or equal to 2.77 105 .
The relative roughness of the pipe is then calculated by dividing the effective roughness
by the diameter of the pipe. The Fanning friction factor is obtained using the Chen equation
and assuming a Reynolds Number (Re) of 107 . Finally, the expression for the friction
pressure loss is:
2 f v2m NS L
PF = .
144gc D
6.3.6. Gray correlation 237

6.3.7 Aziz, Govier and Fogarasi correlation

Aziz, Govier and Fogarasi ([11], 1972)proposed a multiphase flow correlation that was de-
pendent on the flow regime. This correlation type has some theoretical justification and is
considered to be one of the least empirical correlations available.
The flow regime identifying.
Four flow regimes are considered: Bubble, slug, transition, and annular-mist (see figure
below).
The flow regimes are identified with the following variables:

1/3 72 1/4
G L
NX = vsG ;
0.0764 62.4 L
1/4
72 L
NY = vsL .
62.4 L
NX and NY give the location within the flow map while the boundaries of the flow
regimes are given by:
B12 = 0.51(100NY )0.172 ;
B23 = 8.6 + 3.8NY ;
B34 = 70(100NY )0.152 .
The flow regimes may be identified as follows:
Bubble Flow:
NX < B12 .
Slug Flow:
B12 < NX < B23 and NY < 4;
B12 < NX < 26.5 and NY > 4.
Transition Flow:
B23 < NX < B34 and NY < 4.
6.3.7. Aziz, Govier and Fogarasi correlation 238

Annular-Mist:
NX > B34 and NY < 4;
NX > 26.5 and NY > 4.
Flow-Pattern map proposed by Aziz, Govier, and Fogarasi is presented in the figure:
Pressure calculation due to flow regime.

Bubble Flow.
The liquid holdup as (EL liquid holdup) defined as:
vsG
EL = 1 ,
vBF
where:
vBF = 1.2vm + vBS ;
L g(L G ) 1/4

vBS = 1.41 .
L2
density (m ):
m = L EL + G (1 EL ).
head:
g
PH = m sin.
gc
The friction factor is obtained from standard methods using pipe roughness and Reynolds
number, Rem :
L Dvm
Re = .
L
f m v2m
PF = .
2gc D

Slug Flow.
The density component in the slug flow regime uses the same definition for liquid holdup
and vBF employed in the bubble flow regime. However, vBS is defined as:
gD(L G ) 1/2

vBS = C
L
where:
3.37 NE
C = 0.345 1 exp(0.029NV ) 1 exp
m
gD(L G )
NE =
L
1/2
gD3 (L G )
NV =
L
where m in expression for C is evaluated as follows:
if NV 18, then m = 15;
if 18 < NV < 250, then m = 69NV0.35 ;
if NV 250, then m = 10.

Having obtained the liquid holdup, the hydrostatic head component of the total pressure
gradient is:
g
PH = m sin.
gc
The friction factor f is obtained from standard methods using pipe roughness and Reynolds
number, Rem :
L Dvm
Re = .
L
f L EL v2m
PF = .
2gc D
Transition Flow.
The transition flow region is, as the name indicates, a region of transition between the slug
flow region and the annular-mist flow region. The transition flow region is, as the name
indicates, a region of transition between the slug flow region and the annular-mist flow
region. The interpolation is performed as follows:

B34 NX NX B23
Ptrans = Pslug + Pmist .
B34 B23 B34 B23
Annular-Mist.
For modeling the annular-mist flow regime it is assumed that the high gas velocity of the

annular-mist region would allow no slippage to occur between the phases. The mixture
density used to calculate the density component is, therefore, the no-slip density, NS . The
expression for the density component is:
g
PH = NS sin.
gc
The friction component for the annular-mist region is based solely on the gas phase and is
given by:
G f v2sG
PF = .
2gc D
where the Moody friction factor f is based on the Reynolds number of the gas:
1488G DvsG
Re = .
G
Duns and Ros method is based on suggestion that the pipe roughness was altered by the thin
layer of liquid on the wall of the pipe. Two variables are used to characterize this effect. The
first is a form of the Weber number:
G v2sG
NW E = ;
L
and the second is dimensionless number based on liquid viscosity:
L
N =
L L
Duns and Ros proposed the following relationship to model the relative roughness:
if NW E N 0.005
0.0749L
=
D G v2sG D
if NW E N > 0.005
0.3713L
= (NW E N )0.302
D G v2sG D
The value of the relative roughness D is constrained to be no less than the actual relative
roughness of the pipe and no more than 0.5.
6.3.8 Mukherjee & Brill correlation

To calculate pressure change via Mukherjee & Brill correlation ([15]) it is necessary to de-
termine flow pattern at first, and then to calculate pressure change by formulas for according
regime.
Flow-Pattern prediction.
The following procedure to determine flow regime is used:
6.3.8. Mukherjee & Brill correlation 241

The bubble-slug transition equation for upflow (NLvBS ). Lets define several values:
0.25
L
NLv = vsL 2 ;
g 0.00010197
0.25
L
NGv = vsG 2 ;
g 0.00010197
0.25
1
NL = 0.001 L 2 .
g L (0.00010197 )3
Calculate dimensionless value NLv
2 +3.695N }
NLvBS = 10{log NGv +0.94+0.074 sin 0.855 sin L
.
The slug-annular mist transition equation: NGvSM .
0.329 }
NGvSM = 10{1.4012.694NL +0.521NLv .
Equation of transition bubble-slug for downhill or horizontal flow is given by:
2 sin }
NGvBS = 10{0.431+1.132 sin 3.003NL 1.138 log NLv sin 0.429(log NLv ) .
Equation of transition of stratified regime for downflow horizontal flow is given by:
2 3.925 sin2 }
NLvST = 10{0.3210.017NGv 4.267 sin 2.972NL 0.033(log NGv ) .
The following scheme is used to determine flow pattern:

Estimation for liquid volume fracture.

The liquid holdup (EL liquid holdup) data were correlated with an equation of the
form: " #
N c5
EL = exp (c1 + c2 sin + c3 sin2 + c4NL2 ) Gv
c6
NLv
Coefficient C1 , ...C6 are taken from the table below:
Uphill Downhill Stratified Downhill Other

c1 -0.380113 -1.330282 -0.516644
c2 0.129875 4.808139 0.789805
c3 -0.119788 4.171584 0.551627
c4 2.343227 56.262268 15.519214
c5 0.475686 0.079951 0.371771
c6 0.288657 0.504887 0.393952
Pressure loss calculation.

Bubble and Slug Flow.
Pressure gradient for bubble flow and slug flow is determined from:
f m v2m
2D + m ggc sin
P =
1 Ek
where
m vm vsG
Ek =
p
The friction factor, f , is obtained from standard methods using pipe roughness and Reynolds
number, Re:
1488NS Dvm
Re =
NS
Annular Flow.
A ratio of liquid fraction to liquid holdup is calculated as:
CL
ER =
EL
Using the value of (ER ), the value of factor of liquid fraction ( fR ) can be estimated by the
following:
if ER 0.01, then fR = 1.0;
if 0.01 < ER 0.2, then fR = 0.1053ER + 1.0011;
if 0.2 < ER 1, then fR = 2.1863ER3 5.7901ER2 + 4.2488ER + 0.3561;
if ER > 1, then fR = 1.0.

Friction factor is given by:

f = fR fNS ,
And pressure gradient for annular flow is calculated as:
f m v2m
2D + m ggc sin
P = .
1 Ek
Stratified Flow.
Pressure loss values for this flow can be calculated from a steady-state momentum balance
on the gas and liquid phases:
dP g
AG = (wG PG + iWi ) G AG sin ;
dL gc
dP g
AL = (wL PL + iWi ) L AL sin ;
dL gc
Lets define some geometrical parameters::
2hL
= 2 cos1 (1 );
D
s 2
hL hL
Wi = 2D ;
D D
1
EL = ( sin ).
2
Hydraulic diameters for the gas and liquid phases can be defined by
( sin )
DEL = D ;
+ 2 sin( /2)

2 ( sin )
DEG = D .
2 + 2 sin( /2)
Perimeter of gas phase is given by:

PG = 1 P,
2
and total perimeter:

P = PG + PL .
The wall shear stresses can be evaluated by assuming a single-phase flow to occur in the
cross section occupied by a given phase:
4 fL L v2L
wL = ;
2g
4 fG G v2G
wG = ,
2g
where fL and fG based on Reynolds numbers of liquid and gas phases.
Pressure loss can be calculated as
1
P = ((wL (D PG ) + wG PG ) + (L AL + G AG )sin).
A

7.1. Reasons for the difference in calculation results tNavigator-4.2
7 FAQ
In this section we have the overview of interesting questions:
Reasons for the difference in calculation results 7.1.
What is the "right" answer in hydrodynamic simulation 7.2.
How to speedup model calculation without its simplification 7.3.
7.1 Reasons for the difference in calculation results

In this section is given brief description of reasons for difference of tNavigator calculation
results on various number of cores and difference between tNavigator calculation results and
other simulators.
Full description of notion right answer in dynamic modelling is given in section 7.2.
This section gives a detailed answer to the following questions:
Model was calculated by tNavigator on different numbers of cores. We have different

values of oil, water, gas production. Why does the answer depend on the number of
cores? Which answer is correct?
Model was calculated by tNavigator and other simulator. All the keywords in the model
are supported by tNavigator, and there are no tNavigator-specific keywords that other
simulator doesnt support, but difference in the results is significant. Why? How can I
match together the results of tNavigator calculation and another simulator?
Usually, visible differences between tNavigator calculations on different number of cores

and differences between tNavigator and another simulators calculation take place in models
where there are:
group controls;
economical limits WECON (see 12.18.62), GECON (see 12.18.102);
keywords ACTION (see 12.18.131), ACTIONG (see 12.18.132), ACTIONR (see

12.18.133), ACTIONW (see 12.18.134), ACTIONX (see 12.18.135);
well control mode is THP and VFP table number can change in case if user-defined
ACTION condition takes place;
keywords UDQ (see 12.18.138).

Difference in results in many cases occurs due to the fact that these keywords are triggered
at different times in tNavigator calculation on different numbers of cores (or at different
times in tNavigator calculation and another simulator calculation). Significant difference in
calculation can be obtained especially if we have long time steps.
7. FAQ 246
Example
DATES
1 JAN 2020 /
1 JAN 2021 /
1 JAN 2022 /
/
In the example the given length of time steps is one year. In the calculation process they
are divided into small computational steps.
If the keywords (that are listed above) trigger at different times, then it can lead to the situa-
tion when the well is closed in one case, but continues its operation otherwise.
Example 1 of possible difference in calculation results.

In the model there is one production well. We specify the economic constraint WECON
(see 12.18.62), the well will be shut if it exceeds 90% watercut. We calculate on 4 cores.
On the N-th time step the watercut is 90.00%. We calculate on 10 cores. The watercut is -
89.99%.
As a result, the well is shut on 4 cores calculation, by continues to produce in 10 core cal-
culation. If this well rate is 30 cubic meters per day (and restrictions on the time step length
is not set), the simulator immediately steps on 100 days (default maximum time step is 100
days DTMAX in RUNCTRL (see 12.18.119)). In this case, fluid production from these two
options will vary by 30 cubic meters * 100 days = 3000 cubic meters. Water cut is 90%, so
this means 300 cubic meters of oil.
Example 2 of possible difference in calculation results.

In the model there is user-defined condition for ACTION (G, R, W, X).
Example
DEFINE WUVFPTAB (WUVFPTAB 'W*'+(WUVFPTAB 'W*'< 5)*(WTHP
'W*'>45)+(WUVFPTAB 'W*'== 5)*(WGOR 'W*'> 1200)+(WSTAT 'W*'== 4))
This condition can have significant influence on calculation results. The reason is that
when THP exceeds 45 atmospheres and GOR exceeds 1200 then the VFP table number
and well limits will be changed. Even a small fluctuation within the accuracy of numerical
solution can lead to the fact that in one case the operation is triggered, and in other no. Ac-
cordingly, the operation at different times can have significant influence on calculation results.
Question: Why does the answer depend on the number of cores?

The reason of different results on different number of cores is: the quality of number
rounding and the preconditioner quality depend on the number of cores (preconditioner is the
special matrix, which is constructed for solving systems of linear equations).
An example of different number rounding.
Let there are 4 numbers to sum a, b, c, d .
a + b + c + d non-parallel programme code (for one core).
7.1. Reasons for the difference in calculation results 247

(a + b) + (c + d) parallel programme code for two cores. In parentheses different

cores sum numbers.
The answer will be different because of rounding. Both answers are correct.
Question: At what number of cores we obtain the most accurate result?

The question is not correct. All results are accurate and correct and they form a set
of solutions. Any result inside the particular area is also a solution. We shouldnt call one
number a correct solution. A solution is a set of solutions.
Uncertainty is present in the initial data. For example, we can construct a model porosity
cube (from LOGs) different ways by using different interpolation methods. In fact, these
will be different variants of one model. The uncertainty generated by numerical methods for
solving systems of equations is significantly less than the uncertainty in the input data.
Simulator does not solve the equations precisely. There is a numerical error in the solution
(residual). It may be distributed differently on a different number of cores. However, even a
small deviation in the solution on a specific step may lead to large differences in the results
in the next step if the complex ACTION and economic constraints are used. The difference
may be in the thousandth percent, but in one case the conditions have been triggered, and in
the other no. Further the results dont match (see examples above).
In this case we observe a model sensitivity to a particular combination of group controls,
economic constraints and ACTIONs. Simulator works correctly in both cases.
Thus, it is not correct to say that one or the other calculation result is more correct.
Within the task of production forecasting it is logical to consider all the options as equally
correct. The forecast itself is an estimation.
Question: What calculation result should I take?

In our opinion, all results are equal and correct, you can choose any one you like. As for
the choice of one variant of the two equal variants, we would advise to choose calculation on
the maximum available number of cores. It is the fastest. Taking into account the shortage of
time, this calculation can be considered as the best.
Question: How can I match together the results of tNavigator calculation and
another simulator?
If necessary, the sensitivity of the model to the conditions in SCHEDULE can be reduced
by specifying restrictions of the maximum time step length. In tNavigator this can be done
via the command:
Example
RUNCTRL
DTMAX 1 /
/
where DTMAX maximal allowed time step (days).

You should set in TUNING (see 12.18.114) maximum time step 1 day to calculate your

model by another simulator.

For the correctness of comparison run calculations on one core.
Most probably the results of calculations will match together. However, in this case
calculation time may significantly increase due to increase of the number of steps.

7.2. The correct answer in dynamic modelling tNavigator-4.2
7.2 The correct answer in dynamic modelling

In this section well identify some of uncertainty factors that influence the dynamic problem
solution. The solution "sensitivity" to
maximal time step limit,
linear and non-linear problem convergence tolerance,
number of cores used
will be analyzed.
7.2.1 Problem discretization and solution

We are finding solution of differential equations system 2.1.
Standard three-phase three-component isothermal filtration problem(black-oil) taking into

account compositional in main variables molar densities.
Algorithm to find solution:
Time approximation (fully implicit) half-discrete scheme

Space approximation (finite volumes to fulfil conservation) a system of non-linear
equations on each step

Newton method a system of linear equations on each iteration of Newton

BCGStab or GMRES algorithms with preconditioners to solve system of linear equations
with non-symmetric matrix calculating preconditioner on each linear system solution
iteration
Parameters which influences calculation
Time step there may be limits on min and max step, and parameters controlling
automatic step choice.
7.2. The correct answer in dynamic modelling 250

Non-linear problem solution parameters accuracy, minimal and maximal Newton

iterations number.
Linear problem solution parameters choice of algorithm, its parameters, accuracy,
min and max number of of iterations.
Well equations solution parameters accuracy, number of Newton iterations when wells
may be switched to other controls.
Group control parameters accuracy, max number of iterations.
Surface network parameters accuracy to satisfy conditions, max number of iterations.
Linear problem solution
The linear problem looks like

Ax = b,
where A is matrix, b the right-hand side. The simplest solution of this problem is given
by minimal residual method, the ancestor of generalized minimal residual method (GMRES).
The algorithm looks like
xk+1 xk
+ Axk = b
k
Where iterational parameter k is chosen to minimize the length of residual
rk+1 = b Axk+1 , kb Axk+1 k min

as
(rk , rk )
k =
(Ark , Ark )
where (, ) vector scalar product.
The common traits of all linear problem solution algorithms:

new solution xk+1 is a subtraction of previous solution and residual with multiplier :
xk+1 = xk k rk
So, the new solution is very sensible to the value of k .
The norm of residual (sum of squared elements) is minimized,
s
n 2
k+1 k+1
kr k = ri
i=1
so the residual (and the error) goes to zero in average, and the residuals in some
blocks (usually near well perforations) may be higher than in other blocks. Different
methods minimize different norms, so there may be different answers for wells even
for the same accuracy.
7.2.1. Problem discretization and solution 251

Figure 10: Work is distributed evenly between all cores
7.2.2 Influence of the number of cores

Parallel calculation
With parallel calculation, the work is distributed evenly between all cores picture 10.
If there are no rounding errors, the result of the above minimal residual algorithm co-
incides with non-parallel version. When the so-called preconditioners are used to speed up
convergence, the structure of preconditioner will depend on number of cores and the solution
will be a little different.
Influence on the result
Scalar product calculation

Iterational algorithms are very sensitive to iterational parameter tau. Its calculated from
vector scalar products.
Let n vector length, p core numbers, each core working with vector elements from
ni to ni+1 , n1 = 1, n p+1 = n. Sum of products will be calculated as:
!
n p ni+1
one core: (a, b) = ai bi , p cores: (a, b) = aibi
i=1 k=1 i=ni
Due to differences in rounding error summation, the answer is different! The answer will be
different even on one core, if we sum the item in different order.
Rounding error
Machine accuracy is maximal such that 1 + is 1. On most modern computers this
is 1016 , characterising density of real numbers near 1. If we know it, we can calculate
difference between two numbers at any point. For example, 1016 + 1 is equal to 1016 .
7.2.2. Influence of the number of cores 252

Figure 11: Different answers.
Solution calculation
So, for different number of cores well get different values of and, hence, different
solutions.
Which of them is most correct? None! They are all equally correct and all are solutions.
Reserves calculation
Another example: reserves calculation. Let s = (si ) be reserves in any grid block. In this case
the reserves will be
!
n p ni+1
on one core: S = si , on p cores: S = si
i=1 k=1 i=ni
Due to differences in rounding error summation, the answer is different

Which reserves are most correct?
Calculating well, group, network production

The same way renumbering of items in the sum influences the result. Remember that solution
accuracy is largest in wells with wells and depends on number of cores due to preconditioner.
What to do to get the correct answer?

Nothing! All these results are correct. The answer (for example, field production) is not
a number, but a numeric interval picture 11.
This uncertainty interval due to calculation is much smaller than the uncertainty due to
initial data.
7.2.3 Influence of timestep

Calculation and reporting steps
7.2.3. Influence of timestep 253

Figure 12: Rate at reporting step
Often during one reporting step (where the well conditions are set) the simulator passes
several calculation steps, the size of these steps is chosen to optimize approximation and
convergence picture 12.
The well rate on a reporting step is rate on step 3 (picture 12). As a result, well rate
depends on time step sizes during reporting step.
Current indices uncertainty
The simulators report all current measurements (such as rates, water cut, BHP etc) for
last calculation step during current reporting step, so the values depend on size and number
of calculation steps during current reporting step. This is a function of:
Limits on Max and Min timesteps.
Settings of non-linear and linear problem solution accuracy, iteration number limits,
linear system algorithm choice.
Number of cores used since linear problem solution algorithm changes.
Instead of Current data, it is better to use either Cumulative, or Average for this step. For
example, average rate for the step is cumulative production during this time step divided on
its length.
The current well modes are uncertain
If the well has several limits, like, liquid production, BHP and THP, these limits are
checked on each calculation time step. As a result, for different calculation settings, there
will be different timesteps and different well switch times.

Well closure time is uncertain
If the limits make the well shut in (like, BHP above block pressure), for different time
steps the well may be shut in at different moments of time. In this case, the cumulative
indices also change.
Conditions checked on calculation time steps
If some condition is checked on every time step, and if it is fulfilled, the well regimes
change, then at moments depending on the following settings:
Min and Max timestep limits,
Non-linear and linear problem settings,
Number of cores
The model behavior can change by a jump . This is how small rounding errors produce
large differences in calculation.
Example.
Economic limits WECON (see 12.18.62)
Typical case: well water cut or Gas-oil ratio is checked and the well is closed (WECON
(see 12.18.62)). Here two uncertainties influence:
Current value of parameter is used;
Its checked on calculation time step.
As a result of WECON, global model changes the well or perforations close.
Example.
On January 1 well has water cut 99.01% on 1 core and 98.99% on 8 cores. In the first case,
well is closed, in the second it may work one more year (calculation step) and produce 100
m3 of oil, thats 30% of its yearly production on previous year
Which answer is more correct?
How do we cope with this uncertainty?
As with one of possible scenarios.
How to reduce uncertainty?
Calculate several scenarios, with different maximal time step limits.

Use WTEST (see 12.18.158), designed to reduce uncertainty influence on global model
(well closure). The WTEST (see 12.18.158) may reopen the well. Also, its checked
on calculation time steps so its subject to uncertainty too.
Compensation WCONINJP (see 12.18.38)
Injection well rate is calculated from production well rates. There are two uncertainties:
Current parameter value used;
The check is on calculation timesteps.
The result is global model change, because injection well regime changes.
Group control GCONPROD (see 12.18.72)
Group production is distributed between wells members of group. There are several
uncertainties:
current parameter value used;
the check is on calculation timesteps;
wells in group can be calculated by different cores, then answer depends on order of
summing.
The result is global model change, because injection well regime changes.
Group control and others
Economic limits for groups;
Surface networks;
Triggers (ACTIONX (see 12.18.135)).
ACTIONX (see 12.18.135) can generate most unstable calculations since it can set:
Well mode changes,
Group mode changes,
Surface network regime changes,
based on current value of parameter on one well. This global model change due to one
current value of parameter on calculation time step is really a winner among all instability
and uncertainty options.

7.2.4 What can we do?

We should change the definition of solution.
The oil production depending on time is not a one graph, but a set of graphs, showing
the uncertainty of this solution. All the graphs in this band are solutions picture 11.
Sensitivity analysis
We should check the solution sensitivity to changes in calculation parameters. In other

words, we should check
Sensitivity to time step size limit,
Sensitivity to accuracy of linear and non-linear problem increase,
Sensitivity to number of cores.
We should check the solution sensitivity to changes in model parameters.. There are many
of them. Check at least those that may be automated easily:
Sensitivity to relative permeability end-points,
Sensitivity to layer permeability increase,
Sensitivity to GOC and WOC.
7.2.4. What can we do? 257

7.3. How to speed-up model calculation without its simplification tNavigator-4.2
7.3 How to speed-up model calculation without its simplification

In this section we analyse the problem how to speed-up model calculation without its sim-
plification or increasing computing capacity. We will discuss the effect of model data quality
at the time of its calculation, which follows from the mathematical model and approximation
conditions.
We will analyse examples and give recommendations on model optimization.
What affects the calculation time

CPU frequency;
the number of processors;
speed of simulator;
the number of active blocks in the model;
model physics;
the complexity of the field development scenario.
7.3.1 Problem statement

How to calculate THIS (picture 13) fast?
Figure 13: Model with big number of LGRs
A simple way to reduce the time: Instead of the compositional model with 15 compo-
nents, dual porosity, dual permeability, 30 LGRs on each of 1000 multisegment horizontal
7.3. How to speed-up model calculation without its simplification 258

wells with gas re-injection through one of the stages of the multistage separator with surface
network and 15 million active grid blocks calculate two-phase black oil model with all
vertical wells and 100 thousand active grid blocks on the high-speed cluster.
Motivation to speed-up:
improve life quality of reservoir engineer;
opportunity to make sensitivity analysis;
the possibility to do manual or assisted history matching.
What can be improved without model simplification:
quality of the input data this is ageless problem usually reservoir engineer
cant change it;
quality of the model how to do your work perfectly using existing data.
Lets analyze the possible improvements of model quality.
7.3.2 Flow through the block

The simplified formulation of the mixture approximation in the block: the flow during one
step does not exceed the pore volume of the block.
Block number 1 2 3
Flow between blocks 10m3 /day 10m3 /day 10m3 /day
Block pore volume 1000m3 1m3 1000m3
Figure 14: Blocks with different pore volumes
What slows down the simulation:

Large ratio of the flux through the block face to the pore volume. A large amount of
fluid is flowing through a small pore volume so it will lead to significant pressure increasing
7.3.2. Flow through the block 259

in the block.
The presence of blocks with small pore volume doesnt slow down calculation. The big
variation in pore volumes slows down calculation - picture 14. If during the time step
the volume of the fluid that is passing through the grid block is significantly larger than its
volume, then the time step will be reduced, calculation will be slower.
How to deal with this problem:
1. Reduce the pore volume variation.
2. Reduce the flow through the block faces.
So the time step length will be increased according to approximation conditions.
Pore volume variation.

An example how to find the blocks with small pore volume picture 15. Create User
Cut for pore volume. In Map arithmetic command line enter porv < 1 (minimal pore volume
can be different for different models; it can be equal 1 or 10 as well). Apply. Use Cut for
visualization. Press the button Statistics. The value in the box Entries, is equal to the number
of blocks with small pore volume that are selected via Cut.
Figure 15: Cut for blocks with small pore volumes

Resources in blocks with small pore volume.

How to calculate resources in these blocks picture 16. Go to map Resources. Oil in
place. Cut should be switched on for visualization. In Statistics in the box Sum we can see
the value of sum of oil resources in these blocks.
Figure 16: Resources in the blocks with small pore volume
Removal of the blocks with small pore volume.

In the section GRID we add the keyword:
MINPV
1 /
The keyword MINPV (see 12.2.30) makes blocks with the pore volume less then specified
value inactive. So the variation of the pore volume is decreased. The value of minimal pore
volume should be chosen for each model independently.

7.3.3 Grid connection

If we have in the model parts of the grid that are not connected to each other and there are no
well perforations in these parts, then they can be excluded from the grid to speed-up model
calculation.
How to select model parts that are not connected to each other - picture 17.
User Maps. Map. Right mouse click on the Map to open Model Editing. Choose the tab
Connected Components, Show all connected components.
Figure 17: Marking out connected components
These components can be excluded via the keyword ACTNUM (see 12.2.29).
Select the components via User Cut (Cut can be created via depth, layer number in Z
direction, values of User map Map etc). In main model part we assign value 1 to blocks. In
components, that are not connected and we want to exclude, we assign value 0 to blocks.
Right mouse click on Cut and choose Export. Save 3D to ACTNUM. Then the saved file
should be included into GRID section via the keyword INCLUDE (see 12.1.73).
7.3.3. Grid connection 262

7.3.4 Grid stratification factor

In case of high grid stratification factor we recommend to increase connection.
For existing pore volume the flow can be reduced by increasing blocks connections to
neighbouring blocks. Now we consider only the holes, arising from pore volume cut-off
picture 7.3.4.
Additional connections for blocks.

Due to the dominant gravitational component it is particularly important to make vertical
connections. They can be introduced using the keyword PINCH (see 12.2.54).
PINCH
/
Lateral links through the blocks with zero permeability.
Look at the picture 18. Well has a perforation in the block 1. If permeability in the block
2 is equal to zero, then the production from the block 3 is impossible.
Figure 18: The permeability of the neighboring blocks
This problem can be solved using lateral links through the blocks with zero permeability
via the keyword PERMAVE (see 12.2.36). In this case averaged permeability will be used in
7.3.4. Grid stratification factor 263

transmissibility calculation.
Picture 18. The usage of averaged permeability in transmissibility calculation will help
to produce fluid from block 3 (permeability in block 2 is equal to 0). Using averaging the
permeability of block 2 will be small but not zero, that will provide the flow from block 3
to block 1, where we have well perforation.
We should add to the model:
PERMAVE
1 1 -1 /
Then:
1 Ki + K j
Ki j = or Ki j =
1 1 2
+
Ki K j
7.3.5 Influence of smoothness of the data

On the pictures 19 and 20 there are examples of relative permeability curves and capillary
pressure, the usage of which in the model can lead to calculation slow down. There is a jump
on the curve of parameter.
Figure 19: Jump on the capillary pressure curve
With a large jump on the curve the value of the derivative of this parameter will be very
large as well, that can slow down the calculation.
The detailed description of system of equations is in the section Transition from physical
model to system of equations.
We can briefly mention here, that derivatives matrix is used in the solution process.
7.3.5. Influence of smoothness of the data 264

Figure 20: Jump on RP curves
The resulting system of equations (after approximation) is a non-linear system of algebraic

equations of the form
F(p, N1 , . . . Nnc ) = 0
where p = (pi ), Nc = (Nci ) values in grid blocks. Standard Newton method is used to
solve non-linear system of equations F(U) = 0, U (p, N):
1
F(U m )

m+1 m
U =U F(U m )
U
Where F(U m )/ U matrix R(1+nc )N R(1+nc )N R(1+nc )N , N number of grid blocks.

At each step of Newtons method it is necessary to solve the system with asymmetric ma-
trix F(U m )/ U . The better the matrix (e.g., closer to the diagonal), the faster the solution.
So, what is bad for the calculation speed:
High values of derivatives (pictures 19, 20);
A large number of points of discontinuity of the derivatives (picture 21).
Lets discuss where a large number of points of discontinuity of the derivatives comes
from.
On the picture 21 there are RP curves specified via tables SWOF (see 12.6.1), SGOF (see
12.6.2). In this case RP is specified in certain points and linear function is used between
them. Each interval between two points has its own function. So, the derivative has a large
number of points of discontinuity.
As a solution for this problem we propose to set the smooth RP curves via Corey or LET
correlation using the keywords COREYWO (see 12.6.3), COREYGO (see 12.6.4), LETWO

Figure 21: Convert RP in Corey correlation
Figure 22: Smooth RP curves
(see 12.6.8), LETGO (see 12.6.9). We set only end-points, smooth curve is constructed auto-
matically by taken into account the defined curvature picture 22.
Available tables SWOF (see 12.6.1), SGOF (see 12.6.2) etc. can be converted to Corey
or LET correlation picture 21.
In the menu Document. Approximate RP. Choose Convert to Corey or LET correlation.
After conversion in the USER folder there will be a new file with new RP defined by
keywords COREYWO (see 12.6.3), COREYGO (see 12.6.4) or LETWO (see 12.6.8), LETGO
(see 12.6.9). This conversion may lead to calculation speed up.

7.3.6 Influence of end-points match

RP end points for drainage and imbibition process (hysteresis) must be the same. Please pay
attention on the following messages during model loading picture 23:
Warning: SWU is not equal to ISWU in block[ , , ].
Drainage and imbibition curves for blocks can be analysed in the option Properties. SPR
Water-Oil, SPR Gas-Oil (scaled relative permeabilities).
Figure 23: Unmatched end-points in hysteresis
7.3.6. Influence of end-points match 267

7.3.7 Conservation equation

It is unacceptable to have blocks in different PVT (EOS) regions with a hydrodynamic con-
nection picture 24.
Figure 24: Neighboring blocks with different PVT
Properties in these blocks:

Blocks number 1 2
PVT region 1 2
Oil density in surface conditions 900kg/sm3 600kg/sm3
Oil volume in surface conditions 1000sm3 1000sm3
Oil weight in block 900ton 600ton
Then when fluid flows from one block to another it changes its properties immediately.
In this situation, conservation of fluid volume is possible (while mass is not saved) or con-
servation of mass (then the volume is not saved).
Conservation of fluid volume mass is not saved:
Flowed from 1 Flowed into 2

Oil volume -100sm3 +100sm3
Oil mass -90ton +60ton
Conservation of mass volume is not saved:
Flowed from 1 Flowed into 2

Oil mass -90ton +90ton
Oil volume -100sm3 +150sm3
7.3.7. Conservation equation 268

7.3.8 VFP tables

Non-monotonic VFP tables (picture 25) can slow down calculation significantly if the well
control mode occurs on the problem area. This applies both for THP control mode and to
surface network simulation.
Usage of monotone curves is necessary to provide the correct work of the simulator: one BHP
value should correspond to one THP value. Otherwise, as shown on picture 25, it turns out
that 2 different THP values correspond to one value of BHP, that can lead to the instability
in calculation.
Figure 25: Non-monotonic VFP tables
Please pay attention on the corresponding messages during model loading, and edit VFP
tables if necessary.
7.3.8. VFP tables 269

8.1. License for console tNavigator tNavigator-4.2
8 tNavigator Console version

tNavigator has GUI and console version.
To run console version:
1. Run command prompt: cmd
2. cd path_to_tNavigator-con.exe
3. Usage: tNavigator-con.exe [OPTIONS]... [FILES]...
For example:
tNavigator-con.exe --large-model FOLDER1\OILFIELD.data
This will open model OILFIELD.data (from the FOLDER1) in two-pass mode.
Useful commands in cmd:
cd change directory
Arrow up /down previous or next command
Tab continue the name of the file from this folder
Dir list all files in the current folder
Cd .. go to upper folder
To see help you can run console the following way:
tNavigator-con.exe -h (Print help and exit)
tNavigator-con.exe --help (Print help and exit)
tNavigator-con.exe --full-help (Print help, including hidden options, and exit)
All console version options are listed in the section 8.2.
8.1 License for console tNavigator

Console version always starts work with checking for file license available. It looks in two
standard paths:
1. Console version folder
2. Folder in Application Data like C:\Users\userName\AppData\RFD\tNavigator
8. tNavigator Console version 270

8.2. Console version options tNavigator-4.2
If file license if there, console will use it.
Possible problem: old expired file licenses.

Diagnostics: run console with no arguments (run only tNavigator-con.exe), it will output
information what license its using and where is the license file.
Possible solutions:
go to this folder and delete expired or non-suitable file license;
use argument --license-type and choose proper value: file\usb\network;
use server license, by setting the path to license server explicitly with option --server-
url=PATH.
Console can take network license.

If a network license was successfully installed in tNavigator GUI, it appears in environment
variables.
Check:
MyComputer->Properties->Additional system properties-> Environment variables->local
variable tNavigator_LICENSE_SERVER Check that its set to correct servers license path.
Important: If you change this variable, run a new cmd for console. The console run from
existing cmd will not get new path.
Important: If there is a file license in one of the paths indicated above, even an expired one,
the console will not use server license from the environment variable. By default, the console
will look for server license only if there is NO file license in corresponding paths. This is not
true only if license server path or license type is set directly when console version is called
(using options --license-type or --server-url).
8.2 Console version options

Usage: tNavigator-con.exe [OPTIONS]... [FILES]...
Help:
OPTION Description
-h, --help Print help and exit
--full-help Print help, including hidden options, and exit
-V, --version Print version and exit
Input data:
8.2. Console version options 271

OPTION Description
-c, --continue Continues calculation from last calculated step
(default=off)
--restart=INT Continues calculation from input step or last
calculated step if input step is not calculated
(default=0)
--input=ENUM Input data file format (possible values=e100,
e300, imex, gem, stars, mored. Default=e100)
--large-model Open model in two-pass mode (default=off)
--fast-array-reader=ENUM Use fast array reader (experimental)=on (de-
fault=off)
--single-pass Do not open model in two-pass mode (for MPI
only) (default=off)
--force-first-pass Force first pass in two-pass mode (default=off)
--nousersch Do not read user schedule. (default=off)
--source-dir=STRING Prefix for models directory
--dest-dir=STRING Prefix for results directory
--base-dest-dir=STRING Prefix for base results directory
Client-server options:
OPTION Description
--license-type=ENUM Specify license type. Possible values = file
(file license), network (network license), usb
(usb license)
--no-license-exit Exit with status 69 if there is no license on
first step (default=off)
--license-wait-time-limit=INT How many seconds wait for network license
(default=0)
Interpolation:

OPTION Description
--interpolate-map Enables interpolation if set. (default=off)
--interpolation-method=ENUM Interpolation algorithm to use (possible
values=least-squares, kriging, least-squares-3d.
Default=least-squares)
--interpolation-detalization-x=INT Detalization: block x size (in mesh blocks)
(default=1)
--interpolation-detalization-y=INT Detalization: block y size (in mesh blocks)
(default=1)
--interpolation-silent-mode Do not print per-layer messages (default=off)
--interpolation-alpha=DOUBLE First derivative smoothing extent (default=1.0)
--interpolation-beta=DOUBLE Second derivative smoothing extent (de-
fault=1.0)
--interpolation-source=ENUM Interpolation sources (possible values=wells,
valid-blocks. Default=wells)
--interpolation-geometry=ENUM Geometry for 3D interpolation (possible val-
ues=none, distances, transmissibilities. De-
fault=none)
--interpolation-ignore-vlinks Ignore vertical links in 3D interpolation (de-
fault=off)
--interpolation-tr-threshold=DOUBLE Transmissibility threshold (default=1.0)
--interpolation-novalue=DOUBLE Value to be considered unknown (default=0.0)
--interpolation-default-value=DOUBLE Value for layers without interpolation sources
(default=0.0)
--kriging-type=ENUM Type of kriging interpolation (possible
values=simple, ordinary, universal. De-
fault=simple)
Simulation proccess:
OPTION Description
--nosim Parse and check only. Dont start simulation.
(default=off)
--low Set prioriry to low. (default=off)
--stream-flux=DOUBLE Streamlines density (rate per one streamline)
(default=5.)
--stream-flight=INT Streamlines max flight time (default=50000)
--stop-step=INT Last calculated step. (default=-1)
Parallel computation:

OPTION Description
-n, --cpu-num=number of available Number of computational threads (de-
CPUS fault=number of available CPUS) (default=-1)
--memory-bind-logic=ENUM NUMA bind logic (possible values=off, init,
full. Default=full)
--sync-method=ENUM Synchronization method (possible val-
ues=mutex, barrier. Default=barrier)
--mppn=INT Number of MPI processes running simultane-
ously on each node. (default=1)
Group: thread to CPU bind logic model
OPTION Description
--thread-bind-logic=ENUM Thread bind logic. (possible val-
ues=none, node_uniform, cpu_uniform,
process_to_first_cpus. Default=node_uniform)
--thread-bind-to-cpu=CPU-1,CPU- Where (id of logical CPU) to bind each thread
2,...,CPU-N (N - number of threads). CPU numeration
starts from 0.
Debug:
OPTION Description
--dump-matrix=INT Dump matrix. (default=0)
--drainage-matrix Compute and dump drainage matrix. (de-
fault=off)
--time-detailed=ENUM Display detailed information about CPU us-
age time (possible values="off", "total" (for all
processes at the end of calculations), "all" (for
all processes at each time step) (default=off)
Result files:

OPTION Description
--no-dump-res Dont dump result files. (default=off)
--dump-res Dump res files. Can be used with option
--ecl-dump (default=off)
--summary-only Print to log file only summary information.
(default=off)
--dump-step-summary Print time step summary. (default=off)
--export-avg-maps Export average maps on each step. (de-
fault=off)
--dump-result-files=ENUM Modify set of result files to dump (pos-
sible values=all_on, all_off, mesh_on,
mesh_off, initial_maps_on, initial_maps_off,
step_maps_on", step_maps_off, well_on,
well_off, group_on, group_off, conn_on,
conn_off, frac_on, frac_off, aquifer_on,
aquifer_off, statistics_on, statistics_off, rst_on,
rst_off. Default=all_on)
--ignore-lock Compute model even if *.lock file exists (is
model is calculated by another version of
tNavigator at this moment) (default=off)
--use-rptrst-map-freq Use information about output results map fre-
quency from keyword RPTRST (see 12.1.9).
(default=off)
--ecl-rsm RSM file export for E100/E300 models
Linear solver:
OPTION Description
--linear-solver-alg=ENUM Force use of algorithm for linear solver (possi-
ble values=bcgstab, orthomin, qgmres, dqgm-
res. Default=bcgstab)
--linear-solver-param=INT Parameter (default=15)
--linear-solver-restart=INT Number of iterations before restart (de-
fault=50)
--solver-preconditioner=ENUM Type of linear solver preconditioner (possible
values=ilu_ikj, jacobi, no. Default=ilu_ikj)
Boundary conditions:
OPTION Description
--bc-dont-correct Dont correct boundary conditions if they seem
to be wrong (default=off)
Client/server options:
OPTION Description
--server-url=STRING Url to license server

Eclipse compatibility output:
When binary files are dumped calculation data is saved at calculation time steps. This
option is used for default and casn be switched off using the keyword RPTONLY in SUM-
MARY section (then results will be saved at reporting time steps).
OPTION Description
--ecl-root Dump binary files to model directory. (de-
fault=off, files are dumped in RESULTS
folder)
-l, --ecl-little Switch eclipse binary output to little-endian
format. (default=off)
-d, --ecl-dump Dump UNSMRY, SMSPEC files to model di-
rectory. (default=off)
-e, --ecl-egrid Dump EGRID file. (default=off)
-i, --ecl-init Dump INIT file. (default=off)
-s, --ecl-summary Dump summary information. (default=off)
-r, --ecl-unrst Dump result binary UNRST file. (default=off)
-u, --ecl-unsmry Dump result binary UNSMRY file. (de-
fault=off)
-m, --ecl-smspec Dump result binary SMSPEC file. (de-
fault=off)
--rfd-summary Dump short (FIELD only) SMSPEC and UN-
SMRY files. (default=off)
--ecl-upscaled-dump-xyz=X-scale,Y- Dump Eclipse binary files upscaled along X,
scale,Z-scale Y, Z directions. (default=off)
--ecl-sln Dump streamlines data in SLNSPEC,
SLNxxxx files. (default=off)
Annual summary reports:
OPTION Description
-t, --report-tables Tables for output. (default=off)
TMORE options:

OPTION Description
--dump-converter-maps Use disk space to prevent the memory peak
(default=off)
--dump-intermediate-eclipse Save intermediate eclipse model to data files
(default=off)
--not-dump-intermediate-eclipse-maps Dont save intermediate eclipse model to data
files (default=off)
--dump-intermediate-eclipse-sch Save intermediate eclipse SCHEDULE section
to file (default=off)
--multiple-error-messages Dont hide multiple messages on conversion
(default=off)
GUI:
OPTION Description
--auto-run Run simulation. (default=off)
--auto-exit Exit at end of calculation. (default=off)
--ini-file=STRING Ini file name.
--no-gl Dont use OpenGL (no graphs and maps at
all). (default=off)
--no-gl-vbo Dont use OpenGL VBO. (default=off)
Remote GUI:
OPTION Description
--task-id=INT Task ID on server (default=0)
--dispatcher-ip=STRING Dispatcher IP
--dispatcher-task-port=INT Dispatcher port for tasks (default=0)
Model save:
OPTION Description
--save-model=STRING Save model in eclipse format
--save-scaled-model-xyz=X-scale,Y- Save model scaled by X, Y, Z directions
scale,Z-scale
--split Auto split input models. The pattern is set with
FIPPATT (see 12.4.13) region. (default=off) If
this option is used one needs to set the path
to save the results of splitting. --split <the
path to the folder with patterns model>. For
example, --split=split/variant_1
Client-server options:

OPTION Description
--license-type=ENUM Specify license type. Possible values="file"
(file license), "network" (network license),
"usb"(usb license))
--no-license-exit Exit with status 69 if there is no license on
first step (default=off)
--license-wait-time-limit=INT How many seconds wait for network license
(default=0)

9.1. Results of tNavigator calculation tNavigator-4.2
9 Data files
tNavigator may be started either directly (version with graphical user interface), or from
command line with one argument name of data file <name>.data (console version
section 8).
tNavigator uses the following files:
<name>.data file with initial data, should be passed to the program as an argument.
Initial data file contains description of input parameters. It is written on keyword
language (see 11.1),
<name>.inc files included into data file (if they exist).
Opening a model creates RESULTS and USER folders.

Results of tNavigator calculation section 9.1.
USER folder section 9.2.
In addition to it the following files can be loaded to tNavigator or exported form it

section 9.4.3.
9.1 Results of tNavigator calculation

Results of tNavigator calculation can be saved in the following formats:
tNavigator format files that are saved in the RESULTS folder:
<name>.log text file with report on simulation process. The detailed descrip-
tion of the .log-file is in the section 9.3.
If the model had been calculated, closed and then opened again a new .log file is
written. Old file is saved as <name>.log.old.
Its better to use modes ViewResults/ViewGraphs when you are not going to
calculate the model;
<name>.log.old saved copy of a .log file with results of previous model
opening. This file is created when the model is opened second time;
<name>.err text file with report on all errors in input data and during simula-
tion;
<name>.end text file with number of errors, problems, warnings in the model;
<name>_*.res, binary files with simulation results (pressure and saturation
maps, well modes description, etc.); these files are also used restarting previously
carried out computations (RESTART (see 12.1.14)).
<name>.sdata text file. This file is used when the model in opening in the
modes View Graphs, View Results.
These modes should be used when you are not going to calculate the model.
9. Data files 279

9.1. Results of tNavigator calculation tNavigator-4.2
In these modes you cant change results: i.e., for example, they can not be deleted
or rewritten;
<name>.lock this file is created by tNavigator in RESULTS folder each time
the model is opened for calculation. This protects this model from spoiling the
results by occasional model opening in two different tNavigator versions or from
opening same model from network disk by different users. When the calculation
is complete, and the model is closed, *.lock file is automatically deleted.
If the model was closed abnormally (for example, computer power was switched
off), the lock-file will stay in the RESULTS directory.
So when you open the model you will see a message: "This model is being
calculated by another instance of tNavigator. Opening by this instance may lead
to unexpected results. Do you really want to proceed?"
If you are sure that this model is not opened anywhere else, press Yes in the
dialogue, to continue work with the model.
To avoid confusion, its better to use modes ViewResults/ViewGraphs when you
are not going to calculate the model. In this case results stay unchanged and
lock-file is not created.
<name>.meta, <name>.sum, <name>.rlog and other files from the folder
RESULTS that are not listed above are tNavigator inner files.
Note.
Simulation result binary files produced by tNavigator may be viewed using tNavigator
post-processing environment.
Text files created by simulator may be viewed using any program that can work with
text files.
For default all maps and graphs for all objects are saved at each time step, specified in
the model.
User can manage a record of calculated maps and graphs to the hard disc (record data
only for time steps selected by the user). Thus, the amount of data written to disk, can
be reduced.
The following possibilities are available:
1. Keywords to record data in specified dates RPTMAPD (see 12.17.2), RPT-

GRAPHD (see 12.17.2).
2. Keywords to record data in selected time intervals RPTMAPT (see 12.17.3),
RPTGRAPHT (see 12.17.3).
3. Keywords to record data only for first and last time steps RPTMAPL
(see 12.17.4), RPTGRAPHL (see 12.17.4).
Binary file in E100 format (*.UNSMRY, *.SMSPEC, *.EGRID, *.INIT,

*.RSSPEC, *.UNRST).
The list of the data that should be saved is specified in the section SUMMARY (see
9.1. Results of tNavigator calculation 280

9.2. USER folder tNavigator-4.2
12.17.1). File format is controlled via the keywords MULTOUT (see 12.1.12), UNI-
FOUT (see 12.1.11).
The settings to save maps are saved via RPTRST (see 12.1.9).
See also the keyword RPTONLY (see 12.17.5).
Output of binary files in E100 format can be done from graphical interface of from
console version. The list of available options of the console version is in the section
8.2.
Text RSM-file.
RSM-file can be created from graphical interface, remote graphical interface and con-
sole version.
SEPARATE (see 12.17.7) and RUNSUM (see 12.17.7) set the option to dump RSM
file for models in E100 and E300 formats correspondingly.
In the console version RSM-file can be exported using --ecl-rsm.
From graphical interface, remote graphical interface RSM-file can be exported for
models in all formats: E100, E300, IMEX, STARS, GEM, MORE.
9.2 USER folder

In USER folder will automatically save User files (created when the model is modified), with
changes of phase permeability parameters, PVT, well settings, new wells, fracs, wellbore
zone treatment:
<name>_rp.inc (phase permeabilities - keywords SWOF (see 12.6.1), SGOF (see

12.6.2), COREYWO (see 12.6.3), COREYGO (see 12.6.4) etc., flow functions - key-
words FLOWFUNC (see 12.8.4), FLOWFNAMES (see 12.8.6), proppant properties
- keywords NPROPANTS (see 12.8.1), PROPANTNAMES (see 12.8.2), PROPANT-
TABLE (see 12.8.3));
<name>_pvt.inc (PVT-PVT-parameters - keywords PVTO (see 12.5.4), PVTW (see

12.5.5), PVDG (see 12.5.7), ROCK (see 12.5.16), DENSITY (see 12.5.23) etc.);
<name>_sch.inc (User-added wells, well constraints, hydraulic fractures, wellbore

zone treatment).
User data is saved automatically by default in USER folder: Automatically Save User
Files is checked in tNavigators Settings. Also by default Automatically Read User Files is
checked in the Settings, the next opening of the model will loaded modified properties and
well constraints.
So, properties editing doesnt change initial model files, tNavigator just writes a new
data to the USER folder. Files <name>_rp.inc, <name>_pvt.inc etc. with new values
in the corresponding keywords. These files are read after initial model files. The model
will be visualized and calculated with properties and well data from the USER folder. The
keywords in the USER folder can be edited manually or deleted.
9.2. USER folder 281

9.3. Log-file tNavigator-4.2
9.3 Log-file
In RESULTS folder the file <name>.log is saved text file with report on simulation pro-
cess.
If the model had been calculated, closed and then opened again a new .log file is written.
Old file is saved as <name>.log.old.
Its better to use modes ViewResults/ViewGraphs when you are not going to calculate the
model.
Detalization of the log can be set via the keyword REPORTFILE (see 12.1.3).
The reason of each Newton iteration.
The line of the log-file for Newton iteration looks the following way:
Newton # = 1, |F| = 8.76e+003, MBErrProd = 0.00e+000, MBErrTot = 1.82e-007, dp =

1.28e-004, dN = 1.43e-003, its = 2. (2)
The value (2) at the end is a value of reason.
Possible reasons:
0 first iteration, is always done;
1 in RUNCTRL (see 12.18.119) user set to do the specified minimum number of

iterations and the current number is less than the specified one;
2 criterion of variation of the main variables is not satisfied;
3 modification of saturation is made according to CHOPSAT (RUNCTRL

(see 12.18.119)), one more iteration is required;
4 modification of pressure and (or) molar densities is made, one more iteration is
required;
5 compositional or thermal modifications are made, one more iteration is required;
6 criterion of material balance error for wells is not satisfied;
7 criterion of material balance error for field is not satisfied;
8 criterion of variation of aquifer flow rate is not satisfied;
9 criterion of variation of rates and (or) pressure for wells is not satisfied.
Blocks with convergence problems
The visualization of the map of linear solver residual is available in graphical user inter-
face Calculated Maps. Number of Convergence problems. This map should be requested
9.3. Log-file 282

9.4. Loadable file formats. Export file formats tNavigator-4.2
via the option CONVERGENCE_PROBLEM_NUM of the keyword TNAVCTRL (see 12.1.4).
This method is analogous to CONV RPTRST (see 12.1.9). Option CONV itself is not
supported in tNavigator.
Also there is a possibility to see the most offending blocks the following way:
Example
REPORTFILE
ALL LOW
ITERS DEBUG
/
Study carefully the messages looking like Chop p... or Chop molar density.... If they are
always in the same grid blocks, then you need to understand what speciality or a problem is
in this grid block.
9.4 Loadable file formats. Export file formats

9.4.1 Load Well Data
The following well data can be loaded to the model in the corresponding tabs in Schedule
Files Dialog:
Layers
File type: Layers.
File format .txt.
Data description: layer name; z1-z2 (numbers along Z, to which this layer corresponds).
Example of this file format
Layer_11-1
Layer_22-2
Layer_33-3
Layer_44-4
Trajectories
1. File type: GWTD.

File format .txt.
Data description: measured depth; x, y, z (negative).
9.4. Loadable file formats. Export file formats 283

Well name: WELL1

3335.08379542 50133.99849282 57365.78811816 -3331.36235500
3350.53042953 50131.05636316 57365.30935266 -3346.51853724
3356.13983138 50129.97016088 57365.15669689 -3352.01963798
3364.20096452 50128.40792386 57364.95680241 -3359.92539399
2. File type: Trajectory.

File format .dat.
Data description: well name; X; Y; Z (absolute depth); MD (depth along the well bore).
welltrack WELL1
100 110 2500.0 2500.000
100 110 2510 2510
100 110 2530 2540;
3. File type: LAS.

File format .las.
Data description: Standard las-format (X, Y, absolute depth, measured depth). The order
of the columns can be changed in the emerging dialogue.
9.4.1. Load Well Data 284

~Version Information
#---------------------------------------------
VERS. 1.2:
WRAP. NO:
~Well Information
#--------------------------------------------
#MNEM.UNIT DATA INFORMATION
#--------- ------------------- -------------
STRT.M 10.00: Top Depth
STOP.M 2288.00: Bottom Depth
STEP.M 10.00: Increment
NULL. -999.25: Null Value
UWI. UNIQE WELL ID: 3070010341
WELL. Well: 107L
DATE. Date: 15022009
COMP. Company:
FLD. FIELD NAME:
LOC. LOCATION:
PROV. Province:
SRVC. Company:
~Other Information
#---------------------------------------------
~A
2500 100 110 2500
2510 100 110 2510
2540 100 110 2530
4. File type: Generalized. File format .dev.

Data description: Generalized GWTD format. Well names must begin with WELL-
NAME: (any letters size). The order of the columns can be changed in the emerging
dialogue. Values Z U not negative. It is possible to check the box Reverse Z in the
dialogue.

WELLNAME: WELL1
1.030384e+007 5733795 -135.7 -135.7
1.030384e+007 5733795 -110.7 -110.7
1.030384e+007 5733795 -85.7 -85.7
1.030384e+007 5733795 -60.7 -60.7
1.030384e+007 5733795 -35.7 -35.7
1.030384e+007 5733795 -10.7 -10.7
5. File type: Dip-circle.

File format .trj.
Data description: measured depth, angle (between Z-axis and well vector), azimuth
(angle between Y-axis and well vector in X direction). Well names must correspond to
the file names.
20 0.75 206.50
40 1.00 206.50
60 1.50 206.50
80 4.50 206.50
100 9.75 206.50
120 11.00 205.50
140 13.12 205.50
160 15.25 206.50
6. File type: WellHead.

WellHead file must be loaded if Dip-circle file is loaded.
File format .txt.
Data description: well name, altitude z0 and wellhead coordinates (x0, y0). Columns
and their order can be selected in the emerging dialogue.

40R 57 33025.7 23427.2

3359 54.7 31384.3 20405.9
3405 57.3 30162.1 20212.8
3451 54.7 31386.8 20401.8
3452 61.5 30890.9 21500.9
Groups
1. File type: Well Group.

File format .txt.
Data description: well name; group to which this well belongs.
WELL1 SAT-1
WELL2 SAT-1
WELL3 SAT-2
WELL4 SAT-2
2. File type: Group Wells.

File format .txt.
Data description: group name; wells which belong to this group.
GRUP1 PROD1 PROD2 PROD8 PROD9

GRUP2 INJ1 INJ2 INJ3 INJ4 INJ5
GRUP3 WPR1 WPR9 WPR17
GRUP4 WELSEGM3
Events
File type: Events.

File format .txt.
Data description: well name; date; event; layer; lower depth; upper depth; radius; diameter;

skin; multiplier.
Columns that are in the file should be selected in the drop-down menu. Order of boxes can
be changed (in accordance with the data in the file).
WELL1 1.7.1997 perforation 3354.8 3358.8 0.2 -3

WELL1 1.7.1997 perforation 3383 3390.6 0.2 -3
History
File type: Prod. history.

File format .txt.
Data description: well name; date; oil rate; gas rate; liquid rate; gs injection; water injection;
THP; BHP; well efficiency factor.
Columns that are in the file should be selected in the drop-down menu. Order of boxes can
be changed (in accordance with the data in the file).
V42-1 01.06.1997 18.8 1.7 0

V42-1 01.07.1997 18 0.6 0
V42-1 01.08.1997 16.7 0.5 0
V42-1 01.09.1997 14.4 0.4 0
V42-1 01.10.1997 11.3 0.3 0
Well Logs
1. File type: Well Logs (LAS).

File format .las.
Data description: Standard las-format.

# LAS format log file from PETREL

# Project units are specified as depth units
#===========================================
~Version information
VERS. 2.0:
WRAP. NO:
#===========================================
~Well
STRT .m 1570.2999268 :
STOP .m 1791.7999268 :
STEP .m 0.00000000 :
NULL . -999.250000 :
COMP. : COMPANY
WELL. 1 : WELL
FLD. : FIELD
LOC. : LOCATION
SRVC. : SERVICE COMPANY
DATE. Friday, April 01 2011 11:47:28 : DATE
PROV. : PROVINCE
UWI. OR__1 : UNIQUE WELL ID
API. : API NUMBER
#===========================================
~Curve
DEPT .m : DEPTH
Facies_west . : Facies_west
KINT_west .mD : KINT_west
PHIE_west .m3/m3 : PHIE_west
SW_west . : SW_west
SW1_west . : SW1_west
~Parameter
#===========================================
~Ascii
1570.29992 -999.25 -999.250000 -999.250000 -999.25 -999.25
1570.30993 1.00000 0.5490000248 0.1199999973 -999.25 -999.25
1570.31994 1.00000 0.5490000248 0.1199999973 -999.25 -999.25
1570.32995 1.00000 0.5490000248 0.1199999973 -999.25 -999.25
1570.33996 1.00000 0.5490000248 0.1199999973 -999.25 -999.25
1570.34997 1.00000 0.5490000248 0.1199999973 -999.25 -999.25
2. File type: RFT (MDT) pressure measurement.

File format .txt.

Data description: well name, measured depth, pressure on this depth, date.
Check in GUI in the dialogue Data is RFT (MDT) pressure measurement.
If RFT measurement date is before 0 time step then tNavigator assigns RFT data to
zero time step.
Wellname Depth Pressure Date

WELL10 1709.59 157.293 15.12.2008
WELL10 1712.43 157.48 15.12.2008
WELL10 1714.55 157.307 15.12.2008
WELL10 1719.20 150.262 15.12.2008
WELL10 1720.58 150.075 15.12.2008
9.4.2 Maps. Export

Common parameters of maps export:
Inactive Block Placeholder a number which specifies that map value in respective
block is absent
Separate Layers by Comment each layer in the file will be headed by its number.
1. Save 3D.
File type: Map of the parameter values (tNavigator format).
File format .map.
Data description: values of parameter are written to the file for all grid blocks. The
coordinates of blocks ascending by X, Y, Z.
--Map: Depth
--Time step: 0
Depth
-- Layer 1 --
+2.748260e+003 +2.742420e+003 +2.742420e+003 +2.737400e+003
+2.737400e+003 +2.733930e+003 +2.733930e+003 0 0 0 0 0
0 0 0 0 0 0
9.4.2. Maps. Export 290

2. Save 3D to ACTNUM
File type: the map of active (corresponding 1 value) and inactive blocks (corresponding
0 value) is saved.
File format .inc.
Data description: values 1 and 0 are written to the file for all grid blocks. The coordi-
nates of blocks ascending by X, Y, Z. Syntax corresponds to the keyword ACTNUM.
-- Map: Map
-- Time step: 0
ACTNUM
-- Layer 1 --
+0 +0 +0 +0 +0 +0
+0 +0 0 0 0 0
0 0 0 0 +0 +1
+1 +1 +1 0 0 0
+1 +1 +1 +1 +1
+1 +1 +1 +1 +1 +1
3. Save 3D to .grd
File type: Binary file.
File format .grd.
4. Save 3D to AQUANCON (#1)

File type: aquifer map is saved. Syntax corresponds to the keyword AQUANCON.
File format .inc.
Data description: According to AQUANCON syntax coordinates of start and end of
cube connected to aquifer are written to the file. Block faces connected with aquifer
are chosen the following way: all blocks that bordering with the inner blocks. The
following faces are possible: I+ face in direction parallel to X axis, I- face in direction
opposite to X axis direction, J+ face in direction parallel to Y axis, J- face in direction
opposite to Y axis direction, K+ face in direction parallel to Z axis, K- face in direction
opposite to Z axis direction (axis Z is directed down). This option can be used to export
blocks to connect aquifer to the blocks insede the reservoir. But after this export one
need to set 11 parameter of AQUANCON (see 12.16.10) equal to YES (for default it
is NO). To do this one can add in the exported AQUANCON keyword to each line 2*
YES /.

-- Map: Cut
-- Time step: 0
AQUANCON
1 1 1 65 65 1 1 J- /
1 2 2 65 65 1 1 J- /
1 3 3 65 65 1 1 J- /
1 4 4 65 65 1 1 J- /
1 5 5 65 65 1 1 J- /

File format .inc.
Data description: Data description: According to AQUANCON syntax coordinates of
start and end of cube connected to aquifer are written to the file. Block faces connected
with aquifer are chosen the following way: all boundary blocks. The following faces
are possible: I+ face in direction parallel to X axis, I- face in direction opposite to X
axis direction, J+ face in direction parallel to Y axis, J- face in direction opposite to Y
axis direction, K+ face in direction parallel to Z axis, K- face in direction opposite to
Z axis direction (axis Z is directed down).

-- Map: Cut
-- Time step: 0
AQUANCON
1 1 1 65 65 1 1 I- /
1 1 1 65 65 1 1 J+ /
1 1 1 65 65 1 1 K+ /
1 1 1 65 65 1 1 K- /
1 2 2 65 65 1 1 J+ /
1 2 2 65 65 1 1 K+ /
1 2 2 65 65 1 1 K- /
1 3 3 65 65 1 1 J+ /
1 3 3 65 65 1 1 K+ /
1 3 3 65 65 1 1 K- /
1 4 4 65 65 1 1 J+ /
1 4 4 65 65 1 1 K+ /
1 4 4 65 65 1 1 K- /
1 5 5 65 65 1 1 J+ /
1 5 5 65 65 1 1 K+ /
1 5 5 65 65 1 1 K- /

File format .inc.
Data description: Data description: According to AQUANCON syntax coordinates of
start and end of cube connected to aquifer are written to the file. Block faces connected
with aquifer are chosen the following way: all boundary blocks in user-specified direc-
tion. The following faces are possible: I+ face in direction parallel to X axis, I- face in
direction opposite to X axis direction, J+ face in direction parallel to Y axis, J- face in
direction opposite to Y axis direction, K+ face in direction parallel to Z axis, K- face
in direction opposite to Z axis direction (axis Z is directed down). One also can specify
whether connections from faces, connected with active blocks, are allowed.

-- Map: Cut
-- Time step: 0
AQUANCON
1 1 1 65 65 1 1 J+ * * NO /
1 2 2 65 65 1 1 J+ * * NO /
1 3 3 65 65 1 1 J+ * * NO /
1 4 4 65 65 1 1 J+ * * NO /
1 5 5 65 65 1 1 J+ * * NO /
7. Save 3D to Wellpics
File type: IJK data.
File format no format is specified.
Data description: Text file with the following data: well name, IJK coordinates of block
with connection, value of parameter in this block.
102 1 4 1 0.175400
102 1 4 2 0.175400
102 1 4 3 0.175400
103 7 4 1 0.176300
103 7 4 2 0.176300
103 7 4 3 0.176300
File type: Block center data.

File format no format is specified.
Data description: Text file with the following data: well name, XYZ (metres) of centre
of block with connection, value of parameter in this block.

102 0.000000 300.000000 2735.030000 0.175400

102 0.000000 300.000000 2740.030000 0.175400
102 0.000000 300.000000 2745.030000 0.175400
103 600.000000 300.000000 2719.000000 0.176300
103 600.000000 300.000000 2724.000000 0.176300
103 600.000000 300.000000 2729.000000 0.176300
8. Save 2D to .grd (Surfer)

File format .grd.
Data description: Text file for the program Surfer.
DSAA
40 65
-50 3950
-50 6450
30.2647 564.92
+57.4933 +58.4596 +59.4258 +60.392 +61.3583 +62.4282
+65.0649 +69.8945 +75.5536 +81.2801 +87.2017 +94.5382
+110.626 +124.216 +126.598 +123.544 +120.511 +117.151
+108.631 +98.4625 +87.8773 +79.3242 +73.3193 +67.9514
9. Save 2D to .xyz
File type: XY data. Save 2D map in .xyz format.
File format .xyz.
Data description: X coordinate of the block (metres), Y coordinate of the block (metres),
value of the parameter in this block.

0.000000e+000 0.000000e+000 5.749330e+001

1.000000e+002 0.000000e+000 5.845960e+001
2.000000e+002 0.000000e+000 5.942580e+001
3.000000e+002 0.000000e+000 6.039200e+001
4.000000e+002 0.000000e+000 6.135830e+001
5.000000e+002 0.000000e+000 6.242820e+001
6.000000e+002 0.000000e+000 6.506490e+001
File type: IJ data. Save 2D map in .xyz format.

File format .xyz.
Data description: block numbers along X, Y axes, value of the parameter in this block.
1 1 5.749330e+001
2 1 5.845960e+001
3 1 5.942580e+001
4 1 6.039200e+001
5 1 6.135830e+001
6 1 6.242820e+001
7 1 6.506490e+001
8 1 6.989450e+001
10. Save 2D to .cps (CPS-3 ASCII)

File format .cps.
Data description: To save 2D map in this format one can specify number of values
along the axes X and Y, ascending or descending order of blocks on the axes. The
resulting data array can be transposed (reflected relatively the main diagonal).

FSASCI 0 1 COMPUTED 0 1.000000e+030

FSATTR 0 0
FSLIMI -33.3333 3933.3333 -33.3333 6433.3333 30.2647 564.9200
FSNROW 195 120
FSXINC 33.333333 33.333333
-> generated by tNavigator
259.6710000 259.6710000 259.6710000 267.4820000 267.4820000
267.4820000 271.0630000 271.0630000 271.0630000 271.8970000
271.8970000 271.8970000 271.9130000 271.9130000 271.9130000
271.7910000 271.7910000 271.7910000 271.6340000 271.6340000
9.4.3 Maps. Import

1. tNavigator map .map
File type: Map in tNavigator format.
File format .map.
Data description: file is loaded the following way: blocks sequentially assigned values
from the file. The coordinates of blocks ascending by X, Y, Z.
--Map: Depth
--Time step: 0
Depth
-- Layer 1 --
+2.748260e+003 +2.742420e+003 +2.742420e+003 +2.737400e+003
+2.737400e+003 +2.733930e+003 +2.733930e+003 0 0 0 0 0
0 0 0 0 0 0
2. GRD file[M] .grd

File type: binary file, generated via Roxar MORE.
File format .grd.
Data description: you will be offered a choice of which cubes of properties available
in the file to load.
3. Array file[M] .ara

File type: binary file, generated via Roxar MORE.
9.4.3. Maps. Import 297

File format .ara.

in the file to load and for which time steps.
4. Restart file .UNRST

File type: binary file, generated via Eclipse.
File format .UNRST.
in the file to load and for which time steps.
9.4.3. Maps. Import 298

10. Units tNavigator-4.2
10 Units
A table of units supported:
Quantity SI METRIC FIELD LAB

Length, depth, radius m m ft cm
Time s day day hr
Density kg/m3 kg/m3 lbl/ft3 gm/cc
Pressure (absolute) Pa Barsa Psia Atma
Pressure (difference) Pa Bars Psi Atm
Temperature (absolute) K K R K
Temperature (difference) C C F C
Compressibility 1/Pa 1/Bars 1/Psi 1/Atm

Viscosity Pa*s cpoise cpoise cpoise
Permeability m2 mDarcy mDarcy mDarcy
Liquid surface volume m3 sm3 stb scc
Gas surface volume m3 sm3 Mscf scc
Reservoir volume m3 rm3 RB rcc
Liquid surface volume rate m3 /s sm3 /day stb/day scc/hr
Gas surface volume rate m3 /s sm3 /day Mscf/day scc/hr
Reservoir volume rate m3 /s rm3 /day RB/day rcc/hr
Rate per unit area m3 /s/m2 m3 /day/m2 stb/s/ft2 scc/hr/cm2
Formation volume factor (liq- m3 /m3 rm3 /sm3 RB/stb rcc/scc
uid)
Formation volume factor (gas) m3 /m3 rm3 /sm3 RB/Mscf rcc/scc
Gas-oil ratio m3 /m3 sm3 /sm3 Mscf/stb scc/scc
Oil-gas ratio m3 /m3 sm3 /sm3 stb/Mscf scc/scc
m3 cp m3 cp RB cp cm3
Transmissibility
s Pa day Bars day Psi hr Atm
Unit conversion factor c depends on the unit system and defined as follows:
c = 0.00852702 for metric unit system;
c = 0.00112712 for field unit system.

Gravity conversion factor g depends on the unit system and is equal to:
g = 0.0000980665 for metric unit system;
g = 0.00694 for field unit system,
Standard conditions pressure and temperature in metric system (METRIC) are:

p = 1.01325 bars;
10. Units 299

10. Units tNavigator-4.2
T = 16C
In case of compositional run, those conditions can be changed by user, STCOND (see
12.13.8).
If units are not specified explicitly in this User Manual, then METRIC system is used by
default (In keywords examples METRIC system is used).
In the current version the following units systems are supported:
E100, E300 data format systems METRIC and FIELD;
MORE data format systems METR (metric) and POFU (the same to FIELD);
IMEX, STARS data formats systems SI and FIELD.
10. Units 300

11.1. Input formats tNavigator-4.2
11 Input data format

11.1 Input formats
For best adaptation of user experience the keyword notations in tNavigator are chosen to be
close as much as possible to the most common simulators:
Eclipse (c) Schlumberger,
IMEX, STARS, GEM (c) Computer Modelling Group Ltd,
Tempest MORE (c) Roxar.
tNavigator reads keyword notations of these simulators and converts them into its inner
data notations.
In addition: In models in conventional syntax you can use special tNavigator keywords that
are not implemented in other simulators.
So, tNavigator supports the following data formats:
E100 (black oil),
E300 (compositional, thermal models),
IMEX,
STARS,
GEM,
Tempest MORE,
tNavigator format (extension of E100, E300 formats that provide more convenient
definition of well data) section 11.2,
Hybrid format (this is tNavigator format: extension of E100, E300 formats where the
keywords in format E100 (or E300) can be used in combination with Tempest MORE
format keywords) section 11.3.
Keywords description in this User Manual.
E100, E300 format keywords are red. For example: TABDIMS (see 12.1.26). Index of
Eclipse format keywords 15.
IMEX, STARS, GEM format keywords are pink. For example: TEMR (see 13.5.11). Index
of CMG format keywords 16.
11. Input data format 301

11.2. tNavigator format tNavigator-4.2
MORE format keywords are green. For example: IDATe (see 14.1.5). Index of MORE
format keywords 18.
The keywords that can be used only in tNavigator are blue. For example: REACCONC
(see 12.14.50). Index of RFD format keywords 17.
In the description of each keyword there is a table where it is checked in which data
format can it be used in tNavigator (first part of the table). In the second part of the table the
sections are checked.
For example. In this table it is checked that the keyword is used in formats tNavigator,
E100, E300.
Data x tNavigator x E300 MORE GEM

format x E100 IMEX STARS
The keyword can be used in sections GRID and EDIT.
RUNSPEC x GRID x EDIT PROPS

Section
REGIONS SOLUTION SUMMARY SCHEDULE
11.2 tNavigator format

This format is an extension of E100, E300 formats that provide more convenient definition
of well data. We recommend to use this format in tNavigator.
All the sections before SCHEDULE can be described with the keywords in formats E100
(E300) and tNavigator special keywords (index 17).
In SCHEDULE section well data is defined via special tNavigator keywords to set well
trajectory and perforations in measured depth.
To use this keyword first define well using the keyword WELSPECS (see 12.18.3). Then
define well trajectory, including different well branches via WELLTRACK (see 12.18.9), then
define well perforations in measured depth COMPDATMD (see 12.18.10).
If this keyword COMPDATMD is used tNavigator automatically intersects the well bore with
the grid and open connections inside defined values of MDU and MDL. Connection factor
and effective KH are calculated.
After that all conventional keywords in format E100 (E300) can be used to define well
data.
11.2. tNavigator format 302

11.3. Hybrid format tNavigator-4.2
11.3 Hybrid format

tNavigator supports hybrid model of input data:
1. Case 1. Basic model is specified in Eclipse format (all sections, except sched-
ule section). Schedule section is specified in MORE format the keyword RECU
(see 12.18.218).
2. Case 2. Basic model is specified in Eclipse format. Well data in MORE format can be
loaded additionally (for example, well trajectories, events, history are loaded).
3. Case 3. Basic model is specified in MORE format. Well events are created additionally
in Eclipse format.
Example for Case 1 is shown in the description of the keyword RECU (see 12.18.218).
What to do in the Case 2.

Usually such models are the result of the following case:
1. There is a model in Eclipse format.
2. Well data (trajectories, events, history) are loaded via GUI. In this case the file con-
taining events in MORE format is automatically saved in USER folder (file name is
MODEL_NAME_more_schedule_0000_User wells data.inc).
3. For wells, that are specified in MORE format, new events in Eclipse format are spec-
ified. For example, tracer injection (WTRACER (see 12.18.148)), hydraulic fracture
(WFRACP (see 12.18.124)), economical limits (WECON (see 12.18.62)) and other.
These events are recorded in a new file in USER folder (the events are added via
GUI). For example, in the file MODEL_NAME_schedule_0000_User wells events.inc.
Attention! In the Case 2.

If USER folder exists, then User_Eclipse_schedule is always read before User_MORE_schedule.
Following the algorithm, that is described above, message that an event is specifying for
nonexistent well will appear if you reload the model.
It is necessary to specify manually in hybrid model .data-file the order of user files.
This problem can be solved by one of the following methods:
Method 1. Saving schedule section. All data will be converted into Eclipse format.
Set time slider to zero time step in GUI, then press the button Save model. Tick only
Schedule. File MODEL_NAME_saved_sch.inc will be saved. All data types are combined
in this file and saved as Eclipse data format.
One need to delete original schedule section from .data-file, and include a saved file instead
of deleted section. (All files in USER folder should be deleted too, because a new including
file replaces them all.)
11.3. Hybrid format 303

Example
SCHEDULE
INCLUDE
'v42_saved_sch.inc' /
/
END
Method 2. Manual editing of schedule section. MORE and Eclipse keyword can be
used simultaneously in the model. Data confluence will not be happened.
Schedule section should be manually converted for correct run of simulator, the following
way, for example:
Example
RECU
RATE 1 MONTH EXACT STAT FIELD GROUP WELL SLIM CRAT

FREQ 0 0 1
/
INCLUDE
'welldata.txt' /
/
USERFILE
'wfracp.inc' /
/
READ 1 JUL 2000 /
STOP
Description of actions:
1. The keyword RECU (see 12.18.218) specifies the beginning of data in MORE format
in Eclipse model.
2. File welldata.txt contains wells data in MORE format and includes as INCLUDE.

Example
welltrack '5'
100 110 2500.0 2500.000
100 110 2510 2510
100 110 2530 2540 ;
...
ETAB
3 03.01.2000 PERF 2500.0 2560.0 0.15 0 /
5 01.12.1994 PERF 2510.0 2520.0 0.15 0 /
5 01.12.1994 PERF 2525.0 2555.0 0.15 0 1 /
...
For example, it can be file which was automatically saved in USER folder
(MODEL_NAME_more_schedule_0000_User wells data.inc) but was renamed to well-
data.txt and was put nearby to a model .data-file.
3. The keyword USERFILE (see 12.18.219) is used in this case. It tells that the data in
Eclipse format is included. It is skipped at first reading. Then all MORE data, that
follows the given file, is read to the end of .data-file.
4. Then the second reading takes place. Now the data included via USERFILE
(see 12.18.219) will be read. As a result, event in Eclipse format overlays on the
MORE format data. Dates, that are specified in the model already, can only be used
inside the including file. Events can bind only with dates that were already occured
(new dates shouldnt be specified in including file).
Example
DATES
11 'FEB' 2000 /
/
WFRACP
'2' 36 4 1 36 4 3 100 0 200 200 0 0 0.02 3* 1 6* 0 /
/
DATES
01 'MAR' 2000 /
/

11.4. Keywords syntax tNavigator-4.2
In the example hydraulic fracture is specified via the keyword WFRACP

(see 12.18.124). For example, it can be a file that was automatically saved in USER
folder (MODEL_NAME_schedule_0000_User wells events.inc), but was renamed to
wfracp.inc and was put nearby to a model .data-file.
11.3.1 Restart for hybrid models

The following data must be copied from base model to restart model:
well trajectories (WELLTRACK);
perforation data (ETAB (see 14.6.5), PERF (see 13.9.13)).
11.3.2 Split and merge of hybrid models

Automatic split and merge can be used for hybrid models the same way as for models of
standard types 5.14.
After splitting in model parts there are the following keywords:
Example
SKIP
SKIPOFF
RECUMESH
SKIPON
ENDSKIP
You shouldnt delete these keywords! .patterns - file (whole model file) can not work
correct without them!
11.4 Keywords syntax

In this section we describe the general features of keywords reading:
1. All keyword names are case insensitive.
2. Values of parameters usually follow on the next string (formats E100, E300, tNavigator)
or can be on the same string with the keyword (formats IMEX, STARS, MORE).
3. If keyword value is not specified by user tNavigator uses a default value if it is defined
or an error message is issued.
11.3.1. Restart for hybrid models 306

11.4. Keywords syntax tNavigator-4.2
4. Data issues are terminated with a symbol slash / (formats E100, E300, tNavigator). If
less elements than array length are specified than the rest elements are filled by default
values if possible, otherwise an error message is issued.
5. For equal values the standard form NUM*VAL can be used, where NUM is the number
of equal values, and VAL the value itself.
6. Reading the keywords in formats E100, E300.

Keywords in format E100, E300 have the first 8 significant characters. Reading is
performed by cutting the first 8 characters. So any keyword that is longer than 8
characters is a complete analog of its 8 literal version. For example, ENDACTIO and
ENDACTION are equivalent.
7. Reading of well names that are longer then 8 characters in formats E100, E300.
For default only first 8 symbols in well names are read. So the wells names LONG-
WELL1 and LONGWELL2 are both read as LONGWELL. This setting is used for
compatibility with input language of simulator Eclipse.
If you need to read full long well names use the setting LONGNAMES 1 of the keyword
TNAVCTRL (see 12.1.4).
8. Reading of keywords after space at the beginning of the line in formats E100,
E300.
For default the keywords that are written after the space symbol in the beginning of the
line are ignored. This setting is used for compatibility with input language of simulator.
To read these keywords use the setting KEYWORDS_SPACE 1 in the keyword TNAVC-
TRL (see 12.1.4).
9. Reading the keywords in format Tempest MORE.

Keywords in format MORE have the first 4 significant characters. For convenience
(analogous to MORE) keywords are written in upper case. Sometimes for clarity all
characters of the keyword may be written. For example: FLUI and FLUId. FLUI the
keyword with 4 significant characters.
11.4. Keywords syntax 307

12. Keywords compatible with tNavigator and E100, E300 tNavigator-4.2
12 Keywords compatible with tNavigator and E100, E300

The general description of data formats that can be used in tNavigator, keywords syntax and
reading of keywords in different formats are in the section 11.
This section describes all keywords which can be used in tNavigator in the following
model formats:
tNavigator;
E100;
E300.
tNavigator or which use is different from Eclipse.
For convenience keyword descriptions are grouped in several sections:
Definition section (12.1)
Grid section (12.2)
Arithmetic section (12.3)
Region section (12.4)
Property section (12.5)
Relative permeabilities and capillary pressures (12.6)
Compositional properties (12.13)
Thermal properties (12.14)
Initialization section (12.15)
Schedule section (12.18)
Inflow from aquifer (12.16)
12. Keywords compatible with tNavigator and E100, E300 308

12.1. Definition section tNavigator-4.2
12.1 Definition section

Definition section contains initial data necessary for oil-and-gas reservoir model specification.
12.1. Definition section 309

12.1.1 RUNSPEC

x RUNSPEC GRID EDIT PROPS

Section
The keyword specifies the beginning of data section which contains initial data necessary
for oil-and-gas reservoir model specification.
12.1.1. RUNSPEC 310

12.1.2 TITLE


Section
Used to specify model title. Any alphabet can be used. The title should be one line long.
Example
TITLE
Test Example
/
This example specifies title for model "Test Example".
Example
TITLE
Model of field with large
number of blocks
/
This example specifies title for model "Model of field with large". Note that the informa-
tion from the second line was ignored.
12.1.2. TITLE 311

12.1.3 REPORTFILE / REPORTSCREEN
Data x tNavigator E300 MORE GEM

format E100 IMEX STARS
x RUNSPEC x GRID x EDIT x PROPS

Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE
The keywords are used to specify reporting level for log file and for the screen. RE-
PORTFILE and REPORTSCREEN keywords provide more advanced capabilities for tuning of
output to log file, and to the screen. To provide most correct reporting on read input data,
keywords REPORTFILE and REPORTSCREEN should be specified in the very beginning of
*.data-file.
All output to the log-file and to the screen will be performed using unit system that is
defined in the model.
The following values should be specified:
section, the following options are available:

<Section> <Description>
READ Information on reading input data
WRITE Information on writing input data
CHECK Information on checking input data
INIT Information on initialization of simulation process
ITERS Information on iteration process
FIP Information on FIP
SOLVE Information on solving
GUI Information on user interface
RSV Information on reservoir
GROUP Information on well groups
WELL Information on wells
CONN Information on connections
GRID Information on grid
PRINT_LOGS All log messages and tables
ALL All sections listed above
priority, characterizing the amount of output to log file (to the screen). The following
options are possible:
12.1.3. REPORTFILE / REPORTSCREEN 312

<Priority> <Description>
WARNING Report only warnings and errors
HIGHEST Report information with highest priority and above
HIGH Report information with high priority and above
MEDIUM Report information with medium priority and above
LOW Report all information
For example, for section PRINT_LOGS highest priority means information (i.e. tables)
only about reservoir, high priority means information on reservoir and groups, medium
priority also includes well information, and, finally, low priority means that all infor-
mation on reservoir, groups, wells and connections will be written to log file (displayed
on the screen). For other sections similar information priority system is used.
One or more pairs <section> <priority> should be specified after keyword REPORTFILE
(or REPORTSCREEN). The list should be terminated by a slash /.
The effect of REPORTFILE and REPORTSCREEN keywords is illustrated in the following

table. Having set a priority for a section, you will get all messages indicated for this section
and this priority and messages to the right. If a section is not present in the table, this means
that priorities choice will not reflect on output to *.log file and to the screen, since all
messages for this section are warning and error messages.

Priority LOW MEDIUM HIGH HIGHEST WARNING
READ
Values of RUNC- 1 line for each key- List of included Error and warning
TRL parameters read word successfully *.inc-files and messages
read: its name and their names
number of lines
(values) read; for
DIMENS, TAB-
12.1. Definition section
DIMS keywords the

values are listed
CHECK
Messages on block Number of connec- Error and warning
deactivation: each tions in the model messages, for ex-
block and reason ample, total number
12.1.3. REPORTFILE / REPORTSCREEN

for deactivation are of blocks switched
listed to inactive for each
constraint type
INIT
Total number of ac- Number of blocks, Error and warning
tive blocks switched to inac- messages
tive due to mini-
Total memory allo- mal pore volume cri- Names of *.data,
cated teria, MINPV (see *.res, *.for,
12.2.30) *.err, *.log files
to be continued on the next page

tNavigator-4.2
314
continued from previous page
ITERS
Information on each Restart time Message on sim- Error and warning
simulator time step ulation start date messages
time, step length, (SIMULATION
number of iterations, STARTED FROM
variable change dp, DATE...)
ds (or dn), dv
After each report
In case of time time step message
step restart cor- on time step comple-
responding information and summary
tion: restart moment, rates, average pres-
old and new time sure (REPORT N
step lengths .. FOR DAY .. IS

DONE)
Messages on New-
ton process conver- After simulation
gence problems that is finished total
cause restart too elapsed time, num-
slow convergence or ber of time steps
convergence to non- and iterations (Total
physical solution elapsed ...)
FIP
Summary tables are Summary tables for Error and warning
enlarged with one all FIP regions messages
column for each FIP reserves, average
region with the same reservoir pressure,
data pore volume
tNavigator-4.2
315
SOLVE
Information on each Error and warning
Newton iteration messages
number, residual, pa-
rameters change
RSV
Information on mate- Error and warning
rial balance error messages
GROUP
Information on Message on com- Error and warning
group controls pensation switch off, messages

if total injection for
group is too small
WELL
Messages on well Information on well Error and warning
switch / perforation clo- messages
sure due to economic
Messages on prob- limit on rate or wa-
lems with well cal- tercut
culation
CONN
Messages on cross- Error and warning
flow through con- messages
nections
tNavigator-4.2
316
GRID
Messages on grid Error and warning
messages
PRINT_
LOGS Injection/production Injection/production Injection/production Summary injec- Error and warning
tables for each tables for each well tables for each group tion/production messages
connection tables for reservoir
All data on new well
perforations

tNavigator-4.2
317
Default:
REPORTFILE
ALL HIGH
/
REPORTSCREEN
ALL HIGH
PRINT_LOGS WARNING
FIP WARNING
/
Example
REPORTFILE
READ LOW
PRINT_LOGS MEDIUM
/
REPORTSCREEN
PRINT_LOGS MEDIUM
/
This example defines that all names and number of read variables will be written to log
file, and all tables concerning production from reservoir, groups and wells will be written
both to the screen and to the log file.
Example
REPORTFILE
ITERS HIGH
WELL LOW
/
REPORTSCREEN
WELL LOW
ITERS MEDIUM
/
This example defines that information on each calculation time step length, relative pres-
sure and saturation variation after this time step and relative material balance error for this
time step will be written to the screen. The information on well control change will also be
written to the screen. In the log file there will be no information on calculation time steps,
summaries only for reporting time steps will be accompanied by information on well control
changes.

12.1.4 TNAVCTRL


Section
The keyword is used to set settings of model reading and calculation in tNavigator. The
data should be terminated with a slash /.
The following options can be used:
1. COMPATIBILITY this option is used to match initialization/computation logic of a

model with one of other simulators different versions. It has the following parameters:
ECL_PRE2014 if this parameter > 0, then copying of NTG (see 12.2.25) values
from matrix to fracture blocks will be turned off. This option is used in E300
dual porosity models. Option DPGRID_PRE2014 with the same functionality is
obsolete;
ECL_PRE2012 additionally to the functionality descripted above this option
turns on logic of using MULTREGP (see 12.3.15), which was used in ECLIPSE
simulator before 2012.
2. CONVERGENCE_PROBLEM_NUM this option allows to request the map of blocks

with convergence problems. After the option a number A% (from 0 to 100) should be
specified value in percents.
The map Number of Convergence problems will be available in user graphical interface
in the option Maps. Calculated Maps.
This map has interger values in blocks, at each time step the value in the block is plus
one if there are convergence problems in this block, i.e. the residual value is greated
than the specified value A% from the maximum residual value.
3. DECAY_MODEL:
1 foam/tracer decays instantaneously at the end of timestep, adsorbed foam/tracer

doesnt participate in decay process. So, at the end of timestep there is no equili-
bration between foam/tracer concentration in solution and in rock;
2 foam/tracer decays instantaneously at the end of timestep, then, because of
decreasing of foam/tracer concentration in solution due to decay process, desorp-
tion is starting, and desorbed foam/tracer takes part in decay process. Desorption
is performed until equilibration is achieved. So, at the end of timestep there is the
equilibration state between foam/tracer concentration in solution and in rock.
12.1.4. TNAVCTRL 319

4. INCREASENETWORKP option is enabled if the value 1 is specified it allows

pressure to increase going up the network, i.e. it may be a situation when pressure on
the underlying network node is below than on the overlaying network node (default: 0,
pressure should not increase);
5. ISOTHERMAL energy conservation equation is not imposed in model. As a conclu-

sion, grid cell temperatures will not change from their specified initial values. This
option can be used only with option ZT of the keyword TFORM (see 12.1.8).
6. KEYWORDS_SPACE if this setting is set to 1 the keywords that are written after the
space symbol at the beginning of the line are read.
If this option is used we recommend to set the keyword TNAVCTRL at the be-
ginning of the section; so all the keywords after it will be read the right way.
For default this option is not used, these keywords are ignored, and the following mes-
sage will be visualized:
Warning: keyword XXXXX was skipped, space found at the first position of cur-
rent line. Use TNAVCTRL KEYWORDS_SPACE 1 in RUNSPEC to prevent skipping
keyword or remove spaces to use keyword without warning;
7. LONGNAMES if this setting is set to 1 then tNavigator will read well names that are
longer than 8 symbols. For default without this setting there is a cut for names that are
longer that 8 symbols. So the wells names LONGWELL1 and LONGWELL2 are both
read as LONGWELL;
8. SCALE_MATRIX option is enabled if the value 1 is specified (or YES); option is not
used if 0 is specified (or NO).
This option can decrease material balance error in some cases. This option provides the
more accurate solution of the system of linear equations, produced by Newton method,
due to the convergence of all the components of the solution vector to the exact value
(not just the components with highest magnitude). When this option is applied at the
stage of solving the system of linear equations the following parameters are modified:
matrix, right hand side, and initial quess to the solution. So this option can possibly
slow down the solving of the system of linear equation.
9. STOCK_TANK_WATER_CREF. Possible values:
YES the volumetric water rates for both injectors and producers are calculated
at reference salt concentration for stock tank water. This concentration is set in
PVTWSALT (see 12.7.14), second parameter of the first keyword data line.
NO the volumetric rates of injectors are calculated from reference salt concen-
tration from WSALT (see 12.18.152), and for producers rates are calculated for
average salt concentration in the wellbore (so, its the concentration of salt for
water produced from reservoir).

10. SWCR_CORR used to correct SWCR values in grid blocks using SWU, SWL. New
values are calculated by the following formula:
(SWCR_value SW L_value) (SWU_value_s SW L_value_s)
SWCR = SW L_value_s+
(SWU_value SW L_value)
Where the value without s (_value) is a table value, and a value with s (_value_s)
scaled value (from the corresponding array).
One of the following values can be specified:
0 correction is not used;
1 if table value of SWCR is not greater than SWL value in some blocks, then
SWCR values in these blocks will be recalculated via specified formula;
2 values of SWCR in blocks in which they werent specified will be calculated
via specified formula;
3 SWCR values in all blocks will be recalculated via specified formula.
Default:
DECAY_MODEL: 1;
INCREASENETWORKP 0, pressure should not increase;
KEYWORDS_SPACE 0. The keywords that are written after the space symbol at the
beginning of the line line are ignored (this setting is used for default to compatibility
with input language of simulator Eclipse);
LONGNAMES 0. Only first 8 symbols in well names are read (this setting is used
for default to compatibility with input language of simulator Eclipse).
SCALE_MATRIX 0, option is not used;
STOCK_TANK_WATER_CREF for models run as E300: YES; for models run as
E100: NO.
Example
TNAVCTRL
DPGRID_PRE2014 1 /
In the example copying of NTG (see 12.2.25) values from matrix to fracture blocks is
turned off.
Example
TNAVCTRL
CONVERGENCE_PROBLEM_NUM 90 /
/

In this example the map of blocks with convergence problems is requested with the
residual value 90%. At each time step the value in the grid block is plus one, if there are
convergence problems in this block, i.e. the residual value is greated than the specified value
90% from the maximum residual value.

12.1.5 AIMCTRL


Section
This keyword sets settings of adaptive implicit method (AIM).
AIM is used by default for compositional models.

In black-oil models fully implicit is used by default. To use AIM in black-oil one need to set
AIM parameter of the keyword RUNCTRL (see 12.18.119).
The data should be terminated with a slash /.

The following parameters should be specified:
1. Throughput target fractional throughput target threshold of the grid block, above
which a fully implicit scheme is used in filtration equation in a cell (dimensionless);
2. Saturation change target maximal phase saturation variation in a grid block at one
time step, above which a fully implicit scheme is used in filtration equation in a cell
(dimensionless);
3. max_dP_dt maximum capillary pressure derivative, above which a fully implicit

scheme is used in filtration equation in a cell (METRIC: Bar/day; FIELD: Psi/day);
4. Critical point tolerance criterion if a grid block state is close to critical point, if
this criterion is satisfied a fully implicit scheme is used in filtration equation in a cell
(dimensionless). This parameter can be specified only for compositional models;
5. Neighbors radius (in grid blocks), around the blocks with open connections; inside
this area for all blocks a fully implicit scheme will be used in filtration equation
(dimensionless). Fully implicit scheme is used for blocks with open connections.
Default:
Throughput target 0.05;
Saturation change target 0.125;
max_dP_dt 0.05;
Nritical point tolerance 0.01;
Neighbors 1.
12.1.5. AIMCTRL 323

12.1.6 FLASHCTRL


Section
REGIONS SOLUTION SUMMARY x SCHEDULE
The keyword allows to change convergency preferences for compositional flash. The
following options and their parameters can be specified:
1. FL_TOL n flash solution tolerance;
2. FL_V_PREC n tolerance of material balance equation solution;
3. PH_STBLTY_QNSS n system of algebraic equations solution method in stability test.

Allowable values are 1 (quasi-Newton successive substitution method, QNSS) and 0
(Newton method);
4. PH_STBLTY_QNSS_PREC n QNSS tolerance in stability test;
5. PH_STBLTY_QNSS_TRIV_TOL n tolerance used to find trivial solution of test

stability system by QNSS method;
6. SHADOWREGION n flash boost option. If certain criteria are satisfied, then without
running stability test it is decided that hydrocarbon is in one-phase state (OIL or GAS).
Allowable values are 1 and 0;
7. ZSCALESHADOW n parameter of SHADOWREGION option which defines how

much component parameter of one-phase hydrocarbon can change to stay it one-phase;
8. PSCALESHADOW n parameter of SHADOWREGION option which defines how

much pressure of one-phase hydrocarbon can change to stay it one-phase;
9. ADD_PF_FL_CALC n option runs path finder algorithm in case if stability test

found out unstability of one-phase states, and flash solving algorithm didnt converge.
Allowable values are 1 and 0.

Default:
FL_TOL: 1E-6;
FL_V_PREC: 1E-6;
PH_STBLTY_QNSS: 1;
PH_STBLTY_QNSS_PREC: 1E-6;
12.1.6. FLASHCTRL 324

PH_STBLTY_QNSS_TRIV_TOL: 1E-4;
SHADOWREGION: 1;
ZSCALESHADOW: 0.1;
PSCALESHADOW: 0.05;
ADD_PF_FL_CALC: 1.
Example
FLASHCTRL
SHADOWREGION 0
/
12.1.6. FLASHCTRL 325

12.1.7 VELDEP


Section
The keyword sets parameters of velocity dependent relative permeabilities. There are two
model of capillary number:
Model 1
It is calculated by the following formula:
vg g
Ncp =

where:
g - gas viscosity;
vg - gas velocity in the flow direction;
- gas-oil surface tension.
Model 2
It is calculated by the following formula:
Kkrvi Pi
Ncp =
L
where:
K - absolute permeability;
krvi - relative permeability which is modified by capillary number of i-th phase
in flow direction at previous time step;
Pi - pressure drop of i-th phase;
L - length of block along flow direction.
For each phase p Forchheimer models are:
Model 1
It is calculated via the following formula:
ap
p = c p
b p S p (Kkrvp )d p
12.1.7. VELDEP 326

Model 2
It is calculated via the following formula:
c
p = d p S pp (Kkrvp )d p ,
where S p is normalized saturation of p-th phase:

(3P)
Sp
Sp =
1 Sw
The following parameters should be specified (The data should be terminated with a slash
/.):
1. capillary number model which will be active for the oil phase (1 or 2);
2. capillary number model which will be active for the gas phase (1 or 2);
3. Forchheimer number model which will be active for the oil phase (1 or 2), IGNORED,
this is an Eclipse compatibility field;
4. Forchheimer number model which will be active for the gas phase (1 or 2);
5. number which sets whether an alternative model for Capillary Number effects in near
wellbore flows in gas condensate reservoirs is active for the gas, or gas and oil, phases
(number 1 model is active for gas phase, 2 for oil and gas phases).
When using this alternative model, parameter 2 must be set to 0.
Parameters of alternative model (5-th parameter of the keyword) have default values, but
they can be changed using the keyword VDKRGC (see 12.13.50).
By default:
0 for all parameters (i.e. models are inactive).
Capillary numbers are set by the keywords VDKRO (see 12.13.51) and VDKRG (see
12.13.49) correspondingly.
Example
VELDEP
1 1 1 0 0 /
In the example first models of capillary numbers are set.
12.1.7. VELDEP 327

12.1.8 TFORM

format E100 IMEX x STARS

Section
The keyword sets primary variable in thermal equation. One of the following parameters
ZH primary variable is system fluid enthalpy;
ZT primary variable is temperature;
MIX each block can has its own primary variable. This option is compatible only with
tNavigator and can be used in STARS and E300 format models (variables are chosen
automatically by tNavigator).
12.1.8. TFORM 328

12.1.9 RPTRST


Section
REGIONS x SOLUTION SUMMARY x SCHEDULE
This keyword allows to save additional calculated data to results file and specify the
options of its saving in E100 format. If the keyword is specified in SOLUTION section, then
initial maps and graphs will be saved, and if the one is specified in SCHEDULE section, then
calculated maps and graphs will be saved.
Then the list of mnemonics follows. These mnemonics corresponds to saving parameters.
The list should end by (/).
The following mnemonics are used in SCHEDULE section:
ALLPROPS saving data includes values of density, viscosity, volume coefficients and
relative permeabilities. If value 2 is set for this mnemonic, then old ones are using for
output.
BASIC=n. Possible cases:
n = 1. Then data will be saved to binaries at every report step.

n = 2. Then data will be saved to binaries at every report step, while this param-
eter is not changed.
n = 3. Then data will be saved to binaries at every k -th report step. The value of
parameter k is specifying by parameter FREQ.
n = 4. Then data will be saved to binaries at first report step of every year. If the
value of parameter FREQ is k , then data will be saved to binaries at every k -th
year.
n = 5. Then data will be saved to binaries at first report step of every month. If
the value of parameter FREQ is k , then data will be saved to binaries at every
k -th month.
n = 6. Then data will be saved to binaries at every time step.
BG gas formation volume factor;
BGAS output of gas reservoir molar densities;
BO oil formation volume factor;
BOIL output of oil reservoir molar densities;
BSOL output of solid reservoir molar densities (SoLID option);
12.1.9. RPTRST 329

BW water formation volume factor;
BWAT output of water reservoir molar densities;
DEN output of phase reservoir densities;
DENO output of oil mass densities at reservoir conditions;
DENW output of water mass densities at reservoir conditions;
ENERGY Internal energy / bulk volume (THERMAL option);
FIP output of fluids-in-place at separator conditions for models in E100 format, and
at reservoir conditions for E300 format. For E100 models, a basic restart file includes
global fluids-in-place only: this mnemonic also outputs local fluids-in-place. Since FIP
is simulator-specific it is recommended that the user uses RFIP or SFIP;
FLOWS output of interblock flows (Includes non-neighbor connection flows and

flows between global and local grids.);
FREQ specify frequency of data saving to binaries, if the value of BASIC greater than
2.
HSOL output solid enthalpy values (for models in E300 format Thermal and SoLID
option);
HWAT output water enthalpy values (for models in E300 format Thermal);
KRG output of gas relative permeabilities: outputs the array GASKR (E100 models)
or KRG (E300 models);
KRO output of oil relative permeabilities: outputs the array OILKR (E100 models) or
KRO (E300 models);
KRW output of water relative permeabilities: outputs the array WATKR (E100 models)
or KRW (E300 models);
PCOW output of oil-water capillary pressures;
PORV output of reservoir pore volumes at reference conditions;
PRES for models in E100 format output of water and gas phase pressures; for models
in E300 format output of grid block pressures;
PRESSURE output of grid block pressures (equivalent to PRES);
RFIP output of fluids-in-place at reservoir conditions. In models of E100 format this

is the product of pore volume at reservoir conditions with saturation. In models of
E300 format, this is a synonym for FIP;
12.1.9. RPTRST 330

RS output dissolved GOR (RS) (In compositional runs this is interpreted as the GOR
at surface conditions of the liquid phase in the reservoir);
RV output vaporized OGR (RV) (In compositional runs this is interpreted as the OGR
at surface conditions of what was the vapor phase in the reservoir);
SFIP output of fluids-in-place at surface/separator conditions;
SFIPWAT output of separator volumes for water FIP data (single component water
only at present);
SGAS output of grid block gas saturations;
SOIL output of grid block oil saturations;
SSOLID output of grid block solid saturations;
SWAT output of grid block water saturations;
TEMP output of reservoir temperatures (THERMAL option);
VGAS output of gas viscosities;
VOIL output of oil viscosities;
VWAT output of water viscosities;
VISC output of fluid viscosities.
Example
RPTRST
'BASIC=3' ' FREQ=2'/
In the example the rule of saving calculation results to binaries is set: data will be saved
at every second report step.
12.1.9. RPTRST 331

12.1.10 OUTSOL

RUNSPEC GRID EDIT PROPS

Section
The keyword is identical with the keyword RPTRST (see 12.1.9).
12.1.10. OUTSOL 332

12.1.11 UNIFOUT


Section
The keyword is used for saving calculation results as Eclipse binary files. It sets mode of
output of RESTART and SUMMARY files. If the keyword is specified, then output of every
reporting step is saving into unified file of corresponding type. You need to use the keyword
MULTOUT (see 12.1.12) to create one output file for one reporting step (multiple-files).
By default:
MULTOUT (see 12.1.12).
Example
UNIFOUT
12.1.11. UNIFOUT 333

12.1.12 MULTOUT


Section
The keyword is used for saving calculation results as Eclipse binary files. It sets mode of
output of RESTART and SUMMARY files. If the keyword is specified, then output of every
reporting step is saving into one file, which corresponds to this step (multiple-files). You
need to use the keyword UNIFOUT (see 12.1.11) to create one unified file for all reporting
steps.
This keyword is used by default.
Example
MULTOUT
12.1.12. MULTOUT 334

12.1.13 START


Section
The keyword sets the start simulation date. The date should be written in format: DD
MONTH YYYY. The date should be terminated with a slash /. MONTH can take the follow-
ing values: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC, or JLY,
which is acceptable alternative to JUL.
Any report dates in the keyword DATES (see 12.18.105) must be later than the start date.
Example
START
01 JUL 1984
/
12.1.13. START 335

12.1.14 RESTART


Section
REGIONS x SOLUTION SUMMARY SCHEDULE
This keyword is used for calculation restart basing on already calculated model from
N-th time step. It is also possible to restart computation process from the date specified, see
RESTARTDATE (see 12.1.15).
Restart data is read from saved results files of the corresponding model.
Note. Restart is available for the model calculated in tNavigator. I.e. base model should be
calculated in tNavigator. Restart from calculation results of another simulator is not available.
The following data should be specified (The data should be terminated with a slash /.):
model name with saved calculation results data, file extension need not be specified,
time step number from which computation should restart.
Example 1. Whole .data-file of restart model. Style of forecast model created by

tNavigator
Example
RESTART
'modelSmall' 139
/
SCHEDULE
INCLUDE
'modelSmall_FORECAST_sch.inc'/
END
In this example results data are loaded for the model modelSmall. and computation starts
from 139-th time step (first step to be calculated will be step 140). Schedule section SCHED-
ULE, file modelSmall_FORECAST_sch.inc is included.
Included file modelSmall_FORECAST_sch.inc can be like this (keyword DATES goes

after WCONPROD, WCONINJE):
12.1.14. RESTART 336

Example
WCONPROD
W1085 OPEN BHP 1* 1* 1* 1* 1* +1.32256675e+002 /
W244 OPEN BHP 1* 1* 1* 1* 1* +1.18884682e+002 /
/
WCONINJE
W1054 WATER OPEN BHP +8.84194000e+001 1* +3.63650355e+002 /
/
DATES
01 OCT 2004 /
/
DATES
01 NOV 2004 /
/
DATES
01 DEC 2004 /
/
Example 2. Part of the .data-file of restart model (style of E100, E300 models)
12.1.14. RESTART 337

Example
...
PROPS
STONE1
INCLUDE
'pvt.inc'/
INCLUDE
'rp.inc'/
REGIONS
INCLUDE
'regs.inc'/
SOLUTION
INCLUDE
'init.inc'/
RESTART
'modelSmall' 139
/
SUMMARY
ALL
SCHEDULE
INCLUDE
END
In this example sections are going in their usual order ..., PROPS, REGIONS, SOLU-
TION. In SOLUTION section restart of the model modelSmall is from time step 139. Next
there are sections SUMMARY, SCHEDULE.
12.1.14. RESTART 338

12.1.15 RESTARTDATE

This keyword is used for calculation restart basing on already calculated model from the
date specified. It is also possible to restart calculation from specified time step, see RESTART
(see 12.1.14).
Restart data is read from saved results files of the corresponding model.
The following data should be specified (The data should be terminated with a slash /.):
1. model name with saved calculation results data, file extension need not be specified,
2. * symbol, field is ignored;
3. date from which computation should restart; if start of model time step does not
coincide with this date, then computation starts from the nearest date before specified
one;
Example
RESTARTDATE
'modelSmall' 1* 01 SEP 2004
/
SCHEDULE
INCLUDE
END
In this example results data are loaded for the model modelSmall. and computa-
tion starts from the 1-st September of 2004. Schedule section SCHEDULE, file modelS-
mall_FORECAST_sch.inc is included.
Included file modelSmall_FORECAST_sch.inc can be like this (keyword DATES goes

after WCONPROD, WCONINJE):
12.1.15. RESTARTDATE 339

Example
WCONPROD
W1085 OPEN BHP 1* 1* 1* 1* 1* +1.32256675e+002 /
W244 OPEN BHP 1* 1* 1* 1* 1* +1.18884682e+002 /
/
WCONINJE
/
DATES
01 OCT 2004 /
/
DATES
01 NOV 2004 /
/
DATES
01 DEC 2004 /
/
12.1.15. RESTARTDATE 340

12.1.16 METRIC


Section
This keywords defines that METRIC system is used in the model.
12.1.16. METRIC 341

12.1.17 FIELD


Section
This keywords defines that FIELD system is used in the model.
12.1.17. FIELD 342

12.1.18 LAB


Section
This keywords defines that LAB system is used in the model.
12.1.18. LAB 343

12.1.19 LANGUAGE


Section
This keyword is used for language and encoding used for input and output data. The
following combination of language and encodings are supported:
ENGLISH - English,
RUS.WIN - Russian in cp1251 (windows) encoding,
RUS.ALT - Russian in cp866 (DOS) encoding,
RUS.KOI - Russian in KOI8 (UNIX) encoding.
The language and encoding specified are used:
for input data,
for generated by simulator files with reports,
for all messages output on terminal.
Default: ENGLISH.
Example
LANGUAGE
RUS.ALT
In this example simulator will use Russian in DOS encoding.
12.1.19. LANGUAGE 344

12.1.20 BLACKOIL


Section
The keyword defines that black oil model is used. Compositional run is defined via the
keyword COMPS (see 12.13.3).
Example
BLACKOIL
12.1.20. BLACKOIL 345

12.1.21 DEFINES


Section
x REGIONS SOLUTION x SUMMARY SCHEDULE
This keyword is used to specify variables to tNavigator Assisted History Matching and
Uncertainty Analysis Module for models in formats E100 and E300 (for MORE format mod-
els one should use the keyword VDEF (see 12.1.22), which syntax is analogous to DEFINES
(see 12.1.21)).
The data for each variable should be terminated with a slash /. All data should be termi-
nated with a final slash /.
For each variable the following parameters should be specified:

1. variable name (name should contain letters, numbers and _ symbols; variable name
can not start with number or _ symbol);
2. variable default value;
3. minimum value (parameter value will vary between minimum and maximum according
to the distribution specified by the user in graphical interface later (normal or uniform).
Minimum and maximum values cant depend on other variables;
4. maximum value (parameter value will vary between minimum and maximum according
to the distribution specified by the user in graphical interface later (normal or uniform).
Minimum and maximum values cant depend on other variables;
5. type. Type can be INT (the variable can be only integer number, for example 1, 2, 3,
...) or FLOAT (float number, for example 2.44, 3.789999). If the Type is not specified
it is considered by default as FLOAT. If the Type is INT then min and max must also
be integer numbers!
Default:
type FLOAT.
How to use variables.
History matching can go for any variables. First variables are defined in DEFINES, then they
can be used in any part of model text files (also in arithmetic expressions) via the syntax
@variable name@.
Note: spaces or any other symbols cant be used between variable name and @.
In history matching process the variable will be replaced by a number (from the range, spec-
ified in DEFINES via min-max).
12.1.21. DEFINES 346

Variables cant be used in the maps with dimensions NXxNYxNZ. Dont define in each
grid block its own variable.
Opening of a model with the keyword DEFINES in tNavigator, without starting a

history matching module.
tNavigator opens and calculates the model with the keyword DEFINES, as a normal model.
In this case, all the variables are assigned values that are set for them by default. In all places
in the model files where the syntax @variable name@ is used the default variable values are
substituted.
Example 1. Define a simple variable.
Example
DEFINES
'SWL' 0.2 0.1 0.4/
/
...
EQUALS
SWL @SWL@/
/
In this example the variable is minimum water saturation SWL. Its default value is 0.2,
minimal value is 0.1, maximal value is 0.4.
The the keyword EQUALS (see 12.3.22) is used to assign to an array SWL (see 12.6.27)
the value of this variable in all grid blocks.
One variable depends on the other.

Dependent variable if the value of this variable is calculated from the values of other vari-
ables. History matching can be performed only for independent variables. Dependent variable
can be used to simplify work with expressions @variable_name@ in model files. We should
set only value for dependent variable as a formula with other variables (minimum, maximum,
type are not specified).
Example 2. Define the dependent variable.
12.1.21. DEFINES 347

Example
DEFINES
'SWL' 0.2 0.1 0.4/ independent
'SWCR' @SWL+0.1@ / dependent
/
...
EQUALS
SWL @SWL@/
SWCR @SWCR@/
/
In this example independent variable SWL is introduced (minimal water saturation) and
a dependent variable SWCR (critical water saturation), that is calculated from SWL.
Arithmetics.
Arithmetic expressions can contain:
variable names;
numbers;
arithmetic operations: +, , , /, ^;
brackets;
constants: pi, e;
functions: round, min, max, avg, sum, rand, arand, rnd, abs, exp, log, log10, sqrt, sin,
cos, tan, if (see description in the keyword ARITHMETIC (see 12.3.2)).
Example 3. Use formula inside @...@.
Example
EQUALS
SWCR @SWL+0.1@/
/
Example 4. Use formula inside @...@.
Example
EQUALS
KRW @KRW@/
KRWR @KRW*0.9@/
/
12.1.21. DEFINES 348

Example 5. Use complex formulas.

Lets set the permeability dependence on porosity.
Example
DEFINES
'per1' 6 5 8 /
'per2' 6 5 8 /
/
...
ARITHMETIC
PERMX = @per1@ * exp(PORO * @per2@) /
The variables per1, per2 are defined (their default, min and max values). Permeability in
X-direction (PERMX) depends on porosity (PORO). The coefficients per1 and per2 will be
chosen in assisted history matching process.
Example 6. Use permeability multipliers for layers.
Example
DEFINES
'PERMH_MULT_LAYERS_1' 1 0.1 3 FLOAT/
'PERMH_MULT_LAYERS_2' 2 1 5 INT/
/
...
MULTIPLY
'PERMX' @PERMH_MULT_LAYERS_1@ 1 19 1 28 1 1 /
/
COPY
'PERMX' ' PERMY'/
/
In this example multipliers for PERMX (permeability in X-direction) are specified for
layers (1, 2, 3, 4, 5).
12.1.21. DEFINES 349

Integer variable PERMH_MULT_LAYERS_2 is specified. If has initial value - 2, minimum

value - 1 and maximum - 5 (integer). At the end of the row INT type is specified. Other
variables are float numbers FLOAT.
In the EDIT section PERMX is multiplied by factors (PERMX in the 1-st layer (Z-axis) is
multiplied by the value of the variable PERMH_MULT_LAYERS_1. Analogously for other
layers). Then the values of PERMX are copied to PERMY.
Example 7. Define RP end-points as variables.

In tNavigator RP can be set via Corey correlation (COREYWO (see 12.6.3), COREYGO
(see 12.6.4)) and LET (LETWO (see 12.6.8), LETGO (see 12.6.9)). You can set only end-
points and RP curves are constructed automatically by tNavigator Corey (LET) correlation.
This functionality is very convenient for AHM because you dont need to edit manually
all RP table if you change one point (tables for example SWOF (see 12.6.1), SGOF (see
12.6.2)).
Example
DEFINES
'NO1' 3 0.8 4/
'NO2' 3 0.8 4/
'NW1' 3 0.8 4/
'NW2' 3 0.8 4/
'KRO1' 1 0.3 1/
'KRO2' 1 0.3 1/
'KRW1' 0.6 0.2 1/
'KRW2' 0.6 0.2 1/
'SWL1' 0.1 0.05 0.2 /
'SWL2' 0.1 0.05 0.2 /
'SWCR1' 0.3 0.2 0.4 /
'SWCR2' 0.3 0.2 0.4 /
'SOWCR1' 0.2 0.05 0.4 /
'SOWCR2' 0.2 0.05 0.4 /
/
...
PROPS
COREYWO
@SWL1@ 1 @SWCR1@ @SOWCR1@ 1 @KRO1@ @KRW1@ 1 1 @NO1@ @NW1@ 4 /
@SWL2@ 1 @SWCR2@ @SOWCR2@ 1 @KRO2@ @KRW2@ 1 1 @NO2@ @NW2@ 4 /
/
In this example relative permeability points are taken as variables for 2 saturation regions.
Then in PROPS section these variables are used as parameters of the keyword COREYWO
12.1.21. DEFINES 350

(see 12.6.3).
Example 8. Different geological realizations.

If you have files with different geological realizations of the model (different grid, porosity
etc.) it is possible to define integer variable to switch between file names.
Example
DEFINES
'PORONUM' 2 1 20 INT/
/
...
INCLUDE
'MODEL_PORO_@PORONUM@.inc '
In this example we define integer variable PORONUM (type - INT). It is used in the file
name that is included and contains model porosity realization.
If you use Assisted History Matching and Uncertainty Analysis module tNavigator
generates automatically the keywords PREDEFINES (see 12.1.23), OPEN_BASE_MODEL
(see 12.1.24). These keywords are not intended for self-use in models.
12.1.21. DEFINES 351

12.1.22 VDEF


Section
This keyword is used to specify model variables to tNavigator Assisted History Matching
Module for models in MORE (for E100 and E300 format models one should use the keyword
DEFINES (see 12.1.21)).
The syntax of this keyword is analogous to DEFINES (see 12.1.21).
12.1.22. VDEF 352

12.1.23 PREDEFINES

This keyword is automatically generated by tNavigator if you use Assisted History

Matching and Uncertainty Analysis module. The keyword is not intended for self-use
in models.
To define variables for AHM use the keyword DEFINES (see 12.1.21) (for models in
formats E100, E300) or VDEF (see 12.1.22) (for models in format MORE).
PREDEFINES is written in model variants and it sets variables values in this variant, and
also minimum, maximum variable value and type. The syntax of this keyword is analogous
to DEFINES (see 12.1.21).
The keyword OPEN_BASE_MODEL (see 12.1.24) puts the value of the variable in the
original model instead of @variable_name@.
Example
PREDEFINES
MULT1 1.0000000 0.1000000 3.0000000 FLOAT /
MULT2 2 1 5 INT /
MULT3 1.0000000 0.1000000 2.0000000 FLOAT /
MULT4 1.0000000 0.1000000 3.0000000 FLOAT /
MULT5 1.0000000 0.1000000 3.0000000 FLOAT /
/
OPEN_BASE_MODEL
'PUNQ_exp1.DATA'/
12.1.23. PREDEFINES 353

12.1.24 OPEN_BASE_MODEL

This keyword is automatically generated by tNavigator if you use Assisted History

Matching and Uncertainty Analysis module. The keyword is not intended for self-use
in models.
See the description of the keyword PREDEFINES (see 12.1.23).
12.1.24. OPEN_BASE_MODEL 354

12.1.25 DIMENS


Section
This keyword defines numbers of grid blocks NX, NY, NZ in X , Y , Z directions. X and
Y are surface coordinates, and Z axis is directed vertically downward. The total number of
cells is a product of these three numbers: NX*NY*NZ.
Default: 100 100 1
Example
DIMENS
50 50 1
/
This example defines grid having 50 50 1 blocks, 50 blocks in X direction, 50 blocks

in Y direction and 1 block in Z direction. The grid will consist of 2500 blocks.
Example
DIMENS
30 23 5
/
This example defines a 30 23 5 grid, with 30 blocks in X direction, 23 blocks in Y

direction and 5 blocks in Z direction. Total number of blocks is 3450.
12.1.25. DIMENS 355

12.1.26 TABDIMS


Section
The data consists of five items, describing number of regions with different parameter
values. The numbers specify:
1. number of saturation function regions (SATNUM (see 12.4.3)),
2. number of regions with different PVT properties (PVTNUM (see 12.4.2)),
3. maximum number of nodes of saturation in one PVT table, entered by keywords SGFN
(see 12.6.14), SGOF (see 12.6.2) (IGNORED). This is an Eclipse compatibility field.
In tNavigator number of lines does not have to be specified because the tables are
allocated dynamically,
4. maximum number of nodes of pressure in one PVT table, entered by keywords PVTG
(see 12.5.8), PVTO (see 12.5.4), PVDG (see 12.5.7), PVDO (see 12.5.2) (IGNORED).
This is an Eclipse compatibility field. In tNavigator number of lines does not have to
be specified because the tables are allocated dynamically,
5. number of fluid-in-place regions (FIPNUM (see 12.4.10)).
6. maximum number of nodes of oil vaporization in gas RG,O in one VPT table, entered
by keywords PVTO (see 12.5.4), PVCO (see 12.5.6). This is an Eclipse compatibility
field. In tNavigator number of lines does not have to be specified because the tables
are allocated dynamically,
7. maximum number of nodes of oil-gas ratio RO,G in one PVT table of wet gas, entered
by a keyword PVTG (see 12.5.8). This is an Eclipse compatibility field. In tNavi-
gator number of lines does not have to be specified because the tables are allocated
dynamically,
8. maximum number of saturation end-point versus temperature tables (tables are specified
using the keyword ENPTVT (see 12.14.69)).
9. maximum number of equation of state regions for reservoir conditions (these regions
are entered using the keyword EOSNUM (see 12.4.21)).
10. maximum number of equation of state regions for surface conditions. Default: is equal
to the 9-th parameter of this keyword.
12.1.26. TABDIMS 356

11. maximum number of flux regions (IGNORED). This is an Eclipse compatibility field.
allocated dynamically,
12. maximum number of thermal regions (IGNORED). This is an Eclipse compatibility

field. In tNavigator number of lines does not have to be specified because the tables
are allocated dynamically,
13. number of rock tables (these regions are entered using the keyword ROCKNUM (see
12.4.14)),
14. maximum number of pressure maintenance regions (IGNORED). This is an Eclipse

compatibility field. In tNavigator number of lines does not have to be specified because
the tables are allocated dynamically,
15. the number of temperatures for Ki (p, T ) tables (KVTEMP (see 12.14.6), KVTABTn
(see 12.14.7)).
The division of grid blocks into regions and setting of appropriate values should be
specified below.
Default: 1 1 20 20 1 20 20 1 1
Example
TABDIMS
2 4 2* 3
/
In this example the grid representing the reservoir is
divided into two regions with different flow characteristics,
divided into four PVT regions, each of them with different PVT properties tables,
3-rd and 4-th numbers are equal 20 (default)
divided into three FIP regions, for each of them fluid-in-place data will be reported.
12.1.26. TABDIMS 357

12.1.27 EQLDIMS


Section
The keyword specifies dimensions of the equilibration tables. The data should be termi-
nated with a slash /.
1. number of equilibration regions (EQLNUM (see 12.4.9), EQUIL (see 12.15.2));
2. number of depth nodes in any table of pressure versus depth constructed internally
by the equilibration algorithm; IGNORED, this is an Eclipse compatibility field; In
tNavigator number of lines does not have to be specified because the tables are allocated
dynamically,
3. maximum number of depth nodes in any table RSVD (see 12.15.3), RVVD (see
12.15.5); IGNORED, this is an Eclipse compatibility field; In tNavigator number of
lines does not have to be specified because the tables are allocated dynamically,
4. maximum number of tables of initial tracer concentration versus depth (TVDP (see
12.15.39));
5. maximum number of lines in the table of initial tracer concentration versus depth
(TNUM (see 12.15.38)).
Default:
1. 1;
2. 100;
3. 20;
4. 1;
5. 20.
Example
EQLDIMS
3 2* 2 5
/
In this example the grid will be divided into three regions, for each of them initial distri-
bution of saturations and pressure will be calculated basing on thermodynamic equilibrium.
Maximum number of tables of initial tracer concentration versus depth 2 tables. Maximum
number of lines in the table of initial tracer concentration versus depth 5 lines.
12.1.27. EQLDIMS 358

12.1.28 ACTDIMS


Section
The keyword sets dimensions for the keywords ACTION (see 12.18.131), ACTIONW
(see 12.18.134), ACTIONG (see 12.18.132), ACTIONR (see 12.18.133). The data should
be terminated with a slash /.
1. the maximum number of types of keywords ACTION (see 12.18.131); ignored, this
is an Eclipse compatibility field. In tNavigator number of types does not have to be
specified because the memory is allocated dynamically,
2. the maximum number of lines of SCHEDULE data (including the ENDACTIO keyword),
that can be defined in any one ACTION (see 12.18.131); ignored, this is an Eclipse
compatibility field. In tNavigator number of lines does not have to be specified because
the memory is allocated dynamically,
3. the maximum number of characters per line of ACTION (see 12.18.131) data; ignored,
this is an Eclipse compatibility field. In tNavigator number of characters does not have
to be specified because the memory is allocated dynamically,
Default:
1. 2;
2. 50;
3. 80.
Example
ACTDIMS
5 40 100
/
12.1.28. ACTDIMS 359

12.1.29 REGDIMS


Section
The data consists of items, describing number of regions with different parameter values.
The numbers specify:
1. maximum number of fluid-in-place regions (FIPNUM (see 12.4.10)), also may be

specified with keyword TABDIMS (see 12.1.26), (IGNORED). This is an Eclipse
compatibility field. In tNavigator number of regions does not have to be specified
because the memory is allocated dynamically;
2. maximum number of sets of user-defined fluid-in-place regions (FIP (see 12.4.11));
3. maximum number of independent reservoir regions, (IGNORED). This is an Eclipse

compatibility field. In tNavigator number of regions does not have to be specified
4. maximum number of flux regions (FLUXNUM (see 12.4.18)),
5. IGNORED, this is an Eclipse compatibility field. In tNavigator number of regions does

not have to be specified because the memory is allocated dynamically;
6. maximum number of Coal Bed Methane regions (COALNUM (see 12.4.15)) (IG-
NORED). This is an Eclipse compatibility field. In tNavigator number of regions does
7. IGNORED, this is an Eclipse compatibility field. In tNavigator number of regions does

8. the number of arrays WORK (see 12.3.6), that can be used in OPERATE (see 12.3.25);
9. the number of arrays IWORK (see 12.3.6), that can be used in OPERATE (see 12.3.25);
10. maximum number of polymer flooding mixing region, which are specified via
PLMIXNUM (see 12.2.95), IGNORED, this is an Eclipse compatibility field. In
tNavigator number of regions does not have to be specified because the memory is
allocated dynamically.
Default: 1 1 0 0 0 1 0 0 0 1
12.1.29. REGDIMS 360

Example
REGDIMS
2 2 0 0
/
In this example the grid representing the reservoir is
divided into two FIP regions, for each of them fluid-in-place data will be reported,
divided into two sets of FIP regions, for each of them fluid-in-place data will be
reported.
12.1.29. REGDIMS 361

12.1.30 VFPIDIMS


Section
The keyword sets the dimensions of BHP tables for injectors, which are specified using
the keyword VFPINJ (see 12.18.56). The data should be terminated with a slash /.
1. maximum number of flow values (FLO) in each table;
2. maximum number of tubing head pressure values (THP) in each table;
3. maximum number of BHP tables for injectors.
Default: 0 0 0
Example
VFPIDIMS
10 5 3
/
This example sets: maximum number of flow values (FLO) in each table 10, maximum
number of tubing head pressure values (THP) in each table 5, maximum number of BHP
tables for injectors 3.
12.1.30. VFPIDIMS 362

12.1.31 VFPPDIMS


Section
The keyword sets the dimensions of BHP tables for producers, which are specified using
the keyword VFPPROD (see 12.18.57). The data should be terminated with a slash /.
1. maximum number of flow values (FLO) in each table;
2. maximum number of tubing head pressure values (THP) in each table;
3. maximum number of water fraction (WFR) in each table;
4. maximum number of gas fraction (GFR) in each table;
5. maximum number of artificial lift quantities (ALQ) in each table;
6. maximum number of BHP tables for producers.
Default: 0 0 0 0 0 0
Example
VFPPDIMS
8 5 3 1 0 2
/
This example sets: maximum number of flow values (FLO) in each table 8, maximum
number of tubing head pressure values (THP) in each table 5, maximum number of water
fraction (WFR) in each table 3, maximum number of gas fraction (GFR) in each table 1,
maximum number of BHP tables for producers 2.
12.1.31. VFPPDIMS 363

12.1.32 GPTDIMS


Section
This keyword is used to specify gas plant table dimensions. Gas plant tables are specified
via the keywords GPTABLE (see 12.15.22), GPTABLE3 (see 12.15.24), GPTABLEN (see
12.15.23). The data should be terminated with a slash /.
1. maximum number of gas plant tables. (IGNORED). This is an Eclipse compatibility

field. In tNavigator number of gas plant tables does not have to be specified because
the memory is allocated dynamically;
2. maximum number of rows in gas plant table. (IGNORED). This is an Eclipse com-
patibility field. In tNavigator number of rows in gas plant table does not have to be
specified because the memory is allocated dynamically;
3. maximum number of rows in recovery plant table. (IGNORED). This is an Eclipse

compatibility field. In tNavigator number of rows in recovery plant table does not have
to be specified because the memory is allocated dynamically.
Example
GPTDIMS
3 15
/
12.1.32. GPTDIMS 364

12.1.33 PIMTDIMS


Section
This keyword is used to specify PI scaling tables dimensions. The tables are specified via
PIMULTAB (see 12.18.31). The data should be terminated with a slash /.
1. maximum number of PI scaling tables. (IGNORED). This is an Eclipse compatibility

field. In tNavigator number of gas plant tables does not have to be specified because
2. maximum number of rows in the table. (IGNORED). This is an Eclipse compatibility

field. In tNavigator number of rows in the table does not have to be specified because
the memory is allocated dynamically.
Example
PIMTDIMS
3 15
/
12.1.33. PIMTDIMS 365

12.1.34 ROCKCOMP


Section
The keyword sets the rock compaction option and maximum number of rock regions
(tables of transmissibility dependence on pressure).
The are three parameters (The data should be terminated with a slash /.):
1. rock compaction option:
REVERS rock compaction is fully reversible with increasing pressure;

IRREVERS rock compaction is irreversible with increasing pressure (the pore
space does not re-inflate).
2. the maximum number of rock regions,
3. flag of the Water Induced Compaction option is used: YES or NO. (IGNORED), this is
an Eclipse compatibility field.
Tables of transmissibility dependence on pressure for each rock region are set using the
keyword ROCKTAB (see 12.5.18). For each grid block one should specify the rock region
to which it belongs using ROCKNUM (see 12.4.14).
Note:
If the number of rock regions is specified both in 13-th parameter of TABDIMS (see 12.1.26)
and in 2-nd parameter of ROCKCOMP (see 12.1.34), then the following logic is used to
calculate the number of rock regions:
E100 format: only the 2-nd parameter of ROCKCOMP (see 12.1.34) is used;
E300 format: the maximum value is taken from the 13-th parameter of TABDIMS (see
12.1.26), and 2-nd parameter of ROCKCOMP (see 12.1.34).
Example
ROCKCOMP
IRREVERS 5
/
In this example there are 5 rock regions and rock compaction is irreversible.
12.1.34. ROCKCOMP 366

12.1.35 ROCKDIMS


Section
This keyword can only be used if THERMAL (see 12.1.50) is present.
The keyword specifies the number of types of cap and base rocks with different proper-
ties, which will be used to model the heat exchange between the reservoir and surroundings.
The are three parameters:
1. maximum number of types of cap and base rocks with different properties,
2. IGNORED,
3. the maximum number of grid blocks which can be connected to any rock type (this
parameter is used in the keyword ROCKCON (see 12.2.79)).
Default:
The value of 3-rd parameter is equal to the value of 1-st parameter.
Example
ROCKDIMS
5 1* 6
/
In this example the maximum number of types of cap and base rocks with different
properties is 5; the maximum number of grid blocks which can be connected to any rock
type is 6.
12.1.35. ROCKDIMS 367

12.1.36 WELLDIMS


Section
The keyword sets up dimensions of the well data. The data should be terminated by a
slash /.
12 parameters are to be specified:
1. the maximum number of wells, (IGNORED). This is an Eclipse compatibility field.
In tNavigator number of wells does not have to be specified because the memory is
allocated dynamically;
2. the maximum number of connections that one well can have, (IGNORED). This is an
Eclipse compatibility field. In tNavigator number of connections does not have to be
3. the maximum number of well groups in the model, (IGNORED). This is an Eclipse
compatibility field. In tNavigator number of well groups does not have to be specified
4. the maximum number of wells in one group, (IGNORED). This is an Eclipse compati-
bility field. In tNavigator number of wells in one group does not have to be specified
5. the maximum number of separator stages (the last one - the stock tank - is included),
(IGNORED). This is an Eclipse compatibility field. In tNavigator number of separator
stages does not have to be specified because the memory is allocated dynamically;
6. the maximum number of well streams (WELLSTRE (see 12.18.159)), (IGNORED).

This is an Eclipse compatibility field. In tNavigator number of well streams does not
have to be specified because the memory is allocated dynamically;
7. the maximum number of mixtures (using in injectors), (IGNORED). This is an Eclipse

compatibility field. In tNavigator number of mixtures does not have to be specified
8. the maximum number of separators (field separator is included), (IGNORED). This is

an Eclipse compatibility field. In tNavigator number of separators does not have to be
9. the maximum number of items in any mixture (using in injectors), (IGNORED). This
is an Eclipse compatibility field. In tNavigator number of items in any mixture does
12.1.36. WELLDIMS 368

10. the maximum number of connections groups allowed to cross domain boundary of one
process during a parallel run, (IGNORED). This is an Eclipse compatibility field. In
tNavigator number of connections groups does not have to be specified because the
memory is allocated dynamically;
11. the maximum number of the well lists that one well can belong to simultaneously,
(IGNORED). This is an Eclipse compatibility field. In tNavigator number of the well
lists does not have to be specified because the memory is allocated dynamically;
12. the maximum number of dynamic well lists during the run, (IGNORED). This is an
Eclipse compatibility field. In tNavigator number of dynamic well lists does not have
to be specified because the memory is allocated dynamically.
Default: any parameter zero.
Example
WELLDIMS
200 7 10 20 5 10 5 4 2 0 1 1
/
12.1.36. WELLDIMS 369

12.1.37 FAULTDIM


Section
The keyword sets the number of faults entered via FAULTS (see 12.2.37). The data
should be terminated with a slash /.
1. maximum number of faults specified via FAULTS (see 12.2.37); (IGNORED). This
is an Eclipse compatibility field. In tNavigator number of faults does not have to be
specified because the memory is allocated dynamically.
Example
FAULTDIM
20 /
12.1.37. FAULTDIM 370

12.1.38 WSEGDIMS


Section
The keyword sets dimensions for multi-segment wells (section 2.19.4). The data should
The following data should be entered:
1. maximum number of multi-segment wells; (IGNORED). This is an Eclipse compatibil-

ity field. In tNavigator number of multi-segment wells does not have to be specified
2. maximum number of segments per well; (IGNORED). This is an Eclipse compatibility

field. In tNavigator number of segments per well does not have to be specified because
3. maximum number of branches per multi-segment well; (IGNORED). This is an Eclipse

compatibility field. In tNavigator number of branches per multi-segment well does not
have to be specified because the memory is allocated dynamically.
Example
WSEGDIMS
10 20 4/
12.1.38. WSEGDIMS 371

12.1.39 HEATDIMS


Section
The keyword sets heater dimensions. The description of heater simulation is in the section
4.31.
The following data should be entered (The data should be terminated with a slash /.):
1. maximum number of heater connections; IGNORED, this is an Eclipse compatibility

field. In tNavigator this dimension does not have to be specified because the memory
is allocated dynamically.
Example
HEATDIMS
20 /
12.1.39. HEATDIMS 372

12.1.40 UDQDIMS


Section
The keyword sets dimensions for the keyword UDQ (see 12.18.138). The data should be
terminated with a slash /.
1. maximum number of functions (including brackets) that can be used in a quantity

definition in UDQ (see 12.18.138); (IGNORED). This is an Eclipse compatibility
field. In tNavigator number of functions does not have to be specified because the
2. maximum number of arguments that can be used in a quantity definition; (IGNORED).

This is an Eclipse compatibility field. In tNavigator number of arguments does not
have to be specified because the memory is allocated dynamically;
3. maximum number of user defined connection quantities; (IGNORED). This is an

Eclipse compatibility field. In tNavigator number of defined connection quantities does
4. maximum number of user defined field quantities; (IGNORED). This is an Eclipse com-
patibility field. In tNavigator number of field quantities does not have to be specified
5. maximum number of user defined group quantities; (IGNORED). This is an Eclipse

compatibility field. In tNavigator number of group quantities does not have to be
6. maximum number of user defined region quantities; (IGNORED). This is an Eclipse

compatibility field. In tNavigator number of region quantities does not have to be
7. maximum number of user defined segment quantities; (IGNORED). This is an Eclipse

compatibility field. In tNavigator number of segment quantities does not have to be
8. maximum number of user defined well quantities; (IGNORED). This is an Eclipse com-
patibility field. In tNavigator number of well quantities does not have to be specified
12.1.40. UDQDIMS 373

9. maximum number of user defined aquifer quantities; (IGNORED). This is an Eclipse

compatibility field. In tNavigator number of aquifer quantities does not have to be
10. maximum number of user defined block quantities; (IGNORED). This is an Eclipse
compatibility field. In tNavigator number of block quantities does not have to be
specified because the memory is allocated dynamically.
Example
UDQDIMS
20 10 4 4 4 4 4 4 4 4/
12.1.40. UDQDIMS 374

12.1.41 UDQPARAM


Section
The keyword sets parameters for UDQ (see 12.18.138) keyword. The data should be
1. (IGNORED). This is an Eclipse compatibility field;
2. (IGNORED). This is an Eclipse compatibility field;
3. a value given to undefined elements when outputting data or using in keywords AC-
TIONG (see 12.18.132), ACTIONR (see 12.18.133), ACTIONW (see 12.18.134),
ACTIONX (see 12.18.135));
4. (IGNORED). This is an Eclipse compatibility field.
Example
UDQPARAM
2* 0.01 /
12.1.41. UDQPARAM 375

12.1.42 UDADIMS


Section
This keyword sets dimensions for user defined arguments UDA for the keyword UDQ
(see 12.18.138). The data should be terminated with a slash /.
User defined arguments UDA can be used in keywords WCONINJE (see 12.18.36),
WECON (see 12.18.62), WELDRAW (see 12.18.104), WCONPROD (see 12.18.34), GCON-
PROD (see 12.18.72), GCONINJE (see 12.18.81), GECON (see 12.18.102).
1. maximum number of user defined arguments for well keywords; (IGNORED). This is
an Eclipse compatibility field. In tNavigator number of does not have to be specified
2. maximum number of user defined arguments for group keywords; (IGNORED). This
is an Eclipse compatibility field. In tNavigator number of does not have to be specified
because the memory is allocated dynamically.
Example
UDADIMS
8 8 /
12.1.42. UDADIMS 376

12.1.43 UDTDIMS


Section
This keyword sets dimensions for user defined tables UDT for the keyword UDT (see
1. maximum number of user defined tables UDT (see 12.18.139); (IGNORED). This is
2. maximum number of rows in the table UDT (see 12.18.139); (IGNORED). This is
3. maximum number of interpolation points in any one dimension; (IGNORED). This is

4. maximum number of dimensions in one table UDT (see 12.18.139); (IGNORED). This
is an Eclipse compatibility field. In tNavigator number of does not have to be specified
because the memory is allocated dynamically.
Example
UDTDIMS
1 8 8 1 /
12.1.43. UDTDIMS 377

12.1.44 TRACERS


Section
The keyword sets dimensions for tracers. The data should be terminated with a slash /.
1. the maximum number of passive oil tracers (entered via the keyword TRACER (see
12.7.1)); ignored, this is an Eclipse compatibility field,
2. the maximum number of passive water tracers (entered via the keyword TRACER (see
3. the maximum number of passive gas tracers (entered via the keyword TRACER (see
4. the maximum number of environmental tracers (for environmental tracer option); ig-
nored, this is an Eclipse compatibility field,
5. ignored, this is an Eclipse compatibility field,
12. ignored, this is an Eclipse compatibility field.
Example
TRACERS
4 5
/
In this example there are: 4 passive oil tracers and 5 passive water tracers.
12.1.44. TRACERS 378

12.1.45 NONNC


Section
If this keyword is used, non-neighbor connections wont be allowed. By default non-

neighbor connections are allowed.
Such connections may be set differently, including explicit definition using keyword NNC
(see 12.2.48).
Example
NONNC
In this example non-neighbourhood connections are not allowed.
12.1.45. NONNC 379

12.1.46 SURFACT


Section
The keyword defines that surfactants will be used in the model (surfactant section 2.25).
Example
SURFACT
12.1.46. SURFACT 380

12.1.47 SURFACTW


Section
The keyword defines that surfactants will be used in the model and change of wettability
will be simulated (surfactant section 2.25).
This keyword is not obligatory in tNavigator. In fact wettability calculation starts in case
if one of the tables SURFDW (see 12.8.14) or SURFADDW (see 12.8.13) is specified.
Example
SURFACTW
12.1.47. SURFACTW 381

12.1.48 POLYMER


Section
This keyword indicates that Polymer Flood will be used in the model (section 2.20).

Example
POLYMER
12.1.48. POLYMER 382

12.1.49 ALKALINE


Section
This keyword indicates that Alkaline Flooding will be used in the model section 2.24.

12.1.49. ALKALINE 383

12.1.50 THERMAL


Section
The keyword is used to label that the thermal simulation will be used. The keywords
which can be used in thermal simulation are described in the section "Thermal properties"
(12.14).
Example
THERMAL
12.1.50. THERMAL 384

12.1.51 REACTION


Section
The keyword specifies the number of chemical reactions (nr ). The data should be termi-
Example
REACTION
3 /
In this example there are 3 chemical reactions.
12.1.51. REACTION 385

12.1.52 OIL


Section
The keyword is used to label that a model contains an oil phase. The keyword should be
used if an oil phase exist or could exist in the model. OIL is added automatically for any
compositional model. No parameters are to be specified.
12.1.52. OIL 386

12.1.53 GAS


Section
The keyword is used to label that a model contains a gas phase. The keyword should be
used if a gas phase exist or could exist in the model. GAS is added automatically for any
compositional model. No parameters are to be specified.
12.1.53. GAS 387

12.1.54 WATER


Section
The keyword is used to label that a model contains a water phase (active). No parameters
are to be specified.
12.1.54. WATER 388

12.1.55 VAPOIL


Section
The keyword is used to label that there is vaporised oil in a wet gas. One can use this
keyword only if OIL (see 12.1.52) and GAS (see 12.1.53) are specified.
Lets consider two conditions: vaporised oil has constant and uniform concentration in
a gas phase and the pressure is always above a dew point. In that case a run can be more
efficiency in the following way:
OIL (see 12.1.52) and VAPOIL shouldnt be specified; gas should be considered as a dry
as; specify vaporised oil concentration using keyword RVCONST (see 12.5.14) in the GRID
(12.2) section.
The model will be considered as a model with dry gas, but the constant vaporised oil
concentration will be taken into consideration during a simulation.
No parameters are to be specified.
12.1.55. VAPOIL 389

12.1.56 DISGAS


Section
The keyword is used to label that there is a dissolved gas in live oil. One can use this
keyword only if OIL (see 12.1.52) and GAS (see 12.1.53) are specified.
Lets consider two conditions: dissolved has constant and uniform concentration in an oil
phase and the pressure is always above a dew point. In that case a run can be more effi-
ciency in the following way:
GAS (see 12.1.53) and DISGAS shouldnt be specified; oil should be considered as a dead
oil; specify dissolved gas concentration using keywords RSCONST (see 12.5.12), RSCON-
STT (see 12.5.13) in the GRID (12.2) section.
The model will be considered as a model with dead oil, but the constant dissolved gas
concentration will be taken into consideration during a simulation.
12.1.56. DISGAS 390

12.1.57 SOLID


Section
The keyword is used to label that there is a solid phase in the model (solid phase consists
of one component coke).
12.1.57. SOLID 391

12.1.58 BRINE


Section
This keyword indicates that the Brine Tracking option is enabled, to allow the modeling
of waters with different salinities.
12.1.58. BRINE 392

12.1.59 LOWSALT


Section
This keyword indicates that low salinity option is used 2.26.3.
This keyword automatically turns on the option BRINE (see 12.1.58) simulation of
waters with different salinities section 2.26.1.
12.1.59. LOWSALT 393

12.1.60 TEMP


Section
This keyword indicates that the temperature option is enabled, to allow the modeling of
the temperature effects of cold water injection section 2.30.
12.1.60. TEMP 394

12.1.61 TEMPR


Section
This keyword indicates that the temperature option is enabled, to allow the modeling of
the temperature effects of cold water injection section 2.30.
This keyword is different from the keyword TEMP (see 12.1.60) the following way:
grid blocks with zero pore volume are used in simulation (if they are not disactivated via
ACTNUM (see 12.2.29)). There is no filtration in these blocks, but their heat capacity will
be taken into account in temperature calculations.
12.1.61. TEMPR 395

12.1.62 API


Section
The keyword indicates that an option API tracking is enabled - 2.10.
12.1.62. API 396

12.1.63 ASPHALTE


Section
This keyword indicates that the asphaltene modeling option is enabled 2.23. The fol-
lowing parameters should be specified:
1. characterization criterion:
WEIGHT percentage molar weight of asphaltene dissolved in the oil as a function

of specified variables. If there is only one variable, then appropriate data are set by
keywords ASPP1P (see 12.10.1) and ASPREWG (see 12.10.2). If there are two
variables, then keywords ASPP2P (see 12.10.3) and ASPPW2D (see 12.10.4)
are used.
2. IGNORED, this is an Eclipse compatibility field;
3. viscosity model:
EI Einstein model (highly diluted solution), one variable: slope of relative vis-
cosity with respect to concentration;
KD Krieger-Dougherty model, two parameters: mass concentration at maximum
packing, and intrinsic viscosity;
TAB viscosity multiplier is set as a function of the asphaltene precipitation
fraction;
NO viscosity is not changed.
If the 3-rd parameter is not NO, then keyword ASPVISO (see 12.10.6) must be used.
Default:
characterization criterion: WEIGHT;
viscosity model: NO.
Example
ASPHALTE
WEIGHT 1* TAB /
12.1.63. ASPHALTE 397

12.1.64 FOAM


Section
That keyword indicates that the foam modeling option is enabled 2.21. The data should
12.1.64. FOAM 398

12.1.65 MISCIBLE


Section
That keyword indicates that an option of properties dependence on surface tension is

enabled 2.6.12. The data should be terminated with a slash /.
12.1.65. MISCIBLE 399

12.1.66 DIFFUSE


Section
That keyword indicates that an option of molecular diffusion is enabled.

The keyword doesnt have any parameters.
The diffusion coefficients are specified via DIFFCGAS (see 12.13.47), DIFFCOIL (see
12.13.48).
12.1.66. DIFFUSE 400

12.1.67 CART


Section
The keyword indicates that a Cartesian geometry is used. Cartesian geometry is used by
default so this keyword is not necessary. tNavigator doesnt support radial geometry.
12.1.67. CART 401

12.1.68 SATOPTS


Section
This keyword provides the following relative permeabilities options:

be defined). Six tables should be specified via the keywords KRNUMX (see 12.4.24),
KRNUMX- (see 12.4.24), KRNUMY (see 12.4.24), KRNUMY- (see 12.4.24), KRNUMZ
(see 12.4.24) and KRNUMZ- (see 12.4.24);
HYSTER hysteresis relative permeabilities 2.6.11;
SURFTENS oil-gas or oil-water capillary pressures depend on surface tension. Tables

of surface tension versus pressure are set with the keywords the STOG (see 12.6.57)
and STOW (see 12.6.58).
The list of the options should be terminated with /.
Hysteresis option allows to specify different saturation functions for drainage (decreas-
ing wetting phase saturation) and imbibition (increasing wetting phase saturation) processes.
Hysteresis option is specified via keyword SATOPTS (see 12.1.68) (parameter HYSTER).
For each grid block two saturation function table numbers should be specified:
1. SATNUM (see 12.4.3) specifies the table number of primary drainage curve;
2. IMBNUM (see 12.4.7) specifies the table number of pendular imbibition curve.
If these table numbers are equal for the block, there will be no hysteresis in this block.
If these table numbers are different, hysteresis will be applied according to the model speci-
fied via the keyword EHYSTR (see 12.6.50).
If DIRECT is used with hysteresis, then for each direction I, J and K the imbibition tables
should be specified (IMBNUMX (see 12.4.7), IMBNUMY (see 12.4.7) and IMBNUMZ (see
12.1.68. SATOPTS 402

12.4.7)).
If also IRREVERS is present, then the additional tables for opposite directions should be
specified (IMBNUMX- (see 12.4.7), IMBNUMY- (see 12.4.7) and IMBNUMZ- (see 12.4.7)).
Example
SATOPTS
HYSTER /
Example
SATOPTS
DIRECT IRREVERS /
12.1.68. SATOPTS 403

12.1.69 NUMRES


Section
This keyword sets a number of reservoirs (if the is more than one reservoir). NUMRES
should be present if there is more than one set of coordinate lines (are used in keywords
COORD (see 12.2.8), ZCORN (see 12.2.9)). If the is more than one reservoir the same
number of sets of data COORD should be specified using the keyword RESVNUM (see
12.2.45) and the bounds of reservoirs should be specified using the keyword COORDSYS
(see 12.2.46).
Default: 1
Example
NUMRES
4
/
12.1.69. NUMRES 404

12.1.70 KVALUES


Section
This keyword defines that K-values will be used to control liquid-vapor phase equilibrium.
K-values are entered via the keyword KVTABLE (see 12.13.16).
Example
KVALUES
The keyword has no parameters.
12.1.70. KVALUES 405

12.1.71 ISGAS


Section
The keyword specifies gas condensate run. This keyword provide the following effects:
blocks with single phase are considered as gas blocks;
direct oil-to-gas transition is impossible and near critical interpolation of KrO , KrG is
not done.
Example
ISGAS
12.1.71. ISGAS 406

12.1.72 NOMIX


Section
The keyword defines that interpolation of oil and gas relative permeabilities near critical
point is not used in three-phase models (by default interpolation is used).
Example
NOMIX
12.1.72. NOMIX 407

12.1.73 INCLUDE


Section
This keyword is used in the keyword-based file to include another keyword-based file.
The included file may, in turn, contain INCLUDE keywords. The nesting level is not limited.
If included file name contains spaces, it should be surrounded by quotation marks. Only
one file may be specified after INCLUDE keyword.
Example
INCLUDE title_grid.inc
/
This example causes the program to include file title_grid.inc in the analyzed file.
Note that file name does not contain spaces.
Example
INCLUDE "title grid.inc"
/
Example
INCLUDE 'title grid.inc'
/
These two example cause the program to include the same file title grid.inc. Note
that file name contains a space.
12.1.73. INCLUDE 408

12.1.74 PATHS


Section
The keyword allows aliases for names of paths to files and directories by any names.
This feature allows to reduce directory names length and improves readability. Aliases can
be used with the keywords INCLUDE (see 12.1.73), IMPORT (see 12.2.97), RESTART (see
12.1.14) and GDFILE (see 12.2.47).
It is allowed to specify not more than 100 data lines (i.e. aliases). Each line should be
ended by a symbol /. The data should be terminated with a slash /.
1. alias name for names of paths. Name should contain up to 8 characters long and
enclosed in quotes;
2. path name to be substitute. Path name should contain up to 132 characters long and
enclosed in quotes.
When using an alias, it should be prefixed by a $ which identifies the following string
as an alias.
Example
PATHS
'GRIDS' '/studies/grids'/
'HM' '/pred/historymatch'/
'VFP' '/wells/vfp'/
/ ...
INCLUDE
'$GRIDS/grid_model.grdecl'/
...
IMPORT
'$HM/endpoints/model.data'/
12.1.74. PATHS 409

12.1.75 IMPLICIT


Section
The keyword is used to set the implicit solution procedure for the simulation.
Example
IMPLICIT
12.1.75. IMPLICIT 410

12.1.76 DUALPORO


Section
The keyword sets that the Dual porosity option ( 2.28) will be used in the run.
Dual porosity. In a reservoir with the dual porosity there are two systems: rock matrix
(the biggest part of the reservoir) and fractures (which have high permeability).
Dual porosity single permeability: fluid flow between matrix cells is possible only us-
ing fractures. Fluid flow through the reservoir is possible only in fractures.
Dual porosity dual permeability: fluid flow between neighboring matrix cells is possible.
Dual porosity is specifying by the keyword DUALPORO.

Dual permeability DUALPERM (see 12.1.77).
If these options are used, for every geometric grid block we consider two cells: the matrix
part and the fracture part of this block. One can specify their properties (porosity, permeabil-
ity etc.) independently.
If the keyword DUALPORO or DUALPERM (see 12.1.77) is used, the number of layers
in the Z-direction should be even (this number is entered by the third parameter of the
keyword DIMENS (see 12.1.25) (NZ).
The first half of the grid blocks corresponds to the matrix cells, and the second half
fracture cells. tNavigator automatically create non-neighbor connections which correspond to
the matrix-fracture flows.
Example
DUALPORO
12.1.76. DUALPORO 411

12.1.77 DUALPERM


Section
The keyword sets that the Dual permeability option will be used in the run.
This option allows fluid flows between matrix cells ( 2.28).
Example
DUALPERM
12.1.77. DUALPERM 412

12.1.78 COAL


Section
The keyword sets that the Coal Bed Methane option will be used 2.29.
12.1.78. COAL 413

12.1.79 GRAVDR


Section
This keyword switches on an option of gravity drainage between matrix and fracture cells
for dual porosity models 2.28.2).
If this keyword is used Z-dimensions for matrix blocks parts should be specified via
DZMTRX (see 12.2.74), DZMTRXV (see 12.2.76).
Example
GRAVDR
/
12.1.79. GRAVDR 414

12.1.80 GRAVDRM


Section
This keyword switches on an option of alternative gravity drainage between matrix and
fracture cells for dual porosity models 2.28.2). The data should be terminated with a slash
/.
The keyword can be use instead of GRAVDR (see 12.1.79).
1. is re-infiltration allowed or not: YES oil flow is possible out or the matrix block and
in it, NO oil flow is only possible out of the matrix block.
Default: is re-infiltration allowed or not YES.
Example
GRAVDRM
NO/
12.1.80. GRAVDRM 415

12.1.81 LGR


Section
The keyword sets options and dimensions for local grid refinement (LGR) section 5.6.
1. maximum number of LGRs in the model. This is an Eclipse compatibility field. (IG-
NORED) In tNavigator specification of this number is not obligatory, because memory
is allocated dynamically;
2. maximum number of cells in each LGR. This is an Eclipse compatibility field. (IG-
3. maximum number of amalgamated coarse cells. This is an Eclipse compatibility field.

(IGNORED) In tNavigator specification of this number is not obligatory, because
4. maximum number of LGR amalgamations. This is an Eclipse compatibility field. (IG-

5. maximum number of LGRs in any amalgamation. This is an Eclipse compatibility

field. (IGNORED) In tNavigator specification of this number is not obligatory, because
6. This is an Eclipse compatibility field. (IGNORED)
12.1.81. LGR 416

12.1.82 VISCD


Section
The keyword sets that the Viscous displacement option will be used in the dual porosity
run ( 2.28).
If this option is used, one should specify the distances between fractures (matrix block sizes)
in X, Y and Z directions using keywords LX (see 12.2.64), LY (see 12.2.64), LZ (see
12.2.64).
Viscous Displacement. Viscous displacement fluid flow under the influence of pres-
sure gradient. One can observe a pressure gradient in the dual porosity system. This gradient
moves the fluid in the fracture towards the production well. If this gradient is small and
fracture permeability is high, the matrix-fracture viscous displacement under the influence
of pressure gradient isnt considered. Nevertheless, if fractions have small permeability then
the matrix-fracture viscous displacement under the influence of pressure gradient can be very
important in production.
tNavigator can compute a SIGMA (see 12.2.67) factor using keywords LX (see 12.2.64),
LY (see 12.2.64), LZ (see 12.2.64) and LTOSIGMA (see 12.2.69). If tNavigator compute
SIGMA, any manually input of this parameter (SIGMA (see 12.2.67)) in data file will be
ignored.
Example
VISCD
12.1.82. VISCD 417

12.1.83 NODPPM

x RUNSPEC x GRID EDIT PROPS

Section
The keyword NODPPM cancels a multiplication of permeability (for the fracture blocks)
by porosity (fracture blocks) during the dual porosity run ( 2.28). Since this multiplication
is used to obtain a net bulk fracture permeability one have to enter this value manually if
NODPPM is enabled.
Example
NODPPM
12.1.83. NODPPM 418

12.1.84 NETWORK


Section
The keyword sets dimensions for extended network model. The extended network model
is specified via keywords NODEPROP (see 12.18.88), BRANPROP (see 12.18.87). The data
(Section: NETWORK option. Automatic chokes. Compressors. 2.19.10.)
1. maximum number of nodes in the network model;
2. maximum number of branches in the network model;
3. maximum number of branches connected to any one node in the network model.
Example
NETWORK
10 9 2 /
In this example:
maximum number of nodes in the network model 10;
maximum number of branches in the network model 9;
maximum number of branches connected to any one node in the network model 2.
12.1.84. NETWORK 419

12.1.85 CO2SOL


Section
This keyword turns on the CO 2 solution option. The CO 2 component is then allowed to
exist in all three phases.
Example
CO2SOL
12.1.85. CO2SOL 420

12.1.86 EQLOPTS


Section
The keyword specifies options for the initial equilibration algorithm. The data should be
The following options are possible:
MOBILE this option activates end point correction of the initial mobile fluid critical
saturations. The option can be used only with the option EQUIL (see 12.15.2).
QUIESC this option enables pressure modifications to achieve initial quiescence. If

this option is set, modifications are applied to the phase pressures to make the initial
solution quiescent.
THPRES threshold pressure option.

This option doesnt allow flow between different equilibration regions until the potential
difference exceeds a threshold value (keyword THPRES (see 12.15.7)). This option is
also required if faults have threshold pressures (keyword THPRESFT (see 12.2.39)).
IRREVER this option allow to the threshold pressures for flow in each direction
between equilibration regions to be different. Threshold pressures should be specified
for each direction; option THPRES should be used.
Example
EQLOPTS
THPRES /
12.1.86. EQLOPTS 421

12.1.87 GRIDOPTS


Section
The keyword set options for grid data processing. The data should be terminated with a
slash /.
1. whether you can use these transmissibility multipliers MULTX- (see 12.2.16), MULTY-
(see 12.2.18), MULTZ- (see 12.2.20): YES or NO.
IGNORED, in tNavigator these multipliers can always be used. This is an Eclipse
compatibility field
2. maximum number of MULTNUM (see 12.4.23) regions. If this value is greater than
zero, then in the keyword MULTREGP (see 12.3.15) MULTNUM regions are used.
Else regions FLUXNUM (see 12.4.18).
3. maximum number of pinchout regions PINCHNUM (see 12.2.57).
Default:
maximum number of MULTNUM (see 12.4.23) regions 0.
maximum number of pinchout regions PINCHNUM (see 12.2.57) 0.
Example
GRIDOPTS
NO 4/
12.1.87. GRIDOPTS 422

12.1.88 FORMOPTS


Section
This keywords specifies the options for gas-oil capillary pressure treatment. The data
The following options can be used (switched off by default):
SINGLEP this option sets the different calculation method of the densities that are
used in the hydrostatic term for flow between two cells when the fluid is a single
phase hydrocarbon. By default a single phase hydrocarbon is considered as oil or
gas, corresponding to the fluid critical temperature calculated by Li correlation. The
density for each phase is then taken as the saturation weighted density of the two
cells between which a flow is being calculated. For single phase hydrocarbon: this
leads to discontinuities as a cell changes state, but physically the fluid is a continuous
single phase. This option treats a single phase hydrocarbon the following way, with the
density taken to be the (saturation weighted) hydrocarbon density without worrying if
the hydrocarbon is an oil or a gas;
NOPCSPT this option sets the different method of capillary pressure treatment in
gas-oil system. If this option is switched on then capillary pressure is associated with
the gas phase:
pO = p
pG = p + pcOG
Else by default:
SO
pO = p + pcOG
SO + SG
SG
pG = p + pcOG
SO + SG
Example
FORMOPTS
NOPCSPT/
12.1.88. FORMOPTS 423

12.1.89 NOSIM


Section
The keyword turns off time step simulation in the SCHEDULE section, tNavigator con-
tinues to read and check the data.
Example
NOSIM
12.1.89. NOSIM 424

12.1.90 GASFIELD


Section
This keyword turns on special options of Gas Field Model section 2.19.7.
/.):
1. flag that defines the possibility to use multiple contract groups. In tNavigator always
YES.
2. flag that defines that accelerated iteration scheme will be used in DCQ calculations in
the first pass of the contract period. In tNavigator always NO usual algorithm is
used.
Example
GASFIELD
YES NO /
12.1.90. GASFIELD 425

12.1.91 GEOMECH


Section
The keyword specifies that will be used geomechanical model describing the elastic
deformation of the rock section 2.31. The data should be terminated with a slash /.
Example
GEOMECH
/
12.1.91. GEOMECH 426

12.1.92 RFD_WFRAC


Section
The keyword defines that hydraulic fracture keywords will be used in the model:
WFRAC (see 12.18.122), COMPFRAC (see 12.18.126), WFRACP (see 12.18.124), WFR-
ACL (see 12.18.123), COMPFRACL (see 12.18.127), WFRACPL (see 12.18.125). Keyword
is optional, i.e. the keywords above can be used without it.
Example
RFD_WFRAC
12.1.92. RFD_WFRAC 427

12.1.93 AIM


Section
This keyword enables an AIM (adaptive implicit) solution option.
AIM is used by default in tNavigator for compositional models.

In black-oil models fully implicit is used by default. To use AIM in black-oil one need to
set AIM parameter of the keyword RUNCTRL (see 12.18.119) or use the keyword AIM (see
12.1.93).
If this keyword is used then tNavigator uses AIM 1 method. AIM 2 and other can be
used via AIM option of the keyword RUNCTRL (see 12.18.119). Description of AIM 1, AIM
2, .. is in the keyword RUNCTRL (see 12.18.119).
Use the keyword AIMCTRL (see 12.1.5) to sets the parameters of adaptive implicit method
(AIM).
12.1.93. AIM 428

12.1.94 AIMFRAC


Section
This keyword enables an AIM (adaptive implicit) solution option.

This keyword is IGNORED because tNavigator uses solution methods different from Eclipse.
12.1.93).
Use the keyword AIMCTRL (see 12.1.5) to sets the parameters of adaptive implicit method
(AIM).
12.1.94. AIMFRAC 429

12.1.95 ECHO / NOECHO


Section
These keyword specify echo output for Eclipse.

This keyword is IGNORED because tNavigators output is different from Eclipse output.
12.1.95. ECHO / NOECHO 430

12.1.96 FULLIMP


Section
This keyword enables a fully implicit solution option.

12.1.93).
12.1.96. FULLIMP 431

12.1.97 IMPES


Section
This keyword enables an IMPES solution option.

tNavigator always uses fully implicit solution option.
12.1.97. IMPES 432

12.1.98 HWELLS


Section
The keyword sets the possibility to use direction, other than Z, in which the interval
penetrates the grid block in the keyword COMPDAT (see 12.18.6) in Eclipse. For tNavigator
this keyword is IGNORED and Z-direction can be used without this keyword.
12.1.98. HWELLS 433

12.1.99 PETOPTS


Section
One option is supported: TRANPORV. The data should be terminated with a slash /.
If this option is used, then only NNC connections, that are directly specified via the
keyword NNC (see 12.2.48) are used. Non-neighbor connections that are made due to grid
irregularities are not counted.
Example
PETOPTS
TRANPORV /
12.1.99. PETOPTS 434

12.1.100 PARALLEL / PARAOPTS


Section
These keywords set the parallel calculation option.

12.1.100. PARALLEL / PARAOPTS 435

12.1.101 NPROCX / NPROCKY


Section
These keywords set the parallel calculation option.

12.1.101. NPROCX / NPROCKY 436

12.1.102 MESSAGE / MESSAGES / MSGFILE


Section
These keywords set the parameters of Eclipse messages.

In tNavigator the keywords REPORTFILE (see 12.1.3) and REPORTSCREEN (see 12.1.3)
provide advanced capabilities for tuning of output to log file, and to the screen.
12.1.102. MESSAGE / MESSAGES / MSGFILE 437

12.1.103 WARN / NOWARN / NOWARNEP


Section
These keywords sets the parameters of Eclipse warnings.

In tNavigator the keywords REPORTFILE (see 12.1.3) and REPORTSCREEN (see 12.1.3)
provide advanced capabilities for tuning of output to log file, and to the screen.
12.1.103. WARN / NOWARN / NOWARNEP 438

12.1.104 END


Section
The keyword terminates the input of data in data file. This keyword doesnt have any
parameters.
Example
END
12.1.104. END 439

12.1.105 ECINIT


Section
The keyword sets values of global economical parameters:
1. Initial capital ($);
2. Discount rate (%);
3. Discount starting time step number.
Data line should be ended by a symbol /. The data should be terminated with a slash /.
Example
ECINIT
10000000 11.4 25 /
/
In the example the keyword ECINIT (see 12.1.105) sets values of initial capital (10000000
$) and discount rate (11.4 %). Discount starting time step number is 25.
12.1.105. ECINIT 440

12.1.106 ECDATES


Section
The keyword sets data list. For these dates values of economical parameters (price of oil,
gas and so on) will be set.
tNavigator uses interpolated values from ECVAL (see 12.1.107) to calculate net present
value NPV at reporting time steps.
Example
ECDATES
1 Jan 2020
3 Feb 2020
16 Jun 2020
21 Sep 2021
1 Dec 2021
/
12.1.106. ECDATES 441

12.1.107 ECVAL


Section
The keyword sets values of economical parameters. tNavigator uses interpolated values
from ECVAL (see 12.1.107) to calculate net present value NPV at reporting time steps.
Maximal number of items is 23. Each item starts with the parameter name, then its values
according to dates (keyword ECDATES (see 12.1.106)) are set. Each line of data should be
ended by a symbol /. The data should be terminated with a slash /.
Parameters:
PRICEO price of oil for sale (home) (METRIC: c.u./m 3 ; FIELD: c.u./bbl);
PRICEG price of gas for sale (home) (METRIC: c.u./1000 m 3 ; FIELD: c.u./Mscf);
PRICEXPO price of oil for sale (export) (METRIC: c.u./m 3 ; FIELD: c.u./bbl);
PRICEXPG price of gas for sale (export) (METRIC: c.u./1000 m 3 ; FIELD: c.u./Mscf);
EXPO oil export (%);
EXPG gas export (%);
PRODO oil production expenses (METRIC: c.u./m 3 ; FIELD: c.u./bbl);
PRODG gas production expenses (METRIC: c.u./1000 m 3 ; FIELD: c.u./Mscf);
INJW water injection expenses (METRIC: c.u./m 3 ; FIELD: c.u./bbl);
INJG gas injection expenses (METRIC: c.u./1000 m 3 ; FIELD: c.u./Mscf);
NWELL cost of a new well (METRIC: c.u./well; FIELD: c.u./well);
NWELLG cost of a horizontal part of a well (METRIC: c.u./m; FIELD: c.u./ft);
NWELLV cost of a vertical part of a well (METRIC: c.u./m; FIELD: c.u./ft);
NWELLD cost of a deviated part of a well (METRIC: c.u./m; FIELD: c.u./ft);
NWPERF cost of a one perforation of a well (METRIC: c.u./m; FIELD: c.u./ft);
SRVWPROD maintenance cost of a production well (c.u./well/year);
12.1.107. ECVAL 442

SRVWINJ maintenance cost of a injection well (c.u./well/year);
TRANSO oil transportation cost (home) (METRIC: c.u./m 3 ; FIELD: c.u./bbl);
TRANSG gas transportation cost (home) (METRIC: c.u./1000 m 3 ; FIELD: c.u./Mscf);
TRANSEXPO oil transportation cost (export) (METRIC: c.u./m 3 ; FIELD: c.u./bbl);
TRANSEXPG gas transportation cost (export) (METRIC: c.u./1000 m 3 ; FIELD:

c.u./Mscf);
TAXBURD tax burdens (home) (%);
TAXBURDEXP tax burdens (export) (%).
Default:
if value 1* is specified then parameter value on this date will be interpolated;
parameter values on dates before the first such that value is not defaulted will be equal
to this value on each previous date;
parameter values on dates after the last such that value is not defaulted will be equal
to this value on each following date;
values of unspecified parameters are 0 on each date.
Example
ECVAL
PRICEO 100 1* 150 130 95.4 /
EXPO 30 13 1* 14 /
SRVWPROD 1* 89900 89000 100000 50000 /
/
In the example the keyword ECVAL (see 12.1.107) set oil value at home market (PRICEO),
oil export (EXPO) and maintenance cost of a production well (SRVWPROD). Value of the
first parameter is 125 at the second date; value of the 3-rd parameter is 89900 (it is the first
value which is not defaulted).
12.1.107. ECVAL 443

12.1.108 SCDPDIMS


Section
The keyword defines the number of scale deposition and scale damage tables. These
tables are defined in the section SCHEDULE via the keywords SCDPTAB (see 12.18.227)
and SCDATAB (see 12.18.229). The data should be terminated with a slash /.
Section Scale deposition model 2.27.
1. the number of scale deposition tables to be entered in the keyword SCDPTAB (see
12.18.227);
2. IGNORED. This is an Eclipse compatibility field. The maximum number of entries in

any scale deposition table;
3. the number of scale damage tables to be entered in the keyword SCDATAB (see
12.18.229);
4. IGNORED. This is an Eclipse compatibility field. The maximum number of entries in

any scale damage table.
Default:
the number of scale deposition tables: 0;
the number of scale damage tables: 0.
Example
SCDPDIMS
1 5 1 5 /
12.1.108. SCDPDIMS 444

12.1.109 LGRCOPY


Section
The keyword allows blocks of refined grid (the keyword LGR (see 12.1.81)) to inherit
formation properties from parent grid host blocks.
If the keyword is used in the RUNSPEC section, then it will be applied to all LGRs:
when new LGR is entered (i.e. the keyword CARFIN (see 12.2.87) is defined), then current
PORO (see 12.2.24), PERMX (see 12.2.13), PERMY (see 12.2.13), PERMZ (see 12.2.13)
and NTG (see 12.2.25) properties will be copied from parent grid into local.
If you need to copy data only for specific LGRs, this keyword should be defined inside
specific CARFIN (see 12.2.87), ENDFIN (see 12.2.89) see an Example 1.
Example 1:
Example
CARFIN
'MYLGR' 1 5 2 4 1 1 10 9 1 8 'GLOBAL'
/
LGRCOPY
MULTIPLY
'PORO' 2 1 10 1 9 1 1/
/
ENDFIN
In case of nested LGRs the properties are copied from direct parent see an Example 2.
If in a certain block a value is not set, then this value (unset) is inherited as well. Therefore,
if you want to copy all the specified values, you need to use LGRCOPY keyword throughout
the chain of parent grids.
Example 2:
12.1.109. LGRCOPY 445

Example
CARFIN
'MYLGR' 1 5 2 4 1 1 10 9 1 8 'GLOBAL'
/
LGRCOPY
MULTIPLY
'PORO' 2 1 10 1 9 1 1/
/
ENDFIN
CARFIN
'NESTLGR' 4 8 1 5 1 1 20 15 1 8 'MYLGR'
/
LGRCOPY
MULTIPLY
'PORO' 2 1 20 1 15 1 1/
/
ENDFIN
In this example properties for MYLGR are copied form global grid GLOBAL, properties
from NESTLGR are copied from its parent MYLGR. In the log-file there will be messages:
Example
Array 'PORO' was copied from LGR 'GLOBAL' to LGR 'MYLGR'.
Warning: Array 'PORO' was copied from LGR 'MYLGR' to LGR
'NESTLGR'.
12.1.109. LGRCOPY 446

12.1.110 BIGMODEL


Section
This keyword is used to run big models in simulator Eclipse.

This keyword is IGNORED in tNavigator because of different data input-output.
12.1.110. BIGMODEL 447

12.1.111 JALS


Section
This keyword sets the usage of linear solver JALS for thermal problems in simulator
Eclipse.
This keyword is IGNORED in tNavigator.
Solution methods that are used in tNavigator are described in the section 5.
12.1.111. JALS 448

12.1.112 SKIPSTAB


Section
This keyword sets the solution method for compositional problems in simulator Eclipse.
This keyword is IGNORED in tNavigator.
Solution methods that are used in tNavigator are described in the section 5.
12.1.112. SKIPSTAB 449

12.1.113 LICENSES


Section
This keyword sets license parameters for simulator Eclipse.

This keyword is IGNORED in tNavigator because of different license policy.
12.1.113. LICENSES 450

12.1.114 MEMORY


Section
These keywords sets parameters for memory allocation for simulator Eclipse.
This keyword is IGNORED in tNavigator because of different memory allocation.
12.1.114. MEMORY 451

12.1.115 FMTIN/ FMTSAVE


Section
These keywords define parameters for RESTART files of simulator Eclipse.

In tNavigator restart is possible only if the base model is calculated in tNavigator. The
keyword RESTART (see 12.1.14).
12.1.115. FMTIN/ FMTSAVE 452

12.1.116 MULTIN/ MULTSAVE


Section

12.1.116. MULTIN/ MULTSAVE 453

12.1.117 MONITOR/ NOMONITO


Section
These keywords define parameters for run-time monitoring for simulator Eclipse.
In tNavigator calculation run-time monitoring is always available in graphical user inter-

face.
12.1.117. MONITOR/ NOMONITO 454

12.1.118 PSPLITX/ PSPLITY/ PSPLITZ


Section
These keywords set blocks division between MPI processes in parallel version of simu-
lator Eclipse.
This keyword is IGNORED. In MPI-version of tNavigator automatic balancing of active grid
blocks between MPI processes is used.
12.1.118. PSPLITX/ PSPLITY/ PSPLITZ 455

12.1.119 RPTHMD/ RPTHMG/ RPTHMW


Section
These keywords set parameters for HMD files for simulator Eclipse.
12.1.119. RPTHMD/ RPTHMG/ RPTHMW 456

12.1.120 RPTISOL/ RPTPROPS/ RPTREGS/ RPTRUNSP/ RPTSCHED/ RPTSMRY/

RPTSOL

x RUNSPEC GRID x EDIT x PROPS

Section
These keywords set parameters for results files for simulator Eclipse.
12.1.120. RPTISOL/ RPTPROPS/ RPTREGS/ RPTRUNSP/ RPTSCHED/ RPTSMRY/ RPTSOL457

12.1.121 UNIFIN/ UNIFSAVE


Section

12.1.121. UNIFIN/ UNIFSAVE 458

12.1.122 PVTGEN


Section
The keyword allows to calculate models which are hybrid in sense of PROPS (see 12.5.1)
section: i.e. in black-oil models set of compositional properties instead of oil and gas PVT
tables is defined. This set of properties is used to calculate PVT tables. Then these tables are
used to calculate model.
1. the number of components;

2. minimal pressure (METRIC: barsa; FIELD: psia);
3. maximal pressure (METRIC: barsa; FIELD: psia);
4. the number of pressure values for which PVT tables will be calculated;
5. oil PVT table:
PVDO;
PVTO;
NONE table for this phase will not be calculated;
6. gas PVT table:
PVTG;
PVTG;
NONE table for this phase will not be calculated;

Default:
minimal pressure: pressure value defined in STCOND (see 12.13.8);
maximal pressure: 100 minimal pressure;
the number of pressure values: 50.
Example
PVTGEN
5 1* 1* 1* NONE PVDG /
12.1.122. PVTGEN 459

12.1.123 CBMOPTS


Section
The keyword is used to set preferences for the Coal Bed Methane Model (see section
2.29). It can be used only if this option is activated by the keyword COAL (see 12.1.78).
1. adsorption model:
INSTANT in this case adsorption time tends to zero; flows between blocks are
absent, adsorption is considered as additional source.
Example
CBMOPTS
INSTANT /
12.1.123. CBMOPTS 460

12.1.124 DPCDT


Section
The keyword sets the maximum rate of change of capillary pressure in explicit cells.
Instead of setting the capillary pressure the limit is set at which it can change from step to
step.
1. maximum rate of change of capillary pressure in explicit cells (METRIC: bars/day,

FIELD: psi/day).
Default:
0.0099972 psi/day for AIM, no limit for fully implicit runs.
Example
DPCDT
1* /
In the example the maximum rate of change of capillary pressure value is defaulted.
12.1.124. DPCDT 461

12.2. Grid section tNavigator-4.2
12.2 Grid section

This section describes all keywords necessary for rectangular grid hydrodynamic model de-
scription.
In tNavigator local grid refinements can be specified section 5.6.
12.2. Grid section 462

12.2.1 GRID

RUNSPEC x GRID EDIT PROPS

Section
The keyword specifies the beginning of data section which contains the keywords neces-
sary for rectangular grid hydrodynamic model description.
12.2.1. GRID 463

12.2.2 DX / DY / DZ


Section
The keywords specify sizes of cells (METRIC: m, FIELD: f t ) first in X direction, then
in Y and Z directions. The same number of values as number of cells in corresponding
direction must be specified (NX * NY * NZ). The data should be terminated with a slash /.
This keyword is used in block-centred geometry 5.5.

Default: none
Example
DIMENS
10 10 2
/
...
DX
50*610 150*520
/
DY
200*470
/
DZ
100*5
100*10
/
This example sets grid block sizes for a 200-block grid: first 50 grid blocks are 610
470 5 m 3 , next 50 grid blocks are 520 470 5 m 3 , and the rest 100 grid blocks are
520 470 10 m 3 .
In the three consecutive examples NX=5, NY=3, NZ=2.
Example
DIMENS
5 3 2
/
...
DX
30*200
/
12.2.2. DX / DY / DZ 464
In this example all grid block sizes in X direction are the same and are equal to 200 m.
Example
DIMENS
5 3 2
/
...
DZ
6.84 6.62 6.87 6.95 6.99 6.80 6.94 7.70 7.76
8.40 7.70 7.76 6.93 8.83 10.63
6.84 6.62 6.87 6.95 6.99 6.80 6.94 7.70 7.76
8.40 7.70 7.76 6.93 8.83 10.63
/
In this example sizes of all grid blocks in Z direction are specified.
12.2.2. DX / DY / DZ 465
12.2.3 DXV


Section
Used to set grid block sizes in X direction, in case when all blocks with the same i-
coordinate have the same size in this direction (METRIC: m, FIELD: f t ). NX values should
be specified, where NX is set in DIMENS (see 12.1.25).

Default: None.
Example
DIMENS
12 10 2
/
DXV
10 3*9 2*2 10 3*9 2*2 /
In this example all cells with i-coordinate equal to 1 have DX = 10; cells with i-
coordinates 2, 3, 4 have DX = 9, cells with i-coordinates 5, 6 have DX = 2. Moreover,
cells with i-coordinate 7 have DX = 10, with coordinates 8, 9, 10 have DX = 9, and with
coordinates 11, 12 have DX = 2.
12.2.3. DXV 466

12.2.4 DYV


Section
Used to set grid block sizes in Y direction, in case when all blocks with the same j -
coordinate have the same size in this direction (METRIC: m, FIELD: f t ). NY values should
be specified, where NY is set in DIMENS (see 12.1.25).

Default: None.
Example
DIMENS
12 12 2
/
DYV
10 3*9 2*2 10 3*9 2*2 /
In this example all cells with j -coordinate equal to 1 have DY = 10; cells with j -
coordinates 2, 3, 4 have DY = 9, cells with j -coordinates 5, 6 have DY = 2. Moreover,
cells with j -coordinate 7 have DY = 10, with coordinates 8, 9, 10 have DY = 9, and with
coordinates 11, 12 have DY = 2.
12.2.4. DYV 467

12.2.5 DZV


Section
Used to set grid block sizes in Z direction, in case when all blocks with the same k -
coordinate have the same size in this direction (METRIC: m, FIELD: f t ). NZ values should
be specified, where NZ is set in DIMENS (see 12.1.25).

Default: None.
Example
DIMENS
12 10 12
/
DZV
10 3*9 2*2 10 3*9 2*2 /
In this example all cells with k -coordinate equal to 1 have DZ = 10; cells with k -
coordinates 2, 3, 4 have DZ = 9, cells with k -coordinates 5, 6 have DZ = 2. Moreover,
cells with k -coordinate 7 have DZ = 10, with coordinates 8, 9, 10 have DZ = 9, and with
coordinates 11, 12 have DZ = 2.
12.2.5. DZV 468

12.2.6 TOPS


Section
The keyword sets depths (METRIC: m, FIELD: f t ) of the tops of each grid blocks. One
value for each block should be specified. The data should be terminated with a slash /.

Default: none
Example
DIMENS
10 10 1
/
...
TOPS
2238.0 2238.0 2238.0 2238.0 2238.0 2238.0 2238.0 2238.0
2238.0 2238.0 2238.0 2238.0 2238.0 2238.0 2238.0 2238.0
2238.0 2238.0 2238.0 2238.0 2238.0 2238.0 2294.0 2295.3
2296.2 2297.5 2298.9 2299.0 2297.7 2296.3 2294.9 2294.1
2294.8 2296.7 2298.7 2300.5 2300.3 2298.3 2296.7 2295.1
2293.6 2293.1 2293.0 2292.3 2291.5 2290.6 2290.4 2290.2
2289.2 2288.2 2287.1 2285.3 2281.3 2275.7 2270.1 2265.4
2266.0 2272.7 2281.5 2238.0 2238.0 2238.0 2238.0 2238.0
2238.0 2238.0 2238.0 2238.0 2238.0 2238.0 2238.0 2238.0
2238.0 2238.0 2238.0 2238.0 2238.0 2238.0 2238.0 2238.0
2292.3 2293.5 2294.7 2295.9 2297.1 2298.2 2298.2 2296.9
2295.5 2294.0 2292.7 2293.0 2295.0 2297.0 2298.9 2299.6
2298.6 2297.1 2295.6 2294.2
/
This example sets depths of tops for 100 grid blocks.
12.2.6. TOPS 469

12.2.7 MIDS


Section
The keyword sets depths (METRIC: m, FIELD: f t ) of the middle of each grid blocks.
One value for each block should be specified. The data should be terminated with a slash /.
This keyword is an alternative to TOPS (see 12.2.6). If MIDS is used then the values
TOPS for each grid block k are calculated via the formula:
DZk
T OPSk = MIDSk
2
Example
DIMENS
7 4 1
/
...
MIDS
2301.98 2303.87 2305.78 2306.86 2303.06 2301.29 2298.46
2297.36 2297.32 2294.87 2293.37 2293.87 2293.40 2296.34
2303.12 2302.26 2300.51 2300.07 2294.68 2288.54 2286.85
2238.09 2238.09 2238.09 2238.09 2301.15 2302.94 2304.96
/
In this example the mid-point depths are set for the grid 7x4x1.
12.2.7. MIDS 470

12.2.8 COORD


Section
This keyword is used in corner-point geometry 5.5. See also the description of the
keyword ZCORN (see 12.2.9).
This keyword is used to specify coordinate lines in Z direction. A coordinate line defines
the possible position for grid block corner points, for each (i,j) cell. A coordinate line is
specified by two triplets of X, Y and Z coordinates, representing two distinct points on it.
Default: none.
Example
DIMENS
1 2 1
/
...
COORD
0 0 1 0 0 2
1 0 1 1 0 2
0 1 1 0 1 2
1 1 1 1 1 2
0 2 1 0 2 2
1 2 1 1 2 2
/
In this example for all corner points on the top surface of reservoir specified vertical
coordinate lines.
12.2.8. COORD 471

12.2.9 ZCORN


Section
This keyword is used in corner-point geometry 5.5. See also the description of the
keyword COORD (see 12.2.8).
Each grid block has 8 corners. This keyword enables the depths (METRIC: m, FIELD:
f t ) of each corner of each grid block to be separately specified. It is used for specifying
depths for corner point geometry.
The keyword line is followed by 2 NX 2 NY 2 NZ values, with the two corners
in the X direction of the first grid block being specified first, then two corners for the next
block in the i direction, and so on.
Default: none.
Example
DIMENS
1 2 2
/
...
ZCORN
8*2500
8*2505
8*2505
8*2515
/
In this example top of first layer grid blocks is specified as 2500, DZ for first layer grid
blocks is specified as 5 and 10 for DZ in second layer grid blocks.
12.2.9. ZCORN 472

12.2.10 ADDZCORN


Section
The keywords specifies a constant to be added to the corner point depth array ZCORN
(see 12.2.9).
Any data lines, terminated with a slash /, could be entered. All data should be terminated
with a final slash /.
Parameters 2-7 specify the box in which the corner depth will be modified. Parameters 8-11
specify continuous with the surrounding cells or discontinuous this modification will be.
One data line contains the following parameters:
1. constant to be added to the corner point depth array ZCORN (see 12.2.9) (may be
positive and negative) (METRIC: m, FIELD: f t );
2. X1 first block in X-axis direction that will be modified;
3. X2 last block in X-axis direction that will be modified (0 X1 X2 NX ) (NX ,

NY , NZ - grid dimensions, specified by DIMENS (see 12.1.25));
4. Y1 first block in Y-axis direction that will be modified;
5. Y2 last block in Y-axis direction that will be modified (0 Y1 Y2 NY );
6. Z1 first block in Z-axis direction that will be modified;
7. Z2 last block in Z-axis direction that will be modified (0 Z1 Z2 NZ );
8. X1A value: X1 1 or X1 ;
9. X2A value: X2 + 1 or X2 (0 X1A NX , 0 X2A NX );
10. Y1A value: Y1 1 or Y1 ;
11. Y2A value: Y2 + 1 or Y2 (0 Y1A NY , 0 Y2A NY );
12. action:
ALL top and bottom corner points of block will be modified;

TOP top and bottom corner points of block will be modified, except the bottom
layer (the top corners will be only modified in this layer);
BOTTOM top and bottom corner points of block will be modified, except the
top layer (the bottom corners will be only modified in this layer).
12.2.10. ADDZCORN 473

Default: parameters 8-11 specify a continuous surface.
if only certain corners within a block should be modified any of the values X1 , X2 ,
Y1 , Y2 may be 0;
X1A = X1 1 (if X1 > 1);
X2A = X2 + 1 (if X2A < NX );
Y1A = Y1 1 (if Y1 > 1);
Y2A = Y2 + 1 (if Y2A < NY );
action ALL.
Example
ADDZCORN
6.0 7 8 7 8 1 18 /
/
In this example 6 metres are added to the corner depth to all layers from 1 to 18.
12.2.10. ADDZCORN 474

12.2.11 OLDTRAN


Section
This keyword specifies block center transmissibility method.

Transmissibilities are calculated using the values DX (see 12.2.2), DY (see 12.2.2), DZ (see
12.2.2) without reference to corner point positions.
This keyword doesnt have any parameters.

This method is used by default in block-center geometry (keywords DX (see 12.2.2) (or
DXV (see 12.2.3)), DY (see 12.2.2) (or DYV (see 12.2.4)), DZ (see 12.2.2) (or DZV (see
12.2.5)) and TOPS (see 12.2.6).)
12.2.11. OLDTRAN 475

12.2.12 NEWTRAN


Section
This keyword specifies block corner transmissibility method.

Transmissibilities are calculated using grid corner points positions.
This keyword doesnt have any parameters.

This method is used by default in corner-point geometry (keywords COORD (see 12.2.8)
and ZCORN (see 12.2.9)).
In block-center geometry (DX (see 12.2.2) (or DXV (see 12.2.3)), DY (see 12.2.2)
(or DYV (see 12.2.4)), DZ (see 12.2.2) (or DZV (see 12.2.5)) and TOPS (see 12.2.6))
OLDTRAN (see 12.2.11) method is used by default. To use NEWTRAN method this keyword
must be specified.
12.2.12. NEWTRAN 476

12.2.13 PERMX / PERMY / PERMZ


Section
These keywords specify absolute permeability values first in X , then in Y and then in
Z directions (mD). The same number of values as number of grid blocks must be specified.
These are diagonal components of absolute permeability tensor in 2.4.
Default: none
Example
DIMENS
5 5 4
/
...
PERMX
100*1
PERMY
100*1
PERMZ
100*10
In this example absolute permeability values in X (PERMX), Y (PERMY), and Z

(PERMZ) directions are specified for a 100-block grid.
Example
DIMENS
5 6 2
/
...
PERMY
103 103 103 103 103 104 104 104 104 104 105 105 105 105 105
106 106 106 106 106 106 106 106 106 106 106 106 106 106 106
103 103 103 103 103 104 104 104 104 104 105 105 105 105 105
106 106 106 106 106 106 106 106 106 106 106 106 106 106 106
/
12.2.13. PERMX / PERMY / PERMZ 477

12.2.14 PERMMF


Section
The keyword sets permeability values between matrix and fracture cells. Description of
dual porosity option is in the section 2.28.
1. permeability value for each matrix cell (METRIC: mD, FIELD: mD). Nx Ny Nz /2
values should be specified.
Example
PERMMF
125*0.5 /
12.2.14. PERMMF 478

12.2.15 MULTX


Section
This keyword is used to specify transmissibility multipliers in X-direction for plane

between blocks [I, J, K] and [I + 1, J, K]. The keyword should be followed by one non-
negative real number for every grid block. The data should be terminated with a slash
/.
The keyword MULTX can be used several times. In this case:
If MULTX is used several times in one section (GRID, EDIT) the values will be
overwritten. I.e. MULTX is equal to the last specified value.
If MULTX is used several times in different section (GRID and EDIT) the value of
MULTX, specified in GRID section are multiplied by the value, specified in EDIT
section.
In SCHEDULE section MULTX can be entered at every time step. The effect is
cumulative (each time MULTX is specified, it multiplies the current X-direction).
Note: for models in E300 format MULTX cant be used in the EDIT section. In this case
it will be ignored.
Default: 1 in all cells.
Example
DIMENS
5 5 4
/
...
MULTX
100*1.5
/
MULTX
100*2.0
/
In this example transmissibility multipliers are specified for all planes in X-direction as
1.5 2.0 = 3.0.
12.2.15. MULTX 479

12.2.16 MULTX-


Section
This keyword is used to specify transmissibility multipliers in X-direction for plane be-
tween blocks [I, J, K] and [I 1, J, K]. If MULTX and MULTX- are both specified their
product will be used. For example, MULTX is specified for block [I, J, K] and MULTX- is
specified for block [I + 1, J, K]. Then the transmissibility multiplier between these two blocks
is equal to the product of MULTX and MULTX-.
The keyword should be followed by one non-negative real number for every grid block.
The keyword MULTX- can be used several times. In this case:
If MULTX- is used several times in one section (GRID, EDIT) the values will be
overwritten. I.e. MULTX- is equal to the last specified value.
If MULTX- is used several times in different section (GRID and EDIT) the value of
MULTX-, specified in GRID section are multiplied by the value, specified in EDIT
section.
In SCHEDULE section MULTX- can be entered at every time step. The effect is
cumulative (each time MULTX- is specified, it multiplies the current X-direction).
Note: for models in E300 format MULTX- cant be used in the EDIT section. In this
case it will be ignored.

Example
DIMENS
5 5 4
/
...
MULTX-
100*1.5
/
MULTX-
100*2.0
/
In this example transmissibility multipliers are specified for all planes in X-direction as
1.5 2.0 = 3.0.
12.2.16. MULTX- 480

12.2.17 MULTY


Section
This keyword is used to specify transmissibility multipliers in Y-direction for plane be-
tween blocks [I, J, K] and [I, J + 1, K]. The keyword should be followed by one non-negative
real number for every grid block. The data should be terminated with a slash /.
The keyword MULTY can be used several times. In this case:
If MULTY is used several times in one section (GRID, EDIT) the values will be
overwritten. I.e. MULTY is equal to the last specified value.
If MULTY is used several times in different section (GRID and EDIT) the value of
MULTY, specified in GRID section are multiplied by the value, specified in EDIT
section.
In SCHEDULE section MULTY can be entered at every time step. The effect is
cumulative (each time MULTY is specified, it multiplies the current Y-direction).
Note: for models in E300 format MULTY cant be used in the EDIT section. In this case
it will be ignored.
Example
DIMENS
5 5 4
/
...
MULTY
100*1.5
/
MULTY
100*2.0
/
In this example transmissibility multipliers are specified for all planes in Y-direction as
1.5 2.0 = 3.0.
12.2.17. MULTY 481

12.2.18 MULTY-


Section
This keyword is used to specify transmissibility multipliers in Y-direction for plane be-
tween blocks [I, J, K] and [I, J 1, K].
If MULTY and MULTY- are both specified their product will be used. For example,
MULTY is specified for block [I, J, K] and MULTY- is specified for block [I, J + 1, K]. Then
the transmissibility multiplier between these two blocks is equal to the product of MULTY
and MULTY-.
The keyword MULTY- can be used several times. In this case:
If MULTY- is used several times in one section (GRID, EDIT) the values will be
overwritten. I.e. MULTY- is equal to the last specified value.
If MULTY- is used several times in different section (GRID and EDIT) the value of
MULTY-, specified in GRID section are multiplied by the value, specified in EDIT
section.
In SCHEDULE section MULTY- can be entered at every time step. The effect is
cumulative (each time MULTY- is specified, it multiplies the current Y-direction).
Note: for models in E300 format MULTY- cant be used in the EDIT section. In this case
it will be ignored.
Example
DIMENS
5 5 4
/
...
MULTY-
100*1.5
/
MULTY-
100*2.0
/
12.2.18. MULTY- 482

In this example transmissibility multipliers are specified for all planes in Y-direction as
1.5 2.0 = 3.0.
12.2.18. MULTY- 483

12.2.19 MULTZ


Section
This keyword is used to specify transmissibility multipliers in Z-direction for plane be-
tween blocks [I, J, K] and [I, J, K + 1]. The keyword should be followed by one non-negative
real number for every grid block. The data should be terminated with a slash /.
The keyword MULTZ can be used several times. In this case:
If MULTZ is used several times in one section (GRID, EDIT) the values will be
overwritten. I.e. MULTZ is equal to the last specified value.
If MULTZ is used several times in different section (GRID and EDIT) the value of
MULTZ, specified in GRID section are multiplied by the value, specified in EDIT
section.
In SCHEDULE section MULTZ can be entered at every time step. The effect is cumu-
lative (each time MULTZ is specified, it multiplies the current Z-direction).
Note: for models in E300 format MULTZ cant be used in the EDIT section. In this case
it will be ignored.
Example
DIMENS
5 5 4
/
...
MULTZ
100*1.5
/
MULTZ
100*2.0
/
In this example transmissibility multipliers are specified for all planes in Z-direction as
1.5 2.0 = 3.0.
12.2.19. MULTZ 484

12.2.20 MULTZ-


Section
This keyword is used to specify transmissibility multipliers in Z-direction for plane be-
tween blocks [I, J, K] and [I, J, K 1].
If MULTZ and MULTZ- are both specified their product will be used. For example,
MULTZ is specified for block [I, J, K] and MULTZ- is specified for block [I, J, K + 1]. Then
the transmissibility multiplier between these two blocks is equal to the product of MULTZ
and MULTZ-.
The keyword MULTZ- can be used several times. In this case:
If MULTZ- is used several times in one section (GRID, EDIT) the values will be
overwritten. I.e. MULTZ- is equal to the last specified value.
If MULTZ- is used several times in different section (GRID and EDIT) the value of
MULTZ-, specified in GRID section are multiplied by the value, specified in EDIT
section.
In SCHEDULE section MULTZ- can be entered at every time step. The effect is
cumulative (each time MULTZ- is specified, it multiplies the current Z-direction).
Note: for models in E300 format MULTZ- cant be used in the EDIT section. In this case
it will be ignored.
Example
DIMENS
5 5 4
/
...
MULTZ-
100*1.5
/
MULTZ-
100*2.0
/
12.2.20. MULTZ- 485

In this example transmissibility multipliers are specified for all planes in Z-direction as
1.5 2.0 = 3.0.
12.2.20. MULTZ- 486

12.2.21 HMMLTPX / HMMLTPY / HMMLTPZ / HMMLTPXY


Section
These keywords specify cumulative permeability multipliers.
The keywords are multipliers to values PERMX (see 12.2.13), PERMY (see 12.2.13),
PERMZ (see 12.2.13), that have been previously specified.
HMMLTPX cumulative permeability multipliers in X-axis direction. The keyword acts

as a multiplier on any values PERMX (see 12.2.13) that have been previously specified;
HMMLTPY cumulative permeability multipliers in Y-axis direction. The keyword acts

as a multiplier on any values PERMY (see 12.2.13) that have been previously specified;
HMMLTPZ cumulative permeability multipliers in Z-axis direction. The keyword acts

as a multiplier on any values PERMZ (see 12.2.13) that have been previously specified;
HMMLTPXY cumulative permeability multipliers in X and Y directions. The keyword

acts as a multiplier on any values PERMX (see 12.2.13) and PERMY (see 12.2.13)
that have been previously specified;
The same number of values as the number of grid blocks should be entered. The data
The keywords could be used with the keywords EQUALS (see 12.3.22) and BOX (see
12.3.3).
Example
EQUALS
'HMMLTPX' 0.7 5 10 5 10 20 30 /
/
In this example for each cell in 5x5x10 box cumulative permeability multipliers in X-axis
direction are set to 0.75.
12.2.21. HMMLTPX / HMMLTPY / HMMLTPZ / HMMLTPXY 487

12.2.22 HMMULTX / HMMULTY / HMMULTZ / HMMLTXY / HMMULTPV


Section
These keywords specify cumulative pore volume and transmissibility multipliers.
The keywords are multipliers to values MULTX (see 12.2.15), MULTY (see 12.2.17),
MULTZ (see 12.2.19), MULTPV (see 12.2.28), that have been previously specified.
HMMULTX cumulative transmissibility multipliers in X-axis direction. For plane

between blocks [I, J, K] and [I + 1, J, K] transmissibility value will be multiplied by
this multiplier. The keyword acts as a multiplier on any values MULTX (see 12.2.15)
HMMULTY cumulative transmissibility multipliers in Y-axis direction. The keyword

acts as a multiplier on any values MULTY (see 12.2.17) that have been previously
specified;
HMMULTZ cumulative transmissibility multipliers in Z-axis direction. The keyword

acts as a multiplier on any values MULTZ (see 12.2.19) that have been previously
specified;
HMMLTXY cumulative transmissibility multipliers in X and Y direction. The keyword

acts as a multiplier on any values MULTX (see 12.2.15) and MULTY (see 12.2.17)
HMMULTPV cumulative pore volume multipliers. The keyword acts as a multiplier

on any values MULTPV (see 12.2.28) that have been previously specified.
12.3.3).
Example
EQUALS
'HMMULTX' 0.75 5 10 5 10 20 30 /
/
In this example for each cell in 5x5x10 box cumulative transmissibility multipliers in
X-axis direction are set to 0.75.
12.2.22. HMMULTX / HMMULTY / HMMULTZ / HMMLTXY / HMMULTPV 488

12.2.23 HMMULTX- / HMMULTY- / HMMULTZ-


Section
These keywords specify cumulative transmissibility multipliers.
The keywords are multipliers to values MULTX- (see 12.2.16), MULTY- (see 12.2.18),
MULTZ- (see 12.2.20), that have been previously specified.
HMMULTX- cumulative transmissibility multipliers in X-axis direction. For plane

between blocks [I 1, J, K] and [I, J, K] transmissibility value will be multiplied by
this multiplier. The keyword acts as a multiplier on any values MULTX- (see 12.2.16)
HMMULTY- cumulative transmissibility multipliers in Y-axis direction. The keyword

acts as a multiplier on any values MULTY- (see 12.2.18) that have been previously
specified;
HMMULTZ- cumulative transmissibility multipliers in Z-axis direction. The keyword

acts as a multiplier on any values MULTZ- (see 12.2.20) that have been previously
specified.
12.3.3).
Example
EQUALS
'HMMULTX-' 0.75 5 10 5 10 20 30 /
/
In this example for each cell in 5x5x10 box cumulative transmissibility multipliers for
MULTX- (see 12.2.16) are set to 0.75.
12.2.23. HMMULTX- / HMMULTY- / HMMULTZ- 489

12.2.24 PORO


Section
The keyword is used to define porosity for all grid blocks. The same number of values
as number of grid cells must be specified. This is function (x, y, z) in 2.5.
Default: none
Example
DIMENS
5 5 4
/
...
PORO
100*0.1784
/
In this example for all 100 grid blocks the same porosity = 0.1784 is specified.
Example
DIMENS
5 6 2
/
...
PORO
0.20 0.20 0.20 0.20 0.20 0.19 0.19 0.19 0.19 0.19
0.18 0.18 0.18 0.18 0.18 0.17 0.17 0.17 0.17 0.17
0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17
0.20 0.20 0.20 0.20 0.20 0.19 0.19 0.19 0.19 0.19
0.18 0.18 0.18 0.18 0.18 0.17 0.17 0.17 0.17 0.17
0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17
/
This example defines porosity values for a 5x6x2 grid.
12.2.24. PORO 490

12.2.25 NTG


Section
This keyword defines net to gross values of grid blocks. The same number of values as
number of cells must be specified. This is function (x, y, z) in 2.5.
Default: 1 in all grid blocks
Example
DIMENS
5 5 4
/
...
NTG
100*0.2784
/
This example defines equal net to gross values = 0.2784 for all 100 blocks of the grid.
Example
DIMENS
5 4 2
/
...
NTG
0.60 0.60 0.60 0.60 0.60 0.62 0.62 0.62 0.62 0.62
0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62
0.60 0.60 0.60 0.60 0.60 0.62 0.62 0.62 0.62 0.62
0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62
/
This example defines net to gross values distribution for a 5x4x2 grid.
12.2.25. NTG 491

12.2.26 DZNET


Section
This keyword defines net thickness of grid blocks (METRIC: m, FIELD: f t ). The same
number of values as number of cells must be specified. If DZNET is specified, net to gross
ratio (function (x, y, z) in 2.5) will be calculated as follows:
DZNET
NTG =
DZ
Default: DZ (METRIC: m, FIELD: f t ) in all grid blocks.
Example
DIMENS
5 5 4
/
...
DZ
100*5
/
DZNET
100*2.5
/
This example defines equal net thickness values = 2.5 for all 100 blocks of the grid. Net
to gross ratio will be calculated as 2.5
5 = 0.5 for all blocks.
Example
DIMENS
5 4 2
/
...
DZNET
3.60 3.60 3.60 3.60 3.60 0.62 0.62 0.62 0.62 0.62
0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62
3.60 3.60 3.60 3.60 3.60 0.62 0.62 0.62 0.62 0.62
0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62
/
This example defines net thickness distribution for a 5x4x2 grid.
12.2.26. DZNET 492

12.2.27 PORV

RUNSPEC GRID x EDIT PROPS

Section
This keyword defines pore volumes of grid blocks (METRIC: rm3 , FIELD: rb). The
same number of values as number of cells must be specified. If PORV is specified, net block
pore volumes will be recalculated.
Default: Calculated from grid block dimensions, PORO (see 12.2.24) and NTG (see
12.2.25).
Example
DIMENS
5 5 4
/
...
PORV
100*5000
/
This example defines block pore volume values = 5000 for all 100 blocks of the grid.
Example
DIMENS
5 4 2
/
...
PORV
3.60 3.60 3.60 3.60 3.60 0.62 0.62 0.62 0.62 0.62
0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62
3.60 3.60 3.60 3.60 3.60 0.62 0.62 0.62 0.62 0.62
0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62
/
This example defines pore volumes distribution for a 5x4x2 grid.
Below pore volumes are defined for only part of the grid, using keyword ARITHMETIC
(see 12.3.2).
12.2.27. PORV 493

Example
ARITHMETIC
PORV(1:5, 2:3, 7:7) = PORV/10
PORV(1:5, 2:3, 8:8) = 0
/
Here pore volumes of 10 grid blocks from 7th depth layer are divided by ten, and 10
blocks from next layer are deactivated by setting zero pore volume.
12.2.27. PORV 494

12.2.28 MULTPV


Section
This keyword defines multipliers for pore volumes of grid blocks, calculated by simulator
from grid block dimensions, PORO (see 12.2.24) and NTG (see 12.2.25).
The same number of values as number of cells must be specified. MULTPV keyword will
have no effect on grid block pore volume if PORV (see 12.2.27) is specified for the same
grid block. Otherwise net block pore volume will be recalculated on the basis of MULTPV.
The keyword can be used in SCHEDULE section.

Material is still conserved, thats why modification of the pore volume leades to the pressure
change. MULTPV in SCHEDULE section is cumulative: each MULTPV keyword provides
multiplication of the current pore volumes.
Default: 1.
Example
DIMENS
5 5 3
/
...
MULTPV
200 200 200 200 200
200 1 1 1 200
200 1 1 1 200
200 1 1 1 200
200 200 200 200 200
200 200 200 200 200
200 1 1 1 200
200 1 1 1 200
200 1 1 1 200
200 200 200 200 200
200 200 200 200 200
200 1 1 1 200
200 1 1 1 200
200 1 1 1 200
200 200 200 200 200
12.2.28. MULTPV 495

This example defines block pore volume multipliers equal to 200 on reservoir sides and
unit in the rest of the reservoir.
Below the same distribution is set, using keyword ARITHMETIC (see 12.3.2).
Example
ARITHMETIC
MULTPV = 1
MULTPV(1:5, 1:1, 1:3) = 200
MULTPV(1:5, 5:5, 1:3) = 200
MULTPV(1:1, 1:5, 1:3) = 200
MULTPV(5:5, 1:5, 1:3) = 200
/
12.2.28. MULTPV 496

12.2.29 ACTNUM


Section
This keyword specifies active/inactive cells. The number of values should be equal to
number of cells. Values should be integer numbers:
1. For E100 models:
values indicates as additional pore volume multiplier (in particular, 0 cell is
inactive, 1 cell is active, 2 pore volume is doubled and so on);
2. For E300 models:
0 cell is inactive;
1 cell is active;
2 the grid block has rock volume only;
3 the grid block has pore volume only;
Default: 1 for all cells.
Example
DIMENS
5 5 4
/
...
ACTNUM
100*1
/
In this example all cells are active cells.
Example
DIMENS
5 4 1
/
...
ACTNUM
1 1 1 1 1
1 0 0 0 1
1 0 0 0 1
1 1 1 1 1
/
12.2.29. ACTNUM 497

In this example cell [1, 1, 1] is active, but cell [2, 2, 1] is inactive
12.2.29. ACTNUM 498

12.2.30 MINPV


Section
This keyword is used to switch grid blocks into inactive state if its pore volume (METRIC:
rm3 , FIELD: rb) is smaller than specified in this keyword.
Default: 0.000001
Example
MINPV
1200
/
In this example all grid blocks with pore volume less than 1200 rm3 are switch into
inactive state.
12.2.30. MINPV 499

12.2.31 MINPORV


Section
This keyword is an alias for the keyword MINPV (see 12.2.30).
12.2.31. MINPORV 500

12.2.32 MINPVV


Section
This keyword is used to switch grid blocks into inactive state if its pore volume (METRIC:
rm3 , FIELD: rb) is smaller than specified in this keyword. The number of values should be
equal to number of cells.
Default: 0.000001
Example
MINPVV
40*1000 40*1800 30*900 10*1200
/
This example sets different minimal pore volumes for grid blocks (1000, 1800, 900, 1200
rm3 ).
If block pore volume is less that specified number, it will switch into inactive state.
12.2.32. MINPVV 501

12.2.33 MINDZNET


Section
This keyword is used to switch grid blocks into inactive state if its net thickness (DZ (see
12.2.2)) is smaller than specified in this keyword (METRIC: m, FIELD: f t ).
Default: 0.000001
Example
MINDZNET
0.2
/
In this example all grid blocks with net thickness less than 0.2 m are switch into inactive
state.
12.2.33. MINDZNET 502

12.2.34 MINROCKV


Section
The keyword could be used only in thermal run (THERMAL (see 12.1.50)). The keyword
specifies minimum rock volume for active block (METRIC: rm3 , FIELD: rb). The number
of values should be equal to number of blocks. The data should be terminated with a slash
/.
Blocks with a smaller rock volume than the volume specified via this keyword are defined
as having zero rock volume. Blocks with zero rock and pore volume are inactive.
Default: 0.000001
Example
MINROCKV
0.003 /
12.2.34. MINROCKV 503

12.2.35 MINRV


Section
This keyword is analogue of the keyword MINROCKV (see 12.2.34).
12.2.35. MINRV 504

12.2.36 PERMAVE


Section
The keyword sets value of parameter p in formula for calculation permeability averages
for transmissibility:
!1
Wi PERMXip +W j PERMX jp p
PERMXav = .
Wi +W j
Fromulas for transmissibility calculations are in the section 5.5.1.

1. value of p for calculation permeability averages X -direction;
2. value of p for calculation permeability averages Y -direction;
3. value of p for calculation permeability averages Z -direction.
Parameter p should be non-negative or be equal to -1. If another value will be specified,

then p = 1.
Default:
p = 1 for each direction.
Example
PERMAVE 0.0 1.0 -1.0 /
In the example values of parameter p in X -, Y - and Z -directions which are equal to 0,

1, -1 correspondingly.
12.2.36. PERMAVE 505

12.2.37 FAULTS


Section
A table is specified which defines a set of faults. Fault transmissibility can later be
modified using MULTFLT (see 12.2.38) keyword. Each fault is assigned a name; it can
consist of several segments, in this case for all segments this name should be specified.
Number of segments for each fault and order of their appearance in fault table are arbitrary.
The following data should be specified:
fault name,
lower i-coordinate of fault segment,
upper i-coordinate of fault segment; should be equal to lower i-coordinate if fault face
is I or X,
lower j -coordinate of fault segment,
upper j -coordinate of fault segment; should be equal to lower j -coordinate if fault
face is J or Y,
lower k -coordinate of fault segment,
upper k -coordinate of fault segment; should be equal to lower k -coordinate if fault
face is K or Z,
fault face, should be equal to one of the following letters: I, J, K, X, Y, Z.
The table must be terminated with a blank record, containing only a slash (/).
Note: The FAULTS keyword may be used more than once.
Note: The faults defined by means of FAULTS keyword are easy way to modify trans-
missibility in a group of cells with help of keyword MULTFLT (see 12.2.38). They dont
have to coincide with actual faults in the corner-point geometry (see keywords ZCORN and
COORD).
Example
FAULTS
NAME i1 i2 j1 j2 k1 k2 FACE
'fault_1' 8 8 9 20 1 3 'I'/
'fault_2' 8 12 9 9 1 3 'J'/
'fault_2' 8 12 9 20 1 1 'K'/
'fault_1' 8 8 21 21 2 2 'J'/
/
12.2.37. FAULTS 506

This example defines two two-segment faults.
12.2.37. FAULTS 507

12.2.38 MULTFLT


Section
The keyword defines transmissibility multipliers for all cells in specified faults, in direc-
tion corresponding to face of fault, previously defined in FAULTS (see 12.2.37) keyword.
1. fault name (as specified in the FAULTS keyword);
2. transmissibility multiplier;
3. diffusivity multiplier, IGNORED (this is an Eclipse compatibility field).
The table must be terminated with a blank record, containing only a slash (/).
Default:
transmissibility multiplier: 1.0
diffusivity multiplier: 1.0
Note 1: If for the same fault MULTFLT keyword is specified more than once in GRID
section, then the last multiplier will be taken. If for the same fault MULTFLT keyword is
specified more than once in SCHEDULE section, then multipliers will be multiplied (cumu-
lative behaviour).
Note 2: If both MULTFLT and MULTX (see 12.2.15) or MULTY (see 12.2.17) or MULTZ
(see 12.2.19) are used for the same cell face, the effect will be cumulative.
Example
FAULTS
'fault_1' 8 8 9 20 1 3 'I'/
/
MULTFLT
NAME MULT TX MULT D
'fault_1' 0 /
/
In this example one fault is defined, transmissibility is set to 0.
12.2.38. MULTFLT 508

Example
FAULTS
'fault_1' 8 8 9 20 1 3 'I'/
'fault_2' 8 12 9 9 1 3 'J'/
'fault_2' 8 12 9 20 1 1 'K'/
'fault_1' 8 8 21 21 2 2 'J'/
/
MULTFLT
NAME MULT TX MULT D
'fault_1' 0.1 /
'fault_1' 0.2 /
'fault_2' 0.3 /
/
MULTFLT
'fault_2' 0.4 /
/
MULTX
1875*10
/
In this example two two-segment faults are defined, for fault 1 transmissibility multiplier
will be 0.2, for fault 2 0.4 (only the value defined last is used each time). Then MULTX (see
12.2.15) keyword is applied, finally for fault 1, segment oriented in i direction (defined first)
transmissibility will be 2. For segment oriented in j direction transmissibility will be 0.2.
For fault 2 transmissibility will rest equal to 0.4 (since MULTY and MULTZ are not defined,
they are defaulted to 1).
12.2.38. MULTFLT 509

12.2.39 THPRESFT


Section
The keyword is used to set threshold pressure value for flow through fault. If pressure
difference between communicating cells from different fault sides is less than threshold
value, there will be no flow between those cells. Otherwise flow between those cells will
be calculated basing on pressure difference reduced by threshold value. By default, threshold
value is equal to 0.
See also keyword THPRES (see 12.15.7).
Keyword is followed by a 2-column table, each line should end with slash (/). Last table
line should contain only slash symbol (/).
1. fault name;
2. threshold pressure value for flow through this fault (METRIC: barsa, FIELD: psia).
Default: threshold pressure value = 0.
Note:
If threshold pressure value for a fault is indicated several times, last value will be used.
If flow between two grid blocks is governed by THPRES and THPRESFT simultane-
ously, maximum threshold value will be used.
Example
THPRESFT
'fault_1' 10.0 /
'fault_2' 5.0 /
'fault_3' 15.0 /
/
In this example different threshold pressure values are defined for faults fault_1, fault_2,
fault_3.
12.2.39. THPRESFT 510

12.2.40 USEFLUX


Section
This keyword is used in tNavigator for splitting. The keyword should be followed by
.flux-file name, which contains boundary conditions for splitted part of the model.
.flux-file and this keyword are generated automatically when you split the model.
Splitting is described in section 5.14 (in tNavigator approach to splitting is different from
Eclipse).
.flux-files in tNavigator are generated always in two cases:
during calculation of .patterns-file (common file which contains information abolut all
splitted parts);
during model calculation via console version of tNavigator with option --split (if the
keyword FIPPATT (see 12.4.13) is specified in the model).
.flux-file contains boundary conditions for splitted parts of the model (flow across the
boundary).
Example
USEFLUX
'DEMO_SIMPLE_002_2'
This keyword defines that file DEMO_SIMPLE_002_2.flux with boundary conditions is

used.
12.2.40. USEFLUX 511

12.2.41 DUMPFLUX


Section
This keyword is ignored by tNavigator for splitting because in tNavigator approach to

splitting is different from Eclipse. Splitting is described in section 5.14.
.flux-files in tNavigator are generated always in two cases:
during calculation of .patterns-file (common file which contains information abolut all
splitted parts);
during model calculation via console version of tNavigator with option --split (if the
keyword FIPPATT (see 12.4.13) is specified in the model).
.flux-file contains boundary conditions for splitted parts of the model (flow across the
boundary).
The keyword FIPPATT (see 12.4.13) for every grid block specifies the splitted region to
which it belongs.
12.2.41. DUMPFLUX 512

12.2.42 FLUXREG / FLUXTYPE


Section

splitting and boundary conditions is different from Eclipse.
Splitting is described in section 5.14.
12.2.42. FLUXREG / FLUXTYPE 513

12.2.43 DOMAINS


Section
The keywords sets parameters for parallel run for simulator Eclipse.
12.2.43. DOMAINS 514

12.2.44 SOLVDIRS


Section
This keyword overrides the solver principal directions for Eclipse.

12.2.44. SOLVDIRS 515

12.2.45 RESVNUM


Section
The keyword begins COORD (see 12.2.8) data input for every reservoir. One should
enter the number of reservoir for which data will be entered using the keyword COORD (see
12.2.8). The second and following reservoirs should be set by cell box (keyword BOX (see
12.3.3)). The data should be terminated with a slash /.
The number of reservoir should be greater or equal to 1 and less or equal to NUMRES (see
12.1.69). NUMRES (see 12.1.69) should be specified and greater than 1.
Example
RESVNUM
1/
COORD
0 0 1 0 0 2
0 1 1 0 1 2
1 0 1 1 0 2
1 1 1 1 1 2
2 0 1 2 0 2
2 1 1 2 1 2
/
RESVNUM
2/
BOX
1 3 1 2 1 1
/
COORD
1 0 1 3 0 2
2 1 1 4 1 2
1 0 1 1 0 2
1 1 1 1 1 2
3 0 1 2 0 2
2 1 1 2 1 2
/
12.2.45. RESVNUM 516

12.2.46 COORDSYS


Section
The keyword provides information about coordinate system for every reservoir. Layers of
blocks can be put to several reservoirs at the same time.
The keyword should be specified only if the is more than one reservoir. The keyword
should be followed by the NUMRES (see 12.1.69) sets of data (equal to the amount of
reservoirs). Each set of data should be terminated with a slash /.
The following parameters are to be specified for every set of data:
1. minimal block index number in Z-direction for this reservoir (this number shouldnt be
greater than NZ in DIMENS (see 12.1.25));
2. maximal block index number in Z-direction for this reservoir (this number shouldnt
be greater than NZ in DIMENS (see 12.1.25));
3. completion of circle for this reservoir (COMP - circle is completed in Y-direction,

INCOMP - circle is not completed. The circle can be completed if coincident coordinate
lines are identified);
4. connection to the reservoir below (JOIN - transmissibilities to the reservoir below are
calculated, SEPARATE - this reservoir is separated with the reservoir below. In JOIN
case transmissibilities between blocks (i, j, k) and (i, j, k + 1) are calculated (if these
blocks belong to different reservoirs). Fault non-neighbor connections are not calculated
between different reservoirs);
5. lower bound for reservoir number for lateral block connection between reservoirs;
6. upper bound for reservoir number for lateral block connection between reservoirs.
Lower and upper bound may be used to allow fault NNC between cells in different
reservoirs. These numbers should lie between 1 and NUMRES (see 12.1.69).
Default:
completion of circle for this reservoir INCOMP,
connection to the reservoir below SEPARATE,
lower bound for reservoir number current reservoir number,
upper bound for reservoir number current reservoir number.
12.2.46. COORDSYS 517

Example
NUMRES
4
/
COORDSYS
1 4 'INCOMP' ' SEPARATE' 1 1
/
/
/
/
12.2.46. COORDSYS 518

12.2.47 GDFILE


Section
This keyword allows to define model grid by means of file of special format (*.GRID
format of Eclipse simulator). The grid defined in this file is a set of cubes, with coordi-
nates of all 8 vertexes given, a more flexible way than COORD (see 12.2.8), ZCORN (see
12.2.9) allows. Only UNFORMATTED file format is supported. The following data should
be specified (list terminated by a slash /).
file name (file should be of UNFORMATTED format), with grid geometry
file format; possible values are: FORMATTED, F, UNFORMATTED, U; if FORMATTED,

or F, is indicated, grid will NOT be read from file indicated in previous argument.
Default: file format: UNFORMATTED.
Example
GDFILE
filegrid.GRID UNFORMATTED
/
In this example grid will be taken from filegrid.GRID.
12.2.47. GDFILE 519

12.2.48 NNC


Section
Usually non-neighbor connections are created due to faults, but they can be set explicitly
using this keyword. For each non-neighbor connection one line of data is input, with coordi-
nates of cells to be connected and transmissibility between them. Each line should end with
slash (/). Data table should end with slash, input on the new line.
1. I -coordinate of first cell from non-neighbour connection;
2. J -coordinate of this cell;
3. K -coordinate of this cell;
4. I -coordinate of second cell from non-neighbour connection;
7. non-neighbor connection transmissibility (METRIC: cP rm3 /day/bar , FIELD: cP

rb/day/psi).
Default: non-neighbor connection transmissibility: 0;

Note: In non-neighbor connection is set between cells with nonzero transmissibility, this
increases transmissibility between them on this value.
Note: Any non-neighbor connections with transmissibility less than 0.000001 are ignored.
Example
NNC
1 2 2 1 5 2 100 /
1 1 2 1 4 2 100 /
12 18 20 14 44 20 200 /
16 19 31 14 44 31 200 /
/
In this example non-neighbor connections between two pairs of grid blocks are set, with
transmissibility 100 and two pairs of grid blocks are set, with transmissibility 200.
12.2.48. NNC 520

12.2.49 EDITNNC


Section
Using this keyword one can modify non-neighbor connections generated by faults in the
grid. For any non-neighbor connection (you want to modify) you should specify a line of data
with following parameters. A line should be terminated by a /. A single / should terminate
lines of data.
These parameters are to be specified:
1. I -coordinate of first cell from non-neighbour connection;
4. I -coordinate of second cell from non-neighbour connection;
7. T RANM - transmissibility multiplier of this non-neighbor connection; it should be

greater or equal to zero; transmissibility is equal to the product of T RANM and non-
neighbor connection transmissibility. The last one is calculated by the program or
specified by the keyword NNC (see 12.2.48);
8. number of saturation region, corresponding to the flow from the first cell to the second
cell;
9. number of saturation region, corresponding to the flow from the second cell to the first
cell;
10. number of PVT region, corresponding to the flow from the first cell to the second cell;
11. number of PVT region, corresponding to the flow from the second cell to the first cell;
12. direction, corresponding to the flow from the first cell to the second cell; choose one
from this list: X+, X,Y +,Y , Z+, Z;
13. direction, corresponding to the flow from the second cell to the first cell; choose one
from this list: X+, X,Y +,Y , Z+, Z;
12.2.49. EDITNNC 521

14. diffusivity multiplier of this non-neighbor connection (it should be greater or equal
to zero); the diffusivity is equal to the product of the diffusivity multiplier and non-
neighbor connection diffusivity.
Default:
T RANM : 1.0;
number of saturation region, corresponding to the flow from the first cell to the second
cell (or from the second cell to the first cell): 0;
number of PVT region, corresponding to the flow from the first cell to the second cell
(or from the second cell to the first cell): 0
diffusivity multiplier: 0.
Example
EDITNNC
15 3 1 18 13 1 5 3 1 0 0 Y+ Y- 2.5/
5 28 1 9 33 2 3 1 4 2 1 X+ X- 1.3/
/
This example modifies two non-neighbor connections. The transmissibility multiplier of

the first non-neighbor connection is set to 5 and directions, corresponding to the flow between
cells: Y + Y ; the transmissibility multiplier of the second non-neighbor connection is set
to 3 and directions, corresponding to the flow between cells: X+ X.
12.2.49. EDITNNC 522

12.2.50 NNCGEN


Section
The keyword can be used to specify transmissibility between any two cells in any two
grids.
The keyword can contain any number fo data lines, each terminated with a slash /. All
data should be terminaated with a final slash /.

1. grid of the first cell;
2. I -coordinate of the first cell joined to non-neighbor connection;
5. grid of the second cell;
6. I -coordinate of the second cell joined to non-neighbor connection;
9. non-neighbor connection transmissibility (METRIC: cP rm3 /day/bar , FIELD: cP
rb/day/psi).
Default:
grid of the first cell GLOBAL;
grid of the second cell GLOBAL;
non-neighbor connection transmissibility 0 cp rm3 /day/bar .
Example
NNCGEN
'LGR2' 1 1 1 'GLOBAL' 27 4 1 3.2/
'LGR3' 3 4 7 'LGR4' 3 4 16 2.3/
'GLOBAL' 1 1 1 'LGR3' 5 3 8 3.4/
/
12.2.50. NNCGEN 523

In this example there are 3 non-neighbor connections.
12.2.50. NNCGEN 524

12.2.51 TRANX


Section
This keyword is used to specify transmissibility in X-direction for plane between blocks
[I, J, K] and [I + 1, J, K] (METRIC: cP rm3 /day/bar , FIELD: cP rb/day/psi).
This value replaces value calculated by the program. The keyword should be followed by
one non-negative real number for every grid block.
Example
DIMENS
5 5 4
/
...
TRANX
100*1.5
/
In this example transmissibility is specified for all planes in X-direction as 1.5.
12.2.51. TRANX 525

12.2.52 TRANY


Section
This keyword is used to specify transmissibility in Y-direction for plane between blocks
[I, J, K] and [I, J + 1, K] (METRIC: cP rm3 /day/bar , FIELD: cP rb/day/psi).
Example
DIMENS
5 5 4
/
...
TRANY
100*1.5
/
In this example transmissibility is specified for all planes in Y-direction as 1.5.
12.2.52. TRANY 526

12.2.53 TRANZ


Section
This keyword is used to specify transmissibility in Z-direction for plane between blocks
[I, J, K] and [I, J, K + 1] (METRIC: cP rm3 /day/bar , FIELD: cP rb/day/psi).
Example
DIMENS
5 5 4
/
...
TRANZ
100*1.5
/
In this example transmissibility is specified for all planes in Z-direction as 1.5.
12.2.53. TRANZ 527

12.2.54 PINCH


Section
This keyword sets parameters regulating non-neighbor connections for pinched out layers.
If there is an inactive cell (or layer) in the grid, normally there will be no vertical flow
across it, between the active cells immediately above and below. If the keyword PINCH is
entered, non-neighbor connections will be automatically generated between the active cells
on either side of the pinched-out block or layer(s), allowing fluids to flow across it, if the
conditions of PINCH are fulfiled.
The following data should be provided, line ending with slash (/):
1. pinch-out threshold thickness: the vertical connection between active cells separated by
inactive cells is formed, if the vertical distance between them is below this value of
(METRIC: m, FIELD: f t );
2. control over non-neighbor connections across cells deactivated using MINPV (see
12.2.30) and MINPVV (see 12.2.32); possible values GAP and NOGAP; first one
means that non-neighbor connections across cells deactivated by MINPV are created
even if thickness exceeds threshold, and second one (NOGAP) that non-neighbor
connections are created always observing threshold thickness;
3. maximal empty gap allowed between cells in adjacent layers for non-zero transmissi-
bility to be allowed between them (METRIC: m , FIELD: ft ). If PINCH is not used,
its equivalent to default value of this parameter;
4. method of non-neighbor connection transmissibility calculation through pinched out

layers TOPBOT and ALL; first one means that it will be calculated on base of
half-block transmissibilities of active cells below and above pinched-out layer(s), and
second one as harmonic average of cell transmissibilities of pinched out layer(s)
between two active cells;
5. method of vertical transmissibility calculation MULTZ (see 12.2.19) across pinched

out cells, in case if previous parameter is set to TOPBOT; possible values TOP and
ALL, first one means that value of active cell above pinched out cells will be used,
second one minimum MULTZ (see 12.2.19) of this active cell and all nonactive cells
below will be used. Only the values of MULTZ (see 12.2.19) from GRID section are
used here.
In case if previous parameter is set to ALL, this parameter is ignored.
12.2.54. PINCH 528

Default:
1. threshold thickness of pinched out layers: 0.001 (m);
12.2.30) and MINPVV (see 12.2.32): GAP;
3. maximal empty gap allowed between cells in adjacent layers: 1E20;

layers: TOPBOT;

out cells: TOP;
Example
PINCH
0.02 'GAP'1* 'All'/
In this example threshold thickness is set to 0.02, and non-neighbor connections through
cells deactivated using MINPV (see 12.2.30) and MINPVV (see 12.2.32) are set even if
thickness exceeds threshold value.
12.2.54. PINCH 529

12.2.55 PINCHOUT


Section
Analog of PINCH (see 12.2.54), but has no parameters. Equivalent to setting

PINCH
/
For more detailed control over non-neighbor connections across pinched out cells see
PINCH (see 12.2.54).
Example
PINCHOUT
In this example non-neighbor connections through pinched out layers will be created, if
threshold thickness is not exceeded (for blocks deactivated by MINPV (see 12.2.30) and
MINPVV (see 12.2.32) threshold thickness will not be used).
12.2.55. PINCHOUT 530

12.2.56 PINCHREG


Section
This keyword sets parameters regulating non-neighbor connections for pinched out layers
for regions identified by PINCHNUM (see 12.2.57). If PINCHNUM is absent, then PINCHREG
will use the regions FLUXNUM (see 12.4.18).
The following data should be provided, one line ending with slash (/) for each pinchout
region (data is the same as in PINCH (see 12.2.54)). If the whole line is defaulted, no
pinchouts will be generated for this region.
The number of data line should be equal the number of pinchout regions (PINCHNUM
(see 12.2.57)), specified via the 3-rd parameter of the keyword GRIDOPTS (see 12.1.87).
If the 3-rd parameter of GRIDOPTS (see 12.1.87) is defaulted (0), then the number of re-
gions should be specified via the 4-th parameter of REGDIMS (see 12.1.29). In this case the
pinchout regions will be used according to the keyword FLUXNUM (see 12.4.18).
One data line for one pinchout region contains the following parameters:
1. threshold thickness of pinched out layers (METRIC: m, FIELD: f t );
12.2.30) and MINPVV (see 12.2.32); possible values GAP and NOGAP; first one
means that non-neighbor connections across cells deactivated by MINPV are created
even if thickness exceeds threshold, and second one (NOGAP) that non-neighbor
connections are created always observing threshold thickness;
3. maximal empty gap allowed between cells in adjacent layers for non-zero transmissi-
bility to be allowed between them (METRIC: m, FIELD: f t );

layers TOPBOT and ALL; first one means that it will be calculated on base of
half-block transmissibilities of active cells below and above pinched-out layer(s), and
second one as harmonic average of cell transmissibilities of pinched out layer(s)
between two active cells;

out cells, in case if previous parameter is set to TOPBOT; possible values TOP and
ALL, first one means that value of active cell above pinched out cells will be used,
second one minimum MULTZ (see 12.2.19) of this active cell and all nonactive cells
12.2.56. PINCHREG 531

below will be used. Only the values of MULTZ (see 12.2.19) from GRID section are
used here.
In case if previous parameter is set to ALL, this parameter is ignored.
Default:
1. threshold thickness of pinched out layers: 0.001;
12.2.30) and MINPVV (see 12.2.32): GAP;
3. maximal empty gap allowed between cells in adjacent layers: 1E20;

layers: TOPBOT;

out cells: TOP.
Example
PINCHREG
0.02 'GAP'/
/
0.01 'GAP'/
/
In this example threshold thickness is set to 0.02 in first region, and 0.01 in third one.
Non-neighbor connections through cells deactivated using MINPV (see 12.2.30) and MINPVV
(see 12.2.32) are set even if thickness exceeds threshold value. No non-neighbor connections
will be generated in the second region.
12.2.56. PINCHREG 532

12.2.57 PINCHNUM


Section
This keyword is used to specify pinchout regions for non-neighborhood connections

generation through PINCHREG (see 12.2.56).
To use this keyword, one should specify a maximum number of pinchout regions in 3-rd
parameter of the keyword GRIDOPTS (see 12.1.87).
The number of values should be equal to number of cells. Values should be integer num-
bers. The data should be terminated with a slash /.
Example
DIMENS
5 5 4
/
...
PINCHNUM
50*1 50*2
/
In this example upper half of reservoir belongs to first pinchout region, and lower half of
reservoir belongs to second one.
12.2.57. PINCHNUM 533

12.2.58 JFUNC


Section
If end-point scaling is selected by ENDSCALE (see 12.6.24), JFUNC keyword may be

specified. In this case capillary pressures will be calculated according to Leverett J-Function
option.
This keyword defines parameters for whole reservoir. The keyword JFUNCR (see 12.2.59)
can be used to specify data separetely for each saturation region.
The following parameters should be entered (The data should be terminated with a slash
/.):
1. phase flag:
WATER (water-oil capillary pressure will be scaled according to J-function),

GAS (gas-oil capillary pressure will be scaled according to J-function),
BOTH (water-oil and gas-oil capillary pressure will be scaled according to J-
function),
NONE (water-oil and gas-oil capillary pressures (entered in saturation function
tables) should be used without Leverett J-function scaling). In this case parameters
2-6 of this keyword should not be specified. They are ignored by tNavigator.
2. oil-water surface tension, this is STW in 2.96, in dynes/cm; if phase flag is equal to
WATER, or BOTH, this parameter should be specified;
3. oil-gas surface tension, this is STG in 2.96, in dynes/cm; if phase flag is equal to GAS,
or BOTH, this parameter should be specified;
4. power for porosity, this is in 2.96;
5. power for permeability, this is in 2.96;
6. permeability direction: this can be XY (the average of PERMX (see 12.2.13) and
PERMY (see 12.2.13) values), X (PERMX (see 12.2.13) value), Y (PERMY (see
12.2.13) value) or Z (PERMZ (see 12.2.13) value).
Instead of this parameter one can specify the special permeability value used for J-
function computation (JFPERM (see 12.2.60)). If this keyword is specified then perme-
ability direction (the 6-th parameter of JFUNC (see 12.2.58) is ignored).
Default:
12.2.58. JFUNC 534

phase flag BOTH:
power for porosity = 0.5;
power for permeability = 0.5;
permeability direction = XY.
Example
JFUNC
WATER 22.2 /
In this example only oil-water capillary pressure will be scaled, with surface tension equal
to 22.2 dynes/cm.
Example
JFUNC
GAS 1* 12.2 /
In this example only oil-gas capillary pressure will be scaled, with surface tension equal
to 12.2 dynes/cm.
Example
JFUNC
BOTH 22.2 12.2/
In this example both oil-water and oil-gas capillary pressures will be scaled, with surface
tension equal to 22.2 dynes/cm and 12.2 dynes/cm.
12.2.58. JFUNC 535

12.2.59 JFUNCR


Section
If end-point scaling is selected by ENDSCALE (see 12.6.24), JFUNCR keyword may be

specified. In this case capillary pressures will be calculated according to Leverett J-Function
option.
This keyword defines parameters separetely for each saturation region. The keyword JFUNC
(see 12.2.58) can be used to specify data for whole reservoir.
The number of data lines should be equal to the number of saturation regions (1-st pa-
rameter of the keyword TABDIMS (see 12.1.26)). Data for each region should be terminated
with a slash /.
One row contains the following parameters:
1. phase flag:
WATER (water-oil capillary pressure will be scaled according to J-function),

GAS (gas-oil capillary pressure will be scaled according to J-function),
BOTH (water-oil and gas-oil capillary pressure will be scaled according to J-
function),
2. oil-water surface tension, this is STW in 2.96, in dynes/cm; if phase flag is equal to
WATER, or BOTH, this parameter should be specified;
3. oil-gas surface tension, this is STG in 2.96, in dynes/cm; if phase flag is equal to GAS,
or BOTH, this parameter should be specified;
4. power for porosity, this is in 2.96;
5. power for permeability, this is in 2.96;
6. permeability direction: this can be XY (the average of PERMX (see 12.2.13) and
PERMY (see 12.2.13) values), X (PERMX (see 12.2.13) value), Y (PERMY (see
12.2.13) value) or Z (PERMZ (see 12.2.13) value).
Instead of this parameter one can specify the special permeability value used for J-
function computation (JFPERM (see 12.2.60)). If this keyword is specified then perme-
ability direction (the 6-th parameter of JFUNC (see 12.2.58) is ignored).
Default:
12.2.59. JFUNCR 536

phase flag BOTH:
power for porosity = 0.5;
power for permeability = 0.5;
permeability direction = XY.
Example
JFUNCR
WATER 22.2 /
GAS 1* 12.2 /
BOTH 22.2 12.2 /
12.2.59. JFUNCR 537

12.2.60 JFPERM


Section
This keyword sets the special permeability value (mD) used for J-function computation
JFUNC (see 12.2.58). the keyword can be used for E100 and E300 format models.
The number of specified values should be equal to the number of grid blocks. The data
If this keyword is specified for the grid block then permeability direction (the 6-th
parameter of JFUNC (see 12.2.58) (JFUNCR (see 12.2.59)) is ignored).
Example
JFPERM
600*4.5/
12.2.60. JFPERM 538

12.2.61 GRIDUNIT


Section
The keyword is used to specify length units for grid data and indicates if the coordinate
transformation via MAPAXES (see 12.2.62) will be used or not. The data should be termi-
The following parameters should be entered:
1. length units for grid data:
METRES,
FEET,
CM.
2. flag: MAP or not specified. MAP indicates that coordinate transformation is not required
(grid data is specified in global coordinate system). If flag is not specified - there will
be grid data transformation from local coordinate system to global coordinate system
via MAPAXES (see 12.2.62).
Example
GRIDUNIT
FEET /
In this example length units for grid data - feet. The second parameter (flag) is not
specified so the coordinate transformation from local coordinate system to global coordinate
system via MAPAXES (see 12.2.62) will be used.
12.2.61. GRIDUNIT 539

12.2.62 MAPAXES


Section
To transform grid coordinates to coordinate system associated with the map, MAPAXES
may be specified. Usually it is output by grid pre-processors. It is six numbers to be specified:
X coordinate of one point of the grid Y-axis relative to the map (X1),
Y coordinate of one point of the grid Y-axis relative to the map (Y1),
X coordinate of the grid origin relative to the map (X0),
Y coordinate of the grid origin relative to the map (Y0),
X coordinate of one point of the grid X-axis relative to the map (X2),
Y coordinate of one point of the grid X-axis relative to the map (Y2).
Note that the length of vectors (X1, Y1), (X0, Y0) and (X2, Y2), (X0, Y0) should be
equal.
Default: nothing
Example
MAPAXES
-1 1 0 0 1 1
/
In this example the grid is rotated at 45 degrees.
12.2.62. MAPAXES 540

12.2.63 MAPUNITS


Section
The keyword is used to specify MAPAXES data units. Following units are possible:
METRES,
FEET,
CM.
Default: METRES
Example
MAPUNITS
FEET
/
In this example MAPAXES data units are feets.
12.2.63. MAPUNITS 541

12.2.64 LX / LY / LZ


Section
This keyword can be specified in dual porosity run (2.28) if the option viscous displace-
ment is enable (VISCD (see 12.1.82)). The keyword sets the distances between fractures
(matrix block sizes) in X, Y and Z directions.
Values are enumerated in X-direction, then Y-direction, then Z-direction. The data
One should enter NX * NY * (NZ/2) values. The data should be terminated with a slash /.
Default: none. The data will not be used in the calculation of sigma-factor if the keyword
LTOSIGMA (see 12.2.69) is enable.
Example
DUALPORO
VISCD
...
DIMENS
10 10 2
...
LX
100*80
/
LY
50*150 50*180
/
LZ
100*70
/
This example shows the model NX = 10, NY = 10, NZ = 2. Dual porosity is specified
using the keyword DUALPORO (see 12.1.76), Viscous displacement is specified using the
keyword VISCD (see 12.1.82). The distances between fractures (matrix block sizes) in X-
direction is equal to 80 metres for all 100 blocks, in Y-direction for first 50 blocks 150
metres, for next 50 blocks 180 metres, in Z-direction for all blocks 70 metres.
12.2.64. LX / LY / LZ 542
12.2.65 DPNUM


Section
This keyword can be used in dual porosity single permeability run (2.28). The keyword
specifies reservoir fields that should be considered as single porosity fields.
One should enter NX * NY * (NZ/2) values. The data should be terminated with a slash /.
Dual porosity blocks should be marked by one 1, single porosity blocks by zero 0.
Default: If DPNUM isnt specified for the block, this block is considered as dual porosity
block.
One should specify grid data for single porosity blocks only in first half of layers in Z
direction (NZ/2) (matrix blocks). Fracture blocks (corresponding to single porosity matrix
blocks) are inactive.
The keyword will be ignored if DUALPORO (see 12.1.76) isnt specified. DUALPERM
(see 12.1.77) shouldnt be specified in the same time with DPNUM, since single porosity is
not allowed in dual permeability run.
Example
DUALPORO
...
DIMENS
10 10 2
...
DPNUM
10*0 10*1 10*0 10*1
10*0 10*1 10*0 10*1
10*0 10*1
/
This example shows the model NX = 10, NY = 10, NZ = 2. Dual porosity single perme-
ability is specified using the keyword DUALPORO (see 12.1.76), then single porosity field
is specified (the half of the reservoir).
12.2.65. DPNUM 543

12.2.66 DPGRID


Section
This keyword can be used in dual porosity single permeability run (2.28). If the keyword
is enable one should specify grid data only for matrix blocks (NX * NY * (NZ/2)); values
for fracture blocks will be obtained (copied) from corresponding matrix blocks.
This operation is applied for the values specified by following keywords: DX (see 12.2.2),
DY (see 12.2.2), DZ (see 12.2.2), PERMX (see 12.2.13), PERMY (see 12.2.13), PERMZ
(see 12.2.13), PORO (see 12.2.24), TOPS (see 12.2.6), NTG (see 12.2.25), DZNET (see
12.2.26), ZCORN (see 12.2.9), DEPTH (see 12.3.27). This operation is applied only for
fracture blocks which dont have manually input grid data.
Example
DPGRID
12.2.66. DPGRID 544

12.2.67 SIGMA


Section
This keyword can be used in dual porosity or dual permeability run (2.28), specified by
keywords DUALPORO (see 12.1.76), DUALPERM (see 12.1.77). The keyword sets sigma-
factor multiplier that is used in matrix-fracture coupling transmissibilities.
The keyword sets sigma-factor for all blocks. The data should be terminated with a slash
/.
and Z directions:
1 1 1
= 4( 2 + 2 + 2 ),
lx ly lz
Default. If no one of the keywords SIGMA, SIGMAV (see 12.2.68), LTOSIGMA (see
Different sigma-factors for different blocks can be specified using the keyword SIGMAV
(see 12.2.68).
Example
SIGMA
0.25 /
This example sets sigma-factor equal to 0.25.
12.2.67. SIGMA 545

12.2.68 SIGMAV


Section
This keyword can be used in dual porosity run (2.28), specified by keyword DUALPORO
(see 12.1.76). The keyword SIGMAV sets sigma-factor multiplier that is used in matrix-
fracture coupling transmissibilities.
One should enter NX * NY * (NZ/2) values. The data should be terminated with a slash
/.
and Z directions:
1 1 1
= 4( 2 + 2 + 2 ),
lx ly lz
Default. If no one of the keywords SIGMA (see 12.2.67), SIGMAV, LTOSIGMA (see
Common sigma-factor for all blocks can be specified using the keyword SIGMA (see
12.2.67).
Example
DUALPORO
...
DIMENS
10 10 2
...
SIGMAV
25*0.17 25*1 50*0.26
/
This example shows the model NX = 10, NY = 10, NZ = 2. Dual porosity is specified
using the keyword DUALPORO (see 12.1.76). First 25 matrix blocks have sigma-factor 0.17,
next 25 1, next 50 0.26.
12.2.68. SIGMAV 546

12.2.69 LTOSIGMA


Section
This keyword can be used in dual porosity run (2.28), if the option Viscous displacement
is enable (VISCD (see 12.1.82)). Using the keyword LTOSIGMA sigma-factor multiplier can
be obtained from the distances between fractures (matrix block sizes).
The data should be terminated with a slash /. The following parameters are to be speci-
fied:
1. f x ,
2. f y,
3. f z.

and Z directions:
fx fy fz
= 2 + 2 + 2,
lx ly lz
The values of lx , ly, lz that arent specified or are equal to zero will not be used in
calculations.
Default. If no one of the keywords SIGMA (see 12.2.67), SIGMAV (see 12.2.68),
LTOSIGMA is specified, sigma-factor will be considered as zero.
Sigma-factor can be specified manually using the keywords SIGMA (see 12.2.67), SIG-
MAV (see 12.2.68). If LTOSIGMA is enable, manually entered sigma-factor will be ignored.
Example
DUALPORO
...
LTOSIGMA
4 4 2
/
Dual porosity single permeability is specified using the keyword DUALPORO (see
12.1.76). f x is equal to 4, f y = 4, f z = 2.
12.2.69. LTOSIGMA 547

12.2.70 SIGMAGD


Section
This keyword sets the vertical size of a block of matrix material in dual porosity run
(2.28) with gravity imbibition option (2.28.2) (METRIC: m2 , FIELD: f t 2 ).
The keyword sets a sigma-factor for oil-gas system that is used in alternative matrix-
fracture coupling for matrix blocks in which the production mechanism is gravity drainage
due to the presence of gas in the fractures.
The keyword sets sigma-factor for all blocks. The data should be terminated with a slash
/.
Different values of sigma-factor for different blocks can be specified via SIGMAGDV (see
12.2.71).
SIGMAGD matrix-fracture transmissibility is used to calculate the oil flow when:
1. gravity imbibition option is used (2.28.2);
2. oil flows from the matrix to the fracture;
3. gravity drainage head associated with gas in the fracture is greater than the head
associated with water.
The area where the fractures are filled with gas, are created with transmissibiliry base on
SIGMAGD (see 12.2.70), areas filled with water, are created with transmissibiliry base on
SIGMA (see 12.2.67).
and Z directions:
1 1 1
= 4( 2 + 2 + 2 ),
lx ly lz
Default: If no one of the keywords SIGMAGD, SIGMAGDV (see 12.2.71), is specified,

sigma-factor will be taken from SIGMA (see 12.2.67), SIGMAV (see 12.2.68).
12.2.70. SIGMAGD 548

Example
SIGMAGD
0.018 /
This example sets sigma-factor equal to 0.018.
12.2.70. SIGMAGD 549

12.2.71 SIGMAGDV


Section
(2.28) with gravity imbibition option (2.28.2) (METRIC: m2 , FIELD: f t 2 ).
The keyword sets a sigma-factor for oil-gas system that is used in alternative matrix-
fracture coupling for matrix blocks in which the production mechanism is gravity drainage
due to the presence of gas in the fractures.
One value should be specified for each matrix block. So one should specify the number
of values equal to NZ/2 (3-rd parameter of DIMENS (see 12.1.25)). The data should be
One value of sigma-factor can be specified for all grid via the keyword SIGMAGD (see
12.2.70).
SIGMAGDV matrix-fracture transmissibility is used to calculate the oil flow when:
1. gravity imbibition option is used (2.28.2);
2. oil flows from the matrix to the fracture;
3. gravity drainage head associated with gas in the fracture is greater than the head
associated with water.
The area where the fractures are filled with gas, are created with transmissibiliry base on
SIGMAGD (see 12.2.70), areas filled with water, are created with transmissibiliry base on
SIGMA (see 12.2.67).
and Z directions:
1 1 1
= 4( 2 + 2 + 2 ),
lx ly lz
Default: If no one of the keywords SIGMAGD (see 12.2.70), SIGMAGDV (see 12.2.71),
is specified, sigma-factor will be taken from SIGMA (see 12.2.67), SIGMAV (see 12.2.68).
12.2.71. SIGMAGDV 550

Example
SIGMAGDV
10000*0.018 10000*0.02/
In this example for first 10000 blocks the value 0.018 is specified, for next 10000 blocks
0.02.
12.2.71. SIGMAGDV 551

12.2.72 THCONMF


Section
This keyword can be used in dual porosity run (2.28) with THERMAL (see 12.1.50)
option.
This keyword specifies the matrix to fracture thermal conductivity value for each matrix
block (METRIC: kJ/m/Day/K , FIELD: Btu/ f t/Day/F ).
One should enter NX * NY * (NZ/2) values. slashend.
Example
THCONMF
1000*2.5 100*2.8 /
12.2.72. THCONMF 552

12.2.73 MULTMF


Section
This keyword can be used in dual porosity run (2.28) DUALPORO (see 12.1.76). The
keyword specifies multiplier which is used to calculate the matrix-fracture flows.
The same number of values should be specified as the number of matrix blocks. The data
12.2.73. MULTMF 553

12.2.74 DZMTRX


Section
(2.28) with gravity imbibition option (2.28.2) (METRIC: m, FIELD: f t ).
This size is lz in the description of the keyword SIGMA (see 12.2.67).
Obe value should be specified for all grid.The data should be terminated with a slash /.To
set different values fot different blocks one should use the keyword DZMTRXV (see 12.2.76).
Default: 0.
Example
DZMTRX
0.2/
In this example for all grid the vertical size of a block of matrix material 0.2 metres.
12.2.74. DZMTRX 554

12.2.75 DZMATRIX


Section
This keyword is an analogue of DZMTRX (see 12.2.74).
12.2.75. DZMATRIX 555

12.2.76 DZMTRXV


Section
(2.28) with gravity imbibition option (2.28.2) (METRIC: m, FIELD: f t ).
This size is lz in the description of the keyword SIGMA (see 12.2.67).
One value should be specified for each matrix block. So one should specify the number
of values equal to NZ/2 (3-rd parameter of DIMENS (see 12.1.25)). The data should be
To set one value of the vertical size of a block of matrix material use the keyword
DZMTRX (see 12.2.74).
Default: 0.
Example
DZMTRXV
10000*0.2 10000*0.3/
For first 10000 blocks vertical size of a block of matrix material 0.2 meters, for next
10000 blocks 0.3 meters.
12.2.76. DZMTRXV 556

12.2.77 MULTREGT


Section
The keyword specifies transmissibility multiplier between (FLUXNUM (see 12.4.18)) or

MULTNUM (see 12.4.23) regions. If MULTNUM (see 12.4.23) isnt specified, then values of
MULTREGT will be applied to FLUXNUM (see 12.4.18).
The keyword can be used in dual porosity models 2.28.
The multipliers specified via this keyword are applied after accounting for values of
MULTX (see 12.2.15), MULTY (see 12.2.17), MULTZ (see 12.2.19), MULTFLT (see
12.2.38), MULTX- (see 12.2.16), MULTY- (see 12.2.18), MULTZ- (see 12.2.20). If the
region numbers specified via 1-st and 2-nd parameters of the keyword are equal and positive,
then the transmissibilities within that region in the specified directions are multiplied by the
given value and any transmissibilities connecting of any other regions - the same way.
If the keyword is defined in SCHEDULE section, then multipliers are accumulated (i.e.
ones set for previous dates are multiplied) even if keywords are set for the same dates. So it
works like MULTX,Y,Z.
The keyword contains arbitrary number of data lines terminated with a slash /. All data
should be terminated with a final slash /.
1. first region number;
2. last region number;
3. transmissibility multiplier for all transmissibilities connecting regions specified via 1-st
and 2-nd parameter;
4. directions in which the multiplier will be applied: X, Y, Z, XY, YZ, XZ, XYZ.
5. apply transmissibility multiplier to non-neighbor connections:
NNC apply the transmissibility multiplier only to non-neighbor connections

between regions, specified in 1-st and 2-nd parameter;
NONNC dont apply the transmissibility multiplier to non-neighbor connections
between regions, specified in 1-st and 2-nd parameter;
12.2.77. MULTREGT 557

ALL apply the transmissibility multiplier to all connections between regions,

specified in 1-st and 2-nd parameter;
NOAQUNNC dont apply the transmissibility multiplier to numerical aquifer
connections.
6. region:
M MULTNUM (see 12.4.23);

F FLUXNUM (see 12.4.18);
O OPERNUM (see 12.4.22);
Default:
first region number non-positive or defaulted value corresponds to all regions;
last region number non-positive or defaulted value corresponds to all regions;
directions in which the multiplier will be applied XYZ;
apply transmissibility multiplier to non-neighbor connections ALL;
region: M.
Example
MULTREGT
1 2 0.3 'XY'/
1 4 0.65 /
3 3 0.2 'Z'/
7 1* 0.4 /
/
12.2.77. MULTREGT 558

12.2.78 ROCKPROP


Section
The keyword specifies properties of cap and base rocks, which will be used to model the
heat exchange between the reservoir and surroundings. The line contains data for one type
of rock. Each line should be terminated with a slash /. The data for all types should be
terminated with a final /.
The line of properties for one type of rock contains the following parameters:
1. the number of rock type (this value should be less than the 1-st parameter of the
keyword ROCKDIMS (see 12.1.35)),
2. initial temperature (METRIC: C, FIELD: F),
3. rock conductivity (METRIC: kJ/m/day/C , FIELD: Btu/ f t/day/F ),
4. volumetric heat capacity (METRIC: kJ/m3 /C , FIELD: Btu/ f t 3 /F ),
5. temperature-dependent coefficient of the volumetric heat capacity of the rock (MET-
RIC: kJ/m3 /K 2 , FIELD: Btu/ f t 3 /F 2 ),
6. calculation method for heat loss: V - Vinsome and Westerveld, N - numerical.
Default:
temperature-dependent coefficient of the volumetric heat capacity of the rock 0,

calculation method for heat loss V (Vinsome).
Example
ROCKDIMS
2 1* /
...
ROCKPROP
1 65 6 2347 2* /
2 70 7 2347 2* /
/
This example sets properties for two types of cap and base rocks (at first the keyword
ROCKDIMS (see 12.1.35) sets the maximum number of rock types 2).
12.2.78. ROCKPROP 559

12.2.79 ROCKCON


Section
The keyword specifies the connection between the reservoir and cap and base rocks,
which will be used to model the heat exchange between the reservoir and surroundings. The
properties of cap and base rocks are specified using the keyword ROCKPROP (see 12.2.78).
The line contains data for connection between one type of rock and reservoir. Each line
should be terminated with a slash /. The data should be terminated with a final /.
Each line contains the following parameters:
1. the number of rock type (this value should be less than the 1-st parameter of the
keyword ROCKDIMS (see 12.1.35)),
2. lower number of connecting grid block in X-direction;
3. upper number of connecting grid block in X-direction;
4. lower number of connecting grid block in Y-direction;
5. upper number of connecting grid block in Y-direction;
6. lower number of connecting grid block in Z-direction;
7. upper number of connecting grid block in Z-direction;
8. face of the reservoir to which the rock connects (one of the labels I-, I+ (X-direction),
J-, J+ (Y-direction), K- (top face of the reservoir), K+ (bottom face of the reservoir));
9. rock influx coefficient (transmissibility multiplier for the connection between the rock
and the reservoir grid).
The number of grid blocks which can be connected to any rock type shouldnt be greater
than the 3-rd parameter of the keyword ROCKDIMS (see 12.1.35)).
Default:
The 9-th parameter 1.
12.2.79. ROCKCON 560

Example
ROCKCON
1 1 25 1 25 1 1 K- /
2 1 25 1 25 20 20 K+ /
This example sets the connection of two rock types and the reservoir grid 25x25x20 on
top and from the bottom.
12.2.79. ROCKCON 561

12.2.80 ROCKCONT


Section
This keyword can be used in thermal models (THERMAL (see 12.1.50), model type
E300) and in temperature option (TEMP (see 12.1.60), model type E100).
The keyword specifies the connection between the reservoir and cap and base rocks,
initial temperature, volumetric heat capacity, rock conductivity of reservoir surroundings and
minimal difference between temperatures, which will be used to model the heat exchange
between the reservoir and surroundings 4.30.
The line contains data for connection between rock region and cap or base rock. Each
line should be terminated with a slash /. Different values can be entered for different rock
regions (ROCKNUM (see 12.4.14)). The data should be terminated with a final /.
Each line contains the following parameters:
1. rock region number;
2. direction in which heat loss properties are applied: I+, I-, J+, J-, K+, K- (I X-axis, J
Y-axis, K Z-axis);
3. initial temperature of reservoir surroundings (METRIC: C, FIELD: F);
4. volumetric heat capacity (METRIC: kJ/m3 C , FIELD: Btu/ f t 3 F );
5. rock conductivity (METRIC: kJ/m day C , FIELD: Btu/ f t day F ).
6. minimal difference between temperatures when the calculations of the heat exchange
should start (METRIC: C, FIELD: F).
The keyword ROCKCONT has Eclipse compatible analogues ROCKCON (see 12.2.79),
ROCKPROP (see 12.2.78).
Example
ROCKCONT
1 I- 70 2347 4 0 /
3 K+ 60 2347 4 0 /
/
12.2.80. ROCKCONT 562

In this example there is the heat exchange between 1-st rock region and reser-
voir surroundings in I- direction, initial temperature 70C , volumetric heat capacity
2347kJ/m3 C , rock conductivity 4kJ/m day C , minimal difference between tem-
peratures 0.
The heat exchange between 2-nd rock region and reservoir surroundings in I- direction,
initial temperature 60C , volumetric heat capacity 2347kJ/m3 C , rock conductivity
4kJ/m day C , minimal difference between temperatures 0.
12.2.80. ROCKCONT 563

12.2.81 THCGAS


Section
This keyword specifies gas phase thermal conductivity (T HCgas ) (METRIC: kJ/m/day/K ,
FIELD: Btu/ f t/day/R). One value should be entered for each grid block. The data should
This keyword can only be used in thermal models (THERMAL (see 12.1.50)).
This thermal conductivity is used to calculate a porosity weighted average of the phase
and rock conductivities (T HCaverage ).
T HCaverage is used in block conductivity calculation.
T HCoil + T HCgas + T HCwater + T HCsolid

T HCaverage = + (1 )T HCrock
N phases
where:
porosity of the grid block;
N phases the number of phases in the model;
T HCgas gas phase thermal conductivity, specified via THCGAS (see 12.2.81);
T HCoil oil phase thermal conductivity, specified via THCOIL (see 12.2.82);
T HCwater water phase thermal conductivity, specified via THCWATER (see 12.2.83);
T HCsolid solid phase thermal conductivity, specified via THCSOLID (see 12.2.84);
T HCrock rock thermal conductivity, specified via THCROCK (see 12.2.85).
12.2.81. THCGAS 564

Example
FIELD
...
THCROCK
200000*24.56 /
THCWATER
200000*8.587 /
THCOIL
200000*1.846 /
THCGAS
200000*0.1091 /
THCSOLID
200000*12.36 /
12.2.81. THCGAS 565

12.2.82 THCOIL


Section
This keyword specifies oil phase thermal conductivity (T HCoil ) (METRIC: kJ/m/day/K ,

N phases
where:
12.2.82. THCOIL 566

Example
FIELD
...
THCROCK
200000*24.56 /
THCWATER
200000*8.587 /
THCOIL
200000*1.846 /
THCGAS
200000*0.1091 /
THCSOLID
200000*12.36 /
12.2.82. THCOIL 567

12.2.83 THCWATER


Section
This keyword specifies water phase thermal conductivity (T HCwater ) (METRIC:

kJ/m/day/K , FIELD: Btu/ f t/day/R). One value should be entered for each grid block.

N phases
where:
12.2.83. THCWATER 568

Example
FIELD
...
THCROCK
200000*24.56 /
THCWATER
200000*8.587 /
THCOIL
200000*1.846 /
THCGAS
200000*0.1091 /
THCSOLID
200000*12.36 /
12.2.83. THCWATER 569

12.2.84 THCSOLID


Section
This keyword specifies solid phase thermal conductivity (T HCsolid ) (METRIC:

kJ/m/day/K , FIELD: Btu/ f t/day/R). One value should be entered for each grid block.

N phases
where:
12.2.84. THCSOLID 570

Example
FIELD
...
THCROCK
200000*24.56 /
THCWATER
200000*8.587 /
THCOIL
200000*1.846 /
THCGAS
200000*0.1091 /
THCSOLID
200000*12.36 /
12.2.84. THCSOLID 571

12.2.85 THCROCK


Section
This keyword specifies rock thermal conductivity (T HCrock ) (METRIC: kJ/m/day/K ,


N phases
where:
12.2.85. THCROCK 572

Example
FIELD
...
THCROCK
200000*24.56 /
THCWATER
200000*8.587 /
THCOIL
200000*1.846 /
THCGAS
200000*0.1091 /
THCSOLID
200000*12.36 /
12.2.85. THCROCK 573

12.2.86 SPECGRID


Section
The keyword gives the same information as several keywords in the Definition section
12.1. These parameters are not used in the run. They can be used for a checking function.
1. the number of blocks in the X-direction (NX in DIMENS (see 12.1.25));
2. the number of blocks in the Y-direction (NY in DIMENS (see 12.1.25));
3. the number of blocks in the Z-direction (NZ in DIMENS (see 12.1.25));
4. the number of reservoirs (NUMRES (see 12.1.69)), there is a coordinate system for
each reservoir;
5. type of the coordinate system (T - cylindrical, F - Cartesian), tNavigator supports only

Cartesian coordinates.
Example
SPECGRID
10 15 4 2 F
/
12.2.86. SPECGRID 574

12.2.87 CARFIN


Section
The keyword specifies a Cartesian local grid refinement (LGR) section 5.6. CARFIN
specifies a cell or a box of cells identified by its global grid coordinates I1-I2, J1-J2, K1-K2,
to be replaced by refined cells. The dimensions of the refined grid within this box are speci-
fied as NX, NY, NZ. The data should be terminated with a slash /.
CARFIN can be followed by keywords that describe properties in LGR, if they are different
from the properties in parent grid. These keywords should be terminated with the keyword
ENDFIN (see 12.2.89), which terminates data for a local grid refinement.
1. name of the local grid refinement;
2. I1 Lower coordinate of the box in the parent grid (in X direction);
3. I2 Upper coordinate of the box in the parent grid (in X direction);
4. J1 Lower coordinate of the box in the parent grid (in Y direction);
5. J2 Upper coordinate of the box in the parent grid (in Y direction);
6. K1 Lower coordinate of the box in the parent grid (in Z direction);
7. K2 Upper coordinate of the box in the parent grid (in Z direction);
8. NX Number of refined cells along X direction;
9. NY Number of refined cells along Y direction;
10. NZ Number of refined cells along Z direction;
11. Maximum number of wells this local refined grid will contain;
12. Name of parent LGR. This item may be set to either a null string or to the string
GLOBAL to indicate that the parent grid is global (that is, this is not a nested refine-
ment). If the parent grid is already an LGR then the name of the parent LGR should be
specified. The range of I, J K indices should then refer to the parent grid. If the parent
grid is the global grid, then the range of I, J and K indices refers to the global grid.
12.2.87. CARFIN 575

Default:
Name of parent LGR GLOBAL.
Example 1.
Example
CARFIN
LGR1 18 18 3 3 1 2 3 3 4 /
PERMX
0.22 0.23 0.20 0.22 0.23 0.22 0.23 0.22 0.21
0.16 0.18 0.22 0.16 0.17 0.16 0.16 0.17 0.16
0.21 0.23 0.19 0.12 0.17 0.17 0.16 0.17 0.16
0.16 0.18 0.22 0.16 0.17 0.16 0.16 0.17 0.16 /
ENDFIN
In this example there is local grid refinement LGR1 of global grid. Box: layers 1 and
2 of global l grid (in Z direction), layer 18 in X direction, layer 3 in Y, are replaced by
Cartesian LGR 3x3x4 with new values of permeability along X.
Example 2. Dual porosity models. To set the refinement for dual porosity models one
need to set the layer numbers for matrix part and the number of refined cells should be
multiplied by 2 (because both matrix and fracture need to be refined).
Example
CARFIN
LGR1 4 4 8 8 1 1 3 3 6 /
ENDFIN
In this example the block [4, 8, 1] (matrix) and the corresponding [4, 8, 13] (fracture)
will be refined (in this model NZ=24, matrix 12 layers, and next 12 layers fracture). The
refinement will contain 3x3x3 matrix blocks and 3x3x3 fracture blocks.
12.2.87. CARFIN 576

12.2.88 REFINE

RUNSPEC x GRID x EDIT x PROPS

Section
x REGIONS x SOLUTION SUMMARY x SCHEDULE
The keyword initiates data input for a named local grid (LGR) section 5.6. The keyword
is followed by the local grid name, terminated with a slash /. Subsequent keywords, from
the available sets described below, are taken to refer to the specified local grid, until either an
ENDFIN (see 12.2.89) (which terminates data for a local grid refinement) or another REFINE
(see 12.2.88) keyword is entered.
REFINE keyword can be used in sections GRID, EDIT, PROPS, REGIONS, SOLUTION
and SCHEDULE.
GRID section
The REFINE keyword can be used in the GRID section to return to a local grid that has
previously been introduced with CARFIN, to make further modifications to its grid data or to
supply additional data. In addition, the BOX (see 12.3.3), COPY (see 12.3.16), EQUALS
(see 12.3.22), MULTIPLY (see 12.3.13) and COPYBOX (see 12.3.17) keywords can be used
to set or modify keywords in regions of the local grid.
EDIT section
The following grid arrays may be edited for a local grid: PORV (see 12.2.27), TRANX (see
12.2.51), DEPTH (see 12.3.27), TRANY (see 12.2.52), TRANZ (see 12.2.53). In addition,
the BOX (see 12.3.3), COPY (see 12.3.16), EQUALS (see 12.3.22) keywords can be used
to set or modify keywords in regions of the local grid. If any grid block values are defaulted,
the host global grid cell value is used.
PROPS section
In end point scaling runs (keyword ENDSCALE (see 12.6.24)) the following keywords
and their directional equivalents are available: SWL (see 12.6.27), SWCR (see 12.6.30),
SWU (see 12.6.34), SG (see 13.7.14), SGCR (see 12.6.31), SGU (see 12.6.35), SOWCR
(see 12.6.32), SOGCR (see 12.6.33), KRO (see 12.6.42), KRORW (see 12.6.42), KRORG
(see 12.6.42), KRW (see 12.6.43), KRWR (see 12.6.43), KRG (see 12.6.44), KRGR (see
12.6.44). In addition, the BOX (see 12.3.3), COPY (see 12.3.16), EQUALS (see 12.3.22)
keywords can be used to set or modify keywords in regions of the local grid. If any grid
block values are defaulted, the host global grid cell value is used.
REGIONS section
The following keywords are available for local grid data input: PVTNUM (see 12.4.2), SAT-
12.2.88. REFINE 577

NUM (see 12.4.3), EQLNUM (see 12.4.9), ROCKNUM (see 12.4.14). In addition, the BOX
(see 12.3.3), COPY (see 12.3.16), EQUALS (see 12.3.22) keywords can be used to set or
modify keywords in regions of the local grid. If any grid block values are defaulted, the host
global grid cell value is used.
SOLUTION section
The following keywords are available for local grid data input: PRESSURE (see 12.15.8),
SWAT (see 12.15.10), SGAS (see 12.15.11), RS (see 12.15.31) or PBUB (see 12.15.30),
RV (see 12.15.32) or PDEW (see 12.15.33). BOX (see 12.3.3), ADD (see 12.3.20), COPY
(see 12.3.16), EQUALS (see 12.3.22) keywords are not available in the SOLUTION section.
SCHEDULE section
The REFINE keyword can be used in the SCHEDULE section to modify region data during
a simulation, though modification of SATNUM (see 12.4.3) or PVTNUM (see 12.4.2) data
during a simulation should be carried out with care and is not recommended in general. In
addition, the BOX (see 12.3.3) keyword can be used to set or modify keywords in regions
of the local grid. The following keywords can be used after REFINE to enter data for local
grid: PVTNUM (see 12.4.2), SATNUM (see 12.4.3), MULTX (see 12.2.15), MULTY (see
12.2.17), MULTZ (see 12.2.19), MULTPV (see 12.2.28).
In this example in GRID section for local grid LOCAL345 the values of porosity are set:
Example
REFINE
'LOCAL345'/
PORO
23*0 1.912615E-001
1.857747E-001 1.848700E-001 1.843748E-001 1.824189E-001
1.820803E-001 1.813895E-001 1.806574E-001 1.814170E-001
1.828329E-001 1.840282E-001 1.918230E-001 1.929848E-001
1.915058E-001 1.922970E-001 1.928496E-001 1.928771E-001
1.945545E-001 1.933889E-001 2*0
12*0/
ENDFIN
In this example in GRID section for local grid LGR523 the values of permeability in X
and Y direction are multiplied by 0.52 in the specified parallelepiped:
12.2.88. REFINE 578

Example
REFINE
LGR523 /
MULTIPLY
PERMX 0.52 94 98 198 204 1 3 /
PERMY 0.52 94 98 198 204 1 3 /
/
ENDFIN
In this example in REGIONS section for local grid LGR676 the numbers of FIP region
to which cells belong are set:
Example
REFINE
'LGR674'/
FIPNUM
108*8
108*2
108*8
108*2 /
ENDFIN
12.2.88. REFINE 579

12.2.89 ENDFIN


Section
The keyword terminates data for a local grid refinement (LGR) section 5.6.
CARFIN specifies a cell or a box of cells identified by its global grid coordinates to be
replaced by refined cells. CARFIN (or REFINE (see 12.2.88)) can be followed by keywords
that describe properties in LGR, if they are different from the properties in parent grid. These
keywords should be terminated with the keyword ENDFIN (see 12.2.89), which terminates
data for a local grid refinement.
It is not necessary to insert ENDFIN (see 12.2.89) between successive CARFIN (see
12.2.87) or REFINE (see 12.2.88) keywords. The primary purpose of ENDFIN (see 12.2.89)
is to revert the program to reading data for the global grid system. In the EDIT, PROPS,
REGIONS, SOLUTION and SCHEDULE sections, the ENDFIN (see 12.2.89) keyword tells
the program that subsequent data no longer applies to the local grid named in the previous
REFINE (see 12.2.88) keyword.
The ENDFIN keyword has no associated data.
12.2.89. ENDFIN 580

12.2.90 NXFIN / NYFIN / NZFIN


Section
These keywords can be used to specify number of local cells in each global cell of an
LGR (NXFIN in X direction, NYFIN in Y direction, NZFIN in Z direction) (section 5.6).
If a local grid refinement covers more than one global cell in the X direction, NXFIN can
be used to specify how many local cells each of the global cells is divided into. The keyword
should be placed after the keyword CARFIN (see 12.2.87) introducing the local grid, and
before the local grid data is terminated with ENDFIN (see 12.2.89).
NXFIN should be followed by I2-I1+1 values terminated with a slash (/), where I1 and I2
are the I-coordinates defining the box of global grid cells to be refined (parameters 2 and 3 in
keyword CARFIN (see 12.2.87)). The number of values is thus the number of global cells of
the refinement counted along the X direction. The values represent the number of local cell di-
visions, counted along the X direction, in each of the global cells. The sum of the values must,
of course, be equal to NX set in parameter 8 of CARFIN (see 12.2.87). In the absence of this
keyword, the global cells are refined to contain equal numbers of local cells in the X direction.
Analogously for the keywords NYFIN, NZFIN.
Example
CARFIN
LGR1 6 9 2 3 18 22 12 4 16 /
NXFIN
4 3 3 2 /
NYFIN
2 2 /
NZFIN
3 4 3 4 2 /
In this example 4 global cells in X direction are replaced by 12 local cells. First global
cell is replaced by 4 local cells, second global cell by 3 local cells, 3-rd by 3, 4-th by
2.
2 global cells in Y direction are replaced by 4 local cells. First global cell is replaced by 2
local cells, second global cell by 2 local cells.
5 global cells in Z direction are replaced by 14 local cells. First global cell is replaced by 3
12.2.90. NXFIN / NYFIN / NZFIN 581

local cells, second global cell by 4 local cells, 3-rd by 3, 4-th by 4, 5-th by 2.
12.2.90. NXFIN / NYFIN / NZFIN 582

12.2.91 HXFIN / HYFIN / HZFIN


Section
These keywords can be used to specify the size ratios of each cell in a local grid re-
finement (LGR) (HXFIN in X direction, HYFIN in Y direction, HZFIN in Z direction)
(section 5.6).
These keywords should be placed after the CARFIN (see 12.2.87) keyword introducing
the local grid and before the terminating ENDFIN (see 12.2.89).
HXFIN should be followed by NX values the total number of cells in the refined grid
along the X direction as specified in keyword CARFIN (see 12.2.87) parameter 8. The values
represent the X direction size ratios for each the refined grid cells. You may default the size
ratios for all the refined cells belonging to a particular host cell. If no ratios are given for a
host cell, it is divided up in equal proportions. Each host cell must have the size ratios of its
constituent refined cells either all set or all defaulted.
Analogously for the keywords HYFIN, HZFIN.
Example
NZFIN
3 2 /
HZFIN
2.0 1.0 3.0
3.0 2.0 /
In this example 2 global cells in Z direction are replaced by 5 local cells. In upper (in Z
direction) global layer there are 3 local layers (ratios 2:1:3), in bottom global layer 2 local
layers (ratios 3:2).
12.2.91. HXFIN / HYFIN / HZFIN 583

12.2.92 AMALGAM


Section
The keyword specifies LGR amalgamations. Amalgamation are considered as a single

entity, with non-neighbor connections between any LGRs which touch.
The keyword is ignored. This is an Eclipse compatibility field. In tNavigator all LGRs
are considered as with AMALGAM keyword.
12.2.92. AMALGAM 584

12.2.93 COARSEN


Section
The keyword sets blocks coarsening. COARSEN specifies a box of cells identified by its
global grid coordinates I1-I2, J1-J2, K1-K2, to be replaced by coarsened cells. The dimen-
sions of the coarsened grid within this box are specified as NX, NY, NZ. The data should be

1. I1 Lower coordinate of the box in the grid (in X direction);
2. I2 Upper coordinate of the box in the grid (in X direction);
3. J1 Lower coordinate of the box in the grid (in Y direction);
4. J2 Upper coordinate of the box in the grid (in Y direction);
5. K1 Lower coordinate of the box in the grid (in Z direction);
6. K2 Upper coordinate of the box in the grid (in Z direction);
7. NX Number of refined cells along X direction. Number I2 I1 + 1 should be divisible

by NX;
8. NY Number of refined cells along Y direction. Number J2 J1 + 1 should be divisible

by NY;
9. NZ Number of refined cells along Z direction. Number K2 K1 + 1 should be divisible

by NZ.
Any number of such data lines can be specified. Each line should be ended by a symbol
/. The data should be terminated with a slash /.
Application of the keyword COARSEN:

If the keyword COARSEN is used then first the detailed grid with all properties is
made and after that coarsening is applied to the grid.
So, for example if there is initial permeability property, then it is multiplied by the
array of multipliers, operations will be applied in the following order:
1. Initial permeability property is multiplied by the array of multipliers we have

new permeability property array.
12.2.93. COARSEN 585

2. Then to this new permeability property array COARSEN is applied during

coarsening values are recalculated as pore volume weighted average.
If the keyword PINCH (see 12.2.54) is used:
1. blocks between which PINCH was applied appear to be in one coarse block, then
geometrical transmissibilities are recalculated, but non-neighboring connections
dont exist any more.
2. blocks between which PINCH was applied appear to be in different coarse blocks,
then non-neighboring connections can be deleted or not depending on blocks
position. For example, if the blocks are "neighbors" now, then non-neighboring
connections will be deleted.
Example
COARSEN
2 10 1 1 1 1 1 1 1 /
1 10 1 1 2 2 1 1 1 /
2 9 1 1 3 3 1 1 1 /
/
In the example 3 block coarsenings are set. Blocks from 2-nd to 10-th, from 1-st to 10-th
and from 2-nd to 9-th in the 1-st, 2-nd and 3-rd layers along Z correspondingly are replaced
by one block.
12.2.93. COARSEN 586

12.2.94 GRIDFILE


Section
This keyword defines save of calculation results in EGRID and INIT format files
(*.EGRID format and *.INIT format of Eclipse simulator). These files will be gener-
ated, if simulator (its console version) is run with option -b (b stands for binary).
The following parameters should be defined (list should end with a slash, /).
this is an Eclipse compatibility field, possible values are 0, 1, 2, 1* (i.e. default);

value of this parameter is IGNORED because of different processing of result files in
tNavigator;
parameter indicating whether files of INIT and EGRID format should be output (the
latter containing data on inactive cells, non-neighbor connections, local grid refinements
and coarsenings); possible values: 0 (dont output), 1 (output).
Default: output of EGRID and INIT files: 1 (i.e. output).
Example
GRIDFILE
2 1
/
In this example files of EGRID and INIT format will be written after calculation with -b
option. File of *.GRID format will not be generated (first argument of keyword GRIDFILE
is ignored in current version of tNavigator).
12.2.94. GRIDFILE 587

12.2.95 PLMIXNUM


Section
This keyword specifies regions with different polymer properties POLYMER (see
12.1.48).
Polymer Flood section 2.20.

The number of values should be equal to the number of grid blocks. The data should be
Maximal number of these regions is defined via the 10-th parameter of REGDIMS (see
12.1.29).
Each region with different polymer properties can have its own values of Todd-Longstaff
mixing parameter (PLMIXPAR (see 12.8.19)) and maximum polymer and salt concentra-
tions used in the mixing parameter calculation of fluid component viscosity (PLYMAX (see
12.8.18)).
Example
PLMIXNUM
23000*1 23000*2/
In this example first 23000 grid blocks belong to the 1-st region, next 23000 blocks
belong to 2-nd region.
12.2.95. PLMIXNUM 588

12.2.96 ROCKDEN


Section
This keyword sets coal density (METRIC: kg/m3 , FIELD: lb/ f t 3 ) in Coal Bed Methane
Model 2.29.
Example
ROCKDEN
1200*1340 1200*1335 /
12.2.96. ROCKDEN 589

12.2.97 IMPORT


Section
x REGIONS x SOLUTION SUMMARY SCHEDULE
The keyword imports cubes into a model. Cubes should be specified in binary format.
1. file name;
2. file format: UNFORMATTED.
Default:
file format: UNFORMATTED.
Example
IMPORT
X.AAA /
In this example the keyword IMPORT (see 12.2.97) imports the file X.AAA to the model.
12.2.97. IMPORT 590

12.2.98 VISGRID


Section
The keyword is used to specify file of .EGRID format to visualize grid. This keyword is
used in models with unstructured grid.
1. file name to import (or path to file) of EGRID format;
2. formatting type: UNFORMATTED unformatted file. It can be shorted to letter U.
Note: in calculations the centers of grid blocks from EGRID file with unstructured grid
will be used. So the displacement specified in EGRID file will be used (not the calculated
displacement of calculaiton grid); this affects the DEPTH (see 12.3.27) keyword.
During model reading in the log there will be a warning about maximal displacement of grid
block depths.
Default:
formatting type: UNFORMATTED.
Example
VISGRID
MODEL.EGRID /
In the example file MODEL.EGRID is imported.
Data reading when VISGRID keyword is used.

Now tNavigator supports only composite grid consisting of unstructured grids. During reading
tNavigator finds in the header the keyword GRIDHEAD (describing grid properties). Possible
options: 0, 1, 2.
0 composite grid;
1 corner point;
2 unstructured grid.
12.2.98. VISGRID 591

In tNavigator the case 0 is supported composite grid. In this case we check 26-th
parameter, that sets the number of compose grids.
Then the data for each grid goes separately. Each grid has its own GRIDHEAD (GRID-
HEAD describes properties of each compose grid). We check the first parameter. For this
parameter option 2 is supported unstructured grid.
So the composite grid consisting of unstructured grids is set.
The following words are required to construct the grid: NDCOORD, NFACENOD,
FACENODS, NCELLFAC, CELLFACS, EXTCELL, CELLCTRS, ENDGRID:
NDCOORD, NFACENOD, FACENODS are set for one (first) grid and are used for all
grids;
NDCOORD contains three coordinates (x,y,z) of all vertices that are in the grid;
NFACENOD sets the number of vertices on each face. The dimension of the array -
number of faces;
FACENODS vertices numbers are set for each face;
NFACENOD and FACENODS are used together to specify uniquely each face.
The following parameters are set for each grid independently:
NCELLFAC sets the number of faces for each block;
CELLFACS for each face of active block sets its number in the link NFACENOD,
FACENODS;
EXTCELL sets the connection between each active block of unstructured grid and
grid block in calculation grid;
CELLCTRS three coordinates (x,y,z) of the centers of active blocks.
12.2.98. VISGRID 592

12.2.99 DIFFMMF


Section
The keyword can be used only in model with dual porosity mode (the keyword DUAL-
PORO (see 12.1.76)) which uses either the molecular diffusion option (see the keyword
DIFFUSE (see 12.1.66)) or the Coal Bed Methane option (the keyword COAL (see 12.1.78)
and section Coal Bed Methane Model of tNavUserManual)
The keyword sets multipliers of diffusivities which calculated for non-neighbour connec-
tions (see the keyword NNC (see 12.2.48)). Connections represents the matrix-to-fracture
flows.
Values which specified for matrix cells (i.e. upper half of the model) are used as multi-
pliers. Values which specified for fracture cells are ignored.
1. multipliers of diffusivities for each grid cell or each box cell (the keyword BOX (see
12.3.3)).

Default:
multipliers of diffusivities: 1 for cells out of specified box.
Example
BOX
2 1 2 /
DIFFMMF
4*0.80
In the example box of 4 cells is specified. For these cells multipliers of diffusivities are
set, each of them is 0.8.
12.2.99. DIFFMMF 593

12.2.100 INIT


Section
This keyword sets the output of INIT file with model information from sections GRID,
PROPS, REGIONS. This keyword is optional. tNavigator always writes INIT file by default
in the RESULTS folder.
12.2.100. INIT 594

12.2.101 RPTGRID/ RPTGRIDL


Section
These keywords control output for GRID section for simulator Eclipse.
12.2.101. RPTGRID/ RPTGRIDL 595

12.2.102 CORNERS


Section
The keyword sets coordinates of block grid tops (METRIC: m, FIELD: f t ). The data
Note. To this keyword the format Y-pillar grid is converted; so this format can be used
in the model without modifications. See Example 2 Y-pillar grid format.
Data specification.
In case if in the model there are nx ny nz blocks (DIMENS (see 12.1.25)), then one should
set 3 8 nx ny nz coordinates of their tops. For models with single porosity the order is
the following:
8 nx ny nz - X coordinates of blocks;
8 nx ny nz - Y coordinates of blocks;
8 nx ny nz - Z coordinates of blocks;
Geometry for dual porosity models.

For models with dual porosity (section 2.28) the order is the following:
8 nx ny n2z - X coordinates of matrix blocks;
8 nx ny n2z - Y coordinates of matrix blocks;
8 nx ny n2z - Z coordinates of matrix blocks;
8 nx ny n2z - X coordinates of fracture blocks;
8 nx ny n2z - Y coordinates of fracture blocks;
8 nx ny n2z - Z coordinates of fracture blocks.
To set the half data (logic of the keyword DPGRID (see 12.2.66)) the coordinates should
be specified for matrix blocks:
8 nx ny n2z - X coordinates of matrix blocks;
8 nx ny n2z - Y coordinates of matrix blocks;
8 nx ny n2z - Z coordinates of matrix blocks.
12.2.102. CORNERS 596

The data is copied for fracture blocks in the same order.
Example 1. CORNERS keyword.
Example
CORNERS
0 50 50 100
0 50 50 100
0 50 50 100
0 50 50 100
0 50 50 100
0 50 50 100
0 50 50 100
0 50 50 100
0 0 0 0
50 50 50 50
50 50 50 50
100 100 100 100
0 0 0 0
50 50 50 50
50 50 50 50
100 100 100 100
500 500 500 500
500 500 500 500
500 500 500 500
500 500 500 500
502 502 502 502
502 502 502 502
502 502 502 502
502 502 502 502
/
In the example grid of 2x2x1-size is specified. Length of block along x - and y-directions
is equal to 50 m, along z-direction it is equal to 2 m. Deep of a top layer is 500 m, thats
why z-coordinates of a top layer is 500.
Example 2. Format Y-pillar grid.
12.2.102. CORNERS 597

Example
'DIMENS' 3 'INTE'
41 56 332
'MAPUNITS' 1 'CHAR'
'METRES'
'MAPAXES' 6 'REAL'
8.09443375E+05 2.44606656E+05 8.09443375E+05 2.43606656E+05
8.10443375E+05 2.43606656E+05
'GRIDUNIT' 2 'CHAR'
'METRES' 'MAP'
'COORDS' 7 'INTE'
1 1 1 1 1 0
0
'CORNERS' 24 'REAL'
8.09755063E+05 2.42747469E+05 9.91198254E+00 8.09786813E+05
2.42737656E+05 8.43673611E+00 8.09777500E+05 2.42689859E+05
4.49941254E+00 8.09811188E+05 2.42679813E+05 2.84124708E+00
8.09800750E+05 2.42793250E+05 1.50899658E+02 8.09833250E+05
2.42783453E+05 1.47999649E+02 8.09823188E+05 2.42737047E+05
1.46093796E+02 8.09857750E+05 2.42727031E+05 1.43033371E+02
'COORDS' 7 'INTE'
2 1 1 2 1 0
0
'CORNERS' 24 'REAL'
12.2.102. CORNERS 598

12.2.103 DEACDEPT


Section
The keyword deactivates blocks by their depth value. The following parameters should
be specified:
1. depth value (METRIC: m, FIELD: f t ). Block is deactivated if depth of each of its top
is greater than specified value.
Example
DEACDEPT
2000 /
12.2.103. DEACDEPT 599

12.3. Arithmetic section tNavigator-4.2
12.3 Arithmetic section

This section describes all keywords necessary for performing arithmetic operations.
A lot of ket=ywords are available, for example:
ARITHMETIC (see 12.3.2) facilitating work with large data arrays and their modifi-
cation;
IF (see 12.3.7), IF-THEN-ELSE-ENDIF (see 12.3.8) expressions and conditions;
ARR (see 12.3.5) user arrays;
INTERPOLATE (see 12.3.12) interpolation;
BLOCK (see 12.3.9) can be used to prepare source data for interpolation;
STORE (see 12.3.10) saving of array into specified file during model reading;
SYSTEM (see 12.3.11) allows to run external script (for example, pythonSs, perlSs,
bashSs or C++Ss one) during model reading.
12.3. Arithmetic section 600

12.3.1 EDIT


Section
The keyword specifies the beginning of data section which contains instructions for
modifying the pore volumes, transmissibilities and non-neighbor connections computed by
the data entered in the GRID (see 12.2.1) section.
12.3.1. EDIT 601

12.3.2 ARITHMETIC


Section
The keyword specifies arithmetic operations on arrays. It is followed by operation de-

scription. The data should be terminated with a slash /.
Arithmetic operations are performed on arrays element by element. For example, PERMX
= 2 * PERMY + PERMZ * PORO means PERMXi, j,k = 2 PERMYi, j,k + PERMZi, j,k
POROi, j,k . Here equality is an assignment statement, that is: the same array may be used
several times in the expression and both in right and left hand sides of the assignment.
The keyword may be present both in initial data section and in schedule section (see
below list of keywords with indication whether this array may be modified during calculation
in schedule by means of ARITHMETICS keyword or not).
Note that scalar value is expanded to an array with all elements equal to this value.
Interpolation can be used in GRID section INTERPOLATE (see 12.3.12).
The following binary operations are supported (with two arguments):

+ element by element summation;
- element by element subtraction;
* element by element multiplication;
/ element by element division;
raising to a power;
== comparison;
MAX(,) element by element maximum calculation;
MIN(,) element by element minimum calculation;
GROW(Map>0,n) defines surroundings of the selected Map with the radius of n

blocks (for MESH only).
The following unary operations are supported (with one argument):
- element by element negation
LOG element by element logarithm calculation
12.3.2. ARITHMETIC 602

LOG10 element by element decimal logarithm calculation
EXP element by element exponent calculation
SIN element by element sine calculation
COS element by element cosine calculation
TAN element by element tangent calculation
SQRT element by element square root calculation
ABS element by element absolute value calculation
MAX element by element maximum calculation (at the output gives scalar)
MIN element by element minimum calculation (at the output gives scalar)
SUM sum (at the output gives scalar)
AVG average value (at the output gives scalar)
RND(n) at the output gives a map containing not more than n 1 in random blocks on
the map, the rest assume zero) for MESH only
GROW(Map>0,n) defines surroundings of the selected Map with the radius of n

blocks (for MESH only)
ROUND rounds a map parameter value
The following operations with three (or more) arguments are supported:
IF(condition, expr1, expr2) this operation checks a condition. If a condition is true

(condition is nonzero), then the function returns expr1. If a condition is false (condition
= 0), then the function returns expr2.
More complex conditions can be set via the keyword IF-THEN-ELSE-ENDIF

(see 12.3.8).
Example 1. Use of IF
Example
ARR1 = if (FIPNUM == 2, PORO, -999.25)
In this example used-defined array ARR1 is created. In the blocks that belong to the 2-nd
fluid-in-place region (condition FIPNUM == 2) an array ARR1 elements are equal to the
values of porosity map in (PORO). The value -999.25 is assigned to other blocks.
Arrays available in arithmetic:

Grid:
DX (see 12.2.2) size of cells in X-direction

DY (see 12.2.2) size of cells in Y-direction
DZ (see 12.2.2) size of cells in Z-direction
PERMX (see 12.2.13) permeability in X-direction
PERMY (see 12.2.13) permeability in X-direction
PERMZ (see 12.2.13) permeability in X-direction
MULTX (see 12.2.15) transmissibility multipliers in X-direction (also during
calculation)
MULTXM corresponds to the map MULTX- (see 12.2.16)
MULTY (see 12.2.17) transmissibility multipliers in Y-direction (also during
calculation)
MULTYM corresponds to the map MULTY- (see 12.2.18)
MULTZ (see 12.2.19) transmissibility multipliers in Z-direction (also during
calculation)
MULTZM corresponds to the map MULTZ- (see 12.2.20)
TRANX (see 12.2.51) transmissibility in X-direction
TRANY (see 12.2.52) transmissibility in Y-direction
TRANZ (see 12.2.53) transmissibility in Z-direction
TOPS (see 12.2.6) depths for top planes of cells in first layer
DEPTH (see 12.3.27) depths of the block centers
NTG (see 12.2.25) net to gross values
PORO (see 12.2.24) porosity values
PORV (see 12.2.27) net pore volume
STDPORV initial pore volume at reference pressure
MULTPV (see 12.2.28) pore volume multiplier
I (map with integer values) i-coordinate (block number in X-direction)
J (map with integer values) j-coordinate (block number in Y-direction)
K (map with integer values) k-coordinate (block number in Z-direction)
X block coordinate in X-direction
Y block coordinate in Y-direction
Z block coordinate in Z-direction
VOL geometric volume of the block
BOX (see 12.3.3) defines the grid part where parameter value will be edited

ARR (see 12.3.5) temporary user-defined arrays.
Initial conditions:
SOIL (see 12.15.12) initial oil saturation

SWAT (see 12.15.10) initial water saturation
SGAS (see 12.15.11) initial gas saturation
PRESSURE (see 12.15.8) initial pressure
PBUB (see 12.15.30) initial bubble point pressure
RS (see 12.15.31) initial gas solution in oil
RV (see 12.15.32) initial oil vaporization in gas
PDEW (see 12.15.33) initial dew point pressure
Regions:
ACTNUM (see 12.2.29) active/inactive cells

BNDNUM (see 12.4.19) boundary condition
EQLNUM (see 12.4.9) equilibrium regions
FIPNUM (see 12.4.10) FIP regions
FIP (see 12.4.11) additional user-defined FIP regions
SATNUM (see 12.4.3) Saturation regions (also during calculation)
PVTNUM (see 12.4.2) PVT regions (also during calculation)
End-point scaling:
SWL (see 12.6.27) minimal water saturation

SWCR (see 12.6.30) critical water saturation
SWU (see 12.6.34) maximal water saturation
SOWCR (see 12.6.32) critical oil-to-water saturation
PCW (see 12.6.46) water capillary pressure
SWATINIT (see 12.6.48) initial water saturation
SGL (see 12.6.29) minimal gas saturation
SGCR (see 12.6.31) critical gas saturation
SGU (see 12.6.35) maximal gas saturation
SOGCR (see 12.6.33) critical oil-to-gas saturation
PCG (see 12.6.47) gas capillary pressure
KRW (see 12.6.43) maximal water relative permeability that is used in RP
end-point scaling

KRWR (see 12.6.43) water relative permeability at the residual oil (of residual
gas in gas-water system) that is used in RP end-point scaling
KRORW (see 12.6.42) oil relative permeability at the critical water saturation
that is used in RP end-point scaling
KRG (see 12.6.44) maximal gas relative permeability that is used in RP end-
point scaling
KRGR (see 12.6.44) gas relative permeability at the residual oil (of residual
water in gas-water system) that is used in RP end-point scaling
KRORG (see 12.6.42) oil relative permeability at the critical gas saturation that
is used in RP end-point scaling
KRO (see 12.6.42) maximal oil relative permeability that is used in RP end-point
scaling that is used in RP end-point scaling
Grid dimensions (only in the right hand side of arithmetic expressions):
NX (see 12.1.25) number of blocks in X direction

NY (see 12.1.25) number of blocks in Y direction
NZ (see 12.1.25) number of blocks in Z direction
Usual operation priorities are used. Operations may be grouped by parentheses forming
more complex expressions like PERMX = LOG (X) * max (TOPS, 2000) * (2 * PERMY +
PERMZ * PORO).
For performing operation on a subarray, subarray scopes should be specified in brackets:

PERMX(i1:i2,j1:j2,k1:k2) = PERMY + PERMZ * PORO. All the arrays in the right-hand side
of the formula will be taken in these scopes.
An array part can also be specified via BOX (see 12.3.3) function.
Example 2.
Example
ARITHMETIC
PERMX = 2 * PERMY + PERMZ * PORO
/
This example sets permeability in X direction equal to sum of doubled permeability in Y
direction and product of permeability in Z direction and porosity. This operation is performed
on all grid blocks.
The next example illustrates performing arithmetic operation on an array subregion:

Example 3.

Example
ARITHMETIC
PERMX(50:100,10:20,2:2) = 2 *PERMX + PERMY + PERMZ * PORO
/
Here porosity and X, Y, Z permeability values, defined above, are used to redefine
permeability in X direction for the following subarray: in X direction blocks from 50th to
100th are taken, in Y direction from 10th to 20th, and in Z direction layer 2.
Example 4.
Example
-
GRID
-
INCLUDE
'grid.inc'/
INCLUDE
'ARRSAT.inc'/
ARITHMETIC
PERMX =
(ARRSAT==1)*(12*EXP(5*PORO))+(ARRSAT==2)*(8*EXP(10*PORO))+
+(ARRSAT==3)*(15*EXP(0.3*PORO))+(ARRSAT==4)*(15*EXP(9*PORO))
PERMY = PERMX
PERMZ = PERMX*0.1
/
In the example PERMX array via ARRSAT array is defined. ARRSAT array is containing
in including file ARRSAT.inc, it is a copy of SATNUM array. In blocks which belongs to dif-
ferent CodeARRSAT-regions (conditions ARRSAT == 1, ARRSAT == 2 and so on) PERMX
is calculated via differnt formulas from PORO. Description of defining ARRSAT array see at
the description of the keyword ARR (see 12.3.5).

Example
-
REGIONS
-
ARITHMETIC
PVTNUM = 1
EQLNUM = 1
EQLNUM( , ,1:62) = 1
EQLNUM( , ,63:87) = 2
EQLNUM( , ,88:106) = 3
EQLNUM( , ,107:197) = 4
/
In the example PVTNUM and EQLNUM arrays are defined in section REGIONS. At first
each element values of these arrays are equal to 1, i.e. one equilibration region and one
PVT-region are defined. Then values of EQLNUM array are changed: all grid blocks with
k-coordinate (Z direction) from 1 to 62 belong to 1-st equilibration region (empty i and j (X
and Y) coordinates mean that all X and Y coordinates are taken for blocks in specified Z
ranges), all grid blocks with k-coordinate from 63 to 87 belong to 2-nd equilibration region
and so on.

12.3.3 BOX


Section
This keyword is used to define current input box to edit grid properties. Six numbers
must be specified. (For example: IMIN IMAX JMIN JMAX KMIN KMAX).
Example
DIMENS
10 10 50
/
...
BOX
5 10 5 10 20 30
/
This example specifies a 6x6x11 box in a 10x10x50 grid.
12.3.3. BOX 609

12.3.4 ENDBOX


Section
The keyword has no parameters, it reset the current input box to the entire grid.
Example
DIMENS
10 10 50
/
...
BOX
5 10 5 10 20 30
/
...
ENDBOX
/
In this example there were specified a 5x5x10 box, and after applying ENDBOX the
current input box encompasses the entire grid.
12.3.4. ENDBOX 610

12.3.5 ARR


Section
This keyword defines temporary user-defined arrays. Array name must begin with ARR,
then any numbers and letters can be used. For example: ARRUSER1, ARRUSER2, ARRMY-
PORO, etc.
Arrays are temporary, they can be used in sections before SCHEDULE. After SCHEDULE
section these arrays are not saved and cant be used. These arrays can be used in arithmetic
(keyword ARITHMETIC (see 12.3.2)).
These arrays are available in graphical user interface:
Visualization in the tab Maps. Initial Maps.
Can be used in User Cuts and Maps. They are available in the calculator in the list
Maps. Initial Maps.
There are several possibilities to define arrays.
Method 1 assign the number to each array element. The data should be terminated with
a slash /.
Example 1.
Example
ARRUSER1
15000*2
/
Method 2 assign one value for all array elements via EQUALS (see 12.3.22):
Example 2.
Example
EQUALS
ARRUSER1 2 /
/
Method 3 assign one value for all array elements via ARITHMETIC (see 12.3.2):
Example 3.
12.3.5. ARR 611

Example
ARITHMETIC
ARRUSER1=3
/
Examples of usage: Example 4.
Example
COPY
ARRUSER1 MULTX /
/
In this example we assign to MULTX (see 12.2.15) array the values of user-defined array
ARRUSER1.
Example 5.
Example
EDIT
ARITHMETIC
PORV=ARRUSER1
/
In this example we assign to PORV (see 12.2.27) array the values of user-defined array
ARRUSER1.
Example 6.
Example
-
GRID
-
INCLUDE
'grid.inc'/
INCLUDE
'ARRSAT.inc'/
ARITHMETIC
PERMX =
(ARRSAT==1)*(12*EXP(5*PORO))+(ARRSAT==2)*(8*EXP(10*PORO))+
+(ARRSAT==3)*(15*EXP(0.3*PORO))+(ARRSAT==4)*(15*EXP(9*PORO))
PERMY = PERMX
PERMZ = PERMX*0.1
/
12.3.5. ARR 612

in including file ARRSAT.inc, it is a copy of SATNUM array. In blocks which belongs
to different CodeARRSAT-regions (conditions ARRSAT == 1, ARRSAT == 2 and so on)
PERMX is calculated via differnt formulas from PORO.
12.3.5. ARR 613

12.3.6 WORK/IWORK


Section
This keyword can be used to set arbitrary user arrays. It has an analogue keyword ARR
(see 12.3.5).
WORK array of real numbers,
IWORK array of integer numbers.
In tNavigator 2 options to use these keywords are possible:
1. Inside the keyword OPERATE (see 12.3.25).

In this case the arrays should have the names WORK1, WORK2, ... (only numbers can
be used in names). The number of user arrays should be set via 8-th and 9-th parameter
of the keyword REGDIMS (see 12.1.29).
2. Analogously with the keyword ARR (see 12.3.5). WORK array of real numbers,
IWORK array of integer numbers. In this case the keywords can have different names
from numbers and letters. For example IWORKFIPNUM.
Also these keywords can be automatically generated by tNavigator Assisted History
Matching module. In this case it is not recommended to edit them manually.
12.3.6. WORK/IWORK 614

12.3.7 IF


Section
This keyword specifies IF function. See also the keyword IF-THEN-ELSE-ENDIF

(see 12.3.8).
This keyword can be used only in the keyword ARITHMETIC (see 12.3.2).
The data should be specified this way:
IF(condition, expr1, expr2)
This operation checks a condition:
If a condition is true (condition is nonzero), then the function returns expr1.
If a condition is false (condition = 0), then the function returns expr2.
Example
ARR1 = IF (FIPNUM == 2, PORO, -999.25)
In this example used-defined array ARR1 is created. In the blocks that belong to the 2-
nd fluid-in-place region (condition FIPNUM == 2) an array ARR1 elements are equal to the
values of porosity map in these blocks (PORO). The value -999.25 is assigned to other blocks.
12.3.7. IF 615
12.3.8 IF-THEN-ELSE-ENDIF


Section
This keyword set the function If-then-else. See also the keyword IF (see 12.3.7).
The keyword can only be used inside ARITHMETIC (see 12.3.2).

The keyword contains the following parts:
IF if (the beginning);
THEN;
ELSEIF;
ELSE;
ENDIF the end.
Inside one expression several ELSEIF, THEN can be used.

At the end of each line the back slash must be used \ to continue on the next line. The
Example 1.
Example
ARITHMETIC
SATNUM = IF i < 5 THEN 1 \
ELSEIF i > 20 THEN 2 \
ELSEIF i > 10 THEN 1 \
ELSE 2 \
ENDIF
/
In this example saturation regions depend on blocks number in X-direction.
Example 2.
12.3.8. IF-THEN-ELSE-ENDIF 616

Example
GRID
INCLUDE
'grid.inc'/
INCLUDE
'ARRSAT.inc'/
ARITHMETIC
PERMX = IF (ARRSAT==1) THEN 12*EXP(5*PORO) \
ELSEIF (ARRSAT==2) THEN 8*EXP(10*PORO) \
ELSEIF (ARRSAT==3) THEN 15*EXP(0.3*PORO) \
ELSEIF (ARRSAT==4) THEN 15*EXP(9*PORO) \
ELSE 12*EXP(0.8*PORO) \
ENDIF
PERMY = PERMX
PERMZ = PERMX*0.1
/
in including file ARRSAT.inc, it is a copy of SATNUM array. In blocks which belongs
to different CodeARRSAT-regions (conditions ARRSAT == 1, ARRSAT == 2 and so on)
PERMX is calculated via differnt formulas from PORO.
12.3.8. IF-THEN-ELSE-ENDIF 617

12.3.9 BLOCK

RUNSPEC x GRID EDIT x PROPS

Section
This keyword can be used only in the keyword ARITHMETIC (see 12.3.2).
This keyword can be used to prepare source data for interpolation (see an example below).
Interpolation is specified via INTERPOLATE (see 12.3.12).
The data can be specified one of the following ways:
BLOCK (x,y)
The function gives as a result a 3D cube (dimensions NX, NY, NZ), which has 1 values
near the vertical line (x,y), and else zero values.
BLOCK (x,y,z)
The function gives as a result a 3D cube (dimensions NX, NY, NZ), which has 1 values
near the point (x,y,z), and else zero values. There can be several blocks near the point
(x,y,z).
Example
ARITHMETIC
ARRPOROSRC=-999.25
ARRPOROSRC=IF (block (1500, -99000) == 1, 0.3, ARRPOROSRC)
ARRPOROSRC=IF (block (136500, -65000, 2319.7) == 1, 0.03, AR-
RPOROSRC)
PORO= interpolate_ml_idw (ARRPOROSRC, -999.25, 0.5, 2)
PORO=MIN (MAX (PORO, 0), 1)
/
Example description:
1. In this example used-defined array ARRPOROSRC is created (user-defined temporary
arrays ARR (see 12.3.5)).
This is the source cube for interpolation. All blocks has the value -999.25.
2. We assign the value 0.3 to all blocks through which the vertical line (1500, -99000)
goes (other values remain unchanged, see function IF (see 12.3.7)).
12.3.9. BLOCK 618

5. We assign the value 0.03 to all blocks that contain the point (136500, -65000, 2319.7)
(other values remain unchanged, see function IF (see 12.3.7)).
6. Then porosity cube PORO is calculated via IDW interpolation with the source cube
ARRPOROSRC.
7. We check if the result values of porosity dont exceed 1. If it happens then we assign
a value 1 to this block (via a function min).
12.3.9. BLOCK 619

12.3.10 STORE


Section
The keyword calls the saving of array into specified file during reading model process.
In one data line the following parameters should be specified:
1. array (map) name;
2. file name.
Any number of data lines can be specified. Each data line should be ended by the symbol
Example
STORE
PORO OUR_MODEL_PORO.map /
/
Porosity map PORO will be saved into file OUR_MODEL_PORO.map.
Example
STORE
PORO @MODEL_NAME@_PORO.map /
/
Porosity map PORO will be saved into file @MODEL_NAME@_PORO.map. Instead of

@MODEL_NAME@ substring model name will be inserted.
12.3.10. STORE 620

12.3.11 SYSTEM


Section
The keyword allows to run external script (for example, pythons, perls, bashs or C++s
one) during model reading. This way one can generate RP tables by its own formula or
interpolate/smooth some cubes. The following parameters should be specified:
1. line which is interpreted as command line command.
Inside this line users variables can be used. To define users variable the keyword
DEFINES (see 12.1.21) is used. The data should be terminated with a slash /.
Note. For the correct using of SYSTEM for History Matching filename to generate should
depend on MODEL_NAME variable. It allows different model variants to generate different
files.
Example
SYSTEM
'generate_sch.py @MODEL_NAME@ @N_WELLS@'/
...
SCHEDULE
INCLUDE
'@MODEL_NAME@_SCH.inc'/
In the example external python script is used, and python interpreter is containing in
%PATH% variable. The script generates SCHEDULE section by wells number and model
name and saves it to corresponding file. Then this file is included in the model.
12.3.11. SYSTEM 621

12.3.12 INTERPOLATE


Section
The keyword specifies interpolation. The selected interpolation algorithm interpolates pa-
rameter values from source cube to all grid.
This keyword can be used only in the keyword ARITHMETIC (see 12.3.2) in GRID
section.
A source cube with interpolation nodes can be specified via user-defined temporary arrays
ARR (see 12.3.5). The cube has dimensions NX, NY, NZ.
The data is specified the following way:

INTERPOLATE_ML_<ALGORITHM> (SOURCE, NOVALUE, EMPTY_LAYER_VALUE, ...)
Parameters that should be specified first in all interpolation algorithms:

SOURCE cube with values in interpolation nodes and special constant value in other
blocks. These interpolation nodes are source values for interpolation.
A source cube can be prepared via Map Editing in Graphical User Interface or via
BLOCK (see 12.3.9) function in user arithmetic (there is an example in the description
of the keyword BLOCK (see 12.3.9));
NOVALUE the value of special constant;
EMPTY_LAYER_VALUE the value assigned to the layer (at the end of interpolation
process), if the layer contains no interpolation nodes;
<...> algorithms parameters (each algorithm has its own parameters, the description
is below).
It is necessary to specify letter D after algorithm name to use discrete interpolation.
Discrete interpolation can be used with any algorithm. The keyword should has the following
form:
INTERPOLATE_ML_<ALGORITHM>_D (SOURCE, NOVALUE, EMPTY_LAYER_VALUE,
...)
Discrete interpolation can be used to build cubes with integer values (for example, cubes
of PVT-regions). Description of work of discrete interpolation is on the page 626.
Algorithms and parameters (algorithm name is specified instead of <ALGORITHM>).
12.3.12. INTERPOLATE 622

INTERPOLATE_ML_TRIVIAL Trivial. Fills all the blocks where the value is not spec-
ified with the constant.

INTERPOLATE_ML_TRIVIAL (SOURCE, NOVALUE, EMPTY_LAYER_VALUE, ...)
Description of main parameters SOURCE, NOVALUE, EMPTY_LAYER_VALUE is above

(these parameters are common for all interpolation algorithms).
Algorithms own parameters (are specified after main parameters):
1. VALUE_TO_FILL the constant value to fill the blocks.
INTERPOLATE_ML_IDW Inverse Distance Weighting.

INTERPOLATE_ML_IDW (SOURCE, NOVALUE, EMPTY_LAYER_VALUE, ...)

1. POWER_PARAMETER power factor p.
INTERPOLATE_ML_SGS Sequential Gaussian Simulation.

INTERPOLATE_ML_SGS (SOURCE, NOVALUE, EMPTY_LAYER_VALUE, ...)

1. VARIOGRAM_TYPE. One should enter the value, that specifies one of these types:
0 EXPONENTIAL;
1 SPHERICAL;
2 GAUSS;
3 CUBIC;

4 NUGGET_EFFECT;
5 POWER;
6 CAUCHY;
7 Rationally Quadratic (DE_VIJS).
2. VARIOGRAM_RANGE Correlation Radius (range) (METRIC: m, FIELD: f t ).
The distance for which there is a significant correlation between values in these blocks.
Interpolation nodes separated by distances exceeding the radius assigned will be dis-
regarded, interpolation nodes with distances within the radius will be included in the
variogram. If the are a lot of interpolation nodes (in source cube) then this radius can
be reduced if we have not enough interpolation nodes it is better to increase this
radius.
3. VARIOGRAM_SILL Plateau (Sill) (Mean value of the interpolated parameter. Values
of result of interpolation will fluctuate around a given value, so it is best to set a value
that is not far from the mean value).
4. VARIOGRAM_NUGGET_EFFECT non-negative real number; usually 0.
5. VARIOGRAM_AZIMUTH azimuth angle ( ). We need to specify the angle to deter-
mine the XY anisotropy. This angle gives a couple of directions (the direction of this
angle and orthogonal to it). The next two parameters describe the scaling factors in
these areas.
For the isotropic case one should specify 0.
For anisotropic - the required angle.
6. VARIOGRAM_MAIN_AXIS_SCALE Scaling factor in the direction which is given
by azimuth. This parameter is required to set the XY anisotropy XY. This factor is used
to scale the distance.
You must specify a positive real number.
For the isotropic case 1.
For anisotropic the number in the range around 1. For example, between 0.1 and 10.
7. VARIOGRAM_ORTH_AXIS_SCALE Scaling factor in the direction which is given
by the angle orthogonal to azimuth. This parameter is required to set the XY anisotropy
XY. This factor is used to scale the distance.
8. KRIGING_RADIUS Kriging radius (METRIC: m, FIELD: f t ). The radius around
each block for selecting interpolation nodes (the number of Kriging points).
If zero value is specified this parameter is not used.
The smaller the number, the faster the interpolation. However, if the original data
(interpolation nodes) are sparse, and this parameter is small enough, that it can occur
that in some blocks the result value cant be calculated.

9. KRIGING_POINTS the number of Kriging point. A result value in a grid block is

calculated via the existing values in the closest to a given block interpolation nodes.
You should enter an integer number (for example 10, 16).
10. RANDOM_NUMBER any real number (helps to construct different result cubes). This
method adds a Gaussian distribution random seed to the value of each block. The
resulting cube will vary with the random seed: 1, 2, etc. But if the same random
seed is used, the cube corresponding to it is re-created (i. e., there is only one cube
corresponding to each random seed).
INTERPOLATE_ML_KRIGING Kriging.

INTERPOLATE_ML_KRIGING (SOURCE, NOVALUE, EMPTY_LAYER_VALUE, ...)


1. VARIOGRAM_TYPE. One should enter the value, that specifies one of these types:
0 EXPONENTIAL;
1 SPHERICAL;
2 GAUSS;
3 CUBIC;
4 NUGGET_EFFECT;
5 POWER;
6 CAUCHY;
7 Rationally Quadratic (DE_VIJS).
2. VARIOGRAM_RANGE Correlation Radius (range) (METRIC: m, FIELD: f t ).
The distance for which there is a significant correlation between values in these blocks.
Interpolation nodes separated by distances exceeding the radius assigned will be dis-
regarded, interpolation nodes with distances within the radius will be included in the
variogram. If the are a lot of interpolation nodes (in source cube) then this radius can
be reduced if we have not enough interpolation nodes it is better to increase this
radius.
3. VARIOGRAM_SILL variation of interpolated function (non-negative real number).
This is the maximum deviation from the average value. The value with the maximum
deviation may appear at points that are situated far away from the points with defined
values (a distance is greater than the correlation radius of the variogram).

4. VARIOGRAM_NUGGET_EFFECT discontinuous jump at zero point. Non-negative

real number; usually 0.
5. VARIOGRAM_AZIMUTH azimuth angle ( ). We need to specify the angle to deter-

mine the XY anisotropy. This angle gives a couple of directions (the direction of this
angle and orthogonal to it). The next two parameters describe the scaling factors in
these areas.
For the isotropic case one should specify 0.
For anisotropic - the required angle.
6. VARIOGRAM_MAIN_AXIS_SCALE Scaling factor in the direction which is given

by azimuth. This parameter is required to set the XY anisotropy XY. This factor is used
to scale the distance.
7. VARIOGRAM_ORTH_AXIS_SCALE Scaling factor in the direction which is given

by the angle orthogonal to azimuth. This parameter is required to set the XY anisotropy
XY. This factor is used to scale the distance.
8. KRIGING_TYPE. One should enter the value, that specifies one of these types:
0 SIMPLE KRIGING;
1 ORDINARY KRIGING;
2 UNIVERSAL KRIGING.
Description of discrete interpolation.
It is necessary to specify letter D after algorithm name to use discrete interpolation.

Discrete interpolation can be used with any algorithm. The keyword should has the following
form:
INTERPOLATE_ML_<ALGORITHM>_D (SOURCE, NOVALUE, EMPTY_LAYER_VALUE,
...)
Discrete interpolation can be used to build cubes with integer values (for example, cubes
of PVT-regions). If input values are not integers, then they will be rounded to integers.
Let X1 , X2 , ...Xn be possible values of unknown cube K . So, for any block t value of
cube K(t) is one of integers Xi . Also let s1 , s2 , ...sk be blocks with known input data, K(si )
are known values in these blocks. It is required to find values of K for all t .

Example: X is set of different values, which integer cube can be equal. For example, if
cube K is cube of regions, which is equal 1 in the first region, 2 in the next one and 3 in the
third one, then X=1, 2, 3, so that X_1 = 1, X_2 = 2, X_3 = 3.
For all values of Xi additional cube fi is interpolated by standard (not discrete!) method.
They are interpolated by the following input data:

1 if K(s j ) = Xi ,
fi (s j ) =
0 otherwise.
for all j = 1, .., k .

So, n cubes fi are built, where n is the number of possible values of discrete cube.
Every cube fi is built by input values of 0 or 1, but it can be equal to non integer values,
because this cube is built by standard algorithm.
Then the value of cube K at block t is calculating by the following method:
K(t) = Xi , where i is such, that fi (t) is maximal among all i.

So, we need to know Xi which will be set as a value of the discrete cube K at a block
t . We need to find a cube fi in which interpolated value at a block t is maximal. Let it be
fm . Then Xm will be the answer.
The example of building PVT-cube by Kriging with discrete interpolation is on the page
629.
Example 1 of porosity interpolation (construction of PORO cube via IDW algo-

rithm).
Example
GRID
INCLUDE
'ARRPOROSRC.map'/
ARITHMETIC
ARRMYPORO = interpolate_ml_idw (ARRPOROSRC, -999.25, 0.5, 2)
PORO = ARRMYPORO
PORO = min (1, max (0, PORO))
/
1. In this example a file ARRPOROSRC.map is included. In this file in the source points
(interpolation nodes) porosity values are specified, in other points a special constant is
specified -999.25.

2. Then the cube ARRMYPORO (user-defined temporary value) is calculated via IDW
interpolation. Inverse Distance Weighting interpolation (IDW) with power factor 2.
The value 0.5 is assigned to the layer (at the end of interpolation process), if the layer
contains no interpolation nodes.
3. Then porosity cube PORO is set equal to ARRMYPORO.
Example of file ARRPOROSRC.map (there is a keyword ARRPOROSRC at the begin-

ning of the file user-defined temporary array, created via ARR (see 12.3.5)):
Example
ARRPOROSRC
331*-999.25 0.16172062 84*-999.25 0.14223768 308*-999.25
2*0 43*-999.25 0.10645047 3*-999.25 5*0 45*-999.25 5*0 45*-
999.25 6*0 6*-999.25 0.1322713
Example 2 of porosity interpolation (construction of PORO cube via Universal

Kriging algorithm).
Example
GRID
INCLUDE
'ARRPOROSRC.map'/
ARITHMETIC
ARRMYPORO = interpolate_ml_Kriging (ARRPOROSRC, -999.25, 0.5,
0, 20000, 1, 0, 0 , 1, 1, 2)
PORO = min (1, max (0, PORO))
/
In this example, everything is analogously to Example 1 except for the interpola-
tion method. Universal Kriging is used here (KRIGING_TYPE=2), exponential variogram
(VARIOGRAM_TYPE=0).
Example 3 of interpolation in one region, specified by user.

Example
INCLUDE
'ARRMYREG.map'/
INCLUDE
'ARRPOROSRC.map'/
ARITHMETIC
ARRSRC = if (ARRMYREG == 2, ARRPOROSRC, -999.25)
ARRDST = INTERPOLATE_ML_IDW (ARRSRC, -999.25, 0.5, 2)
PORO = if (ARRMYREG == 2, ARRDST, PORO)
PORO = MIN (1, MAX (0, PORO))
/
1. We include a file ARRMYREG.map, that contains a cube of user regions AR-

RMYREG. They are specified via the keyword ARRMYREG (user temporary ar-
rays ARR (see 12.3.5)) analogously to regions SATNUM (see 12.4.3), FIPNUM (see
12.4.10) etc.
We want to interpolate porosity only in one of these regions. For all other regions we
want to remain unchanged the values of initial PORO (see 12.2.24) cube.
2. Then a file ARRPOROSRC.map is included. In this file in the source points (interpola-
tion nodes) porosity values are specified, in other points a special constant is specified
-999.25.
3. Input data is cut to the region. ARRPOROSRC only remains unchanged the values
in the blocks that belong to 2-nd region ARRMYREG. In all other blocks - special
constant -999.25.
4. Then IDW interpolation takes place. The result is user-defined temporary array AR-
RDST. Inverse Distance Weighting interpolation (IDW) with power factor 2. The value
0.5 is assigned to the layer (at the end of interpolation process), if the layer contains
no interpolation nodes.
5. Then porosity cube PORO is set equal to ARRDST in blocks that belong to the 2-
nd region ARRMYREG. In other blocks the values of source porosity cube remain
unchanged.
Example 4 of using interpolation (building PVT-cube by Kriging with discrete in-

terpolation ).

Example
INCLUDE
'ARRPVTSRC.map '/
ARRMYPVT = interpolate_ml_kriging_d (ARRPVTSRC, -999.25, 1,

0, 20000, 1, 0, 0 , 1, 1, 2)
PVTNUM = ARRMYPVT
In the example a cube of PVT-regions is built by universal Kriging with discrete interpo-
lation. File ARRPVTSRC.map contains input data.

12.3.13 MULTIPLY


Section
This keyword is used to multiply grid properties by a constant in current box. It should
be followed by grid parameter to be modified, non-negative constant and current box. Box is
specified similarly to BOX (see 12.3.3). If it is not specified than last defined box will be
used.
Each line should be terminated with a slash /. The data should be terminated with a final
slash /.
Example
DIMENS
10 10 50
/
...
MULTIPLY
PERMX 1.5 5 10 5 10 20 30 /
PERMY 2.0 /
PERMZ 10 /
/
In this example multipliers for parameters PERMX, PERMY, PERMZ of cells in 6x6x11
box are set. Box is specified once.
12.3.13. MULTIPLY 631

12.3.14 MULTIREG


Section
This keyword is used to multiply grid properties by a constant in a specific region.

The regions must previously have been defined using keyword MULTNUM (see 12.4.23),
OPERNUM (see 12.4.22) or FLUXNUM (see 12.4.18).
An arbitrary number of lines could be specified. Each line should be terminated with a
slash /. The data should be terminated with a final slash /.
Each line consists of the following data:
1. the name of the array to be modified;
2. the constant by which the array, specified by parameter 1, is to be multiplied (non-
negative);
3. the region number (MULTNUM (see 12.4.23), OPERNUM (see 12.4.22) or FLUXNUM
(see 12.4.18)) (region is specified via parameter 4);
4. region M (MULTNUM (see 12.4.23)), O (OPERNUM (see 12.4.22)), F (FLUXNUM
(see 12.4.18)).
Default: region M.
Example
DIMENS
5 3 2
/
...
MULTNUM
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
/
...
MULTIREG
PERMX 1.5 1 /
PERMX 2 2 /
PERMX 10 3 /
PERMX 0.7 4 /
/
In this example multiplier for parameter PERMX is set for each of four regions.
12.3.14. MULTIREG 632

12.3.15 MULTREGP


Section
This keyword specifies pore volume multiplier for a specific region. The regions must
previously have been defined using keyword MULTNUM (see 12.4.23) or FLUXNUM (see
12.4.18). This keyword can be used in EDIT section if the keyword PORV (see 12.2.27) is
set. An arbitrary number of lines could be specified. Each line should be terminated with a
Each line consists of the following data:
1. region number;
2. pore volume multiplier for this region;
3. array of region. Possible values and logic of evaluations of them are described below.
In different versions of Eclipse simulator this keyword has different workflow logic. The
first parameter of the keyword TNAVCTRL (see 12.1.4) is used to switch it. Lets define 3
values to describe workflow logic in different Eclipse versions:
gridopts_reg 2-nd parameter of the keyword GRIDOPTS (see 12.1.87) (it response
for the number of MULTNUM (see 12.4.23) regions);
regdims4_reg 4-th parameter of the keyword REGDIMS (see 12.1.29) (it response
for the number of FLUXNUM (see 12.4.18) regions);
regdims7_reg 7-th parameter of the keyword REGDIMS (see 12.1.29) (it response
for the number of OPERNUM (see 12.4.22) regions);
New workflow logic (logic in Eclipse 2012-2014 versions.). E100 models.
Parameter array of region can be the following:

M MULTNUM (see 12.4.23) is using. If MULTNUM (see 12.4.23) is not defined,
then multiplier doesnt applied. Otherwise, any region number can be specified, but it
should be less or equal to max gridopts_reg, regdims4_reg, regdims7_reg. That is, one
can use the greater number of regions than it is specified in GRIDOPTS (see 12.1.87).
F FLUXNUM (see 12.4.18) is using. If FLUXNUM (see 12.4.18) is not defined or
regdims4_reg is 0, then multiplier doesnt applied. Otherwise, region number should
be less or equal to max gridopts_reg, regdims4_reg, regdims7_reg, where gridopts_reg
is accounted only if MULTNUM (see 12.4.23) is defined in the model. That is, one can
use the greater number of regions than it is specified in REGDIMS (see 12.1.29).
12.3.15. MULTREGP 633

O OPERNUM (see 12.4.22) is using. If OPERNUM (see 12.4.22) is not defined or

regdims7_reg is 0, then multiplier doesnt applied. Otherwise, region number should
be less or equal to max gridopts_reg, regdims4_reg, regdims7_reg, where gridopts_reg
is accounted only if MULTNUM (see 12.4.23) is defined in the model. That is, one can
use the greater number of regions than it is specified in REGDIMS (see 12.1.29).
Default:
array of region:
if gridopts_reg is not 0 and MULTNUM (see 12.4.23) is defined, then M is used
by default.
if regdims4_reg is not 0 and FLUXNUM (see 12.4.18) is defined, then F is used
by default.
if regdims4_reg is not 0, then O is used by default.
Case of E300 models. Lets define another parameter: tabdims11 11-th parameter of
the keyword TABDIMS (see 12.1.26).
Then the value of the 3-rd parameter defines the following:
M: MULTNUM (see 12.4.23) is using. If MULTNUM (see 12.4.23) is not defined, then
multiplier doesnt applied.
If gridopts_reg is not 0, then region number should be less or equal to gridopts_reg.
If gridopts_reg is 0, then region number should be less or equal to max (tabdims11,
regdims4_reg).
F: FLUXNUM (see 12.4.18) is using. If FLUXNUM (see 12.4.18) is not defined, then
multiplier doesnt applied. Otherwise, region number should be less or equal to max
(tabdims11, gridopts_reg, regdims4_reg, regdims7_reg).
O: OPERNUM (see 12.4.22) is using. If OPERNUM (see 12.4.22) is not defined, then
multiplier doesnt applied. Otherwise, region number should be less or equal to max
(tabdims11, gridopts_reg, regdims4_reg, regdims7_reg).
Default:
array of region: M.
Old logic (logic in Eclipse 2012 and earlier versions.)
The key point is that using region is not always equal to the specified one. If several data
lines are used, then one array is used to apply. Example:
Example
MULTREGP
2 2 M /
2 3 F / we use MULTNUM here
/
12.3.15. MULTREGP 634

Evaluation of final region has several stages:
1. lets define count_multregp_regions value.
if gridopts_reg > 0 and MULTNUM is set, then count_multregp_regions is gri-

dopts_reg;
if regdims4_reg > 0 and FLUXNUM is set, then count_multregp_regions is
regdims4_reg;
In other cases count_multregp_regions is 0.
2. Searching for preliminary region to apply.
if regdims7_reg > 0 and OPERNUM (see 12.4.22) is set, then OPERNUM (see
12.4.22) is using.
if gridopts_reg > 0 and MULTNUM (see 12.4.23) is set, then MULTNUM (see
12.4.23) is using.
if regdims4_reg > 0 and FLUXNUM (see 12.4.18) is set, then FLUXNUM (see
12.4.18) is using.
3. Searching for pre-final region. It is defined by the third parameter of the first data line
of the keyword MULTREGP (see 12.3.15).
if M default value, then pre-final region is MULTNUM (see 12.4.23);

if F, then pre-final region is FLUXNUM (see 12.4.18);
if O, then pre-final region is OPERNUM (see 12.4.22).
4. Evaluation of final region.
if preliminary region is OPERNUM, then final one is pre-final one.

if preliminary region is MULTNUM, then:
if pre-final one is FLUXNUM, then final one is FLUXNUM,
otherwise, final one is MULTNUM.
In other cases final region is FLUXNUM. The number of specified region should be
less then count_multregp_regions (regdims7_reg for OPERNUM) to apply multiplier.
5. if final region is MULTNUM, but it is not defined, then FLUXNUM will be used.
12.3.15. MULTREGP 635

Example
DIMENS
5 3 2
/
...
MULTNUM
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
/
...
MULTREGP
1 1.5 /
2 2.0 /
3 0.0 /
4 0.5 /
/
In this example pore volume multiplier is set for each of four regions.
12.3.15. MULTREGP 636

12.3.16 COPY


Section
The keyword is used to copy data from one property array to another in current box. It
should be followed by property array from which data is to be copied, than property array to
which data is to be copied and input box. Box is specified similarly to BOX (see 12.3.3).
If it is not specified than last defined box will be used. There may be any number of
records, each of which is terminated by a slash /.
Example
DIMENS
10 10 50
/
...
BOX
5 10 5 10 20 30
/
...
COPY
MULTX MULTY /
MULTX MULTZ /
/
In this example values MULTY and MULTZ are set to MULTX in each cell in 5x5x10 box.
12.3.16. COPY 637

12.3.17 COPYBOX


Section
The keyword is used to copy grid property data from one input box to another. It should
be followed by property array to be modified, box from which data is to be copied, than box
to which data is to be copied. Box is specified similarly to BOX (see 12.3.3).
There may be any number of records, each of which is terminated by a slash /.
Example
DIMENS
10 10 50
/
...
COPYBOX
MULTX 1 5 1 5 10 20 6 10 6 10 10 20 /
DY 2 4 1 5 1 10 2 4 1 5 10 20 /
/
In this example MULTX and DY data is copied from one input box to another.
12.3.17. COPYBOX 638

12.3.18 COPYREG


Section
The keyword is used to copy data from one property array to another in a specific region.
OPERNUM (see 12.4.22) or FLUXNUM (see 12.4.18). The data should be terminated with
a slash /.
1. property array from which data is to be copied;
2. property array to which data is to be copied;
3. region number (the possible regions are specified via keywords - MULTNUM (see
12.4.23), OPERNUM (see 12.4.22), FLUXNUM (see 12.4.18));
4. region (M MULTNUM (see 12.4.23), O OPERNUM (see 12.4.22), F FLUXNUM

(see 12.4.18)).
Default: region MULTNUM (see 12.4.23).
Example
DIMENS
5 3 2
/
...
MULTNUM
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
/
...
COPYREG
MULTX MULTY 2
/
In this example MULTY data is set to MULTX one in each cell of second region.
12.3.18. COPYREG 639

12.3.19 EQUALREG


Section
The keyword is used to set property array to a constant value in a specific region. The
regions must previously have been defined using keyword MULTNUM (see 12.4.23), OPER-
NUM (see 12.4.22) or FLUXNUM (see 12.4.18). The data should be terminated with a slash
/.

1. property array to which constant value is to be set;
2. constant value;
3. region number (the possible regions are specified via keywords - MULTNUM (see
12.4.23), OPERNUM (see 12.4.22), FLUXNUM (see 12.4.18));
4. region (M MULTNUM (see 12.4.23), O OPERNUM (see 12.4.22), F FLUXNUM
(see 12.4.18)).
Default: region MULTNUM (see 12.4.23).
Example
DIMENS
5 3 2
/
...
FLUXNUM
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
/
...
EQUALREG
PORO 0.15 1 F/
PORO 0.12 2 F/
PORO 0.08 3 F/
PORO 0.25 4 F/
/
In this example porosity is assigned to different constant values in four regions FLUXNUM
(see 12.4.18) (0.15 in 1-st region, 0.12 in 2-nd region, 0.08 in 3-rd region, 0.25 in
4-th region).
12.3.19. EQUALREG 640

12.3.20 ADD


Section
This keyword is used to add a constant to grid property array in current box. It should
be followed by grid parameter to be modified, a constant and current box. Box is specified
similarly to BOX (see 12.3.3). If it is not specified than last defined box will be used.
Example
DIMENS
10 10 50
/
...
ADD
PERMX 10.5 5 10 5 10 20 30 /
PERMY 20.3 /
PERMZ 10 /
/
In this example adding constants for parameters PERMX, PERMY, PERMZ of cells in
5x5x10 box are set.
12.3.20. ADD 641

12.3.21 ADDREG


Section
This keyword is used to add a constant to grid property array in a specific region.
OPERNUM (see 12.4.22) or FLUXNUM (see 12.4.18). The keyword should be followed by
grid parameter to be modified, a constant and a region number.
Example
DIMENS
4 3 2
/
...
FLUXNUM
2 2 2 2 2 1 1 1 1 1 3 3
2 2 2 2 2 1 1 1 1 1 3 3
/
...
ADDREG
PERMX 10.5 1 /
SATNUM 1 3 /
/
In this example a constant 10.5 is added to PERMX data in each cell of first region, and
a constant 1 is added to SATNUM data in each cell of third region.
12.3.21. ADDREG 642

12.3.22 EQUALS


Section
This keyword is used to set grid property array in current box to a constant.
One row contains the following parameters:
name of grid parameter to be modified,
a value of parameter
parameters [3-8] current box. Box is specified similarly to BOX (see 12.3.3).
If the box is not specified than last defined box will be used. If no one box was previously
defined then all reservoir will be taken.
There can be an arbitrary number of records, each terminated by a slash /. All data
Example
DIMENS
10 10 50
/
...
EQUALS
DX 100 5 10 5 10 20 30 /
DY 100 /
DZ 5 /
/
In this example for each cell in 5x5x10 box dimensions are set to 100x100x5.
12.3.22. EQUALS 643

12.3.23 MAXVALUE


Section
This keyword is used to set a maximum limit to grid property array in current box. It
should be followed by grid parameter to be modified, a maximum value and current box.
Box is specified similarly to BOX (see 12.3.3). If it is not specified than last defined box
will be used.
Example
DIMENS
10 10 50
/
...
MAXVALUE
SGU 0.85 5 10 5 10 20 30 /
SWU 0.75 /
/
In this example for each cell in 5x5x10 box maximum limit of gas saturation is set to
0.85 and maximum limit of water saturation is set to 0.75.
12.3.23. MAXVALUE 644

12.3.24 MINVALUE


Section
This keyword is used to set a minimum limit to grid property array in current box. It
should be followed by grid parameter to be modified, a maximum value and current box.
Box is specified similarly to BOX (see 12.3.3). If it is not specified than last defined box
will be used.
Example
DIMENS
10 10 50
/
...
MINVALUE
SGU 0.45 5 10 5 10 20 30 /
SWU 0.55 /
/
In this example for each cell in 5x5x10 box minimum limit of gas saturation is set to
0.45 and minimum limit of water saturation is set to 0.55.
12.3.24. MINVALUE 645

12.3.25 OPERATE


Section
This keyword is used to specify arithmetic operations on grid property arrays in current
box. Input parameters:
grid property array to be modified,
input box to be modified, it is specified similarly to BOX (see 12.3.3),
operation, possible operations are represented in table below:
Result Operation Argument First parameter Second parameter

Ri = aXi + b MULTA X a b
Ri = Ri + aXib POLY X a b
Ri = 10(a+bXi ) SLOG X a b
Ri = log 10(Xi ) LOG10 X - -
Ri = ln(Xi ) LOGE X - -
Ri = X1i INV X - -
Ri = aXi MULTX X a -
Ri = a + Xi ADDX X a -
Ri = Xi COPY X - -
Ri = max(a, Xi ) MAXLIM X a -
Ri = min(a, Xi ) MINLIM X a -
Ri = aXib MULTP X a b
Ri = abs(Xi ) ABS X - -
Ri = Xi Ri MULTIPLY X - -
grid property array as argument,
first scalar parameter, if required,
second scalar parameter, if required.
Also arbitrary user arrays can be used in this keyword:
WORK (12.3.6) array of real numbers,
IWORK (12.3.6) array of integer numbers.
12.3.25. OPERATE 646

Example
DIMENS
10 10 50
/
...
OPERATE
MULTY 4 5 4 5 1 15 COPY MULTX
/
In this example MULTX data is copied to MULTY one in each cell in 2x2x15 box.
12.3.25. OPERATE 647

12.3.26 OPERATER


Section
This keyword is used to specify arithmetic operations on grid property arrays in a spe-
cific region. The regions must previously have been defined using keyword OPERNUM (see
12.4.22).
Input parameters:
grid property array to be modified,
input box to be modified, it is specified similarly to BOX (see 12.3.3),
operation, possible operations are represented in table below:
Result Operation Argument First parameter Second parameter

Ri = aXi + b MULTA X a b
Ri = Ri + aXib POLY X a b
Ri = 10(a+bXi ) SLOG X a b
Ri = log 10(Xi ) LOG10 X - -
Ri = ln(Xi ) LOGE X - -
Ri = X1i INV X - -
Ri = aXi MULTX X a -
Ri = a + Xi ADDX X a -
Ri = Xi COPY X - -
Ri = max(a, Xi ) MAXLIM X a -
Ri = min(a, Xi ) MINLIM X a -
Ri = aXib MULTP X a b
Ri = abs(Xi ) ABS X - -
Ri = Xi Ri MULTIPLY X - -
grid property array as argument,
first scalar parameter, if required,
second scalar parameter, if required.
12.3.26. OPERATER 648

Example
DIMENS
5 3 1
/
...
OPERNUM
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
/
...
OPERATER
MULTY 2 COPY MULTX
/
In this example MULTX data is copied to MULTY one in each cell of second region.
12.3.26. OPERATER 649

12.3.27 DEPTH


Section
The keyword is used to specify the depth of the center of the grid block (METRIC: m,
FIELD: f t ). The keyword should be followed by one non-negative real number for every
grid block.
Default: none.
Example
DIMENS
3 4 2
/
...
DEPTH
2301.98 2303.87 2305.78 2306.86 2303.06 2301.29
2297.36 2297.32 2294.87 2293.37 2293.87 2293.40
2303.12 2302.26 2300.51 2300.07 2294.68 2288.54
2238.09 2238.09 2238.09 2238.09 2301.15 2302.94
/
This example sets depths of the center of the blocks for the grid 3x4x2.
12.3.27. DEPTH 650

12.4. Region section tNavigator-4.2
12.4 Region section

This section allows to define regions with different properties. It is also possible to define
regions for reserves calculation and regions with different initial conditions (EQUIL (see
12.15.2)).
Region numbers cannon exceed those ones defined by TABDIMS (see 12.1.26) and
EQLDIMS (see 12.1.27).
12.4. Region section 651

12.4.1 REGIONS


Section
x REGIONS SOLUTION SUMMARY SCHEDULE
The keyword specifies the beginning of data section which contains regions data.
12.4.1. REGIONS 652

12.4.2 PVTNUM


Section
The keyword should be followed by one integer for every grid block specifying the PVT
region to which it belongs. The region number should not be less than 1 or greater than the
second number specified in keyword TABDIMS (see 12.1.26).
For each PVT region all its PVT properties must be specified, see keywords PVDO
(see 12.5.2), PVTO (see 12.5.4), PVTW (see 12.5.5), PVDG (see 12.5.7), PVTG (see
12.5.8), ROCK (see 12.5.16), DENSITY (see 12.5.23), SALTTRM (see 12.7.5), SALTPROP
(see 12.7.4).
Default: 1
Example
DIMENS
5 3 2
/
...
TABDIMS
2 3 2* 4
/
...
PVTNUM
1 1 1 1 1 2 2 2 2 2 3 2 3 3 3
1 1 1 1 1 2 2 2 2 2 3 2 3 3 3
/
This example defines disposition of three PVT-regions with different PVT properties for
a 5x3x2 grid. Note that TABDIMS specifies that there can be 3 regions with different PVT
properties.
12.4.2. PVTNUM 653

12.4.3 SATNUM


Section
The keyword should be followed by one integer for every grid block specifying the satu-
ration function region to which it belongs. The data should be terminated with a slash /.
The region number should not be less than 1 or greater than the first number specified in
TABDIMS (see 12.1.26).
For each saturation function region its relative permeability curves should be specified,
see keywords SWOF (see 12.6.1), SGOF (see 12.6.2), SLGOF (see 12.6.11).
Default: 1
Example
DIMENS
5 3 2
/
...
TABDIMS
2 3 2* 4
/
...
SATNUM
2 2 2 2 2 1 1 1 1 1 2 2 1 1 1
2 2 2 2 2 1 1 1 1 1 2 2 1 1 1
/
This example defines disposition of two flow regions with different PVT properties for
a 5x3x2 grid. Note that TABDIMS specifies that there can be 2 regions with different flow
parameters (relative permeabilities).
12.4.3. SATNUM 654

12.4.4 SURFNUM


Section
The keyword sets the number for every grid block specifying the miscible (high sur-
factant) saturation function region to which it belongs (if is used in models with surfactant
injection section 2.25 when oil and water are miscible at high surfactant concentration).
The region number should not be less than 1 or greater than the first parameter of TAB-
DIMS (see 12.1.26).
The keyword SATNUM (see 12.4.3) defines the immiscibile saturation region numbers
(saturatin functions are specified vian SWFN (see 12.6.13), SOF2 (see 12.6.12), SOF3 (see
12.6.15), SWOF (see 12.6.1)).
Example
SATNUM
55440*1
/
SURFNUM
55440*2 /
In this example all blocks are in the 1-st region for immiscibile case (SATNUM (see
12.4.3)) and they belong to the 2-nd region in case of miscible conditions (SURFNUM (see
12.4.4)).
12.4.4. SURFNUM 655

12.4.5 SURFWNUM


Section
The keyword sets the number for every grid block specifying the saturation function re-
gion to which it belongs for water-wettability case (is used in models with surfactant injection
section 2.25).
DIMS (see 12.1.26).
The keyword SATNUM (see 12.4.3) specifies saturation function regions for oil-
wettability case. For each saturation function region its relative permeability curves should
be specified, see keywords (properties are specified via SWFN (see 12.6.13), SOF2 (see
12.6.12), SOF3 (see 12.6.15), SWOF (see 12.6.1)), also these keywords specify additional
saturation functions which are used for water-wettability case.
The keyword SURFWNUM (see 12.4.5) sets the number for every grid block specifying
the saturation function region to which it belongs for waterwettability case.
Example
SATNUM
55440*1
/
SURFWNUM
55440*2 /
In this example all blocks belong to region 1 in oil-wettability case (SATNUM (see
12.4.3)) and belong to region 2 in water-wettability case (SURFWNUM (see 12.4.5)).
12.4.5. SURFWNUM 656

12.4.6 LWSLTNUM / LSNUM


Section
The keyword sets the number for every grid block specifying the low-salinity saturation
function region to which it belongs (is used in the low salinity option section 2.26.3).
Option is activated via the keyword LOWSALT (see 12.1.59).
DIMS (see 12.1.26).
The keyword SATNUM (see 12.4.3) specifies saturation function regions for high salinity.
Properties for regions SATNUM (see 12.4.3) and LWSLTNUM (see 12.4.6) are specified via
SWFN (see 12.6.13), SOF2 (see 12.6.12), SOF3 (see 12.6.15), SWOF (see 12.6.1) etc
Example
SATNUM
55440*1
/
LWSLTNUM
55440*2 /
In this example all blocks belong to region 1 high salinity case (SATNUM (see 12.4.3))
and belong to region 2 in low salinity case (LWSLTNUM (see 12.4.6)).
12.4.6. LWSLTNUM / LSNUM 657

12.4.7 IMBNUM

RUNSPEC GRID EDIT x PROPS

Section
This keyword is used for relative permeabilities hysteresis 2.6.11 (option HYSTER of
the keyword SATOPTS (see 12.1.68)).
The keyword specifies which saturation table is to be used for each grid block for imbi-
bition processes (defined via SWOF (see 12.6.1), SGOF (see 12.6.2), SLGOF (see 12.6.11)
etc.). For drainage processes and equilibration usual saturation table numbers are used (spec-
ified via SATNUM (see 12.4.3)).
The keyword should be followed by one integer for every grid block. The data should be
Directional and irreversible relative permeabilities can be used for imbibition.

These keywords can be used if corresponding options are specified in the keyword
SATOPTS (see 12.1.68):

for flow direction from I to I-1 ot from I to I+1. (in this case DIRECT must also
(see 12.4.7) and IMBNUMZ- (see 12.4.7);
HYSTER hysteresis relative permeabilities 2.6.11.
Default: region number, specified via IMBNUM (see 12.4.7).
12.4.7. IMBNUM 658

Example
SATNUM
46000*1/
...
IMBNUM
23000*2 23000*3/
In this example for all 46000 model grid blocks 1-st saturation region SATNUM is defined
(will be used for drainage processes). For first 23000 grid blocks 2-nd saturation function
region is specified (for imbibition processes in these blocks), for next 23000 blocks 3-rd
saturation function region is specified (for imbibition processes in these blocks).
Example
SATOPTS
DIRECT IRREVERS HYSTER/
...
IMBNUMX
4000*2 /
IMBNUMX-
4000*3 /
In this example imbibition saturation table number for X+ face for 4000 grid blocks is
2, imbibition saturation table number for X- face 3.
12.4.7. IMBNUM 659

12.4.8 MISCNUM


Section
This keywords specifies the miscibility region number for each gris block 2.6.12.
The keyword should be followed by one integer for every grid block. The data should be
Default: 1.
Example
MISCNUM
23000*2 23000*3/
For first 23000 grid blocks 2-nd miscibility region is specified, for next 23000 blocks
3-rd miscibility region is specified.
12.4.8. MISCNUM 660

12.4.9 EQLNUM


Section
The keyword should be followed by one integer for every grid block specifying the
equilibrium region to which it belongs. The region number should not be less than 1 or
greater than the third number specified in EQLDIMS (see 12.1.27).
For each equilibrium region its initial conditions must be specified (EQUIL (see 12.15.2)).
Note: For each equilibrium region grid blocks from this region should not have different
numbers of PVT regions (PVTNUM (see 12.4.2)) and should not have different numbers of
saturation regions (SATNUM (see 12.4.3)).
Default: 1
Example
DIMENS
5 3 2
/
...
EQLDIMS
2
/
...
EQLNUM
2 2 2 2 2 1 1 1 1 1 2 2 1 1 1
2 2 2 2 2 1 1 1 1 1 2 2 1 1 1
/
This example defines disposition of two equilibration regions for a 5x3x2 grid. Note that
EQLDIMS specifies that there can be 2 equilibration regions.
12.4.9. EQLNUM 661

12.4.10 FIPNUM


Section
The keyword should be followed by one integer for every grid block specifying the fluid-
in-place region to which it belongs. The region number should not be less than 1 or greater
than the fifth number specified in TABDIMS (see 12.1.26).
For each fluid-in-place region summary information on reserves is calculated and is
written down to log file unless other requirements are specified in REPORTFILE (see 12.1.3).
Default: 1
Example
DIMENS
5 3 2
/
...
TABDIMS
3 2 2* 4
/
...
FIPNUM
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
/
This example defines disposition of four fluid-in-place regions for a 5x3x2 grid. Note that
TABDIMS specifies that it is possible to define up to 4 fluid-in-place regions.
12.4.10. FIPNUM 662

12.4.11 FIP


Section
The keyword specifies additional sets of fluid-in-place regions. (One can create sets of
fluid-in-place regions different from standard FIPNUM (see 12.4.10) regions).
The name of this keyword should contain two parts:

FIP
1-3 symbols (English letters and numbers can be used)
This sequence of symbols specifies the name of one set of fluid-in-place regions.
The keyword should be followed by one integer for every grid block specifying the fluid-
in-place region to which it belongs. The number of given integers should be equal to the
number of blocks.
You can specify an arbitrary number of sets of fluid-in-place regions (but not greater than
the second parameter of the keyword REGDIMS (see 12.1.29)).
For each fluid-in-place region summary information on reserves is calculated and is
written down to log file unless other requirements are specified in REPORTFILE (see 12.1.3).
Example
DIMENS
3 3 2
/
...
REGDIMS
3 2
/
...
FIP1
1 1 1 1 2 2 3 3 3 1 1 1 1 2 2 3 3 3
/
This example defines a set FIP1 of three fluid-in-place regions for 3x3x2 grid. Note that
REGDIMS specifies that it is possible to define up to 2 sets of fluid-in-place regions (2-nd
parameter of REGDIMS), the number of fluid-in-place regions in one set can be up to 3 (1-th
parameter of REGDIMS).
12.4.11. FIP 663

Example
DIMENS
25 25 3
/
...
REGDIMS
3 3
/
...
FIPMA1
1000*1 400*2 475*3
/
FIPMA2
875*1 1000*2
/
This example defines two sets FIPMA1 and FIPMA2 of fluid-in-place regions for 25x25x3
grid. FIPMA1 consists of three fluid-in-place regions, FIPMA2 of two.
Note that REGDIMS specifies that it is possible to define up to 3 sets of fluid-in-place
regions (2-nd parameter of REGDIMS), the number of fluid-in-place regions in one set can
be up to 3 (1-th parameter of REGDIMS).
12.4.11. FIP 664

12.4.12 FIPOWG


Section
The keyword specifies an additional set of fluid-in-place (FIP) regions. These FIP regions
will be created automatically. They represent initial gas, oil and water regions according to
WOC (water-oil contact) and GOC (gas-oil contact) depth, specified via the keyword EQUIL
(see 12.15.2).
Standard FIP regions FIPNUM (see 12.4.10), user FIP regions FIP (see 12.4.11).
Free FIP regions will be created:
Gas region (consists of all blocks which are above GOC, specified via 5-th parameter
of EQUIL (see 12.15.2));
Oil region (consists of all blocks which are betwen WOC and GOC);
Water region (consists of all blocks which are below WOC, specified via 3-th parameter
of EQUIL (see 12.15.2)).
Example
FIPOWG
12.4.12. FIPOWG 665

12.4.13 FIPPATT


Section
This keyword specifies the number for each block the number of splitted region to
which this block will belong when splitting is done.
Splitting is described in section 5.14 (in tNavigator approach to splitting is different from
Eclipse).
This keyword specifies the number for each block the number of splitted region to
which this block will belong when splitting is done. Amount of these numbers must be equal
to the number of blocks. The data should be terminated with a slash /.
Example
DIMENS
5 3 2
/
...
FIPPATT
2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
/
In this example for the grid size of 5x3x2 two splitted region are set.
12.4.13. FIPPATT 666

12.4.14 ROCKNUM


Section
x REGIONS SOLUTION SUMMARY x SCHEDULE
number of rock region - transmissibility dependence on pressure table - to which it belongs.
(Tables for each rock region are specifying using the keyword ROCKTAB (see 12.5.18)).
The table number should not be less or equal the second parameter of ROCKCOMP (see
12.1.34).
Example
DIMENS
5 3 2
/
...
ROCKCOMP
IRREVERS 4 /
...
ROCKNUM
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
/
This example defines disposition of four rock regions for 5x3x2 grid. Note that ROCK-
NUM specifies that it is possible to define up to 4 rock regions.
12.4.14. ROCKNUM 667

12.4.15 COALNUM


Section
The keyword should be followed by one integer for every matrix block specifying the
number of Coal Bed Methane region, to which it belongs 2.29.
For each region the following keywords are specified: LANGMUIR (see 12.9.2)) or
LANGMEXT (see 12.9.4).
Amount of the numbers should be equal to the number of matrix blocks. The region num-
ber should not be less or equal the 6-th parameter of the keyword REGDIMS (see 12.1.29).
Zero value sets that there is no coal in this block.
Example
COALNUM
1200*1
1200*2 /
In this example 2 Coal Bed Methane regions are specified.
12.4.15. COALNUM 668

12.4.16 PMANUM


Section
The keyword should be followed by one integer for every grid block specifying the pres-
sure maintenance region to which it belongs. The data should be terminated with a slash /.
Pressure maintenance regions can be used in the GPMAINT (see 12.18.76) keyword.
Default: 1.
Example
PMANUM
400*1 400*2 400*3 /
12.4.16. PMANUM 669

12.4.17 ENDNUM


Section
The keyword should be followed by one integer for every grid block, specifying the end
point scaling versus depth table region to which it belongs. The region number specifies
which end point scaling versus depth table (input using ENPTVD (see 12.6.38), ENKRVD
(see 12.6.39)) should be used to calculate the saturation table end points for each grid block.
Table number should not be greater than 3-rd parameter of the keyword ENDSCALE
(see 12.6.24). The end point scaling option should be activated by specifying keyword END-
SCALE (see 12.6.24). The same number of numbers should be entered as the number of
grid blocks. The data should be terminated with a slash /.
Example
DIMENS
20 20 3
/
...
ENDSCALE
2* 3 1*
/
...
ENDNUM
400*1 400*2 400*3/
In this example (the grid 20x20x3) for all grid blocks the end point scaling versus depth
table region is specified: 1 400 grid blocks, 2 next 400 grid blocks, 3 nest 400 grid
blocks.
12.4.17. ENDNUM 670

12.4.18 FLUXNUM


Section
The keyword should be followed by one integer for every grid block specifying the flux
region to which it belongs. The region number should not be less than 1 or greater than the
forth number specified in REGDIMS (see 12.1.29).
splitting is different from Eclipse. Splitting is described in section 5.14.
For each flux region grid property array operations may be specified further, see keywords
ADDREG (see 12.3.21), COPYREG (see 12.3.18), MULTIREG (see 12.3.14), MULTREGP
(see 12.3.15).
Default: 1
Example
DIMENS
5 3 2
/
...
REGDIMS
2 2 0 4
/
...
FLUXNUM
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
/
This example defines disposition of four flux regions for a 5x3x2 grid. Note that
REGDIMS specifies that it is possible to define up to 4 flux regions.
12.4.18. FLUXNUM 671

12.4.19 BNDNUM


Section
This keyword is used to specify type of boundary condition on vertical boundary surface
for all cells. The number of values should be equal to number of cells. Values should be
integer numbers. 1 is for Dirichlet boundary condition (constant pressure), 2 is for Neumann
boundary condition (non flow). Simulator uses only values in cells located on the boundary. If
Dirichlet boundary condition is specified the simulator get pressure from the initial pressure
(PRESSURE (see 12.15.8)).
Default: 2 in all cells
Example
DIMENS
5 5 4
/
...
BNDNUM
100*2
/
In this example Neumann boundary condition is specified in all cells on the boundary.
12.4.19. BNDNUM 672

12.4.20 VISCNUM


Section
The keyword can only be used if THERMAL (see 12.1.50) is present.

The keyword should be followed by one integer for every grid block specifying the viscosity
region number to which it belongs. The region number should not be greater than the second
parameter of TABDIMS (see 12.1.26). (The maximum number of viscosity regions is equal
to the maximum number of PVT regions).
Default:
In stars data format all blocks belong to the same viscosity region.
In e300 data format viscosity regions coincide with PVT regions (PVTNUM (see 12.4.2)).
Example
DIMENS
5 3 2
/
...
TABDIMS
3 4 2*
/
...
VISCNUM
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
/
This example specifies four viscosity regions for the grid 5x3x2. Note that TABDIMS
specifies that it is possible to define up to 4 viscosity regions.
12.4.20. VISCNUM 673

12.4.21 EOSNUM


Section
equation of state region (EoS region) to which it belongs. The region number should not be
less than 1 or greater than the 9-th parameter of TABDIMS (see 12.1.26). The data should
Default: All grid blocks belong to the same region.
Example
DIMENS
5 3 2
/
...
EOSNUM
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
/
This example defines disposition of four equation of state regions for a 5x3x2 grid.
12.4.21. EOSNUM 674

12.4.22 OPERNUM


Section
performing arithmetic operations region to which it belongs.
For each performing arithmetic region grid property array operations may be specified
further with keyword OPERATER (12.3.26).
Default: 1
Example
DIMENS
5 3 2
/
...
OPERNUM
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
/
This example defines disposition of four performing arithmetic operations regions for a
5x3x2 grid.
12.4.22. OPERNUM 675

12.4.23 MULTNUM


Section
The keyword should be followed by one integer for every grid block specifying the region
of applying multipliers to which it belongs.
For each region of applying multipliers pore volume multipliers may be specified further
with keyword MULTREGP (see 12.3.15).
Default: 1
Example
DIMENS
5 3 2
/
...
MULTNUM
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
/
This example defines disposition of four regions of applying multipliers for a 5x3x2 grid.
12.4.23. MULTNUM 676

12.4.24 KRNUM


Section
This keyword specifies the number of saturation region for each grid block in case of
directional and irreversible phase permeabilities.
One integer number should be entered for each grid block. The data should be terminated
with a slash /.
Saturation region number specifies which saturation fuction table will be used to calculate
relative permeabilities for flow through six block faces X+, X-, Y+, Y-, Z+, Z-. Saturation
tables are specified via keywords SWOF (see 12.6.1), SGOF (see 12.6.2) etc.
These keywords can be used if the corresponding options are specified in SATOPTS (see
12.1.68):
IRREVERS irreversible directional relative permeabilities. Different tables are used for
flow direction from I to I-1 ot from I to I+1. (in this case DIRECT must also be defined).
Six tables should be specified via the keywords KRNUMX (see 12.4.24), KRNUMX-
(see 12.4.24), KRNUMY (see 12.4.24), KRNUMY- (see 12.4.24), KRNUMZ (see
12.4.24) and KRNUMZ- (see 12.4.24).
Default: region number specified in SATNUM (see 12.4.3).
Example
SATOPTS
DIRECT IRREVERS/
...
KRNUMX
4000*2 /
KRNUMX-
4000*3 /
In this example for 4000 blocks saturation table number for X+ face 2, for the face X-
3.
12.4.24. KRNUM 677

12.4.25 KRNUMMF


Section
This keyword specifies the number of matrix-fracture saturation table regions for each
grid block. One integer number should be entered for each grid block. The data should be
The keyword can be used for dual porosiry runs DUALPORO (see 12.1.76) and dual
permeability DUALPERM (see 12.1.77).
In accordance with the grid specification for dual porosity models (upper part the ma-
trix, the lower fracture) the flow from the fracture to the matrix uses a saturation table for
Example
DUALPORO
DUALPERM
...
KRNUMMF
4000*1
4000*2 /
In this example first 4000 blocks correspond to matrix (the flow from the fracture to the
matrix uses a saturation table number 1), next 4000 blocks correspond to fracture (the flow
from the fracture to the matrix uses a saturation table number 2).
12.4.25. KRNUMMF 678

12.4.26 IMBNUMMF


Section
This keyword specifies the number of matrix-fracture imbibition regions for each grid
block. One integer number should be entered for each grid block. The data should be termi-
The keyword can be used for dual porosiry runs DUALPORO (see 12.1.76) and dual
permeability DUALPERM (see 12.1.77) in case when hysterisis option is used (parameter
HYSTER of the keyword SATOPTS (see 12.1.68)).
In accordance with the grid specification for dual porosity models (upper part the ma-
trix, the lower fracture) the flow from the fracture to the matrix uses an imbibition table
for matrix, the flow from the fracture to the matrix uses an imbibition table for fracture.
Example
DUALPORO
DUALPERM
SATOPTS
HYSTER/
...
IMBNUMMF
4000*1
4000*2 /
In this example first 4000 blocks correspond to matrix (the flow from the fracture to the
matrix uses an imbibition table number 1), next 4000 blocks correspond to fracture (the flow
from the fracture to the matrix uses an imbibition table number 2).
12.4.26. IMBNUMMF 679

12.4.27 WH2NUM


Section
The keyword specifies which set of water saturation functions (input using SWOF (see
12.6.1), SWFN (see 12.6.13) and so on) should be used in two-phase system for the water
relative permeabilities associated with the WAG hysteresis option (the keyword WAGHYSTR
(see 12.8.29)).
saturation function region to which it belongs. The region number should not be less than 1
or greater than the second number specified in keyword TABDIMS (see 12.1.26).
1. saturation function region number for each grid block.
If keyword WAGHYSTR (see 12.8.29) is set, then keyword WH2NUM (see 12.4.27) is
optional. If WH2NUM (see 12.4.27) is absent, then regions will be the same as SATNUM
regions. If it is present, then for grid blocks where the WH2NUM region number is different
to SATNUM region, the saturation functions will be taken from the WH2NUM table for
saturation regions for which WAG hysteresis has been applied to the water phase.
Example
WH2NUM
100*1 44*2 96*3 /
In the example 3 saturation function regions are set.
12.4.27. WH2NUM 680

12.4.28 WH3NUM


Section
The keyword specifies which set of water saturation functions (input using SWOF (see
12.6.1), SWFN (see 12.6.13) and so on) should be used in three-phase system for the water
relative permeabilities associated with the WAG hysteresis option (the keyword WAGHYSTR
(see 12.8.29)).
saturation function region to which it belongs. The region number should not be less than 1
or greater than the second number specified in keyword TABDIMS (see 12.1.26).
1. saturation function region number for each grid block.
If keyword WAGHYSTR (see 12.8.29) is set, then keyword WH2NUM (see 12.4.27) is
optional. If WH2NUM (see 12.4.27) is absent, then regions will be the same as SATNUM
regions. If present, then for grid blocks where the WH2NUM region number is different
to SATNUM region, the saturation functions will be taken from the WH2NUM table for
saturation regions for which WAG hysteresis has been applied to the water phase.
Example
WH3NUM
100*1 44*2 96*3 /
In the example 3 saturation function regions are set.
12.4.28. WH3NUM 681

12.4.29 ZONES


Section
This keyword sets zones by defining layers that belong to these zones. Zones can belong
to reservoirs. This keyword can be used if you need to calculate difference between RFT
(MDT) measurement and calculation. If zones are specified this data will be calculated for
zones. If reservoirs are specified this data will be calculated for reservoirs as well.
Each line should be terminated with a slash /. All data should be terminated with a final
slash /.
1. zone name;
2. upper layer of this zone;
3. bottom layer of this zone;
4. reservoir name to which this zone belongs.
Note 1: reservoir name can be not specified.

Note 2: layer number can be defaulted (see Example 2).
Note 3: it is possible to have layers that dont belong to any zone.
Example 1.
Example
ZONES
ZONE1 1 3 TOPres/
ZONE2 4 7 TOPres /
ZONE3 8 10 TOPres /
ZONE4 11 15 TOPres/
ZONE5 16 19 TOPres/
ZONE6 20 21 TOPres /
ZONE7 22 25 BOTTOMres /
/
12.4.29. ZONES 682

In this example we set 10 zones; zones 1-5 belong to the reservoir TOPres, zones 7-10
belong to the reservoir BOTTOMres.
Example 2. Possibility to default layer number:
Example
ZONES
ZONE1 1 1* TOPres/
ZONE2 4 1* TOPres /
ZONE3 8 1* TOPres /
ZONE4 11 1* TOPres/
ZONE5 16 1* TOPres/
ZONE6 20 1* TOPres /
ZONE7 22 1* BOTTOMres /
/
In this example layer 3 is considered as a last for ZONE1 (is calculated as a difference
between number of ZONE2 first layer (number 4) minus 1), then analoqously.
12.4.29. ZONES 683

12.5. PVT Properties tNavigator-4.2
12.5 PVT Properties

The following keywords set PVT properties of water, oil and gas phases:
PVTO (see 12.5.4) live oil;
PVCO (see 12.5.6) live oil (The difference between PVCO and PVTO (see 12.5.4)
is following: PVCO is used if under-saturated oil has a pressure-independent com-
pressibility and the derivative of viscosity of undersaturated oil is pressure-independent
too);
PVDO (see 12.5.2) dead oil;
PVCDO (see 12.5.3) dead oil (with constant compressibility);
RSCONST (see 12.5.12) if dead oil is used to model oil with a constant dissolved
gas concentration;
RSCONSTT (see 12.5.13) if dead oil is used to model oil with a constant dis-
solved gas concentration (dissolved gas concentration may be different in different
PVT regions);
PVTG (see 12.5.8) wet gas;
PVDG (see 12.5.7) dry gas;
PVZG (see 12.5.9) dry gas (with compressibility factor Z-factor);
RVCONST (see 12.5.14) if dry gas is used to model gas with a constant vaporized
oil concentration;
RVCONSTT (see 12.5.15) if dry gas is used to model gas with a constant vapor-
ized oil concentration (vaporized oil concentration may be different in different PVT
regions);
PVTW (see 12.5.5) water.
The keywords specifying initial pressures and saturations (see Initialization section
(12.15)):
RV (see 12.15.32) initial oil vaporization with wet gas (wet gas);
PDEW (see 12.15.33) initial dew point pressure (wet gas);
RS (see 12.15.31) initial gas solution in oil (live oil);
PBUB (see 12.15.30) initial bubble point pressure (live oil).
There are two keyword groups (1 wet gas, 2 live oil). One should use only one
keyword from one group.
group 1: RV (see 12.15.32), PDEW (see 12.15.33)
group 2: RS (see 12.15.31), PBUB (see 12.15.30)
12.5. PVT Properties 684

12.5.1 PROPS


Section
The keyword specifies the beginning of data section which contains the data describing
reservoir fluid properties and reservoir properties.
12.5.1. PROPS 685

12.5.2 PVDO


Section
The keyword sets black oil PVT properties for all PVT regions. The following parameters
are to be specified:
1. bubble point pressure (METRIC: barsa, FIELD: psia) ( pO argument in 2.9, 2.16, 2.8),
2. oil formation volume factor (METRIC: rm3 /sm3 , FIELD: rb/stb) (BO in 2.9),
3. oil viscosity at bubble point (cP) ( O in 2.8).
For each PVT region oil PVT properties tables should follow, each table must be termi-
nated by a slash /. There must be the same number of tables as number of PVT regions
defined in TABDIMS (see 12.1.26).
Default: none.
Note:
Models in E100 format: linear interpolation of the reciprocals of BO and BO O is done

(not parameters themselves) between data points;
Models in E300 format: linear interpolation of parameters BO and O is done.
Example
TABDIMS
1 2 2* 1
/
...
PVDO
83.20 1.15 2.45
239.00 1.12 2.93
/
102.34 1.15 2.56
267.67 1.11 2.89
/
This example sets black oil PVT properties for two PVT regions. Note that TABDIMS
(see 12.1.26) keyword defined 2 PVT regions.
12.5.2. PVDO 686

12.5.3 PVCDO


Section
The keyword sets dead oil (with constant compressibility) PVT properties for all PVT
regions. The following parameters are to be specified:
1. reference pressure (METRIC: barsa, FIELD: psia) ( pref in 2.9, 2.8),
2. oil formation volume factor at the reference pressure (METRIC: rm3 /sm3 , FIELD:
rb/stb) (BO in 2.9),
BO 1
3. oil compressibility (METRIC: 1/bars, FIELD: 1/psi) cO = ,
P BO
4. oil viscosity at the reference pressure (cP) ( O in 2.8),
O 1
5. oil viscosibility (METRIC: 1/bars, FIELD: 1/psi) (Cv = ).
P o
Use new line to enter oil PVT properties of any region. Each line should be terminated
by a slash /. The number of lines should be equal to the number of PVT regions entered by
the keyword TABDIMS (12.1.26).
The oil formation volume factor at the pressure pO is calculated using the formula:
BO (pref )O (pref )exp((cO Cv )(pO pref ))

BO (pO ) = .
O (pO )
Default: none
Example
TABDIMS
1 2 2* 1
/
...
PVDCO
83.20 1.15 1.7e-4 0.22 0
/
102.34 1.15 1.56e-5 0.73 0
267.67 1.11 2.89e-5 0.69 0
/
In this example there are two regions with different dead oil PVT properties. Note that
the keyword TABDIMS (see 12.1.26) sets the number of such regions equal to 2.
12.5.3. PVCDO 687

12.5.4 PVTO


Section
The keyword sets live oil PVT properties for all PVT regions.
The following parameters (one set of data) are to be specified:
1. gas-oil ratio (METRIC: sm3 /sm3 , FIELD: Msc f /stb) (this is RG,O in 2.16),
2. bubble point pressure (METRIC: barsa, FIELD: psia) (this is argument pbub in 2.9,
2.16, 2.8),
3. oil formation volume factor (METRIC: rm3 /sm3 , FIELD: rb/stb) (this is BO in 2.9),
4. oil viscosity at bubble point pressure (cP) (this is O in 2.8).

One set of data specifies PVT properties for one gas-oil ratio RG,O . Some sets of data
may contain extra data specifying properties of under-saturated oil for given gas-oil ratio.
This extra data must be entered in each table for the largest RG,O . The number of lines of
this data for one RG,O shouldnt be larger than 4-th parameter of TABDIMS (see 12.1.26)).
For undersaturated part of the table, solution gas-oil ratio RG,O is not specified. Thus the
extra data should be entered as 3 columns (contain 2-nd, 3rd and 4th parameter described
above).
The edditional data fot under-saturated oil should be written in the 3-column format:
oil phase pressure pO (METRIC: barsa, FIELD: psia) for oil with gas-oil ratio RG,O ,
specified via 1-st parameter;
oil formation volume factor BO (METRIC: rm3 /sm3 , FIELD: rb/stb) for with oil
phase pressure pO and gas-oil ratio RG,O ;
oil viscosity O (cP) at pO and RG,O .

Each set of data should be terminated by a slash /
For each PVT region oil PVT properties tables should follow, each table must be terminated
by a slash /. There must be the same number of tables as number of PVT regions defined
in TABDIMS (see 12.1.26).
A number of sets of data in one PVT table (number of different RG,O ) shouldnt be larger
than 6-th parameter of TABDIMS (see 12.1.26).
Default: none.
Note:
12.5.4. PVTO 688


Models in E300 format: linear interpolation of the reciprocal of BO is done, but for
O interpolation is done directly.
Example
TABDIMS
1 3 2* 1
/
...
PVTO
1 5 1.031 5.81 /
12.33 52 1.080 5.03 /
21.65 73 1.1021 4.23
204 1.092 4.62
321 1.016 6.02 /
/
1 5 1.0002 3.58 /
14.87 58 1.086 2.93 /
27.7 90 1.113 2.25
234 1.1 2.88
387 1.121 3.96 /
/
1 5 1.0002 3.58 /
18.67 57 1.0730 2.89 /
31.65 88 1.1083 2.2
248 1.093 2.57
334 1.073 4.23 /
/
This example sets different live oil PVT properties for three PVT regions: the first table
contains PVT properties of the first PVT region, the second table of the second one, the
third table of the third one. Note that TABDIMS (see 12.1.26) keyword defined 3 PVT
regions. The initial bubble point pressure Pbub user is 73 for the first PVT region, 90 for the
second and 88 for the third.
12.5.4. PVTO 689

12.5.5 PVTW


Section
The keyword sets water PVT properties for all PVT regions.
1. reference pressure (METRIC: barsa, FIELD: psia), (this is argument pref in 2.9, 2.8),
2. water formation volume factor (METRIC: rm3 /sm3 , FIELD: rb/stb), (this is BW
in 2.9),
3. water compressibility (METRIC: 1/bars, FIELD: 1/psi), (this is cW in 2.9),
4. water viscosity (cP) (this is W in 2.8),

W 1
5. water viscosibility (METRIC: 1/bars, FIELD: 1/psi) Cv = .
P W
For each PVT region water PVT properties should follow, each line must be terminated by
a slash /. There must be the same number of strings as number of PVT regions defined in
TABDIMS (see 12.1.26).
Water formation volume factor for given pressure pW will be calculated as follows
BW (pref )
BW (pW ) = 2 (p p )2 /2
.
1 + cW (pW pref ) + cW W ref
Default: none
Example
TABDIMS
1 2 2* 1
/
...
PVTW
234.00 1.02 4.0E-0005 0.42
/
250.00 1.00 4.0E-0005 0.43
/
This example considers two PVT regions. First line after PVTW sets water PVT properties
for the first region, the second line for the second one.
12.5.5. PVTW 690

12.5.6 PVCO


Section
The keyword sets live oil (in compressibility form) PVT properties. These properties can
also be specified by the keyword PVTO (see 12.5.4). The difference between PVCO and
PVTO (see 12.5.4) is following: PVCO is used if undersaturated oil with a special RG,O
( 2.16) has a pressure-independent compressibility and the derivative of viscosity of under-
saturated oil is pressure-independent too. Hence, tables for undersaturated oil which set the
dependence between the formation volume factor, viscosity and pressure shouldnt be speci-
fied.
Live oil PVT properties for each region should be entered in a new line. Region properties
should be terminated with a slash /. The number of lines is equal to the number of regions
with different PVT properties (set by the second parameter of the keyword TABDIMS (see
12.1.26)).

1. the bubble point pressure (METRIC: barsa, FIELD: psia) for oil with gas-oil ratio
specified by the 2-nd parameter of PVCO ( pO in 2.9, 2.16, 2.8),
2. gas-oil ratio (METRIC: sm3 /sm3 , FIELD: Msc f /stb) of saturated oil with bubble
point pressure specified by the 1-st parameter of PVCO (RG,O in 2.16),
3. the formation volume factor (METRIC: rm3 /sm3 , FIELD: rb/stb) of saturated oil at
the bubble point pressure (BO in 2.9),
4. the viscosity (cP) of saturated oil at the bubble point pressure ( O in 2.8),
5. the compressibility (METRIC: 1/bars, FIELD: 1/psi) of undersaturated oil with gas-
BO 1
oil ratio specified by the 2-nd parameter of PVCO (C = ).
P BO
6. the viscosibility (METRIC: 1/bars, FIELD: 1/psi) of undersaturated oil with gas-oil
O 1
ratio specified by the 2-nd parameter of PVCO (Cv = ).
P O
Note. When this keyword is used with a thermal option THERMAL (see 12.1.50) to
set the oil viscosity pressure dependence, you should specify only columns 1 and 4. Other
columns should be defaulted.
Note:
12.5.6. PVCO 691


Models in E300 format: linear interpolation of parameters BO and O is done.
Example
PVCO
14.6 5.2 1.0002 3.3184 0.000130357 0.000876023
38.4 14.6 1.0243 2.6836 0.000130357 0.000876023
62.2 25.2 1.0528 2.2741 0.000130357 0.000876023
86.1 36.6 1.0846 1.9982 0.000130357 0.000876023
109.9 48.7 1.1192 1.8024 0.000130357 0.000876023
133.7 61.4 1.1564 1.6571 0.000130357 0.000876023
149.7 70.7 1.1844 1.5744 0.000130357 0.000876023
154.1 72.5 1.19 1.5601 0.000130357 0.000876023
/
This example sets live oil PVT properties for one PVT region.
12.5.6. PVCO 692

12.5.7 PVDG


Section
The keyword sets gas PVT properties for all PVT regions. The following parameters are
to be specified:
1. reference pressure (METRIC: barsa, FIELD: psia), (this is argument pG in 2.9, 2.8),
2. gas formation volume factor (METRIC: rm3 /sm3 , FIELD: rb/Msc f ), (this is BG
in 2.9),
3. gas viscosity (cP) (this is G in 2.8).
For each PVT region gas PVT properties tables should follow, each table must be terminated
Default: none.
Note:
Models in E100 format: linear interpolation of the reciprocals of BG and BG G is done

Models in E300 format: linear interpolation of parameters BG and G is done.
12.5.7. PVDG 693

Example
TABDIMS
1 3 2* 1
/
...
PVDG
5 0.117 0.0118
73 0.0109 0.0142
204 0.00408 0.021
/
5 0.117 0.0117
90 0.0109 0.0149
234 0.00408 0.0251
/
5 0.117 0.0117
88 0.0109 0.0147
248 0.00408 0.0268
/
This example considers three PVT regions with different gas PVT properties: the first
table sets gas PVT properties for the first region, the second one for the second one, and
the third for the third one.
12.5.7. PVDG 694

12.5.8 PVTG


Section
The keyword sets wet gas PVT properties for all PVT regions. The following parameters
(one set of data) are to be specified:
1. dew point pressure (METRIC: barsa, FIELD: psia) (this is argument pG in 2.9, 2.17,
2.8),
2. oil vaporization in gas (METRIC: sm3 /sm3 , FIELD: stb/Msc f ) (this is RO,G in 2.17),
3. gas formation volume factor (METRIC: rm3 /sm3 , FIELD: rb/Msc f ) (this is BG
in 2.9),
4. gas viscosity at bubble point pressure (cP) (this is G in 2.8).
Each set of data should be terminated by a slash /

For each PVT region oil PVT properties tables should follow, each table must be terminated
A number of sets of data in one PVT table (number of different pG ) shouldnt be larger than
7-th parameter of TABDIMS (see 12.1.26).
One set of data specifies PVT properties for one dew point pressure pG . Some sets of
data may contain extra data specifying properties of undersaturated gas for given dew point
pressure. This extra data must be entered in each table for the largest pG . The number of
lines of this data for one pG shouldnt be larger than 4-th parameter of TABDIMS (see
12.1.26)).
For undersaturated part of the table, dew point pressure pG is not specified. Thus the extra
data should be entered as 3 columns (contain 2-nd, 3rd and 4th parameter described above).
Initial oil vaporization in gas is to be specified by keyword RV (see 12.15.32). For

pressures above dew point pressure saturated oil properties are extrapolated linearly.
Default: none.
Note:
Models in E100 format: linear interpolation of the reciprocals of BG and BG G is done

12.5.8. PVTG 695

Models in E300 format: linear interpolation of parameters BG and G is done.
Example
TABDIMS
1 2 2* 1
/
...
PVTG
1 0.00007 1.131 0.0120 /
12.33 0.00006 0.080 0.0123 /
21.65 0.00005 0.1021 0.0126 /
250.0 0.00006 0.0092 0.021
0. 0.0098 0.02 /
/
1 0.000017 1.131 0.0120 /
12.33 0.000016 0.080 0.0123 /
21.65 0.000015 0.1021 0.0126 /
230.0 0.0000155 0.0092 0.021
0. 0.0098 0.02 /
/
This example sets different live oil PVT properties for two PVT regions: the first table
contains PVT properties of the first PVT region, the second table of the second one. Note
that TABDIMS (see 12.1.26) keyword defined 2 PVT regions.
12.5.8. PVTG 696

12.5.9 PVZG


Section
The keyword sets dry gas PVT properties (compressibility factor is taken into considera-
tion). The data should consist of tables (number of tables less or equal to the 2-nd parameter
of the keyword TABDIMS (see 12.1.26).) Each table contains two sets of data. A set of data
must be terminated by a slash /.
1-st set of data:
One parameter is to be specified:
the reference temperature (for this table) (METRIC: C, FIELD: F). This temperature
is used in the formula of conversion compressibility factor to formation volume factor.
2-nd set of data (a table consists of following columns):
Following parameters (one row of the table) are to be specified:
1. gas phase pressure (METRIC: barsa, FIELD: psia),
2. compressibility factor (Z-factor) for the pressure given by 1-st parameter,
3. gas viscosity for the pressure given by 1-st parameter (cP) ( G in 2.8).
The number of rows in this table should be equal or greater than 2 and not greater than
the 4-th parameter of the keyword TABDIMS (see 12.1.26).
This formula represent a connection among the formation volume factor BG (BG in 2.9),
the reference temperature Tre f and the pressure p:
Tre f + Tbase ps
BG = Z ( )
Ts + Tbase p
where Z - compressibility factor (Z - factor), ps = 1.103 Barsa, Ts = 15.56 K - pressure and
temperature at standard conditions. Tbase = 273.105 K -absolute temperature.
Default: nothing
12.5.9. PVZG 697

Example
TABDIMS
1 2 2* 1
/
...
PVZG
120 /
135 1.31 0.0120
200 1.39 0.0140
270 1.48 0.0160
350 1.56 0.0180
/
In this example the reference temperature is equal to 120. The 2-nd item of data sets gas
phase pressure, compressibility factor and gas viscosity.
12.5.9. PVZG 698

12.5.10 STANDO


Section
The keyword sets data that is used in Oil Standings correlations (2.11) to calculate oil
formation volume factor and viscosity. The data should be terminated with a slash /.
1. Rsb gas solubility at bubble point (sm3 /sm3 );
2. pb bubble-point pressure (METRIC: barsa, FIELD: psia);
3. T system temperature ( C );
4. cO isothermal compressibility coefficient.
One of parameters Rsb or pb can be entered (the second one can be specified as * and
will be calculated).
cO can be *.
Example
STANDO
135 * 121.11 0.000240 /
12.5.10. STANDO 699

12.5.11 STANDG


Section
The keyword sets data that is used in Gas Standings correlations (2.12) to calculate gas
formation volume factor and viscosity. The data should be terminated with a slash /.
1. z gas compressibility factor (Z-factor);
2. T system temperature ( C );
Example
STANDG
0.9 121.11 /
12.5.11. STANDG 700

12.5.12 RSCONST


Section
This keyword sets a constant and uniform gas concentration in dead oil. If there is no
gas phase and a pressure is always above the bubble point a black oil modeling can be more
efficient.
The keywords GAS (see 12.1.53) and DISGAS (see 12.1.56) shouldnt be specified in
the Definition section (12.1). So gas is not considered as an active phase. The model becomes
two-phase or single-phase (if water phase is presented or not).
The data should be terminated by a slash /. Following parameters are to be specified:
1. dissolved gas concentration (constant and uniform) (METRIC: sm3 /sm3 , FIELD:
Msc f /stb);
2. bubble point pressure (METRIC: barsa, FIELD: psia) (the run will stop if the pressure
in any block falls below this value);
The specification of this keyword leads to the modification of the oil density (there is the
dissolved gas in oil phase).
So gas flow rate is equal to the product of the oil flow rate and dissolved gas concentra-
tion.
The keyword RSCONSTT (see 12.5.13) sets a constant and uniform gas concentration in
dead oil for all PVT regions (this concentration may be different for different PVT regions).
Example
RSCONST
0.124 98
/
This example sets dissolved gas concentration to 0.124 and bubble point pressure 98.
12.5.12. RSCONST 701

12.5.13 RSCONSTT


Section
This keyword sets a constant and uniform gas concentration in dead oil for every PVT
region. PVT regions are specified using the keyword PVTNUM (see 12.4.2). If there is no
gas phase and a pressure is always above the bubble point a black oil modeling can be more
efficient.
The keywords GAS (see 12.1.53) and DISGAS (see 12.1.56) shouldnt be specified in
the Definition section (12.1). So gas is not considered as an active phase. The model becomes
The difference between RSCONST (see 12.5.12) and RSCONSTT is the following:
RSCONSTT is used to set a constant and uniform gas concentration in dead oil for all PVT
regions (this concentration may be different for different PVT regions). Oils with different
gas concentrations shouldnt mix (transmissibility shouldnt be allowed between such PVT
regions). Otherwise the gas concentration will change and the model should be considered as
a model with active gas phase.
The keyword is followed by data lines. Each line should be terminated by a slash /. The
number of lines is equal to the number of PVT regions (second parameter of the keyword
TABDIMS (see 12.1.26)). Following parameters are to be specified for every line:
1. dissolved gas concentration (constant and uniform) (METRIC: sm3 /sm3 , FIELD:
Msc f /stb);
2. bubble point pressure (METRIC: barsa, FIELD: psia) (the run will stop if the pressure
The specification of this keyword leads to the modification of the oil density (there is the
dissolved gas in oil phase).
So gas flow rate is equal to the product of the oil flow rate and dissolved gas concentra-
tion (of the PVT region to which this well belongs to). The gas flow rate of a group of wells
(or reservoir) is calculated as the sum of wells gas flow rates of this group (or reservoir).
The second parameter of TABDIMS (see 12.1.26) is equal to 3.
12.5.13. RSCONSTT 702

Example
RSCONSTT
0.124 98 /
0.131 101 /
0.142 102 /
This example sets dissolved gas concentration to 0.124 and bubble point pressure 98
(first PVT region), 0.131 and 101 (second PVT region), 0.142 and 102 (third PVT region).
12.5.13. RSCONSTT 703

12.5.14 RVCONST


Section
This keyword sets a constant and uniform oil concentration in dry gas. If there is no oil
phase and a pressure is always above the dew point a modeling of gas systems can be more
efficient.
The keywords OIL (see 12.1.52) and VAPOIL (see 12.1.55) shouldnt be specified in
the Definition section (12.1). So oil is not considered as an active phase. The model becomes
The data should be terminated by a slash /. Following parameters are to be specified:
1. vaporized oil concentration (constant and uniform) (METRIC: sm3 /sm3 , FIELD:
Msc f /stb);
2. dew point pressure (METRIC: barsa, FIELD: psia) (the run will stop if the pressure
The specification of this keyword leads to the modification of the gas density (there is
the vaporized oil in gas phase).
So oil flow rate is equal to the product of the gas flow rate and vaporized oil concentration.
The keyword RVCONSTT (see 12.5.15) sets a constant and uniform oil concentration in
dry gas for all PVT regions (this concentration may be different for different PVT regions).
Example
RVCONST
0.00024 85
/
This example sets vaporized oil concentration to 0.00024 and dew point pressure 85.
12.5.14. RVCONST 704

12.5.15 RVCONSTT


Section
This keyword sets a constant and uniform oil concentration in dry gas for every PVT
region. PVT regions are specified using the keyword PVTNUM (see 12.4.2). If there is no
oil phase and a pressure is always above the dew point a modeling of gas systems can be
more efficient.
The keywords OIL (see 12.1.52) and VAPOIL (see 12.1.55) shouldnt be specified in
the Definition section (12.1). So oil is not considered as an active phase. The model becomes
The difference between RVCONST (see 12.5.14) and RVCONSTT is the following: RV-
CONSTT is used to set a constant and uniform oil concentration in dry gas for all PVT
regions (this concentration may be different for different PVT regions). Gas with different
oil concentrations shouldnt mix (transmissibility shouldnt be allowed between such PVT
regions). Otherwise the oil concentration will change and the model should be considered as
a model with active oil phase.
The keyword is followed by data lines. Each line should be terminated by a slash /. The
number of lines is equal to the number of PVT regions (second parameter of the keyword
TABDIMS (see 12.1.26)). Following parameters are to be specified for every line:
1. vaporized oil concentration (constant and uniform) (METRIC: sm3 /sm3 , FIELD:
Msc f /stb);
2. dew point pressure (METRIC: barsa, FIELD: psia) (the run will stop if the pressure
The specification of this keyword leads to the modification of the gas density (there is
the vaporized oil in gas phase).
So oil flow rate is equal to the product of the gas flow rate and vaporized oil concen-
tration (of the PVT region to which this well belongs to). The oil flow rate of a group of
wells (or reservoir) is calculated as the sum of wells oil flow rates of this group (or reservoir).
Example
RVCONSTT
0.00024 95 /
0.00034 97 /
12.5.15. RVCONSTT 705

This example sets vaporized oil concentration in two PVT regions.
12.5.15. RVCONSTT 706

12.5.16 ROCK


Section
The keyword specifies rock properties for each PVT region (parameters 3-6 are used in
case of geomechanical model 2.31).
An arbitrary number of data lines can be entered, terminated with a slash /. The num-
ber of lines depends on number of rock regions specified in TABDIMS (see 12.1.26). The
number of rock regions is specified via 13-th parameter of TABDIMS (see 12.1.26); if this
parameter is not set then the number of rock regions is equal to the number of PVT regions
specified in 2-nd parameter of TABDIMS (see 12.1.26)).
Each data line contains the following parameters:

1. pre f - reference pressure (METRIC: barsa, FIELD: psia);
2. C pp - rock compressibility (METRIC: 1/bar , FIELD: 1/psi) (coefficient c in 2.5);
3. CR - compressibility of the rock matrix, CR = KS1 (METRIC: 1/bar , FIELD: 1/psi);

1
4. Cbc = - block compressibility (block that contains mixture), Cbc = K 1 (MET-
Kbulk
RIC: 1/bar , FIELD: 1/psi);
5. porosity value 0 at reference pressure pre f , if CR is not specified or Cbc ;
6. the value of Poisson coefficient 0 at reference pressure pre f , if Cbc is not specified;
Default:
pre f - reference pressure (METRIC: barsa, FIELD: psia) 1.0132 bar ;
If pre f is defaulted and option STORE of the keyword ROCKOPTS (see 12.5.21)
is used then initial pressure will be used (pore volume will be calculated at initial
conditions);
C pp - rock compressibility (METRIC: 1/bar , FIELD: 1/psi) 0;
Parameters CR and Cbc (if they are not specified) are calculated the following way:
if rock compressibility Cbc is not specified, but CR , 0 , C = C pp are specified, then:
Cbc = 0C pp + (1 + 0 )CR (12.1)
12.5.16. ROCK 707

if compressibility of the rock matrix CR is not specified, but 0 , C = C pp are specified:

Cbc
CR = (12.2)
3(1 0 )0
1+
2(1 20 )(1 0 )
if the value of Poisson coefficient is not specified 0 :

Cbc
CR = (12.3)
30
1+
2(1 0 )
if C pp is not specified, the default value will be used C pp = 0.00005bars1

if 0 is not specified, the default value will be used 0 = 0.33;
Note: Rock properties should be specified via the keyword ROCK (see 12.5.16) or
ROCKTAB (see 12.5.18). If these keywords are not set then the default value will be used
and the following warning will be displayed:
Warning: no ROCK or ROCKTAB specified. ROCK with default values will be used
(Reference pressure is (1.013250) bar, rock compressibility is (0.000000) 1/bar).
Example
TABDIMS
1 2 2* 1
/
...
ROCK
234.00 4.0E-0005
/
250.00 4.0E-0005
/
In this examples two PVT regions are considered (TABDIMS (see 12.1.26)). The first
line after ROCK keyword sets compressibility for the first PVT region, the second line for
the second one.
Example
GEOMECH
...
ROCK
200 0.000001 0.33 0.73 0.33 0.2 /
In this example geomechanical model is used and the keyword ROCK has 6 parameters.
12.5.16. ROCK 708

12.5.17 RKTRMDIR


Section
The keyword sets the number of parameters in one table row of the keyword ROCKTAB
(see 12.5.18). If this keyword is present, there are 5 parameters, else 3 parameters. In case
of 3 parameters the third parameter is the transmissibility multiplier. In case of 5 parameters:
the third is the multiplier in the X-direction, the fourth - in the Y-direction and the fifth - in
the Z-direction.
Example
RKTRMDIR
12.5.17. RKTRMDIR 709

12.5.18 ROCKTAB


Section
This keyword is used to set tables of transmissibility dependence on pressure for each
rock region. Each table should be terminated with a slash /. The number of tables should be
less of equal to the second parameter of the keyword ROCKCOMP (see 12.1.34).
The following parameters are to be specified (one table row):

1. pressure (METRIC: barsa, FIELD: psia), values should increase down the column ex-
cept for STRESS option (the 1-st parameter of the keyword ROCKOPTS (see 12.5.21)).
In this case pressure values should decrease. If the overburden pressure (Poverburden
OVERBURD (see 12.5.22)) is greater than the fluid pressure (Pf luid ) (which is of-
ten true), the effective fluid pressure will be negative (Pe f f luid = Pf luid Poverburden ,
Pe f f luid - effective fluid pressure). In this case the rock compaction tables (ROCKTAB
(see 12.5.18)) will have to be entered with negative pressure values. One can avoid
this using STRESS option. Pressure values in this case can be entered positive: pore
volume and transmissibility multipliers will be tabulated against the effective overbur-
den pressure, which will be positive (Pe f over = Poverburden Pf luid ).
2. porosity multiplier;
3. transmissibility multiplier (if RKTRMDIR (see 12.5.17) is present, this parameter is the
transmissibility multiplier in the X-direction);
4. transmissibility multiplier in the Y-direction (can be specified only if RKTRMDIR (see
12.5.17) is present);
5. transmissibility multiplier in the Z-direction (can be specified only if RKTRMDIR (see
12.5.17) is present);
Default: values of transmissibility multiplier are linearly interpolated using pressure val-
ues; all values of multiplier but the ones on the first and last line may be defaulted.
Note: Rock properties should be specified via the keyword ROCK (see 12.5.16) or
ROCKTAB (see 12.5.18). If these keywords are not set then the default value will be used
and the following warning will be displayed:
Warning: no ROCK or ROCKTAB specified. ROCK with default values will be used
(Reference pressure is (1.013250) bar, rock compressibility is (0.000000) 1/bar).
12.5.18. ROCKTAB 710

Example
ROCKTAB
21.74 0.9818 0.8915
65.22 0.9850 1*
108.70 0.9883 0.9341
195.65 0.9948 0.9768
282.61 1.0013 1.0194
/
This example sets one table of transmissibility dependence on pressure for one rock
region. Here transmissibility multipliers for a range of pressures are specified; value on the
second line will be interpolated using pressure values and multiplier values from the first and
third line.
12.5.18. ROCKTAB 711

12.5.19 ROCKAXES


Section
The keyword specifies the azimuth and zenith angle of the regional stress in each ROCK-
region (it is used in geomechanical model 2.31).
Region number - the same number as in the keyword ROCK (see 12.5.16) (i.e. is under
control of the keyword ROCKOPTS (see 12.5.21)).
If the values for any region are not specified they are set equal to the values in previous
region.
Example for one region:
Example
ROCKAXES
10 0/
In this example the azimuth of the regional stress is 10 C and zenith angle is 0 C.
Example for 3 ROCK-regions:
Example
ROCKAXES
110 0 /
/
/
In this example values for 2-nd and 3-rd region are nor specified and are set equal to the
values in 1-st region.
12.5.19. ROCKAXES 712

12.5.20 ROCKSTRE


Section
The keyword specifies the diagonal elements of the stress tensor (the regional stress) (it
is used in geomechanical model 2.31).
3 numbers should be entered (terminated with a slash /) values of the diagonal elements
of the stress tensor (bar ).
Example
ROCKSTRE
250 200 200/
12.5.20. ROCKSTRE 713

12.5.21 ROCKOPTS


Section
The keyword is used to set options for rock compaction or rock compressibility. The data
1. The method of application of the keyword OVERBURD (see 12.5.22) to the pressures
(specified via ROCKTAB (see 12.5.18)). Two options are possible: PRESSURE or
STRESS.
STRESS option. If the overburden pressure (Poverburden OVERBURD (see 12.5.22)) is
greater than the fluid pressure (Pf luid ) (which is often true), the effective fluid pressure
will be negative (Pe f f luid = Pf luid Poverburden , Pe f f luid - effective fluid pressure). In
this case the rock compaction tables (ROCKTAB (see 12.5.18)) will have to be entered
with negative pressure values. One can avoid this using STRESS option. Pressure
values in this case can be entered positive: pore volume and transmissibility multipliers
will be tabulated against the effective overburden pressure, which will be positive
(Pe f over = Poverburden Pf luid ).
If the keyword OVERBURD (see 12.5.22) isnt used, one should left defaulted this
parameter.
2. reference pressure option STORE, NOSTORE or REFFIRST.

STORE: copies the initial equilibrated pressure at the start of the run into the overburden
array. This has the effect of referencing the pore volume (as the function of pressure)
to the initial pressure rather than the reference pressure, that is, the pressure with a
pore volume multiplier of 1.0 in ROCKTAB (see 12.5.18) tables. Thus the input pore
volume for a cell is defined as the pore volume at initial conditions rather than the pore
volume at the reference pressure. OVERBURD (see 12.5.22) should not be used with
the STORE option as the input OVERBURD (see 12.5.22) data will be overwritten and
ignored.
If STORE option is used with the keyword ROCK (see 12.5.16) (first parameter
of ROCK should be defaulted as 1*) for the elastic rock compressibility model, the
input pore volume for cell is similarly defined as the reservoir pore volume at initial
conditions rather than the pore volume at the reference pressure. See example 2. This
functionality is supported for E100 and E300 model formats;
REFFIRST: reference pressure for pore value calculation setting by the first block of
the region.
12.5.21. ROCKOPTS 714

3. table region to be used: SATNUM, PVTNUM, ROCKNUM.
4. this is an Eclipse compatibility field.
Default:
1. PRESSURE,
2. NOSTORE,
3. PVTNUM.
Example 1:
Example
ROCKOPTS STRESS /
Example 2 (pore volume calculation at initial pressure):
Example
ROCKOPTS
1* STORE /
...
ROCK
1* 7E-005 /
12.5.21. ROCKOPTS 715

12.5.22 OVERBURD


Section
The keyword specifies rock overburden pressure tables. The keyword can be used if the
number of rock regions is specified (ROCKCOMP (see 12.1.34)).
The data consists of tables of rock overburden data (the number of tables should be equal
to the 2-nd parameter of the keyword ROCKCOMP (see 12.1.34)). Each table should be
terminated with a slash /. Rock regions are specified via ROCKNUM (see 12.4.14).
Each table row should contain the following parameters:
1. the depth (METRIC: m, FIELD: f t ),
2. the corresponding overburden pressure value (METRIC: barsa, FIELD: psia).
Default: if the keyword isnt present, the overburden pressure is taken to be zero.
STRESS option (the 1-st parameter of the keyword ROCKOPTS (see 12.5.21)). If
the overburden pressure (Poverburden OVERBURD (see 12.5.22)) is greater than the
fluid pressure (Pf luid ) (which is often true), the effective fluid pressure will be negative
(Pe f f luid = Pf luid Poverburden , Pe f f luid - effective fluid pressure). In this case the rock com-
paction tables (ROCKTAB (see 12.5.18)) will have to be entered with negative pressure
values. One can avoid this using STRESS option. Pressure values in this case can be entered
positive: pore volume and transmissibility multipliers will be tabulated against the effective
overburden pressure, which will be positive (Pe f over = Poverburden Pf luid ).
Example
OVERBURD
700 42
1500 112
2134 145
2744 183
/
In this example overburden pressure if specified for one rock region.
12.5.22. OVERBURD 716

12.5.23 DENSITY


Section
The keyword sets fluid densities for all PVT regions. Number of strings depends on
number of PVT regions defined in TABDIMS (see 12.1.26).
The following three parameters are to be specified (terminated with a slash /):
1. oil density (METRIC: kg/m3 , FIELD: lb/ f t 3 ) (this is O,SC in 2.14),
2. water density (METRIC: kg/m3 , FIELD: lb/ f t 3 ) (this is W,SC in 2.14),
3. gas density (METRIC: kg/m3 , FIELD: lb/ f t 3 ) (this is G,SC in 2.14).
Default:
oil density 600 kg/m3 = 37.457 lb/ f t 3 ;
water density 999.014 kg/m3 = 62.366 lb/ f t 3 ;
gas density 1 kg/m3 = 0.062428 lb/ f t 3 .
Example
TABDIMS
1 2 2* 1
/
...
DENSITY
600 999.014 1.0
/
883.40 1001.00 0.90
/
In this example there are two PVT regions with different properties: the first line sets
fluid densities for the first region, the second line for the second one.
12.5.23. DENSITY 717

12.5.24 GRAVITY


Section
The keyword sets fluid densities for all PVT regions. Number of strings depends on
number of PVT regions defined in TABDIMS (see 12.1.26).
The following three parameters are to be specified (terminated with a slash /):
1. oil API gravity,
2. water specific gravity (with reference to pure water),
3. gas gravity (with reference to air).
Default:
oil API gravity 45.5,
water specific gravity (with reference to pure water) 1.0,
gas gravity (with reference to air) 0.7773.
Example
TABDIMS
1 3 2* 1
/
...
GRAVITY
39.2 1.16 0.749 /
42.2 1.03 0.766 /
37.1 1.16 0.749 /
In this example there are free PVT regions with different properties.
12.5.24. GRAVITY 718

12.5.25 APIGROUP


Section
The keyword specifies maximum number of oil PVT tables groups if API tracking option
is used 2.10. The data should be terminated with a slash /.
Example
APIGROUP
3 /
12.5.25. APIGROUP 719

12.6. Relative permeabilities and capillary pressures tNavigator-4.2
12.6 Relative permeabilities and capillary pressures

This section describes keywords used to define relative permeabilities and capillary pres-
sures. First tables used to calculate phase relative permeabilities in case of multiphase flow,
and to calculate phase capillary pressures are described. Next keywords regulating relative
permeabilities interpolation methods and end-point scaling are listed.
The keywords specifying relative permeabilities (see Relative permeabilities and capillary
pressures (12.6)):
SWOF (see 12.6.1) oil-in-water relative permeability (both oil and water phases
should be present);
SGOF (see 12.6.2) oil-in-gas relative permeability (both oil and gas phases should
be present);
SLGOF (see 12.6.11) oil-in-gas relative permeability (both oil and gas phases should
be present);
SWFN (see 12.6.13) water saturation function;
SGFN (see 12.6.14) gas saturation function;
SOF2 (see 12.6.12) oil saturation function (only for two-phase models);
SOF3 (see 12.6.15) oil saturation function (only for three-phase models);
SGWFN (see 12.6.16) gas-water saturation function (may be used in gas-water

models, when oil isnt present).
The are two keyword groups; one shouldnt mix keywords from different groups.
group 1: SWOF (see 12.6.1), SGOF (see 12.6.2)
group 2: SWFN (see 12.6.13), SGFN (see 12.6.14), SOF2 (see 12.6.12), SGWFN (see
12.6.16), SOF3 (see 12.6.15)
One can see different keyword combinations in Property section (12.5) (PVT properties,
permeabilities, initial pressures and saturations).
12.6. Relative permeabilities and capillary pressures 720

The following keyword combinations are allowed (from keywords PVTO, PVCO,
PVCDO, PVDO, PVDG, PVZG, PVTG, PVTW, RSCONST, RSCONSTT, RVCONST, RV-
CONSTT, PBUB, RS, PDEW, RV, SWOF, SGOF, SOF2, SWFN, SGFN, SGWFN) :
Live oil, PVTO (see 12.5.4) (or PVCO (see 12.5.6)),

wet gas, PVTG (see 12.5.8),
water PVTW (see 12.5.5),
SGOF (see 12.6.2), SLGOF (see 12.6.11), SWOF (see 12.6.1)
dry gas, PVDG (see 12.5.7) (or PVZG (see 12.5.9)),
wet gas PVTG (see 12.5.8),
SGOF (see 12.6.2), SLGOF (see 12.6.11)
(or SOF2 (see 12.6.12) + SGFN (see 12.6.14))
Undersaturated oil and PVDO (see 12.5.2) (or PVCDO (see 12.5.3)),
constant dissolved gas RSCONST (see 12.5.12) (or RSCONSTT (see 12.5.13)),
SWOF (see 12.6.1),
(or SOF2 (see 12.6.12) + SWFN (see 12.6.13))
Dry gas and PVDG (see 12.5.7) (or PVZG (see 12.5.9)),
constant vaporised oil, RVCONST (see 12.5.14) (or RVCONSTT (see 12.5.15)),
SGFN (see 12.6.14), SWFN (see 12.6.13),
(or SGWFN (see 12.6.16))
Dead oil PVDO (see 12.5.2) (or PVCDO (see 12.5.3)),
Water PVTW (see 12.5.5),
SWOF (see 12.6.1),
(or SOF2 (see 12.6.12) + SWFN (see 12.6.13))
Dry gas, PVDG (see 12.5.7) (or PVZG (see 12.5.9)),
SGWFN (see 12.6.16)
Dead oil, PVDO (see 12.5.2) (or PVCDO (see 12.5.3)),
Wet gas, PVTG (see 12.5.8),
12.6. Relative permeabilities and capillary pressures 721

12.6.1 SWOF


Section
The keyword specifies relative permeability tables for all saturation function regions from
TABDIMS (see 12.1.26) for water-oil systems.
Each table is a 4-column table with the following columns:
1. SW (water saturation) (this is argument value for functions below)
2. KRWO (water relative permeability) (this is function krWO in 2.6)
3. KROW (oil relative permeability) (this is function krOW in 2.6)
4. POW (oil-water capillary pressure (METRIC: bars, FIELD: psi)) (this is function
PcOW in 2.15.2)
Number of tables depends on number of saturation function regions defined in TABDIMS.

Each table must be terminated by a slash /.
Default:
Default value can be entered in 2-nd, 3-rd or 4-th column of the table (). The default
values are replaced with the values, obtained by linear interpolation
All table for saturation region can be defaulted (except for the first table). In this case,
the table is fully equal to the previous table. In this case the default table must be
specified with a single slash Code /.
12.6.1. SWOF 722

Example
TABDIMS
1 1 2* 1
/
...
SWOF
0 0 1 0
0.25 0 1 0
0.3 0.002 0.81 0
0.35 0.008 0.64 0
0.4 0.018 0.49 0
0.45 0.032 0.36 0
0.5 0.05 0.25 0
0.55 0.072 0.16 0
0.6 0.098 0.09 0
0.65 0.128 0.04 0
0.7 0.162 0.01 0
0.75 0.2 0 0
1 0.2 0 0
/
This example sets relative permeability for a two-phase water-oil system for one saturation
function region.
12.6.1. SWOF 723

Example
TABDIMS
2 1 2* 1
/
...
SWOF
0.42 0 0.737 0
0.45364 1.1e-005 0.704875 0
0.48728 0.000225 0.610213 0
0.52092 0.001292 0.468702 0
0.55456 0.00438 0.310527 0
0.5882 0.011044 0.170133 0
0.62184 0.023012 0.072027 0
0.65548 0.04193 0.020856 0
0.68912 0.069122 0.003178 0
0.72276 0.10541 0.000115 0
0.7564 0.151 0 0
0.79004 0.205444 0 0
0.82368 0.267672 0 0
0.85732 0.336083 0 0
0.89096 0.408671 0 0
0.9246 0.483175 0 0
0.95824 0.557237 0 0
1 0.645099 0 0
/
0 0 1 0
0.25 0 1 0
0.3 0.002 0.81 0
0.35 0.008 0.64 0
0.4 0.018 0.49 0
0.45 0.032 0.36 0
0.5 0.05 0.25 0
0.55 0.072 0.16 0
0.6 0.098 0.09 0
0.65 0.128 0.04 0
0.7 0.162 0.01 0
0.75 0.2 0 0
1 0.2 0 0
/
This example sets relative permeabilities for a two-phase water-oil system for two satu-
ration function regions.
12.6.1. SWOF 724

12.6.2 SGOF


Section
The keyword specifies relative permeability tables for two-phase gas-oil systems for all
saturation regions from TABDIMS (see 12.1.26).
If water is active phase the keyword SWOF (see 12.6.1) should be specified.
1. SG (gas saturation) (this is argument value for functions below)
2. KRGO (gas relative permeability) (this is function krGO in 2.6)
3. KROG (oil relative permeability) (this is function krOG in 2.6)
4. POG (oil-gas capillary pressure (METRIC: bars, FIELD: psi)) (this is function PcOG
in 2.15.1)
Number of tables depends on number of saturation regions defined in TABDIMS. Each

table must be terminated by a slash /.
Default:
12.6.2. SGOF 725

Example
TABDIMS
1 1 2* 1
/
...
SGOF
0 0 1 0
0.25 0 1 0
0.3 0.002 0.81 0
0.35 0.008 0.64 0
0.4 0.018 0.49 0
0.45 0.032 0.36 0
0.5 0.05 0.25 0
0.55 0.072 0.16 0
0.6 0.098 0.09 0
0.65 0.128 0.04 0
0.7 0.162 0.01 0
0.75 0.2 0 0
1 0.2 0 0
/
In this example two-phase gas-oil relative permeability is specified for one saturation
region.
12.6.2. SGOF 726

12.6.3 COREYWO


Section
The keyword approximates relative permeability and capillary pressure functions for
water-oil systems using formulas 2.35, 2.36, 2.37.
The number of lines should be equal to the number of saturation function regions (speci-
fied via TABDIMS (see 12.1.26)). The data for each saturation region should be terminated
with a slash /.
All data should be terminated with a final slash /.
If the parameters are specified for the region, but for the next region they are defaulted
via only /, then all the data for this region will be copied from the previous one.
The picture of relative permeabilities for water-oil system with points 1.

The following parameters for each line should be specified:
1. SW L minimal water saturation;
2. SWU maximal water saturation;
3. SWCR critical water saturation;
4. SOWCR residual oil saturation in the water-oil system;
5. krOLW = krOW (SW L ) must be equal to krOG (SGL );
6. krORW = krOW (SWCR ) must be less or equal to krOLW ;
7. krW R = krW (1 SOWCR SGL );
8. krWU = krW (SWU ), must be greater or equal to krW R ;
9. pcOW = pcOW (SWCR ) oil-water capillary pressure (METRIC: bars, FIELD: psi);
10. nOW degree at krOW ;
11. NW degree at krW ;
12. N p degree at pcOW . If the value 0 is entered, then capillary pressure will be taken
from tables (SWOF, SGOF, ...), see the note below;
13. S pcO point where capillary pressure becomes zero in water-oil system.
12.6.3. COREYWO 727

Default:
SW L minimal water saturation 0;
SWU maximal water saturation 1;
SWCR = SW L ;
SOWCR = 0;
if krOLW and krORW are defaulted, then krOLW = krORW = 1. Otherwise, krOLW =
krORW ;
if krW R and krWU are defaulted, then krW R = krWU = 1. Otherwise, krW R = krWU ;
PcOW = 0;
nOW degree at krOW 4;
NW degree at krW 4;
N p degree at pcOW 4;
S pcO = 1.
Note In tNavigator there is a possibility to use Corey (LET) correlation only for RP and
Example
COREYWO
0.05 0.95 0.15 0.3 0.9 0.7 0.4 0.55 0.11 2 2 2 0.2/
/
This example sets relative permeability and capillary pressure for a two-phase water-oil
system for one saturation region.
Example
COREYWO
0.05 0.95 0.15 0.3 0.9 0.7 0.4 0.55 0.11 2 2 2 0.2/
0.05 0.95 0.25 0.3 0.85 0.7 0.4 0.55 0.2 4 4 3 0.2/
/
system for two saturation regions.
12.6.3. COREYWO 728

12.6.4 COREYGO


Section
The keyword approximates relative permeability and capillary pressure functions for gas-
oil systems using the formulas 2.41, 2.42, 2.43.
with a slash /.
The picture of relative permeabilities for gas-oil system with points 2.

1. SGL minimal gas saturation;
2. SGU maximal gas saturation;
3. SGCR critical gas saturation;
4. SOGCR residual oil saturation in the gas-oil system;
5. krOLG = krOG (SGL ) must be equal to krOW (SW L );
6. krORG = krOG (SGCR ) must be less or equal to krOLG ;
7. krGR = krG (1 SOGCR SW L );
8. krGU = krG (SGU ), must be greater or equal to krGR ;
9. pcOG = pcOG (1 SOGCR SW L ) gas-oil capillary pressure (METRIC: bars, FIELD:

psi);
10. nOG degree at krOG ;
11. NG degree at krG ;
12. N pG degree at pcOG . If the value 0 is entered, then capillary pressure will be taken
13. S pcG point where capillary pressure becomes zero in gas-oil system.
12.6.4. COREYGO 729

Default:
SGL minimal gas saturation 0;
SGU maximal gas saturation 1;
SGCR SGL ;
SOGCR = 0;
if krOLG and krORG are defaulted, then krOLG = krORG = 1. Otherwise, krOLG = krORG ;
if krGR and krGU are defaulted, then krGR = krGU = 1. Otherwise, krGR = krGU ;
pcOG = 0;
nOG degree at krOG 4;
NG degree at krG 4;
N pG degree at pcOG 4;
S pcG = 1.
Example
COREYGO
0 0.9 0 0.4 0.9 1* 0.6 0.85 0.22 2 2 2 0/
/
This example sets relative permeability and capillary pressure for a two-phase gas-oil
Example
COREYGO
0 0.9 0 0.4 0.9 1* 0.6 0.85 0.22 2 2 2 0/
0 0.9 0 0.4 0.85 1* 0.6 0.85 0.22 4 4 2 0/
/
12.6.4. COREYGO 730

12.6.5 COREYWG


Section
water-gas systems using formulas 2.47, 2.48, 2.49.
with a slash /.
The picture of relative permeabilities for water-gas system with points 3.

5. krGU = krG (1 SW L ), must be greater or equal to krGR ;
6. krGR = krG (1 SWCR );
7. krW R = krW (1 SGCR );
9. pcW G = pcW G (SWCR ) water-gas capillary pressure (METRIC: bars, FIELD: psi);
10. nG degree at krG ;
11. NW degree at krW ;
12. N p degree at pcW G . If the value 0 is entered, then capillary pressure will be taken
13. S pcO point where capillary pressure becomes zero in water-oil system.
12.6.5. COREYWG 731

Default:
SWCR = SW L ;
SGCR = 0;
if krGU and krGR are defaulted, then krGU = krGR = 1. Otherwise, krGU = krGR ;
if krW R and krWU are defaulted, then krW R = krWU = 1. Otherwise, krW R = krWU ;
pcW G 0 bars;
nW G degree at krW G 4;
NW degree at krW 4;
N p degree at pcW G 4;
S pcO = 1.
Example
COREYWG
0.05 0.95 0.15 0.3 0.9 0.7 0.4 0.55 0.11 2 2 2 0.2/
/
This example sets relative permeability and capillary pressure for a two-phase gas-water
Example
COREYWG
0.05 0.95 0.15 0.3 0.9 0.7 0.4 0.55 0.11 2 2 2 0.2/
0.05 0.95 0.25 0.3 0.85 0.7 0.4 0.55 0.2 4 4 3 0.2/
/
This example sets relative permeability and capillary pressure for a two-phase gas-water
12.6.5. COREYWG 732

12.6.6 COREYWOMOD


Section
water-oil systems using formulas 2.38, 2.39, 2.40. These formulas are changed from ones
which are used by the keyword COREYWO (see 12.6.3): in new formulas residual oil satu-
ration in the gas-oil system, SOWCR , is not used to calculate SW n and krW ; but it is still used
to calculate krOW .
Parameters list, input order and conditions of their using are the same as ones of the
keyword COREYWO (see 12.6.3).
12.6.6. COREYWOMOD 733

12.6.7 COREYGOMOD


Section
oil systems using formulas 2.44, 2.45, 2.46. These formulas are changed from ones which are
used by the keyword COREYGO (see 12.6.4): in new formulas residual oil saturation in the
gas-oil system, SOGCR , is not used to calculate SGn and krG ; but it is still used to calculate
krOG .
Parameters list, input order and conditions of their using are the same as ones of the
keyword COREYGO (see 12.6.4).
12.6.7. COREYGOMOD 734

12.6.8 LETWO


Section
water-oil systems using formulas 2.50, 2.51.
with a slash /.
4. SOWCR residual oil saturation in the water-oil system;
5. krOLW = krOW (SW L ) must be equal to krOG (SGL );
6. krORW = krOW (SWCR ) must be less or equal to krOLW ;
7. krW R = krW (1 SOWCR SGL );
9. pcOW = pcOW (SWCR ) oil-water capillary pressure (METRIC: bars, FIELD: psi);
10. nOW degree at krOW ; describes the lower part of the curve krOW ;
11. NW degree at krW ; describes the lower part of the curve krW ;
12. N p degree at pcOW ; describes the capillary pressure curve. If the value 0 is entered,
then capillary pressure will be taken from tables (SWOF, SGOF, ...), see the note below;
13. S pcO point where capillary pressure becomes zero in water-oil system;
12.6.8. LETWO 735

14. TW describes the upper part (or the top part) of the curve krW ;
15. EW describes the position of the slope (or the elevation) of the curve krW . E = 1 is
a neutral value, the position of the slope is governed by L and T . Increasing E value
pushes the slope towards the high end of the curve. Decreasing E value pushes the
slope towards the lower end of the curve;
16. TOW describes the upper part (or the top part) of the curve krOW ;
17. EOW describes the position of the slope (or the elevation) of the curve krOW . E = 1
is a neutral value, the position of the slope is governed by L and T . Increasing E
value pushes the slope towards the high end of the curve. Decreasing E value pushes
the slope towards the lower end of the curve.
Default:
SWCR SW L ;
SOWCR 0;
if KrOLW and KrORW are defaulted, then KrOLW = KrORW = 1. Otherwise, KrOLW =
KrORW ;
if KrW R and KrWU are defaulted, then KrW R = KrWU = 1. Otherwise, KrW R = KrWU ;
PcOW 0;
nOW degree at krOW 4;
NW degree at krW 4;
S pcO = 1;
TW 2;
EW 1;
TOW 2;
EOW 1.
12.6.8. LETWO 736

Example
LETWO
0 1 0.2 0.2 1 1 0.6 0.6 0.11 2 5 2 -1 2 1 2 1 /
/
Example
LETWO
0 1 0.2 0.2 1 1 0.6 0.6 0.11 2 5 2 -1 2 1 2 1 /
0 1 0 0 1 1 1 1 0.11 2 5 2 -1 2 0.1 2 0.1 /
/
12.6.8. LETWO 737

12.6.9 LETGO


Section
oil systems using the formulas 2.52, 2.53.
with a slash /.
1. SGL minimal gas saturation;
2. SGU maximal gas saturation;
4. SOGCR residual oil saturation in the gas-oil system;
5. krOLG = krOG (SGL ) must be equal to krOW (SW L );
6. krORG = krOG (SGCR ) must be less or equal to krOLG ;
7. krGR = krG (1 SOGCR SW L );
8. krGU = krG (SGU ), must be greater or equal to krGR ;
9. pcOG = pcOG (1 SOGCR SW L ) gas-oil capillary pressure (METRIC: bars, FIELD:

psi);
10. nOG degree at krOG ; describes the lower part of the curve krOG ;
11. NG degree at krG ; describes the lower part of the curve krG ;
12. N pG degree at pcOG ; describes the capillary pressure curve. If the value 0 is entered,
13. S pcG point where capillary pressure becomes zero in gas-oil system;
12.6.9. LETGO 738

14. TG describes the upper part (or the top part) of the curve krG ;
15. EG describes the position of the slope (or the elevation) of the curve krG . E = 1 is
16. TOG describes the upper part (or the top part) of the curve krOG ;
17. EOG describes the position of the slope (or the elevation) of the curve krOG . E = 1
is a neutral value, the position of the slope is governed by L and T . Increasing E
value pushes the slope towards the high end of the curve. Decreasing E value pushes
the slope towards the lower end of the curve.
Default:
SGL minimal gas saturation 0;
SGU maximal gas saturation 1;
SGCR critical gas saturation 0;
SOGCR = 0;
if KrOLG and KrORG are defaulted, then KrOLG = KrORG = 1. Otherwise, KrOLG =
KrORG ;
if KrGR and KrGU are defaulted, then KrGR = KrGU = 1. Otherwise, KrGR = KrGU ;
pcOG = 0;
nOG degree at krOG 4;
NG degree at krG 4;
N pG degree at pcOG 4;
S pcG = 1;
TG 2;
EG 1;
TOG 2;
EOG 1.
12.6.9. LETGO 739

Example
LETGO
0 0.9 0 0.4 0.9 0.9 0.9 0.9 0.22 2 2 2 -1 2 1 2 1 /
/
Example
LETGO
0 0.9 0 0.4 0.9 0.9 0.9 0.9 0.22 2 2 2 -1 4* /
0 0.9 0 0.4 0.9 1* 0.6 0.85 0.22 2 2 2 -1 4* /
/
12.6.9. LETGO 740

12.6.10 LETWG


Section
water-gas systems using formulas 2.54, 2.55.
with a slash /.
5. krGU = krG (1 SW L );
6. krGR = krG (1 SWCR );
7. krW R = krW (1 SGCR );
9. pcW G = pcW G (SWCR ) oil-water capillary pressure (METRIC: bars, FIELD: psi);
10. nG degree at krOW ; describes the lower part of the curve krOW ;
11. NW degree at krW ; describes the lower part of the curve krW ;
12. N p degree at pcOW ; describes the capillary pressure curve. If the value 0 is entered,
13. S pcO point where capillary pressure becomes zero in water-oil system;
12.6.10. LETWG 741

14. TW describes the upper part (or the top part) of the curve krW ;
15. EW describes the position of the slope (or the elevation) of the curve krW . E = 1 is
16. TG describes the upper part (or the top part) of the curve krG ;
17. EG describes the position of the slope (or the elevation) of the curve krG . E = 1 is
slope towards the lower end of the curve.
Default:
SWCR = SW L ;
SGCR = 0;
if krGU and krGR are defaults, then krGU = krGR = 1, otherwise krGU = krGR ;
if krWU and krW R are defaults, then krWU = krW R = 1, otherwise krWU = krW R ;
PcW G 0;
nW G degree at krOW 4;
NW degree at krW 4;
S pcO = 1;
TW 2;
EW 1;
TG 2;
EG 1.
12.6.10. LETWG 742

Example
LETWG
0 1 0.2 0.2 1 1 0.6 0.6 0.11 2 5 2 -1 2 1 2 1 /
/
This example sets relative permeability and capillary pressure for a two-phase water-gas
Example
LETWG
0 1 0.2 0.2 1 1 0.6 0.6 0.11 2 5 2 -1 2 1 2 1 /
0 1 0 0 1 1 1 1 0.11 2 5 2 -1 2 0.1 2 0.1 /
/
This example sets relative permeability and capillary pressure for a two-phase water-gas
12.6.10. LETWG 743

12.6.11 SLGOF


Section
The keyword specifies relative permeability tables for two-phase gas-oil systems (oil and
gas are active phases) for all saturation regions from TABDIMS (see 12.1.26). Relative per-
meabilities depend on liquid saturations.
If water is active phase the keyword SWOF (see 12.6.1) should be specified.
Number of tables depends on number of saturation regions defined in TABDIMS (see

12.1.26). Each table must be terminated by a slash /.
One table row contains the following parameters:
1. liquid saturation (this is argument value for functions below). Last value of this param-
eter should be 1 (corresponds to zero gas saturation).
2. KRGO (gas relative permeability). Last value of this parameter should be zero. (this is
function krGO in 2.6)
3. KROG (oil relative permeability). First value of this parameter should be zero. (this is
function krOG in 2.6)
4. POG (oil-gas capillary pressure (METRIC: bars, FIELD: psi)) (this is function PcOG
in 2.15.1)
Default:
12.6.11. SLGOF 744

Example
TABDIMS
1 1 2* 1
/
...
SLGOF
0.120000 1.000000 0.000000 0.000000
0.270000 0.497746 0.000000 0.000000
0.420000 0.208062 0.000000 0.000000
0.486250 0.130383 0.000297 0.000000
0.519375 0.100594 0.001228 0.000000
0.585625 0.056059 0.007342 0.000000
0.651875 0.027773 0.023837 0.000000
0.685000 0.018390 0.038038 0.000000
0.751250 0.006719 0.083062 0.000000
0.784375 0.003550 0.115951 0.000000
0.817500 0.001625 0.157229 0.000000
0.883750 0.000144 0.269679 0.000000
0.950000 0.000000 0.430348 0.000000
0.975000 0.000000 0.505684 0.000000
1.000000 0.000000 0.590000 0.000000 /
In this example two-phase gas-oil relative permeability is specified for one saturation
region.
12.6.11. SLGOF 745

12.6.12 SOF2


Section
The keyword specifies relative permeability tables for two-phase water-oil systems for all
saturation regions from TABDIMS (see 12.1.26). Each table is a 2-column table with the
following columns:
1. SO (oil saturation) (this is argument value for function below)
2. KROW (oil relative permeability) (this is function krOW in 2.6)

Default:
Example
TABDIMS
1 1 2* 1
/
...
SOF2
0 0
0.25 0
0.3 0.002
0.35 0.008
0.4 0.018
0.45 0.032
0.5 0.05
0.55 0.072
0.6 0.098
0.65 0.128
0.7 0.162
0.75 0.2
1 0.2
/
12.6.12. SOF2 746

In this example two-phase oil-water relative permeability is specified for one saturation
region.
12.6.12. SOF2 747

12.6.13 SWFN


Section
TABDIMS (see 12.1.26) for two-phase water-oil systems.
2. KRWO (water relative permeability) (this is function krWO in 2.6)
3. POW (oil-water capillary pressure (METRIC: bars, FIELD: psi)) (this is function
PcOW in 2.15.2)

Default:
Default value can be entered in 2-nd, 3-rd column of the table (). The default values
are replaced with the values, obtained by linear interpolation
12.6.13. SWFN 748

Example
TABDIMS
1 1 2* 1
/
...
SWFN
0 0 0
0.25 0 0
0.3 0.002 0
0.35 0.008 0
0.4 0.018 0
0.45 0.032 0
0.5 0.05 0
0.55 0.072 0
0.6 0.098 0
0.65 0.128 0
0.7 0.162 0
0.75 0.2 0
1 0.2 0
/
This example sets relative permeability for a two-phase water-oil system for one saturation
function region.
12.6.13. SWFN 749

12.6.14 SGFN


Section
TABDIMS (see 12.1.26) for two-phase oil-gas systems.
SG - gas saturation (this is argument value for functions below).
KRGO - gas relative permeability (this is function krWO in 2.6). First element of this
column must be zero.
POG - oil-gas capillary pressure (METRIC: bars, FIELD: psi) (this is function PcOW
in 2.15.1).

Default:
12.6.14. SGFN 750

Example
TABDIMS
1 1 2* 1
/
...
SGFN
0 0 0
0.25 0 0
0.3 0.002 0
0.35 0.008 0
0.4 0.018 0
0.45 0.032 0
0.5 0.05 0
0.55 0.072 0
0.6 0.098 0
0.65 0.128 0
0.7 0.162 0
0.75 0.2 0
1 0.2 0
/
This example sets relative permeability for a two-phase oil-gas system for one saturation
function region.
12.6.14. SGFN 751

12.6.15 SOF3


Section
The keyword specifies relative permeability tables for three-phase systems for all satura-
tion regions from TABDIMS (see 12.1.26). Each table should be terminated with a slash /.
Each 3-column table consists of the following columns:
1. SO (oil saturation) (this is argument value for functions below)
2. oil relative permeability (where only oil and water are present);
3. oil relative permeability (where oil, gas and water are present).
Default:
The keyword specifies relative permeability tables for two-phase systems SOF2 (see
12.6.12).
12.6.15. SOF3 752

Example
TABDIMS
1 1 2* 1
/
...
SOF3
0 0 0
0.25 0 0
0.3 0.002 0
0.35 0.008 1*
0.4 0.018 0.01
0.45 0.032 1*
0.5 0.05 0.12
0.55 0.072 1*
0.6 0.098 0.3
0.65 0.128 1*
0.7 0.162 1*
0.75 0.2 0.63
1 0.2 1*
/
This example sets relative permeability for three-phase system for one saturation function
region.
12.6.15. SOF3 753

12.6.16 SGWFN


Section
The keyword specifies relative permeability tables for two-phase gas-water systems for
all saturation regions from TABDIMS.
2. KRGW (gas relative permeability)
3. KRWG (water relative permeability)
4. PGW (gas-water capillary pressure (METRIC: bars, FIELD: psi))

Default:
12.6.16. SGWFN 754

Example
TABDIMS
1 1 2* 1
/
...
SGWFN
0.27 0 1 0
0.3 0.02 0.81 0.3
0.42 0.18 0.49 0.9
0.51 0.34 0.16 1.4
0.6 0.53 0.09 2.7
0.64 0.71 0.04 4.1
0.72 0.92 0.01 5.3
0.85 1.00 0 7.1
1 1.00 0 9.4
/
In this example two-phase gas-water relative permeability is specified for one saturation
region.
12.6.16. SGWFN 755

12.6.17 SOMWAT


Section
The keyword specifies minimum oil saturation (that is used in 3-phase model STONE1
(see 12.6.20)), as a function of water saturation.
If the keyword STONE1 (see 12.6.20) is not specified then the keyword will be ignored.
Alternative keyword SOMGAS (see 12.6.18) specifies minimum oil saturation as a

function of gas saturation. Both keywords SOMGAS (see 12.6.18), SOMWAT (see 12.6.17)
can not be used in one run.
The keyword should be followed by tables. Number of tables depends on number of

saturation regions defined via 1-st parameter of TABDIMS. Each table must be terminated by
a slash /.
1. water saturation.
The first value should be equal to the connate water saturation in the table SWFN (see
12.6.13) (the lowest saturation in SWFN (see 12.6.13)).
The last value should be equal to the 1 SOrW SGc ,
where SGc connate gas saturation;
SOrW residual oil-to-water saturation in the table SOF3 (see 12.6.15) (SOrW the
largest oil saturation with zero krOW value in the 2-nd column of SOF3 (see 12.6.15))
(krOW (SOrW ) = 0).
2. corresponding minimum oil saturation.

The first value at connate water should not exceed SOrG residual oil-to-gas saturation
in the table SOF3. (SOrG the largest oil saturation with zero krOG value in the 3-rd
column SOF3 (see 12.6.15), krOG (SOrG ) = 0.)
The last value at 1 SOrW SGc should not exceed SOrW residual oil-to-water
saturation in the table SOF3 (see 12.6.15).
Relative permeabilities can be specified via the keywords SWOF (see 12.6.1), SGOF
(see 12.6.2). SOMGAS (see 12.6.18), SOMWAT (see 12.6.17) can also be used with these
keywords.
12.6.17. SOMWAT 756

Example
SWOF
0.355 0 1.000 0.
0.393 0.007 0.991 0.
0.431 0.016 0.972 0.
0.469 0.034 0.905 0.
0.507 0.068 0.743 0.
0.545 0.144 0.452 0.
0.583 0.2475 0.064 0.
0.621 0.393 0.020 0.
0.659 0.693 0.008 0.
0.696 0.937 0.002 0.
0.714 0.981 0.000 0.
1.000 1 0.000 0. /
SGOF
0.000 0.0000 1.00 0
0.100 0.0001 0.1810 0
0.150 0.0030 0.0980 0
0.200 0.0100 0.0480 0
0.252 0.0130 0.0210 0
0.280 0.0160 0.0070 0
0.395 0.0690 0.0000 0
0.645 0.2680 0.0000 0 /
SOMWAT
0.355 0.25
0.6 0.24
0.714 0.286 /
12.6.17. SOMWAT 757

12.6.18 SOMGAS


Section
The keyword specifies minimum oil saturation (that is used in 3-phase model STONE1
(see 12.6.20)), as a function of gas saturation.
If the keyword STONE1 (see 12.6.20) is not specified then the keyword will be ignored.
Alternative keyword SOMWAT (see 12.6.17) specifies minimum oil saturation as

a function of water saturation. Both keywords SOMGAS (see 12.6.18), SOMWAT (see
12.6.17) can not be used in one run.
The keyword should be followed by tables. Number of tables depends on number of

saturation regions defined via 1-st parameter of TABDIMS. Each table must be terminated by
a slash /.
1. gas saturation.
The first value should be equal to the connate gas saturation in the table SGFN (see
12.6.14) (usually 0).
The last value should be equal to the 1 SW SOrG ,
where SW c connate water saturation;
SOrG residual oil-to-gas saturation in the table SOF3 (see 12.6.15) (SOrG the
largest oil saturation with zero krOG value in the 3-rd column of SOF3 (see 12.6.15))
(krOG (SOrG ) = 0).
2. corresponding minimum oil saturation.

The first value at connate gas should not exceed SOrW residual oil-to-water saturation
in the table SOF3. (SOrW the largest oil saturation with zero krOW value in the 2-nd
column SOF3 (see 12.6.15), krOW (SOrW ) = 0.)
The last value at 1SOrG SW c should not exceed SOrG residual oil-to-gas saturation
in the table SOF3 (see 12.6.15).
Relative permeabilities can be specified via the keywords SWOF (see 12.6.1), SGOF
(see 12.6.2). SOMGAS (see 12.6.18), SOMWAT (see 12.6.17) can also be used with these
keywords.
12.6.18. SOMGAS 758

Example
TABDIMS
1 1 2* 1
/
...
SWFN
0.18 0.0 0.0
0.80 1.0 0.0 /
SOF3
0.1 0.0 0.0
0.23 0.0 0.3
0.28 0.0 0.5
0.82 1.0 1.0 /
SOMGAS
0.00 0.28
0.25 0.19
0.40 0.08
0.50 0.04
0.72 0.01
/
12.6.18. SOMGAS 759

12.6.19 TOLCRIT


Section
The keyword sets the tolerance for critical saturations, so the method for determination of
the initial relative permeability critical tables saturations is modified. One value of tolerance
should be specified. The data should be terminated with a slash /.
The keyword can be used in case of end-point scaling (ENDSCALE (see 12.6.24)) (2.6.4).
If TOLCRIT (see 12.6.19) isnt specified the critical water saturation SW cr is equal to
SW in the last table entry (SWOF (see 12.6.1), SWFN (see 12.6.13)) for krW , for which
krW 1.0 106 in e100 models (krW 1.0 1020 in e300 models) (finding the last
zero relative permeability value while accounting for machine zero).
If TOLCRIT (see 12.6.19) is specified, the critical water saturation is equal to SW in the
last table entry, for krW T OLCRIT (analogously SGcr , SOW cr , SOGcr ).
Default: 1.0 106 in e100 models, 1.0 1020 in e300 models.
Example
TOLCRIT
1.0E-9 /
12.6.19. TOLCRIT 760

12.6.20 STONE1


Section
The keyword specifies that Stone 1 model will be used for oil relative permeability cal-
culation 2.6.2.
User should specify either STONE1, or STONE2 (see 12.6.21). If none is specified, the
linear Bakers model will be used 2.6.1.
Example
STONE1
12.6.20. STONE1 761

12.6.21 STONE2


Section
The keyword specifies that Stone 2 model will be used for oil relative permeability cal-
culation 2.6.3.
User should specify either STONE1 (see 12.6.20), or STONE2. If none is specified, the
linear Bakers model will be used 2.6.1.
Example
STONE2
12.6.21. STONE2 762

12.6.22 STONE


Section
The keyword specifies that Stone 2 model will be used for oil relative permeability
calculation 2.6.3 (this keyword is analogous to the keyword STONE2 (see 12.6.21)).
User should specify either STONE1 (see 12.6.20), or STONE2 (see 12.6.21). If none is
specified, the linear Bakers model will be used 2.6.1.
Example
STONE
12.6.22. STONE 763

12.6.23 STONEPAR


Section
The keywords sets two numbers, A and B. These numbers are parameters of expression
for Som in the first Stones model of oil three-phase relative permeability (the keyword
STONE1 (see 12.6.20)).
Som is mobile oil balue as a function of gas saturation.
Expression for Som is:
2
Som = Sogcr NgA + Sowcr (1 Ng )A + BSgm Ng (1 Ng ),
where:
Sgm = 1 Swco Sogcr ;

Sg
Ng = Sgm .
1. parameter A;
2. parameter B.

Default:
parameter A: 1;
parameter B: 0.
Example
STONEPAR
1.0 0.0 /
In the example values of A and B is set to their default values.
12.6.23. STONEPAR 764

12.6.24 ENDSCALE


Section
Indicates that end-point scaling of relative permeabilities and capillary pressures will be
used, see 2.6.4, 2.6.5, 2.15.3 for details. Table end-points can then be entered cell by cell
(SWL (see 12.6.27), SWCR (see 12.6.30), SWU (see 12.6.34), KRW (see 12.6.43), PCW
(see 12.6.46)) or with respect to depth (ENPTVD (see 12.6.38), ENKRVD (see 12.6.39),
ENPCVD (see 12.6.40)).
The keyword ENPTRC (see 12.6.41) specifies end-point scaling tables from tracer con-
centration (salt, surfactant). (Surfactants section 2.25).
Only not directional reversible end-point scaling is supported.
/.):
1. directional end-point scaling switch (DIRECT, NODIR), ignored, this is an Eclipse com-
patibility field;
2. irreversible end-point scaling switch (IRREVERS, REVERS), ignored, this is an Eclipse

compatibility field;
3. the number of saturation end-point versus depth tables (keywords ENPTVD (see
12.6.38), ENKRVD (see 12.6.39)); in tNavigator number of tables does not have
to be specified because the memory is allocated dynamically;
4. the maximum number of nodes in any saturation end-point versus depth table (keywords
ENPTVD (see 12.6.38), ENKRVD (see 12.6.39)); in tNavigator number of tables does
not have to be specified because the memory is allocated dynamically.
5. option for combining the temperature-independent (tracer, salt, surfactant-independent)

end-points (for example, SWL (see 12.6.27), SWCR (see 12.6.30), SWU (see 12.6.34),
KRW (see 12.6.43), KRWR (see 12.6.43), PCW (see 12.6.46) etc.) with the
temperature-dependent end-points (for example, ENPTVT (see 12.14.69), ENKRVT
(see 12.14.70), ENPCVT (see 12.14.71)) or tracer (salt, surfactant) concentration-
dependent end-points (ENPTRC (see 12.6.41)) for saturations, relative permeabilities
and capillary pressures.
Temperature-dependent end-points are available only for THERMAL (see 12.1.50) op-
tion, for non-thermal option this parameter will be ignored.
One of the following option can be specified:
12.6.24. ENDSCALE 765

0 combination is not possible. Keywords ENDSCALE (see 12.6.24) and

ENPTVT (see 12.14.69), ENKRVT (see 12.14.70), ENPCVT (see 12.14.71),
ENPTRC (see 12.6.41) can not be used simultaneously;
1 temperature-independent (tracer, salt, surfactant-independent) end-points are
replaced by temperature-dependent (tracer, salt, surfactant-dependent) end-points
where table columns values are specified as non-defaulted;
2 temperature-independent (tracer, salt, surfactant-independent) end-points
are combined with temperature-dependent end-points (tracer (salt, surfactant)
concentration-dependent end-points) where table columns values are specified as
non-defaulted.
For combination with temperature-dependent end-points: a scaling factor is taken
the following way: the resulting value at the lowest temperature in the table will
correspond to the original value in the grid block.
For combination with tracer-dependent (salt, surfactant) end-points: a scaling fac-
tor is taken the following way: the resulting value at the lowest temperature in
the table will correspond to the original value in the grid block.
Default:
the number of saturation end-point versus depth tables (keywords ENPTVD (see
12.6.38), ENKRVD (see 12.6.39)) 1;
the maximum number of nodes in any saturation end-point versus depth table (keywords
ENPTVD (see 12.6.38), ENKRVD (see 12.6.39)) 20;
option for combining the temperature-independent end-points with the temperature-

dependent end-points 0.
Example
ENDSCALE /
12.6.24. ENDSCALE 766

12.6.25 TZONE


Section
This keyword controls the transition zone option. The keyword can be used only is the
keyword ENDSCALE (see 12.6.24) is active indicates that end-point scaling of relative
permeabilities and capillary pressures will be used.
3 parameters should be specified (The data should be terminated with a slash /.) (T
true, F false). Each parameter corresponds to one phase: oil, water and gas.
If the parameter is set true to a phase, then the critical saturations for that phase will
be modified to be the initial immobile saturation in regions where the saturation is below the
input critical value.
Example
TZONE
F T T /
12.6.25. TZONE 767

12.6.26 SCALECRS


Section
Keyword may be present in data file, if ENDSCALE (see 12.6.24) is selected. Allows to
define three-point scaling method for saturation tables end-point scaling. See 2.6.4, 2.6.5 for
details.
Keyword takes one argument, with two possible values
YES (three-point scaling method) or NO (two-point scaling method)
Next line must contain a slash /.

Default: NO
Example
SCALECRS
YES
/
This example sets three-point scaling method.
12.6.26. SCALECRS 768

12.6.27 SWL


Section
This keyword defines minimal water saturation for grid blocks, used for saturation end
point scaling. Keyword may be used only if ENDSCALE (see 12.6.24) is present in data file.
See 2.6.4, 2.6.5, 2.15.3 for details of end-point scaling.
The same number of values as number of cells must be specified. The data should be
Default: connate water saturation in corresponding saturation region, i.e. minimal water
saturation in SWOF (see 12.6.1) table.
Example
DIMENS
5 5 4
/
...
SWL
50*0.35 50*0.45
/
This example defines connate water saturation = 0.35 for first 50 blocks of the grid and
0.45 for last 50 blocks.
12.6.27. SWL 769

12.6.28 SWLPC


Section
point scaling only for capillary pressure Pc curves without scaling the corresponding oil RP
curves.
Keyword may be used only if ENDSCALE (see 12.6.24) is present in data file. See 2.6.4,
2.6.5, 2.15.3 for details of end-point scaling.
Default: if this keyword isnt specified then the oil-water (or gas-water) capillary pres-
sure scaling is done via the connate water saturation specified with the keyword SWL (see
12.6.27).
Example
DIMENS
5 5 4
/
...
SWLPC
5000*0.3 5000*0.23
/
This example defines connate water saturation = 0.3 for first 5000 blocks of the grid and
12.6.28. SWLPC 770

12.6.29 SGL


Section
This keyword defines minimal gas saturation for grid blocks, used for saturation end point
scaling. Keyword may be used only if ENDSCALE (see 12.6.24) is present in data file. See
2.6.4, 2.6.5, 2.15.3 for details of end-point scaling.
Default: connate gas saturation in corresponding saturation region, i.e. minimal gas satu-
ration in SGOF (see 12.6.2) table.
Example
DIMENS
5 5 4
/
...
SGL
50*0.35 50*0.45
/
This example defines connate gas saturation = 0.35 for first 50 blocks of the grid and
12.6.29. SGL 771

12.6.30 SWCR


Section
This keyword defines critical water saturation for grid blocks, used for saturation end
Default: critical water saturations in corresponding saturation region, i.e. maximal water
saturation in SWOF (see 12.6.1), for which krw = 0.
Example
DIMENS
5 5 4
/
...
SWCR
50*0.35 50*0.45
/
This example defines critical water saturation = 0.35 for first 50 blocks of the grid and
12.6.30. SWCR 772

12.6.31 SGCR


Section
This keyword defines critical gas saturation for grid blocks, used for saturation end point
scaling. Keyword may be used only if ENDSCALE (see 12.6.24) is present in data file. See
2.6.4, 2.6.5, 2.15.3 for details of end-point scaling.
Default: critical gas saturations in corresponding saturation region, i.e. maximal gas
saturation in SGOF (see 12.6.2), for which krG = 0.
Example
DIMENS
5 5 4
/
...
SGCR
50*0.35 50*0.45
/
This example defines critical gas saturation = 0.35 for first 50 blocks of the grid and 0.45
for last 50 blocks.
12.6.31. SGCR 773

12.6.32 SOWCR


Section
This keyword defines critical oil-to-water saturation for grid blocks, used for saturation
end point scaling. Keyword may be used only if ENDSCALE (see 12.6.24) is present in data
file. See 2.6.4, 2.6.5, 2.15.3 for details of end-point scaling.
Default: critical oil-to-water saturation in corresponding saturation region, i.e. maximal

oil saturation in SWOF (see 12.6.1), for which the oil relative permeability is zero: krOW = 0.
Example
DIMENS
5 5 4
/
...
SOWCR
50*0.35 50*0.45
/
This example defines critical oil-to-water saturation = 0.35 for first 50 blocks of the grid
and 0.45 for last 50 blocks.
12.6.32. SOWCR 774

12.6.33 SOGCR


Section
This keyword defines critical oil-to-gas saturation for grid blocks, used for saturation end
Default: critical oil-to-gas saturation in corresponding saturation region, i.e. maximal oil
saturation in SGOF (see 12.6.2), for which the oil relative permeability is zero: krOG = 0.
Example
DIMENS
5 5 4
/
...
SOGCR
50*0.35 50*0.45
/
This example defines critical oil-to-gas saturation = 0.35 for first 50 blocks of the grid
and 0.45 for last 50 blocks.
12.6.33. SOGCR 775

12.6.34 SWU


Section
This keyword defines maximal water saturation for grid blocks, used for saturation end
Default: maximal water saturation in corresponding saturation region, i.e. maximal value
of water saturation in SWOF (see 12.6.1).
Example
DIMENS
5 5 4
/
...
SWU
50*0.75 50*0.85
/
This example defines maximal water saturation = 0.75 for first 50 blocks of the grid and
12.6.34. SWU 776

12.6.35 SGU


Section
This keyword defines maximal gas saturation for grid blocks, used for saturation end
Default: maximal gas saturation in corresponding saturation region, i.e. maximal value of
gas saturation in SGOF (see 12.6.2).
Example
DIMENS
5 5 4
/
...
SGU
50*0.75 50*0.85
/
This example defines maximal gas saturation = 0.75 for first 50 blocks of the grid and
12.6.35. SGU 777

12.6.36 ISGL, ISGCR, ISGU, ISWL, ISWLPC, ISWCR, ISWU, ISOGCR, ISOWCR


Section
These keywords are used in scaling the imbibition saturation table (hysteresis option
description 2.6.11):
ISGL minimal (connate) gas saturation (for drainage process this value is specified
via the keyword SGL (see 12.6.29));
ISGCR critical gas saturation (for drainage process this value is specified via the
keyword SGCR (see 12.6.31));
ISGU maximal gas saturation (for drainage process this value is specified via the
keyword SGU (see 12.6.35));
ISWL minimal (connate) water saturation (for drainage process this value is specified
via the keyword SWL (see 12.6.27));
ISWLPC minimal (connate) water saturation for capillary pressure Pc curve scal-
ing only (for drainage process this value is specified via the keyword SWLPC (see
12.6.28));
ISWCR critical water saturation (for drainage process this value is specified via the
keyword SWCR (see 12.6.30));
ISWU maximal water saturation (for drainage process this value is specified via the
keyword SWU (see 12.6.34));
ISOGCR critical oil saturation in oil-gas system (for drainage process this value is
specified via the keyword SOGCR (see 12.6.33));
ISOWCR critical oil saturation in oil-water system (for drainage process this value is
specified via the keyword SOWCR (see 12.6.32)).
The values should be specified for all grid blocks, they will be used for saturation end
point scaling in hysteresis option. The data should be terminated with a slash /.
The keywords can only be used if the keywords ENDSCALE (see 12.6.24) and SATOPTS
(see 12.1.68) are present.
12.6.36. ISGL, ISGCR, ISGU, ISWL, ISWLPC, ISWCR, ISWU, ISOGCR, ISOWCR 778
12.6.37 SCALELIM


Section
The keyword sets limits for saturation table scaling.

The number of numbers should be equal to the 3-rd parameter of the keyword ENDSCALE
(see 12.6.24). Each line should be terminated with a slash /.
These limits are applies only for water relative permeability calculations. the keyword
specifies the upper limit of the value 1 SOWCR .
Example
SCALELIM
0.15 /
0.18 /
0.13 /
12.6.37. SCALELIM 779

12.6.38 ENPTVD


Section
The keyword specifies saturation end point versus depth tables. The number of tables
should not be greater then 3-rd parameter of the keyword ENDSCALE (see 12.6.24). Each
table should be terminated with a slash /.
One table row should contain the following parameters:
1. depth (METRIC: m, FIELD: f t );
2. the corresponding value of connate water saturation (if table end-points are entered cell
by cell the keyword SWL (see 12.6.27) can be used);
3. the corresponding value of critical water saturation (if table end-points are entered cell
by cell the keyword SWCR (see 12.6.30) can be used);
4. the corresponding value of maximum water saturation (if table end-points are entered
cell by cell the keyword SWU (see 12.6.34) can be used);
5. the corresponding value of connate gas saturation (if table end-points are entered cell
by cell the keyword SGL (see 12.6.29) can be used);
6. the corresponding value of critical gas saturation (if table end-points are entered cell
by cell the keyword SGCR (see 12.6.31) can be used);
7. the corresponding value of maximum gas saturation (if table end-points are entered cell
by cell the keyword SGU (see 12.6.35) can be used);
8. the corresponding value of critical oil-in-water saturation (if table end-points are entered
cell by cell the keyword SOWCR (see 12.6.32) can be used);
9. the corresponding value of critical oil-in-gas saturation (if table end-points are entered
cell by cell the keyword SOGCR (see 12.6.33) can be used).
Each saturation entry (parameters 2-9) should be in the range 0.0 to 1.0 inclusive.
12.6.38. ENPTVD 780

Example
ENDSCALE
2* 1 2 /
...
ENPTVD
1800.0 0.15 0.19 1.0 0.0 0.06 1.0 0.19 0.23
2500.0 0.23 0.23 1.0 0.0 0.06 1.0 0.19 0.23 /
In this example one table is specified.
12.6.38. ENPTVD 781

12.6.39 ENKRVD


Section
The keyword specifies relative permeability end point versus depth tables. The number of
tables should not be greater then 3-rd parameter of the keyword ENDSCALE (see 12.6.24).
Each table should be terminated with a slash /.

2. the corresponding value of maximum water relative permeability (if relative permeabil-
ities are entered cell by cell the keyword KRW (see 12.6.43) can be used);
3. the corresponding value of maximum gas relative permeability (if relative permeabilities
are entered cell by cell the keyword KRG (see 12.6.44) can be used);
4. the corresponding value of maximum oil relative permeability (if relative permeabilities
are entered cell by cell the keyword KRO (see 12.6.42) can be used);
5. water relative permeability at the critical oil (or gas) saturation (if relative permeabilities
are entered cell by cell the keyword KRWR (see 12.6.43) can be used);
6. gas relative permeability at the critical oil (or water) saturation (if relative permeabilities
are entered cell by cell the keyword KRGR (see 12.6.44) can be used);
7. oil relative permeability at the critical gas saturation (if relative permeabilities are
entered cell by cell the keyword KRORG (see 12.6.42) can be used);
8. oil relative permeability at the critical water saturation (if relative permeabilities are
entered cell by cell the keyword KRORW (see 12.6.42) can be used).
Each permeability entry (parameters 2-8) should be in the range 0.0 to 1.0 inclusive.
Example
ENDSCALE
2* 1 2 /
...
ENKRVD
1800.0 0.72 1.0 1.0 0.324 2* 0.35
2600.0 0.78 0.94 0.95 0.358 2* 0.36 /
12.6.39. ENKRVD 782

12.6.39. ENKRVD 783

12.6.40 ENPCVD


Section
The keyword specifies maximum capillary pressure versus depth tables. The number of
tables should not be greater then 3-rd parameter of the keyword ENDSCALE (see 12.6.24).
2. the corresponding value of maximum gas-oil capillary pressure (if capillary pressures
are entered cell by cell the keyword PCG (see 12.6.47) can be used) (METRIC:
bars, FIELD: psi);
3. the corresponding value of maximum water-oil capillary pressure (if capillary pressures
are entered cell by cell the keyword PCW (see 12.6.46) can be used) (METRIC:
bars, FIELD: psi).
Example
ENDSCALE
2* 1 2 /
...
ENPCVD
1500.0 0.11 1.52
2000.0 0.1 1.86
2300.0 0.09 2.14 /
12.6.40. ENPCVD 784

12.6.41 ENPTRC


Section
The keyword specifies end-point scaling tables from tracer concentration (salt, surfactant).
Surfactants section 2.25.
These chemical agents are injected to the formation as an admixture to the phase (water
in case of surfactants, oil in case of solvents) and they change the oil-water surface tension.
In tNavigator admixture (surfactants, salts, any other tracers) influence to surface tension is
simulated using relative phase permeability scaling ENPTRC.
Combinations of end-points arrays.
To specify option of combining end-points arrays (Tracer-independent (salt, surfactant) end-
points and tracer-dependent (salt, surfactant) end-points) one can set 5-th parameter of END-
SCALE (see 12.6.24) equal to 2.
Tracer-independent (salt, surfactant) end-points are combined with tracer-dependent end-
points where table columns values are specified as non-defaulted.
For combination with tracer-dependent (salt, surfactant) end-points: a scaling factor is taken
the following way: the resulting value at the lowest temperature in the table will correspond
to the original value in the grid block.

The number of tables is equal to the number of end-point scaling of relative permeabilities
regions. For ENPTRC one should specify the keyword ENDSCALE (see 12.6.24).
The tables contain the following parameters:
1. tracer name (for salts SALT, for surfactants SURFACTANT);
2. one of 8 saturation end-points: SWL (see 12.6.27), SWCR (see 12.6.30), SWU (see
12.6.34), SGL (see 12.6.29), SGCR (see 12.6.31), SGU (see 12.6.35), SOWCR (see
12.6.32), SOGCR (see 12.6.33).
Then the table should be entered, one table row contains parameters:
1. tracer concentration (in the case of tracer: values from 0 to 1; in the case of salts
or surfactants units are METRIC: kg/sm3 , FIELD: lb/stb);
2. the value of the corresponding end-point.
12.6.41. ENPTRC 785

Example
ENPTRC
SURFACTANT SOWCR
0.0 0.2
100.0 0.15 /
In this example there is one table for surfactant and SOWCR. When surfactant concen-
tration in grid block is 100 kg/sm3 the value of the end-points SOWCR is 0.15.
Example
ENPTRC
TRACERWAT1 SOWCR
0.0 0.2
0.1 0.18
0.25 0.16
1 0.16 /
In this example there is one table for tracer and SOWCR. When tracer concentration in
grid block is 0.1 (10%) the value of the end-points SOWCR is 0.18. When tracer concentration
in grid block is 0.25 (25%) the value of the end-points SOWCR is 0.16 (that stays 0.16 if
tracer concentration increases to 1).
12.6.41. ENPTRC 786

12.6.42 KRO, KRORW, KRORG


Section
These keywords define:
KRO maximal oil relative permeability;
KRORG oil relative permeability at the critical gas saturation;
KRORW oil relative permeability at the critical water saturation.
point scaling.
Keywords may be used only if ENDSCALE (see 12.6.24) is present in data file. See
Default: value of relative permeability from table for corresponding saturation.
Example
DIMENS
5 5 4
/
...
KRO
50*0.9 50*1.
/
KRORW
50*0.5 50*0.4
/
This example defines maximal relative permeability to oil as 0.9 for first 50 blocks of the
grid and 1 for last 50 blocks. Relative permeability at critical saturation of displacing phase
is equal to 0.5 and 0.4 correspondingly.
12.6.42. KRO, KRORW, KRORG 787

12.6.43 KRW, KRWR


Section
KRW maximal water relative permeability;
KRWR water relative permeability at the residual oil (of residual gas in gas-water
system).
If KRWR is not set, but KRW is set, then only KRW will be uniformly used for scaling
(see the formula 2.23).
point scaling.
Example
DIMENS
5 5 4
/
...
KRW
50*0.9 50*1.
/
KRWR
50*0.5 50*0.4
/
This example defines maximal relative permeability to water as 0.9 for first 50 blocks
of the grid and 1 for last 50 blocks. Relative permeability at critical saturation of displacing
phase is equal to 0.5 and 0.4 correspondingly.
12.6.43. KRW, KRWR 788

12.6.44 KRG, KRGR


Section
KRG maximal gas relative permeability;
KRGR gas relative permeability at the residual oil (of residual water in gas-water
system).
If KRGR is not set, but KRG is set, then only KRG will be uniformly used for scaling
(see the formula 2.28).
point scaling.
Example
DIMENS
5 5 4
/
...
KRG
50*0.9 50*1.
/
KRGR
50*0.5 50*0.4
/
This example defines maximal relative permeability to gas as 0.9 for first 50 blocks of
the grid and 1 for last 50 blocks. Relative permeability at critical saturation of displacing
phase is equal to 0.5 and 0.4 correspondingly.
12.6.44. KRG, KRGR 789

12.6.45 IKRG, IKRGR, IKRW, IKRWR, IKRO, IKRORW, IKRORG


Section
These keywords specify imbibition (hysteresis option 2.6.11) end-point relative perme-
abilities:
IKRG maximal gas relative permeability (for drainage process this value is specified
via the keyword KRG (see 12.6.44));
IKRGR gas relative permeability at the residual oil (of residual water in gas-water sys-
tem) (for drainage process this value is specified via the keyword KRGR (see 12.6.44));
IKRW maximal water relative permeability (for drainage process this value is specified
via the keyword KRW (see 12.6.43));
IKRWR water relative permeability at the residual oil (of residual gas in gas-water
system) (for drainage process this value is specified via the keyword KRWR (see
12.6.43));
IKRO maximal oil relative permeability (for drainage process this value is specified
via the keyword KRO (see 12.6.42));
IKRORG oil relative permeability at the critical gas saturation (for drainage process
this value is specified via the keyword KRORG (see 12.6.42));
IKRORW oil relative permeability at the critical water saturation (for drainage process
this value is specified via the keyword KRORW (see 12.6.42)).
point scaling in hysteresis option. The data should be terminated with a slash /.
The keywords can only be used if the keywords ENDSCALE (see 12.6.24) and SATOPTS
(see 12.1.68) are present.
12.6.45. IKRG, IKRGR, IKRW, IKRWR, IKRO, IKRORW, IKRORG 790

12.6.46 PCW


Section
This keyword defines maximal oil-water capillary pressure (METRIC: bars, FIELD: psi)
for grid blocks, used for saturation end point scaling. Keyword may be used only if END-
SCALE (see 12.6.24) is present in data file. See 2.15.3 for details.
The same number of values as number of cells must be specified.
Default: maximal oil-water capillary pressure in corresponding saturation region, i.e.

maximum capillary pressure from table SWOF (see 12.6.1).
Note: If the keyword SWATINIT (see 12.6.48) is specified then the values specified via
PCW (see 12.6.46), will be ignored. The keyword PPCWMAX (see 12.6.49) can be used to
specify maximum values of capillary pressure in saturation regions.
Example
DIMENS
5 5 4
/
...
PCW
50*5 50*3
/
This example defines maximal oil-water capillary pressure = 5 for first 50 blocks of the
grid and 3 for last 50 blocks.
12.6.46. PCW 791

12.6.47 PCG


Section
This keyword defines maximal oil-gas capillary pressure (METRIC: bars, FIELD: psi)
for grid blocks, used for saturation end point scaling. Keyword may be used only if END-
SCALE (see 12.6.24) is present in data file. See 2.15.3 for details.
Default: maximal oil-gas capillary pressure in corresponding saturation region, i.e. maxi-
mum capillary pressure from table SGOF (see 12.6.2).
Example
DIMENS
5 5 4
/
...
PCG
50*5 50*3
/
This example defines maximal oil-gas capillary pressure = 5 for first 50 blocks of the
grid and 3 for last 50 blocks.
12.6.47. PCG 792

12.6.48 SWATINIT


Section
This keyword defines initial water saturation for grid blocks, set up using saturation end
point scaling. Water capillary pressure will be scaled in order to make equilibrium water
saturation equal to indicated one (this means that EQUIL (see 12.15.2) should be used for
initialization). When SWATINIT is used, maximum capillary pressure array PCW is generated
(see 2.15.3 for details). Water saturation set up by SWATINIT will not always be honored,
especially for the case when division by zero should be performed to scale pressure (see
notes).
The keyword PPCWMAX (see 12.6.49) can be used to specify maximum values of cap-
illary pressure in saturation regions PPCWMAX (see 12.6.49).
Keyword may be used only if ENDSCALE (see 12.6.24) is present in data file.
Notes:
For grid blocks below oil water contact, where capillary pressure is zero, if SWATINIT
saturation is set below 1.0, it will not be honored.
For grid blocks above oil water contact, if SWATINIT saturation is set to value corre-
sponding to zero Pcw (usually its SW = 1.0), it will not be honored.
If SWATINIT saturation is less or equal to connate water saturation, it will not be

honored.
If 9th argument in EQUIL (see 12.15.2) is not set to zero, SWATINIT saturation will
not exactly be honored due to fine layer equilibrium calculation.
If PCW (see 12.6.46) keyword is set, its values will be ignored.
If JFUNC (see 12.2.58) keyword is used, maximum capillary pressures Pcw calculated
from it will be ignored.
12.6.48. SWATINIT 793

Example
DIMENS
5 5 4
/
...
SWATINIT
50*0.05 25*0.3 25*1
/
This example defines initial water saturation = 0.05 for first 50 blocks of the grid, 0.3 for
next layer, 1 for bottom layer.
12.6.48. SWATINIT 794

12.6.49 PPCWMAX


Section
This keyword sets the limit of calculated capillary pressure values for saturation regions.
This value is used in capillary pressure curves scaling when initial water distribution is set
via SWATINIT (see 12.6.48) (If the input water saturation is above the connate saturation
in blocks above the transition zone, then the scaling of capillary pressure curve may lead to
capillary pressure values).
The number of data lines shouldnt be greater than the 1-st parameter of the keyword
TABDIMS (see 12.1.26) (number of saturation regions). Each data line should be terminated
with a slash /.
1. maximum capillary pressure in the saturation region (the value should be greater than
the maximum capillary pressure in the corresponding saturation function table) (MET-
RIC: barsa, FIELD: psia);
2. flag YES or NO (connate saturation should be modified to correspond to the input

water saturation (SWATINIT (see 12.6.48)) when the capillary pressure is above the
maximum value)
YES capillary pressure is set via saturation tables values, connate saturation is
set to the value, specified via SWATINIT (see 12.6.48);
NO input saturation values (SWATINIT (see 12.6.48)) will not correspond in
blocks, where the capillary pressure is above the maximum value.
Default: NO.
Example
PPCWMAX
0.73 YES /
0.50 YES /
0.68 YES /
In this example maximum capillary pressure is specified for 3 saturation regions.
12.6.49. PPCWMAX 795

12.6.50 EHYSTR


Section
This keyword is used to specify phase permeabilities hysteresis 2.6.11.
Hysteresis curvature parameters for saturation regions (SATNUM (see 12.4.3)) can be set
via the keyword EHYSTRR (see 12.6.51).
/.):
1. curvature parameter for capillary pressure hysteresis (in the range from 0.005 to 0.1);
2. a number specified phase permeabilities hysteresis model (capillary pressure hystere-

sis uses the Killough model): tNavigator supports the following water wet hysteresis
models:
0 Carlsons Hysteresis model used for the non-wetting phase(s), drainage (SAT-
1 Carlsons Hysteresis model used for the non-wetting phase(s), imbibition
(IMBNUM (see 12.4.7)) curve used for the wetting phase.
2 Killoughs Hysteresis model used for the non-wetting phase(s), drainage (SAT-
3 Killoughs Hysteresis model used for the non-wetting phase(s), imbibition
(IMBNUM (see 12.4.7)) curve used for the wetting phase.
4 Killoughs hysteresis model used for both wetting and non-wetting phases.
5 Carlsons non-wetting model for gas and water phases, drainage (SATNUM
6 Killoughs non-wetting model for the gas and water phases, drainage (SAT-
7 Killoughs Hysteresis Model used for the non-wetting gas and water phases
and the wetting oil phase.
8 Jargons Hysteresis Model used for the non-wetting phase, drainage (SATNUM
9 Jargons Hysteresis Model used for the non-wetting phase, imbibition (IMB-
12.6.50. EHYSTR 796

-1 Only equilibration option. If this option is used then the model is equilibrated
using the drainage curve (SATNUM (see 12.4.3)) but the simulation uses the
imbibition curve (IMBNUM (see 12.4.7)).
3. curvature parameter for Killoughs wetting phase relative permeability hysteresis (pos-
itive number);
4. modification parameter for the trapped non-wetting phase saturation in the Killough
model.
5. flag that defines to which parameters hysteresis will be used: only RP, only capillary
pressure or both:
BOTH hysteresis is applied to both RP and capillary pressure. For RP the model,
specified via parameter 2, will be used; for capillary pressure - Killough model.
PC hysteresis is applied to capillary pressure only, Killough model will be used.
KR hysteresis is applied to RP only; the hysteresis model, specified via parameter
2, will be used.
6. IGNORED. This is an Eclipse compatibility field;
7. IGNORED. This is an Eclipse compatibility field;
8. select the wetting phase in models of black-oil type:
OIL oil is wetting to gas;
GAS oil is non-wetting to gas.
Default:
curvature parameter for capillary pressure hysteresis 0.1;
a number specified phase permeabilities hysteresis model 0;
curvature parameter for Killoughs wetting phase relative permeability hysteresis (pos-
itive number) 1;
modification parameter for the trapped non-wetting phase saturation in the Killough
model 0.1;
flag that defines to which parameters hysteresis will be used: only RP, only capillary
pressure or both BOTH;
select the wetting phase in models of black-oil type: OIL.
Example
EHYSTR
0.07 0 1 0.1 /
12.6.50. EHYSTR 797

12.6.51 EHYSTRR


Section
This keyword is used to specify phase permeabilities hysteresis 2.6.11.

The keyword sets hysteresis curvature parameters for saturation regions (SATNUM (see
12.4.3)). The data for each region should be terminated with a slash /.
This keyword overrides the data specified via EHYSTR (see 12.6.50).
1. curvature parameter for capillary pressure hysteresis (in the range from 0.005 to 0.1);
2. curvature parameter for Killoughs wetting phase relative permeability hysteresis (pos-
itive number). This parameter will be used only in the case when parameter 2 of the
keyword EHYSTR (see 12.6.50) is equal 4 (Killoughs hysteresis model used for both
wetting and non-wetting phases);
3. modification parameter for the trapped non-wetting phase saturation in the Killough
model.
Default:
curvature parameter for capillary pressure hysteresis 0.1;
a number specified phase permeabilities hysteresis model 0;
curvature parameter for Killoughs wetting phase relative permeability hysteresis (pos-
itive number) 1.
Example
EHYSTRR
0.06 1.0 0.1 /
0.08 1.0 0.1 /
In this example the data is set for 2 regions.
12.6.51. EHYSTRR 798

12.6.52 DRAINAGE


Section
The keyword is activating drainage option in hysteresis 2.6.11.

It specifies that K r values obtained in the hysteresis option should lie on or below drainage
curve.
12.6.52. DRAINAGE 799

12.6.53 MISCSTR


Section
This keywords specifies the miscibility reference surface tension 2.6.12. One should
use the keyword MISCSTRR (see 12.6.54) to set the miscibility reference surface tension for
each saturation region.

N
F =( )
0
0 reference surface tension.

permeabilities :
/.):
1. reference surface tension (Dynes/cm);
2. maximum expected surface tension. IGNORED. This is an Eclipse compatibility field
3. maximum surface tension that is used to scale the input capillary pressure curves.
IGNORED. This is an Eclipse compatibility field
Example
MISCSTR
49 /
12.6.53. MISCSTR 800

12.6.54 MISCSTRR


Section
This keywords specifies the miscibility reference surface tension for saturation regions
2.6.12. One should use the keyword MISCSTR (see 12.6.53) to set the miscibility reference
surface tension for the whole reservoir.

N
F =( )
0
0 reference surface tension.

permeabilities :
The number of lines should be equal to the number of saturation regions. The data for
each saturation region should be terminates with a slash /.
One data row contains the following parameters:
1. reference surface tension (Dynes/cm);
2. maximum expected surface tension. IGNORED. This is an Eclipse compatibility field
3. maximum surface tension that is used to scale the input capillary pressure curves.
IGNORED. This is an Eclipse compatibility field
Example
MISCSTRR
49 /
40 /
38 /
12.6.54. MISCSTRR 801

12.6.55 MISCEXP


Section
This keyword specified the miscibility exponent (2.6.12).

N
F =( )
0
0 reference surface tension (specified via MISCSTR (see 12.6.53)).

permeabilities :
Example
MISCEXP
0.2 /
12.6.55. MISCEXP 802

12.6.56 PARACHOR


Section
The keyword specifies component parachors (Dynes1/4 cm11/4 /moles).

They should be specified in the case if surface tension should be calculated 2.6.12.
The same number of values as the number of components in the model should be entered
(COMPS (see 12.13.3)). The data should be terminated with a slash /.
Example
COMPS
3/
...
PARACHOR
74.92 192.74 390.4 /
12.6.56. PARACHOR 803

12.6.57 STOG


Section
The keyword sets table of surface tension dependence on pressure in oil-gas system.
This keyword should be used with the option SURFTENS of the keyword SATOPTS (see
12.1.68). The number of tables of this keyword is specified by 2-nd parameter of the keyword
TABDIMS (see 12.1.26). The number of lines in each table should be not less than 2 and
not less than the value of the 4-th parameter of TABDIMS (see 12.1.26).
in the next after the keyword line:
1. oil phase reference pressure (METRIC: bar , FIELD: psi). The data should be
in the following lines table is set. In each line of it the following parameters should be
specified.
1. oil phase pressure (METRIC: bar , FIELD: psi). Values should be strictly in-
creased from line to line;
2. surface tension in oil-gas system at specified pressure (METRIC: N/m, FIELD:
lb f /in).
The last line of table should be ended by a symbol /.
Example
STOG
100 /
100 1
1000 12
2000 14 /
In the example via the keyword STOG (see 12.6.57) one table of surface tension depen-
dence on pressure in oil-gas system is set. Oil reference pressure is 100 psi.
12.6.57. STOG 804

12.6.58 STOW


Section
The keyword sets table of surface tension dependence on pressure in oil-water system.
This keyword should be used with the option SURFTENS of the keyword SATOPTS (see
12.1.68). The number of tables of this keyword is specified by 2-nd parameter of the keyword
TABDIMS (see 12.1.26). The number of lines in each table should be not less than 2 and
not less than the value of the 4-th parameter of TABDIMS (see 12.1.26).
in the next after the keyword line:
1. oil phase reference pressure (METRIC: bar , FIELD: psi). The data should be
in the following lines table is set. In each line of it the following parameters should be
specified.
1. oil phase pressure (METRIC: bar , FIELD: psi). Values should be strictly in-
creased from line to line;
2. surface tension in oil-water system at specified pressure (METRIC: N/m, FIELD:
lb f /in).
The last line of table should be ended by a symbol /.
Example
STOW
100 /
100 1
1000 12
2000 14 /
In the example via the keyword STOG (see 12.6.57) one table of surface tension depen-
dence on pressure in oil-water system is set. Oil reference pressure is 100 psi.
12.6.58. STOW 805

12.6.59 KRSMOOTH


Section
The keyword specifies smoothing type for Krw , Krow , Krg , Krog which are set via
tables. Smoothing is performed by several types of splines.
Possible spline types:
LINEAR linear spline;
QUAD quadratic spline;
CUBIC cubic spline.
Note. If options QUAD or CUBIC are used then smooting is made only in the interval,
where RP value in one its end point is 0, and the second end point is the first point where
RP value is not 0.
Any number of data lines can be specified. Each line specifies data in corresponding
region. One data line should contain the following data:
1. smoothing type for Krw ;
2. smoothing type for Krow ;
3. smoothing type for Krg ;
4. smoothing type for Krog .
Line of data should be ended by a symbol /. The data should be terminated with a slash /.
Default:
LINEAR for each parameter.
This keyword has an alalogue for model in syntax IMEX, STARS: the option
SMOOTHEND in the keywords SWT (see 13.6.3), SLT (see 13.6.4), SGT (see 13.6.5).
Example
KRSMOOTH
LINEAR LINEAR LINEAR QUAD /
QUAD LINEAR LINEAR QUAD /
/
In the example smoothing types for Krw , Krow , Krg , Krog in two regions are set.
12.6.59. KRSMOOTH 806

12.7. Salts and tracers tNavigator-4.2
12.7 Salts and tracers

This section contains the keywords for salt and tracer properties description.
12.7. Salts and tracers 807

12.7.1 TRACER


Section
The keyword sets passive tracers. In e100 each tracer is associated with one of three
phases (water, oil, gas). In e300 each tracer is associated with one hydrocarbon component
or water. In tNavigator each tracer is associated with one hydrocarbon component or water.
For each tracer the data line should be specified. Each line should be terminated with a
Each line should consist of the following parameters:
1. tracer name (in Eclipse tracer name may consist of up to 3 characters, but in tNavigator
tracer name may consist of any number of characters),
2. the name of the fluid associated with the tracer: e100 OIL, WAT, GAS; e300
hydrocarbon component name or WATER,
3. units for tracer amount (this parameter is optional and is used for reporting only),
4. ignored, this is an Eclipse compatibility field(this parameter is specified for partitioned

tracers only),
5. ignored, this is an Eclipse compatibility field(this parameter is specified for partitioned

tracers only).
Example
TRACER
A WAT /
B WAT /
C OIL /
/
In this example there are 3 tracers: tracers A and B are associated with water, tracer C
with oil.
12.7.1. TRACER 808

12.7.2 TRACERM


Section
The keyword sets passive tracers for which the holding time in the reservoir will be
calculated.
Tracer name should be specified in its own new line and be terminated with a slash /.
The data should be terminated with a final slash /.
Example
TRACER
A WAT /
B WAT /
/
...
TRACERM
A /
B /
/
In this example there are 2 tracers A and B for which the holding time in the reservoir
will be calculated.
12.7.2. TRACERM 809

12.7.3 TRACEROPTS


Section
The keyword sets passive tracers and parameters of their method calculation. The key-
word can be used in black oil and compositional models for all passive tracers, API and for
waters with different salinities simulation.
Each line should be terminated with a slash /. The data should be terminated with a final
slash /.
1. tracer name;
2. parameters of tracer method calculation:
FI fully implicit;
EXP explicit; conservation equation for mixture (API, salt, passive tracer) is
solving at the end of timestep.
Default:
parameters of tracer method calculation:
for API and salts with option BRINE (see 12.1.58): FI;
for other tracers and salts, if polymer is used in a model (the keyword POLYMER
(see 12.1.48)): EXP.
Example
TRACER
A1 WAT /
B1 WAT /
/
...
TRACEROPTS
A1 FI /
B1 FI /
/
In this example fully implicit calculation will be used for 2 tracers A1 and B1.
12.7.3. TRACEROPTS 810

12.7.4 SALTPROP


Section
The keyword sets properties of dissolved and reservoir salt. The keyword can be used
only for runs in which the Brine option is active (the keyword BRINE (see 12.1.58)).
Number of data records depends on number of PVT regions (defined in TABDIMS (see
12.1.26)). Each data record contains data for one PVT region and should be terminated with
a slash /. All data should be terminated with a final slash /.
One data record consists of the following parameters:
1. ultimate concentration of dissolved (in the water) salt (concentration of saturated salt
solution) (METRIC: kg/sm3 , FIELD: lb/stb);
2. density of reservoir salt at reference pressure pre f (specified via the keyword ROCK
(see 12.5.16)) i.e. we suppose that reservoir salt compressibility is equal to rock
compressibility (METRIC: kg/sm3 , FIELD: lb/ f t 3 );
3. solution rate constant of reservoir salt salt (1/day).
Then the solution rate of reservoir salt vsalt (kg/day) in the volume V will be calculated
via formula:
vsalt = salt (mmax mcur ) ,
where mcur current salt quantity in the solution (kg), mmax salt quantity in the saturated
salt solution (kg) in the volume V .
Default:
ultimate concentration of dissolved (in the water) salt 300 kg/sm3 ;
density of reservoir salt at reference pressure 2165 kg/sm3 ;
solution rate constant of reservoir salt 0 (1/day).
Example
SALTPROP
350 2165 0.0001
/
12.7.4. SALTPROP 811

12.7.5 SALTTRM


Section
The keyword sets the dependence between permeability and amount of dissolved reservoir
salt. The keyword can be used only for runs in which the Brine option is active (the keyword
BRINE (see 12.1.58)).
Number of tables depends on number of PVT regions (defined in TABDIMS (see

12.1.26)). Each table contains data for one PVT region and should be terminated with a
slash /. All data should be terminated with a final slash /.
One table row consists of the following parameters:
1. ratio of the volume of dissolved reservoir salt to the initial volume of rock in the cell;
2. absolute permeability multiplier.
Example
SALTTRM
0.0 1
0.01 10
0.1 100
0.4 400
0.5 500
/
In this example one table is specified for one PVT region.
12.7.5. SALTTRM 812

12.7.6 SALTNODE


Section
The keyword defines salt concentration that is used in polymer solution viscosity calcu-
lations.
Data is represented as tables, which number is specified by parameter 2 of the keyword
TABDIMS (see 12.1.26). Each table should be terminated with a slash /. Tables set the
nodal values for salt concentration that will be used in the calculation of the polymer solution
viscosity.
Each table contains salt concentration values. The number of these values should not be
greater than value of parameter 4 of the keyword TABDIMS (see 12.1.26). Values must be
positive and strictly increasing.
The number of lines in each table must correspond to the number of polymer solution
viscosity lines (the keyword PLYVISCS (see 12.7.8)).
Each line of each table should contain the following parameters:
1. salt concentration (METRIC: kg/m3 , FIELD: lb/stb);
Example
SALTNODE
.0
40.0
80.0
120.0 /
40.0
120.0 /
In the example 2 tables of salt concentration values are specified. The first table contains
4 lines, the second one contains 2 lines.
12.7.6. SALTNODE 813

12.7.7 ESSNODE


Section
The keyword sets tables of salt concentration values which will be used to set surface
tension in oil-water system (the keyword SURFSTES (see 12.8.15)). The number of tables
is determined by the 2-nd parameter of the keyword TABDIMS (see 12.1.26). The number
of lines in each table shouldnt exceed the value of the 4-th parameter of keyword TABDIMS
(see 12.1.26) and must be equal to the number of data lines which sets surface tension.
Values in each table must be strictly increased.
Each table should be ended by a symbol /.
1. salt concentration values (METRIC: kg/sm3 ; FIELD: lb/stb).
Example
ESSNODE
11.1
15.36
19.56 /
In the example one table of 3 values of salt concentration is set.
12.7.7. ESSNODE 814

12.7.8 PLYVISCS


Section
The keyword should be used only in the BRINE (see 12.1.58) option (mixing of waters
with different salinities).
This keyword sets polymer/salt solution viscosity function as a table. Functions describe
the effect on the viscosity of pure water of increasing the concentration of polymer and salt
in the solution. The number of functions is set by parameter 2 of the keyword TABDIMS (see
12.1.26). Each table should be ended by a symbol /. The number of data sets must not be
greater than value of the parameter 4 of the keyword TABDIMS (see 12.1.26). The number
of data lines in each set also must not be greater than value of this parameter.
First line of one data set should contain the following parameters:
1. polymer concentration in the solution. Its values should be strictly increasing. The first
value should be equal to 0 (METRIC: kg/m3 , FIELD: lb/stb);
2. corresponding factor by which the water viscosity (the keyword PVTW (see 12.5.5)),
has to be multiplied to give the viscosity of a fully mixed solution of polymer/salt
at a polymer concentration given by parameter 1 and a salt concentration given by
parameter 1 in the corresponding salinity table (SALTNODE (see 12.7.6)).
Other lines of one set (overall value of them is equal to the parameter 4 of the keyword
TABDIMS (see 12.1.26)) contains of the 2-nd parameter only.
12.7.8. PLYVISCS 815

Example
PLYVISCS
0.0 1.0
1.0
1.0
1.0 /
0.1 1.10
1.08
1.06
1.04 /
0.2 1.32
1.26
1.20
1.10 /
0.3 1.59
1.50
1.40
1.30 /
/
0.00 1.0
1.0 /
0.2 1.32
1.10 /
/
In the example 2 polymer/salt solution viscosity functions are defined. They corresponds
to tables which are specified by the keyword SALTNODE (see 12.7.6) (see example).
12.7.8. PLYVISCS 816

12.7.9 BDENSITY


Section
The keyword specifies the brine surface density variation with the salt concentration. The
keyword can be used only for runs in which the Brine option is active (the keyword BRINE
(see 12.1.58)).
If the keyword is not specified, the surface density of water is taken which is specified via
DENSITY (see 12.5.23).
The data comprises a number of data lines equal to the 2-nd parameter of TABDIMS (see
12.1.26), each data line should be terminated with a slash (/). Each data line consists of water
surface density values (METRIC: kg/sm3 , FIELD: lb/ f t 3 ). The density values in data line
correspond to the salt concentration in column 1 of each table in the keyword PVTWSALT
(see 12.7.14).
Example
BDENSITY
1200 1213 /
1215 1217 1220 /
PVTWSALT
350 0.0 /
0.00 1.00 4E-005 0.52 0.0
160.00 0.98 8E-005 0.52 0.0 /
400 0.0 /
0.0 1.02 4.00E-06 0.52 0.0
20 1.00 4.00E-06 0.52 0.0
50 0.96 4.00E-06 0.52 0.0 /
/
12.7.9. BDENSITY 817

12.7.10 TRMMULTC


Section
The keyword sets the dependence between absolute permeability multiplier and tracer
concentration (kconc in 2.20.2), for which the option of holding time calculation in the reser-
voir is enabled, (keyword TRACERM (see 12.7.2)).
One should specify tracer name and the following data:
1. tracer concentration (Tconc );
2. function kconc (Tconc ).
Then the final permeability multiplier will be calculated via the formula:
kmult = 1 (1 kconc (Tconc ))(1 ktime (t)),
where ktime (t) is set using the keyword TRMMULTT (see 12.7.11). Dependences between
absolute permeability multiplier and tracer concentration should be entered as a table and be
terminated with a slash /. The data should be terminated with a final slash /.
12.7.10. TRMMULTC 818

Example
TRACERM
A /
Bw /
/
...
TRMMULTC
A
0.1 1.0
0.2 0.9
0.5 0.3 /
BW
0 1
0.05 0.3
0.1 0.25
0.15 0.2
0.2 0.15
0.25 0.1
0.3 0.09
0.35 0.08
0.4 0.07 / /
In this example the dependence between absolute permeability multiplier and tracer con-
centration is specified for two tracers A and Bw.
12.7.10. TRMMULTC 819

12.7.11 TRMMULTT


Section
The keyword sets the dependence between absolute permeability multiplier and holding
time in the reservoir (keyword TRACERM (see 12.7.2)).
1. holding time in the reservoir (t );
2. function ktime (t).
Then the final permeability multiplier will be calculated via the formula:
kmult = 1 (1 kconc (Tconc ))(1 ktime (t)),
where kconc (Tconc ) is set using the keyword TRMMULTC (see 12.7.10). Dependences be-
tween absolute permeability multiplier and holding time should be entered as a table and be
terminated with a slash /. The data should be terminated with a final slash /.
Example
TRACERM
A /
B /
/
...
TRMMULTT
A
0 1.0
1000 0.9 /
/
B
0 1.0
1500 0.8 /
/
In this example the dependence between absolute permeability multiplier and holding
time in the reservoir is specified for two tracers A and B.
12.7.11. TRMMULTT 820

12.7.12 TRMTEMP


Section
The keyword sets the dependence between absolute permeability multiplier and tempera-
ture for polymer models (the final permeability multiplier will be calculated via the formula
in the section 2.20.2). The data should be terminated with a slash /.
1. temperature (METRIC: C, FIELD: F);
2. function ktemp (Tpol ).
Example
TRMTEMP
BW
10 1
20 0.9
60 0.5
70 0.4
90 0.3 /
/
12.7.12. TRMTEMP 821

12.7.13 TRDCY


Section
The keyword sets decay time of tracer. The keyword should be used in the form TRD-
CYXXX where XXX is tracer name which is set via TRACER (see 12.7.1). The number
of data lines must be equal to the value of the 2-nd parameter of keyword TABDIMS (see
12.1.26). Each line applies to its corresponding PVT region (see keyword PVTNUM (see
12.4.2)). The following parameters should be specified:
1. the tracer decay half-life (days).
Each data line should be ended by the symbol /.
Example
TRDCYWAT_1
10.0 /
10.0 /
TRDCYWAT_2
40.0 /
40.0 /
In the example for tracers WAT_1 and WAT_2 in 2 PVT regions decay time is set.
12.7.13. TRDCY 822

12.7.14 PVTWSALT


Section
The keyword supplies the water PVT data for runs in which the Brine option is active
(the keyword BRINE (see 12.1.58)). The keyword is used in place of PVTW (see 12.5.5).
The data consists of tables. The number of tables is equal to the second parameter of the
keyword TABDIMS (see 12.1.26). Each table consists of two data records, each terminated
by a slash (/).
First data record:
1. reference pressure (Pre f ) for this table (METRIC: barsa, FIELD: psia);
2. reference salt concentration for stock tank water (METRIC: kg/sm3 , FIELD: lb/ f t 3 ).
Second data record (one table row consists of):
1. the salt concentration (METRIC: kg/sm3 , FIELD: lb/stb);
2. the water formation volume factor at the reference pressure as a function of salt con-
centration Bw (Pre f ) (METRIC: rm3 /sm3 , FIELD: rb/stb);
3. the water compressibility C = ( BPw )/Bw (METRIC: 1/bars, FIELD: 1/psi);
4. the water viscosity at the reference pressure w (Pre f );
5. the water viscosibility Cv = ( Pw )/w (METRIC: 1/bars, FIELD: 1/psi).
Example
PVTWSALT
250 0.0 /
0.00 1.00 4E-005 0.52 0.0
160.00 0.98 8E-005 0.52 0.0
/
12.7.14. PVTWSALT 823

12.7.15 LSALTFNC


Section
This keyword sets tables of low-salt weighting factors versus salt concentration. These
factors are used in calculations of water and oil saturation, RP and capillary pressures in
water-oil system.
The keyword is used in low salinity option (LOWSALT (see 12.1.59)) section 2.26.3).
The data consists of tables. The number of tables is equal to the first parameter of the
keyword TABDIMS (see 12.1.26). Each table should be terminated by a slash (/).
1. salt concentration (METRIC: kg/sm3 , FIELD: lb/stb);
2. factor F1 , that is used for the low-salinity saturation endpoints and RP interpolation.
The values can be in the range from 0 to 1. Value 0 sets that only the high-salinity
saturation functions will be used (SATNUM (see 12.4.3)). Value 1 sets that only the
low-salinity saturation functions will be used (LWSLTNUM (see 12.4.6)).
3. factor F2 , that is used for the low-salinity capillary pressure interpolation.

The values can be in the range from 0 to 1. Value 0 sets that only the high-salinity
saturation functions will be used (SATNUM (see 12.4.3)). Value 1 sets that only the
low-salinity saturation functions will be used (LWSLTNUM (see 12.4.6)).
Default:
factor F2 , that is used for the low-salinity capillary pressure interpolation is equal to
F1 .
12.7.15. LSALTFNC 824

Example
LSALTFNC
0 1.0 1*
20 0.5 1*
35 0 1*
/
/
SATNUM
55440*1 /
LWSLTNUM
55440*2 /
In this example all grid blocks belong to region 1 for high salinity case (SATNUM
(see 12.4.3)) and to region 2 for law salinity case (LWSLTNUM (see 12.4.6)). One table
LSALTFNC is specified, second table is defaulted /, it is copied from the 1-st one.
12.7.15. LSALTFNC 825

12.8. EOR: Enhanced Oil Recovery tNavigator-4.2
12.8 EOR: Enhanced Oil Recovery

This section contains keywords for EOR (Enhanced Oil Recovery) methods:
Hydraulic fracture (section 5.8.3): keywords NPROPANTS (see 12.8.1), PROPANT-

NAMES (see 12.8.2), PROPANTTABLE (see 12.8.3), FLOWFUNC (see 12.8.4),
NFLOWFTB (see 12.8.5), FLOWFNAMES (see 12.8.6), FLOWFTAB (see 12.8.7);
Alkaline injection (section 2.24): keywords ALSURFST (see 12.8.23), ALSURFAD

(see 12.8.24), ALPOLADS (see 12.8.25), ALKADS (see 12.8.26), ALKROCK (see
12.8.27);
Surfactant injection (section 2.25): keywords SURFADS (see 12.8.8), SURFST

(see 12.8.9), SURFVISC (see 12.8.10), SURFCAPD (see 12.8.11), SURFROCK (see
12.8.12), SURFADDW (see 12.8.13), SURFDW (see 12.8.14);
Polymer injection (section 2.20): keywords PLYVISC (see 12.8.16), PLYADS (see
12.8.17), PLYMAX (see 12.8.18), PLMIXPAR (see 12.8.19), PLYROCK (see 12.8.20).

12.8. EOR: Enhanced Oil Recovery 826

12.8.1 NPROPANTS


Section
This keywords sets the number of proppants in the model. The data should be terminated
with a slash /.
The description of the matematical model of hydraulic fracture in tNavigator is in the
section Modified well model (5.8).
Example
NPROPANTS
2/
In this example there are 2 proppants.
12.8.1. NPROPANTS 827

12.8.2 PROPANTNAMES


Section
This keyword sets proppant names for all proppants in the model. The same number
of names should be specified as the number of proppants in the model (NPROPANTS
(see 12.8.1)). The data should be terminated with a slash /.
Example
NPROPANTS
2/
PROPANTNAMES
'propant 12/18' ' propant 16/20'/
In this example 2 proppants are specified. 1-st proppant name is 'propant 12/18', 2-nd
proppant name 'propant 16/20'.
12.8.2. PROPANTNAMES 828

12.8.3 PROPANTTABLE


Section
This keyword sets the table of relation between pressure ant proppant permeability.

The number of columns of this table depends on the number of proppants (keyword
NPROPANTS (see 12.8.1)).
1. pressure (FIELD: psi, METRIC: bar);
2. proppant permeability (proppant 1) for the unit of hydraulic fraction length at this
pressure (mD);
3. proppant permeability (proppant 2) for the unit of hydraulic fraction length at this
pressure (mD);
4. ...
5. proppant permeability (proppant NPROPANTS) for the unit of hydraulic fraction length
at this pressure (mD).
An arbitrary number of table rows could be specified with different pressures. The data
Default:
Pressure values couldnt be defaulted.

Permeability values couldnt be defaulted in the first table row. It should be at list 2 non-
defaulted values of permeability. If the value is defaulted the result of linear interpolation
will be used in calculations. Permeability value for the last pressure value in the table should
be zero for all propants (pressure of fraction closing).
12.8.3. PROPANTTABLE 829

Example
NPROPANTS
2/
PROPANTNAMES
'propant 12/18' ' propant 16/20'/
PROPANTTABLE
100 10600 5100
200 * 3900
400 2400 1800
800 200 0
1000 0 *
/
In this example 2 proppants are specified. 1-st proppant name is 'propant 12/18', 2-nd
proppant name 'propant 16/20'.
The table of proppant properties is specified for these two proppants (5 different pressure
values in the table). Default: permeability of 1-st proppant at pressure 200 and permeability
of 2-nd proppant at pressure 1000.
12.8.3. PROPANTTABLE 830

12.8.4 FLOWFUNC


Section
The keyword specifies the coefficients of flow functions (the dependence between per-
meability and flow (or time) in the model 5.8.7).

Function f of dimensionless flow s (a ration of accumulated flow from block to block

pore volume), is the following
1. f (0) = 1;
There are 3 flow function types:
1. Exponential: f (s) = k + (1 k) exp(a s), Parameters: k 0, a > 0 are specified

via this keyword FLOWFUNC (see 12.8.4) (function type EXP).
2. Linear: f (s) = max{1 + (k 1) a s, 0}, Parameters: k 0, a > 0 are specified via

this keyword FLOWFUNC (see 12.8.4) (function type LIN).
3. Tabular: the table (s, f (s)) is specified via the keyword FLOWFTAB (see 12.8.7) (the
number of tabular functions are specified via the keyword NFLOWFTB (see 12.8.5),
tabular function names FLOWFNAMES (see 12.8.6)).
If function is not specified, then f (s) = 1 is considered.
One table row contains the parameters for one function:
1. function name;
2. function type (LIN - linear, EXP - exponential);
3. coefficient k;
4. coefficient a.
12.8.4. FLOWFUNC 831

Each row should be terminated with a slash /. The number of rows should be specified
the same as the sum of linear and exponential functions in the model. The data should be
Example
FLOWFUNC
'Func 1' LIN 0.99726 1 /
'Func 2' EXP 0 0.030197 /
/
In this example there are coefficients for 2 flow functions (Func 1 linear, Func 2
exponential).
12.8.4. FLOWFUNC 832

12.8.5 NFLOWFTB


Section
The keyword specifies the number of tabular flow functions f (s) (the dependence be-
tween permeability and flow (or time) in the model 5.8.7). The data should be terminated
with a slash /.

Function f (s) is the following:
1. f (0) = 1;
Example
NFLOWFTB
2 /
In this example there are 2 tabular flow functions.
12.8.5. NFLOWFTB 833

12.8.6 FLOWFNAMES


Section
The keyword specifies the names of tabular flow functions (the dependence between per-
meability and flow (or time) in the fracture model described in 5.8.7).

The same number of names should be specified as the number of flow functions in the
model (NFLOWFTB (see 12.8.5)). The data should be terminated with a slash /.
Example
NFLOWFTB
2 /
FLOWFNAMES
'Func 5' 'Func 6'/
In this example there are 2 tabular flow functions: Func 5 and Func 6.
12.8.6. FLOWFNAMES 834

12.8.7 FLOWFTAB


Section
The keyword specifies the table of flow functions (the dependence between permeability
and flow (or time) in the model 5.8.7).

Function f (s) is the following:
1. f (0) = 1;
The number of table columns depends on the number of flow functions in the model (the
keyword NFLOWFTB (see 12.8.5)).
1. argument s value;
2. function (number 1) value at the given argument s value;
3. function (number 2) value at the given argument s value;
4. ...
5. function (number NFLOWFTB) value at the given argument s value.
An arbitrary number of table rows could be specified with different argument s values.
Default:
Argument s values couldnt be defaulted.
Function values couldnt be defaulted in the first table row. It should be at list 2 non-defaulted
values.
If the value is defaulted the result of linear interpolation will be used in calculations. The
first value of argument s should be 0. The first function value (for all functions) at zero
argument s value should be 1.
12.8.7. FLOWFTAB 835

Example
NFLOWFTB
2/
FLOWFNAMES
'Func 5' 'Func 6'/
FLOWFTAB
0 1 1
1 0.5 *
2 * 0.5
3 0.1 0.1
/
In this example there are 2 tabular flow functions: Func 5 and Func 6.
The table consists of 4 rows (4 different argument s values).
12.8.7. FLOWFTAB 836

12.8.8 SURFADS


Section
The keyword specifies surfactant adsorption functions (surfactants section 2.25).

Alkaline reduces surfactant adsorption (alkaline flooding section 2.24).

The number of specified tables should be equal to the number of saturation tables (first
parameter of the keyword TABDIMS (see 12.1.26)). Each table should be terminated with a
slash /.
One table row for one surfactant should contain the following parameters:
1. local surfactant concentration in the solution surrounding the rock (METRIC: kg/sm3 ,
FIELD: lb/stb);
2. corresponding saturated concentration of surfactant adsorbed by the rock formation

(METRIC: kg/kg, FIELD: lb/lb).
(The first row of the table should contain two zeroes.)
Example
SURFADS
.000 .000
.0023 .00045
.0065 .00067
.0078 .00078
.00110 .00082 /
12.8.8. SURFADS 837

12.8.9 SURFST


Section
This keyword specifies the table of water-oil surface tension as a function of surfactant
concentration in water (SURFACT (see 12.1.46) section 2.25). Surfactant affects on water-
oil surface tension in combination with alkaline (alkaline flooding section 2.24).

slash /.
1. surfactant concentration in the solution (METRIC: kg/sm3 , FIELD: lb/stb);
2. value of water-oil surface tension (METRIC: N/m, FIELD: lb f /in).
Example
SURFST
0.000 9.5
0.030 6.0
0.040 1.0
0.044 0.3 /
0.000 8.0
0.030 5.0
0.040 0.7
0.044 0.3 /
In this example there are 2 tables.
12.8.9. SURFST 838

12.8.10 SURFVISC


Section
This keyword specifies the table of water solution viscosity as a function of surfactant
concentration (SURFACT (see 12.1.46) section 2.25).

If the Polymer Flooding is used then the value, that is specified in this keyword viscosity
value will be multiplied by the viscosity multiplier, specified via PLYVISC (see 12.8.16).
The number of specified tables should be equal to the number of PVT regions (second
slash /.
1. surfactant concentration in the solution (METRIC: kg/sm3 , FIELD: lb/stb);
2. water solution viscosity at this surfactant concentration and the reference pressure,
specified via PVTW (see 12.5.5).
Example
SURFVISC
0.000 0.23
0.030 0.31
0.040 0.35
0.044 0.39 /
0.000 0.18
0.030 0.25
0.040 0.32
0.044 0.35 /
12.8.10. SURFVISC 839

12.8.11 SURFCAPD


Section
The keyword specifies the surfactant capillary de-saturation functions (surfactant section
2.25). This function describes the transition between immiscible conditions (at low surfactant
concentration) and miscibility conditions (at high surfactant concentration).

slash /.
1. log of the capillary number (log1 0(CAPN)) (a value in the range from -20 to 20);
2. miscibility function at the specified value of the log capillary number. A value should
be in the range from 0 to 1 (0 immiscible conditions, 1 miscible conditions).
Default: if the table is defaulted for a region (specified with only a /), then the values
will be copied from the previous specified table.
Example
SURFCAPD
-15 0
-4 0
-1 1
3 1
15 1 /
In this example there is 1 table.
12.8.11. SURFCAPD 840

12.8.12 SURFROCK


Section
The keyword specifies the surfactant-rock properties (surfactants section 2.25).

slash /.
The table contains 2 parameters:
1. desorption index:
1 ASP desorbtion is on;

2 ASP desorbtion is off;
2. mass density of the rock type at reservoir conditions (it is used in the calculation of
the surfactant loss because of adsorption) (METRIC: kg/rm3 , FIELD: lb/rb).
Example
SURFROCK
2 2115 /
1 2400 /
1 2683 /
12.8.12. SURFROCK 841

12.8.13 SURFADDW


Section
This keyword specifies the coefficient that is used in RP calculations as weighted aver-
age of the oil-wettability value and of the water-wettability value (Surfactants section 2.25).
slash /.
If a table is defaulted (/is used instead of table), then all its values are copied from
previous table.

1. concentration of adsorbed surfactant (METRIC: kg/kg, FIELD: lb/lb);
2. coefficient that is used in RP calculations as weighted average of the oil-wettability
value and of the water-wettability value (the value should be in the range from 0 to 1).
block.
Example
SURFADDW
0.0 1.0
0.0001 0.5
0.001 0.2
/
0.0 1.0
0.001 0.3
/
12.8.13. SURFADDW 842

12.8.14 SURFDW


Section
This keyword specifies the coefficient that is used in RP calculations as weighted aver-
age of the oil-wettability value and of the water-wettability value (Surfactants section 2.25).
slash /.
If a table is defaulted (/is used instead of table), then all its values are copied from
previous table.

1. local concentration of dissolved (in the water) surfactant (METRIC: kg/kg, FIELD:
lb/lb);
2. coefficient that is used in RP calculations as weighted average of the oil-wettability
value and of the water-wettability value (the value should be in the range from 0 to 1).
block.
Example
SURFDW
0.0 1.0
0.01 0.5
0.1 0.2
/
0.0 1.0
0.1 0.3
/
12.8.14. SURFDW 843

12.8.15 SURFSTES


Section
The keyword sets surface tension in oil-water system dependence on surfactant and salt
concentrations as a table. This keyword can be used only with option BRINE (see 12.1.58).
The number of tables is set by the 2-nd parameter of keyword TABDIMS (see 12.1.26).
Each table consists of data sets, the number of which shouldnt exceed the value of the 4-th
parameter of the keyword TABDIMS (see 12.1.26). The number of lines in each data set
must be equal to the number of lines in a table which determines salt concentrations (the
keyword ESSNODE (see 12.7.7)).
1. surfactant concentration value (METRIC: kg/sm3 ; FIELD: lb/stb). Values should be
strictly increasing.
2. surface tension in oil-water system value (METRIC: N/m; FIELD: lb f /in).
Example
ESSNODE
11.1
15.36
19.56 /
...
SURFSTES
0 0.000126191
0.000126191
0.000126191 /
0.003 0.000126191
0.000126191
0.000126191 /
0.350 1.4275E-07
4.2254E-08
3.3689E-08 /
2.449 6.281E-08
3.1976E-08
1.0849E-08 /
3.499 5.0248E-07
3.4831E-08
2.2269E-08 /
/
12.8.15. SURFSTES 844

In the example surface tension in oil-water system dependence on surfactant and salt
concentrations is set.
12.8.15. SURFSTES 845

12.8.16 PLYVISC


Section
This keyword specify the multiplier for water viscosity as a function of polymer concen-
tration (Polymer Flood section 2.20).

If surfactant injection is used then the viscosity value, specified with SURFVISC (see
12.8.10), is multiplied by polymer viscosity multiplier, specified by PLYVISC (see 12.8.16).
slash /.
1. polymer concentration in the solution (METRIC: kg/sm3 , FIELD: lb/stb);
2. corresponding multiplier by which the water viscosity (specified in PVTW (see 12.5.5))
is multiplied in solution viscosity calculations. The first specified number should be 1.
Example
PLYVISC
0.0000 1
0.0030 12
0.0040 31
0.0044 45 /
0.0000 1
0.0030 14
0.0040 40
0.0044 60 /
In this example 2 tables are entered.
12.8.16. PLYVISC 846

12.8.17 PLYADS


Section
The keyword specifies polymer adsorption functions (Polymer Flood section 2.20).
Polymer adsorption can be reduced in the case of alkaline injection (alkaline section 2.24).

slash /.
1. polymer concentration in the solution (METRIC: kg/sm3 , FIELD: lb/stb);
2. corresponding saturated concentration of polymer adsorbed by the rock formation

(METRIC: kg/kg, FIELD: lb/lb).
(The first row of the table should contain two zeroes)
Example
PLYADS .0000 .00000
.0005 .00009 /
.0012 .00020 /
12.8.17. PLYADS 847

12.8.18 PLYMAX


Section
This keywords is used to specify polymer and salt concentrations for mixing calculations
(Polymer flood section 2.20).

The number of specified tables should be equal to the 10-th parameter of REGDIMS (see
12.1.29) (the number of regions with different polymer properties).
1. polymer concentration in the solution that is used in the calculation of the maximum
polymer fluid component viscosity (METRIC: kg/sm3 , FIELD: lb/stb);
2. salt concentration in the solution that is used in the calculation of the maximum polymer
fluid component viscosity (METRIC: kg/sm3 , FIELD: lb/stb) (salt option should be
switched on via the keyword BRINE (see 12.1.58)).
Example
PLYMAX
15.8 7.5/
In this example one table is entered.
12.8.18. PLYMAX 848

12.8.19 PLMIXPAR


Section
This keyword specifies the Todd-Longstaff mixing parameter for the viscosity calculation
in the case of Polymer Flood (POLYMER (see 12.1.48) section 2.20).

The number of specified tables should be equal to the 10-th parameter of REGDIMS (see
12.1.29) (the number of regions with different polymer properties).
1. Todd-Longstaff mixing parameter for the viscosity calculation (the value in the range
from 0 to 1).
Example
PLMIXPAR
0.5 /
0.7 /
1 /
12.8.19. PLMIXPAR 849

12.8.20 PLYROCK


Section
This keyword specifies rock properties for Polymer Flood (Polymer Flood section 2.20).

slash /.
1. dead pore space (the value shouldnt be greater then the maximum water saturation for
this rock type);
2. residual resistance factor for this rock type (the value should be greater or equal to 1;
this value defines the decrease in the rock permeability to the aqueous phase when the
maximum amount of polymer is adsorbed);
3. mass density of this rock type at reservoir conditions (it is used in polymer loss
calculations due to adsorption) (METRIC: kg/rm3 , FIELD: lb/rb).
4. adsorption index: 1 (desorption can take place if polymer concentration decreases in

grid block) or 2 (desorption is prevented);
5. maximum polymer adsorption value (METRIC: kg/kg, FIELD: lb/lb).
Default:
Adsorption index: 1 (desorption can take place if polymer concentration decreases in grid
block).
Example
PLYROCK
0.14 1.3 2115 2 0.0004 /
In this example one table is entered.
12.8.20. PLYROCK 850

12.8.21 PLYSHEAR


Section
This keyword specifies polymer shear thinning data (factor for polymer solution viscosity)
for Polymer Flood (section 2.20).
To set polymer shear via logarithmic formula use the keyword PLYSHLOG (see 12.8.22).
slash /.
1. water phase flow velocity (METRIC: m/day3 , FIELD: f t/day).
2. factor by which the polymer solution viscosity, specified by PVTW (see 12.5.5),
PLYVISC (see 12.8.16), is changed due to shear thinning/thickening of the polymer.
The viscosity of the water and polymer solution (for a given polymer concentration and
flow velocity) is calculated via the formula:

1 + (B 1)F
W,poly = W,e
B
where:
W,poly shear viscosity of the polymer+polymer solution;
W,e effective water viscosity;
B viscosity multiplier without shear effect, specified via PLYVISC (see 12.8.16);
F viscosity multiplier with shear effect, specified via this keyword.
If F = 1 (should be entered in the first table row), then W,poly = W,e .

If F = 0, then W,poly = W,e
B .
12.8.21. PLYSHEAR 851

Example
PLYSHEAR
0.00 1.00
4.45 0.60
7.00 0.55 /
12.8.21. PLYSHEAR 852

12.8.22 PLYSHLOG


Section
The keyword sets polymer shear thinning/thickening (via logarithmic formula) for Poly-
mer Flood (section 2.20).
To set polymer shear via factor for polymer solution viscosity use the keyword
PLYSHEAR (see 12.8.21).
in the following after the keyword line:
1. reference polymer concentration (METRIC: kg/sm3 , FIELD: lb/stb);
2. reference salinity (METRIC: kg/sm3 , FIELD: lb/stb).
This data should be ended via symbol / in the next line.
in the following lines tables of shear multiplier dependence on phase flow velocity/shear
rate are set:
1. water phase/polymer velocity or shear rate (units for velocity METRIC: m/day3 ,
FIELD: f t/day; units for shear rate 1/day). The values must increase mono-
tonically down the column, first of them should belong to the interval [0; 10 6 ];
2. shear multiplier.
The number of table lines should be not less than 2 and not greater than the value of
4-th parameter of TABDIMS (see 12.1.26). The number of tables is equal to the value
of 2-nd parameter of TABDIMS (see 12.1.26). The data should be terminated with a
slash /.
Example
PLYSHLOG
50 0
/
0.000001 1.0
0.1 1.3
1.0 1.5
10.0 1.6
100.0 1.7
1000.0 1.8
/
12.8.22. PLYSHLOG 853

In the example reference polymer concentration is 50 lb/stb, reference salinity is 0, then

one table of shear multiplier dependence on phase flow velocity is specified.
12.8.22. PLYSHLOG 854

12.8.23 ALSURFST


Section
The keyword specifies oil-water surface tension multiplier as a function of alkaline con-
centration (Ast (Calkl ) in the section 2.24).

slash /. If the table is specified for default with /, then the values will be copied from the
previous specified table.
1. alkaline concentration in the grid block (METRIC: kg/sm3 , FIELD: lb/stb);
2. surface tension multiplier.
(The first table row should contain the surface tension multiplier at zero alkaline concentra-
tion.)
The factor will not be applied if the minimum value of surface tension is reached (specified
in the table SURFST (see 12.8.9)).
Example
ALSURFST
0.000 1.00000
0.002 0.80000 /
/
In this example two tables are entered. All values in the second table are defaulted (/)
and will be copied from the first table.
12.8.23. ALSURFST 855

12.8.24 ALSURFAD


Section
The keyword specifies surfactant adsorption multiplier as a function of alkaline concen-

tration (Aad (Calkl ) in the section Alkaline Flooding 2.24).

The number of specified tables should be equal to the number of saturation regions (first
2. surfactant adsorption multiplier.
(The first table row should contain the multiplier value at zero alkaline concentration.)
Example
ALSURFAD
0.000 1.00000
0.001 0.90000
0.002 0.80000 /
/
12.8.24. ALSURFAD 856

12.8.25 ALPOLADS


Section
The keyword specifies polymer adsorption multiplier as a function of alkaline concentra-

tion (Aad (Calkl ) in the section Alkaline Flooding 2.24).

2. polymer adsorption multiplier.
(The first table row should contain the multiplier value at zero alkaline concentration.)
Example
ALPOLADS
0.000 1.00000
0.001 0.90000
0.002 0.80000 /
/
12.8.25. ALPOLADS 857

12.8.26 ALKADS


Section
This keyword specifies the alkaline adsorption functions (Alkaline Flooding section
2.24).

slash /.
2. corresponding saturated concentration of alkaline adsorbed by the rock (METRIC:

kg/kg, FIELD: lb/lb).
(The first table row should contain two zeros.)
Example
ALKADS
0.00000 0.00000 0.00027 0.00005 0.00078 0.00007 0.00140
0.00011 /
12.8.26. ALKADS 858

12.8.27 ALKROCK


Section
This keyword specifies the rock properties for alkaline adsorption adsorption index
(Alkaline Flooding section 2.24).

The number of adsorption indexes should be equal to the number of saturation regions
(first parameter of the keyword TABDIMS (see 12.1.26)). Each number should be terminated
with a slash /. If the number is specified for default with /, then the value will be copied
from the previous specified one.
Possible adsorption indexes:
1 desorption is possible (if the alkaline concentration decreases in the grid block then
the amount of adsorbed alkaline will be recalculated);
2 desorption is prevented (alkaline affects on polymer and surfactant constantly in

case if the alkaline concentration decreases in the grid block).
Example
ALKROCK
2 /
1 /
/
In this example 3 values are entered (correspondingly to 3 saturation regions). For the 3-
rd saturation region the adsorption index is defaulted and it will be copied from the previous
one.
12.8.27. ALKROCK 859

12.8.28 STVP


Section
The keyword sets surface tension dependence on pressure value for miscible option (the
keyword MISCIBLE (see 12.1.65)) as a table. For each PVT-region its own SPVT-table
should be set.
Each line of the table should contain the following data:
1. pressure value (METRIC: bar , FIELD: psia);
2. surface tension value (METRIC: dynes/cm, FIELD: dynes/cm).
Pressure values should increase, surface tension values should decrease from one line to
another.
Default:
if value of reference pressure is not set (the keyword MISCSTR (see 12.6.53)), then it
is equal to maximal value of STVP-tables.
Example
STVP
1 10
100 7
200 2
300 0
/
In the example the keyword STVP sets surface tension dependence on pressure value.
12.8.28. STVP 860

12.8.29 WAGHYSTR


Section
The keyword sets parameters of hysteresis model. It can be used only if hysteresis option
is activated (see the keyword SATOPTS (see 12.1.68)).
1. parameter C (Lands parameter). It affects on trapped gas saturation on imbibition and

imbibition curve. Trapped gas saturation is set by formula:
(sgm sgc )
sgt = sgc + ,
1 +C (sgm sgc )
where:
sgt - trapped gas saturation;

sgm - maximum gas saturation value reached;
sgc - critical gas saturation.
2. secondary drainage reduction coefficient, ;
3. gas model flag:
YES - use hysteresis model for gas relative permeability;

NO - turn off hysteresis model.
4. residual oil model flag. This is an Eclipse compatibility field.
5. water model flag:
YES - use hysteresis model for water relative permeability;

NO - turn off hysteresis model.
6. imbibition curve linear part;
7. three-phase model threshold saturation;
8. residual oil modification fraction.
12.8.29. WAGHYSTR 861

The number of data lines must be equal to the number of filtration regions (1-st parameter
of the keyword TABDIMS (see 12.1.26)). Each line should be ended by a symbol /.
Default:
secondary drainage reduction coefficient: 0;
gas model flag: YES;
water model flag: YES;
imbibition curve linear part: 0.1;
three-phase model threshold saturation: 0.001;
residual oil modification fraction: 1.0.
Example
WAGHYSTR
3.0 1* YES NO NO /
3.0 1* YES NO NO /
3.0 1* YES NO NO /
3.0 1* YES NO NO /
In the example the keyword WAGHYSTR (see 12.8.29) sets parameters of hysteresis
model for 4 filtration regions. In each region hysteresis model for gas relative permeability
is used.
12.8.29. WAGHYSTR 862

12.9. Coal Bed Methane properties tNavigator-4.2
12.9 Coal Bed Methane properties
12.9. Coal Bed Methane properties 863

12.9.1 DIFFCOAL


Section
The keyword sets gas diffusion data for Coal Bed Methane model (2.29).
The number of data lines should be equal to the number of CBM regions (COALNUM (see
12.4.15)) should not be less or equal the 6-th parameter of the keyword REGDIMS (see
12.1.29).
Each data line should be terminated with a slash /.
One line contains the following parameters:
1. gas diffusion coefficient (METRIC: m2 /day, FIELD: f t 2 /day);
2. re-adsorption fraction. Zero value prevents re-adsorption;
3. solvent diffusion coefficient (METRIC: m2 /day, FIELD: f t 2 /day).
Default:
re-adsorption fraction 1;
solvent diffusion coefficient is equal to gas diffusion coefficient, specified via parameter
1.
Example
DIFFCOAL
0.2 /
0.15 0 /
0.1 0.7 /
In this example the data for 3 CBM regions is specified. In the 2-nd region re-adsorption
is forbidden.
12.9.1. DIFFCOAL 864

12.9.2 LANGMUIR


Section
This keyword sets the tables of coal surface gas concentration, that is used in Coal Bed
Methane model (2.29).
The number of tables should be equal to the number of CBM regions (COALNUM (see
12.1.29).
The number of columns is equal 2 for black-oil models in E100 format and NCOMPS+1 for
compositional models in E300 format.
One table line contains the following parameters:
1. fracture pressure (METRIC: barsa, FIELD: psia); In the case of compositional model
in E300 format this parameter sets the partial pressure yi p;
2. corresponding surface gas concentration (METRIC: sm3 /m3 , FIELD: Msc f / f t 3 ).

In the case of compositional model in E300 format this parameter sets corresponding
surface concentration of the first component;
3. in the case of compositional model in E300 format this parameter (and next parameters)
sets surface concentration of the second (and next) component (METRIC: sm3 /m3 ,
FIELD: Msc f / f t 3 ).
Example
LANGMUIR
0.0 0.0
10.0 0.03
100.0 0.16
300.0 0.33
1000.0 1
/
/
In this example data for 2 CBM regions is present. The table for 2-nd region is set as /,
i.e. it is copied from the table for 1-st region.
12.9.2. LANGMUIR 865

12.9.3 LANGMULT


Section
This keyword sets multipliers of coal surface gas concentration, that is used in Coal Bed
Methane model (2.29). Coal surface gas concentration is set via the keyword LANGMUIR
(see 12.9.2).
1. multiplier of coal surface gas concentration for each block. The number of multipliers
should be equal to the number of blocks in a model.

Default:
multiplier of coal surface gas concentration: 1.
Example
LANGMULT
10* 5*0.2 /
In the example multipliers of coal surface gas concentration for the first 10 grid blocks
are set to default values, i.e. 1. Concentration value reduced 5 times for the others.
12.9.3. LANGMULT 866

12.9.4 LANGMEXT


Section
This keyword sets extended Langmuir Isotherm for compositional models in Coal Bed
Methane simulation (2.29).
The number of data sets should be equal to the number of CBM regions (COALNUM (see
12.1.29).
Each data set should be terminated with a slash /.

A data set contains an arbitrary number of lines (nc number of components in the model):
p1 V1 p2 V2 ... pnc Vnc
One line contains 2 nc elements:
Langmuir pressure constant pi for component i (METRIC: barsa, FIELD: psia).

Positive number. Langmuir pressure constant can be zero if Langmuir volume constant
is zero;
Langmuir volume constant Vi for component i (METRIC: sm3 /kg, FIELD:

Msc f /ton). Non-negative number.
The values pi and Vi specify the Langmuir curve for the component i.
Default
Langmuir pressure constant pi 0;
Langmuir volume constant Vi 0.
12.9.4. LANGMEXT 867

Example
FIELD
LANGMEXT
365.0 0.983
579.0 0.501
228.0 0.971
3672.0 0.469 /
367.0 0.984
565.0 0.498
230.0 0.961
3566.0 0.451 /
/
12.9.4. LANGMEXT 868

12.9.5 DIFFCBM


Section
This keyword sets the diffusion coefficients for each component, that are used in Coal
Bed Methane model (2.29).
12.1.29).
slash /.
The data line has the following format (nc number of components in the model):
d1 d2 d3 d4 ... dnc
Each line consists of nc elements:
diffusion coefficient di for component i (METRIC: m2 /day, FIELD: f t 2 /day). Non-

negative number.
Default:
diffusion coefficient di for component i 0.
Example
DIFFCBM
0.08 0.17 0.2 0.13 /
0.07 0.14 0.15 0.11 /
/
In this example diffusion coefficients are set for 4 components in 2 CBM regions.
12.9.5. DIFFCBM 869

12.9.6 RESORB


Section
This keyword sets the readsorption factor for each component, that are used in Coal Bed
Methane model (2.29).
12.1.29).
slash /.
The data line has the following format (nc number of components in the model):
r1 r2 r3 r4 ... rnc
Each line consists of nc elements:
readsorption factor ri for component i (METRIC: m2 /day, FIELD: f t 2 /day). This

parameter can be in the range from 0 to 1.
Default:
readsorption factor di for component i 1.
Example
DIFFCBM
1 0.58 0.8 0.8 /
1 0.65 0.9 0.9 /
/
In this example readsorption factors are set for 4 components in 2 CBM regions.
12.9.6. RESORB 870

12.10. Asphaltene properties tNavigator-4.2
12.10 Asphaltene properties
12.10. Asphaltene properties 871

12.10.1 ASPP1P


Section
The keyword sets variable of asphaltene precipitation function. The keyword ASPREWG
(see 12.10.2) should be used in conjunction with this one. These keywords can be used only
if asphaltene precipitation model option (see 2.23) is activated by the keyword ASPHALTE
(see 12.1.63). The following parameters should be specified:
1. variable:
P pressure;
Z total molar fraction.
2. component number (this parameter is specified only if the first parameter is Z).

Default:
variable: P.
Example
ASPP1P
'P'/
Asphaltene precipitation is set as a function of pressure.
12.10.1. ASPP1P 872

12.10.2 ASPREWG


Section
The keyword sets fracture of molar weight dissolved in solution as a function of one
variable. Variable is chosen by the keyword ASPP1P (see 12.10.1). These keywords can
be used only if asphaltene precipitation model option (see 2.23) is activated by the keyword
ASPHALTE (see 12.1.63). The following parameters should be specified:
1. pressure (METRIC: bar , FIELD: psi) or component molar fraction;
2. fraction of asphaltene dissolved in the oil phase (%).
Example
ASPREWG
1000.0 0.0
2000.0 5.0
3900.0 15.0
10000.0 100.0 /

In the example it is specified that at pressure of 1000 psi asphaltene is not contained in
oil phase; but at pressure of 10000 psi asphaltene amounts 100% of oil weight.
12.10.2. ASPREWG 873

12.10.3 ASPP2P


Section
The keyword sets 2 parameters on which fraction of dissolved asphaltene in oil depends.
The keyword ASPPW2D (see 12.10.4) should be used in conjunction with this one. These
keywords can be used only if asphaltene precipitation model option (see 2.23) is activated
by the keyword ASPHALTE (see 12.1.63). First 2 parameters are fixed:
1. P pressure;
2. Z total molar fraction of a component.

Then the 3-rd parameter is specified:
3. component number.
Example
ASPP2P
'P' 'Z' 2 /
Asphaltene precipitation is defined by function of pressure and molar fracture of the 2-nd
component.
12.10.3. ASPP2P 874

12.10.4 ASPPW2D


Section
The keyword sets fracture of molar weight dissolved in solution as a function of two
variables. Variables are chosen via the keyword ASPP2P (see 12.10.3). These keywords can
be used only if asphaltene precipitation model option (see 2.23) is activated by the keyword
ASPHALTE (see 12.1.63).
Data are set as a table. In the 1-st line molar component fractures are set. In the next
lines pressure values (METRIC: bar , FIELD: psi) and fractures molar weight of asphaltene
dissolved in the oil phase (%). The number of fractures should be equal to the number of
molar component fractures.
Each data line should be ended by the symbol /.The data should be terminated with a
slash /.
Example
ASPPW2D
0.001 0.015 0.002 0.004 /
1000 10.0 30.0 50.0 60. /
2000 5.0 20.0 30.0 50. /
3000 10.0 25.0 45.0 70. /
8000 80.0 85.0 90.0 100. /
/
In the example 4 values of molar component fractures are set. They equal to 0.001, 0.015,
0.002 and 0.004. There are also 4 pressure values: 1000, 2000, 3000 and 8000 psi.
12.10.4. ASPPW2D 875

12.10.5 ASPFLRT


Section
The keyword sets the kinetic reaction rates for the flocculation and dissociation processes
for flocs and fines. Keyword CATYPE (see 12.10.7) should be used in conjunction with this
one. These keywords can be used only if asphaltene precipitation model option (see 2.23)
is activated by the keyword ASPHALTE (see 12.1.63). The following parameters should be
specified:
1. rates of the flocculation process (1/day). n values should be specified, where n is the
number of components that can precipitate;
2. rates of the dissociation process (1/day). There also n values should be specified.
Example
ASPFLRT
0.01
0.001 /
In the example rates of the flocculation and dissociation processes for one component are
set.
12.10.5. ASPFLRT 876

12.10.6 ASPVISO


Section
The keyword sets parameters of oil viscosity change model in asphaltene precipitation
run (see 2.23). Asphaltene precipitation option is activated by keyword ASPHALTE (see
12.1.63), model type is set also there. With respect to selected type the following parameters
are set:
type EI:
1. slope coefficient of relative viscosity with respect to concentration.
type KD:
1. mass concentration at maximum packing;

2. intrinsic viscosity.
type TAB. Two-column table:
1. the mass fraction of the asphaltene precipitate;

2. the oil viscosity multiplier.
Example
ASPHALTE
WEIGHT 1* TAB /
...
ASPVISO
0.0 1.0
0.01 1.2
0.1 1.5
1.0 10.0 /
In the example the oil viscosity multiplier is set as a function of the mass fraction of the
asphaltene precipitate.
12.10.6. ASPVISO 877

12.10.7 CATYPE


Section
The keyword is used to set asphaltene properties for each model component. It can be
used only if option of the asphaltene precipitate is activated (see section 2.23 and keyword
ASPHALTE (see 12.1.63)). The following parameters should be specified:
1. component property:
PREC component that can precipitate as asphaltene;

FLOC component that represents the flocculated asphaltene;
NONE an ordinary component.
Only one property can be set for each component. Properties FLOC and PREC can be
assigned to only one component.

Default:
component property: NONE.
Example
CATYPE
5* PREC FLOC /
In the example the first five components have no asphaltene properties. The 6-th one can
precipitate as asphaltene, the 7-th one is the flocculated asphaltene.
12.10.7. CATYPE 878

12.11. Foam properties tNavigator-4.2
12.11 Foam properties
12.11. Foam properties 879

12.11.1 FOAMADS


Section
The keyword sets functions of foam adsorption by the rock formation. Functions are set
via tables. The number of tables must be equal to the value of the 1-st parameter of keyword
TABDIMS (see 12.1.26). Foam modeling option 2.21.
Each table contains 2 columns:
1. local foam concentration in the solution surrounding the rock. Units depends on the
first parameter of FOAMOPTS (see 12.11.2):
if it is GAS METRIC: kg/sm3 , FIELD: lb/Msc f ;

if it is WATER METRIC: kg/sm3 , FIELD: lb/stb.
Concentration values should be monotonically increase;
2. the corresponding saturated concentration of foam adsorbed by the rock formation

(METRIC: kg/kg; FIELD: lb/lb). These values should be level, or increase.
The number of lines in each table should not be less than 2 or greater than the value of
the 3-rd parameter of TABDIMS (see 12.1.26).
Example
FOAMADS
0.0 0.00000
1.0 0.00005
30.0 0.00005 /
0.0 0.00000
1.0 0.00002
30.0 0.00002 /
In the example 2 functions are set.
12.11.1. FOAMADS 880

12.11.2 FOAMOPTS


Section
The keyword sets foam modeling options. It can be used only if foam model option (see
2.21) is activated by the keyword FOAM (see 12.1.64). The following parameters should be
specified:
1. transport phase for foam:
GAS gas;
WATER or WAT water.
2. gas mobility reduction factor calculation type:
TAB reduction calculation will be set by the keywords FOAMMOB (see 12.11.6)
and, optionally, FOAMMOBP (see 12.11.7).

Default:
transport phase for foam: GAS;
gas mobility reduction factor calculation type: TAB.
Example
FOAMOPTS
WATER TAB /
12.11.2. FOAMOPTS 881

12.11.3 FOAMROCK


Section
The keyword sets rock properties for model which uses foam modeling option (see Foam
modeling). Properties are set as tables. The number of tables must be equal to the value of
the 1-st parameter of keyword TABDIMS (see 12.1.26). Each table contains 2 columns:
1. the adsorption index to be used for this rock type:
1 the foam adsorption isotherm is retraced whenever the local foam concentra-
tion in the solution decreases;
2 no foam desorption may occur.
2. the mass density of this rock type at reservoir conditions (METRIC: kg/rm3 , FIELD:
lb/rb).

Default:
the adsorption index: 1.
Example
FOAMROCK
1 2650 /
2 2650 /
12.11.3. FOAMROCK 882

12.11.4 FOAMDCYW


Section
The keyword sets foam decay dependence on water saturation. It can be used only if foam
model option (see 2.21) is activated by the keyword FOAM (see 12.1.64). Dependences are
set as tables. The number of tables must be equal to the value of the 1-st parameter of
keyword TABDIMS (see 12.1.26). Each table contains 2 columns:
1. the local water saturation. The values should increase monotonically from line to line;
2. the corresponding decay half-life (days).
Note. If keyword FOAMDCYO (see 12.11.5) is also defined, the decay half-life is equal
to the minimum of the two values for each cell.
Example
FOAMDCYW
0.0 3000
1.0 2000 /
0.0 3000
1.0 2000 /
12.11.4. FOAMDCYW 883

12.11.5 FOAMDCYO


Section
The keyword sets foam decay dependence on oil saturation. It can be used only if foam
model option (see 2.21) is activated by the keyword FOAM (see 12.1.64). Dependences
are set as tables. The number of tables must be equal to the value of the 1-st parameter of
keyword TABDIMS (see 12.1.26). Each table contains 2 columns:
1. the local oil saturation. The values should increase monotonically from line to line;
2. the corresponding decay half-life (days).
Note. If keyword FOAMDCYW (see 12.11.4) is also defined, the decay half-life is equal
to the minimum of the two values for each cell.
Example
FOAMDCYO
0.0 3000
1.0 2000 /
0.0 3000
1.0 2000 /
12.11.5. FOAMDCYO 884

12.11.6 FOAMMOB


Section
This keyword sets dependences of the gas phase mobility factor on foam concentration.
It can be used only if foam model option (see 2.21) is activated by the keyword FOAM (see
12.1.64). Dependences are set as tables. The number of tables must be equal to the value of
the 2-nd parameter of keyword TABDIMS (see 12.1.26). Each table contains 2 columns:
1. foam concentration. Units depends on the first parameter of FOAMOPTS (see 12.11.2):

Concentration values should be monotonically increase;
2. gas mobility factor.
the 4-th parameter of TABDIMS (see 12.1.26).
Example
FOAMMOB
0 1
0.001 0.4
0.1 0.1
1.2 0.05 /
12.11.6. FOAMMOB 885

12.11.7 FOAMMOBP


Section
The keyword sets dependence of the foam mobility factor on oil pressure. It is optional
keyword; it can be used only if foam model option (see 2.21) is activated by the keyword
FOAM (see 12.1.64). Dependences are set by tables. The number of tables must be equal to
the value of the 2-nd parameter of keyword TABDIMS (see 12.1.26). Each table contains 2
columns:
1. oil pressure (METRIC: barsa, FIELD: psia);
2. multiplier M p (P) which is used to calculate the foam mobility factor as follows:
M = (1 M(C f )) M p (P) + M(C f ),
where:
M foam mobility factor;

M(C f ) the gas phase mobility factor which depends on foam concentration
(keyword FOAMMOB (see 12.11.6));
M p (P) function of oil pressure value. This value is defined by this keyword;
P oil pressure.
the 4-th parameter of TABDIMS (see 12.1.26).
Example
FOAMMOBP
3000 0
6000 0.2 /
12.11.7. FOAMMOBP 886

12.11.8 FOAMMOBS


Section
The keyword sets dependence of the shear on oil pressure. It is optional keyword; it
can be used only if foam model option (see 2.21) is activated by the keyword FOAM (see
12.1.64). Dependences are set by tables. The number of tables must be equal to the value of
the 2-nd parameter of keyword TABDIMS (see 12.1.26). Each table contains 2 columns:
1. The gas phase flow velocity (METRIC: m/day, FIELD: f t/day). The values should
increase monotonically down the column. The first value should be equal to 0.0;
2. multiplier Ms (v) which is used to calculate the foam mobility factor as follows:
M f = (1 M) Ms (v) + M,
where:
M f is the final mobility reduction factor;

M is the foam mobility factor (keywords FOAMMOB (see 12.11.6) and FOAM-
MOBP (see 12.11.7));
Ms (v) is the shear dependency function value;
v is the gas phase velocity.
The number of lines in each table should not be less than 2 or greater than the value of the
4-th parameter of TABDIMS (see 12.1.26).
Example
FOAMMOBS
0.0 0
4.0 0.1 /
12.11.8. FOAMMOBS 887

12.12. Residual oil properties tNavigator-4.2
12.12 Residual oil properties
12.12. Residual oil properties 888

12.12.1 SOR


Section
The keyword activates residual oil modeling option (see section 2.22) and sets residual
oil saturation values in each SATNUM (see 12.4.3) region. This keyword should be used in
conjunction with EOS (see 12.13.5) compositional simulations. Each value is set in separate
line. The number of data lines must be equal to the number of SATNUM regions (i.e. to the
value of the 1-st parameter of keyword TABDIMS (see 12.1.26).)
1. residual oil saturation values in each SATNUM (see 12.4.3) region.
Each data line should be ended by the symbol /.
Example
SOR
0.1 /
0.15 /
0.20 /
In the example values of residual oil saturation are set for 3 SATNUM regions.
12.12.1. SOR 889

12.12.2 SOROPTS


Section
The keyword sets compressibility model of residual oil. It can be used only if residual oil
saturation option (see 2.22) is activated by the keyword SOR (see 12.12.1).
The residual oil saturation is the ratio of the residual oil volume in a cell to the cells
pore volume:
VOILR
SOILR = .
PORV
Since the residual oil composition remains constant, the volume of residual oil depends
only on pressure. Therefore, the residual oil saturation also depends only on pressure:
1 dSOILR 1 dPORV
= COILR ,
SOILR dP PORV dP
where COILR compressibility of residual oil:
1 dVOILR
COILR = .
VOILR dP
3 compressibility models are supported:
ZERO.
1 dSOILR
= 0.
SOILR dP
The residual oil saturation remains constant throughout the simulation. This is the
simplest model, but not physical;
CONSTANT.
COILR = CONSTANT.
The initial compressibility of the residual oil is calculated and used during the model
computation.
FLASH.
The residual oil volume is determined by flashing the residual oil composition at the
cell pressure.

Default:
compressibility model: ZERO.
12.12.2. SOROPTS 890

Example
SOROPTS
FLASH /
12.12.2. SOROPTS 891

12.13. Compositional properties tNavigator-4.2
12.13 Compositional properties

This section describes reservoir fluid properties for a compositional run. The keywords listed
in this section fully describe three-phase multi-component non-isothermal model.
For water and rock property definition keywords from previous section are used (PVTW
(see 12.5.5), ROCK (see 12.5.16), DENSITY (see 12.5.23), SWOF (see 12.6.1), 12.6.2).
For some components, listed below, default values of parameters may be used (TCRIT
(see 12.13.17), PCRIT (see 12.13.19), VCRIT (see 12.13.21), MW (see 12.13.27), BIC
(see 12.13.32)). In this case component properties will be taken from the following table (in
compliance with their names indicated in CNAMES (see 12.13.4)).
12.13. Compositional properties 892

12.13.1 Default values of component properties for compositional model. Part 1
Component Chemical Critical Critical Acentric Molecular Critical
name formula temperature, K pressure, BARSA factor weight volume
N2 N2 1.2620E + 02 3.394387500E + 01 4.000000000E 02 2.8013000E + 01 9.00E 02
CO2 CO2 3.0470E + 02 7.386592500E + 01 2.250000000E 01 4.4010000E + 01 9.40E 02
H2S H2 S 3.7360E + 02 8.936865000E + 01 1.000000000E 01 3.4076000E + 01 9.80E 02
C1 C1 H3 1.9060E + 02 4.604208000E + 01 1.300000000E 02 1.6043000E + 01 9.80E 02
C2 C2 H6 3.0543E + 02 4.883865000E + 01 9.860000000E 02 3.0070000E + 01 1.48E 01
C3 C3 H8 3.6980E + 02 4.245517500E + 01 1.524000000E 01 4.4097000E + 01 2.00E 01
IC4 iC4 H10 4.0810E + 02 3.647700000E + 01 1.848000000E 01 5.8123999E + 01 2.63E 01
NC4 4.2520E + 02 3.796647750E + 01 2.010000000E 01 5.8124001E + 01 2.55E 01
12.13. Compositional properties
nC4 H10
IC5 iC5 H12 4.6040E + 02 3.389321250E + 01 2.270000000E 01 7.2150999E + 01 3.08E 01
NC5 nC5 H12 4.6960E + 02 3.370069500E + 01 2.510000000E 01 7.2151001E + 01 3.11E 01
C6 C6 H14 5.0750E + 02 3.010365750E + 01 2.990000000E 01 8.6178000E + 01 3.51E 01
C7 C7 H16 5.4800E + 02 2.938425000E + 01 3.000000000E 01 9.6000000E + 01 3.92E 01
C8 C8 H18 5.7500E + 02 2.879656500E + 01 3.120000000E 01 1.0700000E + 02 4.33E 01
C9 C9 H20 6.0300E + 02 2.630397000E + 01 3.480000000E 01 1.2100000E + 02 4.84E 01
C10 C10 H22 6.2600E + 02 2.419641000E + 01 3.850000000E 01 1.3400000E + 02 5.34E 01
C11 C11 H24 6.4800E + 02 2.230163273E + 01 4.189999998E 01 1.4700000E + 02 5.87E 01
C12 C12 H26 6.6800E + 02 2.080202250E + 01 4.539999962E 01 1.6100000E + 02 6.37E 01
C13 C13 H28 6.8700E + 02 1.959625500E + 01 4.839999974E 01 1.7500000E + 02 6.83E 01
C14 C14 H30 7.0600E + 02 1.860327000E + 01 5.159999728E 01 1.9000000E + 02 7.30E 01
C15 C15 H32 7.2400E + 02 1.760015250E + 01 5.500000119E 01 2.0600000E + 02 7.79E 01
C16 C16 H34 7.4000E + 02 1.659703500E + 01 5.820000172E 01 2.2200000E + 02 8.31E 01
C17 C17 H36 7.5500E + 02 1.589789250E + 01 6.129999757E 01 2.3700000E + 02 8.74E 01
12.13.1. Default component properties for compositional model. Part 1

C18 C18 H38 7.6700E + 02 1.530007500E + 01 6.380000114E 01 2.5100000E + 02 9.13E 01
C19 C19 H40 7.7800E + 02 1.480358250E + 01 6.620000005E 01 2.6300000E + 02 9.49E 01
C20 C20 H42 7.9000E + 02 1.433748750E + 01 6.899999976E 01 2.7500000E + 02 9.94E 01
tNavigator-4.2
893
12.13.2 Default values of component properties for compositional model. Part 2: Binary interaction coefficients
N2 CO2 H2S C1 C2
N2
CO2 1.200000010E 02
H2S 1.000000015E 01 1.000000015E 01
C1 1.000000015E 01 1.000000015E 01 0
C2 1.000000015E 01 1.000000015E 01 0 0
C3 1.000000015E 01 1.000000015E 01 0 0 0
IC4 1.000000015E 01 1.000000015E 01 0 0 0
NC4 1.000000015E 01 1.000000015E 01 0 0 0
IC5 1.000000015E 01 1.000000015E 01 0 0 0
12.13. Compositional properties
NC5 1.000000015E 01 1.000000015E 01 2.873999672E 02 9.999999776E 03 9.999999776E 03

C6 1.000000015E 01 1.000000015E 01 3.391999674E 02 9.999999776E 03 9.999999776E 03
C7 1.000000015E 01 1.000000015E 01 3.699999675E 02 9.999999776E 03 9.999999776E 03
C8 1.000000015E 01 1.000000015E 01 3.965999676E 02 9.999999776E 03 9.999999776E 03
C9 1.000000015E 01 1.000000015E 01 4.161999677E 02 9.999999776E 03 9.999999776E 03
C10 1.000000015E 01 1.000000015E 01 4.315999678E 02 9.999999776E 03 9.999999776E 03
C11 1.000000015E 01 1.000000015E 01 4.469999678E 02 9.999999776E 03 9.999999776E 03
C12 1.000000015E 01 1.000000015E 01 4.623999679E 02 9.999999776E 03 9.999999776E 03
C13 1.000000015E 01 1.000000015E 01 4.777999680E 02 9.999999776E 03 9.999999776E 03
C14 1.000000015E 01 1.000000015E 01 4.917999680E 02 9.999999776E 03 9.999999776E 03
C15 1.000000015E 01 1.000000015E 01 5.015999681E 02 9.999999776E 03 9.999999776E 03
C16 1.000000015E 01 1.000000015E 01 5.127999681E 02 9.999999776E 03 9.999999776E 03
C17 1.000000015E 01 1.000000015E 01 5.197999682E 02 9.999999776E 03 9.999999776E 03
C18 1.000000015E 01 1.000000015E 01 5.267999682E 02 9.999999776E 03 9.999999776E 03
12.13.2. Default component properties for compositional model. Part 2

C19 1.000000015E 01 1.000000015E 01 5.337999682E 02 9.999999776E 03 9.999999776E 03
C20 0 0 0 0 0
The rest coefficients of lower triangular part of binary interaction matrix are equal to zero by default.
tNavigator-4.2
894
12.13.3 COMPS


Section
This keyword sets the number of components in a compositional run N . Presence of

this keyword indicates that the compositional mode should be turned on.
Default: none
Example
COMPS
6
/
In this example compositional mode is activated. The oil-gas mixture will consist of 6
components.
12.13.3. COMPS 895

12.13.4 CNAMES


Section
This keyword introduces component names in a compositional run. If component name co-
incides with name from table 12.13.1 on page 893, some parameter values for this component
may be defaulted (such as critical temperature (Tc ), critical pressure ( pc ) etc.).
Default: none
Example
COMPS
5
/
...
CNAMES
CO2 C1 NC4 IC4 C10
/
In this example oil-gas mixture consists of 5 components: carbon dioxide (CO2 ), methane
(CH4 ), n-butane (nC4 H10 ), iso-butane (iC4 H10 ) and decane (C10 H22 ).
12.13.4. CNAMES 896

12.13.5 EOS

x RUNSPEC GRID EDIT x PROPS

Section
This keyword specifies for each EoS region which equation of state should be used for
liquid-vapor equilibrium calculation. Current simulator version supports three types of cubic
equations of state in the form of Redlich-Kwong (RK), Soave-Redlich-Kwong (SRK) and
Peng-Robinson (PR).
Equation name for each region starts from new line, each line must be terminated by a
slash /. Number of strings depends on number of EoS regions defined in TABDIMS (see
12.1.26) (9-th parameter).
Default: PR
Example
TABDIMS
2 1 2* 4 4*1
/
...
EOS
SRK
/
Here Soave-Redlich-Kwong equation of state will be used for liquid-vapor equilibrium

calculation.
Example
TABDIMS
2 3 2* 4 4*3
/
...
EOS
SRK
/
RK
/
PR
/
Here in each of 3 EoS regions its own type of equation of state will be used.
12.13.5. EOS 897

12.13.6 EOSS

x RUNSPEC GRID EDIT x PROPS

Section
This keyword specifies for each EoS region which equation of state should be used for
liquid-vapor equilibrium calculation in surface conditions.
By default (if this keyword is not specified) the equation of state, specified by EOS (see
12.13.5) is used. If this keyword EOSS is specified then for calculations in surface condi-
tions the EOS specified by EOSS is used; and for calcultions in reservoir conditions EOS,
specified by EOS (see 12.13.5). The list of keyword that specify parameters for calculations
in surface and reservoir conditions is in the section 3.1.1.
Current simulator version supports three types of cubic equations of state in the form of
Redlich-Kwong (RK), Soave-Redlich-Kwong (SRK) and Peng-Robinson (PR).
Equation name for each region starts from new line, each line must be terminated by a
slash /. Number of strings depends on number of EoS regions defined in TABDIMS (see
Default: PR
Example
TABDIMS
EOSS
SRK
/
Here Soave-Redlich-Kwong equation of state will be used for liquid-vapor equilibrium

calculation in surface conditions.
12.13.6. EOSS 898

12.13.7 RTEMP


Section
The keyword sets constant temperature (METRIC: C, FIELD: F) of each EoS region
in case when isothermal compositional model is used.
Temperature value for each region starts from new line, each line must be terminated by
a slash /. Number of strings depends on number of EoS regions defined in TABDIMS (see
Default: none
Example
TABDIMS
2 1 2* 4 4*1
/
...
RTEMP
80
/
Here isothermal compositional reservoir model is used, reservoir temperature is 80 Cel-

cium degrees.
Example
TABDIMS
2 3 2* 4 4*3
/
...
RTEMP
90
/
80
/
90
/
In this example each of three EoS regions will have its own constant temperature.
12.13.7. RTEMP 899

12.13.8 STCOND


Section
This keyword sets standard temperature (METRIC: C, FIELD: F) and pressure (MET-
RIC: barsa, FIELD: psia) for calculation of gas, oil, water volume in standard conditions.
User should specify two values: standard temperature and pressure.
Default: values from 10
Example
STCOND
20 2
/
12.13.8. STCOND 900

12.13.9 WATERTAB


Section
The keyword specifies water pressure tables.

The table (terminated with a slash /) should be specified for each PVT region (number of
PVT regions is specified via the 2-nd parameter of the keyword TABDIMS (see 12.1.26)).
1. water phase pressure (METRIC: barsa, FIELD: psia);
2. water formation volume factor (METRIC: rm3 /sm3 , FIELD: rb/stb);
3. water viscosity (cP).
In all table rows, except the first and the last row, the value of formation volume factor
and viscosity can be defaulted (linearly interpolated). Values outside the table pressure range
will be linearly extrapolated.
Example
WATERTAB
69 1.0099 0.70
276 1.0000 0.70
620 0.9835 0.70 /
150 1.0008 0.70
300 1.0002 0.70
500 0.9899 0.70 /
In this table water pressure tables are specified for two PVT regions.
12.13.9. WATERTAB 901

12.13.10 ZI


Section
This keyword sets initial composition for each equation of state region (EOSNUM (see
12.4.21)) for a compositional run. Each value molar composition of corresponding compo-
nent. (N is number of components defined in COMPS, see 12.13.3) Note that molar fractions
on each line must add up to unity.
Number of tables depends on number of equation of state regions defined in 9-th param-
eter of TABDIMS (see 12.1.26). Each table must be terminated by a slash /.
Note:
1. If in the PROPS section there is COMPVD (see 12.13.11) or ZMFVD (see 12.13.14)
or ZI (see 12.13.10), then it is used.
2. If in the PROPS section component composition versus depth is not specified (no
COMPVD (see 12.13.11), ZMFVD (see 12.13.14), ZI (see 12.13.10)), but component
composition is specified in SOLUTION in each grid block (ZMF (see 12.15.19) is
present), then:
a message will be written: that the constant distribution of the component compo-
sition for EQUIL regions will be built, based on the composition in the blocks of
each EQUIL region (using ZMF (see 12.15.19) correspondingly);
the table ZMFVD (see 12.13.14) is constructed and used in EQUIL (see 12.15.2);
the table ZMFVD (see 12.13.14) is saved in the .log-file.
Example
COMPS
5/
ZI
0.01 0.62 0.18 0.07 0.12
/
In this example initial composition for 5 components is specified for one equilibration
region.
12.13.10. ZI 902
12.13.11 COMPVD


Section
The keyword specifies the total compositions with respect to depth for compositional
models. The table should be specified for each equilibrium region (EQLDIMS (see 12.1.27))
and be terminated with a slash /.
The numbers of columns depends on the number of components (COMPS (see 12.13.3)).
depth (METRIC: m, FIELD: f t );
...
values of zi , phase mole fractions (columns from 2 to Nc + 1). Sum of all Nc mole
fractions must be equal to 1;
...
0 (vapor) or 1 (liquid) flag indicating if the fluid at this depth is above or below
GOC;
saturation pressure Psat at this depth (METRIC: bars, FIELD: psi).
Note:
present), then:
12.13.11. COMPVD 903

Example
COMPVD
1290 0.025 0.025 0.14 0.65 0.16 0 243
1330 0.025 0.025 0.14 0.64 0.17 0 245
1350 0.021 0.029 0.15 0.69 0.11 1 242
/
In this example total composition is specified for three depth values. Gas composition is
specified at depth 1290 and 1330 metres, liquid composition at depth 1350 metres.
12.13.11. COMPVD 904

12.13.12 XMFVP


Section
This keyword specifies the table of liquid composition versus pressure (distribution of
concentration matrix xc,O c = 1, . . . , n0c . The data should be terminated with a slash /.
The table should be specified for each equilibrium region (EQLDIMS (see 12.1.27)).
pressure P;
the corresponding value of concentration x1,O of first component at pressure P;
the corresponding value of concentration x2,O of second component at pressure P;
...
the corresponding value of concentration xn0c ,O of n0c component at pressure P
An arbitrary number of lines with different pressures can be specified. The data should
Example
XMFVP
1200 0.025 0.025 0.14 0.65 0.16
1800 0.025 0.025 0.14 0.65 0.16
/
In this example concentration matrix is specified for two different values of pressure.
12.13.12. XMFVP 905

12.13.13 YMFVP


Section
This keyword specifies the table of vapor composition versus pressure (distribution of
concentration matrix xc,G c = 1, . . . , n0c , P = O, G (for P = W )). The data should be termi-
The table should be specified for each equilibrium region (EQLDIMS (see 12.1.27)).
pressure P;
the corresponding value of concentration x1,G of first component at pressure P;
the corresponding value of concentration x2,G of second component at pressure P;
...
the corresponding value of concentration xn0c ,G of n0c component at pressure P
An arbitrary number of lines with different pressures can be specified. The data should
Example
YMFVP
60 0.0 0.0 0.806 0.194 0.0
100 0.0 0.0 0.806 0.194 0.0 /
In this example concentration matrix is specified for two different values of pressure.
12.13.13. YMFVP 906

12.13.14 ZMFVD


Section
This keyword sets initial composition with respect to depth data for each equilibration
region (for a compositional run). First column lists depth values, the rest N columns (N
is number of components defined in COMPS, see 12.13.3) list molar composition of corre-
sponding components for this depth. Note that molar fractions on each line must add up to
unity.
For depth values outside the specified range, constant value extrapolation will be per-
formed. Table may consist of only one line; this would result in constant component distri-
bution for all equilibration regions.
Number of tables depends on number of equilibration regions defined in EQLDIMS (see
12.1.27). Each table must be terminated by a slash /.
Default: none.
Note:
present), then:
12.13.14. ZMFVD 907

Example
EQLDIMS
1 /
...
COMPS
5
/
...
ZMFVD
1800 0.01 0.64 0.19 0.06 0.1
2000 0.01 0.62 0.18 0.07 0.12
/
In this example mixture composition is defined for depths 1800 and 2000. Between these
depths linear interpolation will be used, outside the interval composition will remain constant.
Example
EQLDIMS
2 /
...
COMPS
5
/
...
ZMFVD
1800 0.01 0.64 0.19 0.06 0.1
2000 0.01 0.62 0.18 0.07 0.12
/
2000 0.01 0.62 0.18 0.07 0.12
/
In this example mixture composition in first equilibration region is defined for depths
1800 and 2000. Between these depths linear interpolation will be used, outside the interval
composition will remain constant. In the second equilibration region constant composition is
defined.
12.13.14. ZMFVD 908

12.13.15 NEI


Section
This keyword sets initial composition for non-equilibrium initialization for each equili-
bration region (for a compositional run). (EQLDIMS (see 12.1.27), EQLNUM (see 12.4.9)).
After the keyword N values should be specified: molar composition of components in

the mixture for an equilibration region (N is number of components defined in COMPS (see
12.13.3)).
The data for each equilibration should be terminated with a slash /.
Initial oil and gas phase composition can be specified via keywords XMF (see 12.15.17),
YMF (see 12.15.18), XMFVP (see 12.13.12), YMFVP (see 12.13.13).
Example
NEI
0.384480 0.067150 0.141940 0.067050 0.089940 0.109580
0.087820 0.052040 /
12.13.15. NEI 909

12.13.16 KVTABLE


Section
The keyword specifies the table of K-values to control liquid-vapor phase equilibrium.
If the keyword KVALUES (see 12.1.70) is enable, then the values, specified via this key-
word, will be used instead of the equation of state equal fugacity relationships to obtain the
composition of the liquid and vapor hydrocarbon phases in a cell, and the split of the total
moles in the cell between these phases.
The table can contain an arbitrary number of rows. The table should be terminated with
a slash /.
oil phase pressure (METRIC: barsa, FIELD: psia);

y1
K-value of 1-st component K1 = x1 , where y1 , x1 mole fractions of component 1 in
vapor and liquid phases;
y2
K-value of 2-nd component K2 = x2 , where y2 , x2 mole fractions of component 2
in vapor and liquid phases;
...
yN
K-value of N -th component KN = xN , where yN , xN mole fractions of component
N in vapor and liquid phases;
Example
KVTABLE
220 1.08 1.22 1.21 0.15 0.038
300 1.21 1.45 0.98 0.43 0.022
350 1.27 1.46 0.92 0.46 0.017
/
In this example there is a table of K-values for 5 components.
12.13.16. KVTABLE 910

12.13.17 TCRIT


Section
The keyword associates critical temperature (METRIC: K, FIELD: R) with each com-
ponent of a compositional model for each EoS region. For each region a line of N values
should be entered, where N is number of components defined in COMPS (see 12.13.3). Each
line must be terminated by a slash /. Number of lines depends on number of EoS regions
defined in TABDIMS (see 12.1.26) (9-th parameter).
In case of metric system temperature should be specified in Kelvin degrees, and for field
unit system in Rankine degrees (see 10).
If component name is present in table 12.13.1, default values may be used for this com-
ponent.
Default: values from table 12.13.1
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
TCRIT
3.047000000E+02 1* 4.252000000E+02 6.260000000E+02
/
Here critical temperature is specified for components {CO2 ,C1 , NC4 ,C10 }. Value for
component C1 will be defaulted from table 12.13.1.
12.13.17. TCRIT 911

Example
TABDIMS
1 2 2* 4 4*2
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C8
/
...
TCRIT
4*
/
3* 6.260000000E+02
/
Here critical temperature is specified for components {CO2 ,C1 , NC4 ,C8 }. In the first
region default temperature values will be taken from table 12.13.1, in the second region all
values but for component C8 will also be taken by default.
12.13.17. TCRIT 912

12.13.18 TCRITS


Section
The keyword associates critical temperature (METRIC: K, FIELD: F) with each com-
ponent of a compositional model for each EoS region for calculations in surface conditions.
If this keyword is specified then for calculations in surface conditions all parameters are
taken from this keyword, and for reservoir conditions parameters, specified via TCRIT (see
12.13.17). Thus two sets of parameters can be used. The list of all keywords that specify
parameters for calculations in surface and reservoir conditions is in the section 3.1.1.
For each region a line of N values should be entered, where N is number of components
defined in COMPS (see 12.13.3). Each line must be terminated by a slash /. Number of lines
depends on number of EoS regions defined in TABDIMS (see 12.1.26) (9-th parameter).
In case of metric system temperature should be specified in Kelvin degrees, and for field
unit system in Rankine degrees (see 10).
ponent.
Default: values TCRIT (see 12.13.17).
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
TCRITS
3.047000000E+02 1* 4.252000000E+02 6.260000000E+02
/
12.13.18. TCRITS 913

12.13.19 PCRIT


Section
The keyword associates critical pressure (METRIC: barsa, FIELD: psia) with each com-
ponent of a compositional model for each EoS region. For each region a line of N values
should be entered, where N is number of components defined in COMPS (see 12.13.3). Each
line must be terminated by a slash /. Number of lines depends on number of EoS regions
defined in TABDIMS (see 12.1.26) (9-th parameter).
ponent.
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
PCRIT
1* 4.604208000E+01 3.796647750E+01 2.419641000E+01
/
Here critical pressure for components {CO2 ,C1 , NC4 ,C10 } is specified. Value for CO2
will be defaulted from table 12.13.1.
12.13.19. PCRIT 914

Example
TABDIMS
2 2 2* 4 4*2
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C8
/
...
PCRIT
7.386592500E+01 4.604208000E+01 3.796647750E+01 2.87000E+01
/
1* 4.604209000E+01 2*
/
Here critical pressure for components {CO2 ,C1 , NC4 ,C8 } is specified. In the second
region all values but for component C1 will be taken by default from table 12.13.1.
12.13.19. PCRIT 915

12.13.20 PCRITS


Section
The keyword associates critical pressure (METRIC: barsa, FIELD: psia) with each com-
ponent of a compositional model for each EoS region for calculations in surface conditions.
taken from this keyword, and for reservoir conditions parameters, specified via PCRIT (see
For each region a line of N values should be entered, where N is number of compo-
nents defined in COMPS (see 12.13.3). Each line must be terminated by a slash /. Number of
lines depends on number of EoS regions defined in TABDIMS (see 12.1.26) (9-th parameter).
ponent.
Default: values PCRIT (see 12.13.19).
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
PCRITS
1* 4.604208000E+01 3.796647750E+01 2.419641000E+01
/
12.13.20. PCRITS 916

12.13.21 VCRIT


Section
The keyword associates critical volume (METRIC: m3 /kg.M , FIELD: f t 3 /lb.M ) with
each component of a compositional model for each EoS region. For each region a line of
N values should be entered, where N is number of components defined in COMPS (see
12.13.3). Each line must be terminated by a slash /. Number of lines depends on number of
EoS regions defined in TABDIMS (see 12.1.26) (9-th parameter).
ponent.
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
VCRIT
3* 5.340000000E-01
Here critical volumes for components {CO2 ,C1 , NC4 ,C10 } are specified. Values for com-
ponents CO2 ,C1 , NC4 are taken by default from table 12.13.1.
12.13.21. VCRIT 917

Example
TABDIMS
2 2 2* 4 4*2
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
VCRIT
3* 5.340000000E-01
/
3* 5.350000000E-01
/
Here critical volumes for components {CO2 ,C1 , NC4 ,C10 } are specified for two regions.
Values for components CO2 ,C1 , NC4 will be taken by default from table 12.13.1.
12.13.21. VCRIT 918

12.13.22 VCRITS


Section
The keyword associates critical volume (METRIC: m3 /kg.M , FIELD: f t 3 /lb.M ) with
each component of a compositional model for each EoS region for calculations in surface
conditions.
taken from this keyword, and for reservoir conditions parameters, specified via VCRIT (see
ponent.
Default: values VCRIT (see 12.13.21).
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
VCRITS
3* 5.340000000E-01
12.13.22. VCRITS 919

12.13.23 VCRITVIS


Section
This keyword specify critical volumes (METRIC: m3 /kg.M , FIELD: f t 3 /lb.M ) (which
will be used for viscosity calculation only) for each component of a compositional model for
each EoS region. For each region a line of N values should be entered, where N is number
of components defined in COMPS (see 12.13.3).
Each line must be terminated by a slash /. Number of lines depends on number of EoS
regions defined in TABDIMS (see 12.1.26) (9-th parameter).
If the keywords ZCRITVIS (see 12.13.26), VCRITVIS (see 12.13.23) are not specified,
the data from the keywords ZCRIT (see 12.13.24), VCRIT (see 12.13.21) will be used.
Example
COMPS
4
/
VCRITVIS
5.350000000E-01 5.340000000E-01 4.320000000E-01 3.890000000E-
01
/
In this example critical volumes (which will be used for viscosity calculation only) are
entered for 4 components.
12.13.23. VCRITVIS 920

12.13.24 ZCRIT


Section
This keyword specify critical Z-factor for each component of a compositional model for
each EoS region. For each region a line of N values should be entered, where N is number
of components defined in COMPS (see 12.13.3).
Critical Z-factors are used to calculate critical molar volume via the following relation-
ship:
Vc = Zc RTc /Pc
Example
COMPS
6
/
ZCRIT
0.290
0.277
0.264
0.257
0.245
0.235
/
In this example critical Z-factors are entered for 6 components.
12.13.24. ZCRIT 921

12.13.25 ZCRITS


Section
This keyword specify critical Z-factor for each component of a compositional model for
each EoS region for calculations in sufrace conditions.
taken from this keyword, and for reservoir conditions parameters, specified via ZCRIT (see
For each region a line of N values should be entered, where N is number of components
defined in COMPS (see 12.13.3).
Critical Z-factors are used to calculate critical molar volume via the following relation-
ship:
Vc = Zc RTc /Pc
Default: values ZCRIT (see 12.13.24).
Example
COMPS
6
/
ZCRITS
0.290
0.277
0.264
0.257
0.245
0.235
/
In this example critical Z-factors are entered for 6 components.
12.13.25. ZCRITS 922

12.13.26 ZCRITVIS


Section
This keyword specify critical Z-factor (which will be used for viscosity calculation only)
for each component of a compositional model for each EoS region. For each region a line
of N values should be entered, where N is number of components defined in COMPS (see
12.13.3).
Critical Z-factors are used to calculate critical molar volume (for use in viscosity correla-
tion) via the following relationship:
Vc = Zc RTc /Pc
If the keywords ZCRITVIS (see 12.13.26), VCRITVIS (see 12.13.23) are not specified,
the data from the keywords ZCRIT (see 12.13.24), VCRIT (see 12.13.21) will be used.
Example
COMPS
6
/
ZCRITVIS
0.290
0.277
0.264
0.257
0.245
0.235
/
In this example critical Z-factors (which will be used for viscosity calculation only) are
entered for 6 components.
12.13.26. ZCRITVIS 923

12.13.27 MW


Section
The keyword associates molecular weight with each component of a compositional model
for each EoS region (METRIC: kg/kg M , FIELD: lb/lb M ). For each region a line of
N values should be entered, where N is number of components defined in COMPS (see
12.13.3). Each line must be terminated by a slash /. Number of lines depends on number of
EoS regions defined in TABDIMS (see 12.1.26) (9-th parameter).
ponent.
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
MW
4.401000000E+01 1.604300000E+01 5.812400000E+01
1.340000000E+02
/
Here molecular weights for components {CO2 ,C1 , NC4 ,C10 } are specified.
12.13.27. MW 924
Example
TABDIMS
2 3 2* 4 4*3
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
MW
3* 1.342000000E+02
/
3* 1.343000000E+02
/
4.401000000E+01 1.604300000E+01 5.812400000E+01
1.342000000E+02
/
Here molecular weights for components {CO2 ,C1 , NC4 ,C10 } are specified in three EoS
regions. Molecular weights of first three components in first two regions will be taken by
default from table 12.13.1.
12.13.27. MW 925
12.13.28 MWS


Section
The keyword associates molecular weight with each component of a compositional model
for each EoS region for calculations in surface conditions (METRIC: kg/kg M , FIELD:
lb/lb M ).
taken from this keyword, and for reservoir conditions parameters, specified via MW (see
ponent.
Default: values MW (see 12.13.27).
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
MWS
4.401000000E+01 1.604300000E+01 5.812400000E+01
1.340000000E+02
/
Here molecular weights for components {CO2 ,C1 , NC4 ,C10 } are specified.
12.13.28. MWS 926

12.13.29 MWW


Section
The keyword sets molecular weight for water component of a compositional model for
each EoS region (METRIC: kg/kg M , FIELD: lb/lb M ). This keyword is supported only
for models with one water component.
The data for each region must be terminated by a slash /. Number of lines depends on
number of EoS regions defined in TABDIMS (see 12.1.26) (9-th parameter).
Default: 18.0.
Example
MWW 18.3 /
In this example water molecular weight is set for one EoS region.
12.13.29. MWW 927

12.13.30 ACF


Section
The keyword associates acentric factor with each component of a compositional model
for each EoS region. For each region a line of N values should be entered, where N is
number of components defined in COMPS (see 12.13.3). Each line must be terminated by
a slash /. Number of lines depends on number of EoS regions defined in TABDIMS (see
ponent.
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
ACF
2.250000000E-01 1.300000000E-02 1* 3.850000000E-01
/
Here acentric factors are specified for components {CO2 ,C1 , NC4 ,C10 }. Value for NC4
will be taken by default from table 12.13.1.
12.13.30. ACF 928

Example
TABDIMS
2 2 2* 4 4*2
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C8
/
...
ACF
3* 0.311
/
2.250000000E-01 1.300000000E-02 1* 0.313
/
Here acentric factors are specified for components {CO2 ,C1 , NC4 ,C8 }. Values for com-
ponents {CO2 ,C1 , NC4 } in the first region and for component NC4 in the second region will
be taken by default from table 12.13.1.
12.13.30. ACF 929

12.13.31 ACFS


Section
The keyword associates acentric factor with each component of a compositional model
for each EoS region for calculations in surface conditions.
taken from this keyword, and for reservoir conditions parameters, specified via ACF (see
ponent.
Example
ACFS
2.250000000E-01 1.300000000E-02 1* 3.850000000E-01
/
12.13.31. ACFS 930

12.13.32 BIC


Section
The keyword specifies binary interaction coefficients between the components of a com-
positional model for each EoS region. For each region a table of N(N 1)/2 values should
be specified, where N is number of components defined in COMPS (see 12.13.3). These
elements form lower triangular part of binary interaction matrix.
Number of tables depends on number of EoS regions defined in TABDIMS (see 12.1.26)
(9-th parameter). Each table must be terminated by a slash /.If component name is present
in table 12.13.1, default values may be used for this component.
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
BIC
1.000000015E-01
1.000000015E-01 0.000000000E+00
1.000000015E-01 4.161999677E-02 0.000000000E+00
/
Here binary interaction coefficients for components {CO2 ,C1 , NC4 ,C10 } are specified.
12.13.32. BIC 931

Example
TABDIMS
2 2 2* 4 4*2
/
...
COMPS
3
/
CNAMES
methane ethane Cplus
/
...
BIC
-1.000000015E-01
1.000000015E-01 0.000000000E+00
/
-1.000000016E-01
1.000000015E-01 0.000000000E+00
/
Here binary interaction coefficients are specified for two EoS regions.
12.13.32. BIC 932

12.13.33 BICS


Section
The keyword specifies binary interaction coefficients between the components of a com-
positional model for each EoS region for calculations in surface conditions.
taken from this keyword, and for reservoir conditions parameters, specified via BIC (see
For each region a table of N(N 1)/2 values should be specified, where N is number
of components defined in COMPS (see 12.13.3). These elements form lower triangular part
of binary interaction matrix.
Number of tables depends on number of EoS regions defined in TABDIMS (see 12.1.26)
(9-th parameter). Each table must be terminated by a slash /.If component name is present
in table 12.13.1, default values may be used for this component.
Default: values BIC (see 12.13.32).
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
BICS
1.000000015E-01
1.000000015E-01 0.000000000E+00
1.000000015E-01 4.161999677E-02 0.000000000E+00
/
12.13.33. BICS 933

Here binary interaction coefficients for components {CO2 ,C1 , NC4 ,C10 } are specified.
12.13.33. BICS 934

12.13.34 OMEGAA / OMEGAB


Section
Default values of parameters a0 and b0 can be overridden via the keywords OMEGAA
(see 12.13.34) and OMEGAB (see 12.13.34).
One value should be specified for one component. The data should be terminated with a
slash /.

RT a
p= .
v b (v + m1 b)(v + m2 b)

EOS m1 m2 a0 b0
RK, SRK 0 1 0.4274802 0.08664035
PR 1+ 2 1 2 0.457235529 0.07796074
If these keywords are used, the default values will be overridden.
Example
OMEGAA
0.459 0.457 0.461 0.462 0.457 /
OMEGAB
0.07791 0.07794 0.0777 0.0780 0.0777 /
In this example default values for 5 components will be overridden.
12.13.34. OMEGAA / OMEGAB 935

12.13.35 OMEGAAS / OMEGABS


Section
Default values of parameters a0 and b0 can be overridden via the keywords

OMEGAAS (see 12.13.35) and OMEGABS (see 12.13.35) for calculations in surface con-
ditions.
taken from this keyword, and for reservoir conditions parameters, specified via OMEGAA
(see 12.13.34) and OMEGAB (see 12.13.34). Thus two sets of parameters can be used.
The list of all keywords that specify parameters for calculations in surface and reservoir
conditions is in the section 3.1.1.
One value should be specified for one component. The data should be terminated with a
slash /.

RT a
p= .
v b (v + m1 b)(v + m2 b)

EOS m1 m2 a0 b0
RK, SRK 0 1 0.4274802 0.08664035
PR 1+ 2 1 2 0.457235529 0.07796074
Example
OMEGAAS
0.459 0.457 0.461 0.462 0.457 /
OMEGABS
0.07791 0.07794 0.0777 0.0780 0.0777 /
12.13.35. OMEGAAS / OMEGABS 936

12.13.36 LBCCOEF


Section
The keyword overrides default values of coefficients in viscosity correlation formula

Lohrenz-Bray-Clark (3.3.1). 5 values should be specified. The data should be terminated
with a slash /.
One should use the keyword LBCCOEFR (see 12.13.37) to set different coefficients for
each equation of state region.
Default values: a1 = 0.1023000, a2 = 0.0233640, a3 = 0.0585330, a4 = 0.0407580,

a5 = 0.0093324.
Example
LBCCOEF
2* 0.0565 1* 0.00922 /
In this example the coefficients a1 , a2 , a4 keep default values, the values of coefficients
a3 , a5 are overridden.
12.13.36. LBCCOEF 937

12.13.37 LBCCOEFR


Section
The keyword overrides default values of coefficients in viscosity correlation formula

Lohrenz-Bray-Clark (3.3.1) for each equation of state region. Equation of state regions are
specified via EOSNUM (see 12.4.21).
One should use the keyword LBCCOEF (see 12.13.36) to set the coefficients for whole
reservoir.
5 values should be specified for each equation of state region. The data for each region
Default values: a1 = 0.1023000, a2 = 0.0233640, a3 = 0.0585330, a4 = 0.0407580,

a5 = 0.0093324.
Example
LBCCOEF
2* 0.03 2* /
2* 0.0565 1* 0.00922 /
In this example the coefficients are set for 2 equation of state region.
For the 1-st region: a1 , a2 , a4 , a5 keep default values, the value of coefficient a3 is overridden.
For the 2-nd region: a1 , a2 , a4 keep default values, the values of coefficients a3 , a5 are
overridden.
12.13.37. LBCCOEFR 938

12.13.38 FACTLI


Section
The keyword adds a factor (usually a value from 0.7 to 1.3) to the Li correlation for
the critical temperature. One value should be entered for each equilibration region. The data
Default: 1.
Li correlation formula for the critical temperature of a fluid mixture:
i TciVci zi
Tcrit =
i Vci zi
If a cell is single-phase cell (without fluid in bubble or dew point), Tcrit is compared with
the reservoir temperature to determine in which phase is fluid: liquid or gas. (Ordinarily it is
used at a distance from two-phase region).
Factor by which Tcrit will be multiplied, is used to set the point at which the cell is
nominally containing oil or gas. To avoid installing state oil for saturated condensate one
should enter a value less than 1.
Example
FACTLI
0.82 0.84 0.89 /
In this example factors for Li correlation is specified for three equilibration regions.
12.13.38. FACTLI 939

12.13.39 LILIM


Section
This keyword specifies limits for Li correlation. The data should be terminated with a
slash /.
Two parameters should be specified:

1. lower limit for hydrocarbon-water interpolation fG ;
2. upper limit for hydrocarbon-water interpolation fO .
Default:
lower limit for hydrocarbon-water interpolation fG 0.75;
upper limit for hydrocarbon-water interpolation fO 1.25.
These values are used to calculate the water-hydrocarbon relative permeability for single-
phase state of hydrocarbons. The relative permeability of the oil-gas and gas-oil are used
only when both phases are present. Coefficient of water-hydrocarbon KrG should be closer
to the value KrO , entered by user, if the composition is close to the oil, and to KrG , entered
by user, if the composition is close to the gas. To set a variable to interpolate between these
two values, the critical temperature Tcrit is used:
Li correlation formula for the critical temperature of a fluid mixture:
i TciVci zi
Tcrit =
i Vci zi
The ration of critical temperature to reservoir temperature:
Tcrit
f=
Treservoir
If reservoir temperature is equal to critical temperature, then f = 1. For oil f > 1, for gas
f < 1. This keyword can specify the values at which the system is considered as totally oil
system (default fO 1.25) or totally gas system (default fG 0.75), interpolation formula is
defined in the region fG < f < fO via the following formula:
f fG
E=
fO fG
In gas-like system 0 ( f < fG ); in oil-like system 1 ( f > fO ). In the midpoint values -
linear interpolation.
12.13.39. LILIM 940

Example
LILIM
0.82 1.12 /
12.13.39. LILIM 941

12.13.40 PRCORR


Section
The keyword defines that modified Peng-Robinson equation of state is used. This equa-
tion is called PR in the section 3.1.
12.13.40. PRCORR 942

12.13.41 SSHIFT


Section
The keyword specifies equation of states shift parameters 3.5. The data should be termi-
Example
SSHIFT
0.0 0.019066509 -0.4412272 -0.5106669 -0.10078032 -0.11951863
/
12.13.41. SSHIFT 943

12.13.42 SSHIFTS


Section
The keyword specifies equation of states shift parameters 3.5 for calculation in surface
conditions. The data should be terminated with a slash /.
taken from this keyword, and for reservoir conditions parameters, specified via SSHIFT
(see 12.13.41). Thus two sets of parameters can be used. The list of all keywords that specify
Default: values SSHIFT (see 12.13.41).
Example
SSHIFTS
0.0 0.019066509 -0.4412272 -0.5106669 -0.10078032 -0.11951863
/
12.13.42. SSHIFTS 944

12.13.43 EPSCOMP


Section
The keyword specified the number of component which molar concentration is used in
interpolation of end-point scaling tables ENKRVC (see 12.13.44), ENPCVC (see 12.13.45),
ENPTVC (see 12.13.46).
The number of specified values should be equal to the number of saturation function
region (1-st parameter of TABDIMS (see 12.1.26)). Each value should be terminated with a
slash /.
Example
EPSCOMP
2 /
In this example the end-point dependence will be from the molar concentration of the
2-nd component.
12.13.43. EPSCOMP 945

12.13.44 ENKRVC


Section
The keyword specifies relative permeability end point versus composition tables. The
number of specified tables should be equal to the number of saturation function region (1-st
parameter of TABDIMS (see 12.1.26)). Each table should be terminated with a slash /.
1. molar concentration of the component specified via the keyword EPSCOMP (see
12.13.43);
2. the corresponding value of maximum water relative permeability (krW );
3. the corresponding value of maximum gas relative permeability (krG );
4. the corresponding value of maximum oil relative permeability (krO );
5. water relative permeability at the critical oil saturation (krW r );
6. gas relative permeability at the critical oil (or gas) saturation (krGr );
7. oil relative permeability at the critical gas saturation (krOrG ) (oil saturation = 1 -
minimum water saturation - critical gas saturation);
8. oil relative permeability at the critical water saturation (krOrW ) (oil saturation = 1 -
critical water saturation - minimum gas saturation).
Parameters 2-8 should have values in th range from 0.0 to 1.0.
By default one one method of end-points scaling can be used:
usual end-points scaling (ENDSCALE).
temperature-dependent end-points (ENPTVT (see 12.14.69), ENKRVT (see 12.14.70),

ENPCVT (see 12.14.71)).
composition-dependent end-points (ENPTVC (see 12.13.46), ENKRVC (see 12.13.44),

ENPCVC (see 12.13.45)).
(see 12.6.24).
12.13.44. ENKRVC 946

Example
ENKRVC
0 0.72 1.0 1.0 0.324 2* 0.35
1 0.78 0.94 0.95 0.358 2* 0.36 /
12.13.44. ENKRVC 947

12.13.45 ENPCVC


Section
The keyword specifies maximum capillary pressure end point versus composition tables.
The number of specified tables should be equal to the number of saturation function region
(1-st parameter of TABDIMS (see 12.1.26)). Each table should be terminated with a slash /.
12.13.43);
2. the corresponding value of maximum oil-gas capillary pressure (PcG ) (METRIC: bars,
FIELD: psi);
3. the corresponding value of maximum water-oil capillary pressure (PcG ) (METRIC:

bars, FIELD: psi).

ENPCVT (see 12.14.71)).

ENPCVC (see 12.13.45)).
(see 12.6.24).
Example
ENPCVC
0 0.11 1.52
1 0.09 2.14 /
12.13.45. ENPCVC 948

12.13.46 ENPTVC


Section
The keyword specifies saturation end point versus composition tables. The number of
specified tables should be equal to the number of saturation function region (1-st parameter
of TABDIMS (see 12.1.26)). Each table should be terminated with a slash /.

12.13.43);
2. the corresponding value of connate water saturation (SW l );
3. the corresponding value of critical water saturation (SW cr );
4. the corresponding value of maximum water saturation (if table end-points are entered
cell by cell the keyword SWU (see 12.6.34) can be used); (SWu );
5. the corresponding value of connate gas saturation (SGl );
6. the corresponding value of critical gas saturation (SGcr );
7. the corresponding value of maximum gas saturation (SGu );
8. the corresponding value of critical oil-in-water saturation (SOW cr );
9. the corresponding value of critical oil-in-gas saturation (SOGcr ).
Parameters 2-9 should have values in th range from 0.0 to 1.0.

ENPCVT (see 12.14.71)).
ENPCVC (see 12.13.45)).
(see 12.6.24).
12.13.46. ENPTVC 949

Example
ENPTVC
0 0.15 0.19 1.0 0.0 0.06 1.0 0.19 0.23
1 0.23 0.23 1.0 0.0 0.06 1.0 0.19 0.23 /
12.13.46. ENPTVC 950

12.13.47 DIFFCGAS


Section
This keyword specifies a gas phase diffusion coefficients for each component in the model
(METRIC: m2 /day, FIELD: f t 2 /day).
Option of molecular diffusion is swithed on via the keyword DIFFUSE (see 12.1.66). The
diffusion coefficients for oil phase is specified via DIFFCOIL (see 12.13.48). Oil diffusion
coefficients are usually lower than gas diffusion coefficients (by an order). See an example
below.
The number of values should be equal to the number of conponents in the model. The
Default: 0.
Example
DIFFUSE
FIELD
...
DIFFCGAS
0.42 0.42 0.30 0.30 0.12 0.06 /
DIFFCOIL
0.042 0.042 0.030 0.030 0.012 0.006 /
12.13.47. DIFFCGAS 951

12.13.48 DIFFCOIL


Section
This keyword specifies an oil phase diffusion coefficients for each component in the
model (METRIC: m2 /day, FIELD: f t 2 /day).
Option of molecular diffusion is swithed on via the keyword DIFFUSE (see 12.1.66). The
diffusion coefficients for gas phase is specified via DIFFCGAS (see 12.13.47). Oil diffusion
coefficients are usually lower than gas diffusion coefficients (by an order). See an example
below.
The number of values should be equal to the number of conponents in the model. The
Default: 0.
Example
DIFFUSE
FIELD
...
DIFFCGAS
0.42 0.42 0.30 0.30 0.12 0.06 /
DIFFCOIL
0.042 0.042 0.030 0.030 0.012 0.006 /
12.13.48. DIFFCOIL 952

12.13.49 VDKRG


Section
The keyword is used to specify the tables of gas velocity dependent relative permeability
(VELDEP (see 12.1.7)). The number of tables is specified by the first parameter of the
keyword TABDIMS (see 12.1.26). Enter of each table should be ended by symbol /.
The following parameters should be specified in each table:
1. mg - parameter that changes critical gas saturation dependent on normalized capillary

number;
2. n1g - this and n2g parameters controls the weighting between miscible and immiscible
relative permeability curves;
3. n2g - see n1g parameter;
4. The base capillary number for gas Ncbd - this is the threshold value of capillary number.
If value of capillary number greater than the base one, then VDRP effect is expected to
activate;
5. Forchheimer parametera ag for gas. This value should be specified for Forchheimer
model B1 (UNITS: Forch(mD)d , 1 Forch = 1 atm.s2 .gm1 ; value of d is set by
parameter 8);
6. Forchheimer parameter bg for gas. This value should be specified for Forchheimer
model B1 ;
7. Forchheimer parameter cg for gas;
8. Forchheimer parameter dg for gas;
9. Forchheimer parameter dg for gas. This value should be specified for Forchheimer
model B2 B2 (UNITS: Forch/(mD)d , 1 Forch = 1 atm.s2 .gm1 ; value of d is set by
parameter 8).
By default:
0 for all parameters.
12.13.49. VDKRG 953

Example
VDKRG
M N1 N2 Ncb
23.89 6.23 0.0 6.0E-05 /
In the example is specified one table. The base gas capillary number was specified by the
keyword VELDEP.
12.13.49. VDKRG 954

12.13.50 VDKRGC


Section
The keyword sets data for capillary number based model of velocity dependent relative
permeability for near wellbore gas flow in a gas condensate reservoir. The number of data
lines should be equal to the value of the 1-st parameter of the keyword TABDIMS (see
12.1.26).
Capillary number and Forchheimer model are set via the keyword VELDEP (see 12.1.7).
If the 5-th parameter of VELDEP (see 12.1.7) is 1, then parameters of VDKRGC (see
12.13.50) are used to calculate miscibility.
Each data line should contain the following parameters:
1. exponent n. It is used to calculate miscibility which combines the immiscible relative

permeability curve with the miscible one;
2. coefficient c0 . It is used to scale capillary number.
Each data line should be ended by a symbol /.

Default:
exponent n: 0.65;
coefficient c0 : 1.0E4.
Example
VDKRGC
0.7 1000 /
0.65 1000 /
12.13.50. VDKRGC 955

12.13.51 VDKRO


Section
The keyword is used to specify the tables of oil velocity dependent relative permeability
(VELDEP (see 12.1.7)). The number of tables is specified by the first parameter of the
keyword TABDIMS (see 12.1.26). Enter of each table should be ended by symbol /.
The following parameters should be specified in each table:
1. mg - parameter that changes critical oil saturation dependent on normalized capillary

number;
2. n1g - this and n2g parameters controls the weighting between miscible and immiscible
relative permeability curves;
3. n2g - see n1g parameter;
4. The base capillary number for gas Ncbo - this is the threshold value of capillary number.
If value of capillary number greater than the base one, then VDRP effect is expected to
activate;
5. Forchheimer parametera ag for oil. This value should be specified for Forchheimer
model B1 (UNITS: Forch(mD)d , 1 Forch = 1 atm.s2 .gm1 ; value of d is set by
parameter 8);
6. Forchheimer parameter bg for oil. This value should be specified for Forchheimer
model B1 ;
7. Forchheimer parameter cg for oil;
8. Forchheimer parameter dg for oil;
9. Forchheimer parameter dg for oil. This value should be specified for Forchheimer
model B2 (UNITS: Forch/(mD)d , 1 Forch = 1 atm.s2 .gm1 ; value of d is set by
parameter 8).
By default:
the number of tables: 1.
12.13.51. VDKRO 956

Example
VDKRO
M N1 N2 Ncb
79.62 24.2 0.0 6.0E-05 /
In the example is specified one table. The base oil capillary number was specified by the
keyword VELDEP.
12.13.51. VDKRO 957

12.13.52 PEDERSEN


Section
The keyword specifies that viscosities will be calculated via Pedersons method (see
section Pedersen Correlation).
If this keyword is not specified default method will be used - Lohrenz-Bray-Clark Correlation
(see section 3.3.1).
Example
PEDERSEN
12.13.52. PEDERSEN 958

12.13.53 PEDTUNE


Section
The keyword is used to set user parameters of Pedersen viscosity correlation (3.3.2)) in
the entire reservoir. If you need to set user parameters in each EoS region use the keyword
PEDTUNER (see 12.13.54).
1. parameter 1 value. Allowed values: 0.1 10;
2. parameter 2 value. Allowed values: 0.1 10.

Parameters 1 and 2 are used to calculate mixture molecular weight which is given by:
c 2.303 c 2.303
Mwmix = c1 1.304 104 (Mw 2 Mn 2 ) + Mn ,
where:
Mw weight average;
Mn number average mole weights ;
c1 and c2 parameters 1 and 2 which are set above.
3. parameter 3 value. Allowed values: -100 100;
4. parameter 4 value. Allowed values: -1000 1.5;
5. parameter 5 value. Allowed values: -0.15 0.1;
6. parameter 6 value. Allowed values: -0.2 1.1.

Parameters 3-6 are used to calculate the rotational coupling factors, which are given
by:
mix = 1 + c5 (rmix )c3 (Mwmix )c4
0 = 1 + c6 (rmix )c3
where:
rmix reduced density;

c3 , c4 , c5 and c6 parameters 3-6 which are set above.

Default:
12.13.53. PEDTUNE 959

parameter 1 value: 1;
parameter 2 value: 1;
parameter 3 value: 1.847;
parameter 4 value: 0.5173;
parameter 5 value: 7.378E-3;
parameter 6 value: 3.1E-2.
Example
PEDTUNE
0.1000 1.2190 /
In the example via the keyword PEDTUNE (see 12.13.53) user values of the first two
parameters of Pedersen correlation are set. Other ones are set by default.
12.13.53. PEDTUNE 960

12.13.54 PEDTUNER


Section
The keyword is analogous to the keyword PEDTUNE (see 12.13.53), but it is used to set
user values of Pedersen (3.3.2)) viscosity correlation for several EoS-regions.
Sets of parameters of these two keywords are the same. Parameters for each region are
set in separate line which should be ended by a symbol /.
Example
PEDTUNER
0.1000 1.2190 /
0.1000 1.3190 /
In the example by the keyword PEDTUNER (see 12.13.54) parameters of Pedersen

viscosity correlation are set for two EoS regions. The first two parameters are set by user,
the others are set by default.
12.13.54. PEDTUNER 961

12.13.55 NCOMPS


Section
This keyword confirms the number of components for compositional run in simulator
Enlipse. The keyword is optional and it shouldnt be used in tNavigator. Use the keyword
COMPS (see 12.13.3) to set the number of components.
12.13.55. NCOMPS 962

12.13.56 DNGL


Section
The keyword is used for compositional models which use gas plants producing NGLs
(natural gas liquid). It sets densities for components of NGL which defined via the keyword
GPTABLEN (see 12.15.23). Densities are converted to partial molar volumes, and the molar
volume of a NGL mixture is calculated as a mole fraction weighted sum.
1. NGL components densities (METRIC: kg/m3 , FIELD: lb/ f t 3 ). Nc values should be

specified, where Nc the number of the model components;
Default:
if DNGL (see 12.13.56) is not specified, then the data is taken from the keyword DREF
(see 12.14.34). If DREF (see 12.14.34) is not specified also, then default value 799.2
kg/m3 for each component is used.
Example
DNGL
776.0 802.0 424.6 547.5 581.1 608.4 640.4 720.5 800.5 803.7 /
In the example densities of 10 NGL components are specified.
12.13.56. DNGL 963

12.13.57 SOLUBILI


Section
The keyword sets properties of water-CO 2 system as a table. One table line should
contain the following parameters:
1. pressure (METRIC: barsa; FIELD: psia);
2. dissolved gas-water factor at the specified pressure (METRIC: sm3 /sm3 ; FIELD:
Msc f /stb);
3. formation volume of water saturated with gas at the specified pressure (METRIC:
rm3 /sm3 ; FIELD: rb/stb);
4. viscosity of water saturated with gas at the specified pressure (cP);
5. compressibility of water saturated with gas at the specified pressure (METRIC: 1/bar ;
FIELD: 1/psi).
Example
SOLUBILI
1.013 0.7537 1.0157 .30 .3E-4
54.29 23.09 1.0137 .30 .3E-4
373.9 36.68 .99052 .30 .3E-4
693.6 42.10 .97837 .30 .3E-4
1013. 47.52 .96725 .30 .3E-4
/
In the example properties of water-CO 2 system are set.
12.13.57. SOLUBILI 964

12.13.58 RSWVD


Section
The keyword sets CO 2 concentration in water phase dependence on depth as a table.

Each line of the table contains the following parameters:
1. depth values (METRIC: m; FIELD: f t ). They should increase monotonically down

column;
2. CO 2 concentration in water phase (METRIC: sm3 /sm3 ; FIELD: stb/Msc f ).
Example
RSWVD
200 0.001
20000 0.002
/
12.13.58. RSWVD 965

12.14. Thermal properties tNavigator-4.2
12.14 Thermal properties
12.14. Thermal properties 966

12.14.1 CVTYPE


Section

The keyword sets the component volatility type for each component. N values should be
entered (N number of components COMPS (see 12.13.3)). The data should be terminated
with a slash /.
The values should be the following:
LIVE if component is both volatile and condensible (can be in the oil ahd gas phase);
SOLID if component is only in solid phase;
DEAD if component is only in oil phase;
GAS if component is only in gas phase.
Example
COMPS
3 /
...
CVTYPE
LIVE GAS DEAD /
12.14.1. CVTYPE 967

12.14.2 WATDENT


Section

The keyword sets water molar density as s function of temperature for each PVT region (the
number of PVT regions is equal to the 2-nd parameter of TABDIMS (see 12.1.26)). The data
for each region should be terminated with a slash /.

1. reference temperature Tw,re f (METRIC: K, FIELD: R);
2. the first thermal expansion coefficient cw,1,T (METRIC: 1/ K , FIELD: 1/ R);
3. the second thermal expansion coefficient cw,2,T (METRIC: 1/ K 2 , FIELD: 1/ R2 ).

In e300 data format the mass density and the molar water density on default (or if the
keyword THANALB (see 12.14.3) is present) are calculated
W = e , W = W ,
1 + A6 T MWW
where
A0 = 9998.3952 A1 = 169.55176
A2 = 7.987 102 A3 = 46.170461 105
A4 = 105.56302 108 A5 = 280.54353 1011
A6 = 16.87985 102 A7 = 102
If the keyword WATDENT is enable, then
w,re f 1
W = , W = W
(1 cw,p (p pw,re f ))(1 + cw,1,T (T Tw,re f ) + cw,2,T (T Tw,re f )2 ) MWW
(12.4)
where
w,re f = W,SC /BW (pre f ) (kg/m3 )
W,SC is set via DENSITY (see 12.5.23)
cw,p , pw,re f , BW (pre f ), is set via PVTW (see 12.5.5)
cw,1,T , cw,2,T , Tw,re f , is set via WATDENT
MWW water molar weight
12.14.2. WATDENT 968

In stars data format the mass density and the molar water density are calculated
!
T 2 Tre2 f
W = w,re f exp cw,p (p pre f ) cw,1,T (T Tre f ) cw,2,T + cw,pT (p pre f )(T Tre f )
2
W = W MWW
where
pre f reference pressure PRSR (see 13.5.10)
Tre f reference temperature TEMR (see 13.5.11)
w,re f component density w from MOLDEN (see 13.5.14) (mol/m3 )
ck,p , ck,1,T , ck,2,T , ck,pT the properties of component w specified via CP (see
13.5.16), CT1 (see 13.5.17), CT2 (see 13.5.18), CPT (see 13.5.19)
Example
WATDENT
293 0.00027 0.0000034 /
12.14.2. WATDENT 969

12.14.3 THANALB


Section

The keyword sets that water molar and mass densities are calculated using the following
formulas
W = e , W = W ,
1 + A6 T MWW
where
A0 = 9998.3952 A1 = 169.55176
A2 = 7.987 102 A3 = 46.170461 105
A4 = 105.56302 108 A5 = 280.54353 1011
A6 = 16.87985 102 A7 = 102
If the keyword is missing but WATDENT (see 12.14.2) is specified, then densities are
calculated via 4.6.
Example
THANALB
12.14.3. THANALB 970

12.14.4 KVCR


Section

The keyword sets 5 constants (Ai , Bi , Ci , Di , Ei ) for each component. These constants are
used in the correlation formula:
Ki (p, T ) = (Ai + Bi /p +Ci p) eDi /(T Ei )
where p pressure, T temperature, i component number, Ki (p, T ) the ratio of mole

fractions of component in vapor and liquid phases.
1. Ai ; N values should be entered (N number of components COMPS (see 12.13.3)).
2. Bi ; N values should be entered (N number of components COMPS (see 12.13.3)).
3. Ci ; N values should be entered (N number of components COMPS (see 12.13.3)).
4. Di ; N values should be entered (N number of components COMPS (see 12.13.3)).
5. Ei ; N values should be entered (N number of components COMPS (see 12.13.3)).
If there are more then one EoS region, the data should be entered for all regions (the num-
ber of EoS regions is equal to the 9-th parameter of the keyword TABDIMS (see 12.1.26)).
The data for each region should be terminated with a slash /.
Ki (p, T )-values can be entered manually using the keywords KVTEMP (see 12.14.6),
KVTABTn (see 12.14.7).
K-values for surface calculation can be set optionally via KVCRS (see 12.14.5).
12.14.4. KVCR 971

Example
COMPS
3 /
...
KVCR
300 800 523
236030 544000 345220
0 0 0
5000 11000 7000
220 0 0
/
This example sets the coefficients for the correlation formula for 3 components.
12.14.4. KVCR 972

12.14.5 KVCRS


Section
This keyword sets K-values for surface calculation for thermal runs (THERMAL (see
12.1.50)).
K-values for reservoir calculation are set via KVCR (see 12.14.4).
This keyword is optional. If it is not specified then for surface calculation reservoir K-
values will be used.
Keyword syntax is similar to KVCR (see 12.14.4).
12.14.5. KVCRS 973

12.14.6 KVTEMP


Section

The keyword sets the temperature values (METRIC: C, FIELD: F) for Ki (p, T ) tables
entered using the keyword KVTABTn (see 12.14.7) for each component. Ki (p, T ) the
ratio of mole fractions of component in vapor and liquid phases. The number of temperature
values should be equal to the 15-th parameter of TABDIMS (see 12.1.26). The data should
Ki (p, T )-values can be entered using the correlation formula (KVCR (see 12.14.4)).
Example
KVTEMP
300 500 700
/
This example sets 3 temperature values for Ki (p, T ) tables.
12.14.6. KVTEMP 974

12.14.7 KVTABTn


Section

The keyword sets Ki (p, T ) tables for each component. Ki (p, T ) the ratio of mole fractions
of component in vapor and liquid phases. Each KVTABTn (see 12.14.7) corresponds to its
temperature, entered using KVTEMP (see 12.14.6).
The following parameters should be specified in one data line:
the oil phase pressure;
N values of Ki (p, T ) at this pressure (N - number of components COMPS (see

12.13.3)).
An arbitrary number of keywords can be entered. The data should be terminated with a slash
/.
Ki (p, T )-values can be entered using the correlation formula (KVCR (see 12.14.4)).
Example
KVTEMP
300 500 /
KVTABT1
45 0.0155 0.013
90 0.0075 0.003
/
KVTABT2
105 0.0055 0.0007
150 0.0045 0.0003
/
This example sets Ki (p, T ) tables for two temperature values entered using KVTEMP (see
12.14.6).
12.14.7. KVTABTn 975

12.14.8 KVTABLIM


Section

The keyword sets Ki (p, T ) tables for components. (Ki (p, T ) the ratio of mole fractions
of component in vapor and liquid phases.) For each component one should use individual
keyword KVTABLIM.
1. Component number.
2. The number of columns in Ki (p, T ) table.
3. The number of rows in Ki (p, T ) table (this value can be defaulted, then the number of
rows will be calculated automatically).
The parameters 1-3 should be terminated with a slash /.
4. The minimal value of pressure for Ki (p, T ) (METRIC: kPa, FIELD: psi) plow.
5. The maximal value of pressure for Ki (p, T ) (METRIC: kPa, FIELD: psi) phigh.
6. The minimal value of temperature for Ki (p, T ) (METRIC: C, FIELD: F) T low.
7. The maximal value of temperature for Ki (p, T ) (METRIC: C, FIELD: F) T high.

The parameters 4-7 should be terminated with a slash /.
After these parameters one should specify a Ki (p, T ) table, terminated with a slash /.
K(T low, plow) . . . K(T low, phigh)

... ... ...
K(T high, plow) . . . K(T high, phigh)
Interpolation between table entries:
between two Ki (p, T ) for two adjacent pressures: Ki (p, T ) varies linearly with the
coefficient 1/p;
between two non-zero Ki (p, T ) for two adjacent temperatures: ln(Ki (p, T )) varies
linearly with the coefficient 1/T ;
between two Ki (p, T ) (one of the value entries is zero) for two adjacent temperatures:
Ki (p, T ) varies linearly with the coefficient 1/T .
12.14.8. KVTABLIM 976

Example
KVTABLIM
3 2 1* /
10 500 20 250 /
0.0001 0.0008
0.01 0.09
/
In this example the Ki (p, T ) table for 3-rd component has 2 rows and 2 columns.
12.14.8. KVTABLIM 977

12.14.9 KVWI


Section

If KVWI is specified then Ki (p, T ) - values for oil components are calculated using the
following correlation formula (Ki (p, T ) the ratio of mole fractions of component in vapor
and liquid phases):
pci 5.372697(1+Ai )(1Tci /T )
Ki (p, T ) = e
p
where
Tci component critical temperature TCRIT (see 12.13.17);
pci component critical pressure PCRIT (see 12.13.19);
Ai component acentric factor ACF (see 12.13.30).
Ki = Ki (p, T ) -values can be entered directly using the tables KVTEMP (see 12.14.6),
KVTABTn (see 12.14.7), or correlation formula KVCR (see 12.14.4).
Example
KWVI
12.14.9. KVWI 978

12.14.10 HEATCR


Section

The keyword sets the rock volumetric heat capacity value for each grid block (METRIC:
kJ/m3 /K , FIELD: Btu/ f t 3 /F ). The same number of values should be specified as the
number of grid blocks. The data should be terminated with a slash /.
Heat capacity (Hrock ) in each grid block is calculated as:
Cr1 (T Tre f )2
Hrock = Cr0 (T Tre f ) +
2
where
Tre f reference temperature;
Cr0 rock volumetric heat capacity (doesnt depend on temperature), kJ/m3/K (is
specified using this keyword);
Cr1 temperature (T ) dependence of the rock volumetric heat capacity for each grid
block, kJ/m3/K/K (is specified using the keyword HEATCRT (see 12.14.11)).
Example
DIMENS
10 10 2
/
...
HEATCR
100*32 50*35 50*37 /
/
This example sets the rock volumetric heat capacity: for first 100 grid blocks 35
(kJ/m3/K), next 50 blocks 35 (kJ/m3/K) and the remaining 50 blocks 37 (kJ/m3/K).
12.14.10. HEATCR 979

12.14.11 HEATCRT


Section

The keyword sets the temperature dependence of the rock volumetric heat capacity for each
grid block (METRIC: kJ/m3 /K 2 , FIELD: Btu/ f t 3 /F 2 ). The same number of values should
be specified as the number of grid blocks. The data should be terminated with a slash /.
Cr1 (T Tre f )2
2
where
Tre f reference temperature;
Cr0 rock volumetric heat capacity (doesnt depend on temperature), kJ/m3/K (is
specified using the keyword HEATCR (see 12.14.10));
Cr1 temperature (T ) dependence of the rock volumetric heat capacity for each grid
block, kJ/m3/K/K (is specified using this keyword).
Example
DIMENS
10 10 2
/
...
HEATCRT
100*0.0004 50*0.0003 50*0.0001 /
/
This example sets the temperature dependence of the rock volumetric heat capacity: for
first 100 grid blocks 0.0004 (kJ/m3/K/K), next 50 blocks 0.0003 (kJ/m3/K/K) and the
remaining 50 blocks 0.0001 (kJ/m3/K/K).
12.14.11. HEATCRT 980

12.14.12 HEATTCR


Section

The keyword sets the rock heat capacity. The value of rock heat capacity is constant for
every rock region (the keyword ROCKNUM (see 12.4.14) specifies for every grid block the
number of rock region - transmissibility dependence on pressure table - to which it belongs).
The same number of values should be specified as the number of rock regions (see
below the Note how to set the number of rock regions). The data for each region should be
The keyword has an Eclipse compatible analogues HEATCR (see 12.14.10), HEATCRT
(see 12.14.11).
1. Cr0 the rock volumetric heat capacity (doesnt depend on temperature) (METRIC:
kJ/m3 /K , FIELD: Btu/ f t 3 /F );
2. Cr1 temperature T dependence of the rock volumetric heat capacity (METRIC:
kJ/m3 /K 2 , FIELD: Btu/ f t 3 /F 2 ).
Cr1 (T Tre f )2
2
where Tre f - reference temperature.
Default:
1. the rock volumetric heat capacity not specified,
2. temperature dependence of the rock volumetric heat capacity 0.
Note. Setting the number of rock regions:
The number of rock regions can be set in TABDIMS (see 12.1.26) (13-th parameter) and
ROCKCOMP (see 12.1.34) (2-nd parameter). The option to set the number of rock regions
depends on the way to set rock properties:
ROCKCOMP (see 12.1.34) ROCKTAB (see 12.5.18).
If the number of rock regions is specified both in 13-th parameter of TABDIMS (see
12.1.26) and in 2-nd parameter of ROCKCOMP (see 12.1.34), then the following logic
is used to calculate the number of rock regions:
12.14.12. HEATTCR 981

E100 format: only the 2-nd parameter of ROCKCOMP (see 12.1.34) is used;
E300 format: the maximum value is taken from the 13-th parameter of TABDIMS
(see 12.1.26), and 2-nd parameter of ROCKCOMP (see 12.1.34).
ROCK (see 12.5.16).

The number of rock regions is specified via 13-th parameter of TABDIMS (see 12.1.26);
if this parameter is not set then the number of rock regions is equal to the number of
PVT regions specified in 2-nd parameter of TABDIMS (see 12.1.26))..
Example
ROCKCOMP
0 2 0
/
...
HEATTCR
35 0.1 /
40 /
/
In this example there are 2 rock regions. First rock region: the rock volumetric heat
capacity 35, temperature dependence of the rock volumetric heat capacity - 0.1.
Second rock region: the rock volumetric heat capacity 40, temperature dependence of the
rock volumetric heat capacity default: 0.
12.14.12. HEATTCR 982

12.14.13 HEATVAP


Section

The keyword specifies the second Ac in the formula below (METRIC: kJ/kg, FIELD:
Btu/lb). The same number of values as the number of components: N should be entered
(COMPS (see 12.13.3)). The data should be terminated with a slash /.

Bc
where:
In e300 data format Ac is specified using the keyword HEATVAP (default: 0kJ/kg),
In stars data format A0c is specified using the keyword HVR (see 13.5.30) (default:
Bc (default: 0.38) is specified using the keyword HEATVAPE (see 12.14.14) (e300), EV
(see 13.5.31) (stars).
12.13.17) (e300), TCRIT (see 13.5.21) (stars).
Default: 0.
Example
HEATVAP
322 118 109 /
This example specifies the coefficient Ac for three components.
12.14.13. HEATVAP 983

12.14.14 HEATVAPE


Section

The keyword specifies the second Bc in the formula below. The same number of values as
the number of components: N should be entered (COMPS (see 12.13.3)). The data should

Bc
where:
In e300 data format Ac is specified using the keyword HEATVAP (see 12.14.13) (default:
0kJ/kg), In stars data format A0c is specified using the keyword HVR (see 13.5.30) (default:
Bc (default: 0.38) is specified using the keyword HEATVAPE (e300), EV (see 13.5.31)
(stars).
12.13.17) (e300), TCRIT (see 13.5.21) (stars).
Default: 0.38.
Example
HEATVAPE
3* /
This example specifies default values 0.38 for the coefficient Bc for three components.
12.14.14. HEATVAPE 984

12.14.15 THCONR


Section
This keyword can be used if THERMAL (see 12.1.50) is present or if temperature option
is enable (2.30).
The keyword sets the rock thermal conductivity (METRIC: kJ/m/day/C , FIELD:
Btu/ f t/day/F ). The same number of values should be specified as the number of grid
blocks. The data should be terminated with a slash /.
Default: 1.496 105 J/m day K = 24Btu/ f t day F
Example
DIMENS
20 20 10
/
...
THCONR
2000*180.86 1000*165 1000*180.86 /
/
In this example the rock thermal conductivity for 2000 grid blocks is equal to
180.86 kJ/m/C/day, for next 1000 blocks 165kJ/m/C/day, next 1000 blocks 180.86
kJ/m/C/day.
12.14.15. THCONR 985

12.14.16 THCONSF


Section

If the keyword is enable the thermal conductivity (specified using THCONR (see 12.14.15))
is multiplied by a multiplier 1 SG .
The value of shouldnt be less than 0 and greater than 1. is specified using this keyword.
The same number of values should be specified as the number of grid blocks. The data should
Example
DIMENS
10 10 2
/
...
THCONSF
100*0.01 100*0.05/
/
This example set the value of equal to 0.01 for 100 grid blocks and 0.05 for next grid
blocks.
12.14.16. THCONSF 986

12.14.17 ROCKT


Section
The keyword sets the rock compressibility factor for each PVT region (this factor depends
on the temperature).
The description of models that can be used in tNavigator (Linear Elastic, Nonlinear Elas-
tic, Dilation- Recompaction) is in the section 4.24.
Two parameters are to be specified in each row:
1. effective thermal expansion coefficient of the formation (cT );
2. pressure-temperature cross-term coefficient of the formation effective porosity (c pT );
3. effective formation compressibility near the value of 5-th parameter (METRIC: 1/kPa,
FIELD: 1/psi);
4. lower reference pressure for pressure-dependent formation compressibility (METRIC:

kPa, FIELD: psi). The value must be non-negative;
5. upper reference pressures for pressure-dependent formation compressibility (METRIC:

kPa, FIELD: psi). The value must be greater than the value of pressure at 4th param-
eter;
6. maximal fractional increase in porosity due to pressure.
Each row should be terminated with a slash /. The same number of rows as the number of
PVT regions should be specified (TABDIMS (see 12.1.26)).
Default: none.
In stars data format the porosity = (p, T, x, y, z) is
(p, T, x, y, z) = (x, y, z) (x, y, z)(1 + c p (p pre f ) cT (T Tre f ) + c pT (p pre f )(T Tre f ))
where
(x, y, z) net to gross factor (NETPAY);
(x, y, z) porosity at the pressure pre f (POR);
c p , cT , c pT compressibilities (CPOR, CTPOR, CPTPOR) (default: 0); tNavigator

also uses the keyword ROCKT (see 12.14.17) to specify cT , c pT ;
12.14.17. ROCKT 987

pref reference pressure for (x, y, z) (PRPOR) (default the pressure in the first
active grid block).
Tre f reference temperature TEMR (see 13.5.11).
Example
TABDIMS
1 2 2* 1
/
...
ROCKT
0.01 4.0E-0005 6.6E-06 1. 850. 0.1
/
0.012 4.0E-0005 13.5E-06 1. 850. 0.1
/
12.14.17. ROCKT 988

12.14.18 THCONT


Section
The keyword sets the rock thermal conductivity and the phase thermal conductivities. The
value is constant in each rock region. (The keyword ROCKNUM (see 12.4.14) specifies for
every grid block the number of rock region - transmissibility dependence on pressure table -
to which it belongs).
The parameters of this keyword are used in the calculations of thermal conductivity of
the grid block 4.28.
The same number of values should be specified as the number of rock regions (the second
parameter of the keyword ROCKCOMP (see 12.1.34)). The data for each region should be
The keyword has an Eclipse compatible analogues THCONR (see 12.14.15), THCONSF
(see 12.14.16).
The following parameters are to be specified (for each rock region):
1. rock thermal conductivity (METRIC: kJ/m/day/C , FIELD: Btu/ f t/day/F );
2. water thermal conductivity (METRIC: kJ/m/day/C , FIELD: Btu/ f t/day/F ) (isnt

used in case if there is no water phase: two phase model oil-gas);
3. oil thermal conductivity (METRIC: kJ/m/day/C , FIELD: Btu/ f t/day/F ) (isnt used
in case if there is no oil phase: two phase model water-gas);
4. gas thermal conductivity (METRIC: kJ/m/day/C , FIELD: Btu/ f t/day/F ) (isnt used
in case if there is no gas phase: two phase model oil-water);
5. solid phase thermal conductivity (METRIC: kJ/m/day/C , FIELD: Btu/ f t/day/F )

(isnt used in case if there is no solid phase).
Default:
parameters 1-4 non specified,
solid phase thermal conductivity is equal to the rock thermal conductivity (the first
parameter of this keyword).
12.14.18. THCONT 989

Example
ROCKCOMP
IRREVERS 2 /
...
THCONT
160 54 10 250 /
160 54 10 /
/
In this example there are 2 rock regions. First region: rock thermal conductivity - 160,
water thermal conductivity - 54, oil thermal conductivity - 10, gas thermal conductivity - 250.
Second region: rock thermal conductivity - 160, water thermal conductivity - 54, oil
thermal conductivity - 10.
12.14.18. THCONT 990

12.14.19 THCONMIX


Section
The keyword sets the method of block thermal conductivity calculation for each rock-
region. Data for each region is set in separate line. Two methods are possible:
SIMPLE
COMPLEX
In stars data format thermal conductivity of the grid block is specified using the
keyword THCONMIX (see 13.4.13) option SIMPLE

Kb = 1 SbS (kW SW + kO SO + kG SG ) + kS SbS + (1 ) kR
where

(see 13.4.12) = THCONR (see 13.4.8));
porosity.
In stars data format isothermal part of the block thermal conductivity specified using
the keyword THCONMIX (see 13.4.13) option COMPLEX

0
p kR p kR
kG kL
where
kW SW + KO SO
SW + SO
where
f mobile porosity.
12.14.19. THCONMIX 991

Kb = Kb0 1.7524 105(T Tre f ) (Kb0 119616)

0
0.64 0 3
(3.6784106 Kb0 )
Kb Kb 1.8 10 T + 110644.8

Kb = (1 SG ) kR
where
SG gas saturation.
Example
THCONMIX
SIMPLE /
/
12.14.19. THCONMIX 992

12.14.20 STHERMX1


Section
The keyword sets the thermal expansion coefficient for each component (METRIC: 1/ K,
FIELD: 1/ R) in the solid phase.
The same number of values as the number of components should be specified (COMPS
Default: 0.
In stars component k solid density at pressure p and temperature T is

k = k,re f exp ck,p (p pre f ) ck,T (T Tre f ) + ck,pT (p pre f )(T Tre f )
where
13.5.22)):
gator uses this keyword STHERMX1),
this parameter tNavigator uses this keyword STHERMX2 (see 12.14.21))
In e300 component k solid density at pressure p and temperature T is

k = k,re f / (1 ck,p (p pk,re f ))(1 + ck,T (T Tk,re f ))
where
12.14.20. STHERMX1 993


(SDREF (see 12.14.22))
5. ck,T thermal expansion coefficient for component k (is specified using this keyword
STHERMX1)
Example
STHERMX1
0.0000024 0.0000033 2*
/
This example sets the thermal expansion coefficient for 4 components in the solid phase:
1-st component 0.0000024, 2-nd 0.0000033, 3-rd and 4-th components have the default
value 0.
12.14.20. STHERMX1 994

12.14.21 STHERMX2


Section
The keyword sets the coefficient of density dependence on temperature and pressure for
each component in the solid phase (METRIC: 1/(kPa K), FIELD: 1/psi R).
Default: 0.
In stars component k solid density at pressure p and temperature T is

k = k,re f exp ck,p (p pre f ) ck,T (T Tre f ) + ck,pT (p pre f )(T Tre f )
where
13.5.22)):
gator uses the keyword STHERMX1 (see 12.14.20)),
this parameter tNavigator uses this keyword STHERMX2)

where
12.14.21. STHERMX2 995


(SDREF (see 12.14.22))
5. ck,T thermal expansion coefficient for component k (is specified using the keyword
STHERMX1 (see 12.14.20))
Example
STHERMX2
0.0000011 0.0000017 2*
/
This example sets the coefficient of density dependence on temperature and pressure for
4 components in the solid phase: 1-st component 0.0000011, 2-nd 0.0000017, 3-rd and
4-th components have the default value 0.
12.14.21. STHERMX2 996

12.14.22 SDREF


Section
The keyword sets the density for each component in the solid phase at reference pressure
and reference temperature (METRIC: kg/m3 , FIELD: lb/ f t 3 ).

where

(SDREF)
5. ck,T thermal expansion coefficient for component k (STHERMX1 (see 12.14.20))
Example
SDREF
35.2 48.13
/
This example sets density for two components in the solid phase at reference pressure
and reference temperature: 1-st component has the density 35.2, 2-nd component 48.13.
12.14.22. SDREF 997

12.14.23 SPREF


Section
The keyword sets the reference pressure for each component in the solid phase (METRIC:
bars, FIELD: psi).

where
1. pk,re f reference pressure for component k (SPREF)

(SDREF (see 12.14.22))
Example
SPREF
120 125
/
This example sets the reference pressure for two components: for 1-st component 120,
for 2-nd component 125.
12.14.23. SPREF 998

12.14.24 SCREF


Section
The keyword sets the component compressibility for each component in the solid phase
(METRIC: 1/bars, FIELD: 1/psi).

where

(SDREF (see 12.14.22))
4. ck,p component k compressibility (SCREF)
Example
SCREF
0.000045 0.000053
/
This example sets the component compressibility for two components: for 1-st component
0.000045, for 2-nd component 0.000053.
12.14.24. SCREF 999

12.14.25 STREF


Section
The keyword sets the reference temperature for each component in the solid phase (MET-
RIC: K, FIELD: R).

where
2. Tk,re f reference temperature for component k (STREF)

(SDREF (see 12.14.22))
Example
STREF
320 380 280
/
This example sets the reference temperature for free components.
12.14.25. STREF 1000

12.14.26 THERMEX1


Section
The keyword sets the first thermal expansion coefficient for each component in the liquid
phase (METRIC: 1/ K , FIELD: 1/ R. The same number of values as the number of com-
ponents should be specified (COMPS (see 12.13.3)). The data should be terminated with a
slash /.
Default: 0.
In stars component k liquid density at pressure p and temperature T is

2 2
k = k,re f exp ck,p (p pre f ) ck,1,T (T Tre f ) ck,2,T (T Tre f )/2 + ck,pT (p pre f )(T Tre f )
where

ck,p (CP (see 13.5.16)) component k compressibility k ,

ck,1,T (CT1 (see 13.5.17)) the first thermal expansion coefficient for component
k (for this parameter tNavigator uses this keyword THERMEX1 (see 12.14.26)),
ck,2,T (CT2 (see 13.5.18)) the second thermal expansion coefficient for
component k (for this parameter tNavigator uses the keyword THERMEX2
(see 12.14.27)); total thermal expansion coefficient is equal to ck,1,T + T ck,2,T ,
ck,pT (CPT (see 13.5.19)) the coefficient of density dependence on temper-
ature and pressure (for this parameter tNavigator uses the keyword THERMEX3
(see 12.14.28))
12.14.26. THERMEX1 1001

In e300 component k liquid density at pressure p and temperature T is

where

(see 12.14.34))
Example
THERMEX1
0.0000024 0.0000033 2*
/
This example sets the first thermal expansion coefficient for four components in the liquid
phase: for 1-st component 0.0000024, for 2-nd component 0.0000033, for 3-rd and 4-th
components the default value 0.
12.14.26. THERMEX1 1002

12.14.27 THERMEX2


Section
The keyword sets the second thermal expansion coefficient for each component in the
liquid phase (METRIC: 1/C2 , FIELD: 1/ F 2 . The same number of values as the number
of components should be specified (COMPS (see 12.13.3)). The data should be terminated
with a slash /.
Default: 0.

2 2
where


(see 12.14.28))
12.14.27. THERMEX2 1003


where

(see 12.14.34))
Example
THERMEX2
0.00000024 0.00000033 2*
/
This example sets the second thermal expansion coefficient for four components in the
liquid phase: for 1-st component 0.00000024, for 2-nd component 0.00000033, for 3-rd
and 4-th components the default value 0.
12.14.27. THERMEX2 1004

12.14.28 THERMEX3


Section
The keyword sets the coefficient of density dependence on temperature and pressure for
each component in the liquid phase (METRIC: 1/(kPa C), FIELD: 1/psi F ). The same
number of values as the number of components should be specified (COMPS (see 12.13.3)).
Default: 0.

2 2
where


(see 12.14.28))
12.14.28. THERMEX3 1005


where

(see 12.14.34))
Example
THERMEX3
0.0000024 0.0000033 2*
/
four components in the liquid phase: for 1-st component 0.0000024, for 2-nd component
0.0000033, for 3-rd and 4-th components the default value 0.
12.14.28. THERMEX3 1006

12.14.29 PREF


Section
The keyword sets the reference pressure for each component in the liquid phase (MET-
RIC: bars, FIELD: psi). The same number of values as the number of components should
be specified (COMPS (see 12.13.3)). The data should be terminated with a slash /.
Component k liquid density at pressure p and temperature T is

where
1. pk,re f reference pressure for component k (PREF)

(see 12.14.34))
Example
PREF
120 105
/
This example sets the reference pressure for two components in the liquid phase: for 1-st
component 120, for 2-nd component 105.
12.14.29. PREF 1007

12.14.30 PREFT


Section
This keyword is an alias for the keyword PREF (see 12.14.29).
12.14.30. PREFT 1008

12.14.31 CREF


Section
The keyword sets the compressibility for each component in the liquid phase (METRIC:
1/bars, FIELD: 1/psi). The same number of values as the number of components should be
specified (COMPS (see 12.13.3)). The data should be terminated with a slash /.

where

(see 12.14.34))
4. ck,p component k compressibility (CREF),
Example
CREF
0.0000049 0.0000055
/
This example sets the compressibility for two components in the liquid phase: for 1-st
component 0.0000049, for 2-nd component 0.0000055.
12.14.31. CREF 1009

12.14.32 TREF


Section
The keyword sets the reference temperature for each component in the liquid phase (MET-
RIC: K, FIELD: R). The same number of values as the number of components should be
specified (COMPS (see 12.13.3)). The data should be terminated with a slash /.

where
2. Tk,re f reference temperature for component k (TREF)

(see 12.14.34))
Example
TREF
120 180 200
/
This example sets the reference temperature for 3 components in the liquid phase.
12.14.32. TREF 1010

12.14.33 TREFT


Section
This keyword is analogue of the keyword TREF (see 12.14.32).
12.14.33. TREFT 1011

12.14.34 DREF


Section
The keyword sets the density at reference pressure and reference temperature for each
component in the liquid phase (METRIC: kg/m3 , FIELD: lb/ f t 3 ). The same number of
values as the number of components should be specified (COMPS (see 12.13.3)). The data

where
3. k,re f density of component k at reference pressure and reference temperature (DREF)
Example
DREF
49.2 39.3 37.4
/
This example sets the density of three components at reference pressure and reference
temperature.
12.14.34. DREF 1012

12.14.35 DREFT


Section
This keyword is analogue of the keyword DREF (see 12.14.34).
12.14.35. DREFT 1013

12.14.36 ZFACTOR


Section

The keyword sets the coefficients Zk,0 for each component in the formula below. (The coef-
ficients Zk,1 are set via the keyword ZFACT1 (see 12.14.37).) The same number of values as
the number of components N should be specified (COMPS (see 12.13.3)). The data should
In e300 data format the molar and the gas mass density are calculated
n0c
, !
MWw Zk,0 RT
w k=2 p
n0c
, !
xw,G xk,G Zk,0 RT
G = 1 + Zk,1
w k=2 MWk p
!
5
j Tb
w = exp C j TbK
j=0 T
Tb = a (p/10)b , a = 180.89 b = 0.2350

C0 = 93.7072 C1 = 0.833941 C2 = 0.003208
C3 = 6.57652 106 C4 = 6.93747 109 C5 = 2.97203 1012
The coefficients Zk,0 , Zk,1 are specified using the keywords ZFACTOR, ZFACT1 (see
12.14.37).
n0c
p
G = , G = G xk,G MWk
ZRT k=1
12.14.36. ZFACTOR 1014

pri pri p T
Ai = 0.4274802 , Bi = 0.08664035 , A jk = (A j Ak )0.5 , pri = , Tri = ,
Tri2.5 Tri pci Tci
n0c n0c n0c
A= x j,Gxk,GA jk , B= x j,GB j
j=1 k=1 j=1
Z 3 Z 2 + (A B2 B)Z AB = 0
Z [0.3, 1.2].
Example
ZFACTOR
5*0.96
/
This example sets the coefficients Zk,0 of five components equal to 0.96.
12.14.36. ZFACTOR 1015

12.14.37 ZFACT1


Section

The keyword sets the coefficients Zk,1 for each component in the formula below. (The co-
efficients Zk,0 are set via the keyword ZFACTOR (see 12.14.36).) The same number of
values as the number of components N should be specified (COMPS (see 12.13.3)). The
In e300 data format the molar and the gas mass density are calculated
n0c
, !
MWw Zk,0 RT
w k=2 p
n0c
, !
xw,G xk,G Zk,0 RT
G = 1 + Zk,1
w k=2 MWk p
!
5
j Tb
w = exp C j TbK
j=0 T
Tb = a (p/10)b , a = 180.89 b = 0.2350

C0 = 93.7072 C1 = 0.833941 C2 = 0.003208
C3 = 6.57652 106 C4 = 6.93747 109 C5 = 2.97203 1012
The coefficients Zk,0 , Zk,1 are specified using the keywords ZFACTOR (see 12.14.36),
ZFACT1.
n0c
p
G = , G = G xk,G MWk
ZRT k=1
12.14.37. ZFACT1 1016

pri pri p T
Ai = 0.4274802 , Bi = 0.08664035 , A jk = (A j Ak )0.5 , pri = , Tri = ,
Tri2.5 Tri pci Tci
n0c n0c n0c
A= x j,Gxk,GA jk , B= x j,GB j
j=1 k=1 j=1
Z 3 Z 2 + (A B2 B)Z AB = 0
Z [0.3, 1.2].
Example
ZFACT1
5*0.15
/
This example sets the coefficients Zk,1 of five components equal to 0.15.
12.14.37. ZFACT1 1017

12.14.38 VISCREF


Section
This keyword can be used if THERMAL (see 12.1.50) is present or if temperature option
is enable (2.30).
The keyword sets reference pressure and dissolved gas concentration for each PVT region.
In e300 data format the keyword should be present if oil or water viscosity depends on
pressure.
For each PVT region the following parameters should be entered:
1. reference pressure (METRIC: barsa, FIELD: psia);
2. reference Rs dissolved gas concentration (METRIC: sm3 /sm3 , FIELD: Msc f /stb)
(DISGAS (see 12.1.56));
3. IGNORED, this is an Eclipse compatibility field
The data for each PVT region should be terminated with a slash /.
Example
VISCREF
207 1.27 /
In this example reference pressure and dissolved gas concentration are specified for 1
PVT region.
12.14.38. VISCREF 1018

12.14.39 WATVISCT


Section
This keyword can be used if THERMAL (see 12.1.50) is present or temperature option is
enable (2.30).
The keyword sets the table of water viscosity as a function of temperature for each PVT
region (The number of PVT regions is equal to the second parameter of TABDIMS (see
12.1.26)).
For each PVT region the table should be terminated with a slash /. Each row of the table
consists of two parameters:
1. temperature (METRIC: C, FIELD: F) (values should increase down the column);
2. water viscosity at this temperature W (T )(cP).
Viscosity in this keyword is specified are reference pressure. Viscosity dependence on

pressure can be specified:
W0 (p)
W (p, T ) = W (T ) 0
W (pre f )
W (T ) water viscosity (depends on temperature);

W
Example
WATVISCT
10 1
60 0.8
130 0.45
210 0.1
350 0.08
/
This example sets the table of water viscosity as a function of temperature for one PVT
region.
12.14.39. WATVISCT 1019

12.14.40 OILVISCT


Section
This keyword can be used if THERMAL (see 12.1.50) is present or if the temperature
option is enable (2.30).
Temperature option for models e100.
The keyword sets the table of oil viscosity as a function of temperature for each PVT
region (The number of PVT regions is equal to the second parameter of TABDIMS (see
12.1.26)). For each PVT region the table should be terminated with a slash /.
Each row of the table consists of parameters:
temperature (METRIC: C, FIELD: F) (values should increase down the column);
oil viscosity at this temperature (cP).
Oil viscosity at the prevailing pressure and Rs is calculated the following way
p (p, Rs )
O = T (T )
p (pre f , Rsre f )
where
T viscosity from this keyword (assumed to be at the reference pressure and Rs ,

specified via VISCREF (see 12.14.38));
p viscosity from PVCO (see 12.5.6) (or PVDO (see 12.5.2));
pre f reference pressure, specified via VISCREF (see 12.14.38);
Rsre f reference Rs , specified via VISCREF (see 12.14.38).
Example
OILVISCT
75 3.0
128 0.58
/
In this example there is a table for one PVT region.
12.14.40. OILVISCT 1020

Thermal simulation for models e300.
The keyword sets the table of oil component viscosity as a function of temperature for
each PVT region (The number of PVT regions is equal to the second parameter of TABDIMS
(see 12.1.26)).
consists of parameters:
temperature;
N values of oil component viscosities (cP) for this temperature k,O (T ) (N the
number of components COMPS (see 12.13.3)).
n0c
O (T ) = (k,O ) fk (xk,O )
k=2
the tables of this keyword OILVISCT (in e300 data format), VISCTABLE (see 13.5.53)
(stars), or using correlation (OILVISCC (see 12.14.41)).
(stars).
O0 (p)
O (p, T ) = O (T )
O0 (pre f )
where
Example
OILVISCT
60 2500 4700
100 950 1200
130 115 161
250 14 17
370 3.3 3.9
500 1.8 2.1
/
This example specifies the table of oil component viscosity as a function of temperature
for one PVT region.
12.14.40. OILVISCT 1021

12.14.41 OILVISCC


Section

The keyword sets the table of coefficients for correlation formula (oil viscosity as a function
of temperature).
n0c
O (T ) = (k,O ) fk (xk,O )
k=2
the tables of the keyword OILVISCT (see 12.14.40) (in e300 data format), VISCTABLE (see
13.5.53) (stars), or using correlation (this keyword OILVISCC).
(stars).
In e300 data format the following correlations can be used to calculate k,O (specified
using this keyword OILVISCC):
Name Formula Name Formula

ASTM log10 (k,O + Ak ) = Bk T Ck Vogel log10 (k,O ) = Ak + Bk /(T +Ck )
Andrade log10 (k,O ) = Ak + Bk /T logarithmic log10 (k,O ) = Ak + Bk log10 (T )
In stars data format Andrade correlation is used with parameters Ak = log10 A0k , Bk =
B0k log10 e, where A0k , B0k are specified using keywords AVISC (see 13.5.51), BVISC (see
13.5.52).
The coefficients of correlation formula should be entered as several rows. First row con-
sists of the name of correlation formula. Other rows contain the coefficients A, B, C. The
ASTM:
1. ASTM FORMULA
2. coefficient A (N (COMPS (see 12.13.3)) values: each value for one component);
A<1
12.14.41. OILVISCC 1022

3. coefficient B (N (COMPS (see 12.13.3)) values: each value for one component);
B>0
4. coefficient C (N (COMPS (see 12.13.3)) values: each value for one component);
C>0
Andrade:
1. ANDRADE FORMULA
Vogel:
1. VOGEL FORMULA
4. coefficient C (N (COMPS (see 12.13.3)) values: each value for one component);
Logarithmic:
1. LOG FORMULA
Example
OILVISCC
ASTM FORMULA
0.4 0.5 0.6
12 18 20
11 21 24
/
This example sets the coefficients for ASTM correlation formula for one EoS region.
12.14.41. OILVISCC 1023

12.14.42 OILVINDX


Section

The keyword sets the table of functions fk (x) (indices in oil viscosity formula below) for
(see 12.1.26)).
mole fraction value x (the number between 0 and 1);
N values of fk (x) (N the number of components COMPS (see 12.13.3)).
fk (0) = 0, fk (1) = 1.
n0c
O (T ) = (k,O ) fk (xk,O )
k=2
fk (x) (default: fk (x) = x ) are specified using this keyword OILVINDX (in e300 data format)
(stars).
tNavigator also uses the keyword OILVINDT (see 12.14.43).
O0 (p)
O (p, T ) = O (T ) 0
O (pre f )
where
12.14.42. OILVINDX 1024

Example
OILVINDX
0 0 0
0.1 0.01 0.02
0.2 0.03 0.04
0.3 0.07 0.08
0.4 0.09 0.12
0.5 0.18 0.22
0.6 0.28 0.39
0.7 0.50 0.51
0.8 0.73 0.67
0.9 0.82 0.89
1 1 1
/
This example specifies the table of functions fk (x) for one PVT region.
12.14.42. OILVINDX 1025

12.14.43 OILVINDT


Section

The keyword sets the table of functions fk (x) (indices in oil viscosity formula below) for
(see 12.1.26)).
For each PVT region the following table should be specified.
x1,1 f1 (x1,1 )
... ...
x1,11 f1 (x1,11 )
/
x2,1 f2 (x2,1 )
... ...
x2,11 f2 (x2,11 )
/
... ...
/
xN,1 fN (xN,1 )
... ...
xN,11 fN (xN,11 )
/
This table consists of the following parameters:
mole fraction value xi, j (the number between 0 and 1), 0 xi,1 xi,2 . . . xi,11 1;
values of fk (x), 1 k N (N the number of components COMPS (see 12.13.3)).
fk (0) = 0, fk (1) = 1.
If the are more than one PVT region, the tables for all regions should be specified one
after another in this keyword.

n0c
O (T ) = (k,O ) fk (xk,O )
k=2
12.14.43. OILVINDT 1026

fk (x) (default: fk (x) = x ) are specified using the keyword OILVINDX (see 12.14.42) (in
e300 data format) or VSMIXCOMP (see 13.5.54), VSMIXENDP (see 13.5.55), VSMIXFUNC
(see 13.5.56) (stars).
tNavigator also uses the keyword OILVINDT (see 12.14.43).
O0 (p)
O (p, T ) = O (T )
O0 (pre f )
where
12.14.43. OILVINDT 1027

Example
COMPS
2 /
...
OILVINDT
0 0 0
0.1 0.01
0.2 0.03
0.3 0.07
0.4 0.09
0.5 0.18
0.6 0.28
0.7 0.50
0.8 0.73
0.9 0.82
1 1 1
/
0 0 0
0.1 0.02
0.2 0.04
0.3 0.09
0.4 0.19
0.5 0.32
0.6 0.44
0.7 0.60
0.8 0.79
0.9 0.89
1 1 1
/
This example specifies the table of functions fk (x) for two components and one PVT
region.
12.14.43. OILVINDT 1028

12.14.44 GASVISCT


Section

The keyword sets the table of gas component viscosity as a function of temperature for each
PVT region (The number of PVT regions is equal to the second parameter of TABDIMS (see
12.1.26)).
temperature (METRIC: C, FIELD: F);
N values of gas component viscosities (cP) for this temperature k,G (T ) (N the
number of components COMPS (see 12.13.3)).
n0c
G (p, T ) = xk,G k,G
k=1

Ag = 4.9402 103 , Bg = 5.0956 105 , Cg = 2.9223 106 , Dg = 2.5077
of temperature using the tables of this keyword GASVISCT, or using the correlation formula
with the coefficients GASVISCF (see 12.14.45):
k,G (T ) = Ak T Bk

n0c n0c
!, !
p p
G (T ) = k,G xk,G MWk xk,G MWk
k=1 k=1
component viscosities are set via correlation (4.35) with the coefficients AVG (see 13.5.57),
BVG (see 13.5.58). If gas viscosity isnt specified by user then in stars data format it is
calculated as
G (T ) = 0.0136 + 3.8 105 TC , TC = T 273.15
12.14.44. GASVISCT 1029

Example
GASVISCT
60 0.0122 0.017
100 0.0132 0.027
130 0.0150 0.027
250 0.0191 0.030
370 0.0210 0.033
500 0.0310 0.039
/
This example specifies the table of gas component viscosity as a function of temperature
for one PVT region.
12.14.44. GASVISCT 1030

12.14.45 GASVISCF


Section

The keyword sets the table of coefficients for correlation formula (gas component viscosity
as a function of temperature).
The rows of table for one EoS region contains the following parameters:
coefficient A (N (COMPS (see 12.13.3)) values: each value for one component);
coefficient B (N (COMPS (see 12.13.3)) values: each value for one component);
n0c
G (p, T ) = xk,G k,G
k=1
Ag = 4.9402 103 , Bg = 5.0956 105 , Cg = 2.9223 106 , Dg = 2.5077
of temperature using the tables of this keyword GASVISCT, or using the correlation formula
with the coefficients GASVISCF (see 12.14.45):
k,G (T ) = Ak T Bk
n0c n0c
!, !
p p
G (T ) = k,G xk,G MWk xk,G MWk
k=1 k=1
component viscosities are set via correlation with the coefficients AVG (see 13.5.57), BVG
(see 13.5.58). If gas viscosity isnt specified by user then in stars data format it is calculated
as
G (T ) = 0.0136 + 3.8 105 TC , TC = T 273.15
12.14.45. GASVISCF 1031

Example
GASVISCF
0.00022 0.00017
0.8 0.7
/
This example sets the coefficients for correlation formula for one EoS region.
12.14.45. GASVISCF 1032

12.14.46 REACRATE


Section
The keyword sets the rate of chemical reactions (the rate is constant for each reac-
tion). The same number of values as the number of chemical reactions nr (REACTION (see
12.1.51)) should be specified. The data should be terminated with a slash /.
Default: 0.
stars;
stars;
Ar reaction rate of the reaction number r , are specified using REACRATE in e300;
FREQFAC (see 13.5.34) in stars;

is
nc
0
Rr = Vb Ar eEr /(RT ) (c0ri )nri
i=1
12.14.46. REACRATE 1033

kJ
K kg mol

1 SbS O SO xiO if the reactant i is in the oil phase

1 SbS G SG xiG if the reactant i is in the gas phase

cri = 1 SS W SW xiW if the reactant i is in the water phase
b


N
(
c0ri =

Tu if T > Tu pu if p > pu (
if c0ri > Cri

0 0 nri
T = Tl if T < Tl p = pl if p < pl n0ri =
1 else
T else p else

where

data format),

( p0 = p)).
Example
REACTION
9 /
...
REACRATE
1.024E+013 1.0348E+007 3.35619E+010 1* 1.024E+013
2.48832E+010 100 1.37865 1E+014 /
This example sets the reaction rate for nine chemical reactions, the fourth reaction has
default zero rate. 9 reactions are specified using the keyword REACTION (see 12.1.51).
12.14.46. REACRATE 1034

12.14.47 REACACT


Section
The keyword sets the activation energy in chemical reaction rates (kJ/kg-M); the acti-
vation energy is constant for each reaction. The same number of values as the number of
chemical reactions nr (REACTION (see 12.1.51)) should be specified. The data should be
Default: 0.
stars;
stars;

specified using REACACT in e300; EACT (see 13.5.36) in stars;
is
nc
Er /(RT 0 )
Rr = Vb Ar e (c0ri )nri
i=1
12.14.47. REACACT 1035

kJ
K kg mol



b


N
(
c0ri =

if c0ri > Cri

0 0 nri
1 else
T else p else

where

data format),

( p0 = p)).
Example
REACTION
8 /
...
REACACT
138629 45942.9 87719.8 1* 138629 85645.1 36573.3 21700 /
This example sets the activation energy in reaction rate for eight chemical reactions, the
fourth reaction has default zero activation energy. 8 reactions are specified using the keyword
REACTION (see 12.1.51).
12.14.47. REACACT 1036

12.14.48 REACCORD


Section
The keyword sets the order of component terms in chemical reaction rates (this parameter
can possess different values for the same reactant and different reactions).
The same number of rows as the number of chemical reactions nr (REACTION (see 12.1.51))
should be specified. Each row should be terminated with a slash /. Each row contains the
same number of values as the number of components N (COMPS (see 12.13.3)).
If this order is 0, then the rate of this reaction is independent from the concentration
of this reactant. If this order is positive number - this reactant is catalyst (1 there is
linear dependence between the reaction rate and the concentration, 2 quadratic dependence,
etc.). If this order is negative number - this reactant is inhibitor (-1 inversely proportional
dependence, etc.).
Default: 0.

stars;
stars;
reactants can be > 0 (for catalyst), < 0 (for inhibitor)), are specified using REAC-
CORD, REACSORD (see 12.14.55) in e300; RORDER (see 13.5.39) in stars.
is
nc
Er /(RT 0 )
i=1
12.14.48. REACCORD 1037

kJ
K kg mol



b


N
(
c0ri =

if c0ri > Cri

0 0 nri
1 else
T else p else

where

data format),

( p0 = p)).
Example
REACTION
2 /
COMPS
6 /
...
REACCORD
0 0 1 1 0 0 /
1 0 0 0 -1 0 /
12.14.48. REACCORD 1038

In this example two chemical reactions are specified using the keyword REACTION
(see 12.1.51) and 6 components using the keyword COMPS (see 12.13.3). The rate of
first reaction depends (linearly) of the concentration of 3-rd and 4-th components. The rate
of second reaction depends (linearly) of the concentration of 1-st component and depends
(inversely) of the concentration of 5-th component.
12.14.48. REACCORD 1039

12.14.49 REACLIMS


Section
The keyword sets the maximum and minimum temperature and pressure for each chemi-
cal reaction, which is used in the reaction rate calculations.
The same number of lines as the number of chemical reactions nr (REACTION (see
12.1.51)) should be specified. Each line should be terminated with a slash /.
Default: are not specified.
One line consists of the following parameters:

1. minimum pressure pl (METRIC: barsa, FIELD: psia). If the pressure in the grid
block is below this minimum value pl , then pl is used in the reaction rate calculations
(according the formula below);
2. maximum pressure pu (METRIC: barsa, FIELD: psia). If the pressure in the grid
block is above this maximum value pu , then pu is used in the reaction rate calculations
3. minimum temperature Tl (METRIC: C, FIELD: F). If the temperature in the grid
block is below this minimum value Tl , then Tl is used in the reaction rate calculations
4. maximum temperature Tu (METRIC: C, FIELD: F). If the temperature in the grid
block is above this maximum value Tu , then Tu is used in the reaction rate calculations
(according the formula below).

stars;
stars;
12.14.49. REACLIMS 1040


is
nc
Er /(RT 0 )
i=1
kJ
K kg mol



cri = 1 SbS W SW xiW if the reactant i is in the water phase


N
(
c0ri =

T u if T > Tu pu if p > pu (
if c0ri > Cri

0

0 nri
1 else
T else p else

where

data format),

( p0 = p)).
12.14.49. REACLIMS 1041

Example
REACTION
2 /
...
REACLIMS
20 75 120 320 /
30 80 100 220 /
In this example two chemical reactions are specified using the keyword REACTION (see
12.1.51). The maximum and minimum temperature and pressure are specified.
12.14.49. REACLIMS 1042

12.14.50 REACCONC


Section
The keyword sets the critical value of reactant concentration (this (METRIC: barsa,
FIELD: psi, if the pressure is used or METRIC: kg mole/m3 , FIELD: lb mole/ f t 3 ,
if the concentration is used). If the concentration of reactant is below this value, then the
reaction rate depends linearly of this concentration (according the formula below).
The same number of rows as the number of chemical reactions nr (REACTION (see 12.1.51))
should be specified. Each row should be terminated with a slash /. Each row contains the
same number of values as the number of components N (COMPS (see 12.13.3)).
Default: 0.
stars;
stars;

is
nc
0
Rr = Vb Ar eEr /(RT ) (c0ri )nri
i=1
12.14.50. REACCONC 1043

kJ
K kg mol

1 SS O SO xiO if the reactant i is in the oil phase

b


cri = 1 SbS W SW xiW if the reactant i is in the water phase


N
(
c0ri = 0
p xi,G else (for gas)

if c0ri > Cri

0 0 nri
1 else
T else p else

where
data format),
( p0 = p)).
Example
REACTION
2 /
COMPS
6 /
...
REACCONC
0.00025 /
0.00011 0.00037 /
In this example two chemical reactions are specified using the keyword REACTION (see
12.1.51) and 6 components using the keyword COMPS (see 12.13.3). For first reaction
the critical value of concentration is specified for first reactant; for second reaction for first
and second reactants. Other critical values have default zero values.
12.14.50. REACCONC 1044

12.14.51 REACPORD


Section
The keyword sets the order of pore volume in chemical reaction rates nr,p (formula
4.71). The same values should be specified as the number of chemical reactions. The data
Chemical reaction rate could be independent of pore volume (nr,p = 0).
Example
REACTION
3 /
REACPORD
0 0 1 /
In this example three chemical reactions are specified using the keyword REACTION
(see 12.1.51). Chemical reaction rate of first and second reactions are independent of pore
volume (nr,p = 0). Chemical reaction rate of third reaction depends of pore volume linearly
(nr,p = 1).
12.14.51. REACPORD 1045

12.14.52 STOPROD


Section
The keyword specifies the stoichiometric coefficients for all products in each chemical
reaction as a line of numbers. The same number of lines as the number of chemical reactions
(nr ) should be entered (REACTION (see 12.1.51)). Each line should be terminated with a
slash /.
Each line should contain N values (number of components entered using COMPS (see
12.13.3)). If the component isnt the product of the reaction one should enter zero or default
value.
Stoichiometric coefficients are specified using this keyword and STOREAC (see
12.14.53).
Default: 0.
Example
REACTION
1 /
COMPS
9 /
...
STOPROD
0 0 0 3 0 0 7 0 0/
STOREAC
2 0 6 0 0 0 0 0 0/
This example sets 1 chemical reaction using the keyword REACTION (see 12.1.51) and
9 components using the keyword COMPS (see 12.13.3).
The products of this reaction are: the 4-th component (with the coefficient 3) and the 7-th
component (with the coefficient 7).
The reactants of this reaction are: the 1-st component (with the coefficient 2) and the 3-rd
2-nd, 5-th, 6-th, 8-th, 9-th components are not present in this reaction.
12.14.52. STOPROD 1046

12.14.53 STOREAC


Section
The keyword specifies the stoichiometric coefficients for all reactants in each chemical
reaction as a line of numbers. The same number of lines as the number of chemical reactions
(nr ) should be entered (REACTION (see 12.1.51)). Each line should be terminated with a
slash /.
Each line should contain N values (number of components entered using COMPS (see
12.13.3)). If the component isnt the reactant of the reaction one should enter zero or default
value.
Stoichiometric coefficients are specified using this keyword and STOPROD (see
12.14.52).
Default: 0.
Example
REACTION
1 /
COMPS
9 /
...
STOPROD
0 0 0 3 0 0 7 0 0/
STOREAC
2 0 6 0 0 0 0 0 0/
9 components using the keyword COMPS (see 12.13.3).
The products of this reaction are: the 4-th component (with the coefficient 3) and the 7-th
The reactants of this reaction are: the 1-st component (with the coefficient 2) and the 3-rd
2-nd, 5-th, 6-th, 8-th, 9-th components are not present in this reaction.
12.14.53. STOREAC 1047

12.14.54 REACPHA


Section
The keyword specifies the component phase in chemical reaction. Each line of phases
corresponds to one chemical reaction. The same number of lines as the number of chemical
reactions (nr ) should be entered (REACTION (see 12.1.51)). Each line should be terminated
with a slash /. Each line should contain N values (number of components entered using
COMPS (see 12.13.3)). If the component isnt the reactant of the reaction one can enter
default value - ALL (component phase is not used in the calculations if the component isnt
reactant).
A phase can be one of the following values:
ALL if all phases of component react,
OIL oil phase reacts,
GAS gas phase reacts,
GPP gas phase reacts and the reaction rate depends on gas gas partial pressure,
WAT water in eater phase reacts,
NONE the reaction rate doesnt depend on the component.
If the component can react in different phases and the reaction rate depends on the phase,
then two reactions should be specified (with the same stoichiometric coefficients STOREAC
(see 12.14.53) and different REACPHA).
Default: ALL. If the component has zero order in REACCORD the component phase will
be ignored.
For the chemical reaction
C3 H8 + 5O2 3CO2 + 4H2 O
there is an example:
12.14.54. REACPHA 1048

Example
REACTION
1 /
COMPS
5 /
...
STOPROD
0 0 0 3 4 /
STOREAC
0 1 5 0 0 /
REACPHA
1* OIL GAS 2* /
5 components using the keyword COMPS (see 12.13.3). The reactants of this reaction are:
the 2-nd component (with the coefficient 1) and the 3-rd component (with the coefficient 5).
1-st component isnt present in this reaction. The 2-nd component is in the oil phase, the 3-rd
gas phase. Other phase components are defaulted, because the reaction rate doesnt depend
on them.
12.14.54. REACPHA 1049

12.14.55 REACSORD


Section
The keyword specifies the order of dependence between solid saturation and chemical
reaction rate. The same number of values as the number of chemical reactions (nr ) should
be entered (REACTION (see 12.1.51)).
The chemical reaction rate is proportionate to the multiplier:
(1 SS )ns
where ns order, SS solid saturation.
In there is a solid phase in the model then the equation 2.4 is replaced by the equation
SO + SG + SW + SS = 1
Oil, gas and water saturation are:
SO SG SW
SO = , SG = , SW =
1 SS 1 SS 1 SS
Example
REACTION
3 /
...
REACSORD
0 1 0 /
12.14.55. REACSORD 1050

12.14.56 REACENTH


Section
The keyword specifies the enthalpy of each chemical reaction (METRIC: kJ/kg mol ,
FIELD: Btu/lb mol ). It can only be used if THERMAL (see 12.1.50) is present. The same
number of values as the number of chemical reactions (nr ) should be entered (REACTION
Default: 0.
Example
REACTION
9 /
...
REACENT
1.27618E+007 806904 4.0646E+006 0 1.91426E+007 5.7428E+006
622136 1.3392E+007 0 /
This example sets 9 chemical reactions using the keyword REACTION (see 12.1.51).
12.14.56. REACENTH 1051

12.14.57 SPECHA


Section

The keyword specifies the first coefficient of the oil component liquid specific heats CP1,c in
the formula below (METRIC: kJ/kg/K , FIELD: Btu/lb/R). The same number of values as
the number of components: N should be entered (COMPS (see 12.13.3)). The data should

1
Hc,O (T ) = CP1,c (T Tre f ) + CP2,c (T Tre f )2
2

where the coefficients CP1,c (kJ/kg/ C ), CP2,c are specified using the keywords SPECHA,
SPECHB (see 12.14.58) (default: 0), Tre f is specified using STCOND (see 12.13.8).
4
1
Hc,O (T ) = CPi,c (T Tre f )i
i=1 i
where the coefficients CPi,c , i = 1, . . . , 4 are specified using the keywords CPL1 / CPL2
/ CPL3 / CPL4 (see 13.5.27). tNavigator also uses the keywords CP3,c = SPECHC
(see 12.14.59), CP4,c = SPECHD (see 12.14.60). Default values: CP1,c = 0.5Btu/lbmol/F =
0.5 1.05506/0.453592 1.8kJ/mol/C = 2.0934kJ/mol/C , the other coefficients: 0, Tre f is
Default: 0.
Example
SPECHA
0.66 0.52 /
This example specifies the first coefficient of the formula of component liquid enthalpy
for two components.
12.14.57. SPECHA 1052

12.14.58 SPECHB


Section

The keyword specifies the second coefficient of the oil component liquid specific heats CP2,c
in the formula below (METRIC: kJ/kg/K/K , FIELD: Btu/lb/R/R). The same number of
values as the number of components: N should be entered (COMPS (see 12.13.3)). The data

1
2

4
1
i=1 i
where the coefficients CPi,c , i = 1, . . . , 4 are specified using the keywords CPL1 / CPL2
/ CPL3 / CPL4 (see 13.5.27). tNavigator also uses the keywords CP3,c = SPECHC
(see 12.14.59), CP4,c = SPECHD (see 12.14.60). Default values: CP1,c = 0.5Btu/lbmol/F =
Default: 0.
Example
SPECHB
0.0066 0.0052 /
This example specifies the second coefficient of the formula of component liquid enthalpy
for two components.
12.14.58. SPECHB 1053

12.14.59 SPECHC


Section

The keyword specifies the third coefficient of the oil component liquid specific heats CP3,c
in the formula below (METRIC: kJ/kg/K/K/K , FIELD: Btu/lb/R/R/R). The same number
of values as the number of components: N should be entered (COMPS (see 12.13.3)). The

1
2
where the coefficients CP1,c (kJ/kg/C ), CP2,c are specified using the keywords SPECHA
(see 12.14.57), SPECHB (see 12.14.58) (default: 0), Tre f is specified using STCOND (see
12.13.8).
4
1
i=1 i
where the coefficients CPi,c , i = 1, . . . , 4 are specified using the keywords CPL1 / CPL2 /
CPL3 / CPL4 (see 13.5.27). tNavigator also uses the keywords CP3,c = SPECHC, CP4,c =
SPECHD (see 12.14.60). Default values: CP1,c = 0.5Btu/lbmol/F = 0.51.05506/0.453592
1.8kJ/mol/C = 2.0934kJ/mol/C , the other coefficients: 0, Tre f is specified using TEMR (see
13.5.11).
Default: 0.
Example
SPECHC
0.00066 0.00052 /
12.14.59. SPECHC 1054

This example specifies the third coefficient of the formula of component liquid enthalpy
for two components.
12.14.59. SPECHC 1055

12.14.60 SPECHD


Section

The keyword specifies the third coefficient of the oil component liquid specific heats CP4,c
in the formula below (METRIC: kJ/kg/K/K/K/K , FIELD: Btu/lb/R/R/R/R). The same
number of values as the number of components: N should be entered (COMPS (see 12.13.3)).

1
2

4
1
i=1 i
where the coefficients CPi,c , i = 1, . . . , 4 are specified using the keywords CPL1 /
CPL2 / CPL3 / CPL4 (see 13.5.27). tNavigator also uses the keywords CP3,c =
SPECHC (see 12.14.59), CP4,c = SPECHD. Default values: CP1,c = 0.5Btu/lbmol/F =
Default: 0.
Example
SPECHD
0.000066 0.000052 /
This example specifies the fourth coefficient of the formula of component liquid enthalpy
for two components.
12.14.60. SPECHD 1056

12.14.61 SPECHG


Section

The keyword specifies the first coefficient of the gas component specific heats CP1,c (MET-
RIC: kJ/kg/K , FIELD: Btu/lb/R) in the formula 4.46. The same number of values as the
number of components: N should be entered (COMPS (see 12.13.3)). The data should be
Default: 0.
Example
SPECHG
0.0066 0.0052 /
This example specifies the first coefficient of the formula of component gas phase en-
thalpy for two components.
12.14.61. SPECHG 1057

12.14.62 SPECHH


Section

The keyword specifies the second coefficient of the gas component specific heats CP2,c
(METRIC: kJ/kg/K/K , FIELD: Btu/lb/R/R) in the formula 4.46. The same number of
Default: 0.
Example
SPECHH
0.00066 0.00052 /
This example specifies the second coefficient of the formula of component gas phase
enthalpy for two components.
12.14.62. SPECHH 1058

12.14.63 SPECHI


Section

The keyword specifies the third coefficient of the gas component specific heats CP3,c (MET-
RIC: kJ/kg/K/K/K , FIELD: Btu/lb/R/R/R) in the formula 4.47. The same number of
Default: 0.
Example
SPECHI
0.000066 0.000052 /
This example specifies the third coefficient of the formula of component gas phase
12.14.63. SPECHI 1059

12.14.64 SPECHJ


Section

The keyword specifies the fourth coefficient of the gas component specific heats CP4,c (MET-
RIC: kJ/kg/K/K/K/K , FIELD: Btu/lb/R/R/R/R) in the formula 4.47. The same number
of values as the number of components: N should be entered (COMPS (see 12.13.3)). The
Default: 0.
Example
SPECHJ
0.0000066 0.0000052 /
This example specifies the fourth coefficient of the formula of component gas phase
12.14.64. SPECHJ 1060

12.14.65 HEATVAPS


Section

The keyword specifies the coefficient hc,G (METRIC: kJ/kg, FIELD: Btu/lb) (heat of
vaporization at temperature STCOND (see 12.13.8)) in the formula 4.46.
The same number of values as the number of components: N should be entered (COMPS
Default: 0.
Example
HEATVAPS
1200 2100 /
This example specifies the coefficient hc,G (heat of vaporization) of the formula of
component gas phase enthalpy for two components.
12.14.65. HEATVAPS 1061

12.14.66 SPECHS


Section

The keyword specifies the first coefficient of the soild phase specific heats CP1,c in the
formula below (METRIC: kJ/kg/K , FIELD: Btu/lb/R). The same number of values as the
number of components: N should be entered (COMPS (see 12.13.3)). The data should be
In e300 data format the component solid phase enthalpy

1
Hc,S (T ) = CP1,c (T Tre f ) + CP2,c (T Tre f )2
2
keywords SPECHS, SPECHT (see 12.14.67) (default: 0), Tre f is specified using the
keyword STCOND (see 12.13.8).
Default: 0.
Example
SPECHS
0.52 0.58 /
This example specifies the first coefficient of the formula of component solid phase
12.14.66. SPECHS 1062

12.14.67 SPECHT


Section

The keyword specifies the second coefficient of the soild phase specific heats CP2,c in the
formula below (METRIC: kJ/kg/K/K , FIELD: Btu/lb/R/R). The same number of values
as the number of components: N should be entered (COMPS (see 12.13.3)). The data should
In e300 data format the component solid phase enthalpy

1
Hc,S (T ) = CP1,c (T Tre f ) + CP2,c (T Tre f )2
2
keywords SPECHS (see 12.14.66), SPECHT (default: 0), Tre f is specified using the
keyword STCOND (see 12.13.8).
Default: 0.
Example
SPECHT
0.0052 0.0058 /
This example specifies the second coefficient of the formula of component solid phase
12.14.67. SPECHT 1063

12.14.68 TEMPVD


Section
The keyword specifies the table of initial temperature distribution versus depth for each
equilibrium region (EQLDIMS (see 12.1.27)). The data should be terminated with a slash /.
Each table row consists of the following parameters:
1. depth (METRIC: m, FIELD: f t ),
2. temperature at this depth (METRIC: C, FIELD: F).
Example
TEMPVD
1200 90
1800 130
2500 180
3600 218
/
In this example temperature values are specified at four depth values.
12.14.68. TEMPVD 1064

12.14.69 ENPTVT


Section
This keyword can be used in thermal models (THERMAL (see 12.1.50), model type
E300) and in temperature option (TEMP (see 12.1.60), model type E100).
This keyword specifies the temperature variation of the saturation table end points for
the saturation table regions. The number of tables can not be greater then the 1-st param-
eter of the keyword TABDIMS (see 12.1.26). Each table should be terminated with a slash /.
The flow of each phase across each grid block is calculated using capillary pressure and
relative permeability curves obtained be linearly scaling the tabulated curves between the end
points (specified via this keyword ENPTVT (see 12.14.69)).
Each row should contain the following parameters:

2. SW L minimal value of water saturation SW ;
3. SWCR maximal (critical) value of water saturation SW (for which krW (SW ) = 0);
4. SWU maximal value of water saturation SW ;
5. SGL minimal value of gas saturation SG ;
6. SGCR maximal (critical) value of gas saturation SG (for which krG (SG ) = 0);
7. SGU maximal value of gas saturation SG ;
8. SOWCR maximal (critical) value SO = 1 SW SGL , for which krOW (SW ) = 0;
9. SOGCR maximal (critical) value SO = 1 SG SW L , for which krOG (SG ) = 0.
Parameters 2-9 should be in the range 0.0 to 1.0.
Example
ENPTVT
120 0.19 0.19 1.0 0.0 0.05 1.0 0.19 0.22
210 0.21 0.21 1.0 0.0 0.05 1.0 0.19 0.22
250 0.23 0.23 1.0 0.0 0.05 1.0 0.19 0.22 /
In this example there are saturation table end points for free different temperatures.
12.14.69. ENPTVT 1065

12.14.70 ENKRVT


Section

The keyword sets the tables of relative permeabilities versus temperature. The table should
be specified for every saturation table region (the number of saturation table regions is set via
the 1-st parameter of TABDIMS (see 12.1.26). Each table should be terminated with a slash /.
2. krW max maximal value of water relative permeability krW (SW );
3. krGmax maximal value of gas relative permeability krG (SG );
4. krOmax maximal value of oil relative permeability (functions krOW (SW ) and
krOG (SG ));
5. krW R water relative permeability at critical oil saturation (krW (1 SOWCR SGL ));
6. krGR gas relative permeability at critical oil saturation (krG (1 SOGCR SW L ));
7. krORG oil relative permeability at critical gas saturation (krOG (SGCR ));
8. krORW oil relative permeability at critical water saturation (krOW (SWCR )).
Example
ENKRVT
120 0.53 1.0 1.0 0.34 1* 0.75
170 0.62 1.0 0.95 0.36 1* 0.75
220 0.71 1.0 0.89 0.38 1* 0.75 /
In this example there are relative permeabilities for free different temperatures.
12.14.70. ENKRVT 1066

12.14.71 ENPCVT


Section

The keyword sets the tables of capillary pressures versus temperature. The table should be
specified for every saturation table region (the number of saturation table regions is set via
the 1-st parameter of TABDIMS (see 12.1.26). Each table should be terminated with a slash /.
2. PCGmax maximum gas capillary pressure PcOG (SG ) (METRIC: bars, FIELD: psi);
3. PCW max maximum water capillary pressure PcOW (SW ) (METRIC: bars, FIELD: psi).
Example
ENPCVT
120 0.79 0.03
220 1.12 0.32 /
In this example there are capillary pressures for two different temperatures.
12.14.71. ENPCVT 1067

12.14.72 ROCKV


Section
The keyword sets rock volume in each grid block (METRIC: m3 , FIELD: BBL ). The
same number of values should be specified as the number of grid blocks is. The data should
Formula of grid block volume is in the section 4.26.
If rock volume and pore volume of a grid block are set to zero, this block is inactive.
Example
ROCKV
120*1500 200*0 2500*14432 /
In this example rock volume of 120 blocks 1500m3 , of 200 blocks 0m3 , of 2500
blocks 14432m3 .
12.14.72. ROCKV 1068

12.14.73 THSVC


Section
This keyword allows to specify coefficients in steam viscosity expression:

D
g = Ag + Bg TC +Cg Pp g ,
where:
TC temperature ( C );
Pp pressure (MPa).
1. Ag ;
2. Bg ;
3. Cg ;
4. Dg .
Default:
Ag = 4.9402 103 ;
Bg = 5.0956 105 ;
Cg = 2.9223 106 ;
Dg = 2.5077.
Example
THSVC
1.5581E-2
3.2211E-5
2.2227E-6
2.0088
/
In the example 4 coefficients for steam viscosity expression are specified.
12.14.73. THSVC 1069

12.14.74 THWVC


Section
This keyword allows to specify coefficients in water viscosity expression:

Aw
w = ,
1 + Bw TF +Cw TF 2
where:
TF temperature ( F ).
1. Aw ;
2. Bw ;
3. Cw .

Default:
Aw = 2.1850;
Bw = 0.04012;
Cw = 5.1547 106 .
Example
THWVC
2.16E-2
3.15
1.21E-3
/
In the example 3 coefficients for water viscosity expression are specified.
12.14.74. THWVC 1070

12.14.75 SPECROCK


Section
The keyword can be used only if temperature option is enable section 2.30.
The keyword specifies the volume specific heat of rock as a function of temperature. The
same number of tables as the number of saturation regions (1-st parameter of TABDIMS (see
12.1.26)) should be entered. Each table should be terminated with a slash /.
2. volume specific heat of rock at this temperature (METRIC: kJ/rm3 . C, FIELD:

btu/r f t 3 . F).
Example
SPECROCK
0 0.8
90 0.8
/
0 0.8
90 0.8
/
In this example there are two tables.
12.14.75. SPECROCK 1071

12.14.76 SPECHEAT


Section
The keyword can be used only if temperature option is enable section 2.30.
The keyword specifies the volume specific heat of oil, gas, water as a function of tem-
perature. The same number of tables as the number of PVT regions (2-nd parameter of
TABDIMS (see 12.1.26)) should be entered. Each table should be terminated with a slash /.
2. volume specific heat of oil at this temperature (METRIC: kJ/kg. C, FIELD:

btu/lbm. F);
3. volume specific heat of water at this temperature (METRIC: kJ/kg. C, FIELD:

btu/lbm. F);
4. volume specific heat of gas at this temperature (METRIC: kJ/kg. C, FIELD:

btu/lbm. F);
Example
SPECHEAT
0 1.7 4.2 1.6
90 1.7 4.2 1.6
/
In this example there is one table.
12.14.76. SPECHEAT 1072

12.14.77 CALVAL


Section
The keyword sets component calorific values. If it is needed to set component calorific
values in each EoS-region, use the keyword CALVALR (see 12.14.78).
1. component calorific values (METRIC: kJ/kg M , FIELD: Btu/lb M ). Nc values

should be specified (i.e. the same value as the number of model components).
Example
CALVAL
1776.0
202.0
5424.6
547.5
2581.1
/
In the example calorific values of 5 components are set.
12.14.77. CALVAL 1073

12.14.78 CALVALR


Section
The keyword sets component calorific values in each EoS-region (see the keyword
EOSNUM (see 12.4.21)). If it is needed to set component calorific values for entire reservoir,
use the keyword CALVAL (see 12.14.77).
For each EoS-region data should be specified in separate line which ends by a symbol
/. The number of data lines should be equal to the number of EoS-regions. In each line the
following parameters should be specified:
1. component calorific values (METRIC: kJ/kg M , FIELD: Btu/lb M ). Nc values

should be specified (i.e. the same value as the number of model components).
Example
CALVALR
1776.0 202.0 5424.6 547.5 2581.1 /
4608.4 640.4 3720.5 7800.5 5803.7 /
In the example calorific values of 5 components in 2 EoS-regions are set.
12.14.78. CALVALR 1074

12.15. Initialization section tNavigator-4.2
12.15 Initialization section

This section describes initial distribution of saturations and pressures.
There are two ways to specify initial conditions:
Initial equilibrium, using keyword EQUIL (see 12.15.2) and (for 3-phase models)
either PBVD (see 12.15.4) or RSVD (see 12.15.3); user has to specify one of these
two keywords unless GOC depth coincides with reference depth in all equilibrium
regions (DGOc = Ddat );
User defined saturations and pressure distribution, using keywords SWAT (see
12.15.10), SGAS (see 12.15.11) (for 3-phase models), PRESSURE (see 12.15.8)
(or PRVD (see 12.15.9)), PBUB (see 12.15.30) or RS (see 12.15.31)(for live oil
models), RV (see 12.15.32) or PDEW (see 12.15.33)(for wet gas models).
The keywords specifying initial pressures and saturations (see Initialization section
(12.15)):
RV (see 12.15.32) initial oil vaporization with wet gas (wet gas);
PDEW (see 12.15.33) initial dew point pressure (wet gas);
RS (see 12.15.31) initial gas solution in oil (live oil);
PBUB (see 12.15.30) initial bubble point pressure (live oil).
There are two keyword groups (1 wet gas, 2 live oil). One should use only one
keyword from one group.
group 1: RV (see 12.15.32), PDEW (see 12.15.33)
group 2: RS (see 12.15.31), PBUB (see 12.15.30)
One can see different keyword combinations in Property section (12.5) (PVT properties,
permeabilities, initial pressures and saturations).
12.15. Initialization section 1075

12.15.1 SOLUTION


Section
The keyword specifies the beginning of data section which contains initial data.
12.15.1. SOLUTION 1076

12.15.2 EQUIL


Section
This keyword specifies for each equilibrium region properties used in initial conditions
computations. The following parameters are to be specified:
1. reference depth, Ddat (METRIC: m, FIELD: f t );
2. pressure on reference depth, Pdat (METRIC: barsa, FIELD: psia);
3. depth of water-oil contact (WOC), DWOc (METRIC: m, FIELD: f t );
4. capillary pressure at water-oil contact, PWOc (METRIC: barsa, FIELD: psia);
5. depth of gas-oil contact (GOC), DGOc (METRIC: m, FIELD: f t );
6. capillary pressure at gas-oil contact, PGOc (METRIC: barsa, FIELD: psia);
7. parameter regulating table RSVD (see 12.15.3) (or PBVD (see 12.15.4)) usage for
initialization calculation. If set to positive integer, the noted table will be used to
calculate oil bubble point pressure (under condition that solution gas oil ratio cant
exceed saturated solution gas oil ratio value for current pressure). If parameter is set
to negative or zero value, tables RSVD (see 12.15.3) and PBVD (see 12.15.4) will be
ignored, in this case for live oil its necessary that GOC corresponds with datum depth:
DGOc = Ddat . For dead oil case (without solution gas) this parameter will be ignored;
8. parameter regulating table RVVD (see 12.15.5) (or PDVD (see 12.15.6)) usage for
initialization calculation. If set to positive integer, the noted table will be used to
calculate gas dew point pressure (under condition that vaporized oil concentration cant
exceed saturated vaporized oil concentration for current pressure). If parameter is set
to negative or zero value, tables RVVD (see 12.15.5) and PDVD (see 12.15.6) will
be ignored, in this case for wet gas its necessary that GOC corresponds with datum
depth: DGOc = Ddat . For dry gas case (without vaporized oil) this parameter will be
ignored;
9. integer defining accuracy of equilibrium calculation; if set to zero, equilibrium will be

calculated for block centers. This solution will be steady-state. Otherwise (value other
than zero) grid blocks will be divided into thin layers (with thickness equal to 1thinnest
reservoir active block, but not less than 0.0011 m) and equilibrium will be calculated
for each one of those layers. Resulting saturations will be calculated as average values.
12.15.2. EQUIL 1077

10. integer defining the type of initialization in the compositional case.

For a gas-water case, the parameter should be equal to 1, which coincides with default
value.
tNavigator supports the following options of this keyword:
1 Single phase state (no gas-oil contact in the region).

2 There is a gas-oil contact in the region, the composition specified by user
is taken as vapor composition at contact. Pressure at datum depth will be set to
retrograde dew point pressure for this gas, oil composition will be calculated as
composition of first condensate drop for this gas near this pressure.
3 There is a gas-oil contact in the region, the composition specified by user is
taken as oil composition at contact. Pressure at datum depth will be set to bubble
point pressure for this oil, gas composition will be calculated as composition of
first gas bubble for this oil near this pressure.
Note.
If parameter 10 for compositional case is set to 2 and 3, then it is supposed that GOC
is equal to reference depth. If this is not correct then reference depth will be modified
and will be set equal to GOC. If gas composition is known (value 2) or oil composition
is known (value 3) at GOC, tNavigator calculates corresponding value of dew point
(or bubble point). If this value is different from pressure at refernce depth (value in
parameter 2) more than = 1, then pressure at refernece depth will be ignored and be
taken equal to dew point (bubble point). However if parameter 11 is set 1, this will
not take place and tNavigator will take user-defined reference pressure as pressure at
reference depth.
11. if this value is 1, and parameter 10 is equal to 2 or 3, the field pressure is not set to the
saturation pressure at the contact and will be equal to user defined pressure at contact
(see details in description of parameter 10).
The number of lines specified is equal to number of equilibrium regions defined in

EQLDIMS (see 12.1.27). Each line must end with slash (/).
Default:
For water-oil capillary pressure default value is zero: PWOc = 0;
For gas-oil capillary pressure default value is zero: PGOc = 0.
integer defining the type of initialization in the compositional case 1.
Notes:
For depths specified the following relation must be fulfilled: DGOc DWOc .
12.15.2. EQUIL 1078

If Ddat is above GOC, pressure Pdat will correspond to gas phase pressure on this
depth; if Ddat is below WOC, it corresponds to water phase, otherwise oil phase.
For 3-phase models, when DGOc = Ddat , oil bubble point pressure on GOC and below
will be taken equal to Pdat , and above to grid block pressure. If DGOc <> Ddat , to
provide data for oil bubble point pressure calculation user should specify either RSVD
(see 12.15.3) or PBVD (see 12.15.4).
For each equilibrium region grid blocks from this region should not have different
numbers of PVT regions (PVTNUM (see 12.4.2)).
Gas-oil contact DGOc may be less then reservoir depth (TOPS (see 12.2.6)), that
means mobile gas phase absence. Gas-oil contact DGOc may be greater then reservoir
bottom depth, that means that only gas is mobile in the model.
Water-oil contact DWOc may be less then reservoir depth (TOPS (see 12.2.6)), that
means that only water is mobile in the model. Water-oil contact DWOc may be greater
then reservoir bottom depth, that means mobile water phase absence.
Example
EQLDIMS
3 /
...
EQUIL
2300 200 2500 0.1 2300 0.001 /
2310 205 2520 0.05 2310 0.0 /
2305 210 2510 1* 2305 1* /
In this example the data for three regions are specified. Default values for capillary
pressures in the third region are zero values. Since GOC coincides with Ddat for all three
regions, theres no need to define RSVD (see 12.15.3) or PBVD (see 12.15.4).
12.15.2. EQUIL 1079

12.15.3 RSVD


Section
This keyword specifies for each equilibrium region initial solution gas ratio distribution,
used in initial conditions computations in case of equilibrium initialization using EQUIL (see
12.15.2). If in a 3-phase live oil model all equilibrium regions have GOC equal to Ddat ,
there is no need to define RSVD (see 12.15.3) or PBVD (see 12.15.4). Otherwise either
RSVD or PBVD (see 12.15.4) should be specified.
2. solution gas ratio value at this depth (METRIC: sm3 /sm3 , FIELD: Msc f /stb).
The number of tables specified is equal to number of equilibrium regions defined in
EQLDIMS (see 12.1.27). Each table should end with slash (/). Between depth points dis-
solved gas-oil ratio will be interpolated linearly.
Example
EQLDIMS
2 /
...
EQUIL
2300 200 2500 0.1 2300 0.001 1 /
2310 205 2520 0.05 2360 0.0 1 /
/
RSVD
2000 60
2500 68
3000 73.5
/
2000 100
3000 200
/
In this example the data for two regions are specified. Since in the first region GOC
coincides with reference depth Ddat , first RSVD table will not be used, because bubble point
pressure on GOC and below will be set equal to datum pressure, 200.
In the second equilibration region GOC depth differs from Ddat , so second (2-line) RSVD
table will be used to calculate oil bubble point pressure.
12.15.3. RSVD 1080

12.15.4 PBVD


Section
This keyword specifies for each equilibrium region initial bubble point pressure distribu-
tion, used in initial conditions computations in case of equilibrium initialization using EQUIL
(see 12.15.2). If in a 3-phase live oil model all equilibrium regions have GOC equal to Ddat ,
there is no need to define RSVD (see 12.15.3) or PBVD (see 12.15.4). Otherwise either
PBVD or RSVD (see 12.15.3) should be specified.
2. bubble point pressure value at this depth (METRIC: barsa, FIELD: psia).

EQLDIMS (see 12.1.27). Each table should end with slash (/). Between depth points bubble
point pressure will be interpolated linearly.
Example
EQLDIMS
2 /
...
EQUIL
2300 200 2500 0.1 2400 0.001 1 /
2310 205 2520 0.05 2310 0.0 1 /
PBVD
2000 250
2500 310
3000 350
/
2000 200
3000 300
/
In this example the data for two regions are specified. Since in the second region GOC
coincides with reference depth Ddat , second PBVD table will not be used, because bubble
point pressure on GOC and below will be set equal to datum pressure, 205.
12.15.4. PBVD 1081

In the first equilibration region GOC depth differs from Ddat , so first (3-line) PBVD table
will be used to calculate oil bubble point pressure.
12.15.4. PBVD 1082

12.15.5 RVVD


Section
This keyword specifies for each equilibrium region initial vaporized oil concentration
distribution, used in initial conditions computations in case of equilibrium initialization using
EQUIL (see 12.15.2). If in a 3-phase wet gas model all equilibrium regions have GOC equal
to Ddat , there is no need to define RVVD (see 12.15.5) or PDVD (see 12.15.6). Otherwise
either RVVD or PDVD (see 12.15.6) should be specified.
2. vaporized oil concentration value at this depth (METRIC: sm3 /sm3 , FIELD:
Msc f /stb).

EQLDIMS (see 12.1.27). Each table should end with slash (/). Between depth points dis-
solved gas-oil ratio will be interpolated linearly.
Example
EQLDIMS
2 /
...
EQUIL
2300 200 2500 0.1 2300 0.001 0 1 /
2310 205 2520 0.05 2360 0.0 0 1 /
/
RVVD
2000 0.00060
2500 0.00068
3000 0.000735
/
2000 0.000100
3000 0.000200
/
In this example the data for two regions are specified. Since in the first region GOC
coincides with reference depth Ddat , first RVVD table will not be used, because dew point
12.15.5. RVVD 1083

In the second equilibration region GOC depth differs from Ddat , so second (2-line) RVVD
table will be used to calculate gas dew point pressure.
12.15.5. RVVD 1084

12.15.6 PDVD


Section
This keyword specifies for each equilibrium region initial dew point pressure distribution,
used in initial conditions computations in case of equilibrium initialization using EQUIL (see
12.15.2). If in a 3-phase wet gas model all equilibrium regions have GOC equal to Ddat ,
there is no need to define RVVD (see 12.15.5) or PDVD (see 12.15.6). Otherwise either
PDVD or RVVD (see 12.15.5) should be specified.
2. dew point pressure value at this depth (METRIC: barsa, FIELD: psia).
EQLDIMS (see 12.1.27). Each table should end with slash (/). Between depth points bubble
point pressure will be interpolated linearly.
Example
EQLDIMS
2 /
...
EQUIL
2300 200 2500 0.1 2400 0.001 0 1 /
2310 205 2520 0.05 2310 0.0 0 1 /
PDVD
2000 250
2500 310
3000 350
/
2000 200
3000 300
/
In this example the data for two regions are specified. Since in the second region GOC
coincides with reference depth Ddat , second PDVD table will not be used, because dew point
In the first equilibration region GOC depth differs from Ddat , so first (3-line) PDVD
table will be used to calculate gas dew point pressure.
12.15.6. PDVD 1085

12.15.7 THPRES


Section
The keyword is used to set threshold pressure value for flow between equilibration re-
gions. If pressure difference between cells of specified regions is less than threshold value,
there will be no flow between those cells. Otherwise flow between cells will be calculated
basing on pressure difference reduced by threshold value. By default, threshold value is equal
to 0.
See also keyword THPRESFT (see 12.2.39).
Keyword is followed by a 3-column table, each line should end with slash /. Last table
line should contain only slash symbol (/).
1. number of first equilibration region;
2. number of second equilibration region;
3. threshold pressure value for flow between those regions (METRIC: barsa, FIELD:
psia) .
Default: threshold pressure equal to 0.

Note: if two regions are indicated several times (in any order), last value of threshold
pressure will be used in calculations.
Example
THPRES
1 2 10.0 /
2 1 5.0 /
1 3 15.1 /
3 1 15.1 /
2 3 7.0 /
1 4 /
4 1 /
/
In this example threshold pressure in any direction will be equal to 5 for regions 1 and
2 (last indicated value), 15.1 for regions 1 and 3, 7 for regions 2 and 3, default (zero) for
regions 1 and 4.
12.15.7. THPRES 1086

12.15.8 PRESSURE


Section
This keyword specifies initial pressures (METRIC: barsa, FIELD: psia). The same
number of values as number of grid blocks must be specified. This is initial value of pO
in 2.3.
Default: none
Example
DIMENS
5 5 1
/
...
PRESSURE
25*235
/
This example sets equal pressures = 235 in all 25 grid blocks (grid dimensions are 5x5x1).
Example
DIMENS
5 3 2
/
...
PRESSURE
235 235 235 235 235 235 235 235
235 235 235 235 235 235 235
250 250 250 250 250 250 250 250
250 250 250 250 250 250 250
/
This example specifies pressure equal to 235 in the first layer of a 5x3x2 two-layer grid,
and pressure equal to 250 in the second layer.
12.15.8. PRESSURE 1087

Example
DIMENS
5 3 2
/
...
PRESSURE
15*235 15*250
/
This example is equivalent to the previous one, but uses the short form with asterisks.
12.15.8. PRESSURE 1088

12.15.9 PRVD


Section
This keyword specifies initial pressure for each depth level. It can be used to specify
initial pressure distribution instead of PRESSURE (see 12.15.8) keyword.
Table should consist of at least two lines. The following parameters are to be specified
on each line:
2. pressure value at this depth (METRIC: barsa, FIELD: psia).

EQLDIMS (see 12.1.27). Each table should end with slash (/). Between depth points pressure
will be interpolated linearly. Extrapolation outside specified pressure interval will also be
linear.
Example
EQLDIMS
2 /
PRVD
2000 250
2500 310
3000 350
/
2000 200
3000 300
/
In this example the data for two regions are specified.
12.15.9. PRVD 1089

12.15.10 SWAT
Data x tNavigator x E300 x MORE GEM


Section
This keyword specifies initial water saturations. The same number of values as the number
of grid blocks must be specified. This is initial value of SW in 2.3.
If only water saturation is specified, gas saturation is defaulted to zero and initial oil
saturation is calculated automatically according to formula SO = 1 SW .
Default: none
Example
DIMENS
5 5 1
/
...
SWAT
25*0.25
/
This example sets initial water saturation equal to 0.25 in all 25 grid blocks (grid dimen-
sions are 5x5x1).
Example
DIMENS
5 3 2
/
...
SWAT
0.25 0.25 0.25 0.25 0.25 0.25 0.25 0.25
0.25 0.25 0.25 0.25 0.25 0.25 0.25
0.50 0.50 0.50 0.50 0.50 0.50 0.50 0.50
0.50 0.50 0.50 0.50 0.50 0.50 0.50
/
This example sets different water saturations in two layers of a 5x3x2 grid: 0.25 in the
upper layer and 0.50 in the lower layer.
12.15.10. SWAT 1090

Example
DIMENS
5 3 2
/
...
SWAT
15*0.25 15*0.50
/
This example is equivalent to the previous one, but it uses short form with asterisks.
12.15.10. SWAT 1091

12.15.11 SGAS


Section
This keyword specifies initial gas saturations. The same number of values as the number
of grid blocks must be specified. This is initial value of SG in 2.3.
If SGAS (see 12.15.11) is specified, then gas is considered to present in the system and
initial oil saturation is calculated according to formula SO = 1 SG SW
Default: none
Example
DIMENS
5 5 1
/
...
SGAS
25*0.75
/
This example sets initial gas saturation equal to 0.75 in all 25 grid blocks (grid dimensions
are 5x5x1).
Example
DIMENS
5 3 2
/
...
SGAS
0.75 0.75 0.75 0.75 0.75 0.75 0.75 0.75
0.75 0.75 0.75 0.75 0.75 0.75 0.75
0.50 0.50 0.50 0.50 0.50 0.50 0.50 0.50
0.50 0.50 0.50 0.50 0.50 0.50 0.50
/
This example sets different gas saturations in two layers of a 5x3x2 grid: 0.75 in the
upper layer and 0.50 in the lower layer.
12.15.11. SGAS 1092

Example
DIMENS
5 3 2
/
...
SGAS
15*0.75 15*0.50
/
12.15.11. SGAS 1093

12.15.12 SOIL


Section
This keyword specifies initial oil saturations. The same number of values as the number
of grid blocks must be specified. This is initial value of SO in 2.3.
If only SOIL (see 12.15.12) is specified, then gas is considered to be absent in the system
and initial water saturation is calculated according to formula SW = 1 SO
Default: none
Example
DIMENS
5 5 1
/
...
SOIL 25*0.21
/
This example sets initial oil saturation equal to 0.21 in all 25 grid blocks (grid dimensions
are 5x5x1).
Example
DIMENS
5 3 2
/
...
SOIL
0.21 0.21 0.21 0.21 0.21 0.21 0.21 0.21
0.21 0.21 0.21 0.21 0.21 0.21 0.21
0.50 0.50 0.50 0.50 0.50 0.50 0.50 0.50
0.50 0.50 0.50 0.50 0.50 0.50 0.50
/
This example sets different oil saturations in two layers of a 5x3x2 grid: 0.21 in the upper
layer and 0.50 in the lower layer.
12.15.12. SOIL 1094

Example
DIMENS
5 3 2
/
...
SOIL
15*0.21 15*0.50
/
12.15.12. SOIL 1095

12.15.13 SSOLID


Section
The keyword specifies the initial solid saturation. The same number of values as the
number of blocks should be specified. The data should be terminated with a slash /.
Default: not specified.
Example
SSOLID
1500*0.087
In this example 1500 grid blocks have the same initial solid saturation 0.087.
12.15.13. SSOLID 1096

12.15.14 APIVD


Section
The keyword specifies tables of oil API density versus depth for API tracking option
2.10.
The number of tables should be equal to the number of equilibration regions. Each table
One table row contains the following data:
1. depth (METRIC: m, FIELD: f t ) (the values should increase in each next row);
2. oil API gravity at this depth.
Example
APIVD
2500 35.3
3000 39.4
3200 40.1 /
12.15.14. APIVD 1097

12.15.15 OILAPI


Section
The keyword is used to specify initial oil API values for API tracking option 2.10.
The same number of values as the number of grid blocks must be specified. The data
Example
OILAPI
2000*38.5 2000*39.6 2000*41.8/
In this example first 2000 grid blocks have API gravity 38.5, next 2000 blocks - 39.6,
next 2000 blocks - 41.8.
12.15.15. OILAPI 1098

12.15.16 SMF


Section
This keyword specifies cell initial solid composition. The same number of values as
the product of grid blocks NX * NY * NZ (DIMENS (see 12.1.25)) and the number of
components (COMPS (see 12.13.3)) should be specified.The data should be terminated with
a slash /.
Default: not specified.
Example
DIMENS
5 10 2 /
COMPS
5 /
...
SMF
100*0.
100*0.
100*0.
100*0.
100*1.
/
This example sets initial solid composition for 100 grid blocks and 5 components.
12.15.16. SMF 1099

12.15.17 XMF


Section
The keyword sets the initial oil composition for each grid block. One should specify the
same number of values as the product of numbers of grid blocks NX * NY * NZ (DIMENS
(see 12.1.25)) and the number of components (COMPS (see 12.13.3)). The data should be
If the sum of values for any grid block isnt 1 then the values are normalized so that
the error is less than 10 percent. If the error if greater than 10 percent the message of data
initialization error will occur.
Default: none.
Example
DIMENS
5 10 2 /
COMPS
5 /
...
XMF
100*0.5
100*0.3
100*0.2
100*0.
100*0.
/
This example sets initial oil composition for 100 grid blocks and 5 components.
12.15.17. XMF 1100

12.15.18 YMF


Section
The keyword sets the initial gas composition for each grid block. One should specify the
same number of values as the product of numbers of grid blocks NX * NY * NZ (DIMENS
(see 12.1.25)) and the number of components (COMPS (see 12.13.3)). The data should be
Default: none.
Example
DIMENS
5 10 2 /
COMPS
5 /
...
YMF
100*1
100*0
100*0
100*0
100*0
/
This example sets initial gas composition for 100 grid blocks and 5 components.
12.15.18. YMF 1101

12.15.19 ZMF


Section
The keyword sets the initial total composition for each grid block (values z0c = Nc /Ntot
0 ,
n0c
c= 2, . . . , n0c , 0
Ntot = Nc ). One should specify the same number of values as the product
c=2
of numbers of grid blocks NX * NY * NZ (DIMENS (see 12.1.25)) and the number of
components (COMPS (see 12.13.3)). The data should be terminated with a slash /.
Default: none.
Note:
composition is specified in SOLUTION in each grid block (ZMF (see 12.15.19) or
XMF (see 12.15.17)/YMF (see 12.15.18) is present), then:
each EQUIL region (using ZMF (see 12.15.19) or XMF (see 12.15.17)/YMF (see
12.15.18) correspondingly);
12.15.19. ZMF 1102

Example
DIMENS
5 10 2 /
COMPS
5 /
...
ZMF
100*0.5
100*0.2
100*0.2
100*0.06
100*0.04
/
This example sets initial total composition for 100 grid blocks and 5 components.
12.15.19. ZMF 1103

12.15.20 FIELDSEP


Section
This keyword specifies field separator. All the wells use this separator for default. To
specify different separator for one well or for well group one should use the keywords SEP-
COND (see 12.18.144), WSEPCOND (see 12.18.145).
This separator is used to calculated oil and gas in-place volumes for field. To calculate
oil and gas in-place volumes for different FIP regions with different separators one should
specify the keyword FIPSEP (see 12.15.21).
Sum of oil and gas in-plase for FIP region (FIPSEP) can be not equal to oil and gas in-plase
for field calculated via FIELDSEP (see 12.15.20).
Each data row specifies one separator stage. Multi-stage separator is specified via several
data lines.
The keyword can be followed by several number of data rows, that specify separator
stages (in increasing order). Each row should be terminated with a slash /. The data should
be terminated with a final slash /.

1. stage number;
2. separator stage temperature (METRIC: C, FIELD: F).
The value should not be less then 5 C or 41 F. Else the following warning will be
displayed:
Warning: temperature value (-50.000000) set at stage number 2 is below expected
minimum 41F;
3. separator stage pressure (METRIC: barsa, FIELD: psia);
4. liquid destination output from the separator. If the stage before last has the number -1,
then the oil volume after this stage is added to the stock tank oil;
5. gas destination output from the separator;
6. k-value table number (IGNORED), this is an Eclipse compatibility field;
7. gas plant table number. Tables are specified via keywords GPTABLE (see 12.15.22),
GPTABLE3 (see 12.15.24), GPTABLEN (see 12.15.23). If 0 value is specified then
gas plant table is not used and calculation of equation of state will be done;
12.15.20. FIELDSEP 1104

8. surface equation of state number.
Default:
separator stage temperature 15.56( C);
separator stage pressure 1.013 (barsa);
liquid destination output from the separator 0. Defines the liquid transition to the next
separator stage (for all stages except the last one), or the stock-tank (for the last stage);
gas destination output from the separator 0. Gas is accumulated in the stock-tank or
field separator vapor. The volume is converted to the standard conditions;
gas plant table number 0.
Example
FIELDSEP
1 37.000 110.81469 1* 1* /
2 -25.000 49.03305 1* 1* /
3 -8.73 12.491 1* 1* /
4 20.000 1.01325 1* 1* /
/
In this example four-stage separator is specified.

Luquid from the stage 1 goes to the stage 2. From the stage 2 to the stage 3, from the stage
3 to the stage 4, from the stage 4 to the stock-tank.
Gas from the stages 1, 2, 3, 4 to the stock-tank (for default).
12.15.20. FIELDSEP 1105

12.15.21 FIPSEP


Section
This keyword specifies separator for FIP regions. This separator is used to calculated oil
and gas in-place volumes for FIP region.
Oil and gas volume in-place are calculated via field separator FIELDSEP (see 12.15.20),
thats why sum of oil and gas in-plase for FIP region (FIPSEP) can be not equal to oil and
gas in-plase for field calculated via FIELDSEP (see 12.15.20).
data lines.
1. number of the FIP region in which this separator is used for oil and gas resources
calculations;
2. stage number;
3. separator stage temperature (METRIC: C, FIELD: F);
gas plant table is not used and calculation of equation of state will be done.
Default:
12.15.21. FIPSEP 1106

separator stage (for all stages except the last one), or the tock-tank (for the last stage);
Example
FIPSEP
2 1 15 1.03 3* 1 /
/
In this example for FIP region number 2 a one-stage separator is specified.
12.15.21. FIPSEP 1107

12.15.22 GPTABLE


Section
This keyword is used to specify gas plant recovery factors. (Also gas plant table can be
specified via the keywords GPTABLE3 (see 12.15.24), GPTABLEN (see 12.15.23)).
The number of gas plant table should be specified in the keywords FIELDSEP (see
12.15.20), FIPSEP (see 12.15.21), SEPCOND (see 12.18.144) to use these tables in con-
verting flow rates into surface conditions.
The first table row contains the following parameters:
1. gas plant table number;
2. first component number to define the heavy fractions;
3. last component number to define the heavy fractions.
After the first row goes the table itself. It consists of the recovery fractions for all
components as a function of the heavy mole fractions. One row of the table contains the
following data:
1. heavy component mole fractions;
2. Nc values (is equal to the numer of component in the run COMPS (see 12.13.3)):
liquid recovery fractions for each hydrocarbon component. Liquid recovery fraction for
one component the number of moles of liquid per one mole of feed.
Default:
first component number to define the heavy fractions number of the last model
component;
last component number to define the heavy fractions number of the last model
component.
12.15.22. GPTABLE 1108

Example
GPTABLE
1 8 8
0.0 0.0 0.00 0.08 0.00031 0.05 0.10 1.0 1.0
0.2 0.0 0.00 0.09 0.00032 0.07 0.12 1.0 1.0
0.3 0.0 0.00 0.09 0.00034 0.07 0.14 1.0 1.0
/
In this example first table column contains heavy component mole fractions for 8-th
component. Other columns liquid recovery factors for components from 1-st to 8-th.
12.15.22. GPTABLE 1109

12.15.23 GPTABLEN


Section
This keyword is used to specify gas plant recovery table (oil recovery fraction and NGL
(natural gas liquid) recovery fraction). (Also gas plant table can be specified via the keywords
GPTABLE (see 12.15.22), GPTABLE3 (see 12.15.24)).
After the first row goes the table itself. It consists of the recovery fractions for all com-
ponents as a function of the heavy mole fractions.
One row of the table contains the following data:
oil recovery fractions for each hydrocarbon component. Oil recovery fraction for one
component the number of moles of oil per one mole of feed;
NGL recovery fractions for each hydrocarbon component.
Default:
component;
component.
12.15.23. GPTABLEN 1110

Example
GPTABLEN
1 8 8
0.2 0.00 0.00 0.00 0.00061 0.05 0.10 1.0 1.0
0.02 0.03 0.01 0.05200 0.02 0.01 0.0 0.0
/
In this example: 2-nd table row: value 0.2 heavy component mole fractions for 8-th
component. Other columns oil recovery factors for components from 1-st to 8-th.
3-rd row: NGL (natural gas liquid) recovery fractions for components from 1-st to 8-th (for
the same value 0.2).
In this example recovery factors doesnt change with the heavy mole fraction, so only
one value is specified 0.2 and recovery fractions for it.
In case if recovery fractions change, one should specify the next value of heavy mole fraction
and corresponding recovery fractions data arrays for it.
12.15.23. GPTABLEN 1111

12.15.24 GPTABLE3


Section
This keyword is used to specify gas plant recovery table (oil, NGL (natural gas liquid)
and gas recovery fraction). (Also gas plant table can be specified via the keywords GPTABLE
(see 12.15.22), GPTABLEN (see 12.15.23)).
After the first row goes the table itself. It consists of the recovery fractions for all com-
ponents as a function of the heavy mole fractions.
oil recovery fractions for each hydrocarbon component. Oil recovery fraction for one
component the number of moles of oil per one mole of feed;
NGL recovery fractions for each hydrocarbon component;
4. Nc values (is equal to the numer of component in the run COMPS (see 12.13.3)): gas
recovery fractions for each hydrocarbon component.
The sum for each component of oil, gas and NGL recovery fractions can be not equal to
1.
Default:
12.15.24. GPTABLE3 1112

component;
component.
Example
GPTABLE3
1 8 8
0.2 0.00 0.00 0.00 0.00031 0.05 0.10 1.0 1.0
0.02 0.01 0.01 0.05000 0.02 0.01 0.0 0.0
0.84 0.77 0.99 0.94969 0.93 0.89 0.0 0.0
/
In this example: 2-nd table row: value 0.2 heavy component mole fractions for 8-th
component. Other columns oil recovery factors for components from 1-st to 8-th.
3-rd row: NGL (natural gas liquid) recovery fractions for components from 1-st to 8-th (for
the same value 0.2).
4-th row: gas recovery fractions for components from 1-st to 8-th (for the same value 0.2).
In this example recovery factors doesnt change with the heavy mole fraction, so only
one value is specified 0.2 and recovery fractions for it.
In case if recovery fractions change, one should specify the next value of heavy mole fraction
and corresponding recovery fractions data arrays for it.
12.15.24. GPTABLE3 1113

12.15.25 RECOVERY


Section
This keywords specified recovery plant table.
After the first row goes the table itself. It consists of Nc + 1 columns (Nc is equal to
cumber of the components in the model COMPS (see 12.13.3)).
heavy component mole fraction;
Nc values: NGL (natural gas liquid) recovery fractions of each component for this
heavy component mole fraction. Liquid recovery fraction for one component the
number of moles of NGL (natural gas liquid) per one mole of feed.
Default:
component;
component.
Example
RECOVERY
6 6
0.0 0.0 0.001 0.03 0.35 0.74 0.77
0.03 0.0 0.002 0.07 0.39 0.85 0.81
0.05 0.0 0.004 0.10 0.48 0.89 0.85
/
12.15.25. RECOVERY 1114

12.15.26 TEMPI


Section
The keyword sets the initial temperature (METRIC: C, FIELD: F) in each grid block.
The same number of values as the number of grid blocks must be specified. The data should
Default: none
Example
DIMENS
10 10 5 /
...
TEMPI
250*100 250*120
/
This example sets the initial temperature in the reservoir: 100 C in first 250 grid blocks
and 120 C in next 250 grid blocks.
12.15.26. TEMPI 1115

12.15.27 RTEMPA


Section
The keyword specifies initial reservoir temperature (METRIC: C, FIELD: F) when

temperature option is used (2.30). One temperature value should be specified. The data
Default:
temperature: 60 F for E100 models, 100 C for E300 models.
Example
RTEMPA
90 /
In this example initial reservoir temperature is 90 C.
12.15.27. RTEMPA 1116

12.15.28 RTEMPVD


Section
The keyword specifies the dependence between initial reservoir temperature and depth
(METRIC: C, FIELD: F) when temperature option is used (2.30). The same number of
tables as the number of equilibration regions should be entered (first parameter of the key-
word EQLDIMS (see 12.1.27)). Each table should be terminated with a slash /.
depth (METRIC: m, FIELD: f t );
corresponding value of reservoir temperature (METRIC: C, FIELD: F).
Example
RTEMPVD
1200 60
1500 70
1900 80
2500 90
2700 102
/
12.15.28. RTEMPVD 1117

12.15.29 WTEMPDEF


Section
The keyword specifies the default water temperature for injectors (METRIC: C, FIELD:
F)in case if the keyword WTEMP (see 12.18.153) is not specified. In Eclipse default tem-
perature of injected water is 0 C. In case when in Eclipse data format model the keyword
WTEMPDEF is used it redefines zero value of water temperature.
The same number of values as the number of PVT-regions should be entered (default
injected water temperature should be specified for each PVT-region). The data should be
Example
WTEMPDEF
15 6 12 /
/
In this example default temperature of injected water is specified for 3 PVT-regions.
12.15.29. WTEMPDEF 1118

12.15.30 PBUB


Section
This keyword specifies initial bubble point pressure (METRIC: barsa, FIELD: psia)
for undersaturated reservoir. The same number of values as number of grid blocks must be
specified. The data should be terminated by a slash /.
This keyword is an alternative to the keyword RS (see 12.15.31) (only one of them
should be specified).
Default: none
Note: The following rules apply for initializing the reservoir with user specified initial bubble
point pressure:
If the gas saturation in some grid block is non zero, then the specified bubble point
pressure for this grid block is ignored and it is reset to block pressure in this grid block;
If specified bubble point pressure in some block exceeds the initial pressure in this grid
block the bubble point pressure for this grid block is reset to initial block pressure;
Example
DIMENS
5 5 1
/
...
PBUB
25*235
/
This example sets equal initial bubble point pressures = 235 in all 25 grid blocks (grid
dimensions are 5x5x1).
12.15.30. PBUB 1119

Example
DIMENS
5 3 2
/
...
PBUB
235 235 235 235 235 235 235 235
235 235 235 235 235 235 235
250 250 250 250 250 250 250 250
250 250 250 250 250 250 250
/
This example specifies initial bubble point pressure equal to 235 in the first layer of a
5x3x2 two-layer grid, and equal to 250 in the second layer.
Example
DIMENS
5 3 2
/
...
PBUB
15*235 15*250
/
12.15.30. PBUB 1120

12.15.31 RS


Section
This keyword specifies initial gas solution in oil for live oil model (METRIC: sm3 /sm3 ,
FIELD: Msc f /stb). The same number of values as number of grid blocks must be specified.
The data should be terminated by a slash /.
This is initial value of RG,O in 2.3.

This keyword is an alternative to the keyword PBUB (see 12.15.30) (only one of them
Example
DIMENS
4 4 1
/
...
RS
16*0.003
/
This example sets equal initial gas solution in oil = 0.003 in all 25 grid blocks (grid
Example
DIMENS
3 3 2
/
...
RS
.235 .235 .235 .235 .235 .235 .235 .235 .235
.250 .250 .250 .250 .250 .250 .250 .250 .250
/
This example specifies initial gas solution in oil equal to .235 in the first layer of a 5x3x2
two-layer grid, and equal to .0250 in the second layer.
12.15.31. RS 1121
Example
DIMENS
3 3 2
/
...
RS
9*.235 9*.250
/
12.15.31. RS 1122
12.15.32 RV


Section
This keyword specifies initial oil vaporization in gas for wet gas model (METRIC:
sm3 /sm3 , FIELD: Msc f /stb). The same number of values as number of grid blocks must be
specified. This is initial value of RO,G in 2.3.
This keyword is an alternative to the keyword PDEW (see 12.15.33) (only one of them
Default: none
Example
DIMENS
5 5 1
/
...
RV
25*0.0001
/
This example sets equal initial oil vaporisation in gas values = 0.0001 in all 25 grid
blocks (grid dimensions are 5x5x1).
Example
DIMENS
5 3 2
/
...
RV
.0235 .0235 .0235 .0235 .0235 .0235 .0235 .0235
.0235 .0235 .0235 .0235 .0235 .0235 .0235
.0250 .0250 .0250 .0250 .0250 .0250 .0250 .0250
.0250 .0250 .0250 .0250 .0250 .0250 .0250
/
This example specifies initial oil vaporisation equal to .0235 in the first layer of a 5x3x2
two-layer grid, and equal to .0250 in the second layer.
12.15.32. RV 1123
Example
DIMENS
5 3 2
/
...
RV
15*.0235 15*.0250
/
12.15.32. RV 1124
12.15.33 PDEW


Section
This keyword specifies initial bubble point pressure (METRIC: barsa, FIELD: psia) for
black oil model. The same number of values as number of grid blocks must be specified.
This keyword is an alternative to the keyword RV (see 12.15.32) (only one of them
Default: none
Example
DIMENS
6 5 2
/
...
PDEW
60*193
/
This example sets equal initial bubble point pressure = 193 in all 60 grid blocks (grid
Example
DIMENS
7 5 2
/
...
PDEW
35*162 35*170
/
This example specifies initial bubble point pressure to 162 in the first layer of a 5x3x2
two-layer grid, and equal to 170 in the second layer.
12.15.33. PDEW 1125

12.15.34 DATUM


Section
The keyword sets the datum depth for calculations of depth (METRIC: m, FIELD: f t )
corrected pressures. If this keyword isnt specified the depth entered by 1-st parameter of
EQUIL (see 12.15.2) for 1-st equilibrium region will be used.
Example
DATUM 3000
/
12.15.34. DATUM 1126

12.15.35 DATUMR


Section
The keyword sets the datum depth for calculations of depth (METRIC: m, FIELD: f t )
corrected pressures for each FIP region.
One should specify the same number of values as the number of FIP regions (5-th parameter
of TABDIMS (see 12.1.26)).
Example
TABDIMS 3 2 2* 4
DATUMR 3000 4200 5100 2800
/
This example sets datum depths for 4 FIP regions.
12.15.35. DATUMR 1127

12.15.36 DATUMRX


Section
The keyword sets datum depths for each region in FIP-family (regions that are specified
via FIP (see 12.4.11) keyword in addition to standard FIPNUM (see 12.4.10) regions). The
number of values for each family cant exceed the number of regions in this family. If depths
are not specified for all regions, and if the keyword DATUMR (see 12.15.35) is present, then
datum depths values will be taken from it. Otherwise, values for remaining regions will be
equal to the last specified region value.
After the keyword any number of data lines can be specified. Each data line contains the
following parameters:
1. FIP-family name. In particular, family name can be specified via the keyword FIP (see
12.4.11) as FIPX, where X is a family name;
2. datum depth for each region (METRIC: m, FIELD: f t );
Each data line should be ended by a symbol /. The data should be terminated with a
slash /.
Default:
FIP-family name: standard fluid-in-place regions FIPNUM (see 12.4.10).
Example
DATUMRX
NUM 100 600 1100 /
/
In the example for three regions of FIP-family NUM datum depths are specified.
12.15.36. DATUMRX 1128

12.15.37 TBLK


Section
The keyword specifies the initial concentration of a tracer in each grid block The key-
word should be followed by real numbers, specifying the initial tracer concentration. The
same number of values as the number of grid blocks should be specified. Grid blocks are
ordered with the X-axis index cycling fastest, followed by the Y-axis index, followed by the
Z-axis index. The data should be terminated with a slash /.
The keyword may be entered in two formats: e100 and e300.
Note. In tNavigator tracer is associated with component, not with phase (even for black-
oil case). Thus, it can be in different phase states.
The keyword in e100 format:
1. characters 1-4 should be TBLK;
2. character 5 letter F (for the tracer whose associated phase can only exist in the free
state) or letter S (for the tracer whose associated phase can only exist in the solution
state).
If a letter S is specified, this keyword is ignored.
If the letter F is specified, this letter is ignored, the keyword will be read in e300
format;
3. other characters name of the tracer whose concentration is initialized (name is speci-
fied via the keyword TRACER (see 12.7.1); in Eclipse tracer name may consist of up
to 3 characters, but in tNavigator tracer name may consist of any number of characters).
1. characters 1-4 should be TBLK;
2. other characters name of the tracer whose concentration is initialized (name is speci-
fied via the keyword TRACER (see 12.7.1); in Eclipse tracer name may consist of up
to 3 characters, but in tNavigator tracer name may consist of any number of characters).
12.15.37. TBLK 1129

Example
TRACER
A WAT /
B WAT /
/
...
TBLKFA
2600*1 /
TBLKFB
2600*0. /
In this example there are two tracers A and B, associated with water phase. Tracer A has
initial concentration 1 in all grid blocks, tracer B 0 in all grid blocks.
12.15.37. TBLK 1130

12.15.38 TNUM


Section
The keyword specifies tracer concentration region numbers for each grid block. For each
tracer concentration region the keyword TVDP (see 12.15.39) specifies the table of initial
tracer concentration with respect to depth.

1. characters 1-4 should be TNUM;
state). If a letter S is specified, this keyword is ignored. If the letter F is specified, this
letter is ignored, the keyword will be read in e300 format;
3. other characters name of the tracer whose tracer concentration regions are initialized
(name is specified via the keyword TRACER (see 12.7.1); in Eclipse tracer name may
consist of up to 3 characters, but in tNavigator tracer name may consist of any number
of characters).
1. characters 1-4 should be TNUM;
2. other characters name of the tracer whose tracer concentration regions are initialized
(name is specified via the keyword TRACER (see 12.7.1); in Eclipse tracer name may
consist of up to 3 characters, but in tNavigator tracer name may consist of any number
of characters).
The keyword should be followed by one integer for every grid block, specifying the
initial tracer concentration region number to which it belongs. The region number should not
be grater than the 4-th parameter of the keyword EQLDIMS (see 12.1.27). Grid blocks are
ordered with the X-axis index cycling fastest, followed by the Y-axis index, followed by the
Z-axis index. The data should be terminated with a slash /.
12.15.38. TNUM 1131

Example
TNUMFB
32*1 32*2
/
...
TVDPFB
0 0.1
1000 0.3
2000 0.5 /
0 0.2
1000 0.4
2000 0.6 /
/
In this example tracer B has 2 initial concentration regions (specified via TNUM (see
12.15.38)): first 32 blocks belong to 1-nd region, next 32 blocks 2-nd region. These two
regions have two corresponding tables of initial tracer concentration with respect to depth
(specified via TVDP (see 12.15.39)).
12.15.38. TNUM 1132

12.15.39 TVDP


Section
The keyword specifies tables of initial tracer concentration with respect to depth for each
tracer. Tracer concentration region numbers for each grid block are specified via the keyword
TNUM (see 12.15.38).

1. characters 1-4 should be TVDP;
state). If a letter S is specified, this keyword is ignored. If the letter F is specified, this
letter is ignored, the keyword will be read in e300 format;
3. other characters name of the tracer whose table of initial tracer concentration with
respect to depth is initialized (name is specified via the keyword TRACER (see 12.7.1);
in Eclipse tracer name may consist of up to 3 characters, but in tNavigator tracer name
may consist of any number of characters).
1. characters 1-4 should be TVDP;
2. other characters name of the tracer whose table of initial tracer concentration with
respect to depth is initialized (name is specified via the keyword TRACER (see 12.7.1);
in Eclipse tracer name may consist of up to 3 characters, but in tNavigator tracer name
may consist of any number of characters).
The keyword should be followed by table of initial tracer concentration with respect to
depth. For each concentration region (entered via TNUM (see 12.15.38)) should be specified
one table. Each table should be terminated with a slash /. All tables should be terminated
Each table row should consist of the following parameters (the number of lines should
not be greater than the 5-th parameter of the keyword EQLDIMS (see 12.1.27)):
12.15.39. TVDP 1133

2. the corresponding initial tracer concentration at this depth (the concentration should be
not negative).
Example
TNUMFB
32*1 32*2
/
...
TVDPFB
0 0.1
1000 0.3
2000 0.5 /
0 0.2
1000 0.4
2000 0.6 /
/
In this example tracer B has 2 initial concentration regions (specified via TNUM (see
12.15.38)): first 32 blocks belong to 1-nd region, next 32 blocks 2-nd region. These two
regions have two corresponding tables of initial tracer concentration with respect to depth
(specified via TVDP (see 12.15.39)).
12.15.39. TVDP 1134

12.15.40 ROCKSALT


Section
The keyword is used to specify initial mass of reservoir salt (METRIC: kg, FIELD: lb).
The same number of values as the number of grid blocks should be specified. The data
This keyword can be used only if the Brine option is active (the keyword BRINE (see
12.1.58)). The dissolution rate constant salt (the keyword SALTPROP (see 12.7.4)) should
also be specified to simulate dissolution process.
Example
DIMENS
5 5 1
/
...
ROCKSALT
25*20000
/
In this example initial mass of reservoir salt is the same for all grid blocks - 20000(kg).
12.15.40. ROCKSALT 1135

12.15.41 SALT


Section
The keyword should be followed by one real number for every grid block specifying the
initial salt concentration (METRIC: kg/m3 , FIELD: lb/stb). The number of values should
be equal to the number of grid blocks. Grid blocks should be ordered with the X axis index
cycling fastest, followed by the Y axis index and finally the Z axis index. The data should
The keyword should be used when the initial state has been set by enumeration (keywords
PRESSURE (see 12.15.8), RS (see 12.15.31), RV (see 12.15.32), SGAS (see 12.15.11)
and SWAT (see 12.15.10)). For a run initialized by equilibration EQUIL (see 12.15.2),
the keyword SALTVD (see 12.15.42) should be used instead of SALT (see 12.15.41) (salt
concentration versus depth for equilibration).
Example
SALT
50*0
50*0.75
50*2.6
50*9.2
50*21.0 /
12.15.41. SALT 1136

12.15.42 SALTVD


Section
The keyword sets salt concentration versus depth for equilibration for each equilibration
region.
The keyword should be used when the initial state has been set by equilibration EQUIL
(see 12.15.2). For a run initialized by enumeration (keywords PRESSURE (see 12.15.8),
RS (see 12.15.31), RV (see 12.15.32), SGAS (see 12.15.11) and SWAT (see 12.15.10)).
the keyword SALT (see 12.15.41) should be used instead of SALTVD (see 12.15.42).
The data consists of the tables. Number of tables should be equal to the number of equi-
libration region (first parameter of the keyword EQLDIMS (see 12.1.27)). Each table should
One table row consists of:
2. the corresponding value of salt concentration (METRIC: kg/m3 , FIELD: lb/stb).
Example
SALTVD
1000.0 144.0
2000.0 144.0
/
1000.0 144.0
2000.0 144.0
/
In this example there are 2 tables of salt concentration versus depth. In both tables the
value of salt concentration is the same at all specified depths and is equal to 144 kg/m3 .
12.15.42. SALTVD 1137

12.15.43 SRSALT


Section
The keyword specifies initial reservoir salt distribution through its saturation (Saturation
Rock SALT). The keyword can be used only for runs in which the Brine option is active (the
keyword BRINE (see 12.1.58)).
The number of values to be entered is equal to the number of blocks in the model. The
Reservoir salt distribution through its saturation (Saturation Rock SALT) - it is a 3D map,
the values are calculated by the following formula:
VRockSalt
SRSALT =
VRock
where VRockSalt - reservoir salt volume, VRock - rock volume at pressure pre f , specified by
the keyword ROCK (see 12.5.16).
Example
SRSALT
2000*0.2
/
This example sets the initial ratio of reservoir salt volume to the rock volume - 0.2.
12.15.43. SRSALT 1138

12.15.44 SURF


Section
initial surfactant concentration (METRIC: kg/sm3 , FIELD: lb/stb).
The number of values should be equal to the number of grid blocks. Grid blocks should
be ordered with the X axis index cycling fastest, followed by the Y axis index and finally
the Z axis index. The data should be terminated with a slash /.
Surfactant injection section 2.25.

Example
SURF
500*0
500*0.75
500*0.6
500*0 /
12.15.44. SURF 1139

12.15.45 SPOLY


Section
initial polymer concentration (METRIC: kg/sm3 , FIELD: lb/stb).
The number of values should be equal to the number of grid blocks. Grid blocks should
Polymer injection section 2.20.

Example
SPOLY
500*0
500*3.75
500*0
500*3.75 /
12.15.45. SPOLY 1140

12.15.46 GASCONC


Section
The keyword should be followed by one real number for every matrix block specify-
ing the initial coal gas concentration (METRIC: sm3 /m3 , FIELD: Msc f / f t 3 ) in Coal Bed
Methane model 2.29.
The number of values should be equal to the number of matrix blocks. Grid blocks should
Note: for compositional model in E300 format the keyword GASCONC can set the initial
coal gas concentration for one component defined via GASCCMP (see 12.15.48).
Example
GASCONC
1200*79.3 1200*77.2 1200*75.4 /
12.15.46. GASCONC 1141

12.15.47 GASSATC


Section
The keyword should be followed by one real number for every matrix block specifying
the initial saturated gas concentration in the coal (METRIC: sm3 /m3 , FIELD: Msc f / f t 3 ) in
Coal Bed Methane model 2.29.
The number of values should be equal to the number of matrix blocks. Grid blocks should
Note 1: for the model in the format E100 the keyword GASSATC is used for the Lang-
muir isotherm scaling LANGMUIR (see 12.9.2) at the initial reservoir pressure. In case if
the keyword GASSATC is not specified, LANGMUIR (see 12.9.2) data will be used without
scaling.
Note 2: for compositional model in E300 format the keyword GASSATC is used for the
Langmuir isotherm scaling (LANGMUIR (see 12.9.2) or LANGMEXT (see 12.9.4)) at the
initial reservoir pressure and composition in the reservoir for one component. The component
is defined via the keyword GASCCMP (see 12.15.48). This scaling factor is used for other
components.
Example
GASSATC
1200*80.3 1200*87.2 1200*85.4 /
12.15.47. GASSATC 1142

12.15.48 GASCCMP


Section
The keyword sets the number of component that is used in the keywords GASSATC (see
12.15.47) and GASCONC (see 12.15.46). If there is only one component in the run you may
not define this keyword.
Example
GASCCMP
4 /
12.15.48. GASCCMP 1143

12.15.49 RPTMAPS


Section
The keyword allows to save additional maps with calculation results.
The following mnemonics are accepted in RUNSPEC section (tNavigator calculations

only; non-compatible with other simulators):
FLOWW - accumulated interblock flows of water phase;
FLOWO - accumulted interblock flows of oil phase;
FLOWG - accumulated interblock flows of gas phase;
FLOWWZ - accumulated interblock flows of water phase in vertical direction;
FLOWOZ - accumulated interblock flows of oil phase in vertical direction;
FLOWGZ - accumulated interblock flows of gas phase in vertical direction;
FIPFLOW - enable FIP flow calculations.
Default: None.
Example
RPTMAPS
FLOWO FLOWG /
This example requests saving two additional parameter maps to results file oil and gas
accumulated flows.
12.15.49. RPTMAPS 1144

12.15.50 RSW


Section
The keyword sets initial concentration of CO 2 in water phase. The following parameters
1. initial concentration of CO 2 in water phase for each grid block (METRIC: m3 /sm3 ;
FIELD: stb/Msc f .
Example
RSW 200*0.145 /
In the example initial concentration of CO 2 in water phase is 0.145 in each grid block.
12.15.50. RSW 1145

12.15.51 SFOAM


Section
The keyword sets initial foam concentration in grid blocks. It can be used only if foam
model option (see 2.21) is activated by the keyword FOAM (see 12.1.64). The following
parameters should be specified:
1. foam concentration in each grid block. Units depends on the first parameter of
FOAMOPTS (see 12.11.2):

Example
SFOAM
300*0.4 /
In the example initial foam concentration in each block is 0.4.
12.15.51. SFOAM 1146

12.15.52 SOILR


Section
The keyword sets initial residual oil saturation values in each grid block. It can be
used only if residual oil saturation option (see 2.22) is activated by the keyword SOR (see
12.12.1).
1. initial residual oil saturation values in each grid block.
Example
SOILR
49*.1
49*.15
49*.2 /
In the example in the first 49 grid blocks initial residual oil saturation is 0.1, in the next
ones are 0.15 and 0.2 respectively.
12.15.52. SOILR 1147

12.15.53 ROMF


Section
The keyword sets initial composition of residual oil in each grid block. It can be used only
if residual oil saturation option (see 2.22) is activated by the keyword SOR (see 12.12.1).
1. component fraction in each grid block. First, fraction of the first component in each
grid block is defined, then the same is performed for the second component and so on.
Example
COMPS
6 /
.....
ROMF
147*0.0
147*0.0
147*0.0
147*0.0
147*0.1
147*0.9 /
6 components are defined in the model. Fraction of the first one is 0 in each block.
Fraction of the 5-th is 0.1, of the 6-th is 0.9.
12.15.53. ROMF 1148

12.16 Inflow from aquifer

tNavigator 4.2 supports the following type of aquifers:
numerical aquifer. Is set via the keywords AQUCON (see 12.16.12), AQUNUM (see
12.16.11);
constant-flux aquifer (analytic aquifer). Is set via the keywords AQUFLUX (see
12.16.2), AQUANCON (see 12.16.10);
Fetkovich aquifer (analytic aquifer). Is set via the keywords AQUFETP (see 12.16.6),
AQUANCON (see 12.16.10), AQUFET (see 12.16.4);
Carter-Tracy aquifer (analytic aquifer). Is set via the keywords AQUTAB (see 12.16.9),
AQUANCON (see 12.16.10), AQUCT (see 12.16.8);
constant head/pressure water aquifer. Is set via the keywords AQUCHWAT (see
12.16.3), AQUANCON (see 12.16.10).
AQANTRC (see 12.16.7) the keyword specifies initial tracer concentrations for analytic
aquifers (keywords AQUFET (see 12.16.4), AQUFETP (see 12.16.6), AQUCT (see 12.16.8),
AQUFLUX (see 12.16.2)).
Calculation options for analytic aquifers are set via the keyword AQUOPTS (see 12.16.5).

12.16.1 AQUDIMS


Section
This keyword sets dimensions for aquifers. The data should be terminated with a slash /.
1. maximum number of lines of numerical aquifer data entered via keyword AQUNUM
(see 12.16.11); this is an Eclipse compatibility field. (IGNORED) In tNavigator number
of lines does not have to be specified because the tables are allocated dynamically;
2. maximum number of lines of connection data for numerical aquifers entered via
keyword AQUCON (see 12.16.12); this is an Eclipse compatibility field. (IGNORED)
allocated dynamically;
3. maximum number of influence tables for Carter-Tracy aquifers, entered via the key-
word AQUTAB (see 12.16.9), (if there are any user supplied tables AQUTAB (see
12.16.9) this number should be 2 or greater, because first table is default);
4. maximum number of rows in a Carter-Tracy aquifer influence table;
5. maximum number of analytic aquifers in the model;
6. maximum number of grid blocks connected to any single analytic aquifer; this is an
Eclipse compatibility field. (IGNORED) In tNavigator number of lines does not have
to be specified because the tables are allocated dynamically.
7. maximum number of aquifer lists; this is an Eclipse compatibility field. (IGNORED)

allocated dynamically.
8. maximum number of analytic aquifers in any single aquifer list; this is an Eclipse
compatibility field. (IGNORED) In tNavigator number of lines does not have to be
specified because the tables are allocated dynamically.
For E300 models parameters 1 and 5 of this keyword are similar. Analogously param-
eters 2 and 6 are similar. If both parameters are specified then the maximum value will be
taken.
Default:
12.16.1. AQUDIMS 1150

maximum number of lines of numerical aquifer data entered via keyword AQUNUM
(see 12.16.11) 1;
maximum number of lines of connection data for numerical aquifers entered via
keyword AQUCON (see 12.16.12) 1;
maximum number of influence tables for Carter-Tracy aquifers, entered via the key-
word AQUTAB (see 12.16.9) 1;
maximum number of rows in a Carter-Tracy aquifer influence table 36;
maximum number of analytic aquifers in the model 1;
maximum number of grid blocks connected to any single analytic aquifer 1.
maximum number of aquifer lists 0.
maximum number of analytic aquifers in any single aquifer list 0.
Example
AQUDIMS
0 0 6 100 100 100 0 0 /
12.16.1. AQUDIMS 1151

12.16.2 AQUFLUX


Section
Defines constant flux from aquifer. This keyword may be used in schedule section. Hav-
ing defined aquifer, connections of grid blocks and aquifer should be defined by means of
AQUANCON (see 12.16.10).
Formula of water inflow from the aquifer 2.97.
Below the following data should be input for each aquifer (terminated with a slash /):
1. aquifer number (positive number),
2. aquifer flux, inflow rate per unit area (METRIC: sm3 /day/m2 , FIELD: stb/day/ f t 2 ),
3. initial salt concentration in the aquifer (METRIC: kg/sm3 , FIELD: lb/stb) (this pa-
rameter can be entered only if Brine option is active BRINE (see 12.1.58)).
4. temperature in aquifer (METRIC: C, FIELD: F) (this parameter is used only if

temperature TEMP (see 12.1.60) or thermal option THERMAL (see 12.1.50) is used),
5. pressure in aquifer at datum depth (METRIC: barsa, FIELD: psia). This parameter
is used with temperature (specified via previous parameter) only if thermal option
THERMAL (see 12.1.50) is used.
Example
AQUFLUX
1 10 /
2 20 /
/
In this example two aquifers are set, inflow per square meter from first aquifer will be
equal to 10 cubic meters a day, and from second aquifer 20 square meters. To calculate
resulting inflow to grid block, simulator will multiply this number on aquifer influx coefficient
multiplier, defined in AQUANCON (see 12.16.10), and then by block face area.
12.16.2. AQUFLUX 1152

12.16.3 AQUCHWAT


Section
The keyword specifies the data for constant head/pressure water aquifer.
Having defined aquifer, connections of grid blocks and aquifer should be defined by means
of AQUANCON (see 12.16.10).
An arbitrary number of data lines could be entered, terminated with a slash / (each line
specifies one aquifer). All data should be terminated with a final slash /.
1. aquifer number;
2. datum depth da (METRIC: m, FIELD: f t );
3. data format of the 4-th parameter of the keyword:
PRESSURE;
HEAD.
4. the following variants are possible:
pressure in the aquifer pa at the datum depth if 3-rd parameter is PRESSURE

(METRIC: bars, FIELD: psi);
head in the aquifer H at the datum depth if 3-rd parameter is HEAD (METRIC:
m, FIELD: f t ).
In this case H is calculated to pressure via the formula pa = g(H da ) +
1atmosphere, where density is taken from the table, specified via 6-th param-
eter of the keyword;
5. aquifer productivity index J (total influx rate per unit pressure difference) (METRIC:
sm3 /day/bars, FIELD: stb/day/psi);
6. PVT table number for water (PVTW (see 12.5.5));
12.16.3. AQUCHWAT 1153

8. minimum pressure if 3-rd parameter is PRESSURE (METRIC: barsa, FIELD: psia)

or minimum head if 3-rd parameter is HEAD (METRIC: m, FIELD: f t ). IGNORED.
This is an Eclipse compatibility field.
9. maximum pressure if 3-rd parameter is PRESSURE (METRIC: barsa, FIELD: psia)

or maximum head if 3-rd parameter is HEAD (METRIC: m, FIELD: f t ). IGNORED.
This is an Eclipse compatibility field.
10. IGNORED. This is an Eclipse compatibility field.
11. minimum value of allowed flow per aquifer connection (METRIC: sm3 /day, FIELD:
stb/day). IGNORED. This is an Eclipse compatibility field.
12. maximum value of allowed flow per aquifer connection (METRIC: sm3 /day, FIELD:
stb/day). IGNORED. This is an Eclipse compatibility field.

temperature TEMP (see 12.1.60) or thermal option THERMAL (see 12.1.50) is used).
Default:
data format of the 4-th parameter of the keyword PRESSURE;
PVT table number for water (PVTW (see 12.5.5)) 1;
initial salt concentration in the aquifer (METRIC: kg/sm3 , FIELD: lb/ f t 3 ) 0.
Example
AQUCHWAT
1 2400 'PRESSURE' 90 0.00002 1 /
/
12.16.3. AQUCHWAT 1154

12.16.4 AQUFET


Section
The keyword is used to specify properties of Fetkovich aquifer and its connections with
grid blocks. The keyword is used to connected only one reservoir face with one aquifer
(if an aquifer is connected to several faces use the keywords AQUFETP (see 12.16.6),
AQUANCON (see 12.16.10)).
Below the following data should be input (terminated with a slash /):
1. datum depth (METRIC: m, FIELD: f t ),
2. initial pressure on datum depth (METRIC: bars, FIELD: psi),
3. initial water volume in aquifer (METRIC: sm3 , FIELD: stb),
4. total aquifer compressibility (cumulative compressibility of water and rock) (METRIC:

1/bars, FIELD: 1/psi),
5. aquifer productivity index (METRIC: sm3 /day/bars, FIELD: stb/day/psi),
6. number of PVTW (see 12.5.5) table, describing properties of water in aquifer,
7. i-coordinate of start of cube connected with aquifer,
8. i-coordinate of end of cube connected with aquifer,
9. j -coordinate of start of cube connected with aquifer,
10. j -coordinate of end of cube connected with aquifer,
11. k -coordinate of start of cube connected with aquifer,
12. k -coordinate of end of cube connected with aquifer,
13. index denoting which face will be connected with aquifer; possible values I (face
I = 1), I+ (face I = NX ), J (face J = 1), J+ (face J = NY ), K (face K = 1),
K+ (face I = NZ ) (NX , NY , NZ are set via DIMENS (see 12.1.25)),
12.16.4. AQUFET 1155

Default:
initial salt concentration in the aquifer 0kg/sm3 .
The aquifer is connected with grid blocks that are within the specified cube and have no
active neighboring block on the side facing the aquifer.
The aquifer productivity index is apportioned between the connecting grid blocks in
proportion to the area of their connecting faces.
Example
AQUFET
5800 2500 1.7E7 1.0E-6 20.0 1 1 7 1 7 3 3 'K-'
/
12.16.4. AQUFET 1156

12.16.5 AQUOPTS


Section
The keyword set preferences of analytical aquifers calculation. The following parameters
1. number of aquifer;
2. aquifer calculation option:
type of numerical scheme, which is used to calculate aquifers effect on reservoir:

FI fully implicit scheme;
FI_ELIM_AQ_VAR fully implicit scheme. For this option numerical value
can be specified percent of aquifer blocks, which will be calculated by fully
implicit method (see the following parameter description);
PSEUDO_FI pseudo-implicit scheme. Note: selection between FI and
PSEUDO_FI is important only for Fetkovich and Carter-Tracy aquifers,
AQUCHWAT (see 12.16.3) and AQUFLUX (see 12.16.2) aquifers are always
calculated by fully implicit method.
restriction for flow from reservoir to aquifer:
OUTFLOW_S flow of mobile water from reservoir to aquifer is allowed
only;
OUTFLOW_S_SMOOTH flow of mobile water from reservoir to aquifer is
allowed only. If water in a connected block becomes immobile, then flow is
smoothed;
OUTFLOW_RP water RP is being to account at calculation of flow from
reservoir to aquifer.
capillary pressure account:
PCOW_IGNORE capillary pressure values are not accounted during aquifer
flow calculation;
PCOW_CONSIDER capillary pressure values are accounted during aquifer
flow calculation. Note: it is important only for Fetkovich, Carter-Tracy and
AQUCHWAT (see 12.16.3) aquifer types.
3. percent of aquifer blocks, which will be calculated by fully implicit method. This value
should obtain to interval (0; 100).
12.16.5. AQUOPTS 1157

In one data line only one option of aquifer calculation can be specified. If it is necessary
to specify several option for one aquifer, then use several line (see the example). Only one
option from each group can be specified for one aquifer.
slash /.
Default:
restriction for flow from reservoir to aquifer: in E100/E300 models for Fetkovich,
Carter-Tracy and AQUCHWAT (see 12.16.3) aquifers OUTFLOW_S option is used by
default. In MORE models for these aquifers OUTFLOW_RP option is used by default;
capillary pressure account: in E100/E300 models for Fetkovich and AQUCHWAT (see
12.16.3) aquifers capillary pressures are accounted, for Carter-Tracy they are not ac-
counted. For MORE models capillary pressures are not accounted.
percent of aquifer blocks, which will be calculated by fully implicit method: 0.
Example
AQUOPTS
1 FI /
2 FI 5.5 /
/
In the example the first aquifer is calculated by fully implicit scheme. Percent of the 2-nd
aquifer blocks which will be calculated by fully implicit scheme is 5.5.
Example
AQUOPTS
1 FI /
1 OUTFLOW_RP /
2 OUTFLOW_S_SMOOTH /
/
In the example for aquifer 1 two options are set: FI and OUTFLOW_RP.
12.16.5. AQUOPTS 1158

12.16.6 AQUFETP


Section
Defines inflow from aquifer calculated according to Fetkovich model. Having defined
aquifer, connections of grid blocks and aquifer should be defined by means of AQUANCON
(see 12.16.10).
Below the following data should be input:
4. initial water volume in aquifer (METRIC: sm3 , FIELD: stb),
5. total aquifer compressibility (cumulative compressibility of water and rock) (1/bars),
6. aquifer productivity index (METRIC: sm3 /day/bars, FIELD: stb/day/psi),

Each data line should be terminated with a slash /. All data should be terminated with a
final slash /.
Default:
Example
AQUFETP
1 2000 250 100000 1e-5 20 1/
2 2000 250 100000 1e-5 40 1 /
/
12.16.6. AQUFETP 1159

In this example two aquifers are defined, flow per unit area from second aquifer will be
twice higher because it has twice higher productivity index, for the same volume (100000
m 3 ) and same initial pressure on depth 2000 m, equal to 250 bars.
12.16.6. AQUFETP 1160

12.16.7 AQANTRC


Section
The keyword specifies initial tracer concentrations for analytic aquifers (keywords
AQUFET (see 12.16.4), AQUFETP (see 12.16.6), AQUCT (see 12.16.8), AQUFLUX (see
12.16.2)).
An arbitrary data lines terminated with a slash / could be entered. All data should be
terminated with a final slash /.
1. aquifer number (positive value),
2. tracer name (tracer should be defined to exist in the water phase TRACER (see 12.7.1)),
3. initial tracer concentration in the aquifer (from 0 to 1).
Default: if tracer isnt specified its concentration is 0.
Example
AQANTRC
1 A1 0.3 /
/
Initial tracer A1 concentration in the aquifer 1 is 30%.
12.16.7. AQANTRC 1161

12.16.8 AQUCT


Section
Defines inflow from aquifer calculated according to Carter Tracy model. Having defined
aquifer, connections of grid blocks and aquifer should be defined by means of AQUANCON
(see 12.16.10).
Dimensions for aquifer are set via AQUDIMS (see 12.16.1).
Below the following data should be input:

4. aquifer permeability (mD),
5. aquifer porosity,
6. total aquifer compressibility (cumulative compressibility of water and rock) (METRIC:

1/bars, FIELD: 1/psi),
7. reservoir outer radius, i.e. aquifer inner radius (METRIC: m, FIELD: f t ),
8. aquifer thickness (METRIC: m, FIELD: f t ),
9. angle of influence (angle subtended by mutual boundary of reservoir and aquifer),

degrees,
11. AQUTAB (see 12.16.9) table number, controlling dependence of pressure on dimen-
sionless time,
rameter can be entered only if Brine option is active BRINE (see 12.1.58)),

12.16.8. AQUCT 1162

Each data line should be terminated with a slash /. All data should be terminated with a
final slash /.
Default:
aquifer porosity: 1.0;
angle of influence: 360 degrees;
PVTW (see 12.5.5) table number: 1;
AQUTAB (see 12.16.9) table number: 1;
Example
AQUCT
1 2000 250 100 0.3 1e-5 1000 100 90 1 2* /
2 2000 250 100 0.3 1e-5 1000 100 45 1 2* /
/
In this example two aquifers are defined, with different angle (90 and 45 degrees), same
porosity and permeability (0.3 and 100), compressibility (1e 5), thickness (100), radius
(1000) and same initial pressure on depth 2000 m, equal to 250 bars.
12.16.8. AQUCT 1163

12.16.9 AQUTAB


Section
The keyword defines an influence function tables for Carter-Tracy aquifers. (the number
of tables in set via AQUDIMS (see 12.16.1)). Each table should be terminated with a slash /.
The first table cannot be modified (default table). First table is specified and reserved for
the constant terminal rate case for an infinite aquifer as given by Van Everdingen and Hurst.
Tables entered via this keyword are numbered from 2.
1. dimensionless time (positive and increasing down the column),
2. corresponding dimensionless pressure (positive).
Example
AQUTAB
0.012 0.167
0.045 0.223
0.1 0.3
0.17 0.38
0.2 0.45
0.27 0.48
0.3 0.5
0.4 0.58
0.5 0.62
0.6 0.68
0.7 0.73
/
12.16.9. AQUTAB 1164

12.16.10 AQUANCON


Section
Used to define connections of analytic aquifers (AQUFLUX (see 12.16.2), AQUFETP

(see 12.16.6), AQUCT (see 12.16.8), AQUFET (see 12.16.4)) and grid blocks. User inputs
table, each line defines cube of grid blocks. Each block will be connected with analytic
aquifer by the face indicated for whole cube. The data should be terminated with a slash /.
The following data is input:
1. aquifer number,
in direction opposite to X axis direction), I+ (face in direction parallel to X axis),
J, J+ (the same but for axis Y ), K, K+ (the same but for axis Z ),
9. aquifer influx coefficient, determines what fraction of total outflow from aquifer will
flow into current block; for constant flux aquifer defined by AQUFLUX (see 12.16.2)
keyword, this coefficient is not used. By default it is equal to area of face connected
with aquifer. If influx coefficient is specified several times for the same cell, the values
are summed. If a zero influx coefficient is specified, this makes cell influx coefficient
equal to zero,
10. influx coefficient multiplier; for constant flux aquifer, specified by AQUFLUX (see
12.16.2) keyword, when multiplier is specified, grid block face area changes, being
multiplied on it,
11. whether connections from faces, connected with active blocks, are allowed; possible
values YES, NO. By default grid block will be connected with aquifer only if its
face is connected with inactive block or if block has no neighbours from this face.
Default:
12.16.10. AQUANCON 1165

aquifer influx coefficient: grid block area,
influx coefficient multiplier: 1,
allow connections from faces connected with inactive blocks: NO
Example
DIMENS
10 17 3
/
...
AQUANCON
1 1 10 1 1 1 3 J- 3* /
1 1 1 1 17 1 3 I- 3* /
/
In this example connections with aquifer number 1 are specified. Two side faces of
reservoir will have water influx, and cells on reservoir arris will have double inflow, because
they all have two faces connected, in I direction and in J direction.
12.16.10. AQUANCON 1166

12.16.11 AQUNUM


Section
The keyword assigns a numerical aquifer to a block (aquifer is set via the keyword
AQUCON (see 12.16.12)). Each line is a grid block representing a numerical aquifer. Each
line should be terminated with a slash /. All data should be terminated with a final slash /.
One line should consist of the following parameters:
1. aquifer number,
2. i-coordinate of grid block representing aquifer;
3. j -coordinate of grid block representing aquifer;
4. k -coordinate of grid block representing aquifer;
5. cross-section area (METRIC: m2 , FIELD: f t 2 ) (may be larger than real cross-section

area of the block i jk );
6. length (METRIC: m, FIELD: f t ) (may be larger than real length of the block i jk );
7. porosity;
8. permeability (mD);
9. aquifer depth (METRIC: m, FIELD: f t ) (may be larger than real depth of the block
i jk );
10. initial pressure (METRIC: barsa, FIELD: psia);
11. PVT table number for aquifer;
12. saturation table number for aquifer.
Default:
porosity value for block i jk ;
aquifer depth value for block i jk ;
PVT table number for aquifer PVTNUM (see 12.4.2) value for block i jk ;
saturation table number for aquifer PVTNUM (see 12.4.2) value for block i jk .
12.16.11. AQUNUM 1167

Example
AQUNUM
1 1 1 5 120000 18500 1* 350.0 4* /
1 1 1 6 120000 18500 1* 350.0 4* /
/
In this example a two-block aquifer is specified, with default porosity, depth, initial
pressure, PVT table number and saturation table number.
12.16.11. AQUNUM 1168

12.16.12 AQUCON


Section
Used to define connections of numerical aquifers (AQUNUM (see 12.16.11)) and grid
blocks. User inputs table, each line defines cube of grid blocks. Each block will be connected
with numerical aquifer by the face indicated for whole cube. The data should be terminated
with a slash /.
The following data is input:
1. aquifer number,
in direction opposite to X axis direction), I+ (face in direction parallel to X axis),
J, J+ (the same but for axis Y ), K, K+ (the same but for axis Z ),
9. transmissibility multiplier (the calculated transmissibility will be multiplied by a user

defined multiplier),
10. transmissibility option (0 or 1) The transmissibility between the numerical aquifer and
grid block is calculated via the formula:
CDARCY
T=
( T1a ) + ( T1c )
Tc component of transmissibility from the grid block;

Ta component of transmissibility from the aquifer (the formula depends on this pa-
rameter of the keyword).
Kc Ac NT G
Tc =
Dc
12.16.12. AQUCON 1169

Kc block permeability in the appropriate direction,

Ac block face area,
NT G block net-to-gross ratio if the cell face X or Y,
Dc distance from the block center the face.
If 0 option:
Ka Aa
Ta =
Da
Ka aquifer permeability (entered via AQUNUM (see 12.16.11)),
Aa aquifer area (entered via AQUNUM (see 12.16.11)),
Da half of aquifer length (entered via AQUNUM (see 12.16.11)).
If 1 option:
Ka Ac
Ta =
Da
11. whether connections from faces, connected with active blocks, are allowed; possible
values YES, NO. By default grid block will be connected with aquifer only if its
face is connected with inactive block or if block has no neighbours from this face.
Default:
transmissibility multiplier 1,
transmissibility option 0,
allow connections from faces connected with inactive blocks: NO.
Example
AQUCON
1 4 4 1 1 2 6 I+ 1.0 /
/
In this example connections with aquifer number 1 are specified. The following blocks
are connected: 4-th column of X-Z section in the layers 2-6. The face I+ connections will
be made if the corresponding blocks in column 5 are inactive or model size in X-direction is
4 blocks (is specified via first parameter of DIMENS (see 12.1.25)).
12.16.12. AQUCON 1170

Example
AQUCON
1 1 28 59 59 1 6 J+ 1.0 0 /
1 25 25 20 21 1 6 I+ 1.0 1 /
1 26 26 22 24 1 6 I+ 1.0 1 /
1 25 25 25 27 1 6 I+ 0.65 1 /
1 24 24 28 29 1 6 I+ 0.65 1 /
1 23 23 30 42 1 6 I+ 0.65 1 /
1 23 23 38 42 1 6 I+ 1.0 1 /
1 24 24 43 46 1 6 I+ 0.65 1 /
1 25 25 47 52 1 6 I+ 0.65 1 /
1 26 26 53 57 1 6 I+ 0.65 1 /
1 27 27 58 59 1 6 I+ 0.65 1 /
2 22 22 15 16 44 45 I+ 1.0 1 /
2 23 23 17 17 44 45 I+ 1.0 1 /
2 24 24 18 19 44 45 I+ 1.0 1 /
2 21 21 12 14 44 45 I+ 1.0 1 /
2 26 26 20 23 44 45 I+ 1.0 1 /
/
In this example connections with aquifer number 1 and number 2 are specified.
12.16.12. AQUCON 1171

12.16.13 AQUGP


Section
The keyword defines geometry of aquifer connection to reservoir. Properties for sev-
eral aquifers can be specified. Each aquifers properties are specified in separate line. The
1. aquifer id;
2. aquifers connection type:
DEPTH to connect aquifer on specified depth_value (the depth value is set

by the 3-rd parameter). Algorithm of connection is the following: for each block
minimal and maximal depth of its tops are defined (dmin and dmax ). Then block
is connected if depth_value [dmin , dmax ]. Links of K- direction are never con-
nected, links of the other directions are connected only if connecting block doesnt
have active neighbor one of the same direction. If aquifer is set by AQUFLUX
(see 12.16.2) then productivity indexes are equal to connection area. For the
other analytical aquifer types productivity indexes are evaluated with respect to
weighting type (see 4-th parameter);
BOTTOM aquifer will be connected to the reservoir bottom: only blocks with
coordinate k which is equal to Nz (see keyword DIMENS (see 12.1.25)) will be
connected. Connection will be performed only by links of K+ direction. Produc-
tivity indexes are equal to aquifer connection area;
BOUNDARY aquifer will be connected to the reservoir boundary: only blocks
which i coordinate is equal to 1 or Nx or coordinate j is equal to 1 or Ny
(see keyword DIMENS (see 12.1.25)). Connection is performed by links with
I+, I-, J+, J- directions only. If aquifer is set by AQUFLUX (see 12.16.2) then
productivity indexes are equal to connection area. For the other analytical aquifer
types productivity indexes are equal to connection area considering NTG (see
12.2.25);
RESBND aquifer will be connected to the real reservoir boundary (modified
BOUNDARY option): block is connected only if it is the first active block near
grid boundary. Connection is performed by links with I+, I-, J+, J- directions only.
Productivity indexes are defined the same way as for BOUNDARY connection
type.
3. aquifer connection depth. This parameter is used only for DEPTH connection type and
it must be specified;
12.16.13. AQUGP 1172

4. equil region number, block of which are allowed to connect to aquifer. This parameter
is used only for DEPTH connection type.
5. weighting type to calculate blocks productivity indexes for DEPTH connection type:
EVEN all productivity indexes are equal to 1;

AREA productivity indexes are equal to connection area considering NTG (see
12.2.25);.
Each data line should be ended by the symbol /.The data should be terminated with a
slash /.
Default:
equil region number: all region;
weighting type to calculate blocks productivity indexes: EVEN.
Example
AQUGP
1 RESBND /
/
12.16.13. AQUGP 1173

12.16.14 HMMLCTAQ


Section
This keyword specifies modifiers for Carter-Tracy aquifer (defined via AQUCT (see
12.16.8)). This keyword can be used for history matching.
An arbitrary number of lines can be specified. Each data line should be terminated with
1. aquifer number (1-st parameter of AQUCT (see 12.16.8)),
2. multiplier on aquifer permeability,
3. multiplier on aquifer angle of influence (angle subtended by mutual boundary of reser-

voir and aquifer),
4. multiplier on aquifer depth.
Default:
multiplier on aquifer permeability 1,
multiplier on aquifer angle of influence (angle subtended by mutual boundary of reser-

voir and aquifer) 1,
multiplier on aquifer depth 1.
Example
HMMLCTAQ
1 3.0 1.7 /
2 3.0 1.7 /
/
12.16.14. HMMLCTAQ 1174

12.16.15 HMMLFTAQ


Section
This keyword specifies modifiers for Fetkovich aquifer (defined via AQUFET (see
12.16.4) (or AQUFETP (see 12.16.6) and AQUANCON (see 12.16.10))). This keyword
can be used for history matching.
An arbitrary number of lines can be specified. Each data line should be terminated with
1. aquifer number (1-st parameter of AQUFETP (see 12.16.6)),
2. multiplier on initial volume of water in the aquifer,
3. multiplier on aquifer productivity index,
4. multiplier on aquifer depth.
Default:
multiplier on initial volume of water in the aquifer 1,
multiplier on aquifer productivity index 1,
multiplier on aquifer depth 1.
Example
HMMLFTAQ
1 2.5 1.7 /
2 1.5 1.7 /
/
12.16.15. HMMLFTAQ 1175

12.17. Data output tNavigator-4.2
12.17 Data output
12.17. Data output 1176

12.17.1 SUMMARY


Section
REGIONS SOLUTION x SUMMARY SCHEDULE
This keyword defines the beginning of the section which contains the list of the data that
will be output to the files with calculation results. A list of all available parameters is in this
section below.
Binary files *.UNSMRY, *.SMSPEC will be saves corresponding to the keywords that
are specified in this section.
For console version: simulator should run with options -u.

All main parameters can be saved using the command:
Example
SUMMARY
ALL
ALL the following parameters will be saved:
FOPR GOPR WOPR FOPT GOPT WOPT

FOIR GOIR WOIR FOIT GOIT WOIT
FWPR GWPR WWPR FWPT GWPT WWPT
FWIR GWIR WWIR FWIT GWIT WWIT
FGPR GGPR WGPR FGPT GGPT WGPT
FGIR GGIR WGIR FGIT GGIT WGIT
FVPR GVPR WVPR FVPT GVPT WVPT
FVIR GVIR WVIR FVIT GVIT WVIT
FWCT GWCT WWCT FGOR GGOR WGOR
FWGR GWGR WWGR
WBHP WTHP WPI
FOIP FOIPL FOIPG
FWIP
FGIP FGIPL FGIPG FPR
FAQR AAQR FAQT AAQT FAQRG FAQTG
There is a list of all available in SUMMARY section parameters below.
Notations:
(H) historical value.
12.17.1. SUMMARY 1177

in res.c. in reservoir conditions.
Oil production and injection parameters.
Parameter Field Region Group Well Connection Completion

Oil rate FOPR ROPR GOPR WOPR COPR
Oil rate (H) FOPRH GOPRH WOPRH
Free oil rate FOPRF GOPRF WOPRF
Solution oil rate FOPRS GOPRS WOPRS
Oil production poten- FOPP WOPP
tial
Oil total FOPT ROPT GOPT WOPT COPT COPTL
WOPTL
Oil total (H) FOPTH GOPTH WOPTH
Free oil total FOPTF ROPTF GOPTF WOPTF COPTF
Solution oil total FOPTS GOPTS WOPTS COPTS
Oil total at n-th separa- FOnPR GOnPR WOnPR
tor stage
Oil injection rate FOIR ROIR GOIR WOIR
Oil injection rate (H) FOIRH GOIRH WOIRH
Oil injection total FOIT ROIT GOIT WOIT COIT COITL
WOITL
Oil injection total (H) FOITH GOITH WOITH
Oil flow rate COFR COFRL
WOFRL
COPRL
WOPRL
Free oil flow rate COFRF
Solution oil flow rate COFRS
12.17.1. SUMMARY 1178

Water production and injection parameters.

Water rate FWPR RWPR GWPR WWPR CWPR
Water rate (H) FWPRH GWPRH WWPRH
Water production po- FWPP WWPP
tential
Water total FWPT RWPT GWPT WWPT CWPT CWPTL
WWPTL
Water total (H) FWPTH GWPTH WWPTH
Water injection rate FWIR RWIR GWIR WWIR CWIR CWIRL
WWIRL
Water injection rate FWIRH GWIRH WWIRH
(H)
Water injection poten- FWPI WWPI
tial
Water injection total FWIT RWIT GWIT WWIT CWIT CWITL
WWITL
Water injection total FWITH GWITH WWITH
(H)
Water flow rate CWFR CWFRL
WWFRL
CWPRL
WWPRL
12.17.1. SUMMARY 1179

Tracer production and injection parameters.
Parameter Well
Traccer injection concentration WTIC
Traccer production concentration WTPC
Traccer injection rate WTIR
Traccer production rate WTPR
Traccer injection total WTIT
Traccer production total WTPT
Polymer injection concentration WCIC
Salt injection concentration WSIC
Alkaline injection concentration WTICALK
Surfactant injection concentration WTICSUR
Traccer A injection concentration WTICA
Plymer production concentration WCPC
Salt production concentration WSPC
Alkaline production concentration WTPCALK
Surfactant production concentration WTPCSUR
Traccre A production concentration WTPCA
Polymer injection WCIR
Salt injection WSIR
Alkaline injection WTIRALK
Surfactant injection WTIRSUR
Tracer A injection WTIRA
Polymer production WCPR
Salt production WSPR
Alkaline production WTPRALK
Surfactant production WTPRSUR
Traccer A production WTPRA
Polymer injection total WCIT
Salt injection total WSIT
Alkaline injection total WTITALK
Surfactant injection total WTITSUR
Traccer A injection total WTITA
Polymer production total WCPT
Salt production total WSPT
Alkaline production total WTPTALK
Surfactant production total WTPTSUR
Traccer A production total WTPTA
12.17.1. SUMMARY 1180

Gas production and injection parameters.

Gas rate FGPR RGPR GGPR WGPR CGPR
Gas rate (H) FGPRH GGPRH WGPRH
Free gas rate FGPRF RGPRF GGPRF WGPRF
Solution gas rate FGPRS GGPRS WGPRS
Wet gas rate WWGPR
Gas production poten- FGPP WGPP
tial
Gas total FGPT RGPT GGPT WGPT CGPT CGPTL
WGPTL
Gas total (H) FGPTH GGPTH WGPTH
Free gas total FGPTF RGPTF GGPTF WGPTF CGPTF
Solution gas total FGPTS GGPTS WGPTS CGPTS
Wet gas total WWGPT
Gas injection rate FGIR RGIR GGIR WGIR CGIR CGIRL
WGIRL
Gas injection rate (H) FGIRH GGIRH WGIRH
Gas injection rate for FGLIR GGLIR WGLIR
gas lift (ALQ)
Gas injection potential FGPI WGPI
Gas injection total FGIT RGOT GGIT WGIT CGIT CGITL
WGITL
Gas injection total (H) FGITH GGITH WGITH
Gas total at n-th sepa- FGnPR GGnPR WGnPR
rator stage
Gas flow rate CGFR CGFRL
WGFRL
CGPRL
WGPRL
Free gas flow rate CGFRF
Solution gas flow rate CGFRS
12.17.1. SUMMARY 1181

Liquid production and injection parameters.
Parameter Field Group Well Connection Completion

Liquid rate FLPR GLPR WLPR CLPR CLPRL
WLPRL
Liquid rate (H) FLPRH GLPRH WLPRH
Liquid rate in res. c. FVPR GVPR WVPR
Liquid total FLPT GLPT WLPT CLPT CLPTL
WLPTL
Liquid total (H) FLPTH GLPTH WLPTH
Liquid total in res. c. FVPT GVPT WVPT CVPT CVPTL
WVPTL
Liquid injection rate FWIR GWIR WWIR CWIR
Liquid injection rate FWIRH GWIRH WWIRH
(H)
Liquid injection rate in FVIR GVIR WVIR
res. c.
Liquid injection total FWIT GWIT WWIT CWIT
Liquid injection total FWITH GWITH WWITH
(H)
Liquid injection total in FVIT GVIT WVIT CVIT CVITL
res.c. WVITL
Liquid flow rate CLFR CLFRL
WLFRL
Liquid flow rate in res. CVFR CVFRL
c. WVFRL
12.17.1. SUMMARY 1182

Pressure.
Parameter Field Region Group Well Connection Block

Pressure FPR RPR GPR CPR BPR
Bottom hole pressure WBHP
Bottom hole pressure WBHPH
(H)
Tubing head pressure WTHP
Tubing head pressure WTHPH
(H)
Pressure in the block WBPH
with first well connec-
tion (H)
1-point pressure aver- WBP
age (WPAVE)
4-point pressure aver- WBP4
age (WPAVE)
age (WPAVE)
age (WPAVE)
Pore volume.
Parameter Field Region Block
Pore volume in res. c. RRPV
Fluids-in-place output.
Parameter Notation
Output of fluids-in-place at surface (separator) conditions SFIP
Output of fluids-in-place at reservoir conditions RFIP
12.17.1. SUMMARY 1183

Oil in regions and grid blocks. Oil recovery efficiency.

Average oil saturation ROSAT
Oil potential FPPO RPPO
Oil-in-place (liquid and wet gas) FOIP ROIP
Oil-in-place (liquid phase) FOIPL ROIPL
Oil-in-place (gas phase) FOIPG ROIPG
(Initial Oil-in-place-current)/initial FOE ROE
(Initial Oil-in-place-current)/Initial mobile oil FOEIG ROEIG
with respect to Gas
(Initial Oil-in-place-current)/Initial mobile oil FOEIW ROEIW
with respect to Water
Oil production from wells/Initial mobile oil FOEWW ROEWW
with respect to Water
Oil production from region ROP
Inter-region oil flow total ROFT
Water in regions and grid blocks.

Average water saturation RWSAT
Water potential FPPW RPPW
Water-in-place FWIP RWIP
Inter-region water flow total RWFT
Water production from region (minus injection RWP
from wells and aquifers)
12.17.1. SUMMARY 1184

Gas in regions and grid blocks.

Average gas saturation RGSAT
Gas potential FPPG RPPG
Gas-in-place (liquid and gas phase) FGIP RGIP
Gas-in-place (liquid phase) FGIPL RGIPL
Gas-in-place (gas phase) FGIPG RGIPG
Inter-region gas flow total RGFT
Watercut, gas-oil ratio, oil-gas ratio, water-gas ratio, gas-liquid factor.
Parameter Field Group Well Connection Completion

Watercut FWCT GWCT WWCT CWCT CWCTL
WWCTL
Watercut (H) FWCTH GWCTH WWCTH
Gas-oil ratio FGOR GGOR WGOR CGOR CGORL
WGORL
Gas-oil ratio (H) FGORH GGORH WGORH
Oil-gas ratio FOGR GOGR WOGR COGR COGRL
WOGRL
Oil-gas ratio (H) FOGRH GOGRH WOGRH
Water-gas ratio FGLR GGLR WGLR CGLR CGLRL
WGLRL
Water-gas ratio (H) FGLRH GGLRH WGLRH
Gas-liquid factor WWGR CWGR CWGRL
WWGRL
Gas-liquid factor (H) WWGRH
Aquifer.
Parameter Field Aquifer

Aquifer influx rate FAQR AAQR
Cumulative aquifer influx FAQT AAQT
Aquifer pressure (for Fetkovich aquifer) AAQP
Aquifer pressure (at current time step) FAQP
12.17.1. SUMMARY 1185

Wells and groups.
Parameter Field Group

Total number of producers FMWPT GMWPT
Total number of injectors FMWIT GMWIT
Number of injectors currently working FMWIN GMWIN
Number of producers currently working FMWPR GMWPR
Number of abandoned producers FMWPA GMWPA
Number of abandoned injectors FMWIA GMWIA
Well and connection parameter.
Parameter Region Well Connection

Well artificial lift quantity (ALQ) WALQ
Well control WMCTL
Well status WSTAT
Productivity Index of wells preferred phase WPI
Oil phase PI WPIO
Gas phase PI WPIG
Water phase PI WPIW
Efficiency factor GEFF WEFF
Blocking factor for generalized pseudo- pres- CDBF
sure method
D-factor for flow dependent skin factor CDFAC
Connection transmissibility factor CTFAC
Well working time at current time step WWT
Well working time at current time step (H) WWTH
Well working time from start to current time WWTT
step
Well working time from start to current time WWTTH
step (H)
12.17.1. SUMMARY 1186

Multisegment wells.
Parameter Segment
Segment oil flow rate SOFR
Segment water flow rate SWFR
Segment gas flow rate SGFR
Segment liquid flow rate SLPR
Segment pressure SPR
Segment pressure drop SPRD
Segment pressure drop due to hydrostatic head SPRDH
Segment pressure drop due to friction SPRDF
Segment pressure drop due to acceleration head SPRDA
Segment oil flow velocity SOFV
Segment gas flow velocity SGFV
Segment water flow velocity SWFV
Segment oil holdup fraction SOHF
Segment water holdup fraction SWHF
Segment gas holdup fraction SGHF
Segment watercut SWCT
Segment gas oil ratio SGOR
Segment oil gas ratio SOGR
Segment gas water ratio SGWR
Segment water gas ratio SWGR
Segment water oil ratio SWOR
Segment oil water ratio SOWR
Segment gas liquid ratio SGLR
Segment liquid gas ratio SLGR
12.17.1. SUMMARY 1187

Parameters for compositional models E300 type.
Parameter Field Group Well Connection

Energy injection rate WEIR
Energy rate WENR
Steam quality WSQU
Well tubing head temperature WTHT
Hydrocarbon Component FCMPR GCMPR WCMPR
Molar Production Rates
Hydrocarbon Component FCMPT GCMPT WCMPT
Molar Production Totals
Hydrocarbon component mo- FCOMR GCOMR WCOMR
lar rates in the oil phase
Hydrocarbon component mo- FCGMR GCGMR WCGMR
lar rates in the gas phase
Hydrocarbon component mo- WCOMT
lar totals in the oil phase
Hydrocarbon component mo- WCGMT
lar totals in the gas phase
Liquid mole fraction FXMF GXMF WXMF
Vapor mole fraction FYMF GYMF WYMF
Total mole fraction FZMF GZMF WZMF
12.17.1. SUMMARY 1188

12.17.2 RPTMAPD/RPTGRAPHD


Section
This keyword allows to manage a record of calculated maps (RPTMAPD) and graphs
(RPTGRAPHD) to the hard disc (record data only for time steps selected by the user). Thus,
the amount of data written to disk, can be reduced.
After the keyword the dates should be specified (for which maps and graphs should be
recorded on hard disc). Dates should be in the format DD MONTH YYYY. MONTH can be
one of the following: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC,
also JLY.
Data on first and last time step is always recorded.
Reducing of number of time steps to record Map data leads to reducing of the size of
the file MODEL NAME_outsol_ts_maps.res.
Reducing of number of time steps to record Graph data leads to reducing of the size
of the file MODEL NAME_conn.res (the biggest file with graph results), MODEL
NAME_aquifer.res, MODEL NAME_fip.res, MODEL NAME_well.res etc.
1. Keywords to record data in specified dates RPTMAPD (see 12.17.2), RPTGRAPHD

(see 12.17.2).
2. Keywords to record data in selected time intervals RPTMAPT (see 12.17.3), RPT-
GRAPHT (see 12.17.3).
3. Keywords to record data only for first and last time steps RPTMAPL (see 12.17.4),
RPTGRAPHL (see 12.17.4).
In graphical interface in the window with model one should choose "Reload with New
Recording Options". Choose "As in RPTMAPD and RPTGRAPHD keywords".
12.17.2. RPTMAPD/RPTGRAPHD 1189

Example
SUMMARY
RPTMAPD
01 AUG 1995
01 SEP 1995
01 OCT 1995
01 NOV 1997
01 DEC 1997
01 JAN 1998
/
RPTGRAPHD
01 AUG 1995
01 SEP 1995
01 OCT 1995
01 NOV 1997
01 DEC 1997
01 JAN 1998
/
In this example the calculated data for maps and graphs will be recorded on disc for the
dates: 1 august 1995, 1 september 1995, 1 october 1995, 1 november 1997, 1 december 1997,
1 january 1998.
12.17.2. RPTMAPD/RPTGRAPHD 1190

12.17.3 RPTMAPT/RPTGRAPHT


Section
This keyword allows to manage a record of calculated maps (RPTMAPT) and graphs
(RPTGRAPHT) to the hard disc (record data only for time steps selected by the user). Thus,
After the keyword the time unit should be entered and an array, that defines the time
intervals to record the data. If the field development history is longer then the sum of all
specified time intervals then the results will be recorded for the last specified time interval.
Detailed description is shown on example below. Possible time units MONTH (month),
DAY (day), YEAR (year). The data should be terminated with a slash /.
Data on first and last time step is always recorded.

(see 12.17.2).
In graphical interface in the window with model one should choose "Reload with New
Recording Options". Choose "As in RPTMAPD and RPTGRAPHD keywords".
12.17.3. RPTMAPT/RPTGRAPHT 1191

Example
RPTMAPT
MONTH
2 3 4
/
RPTGRAPHT
MONTH
2 3 4
/
In this example the time unit is specified - month. Below there are numbers 2, 3 and 4.
This means that Map and Graphs results will be recorded on first time step, then in 2 month,
then in 3 month then in 4 month. Then also in 4 month, then in 4 month and etc.
For example,
If there are the following dates in the model:
01 JAN 1998
01 FEB 1998
01 MAR 1998
01 APR 1998
01 MAY 1998
01 JUN 1998
01 JUL 1998
01 AUG 1998
01 SEP 1998
01 OCT 1998
01 NOV 1998
01 DEC 1998
01 JAN 1999
01 FEB 1999
01 MAR 1999
01 APR 1999
Then Maps and Graphs results will be recording on the following time steps:
01 JAN 1998 (first time step)
01 MAR 1998 (in 2 month)
01 JUN 1998 (in 3 month)
01 OCT 1998 (in 4 month)
01 FEB 1999 (in 4 month)
01 APR 1999 (last time step)
12.17.3. RPTMAPT/RPTGRAPHT 1192

12.17.4 RPTMAPL/RPTGRAPHL


Section
This keyword allows to manage a record of calculated maps (RPTMAPL) and graphs
(RPTGRAPHL) to the hard disc (record data only for time steps selected by the user). Thus,
If these keywords are used results will be recorded on disc only for first and last time
steps. The data should be terminated with a slash /.

(see 12.17.2).
In graphical interface in the window with model one should choose Reload with New
Recording Options. Choose As in RPTMAPD and RPTGRAPHD keywords.
Example
RPTMAPL
/
RPTGRAPHL
/
12.17.4. RPTMAPL/RPTGRAPHL 1193

12.17.5 RPTONLY


Section
This keyword is used to save reporting parameters for wells, groups in binary files in
E100 format at calculation time steps when the model is calculated by tNavigator console
version. The keyword doesnt need any parameters after it.
Description of console version tNavigator section 8.
For default (if this keyword is not specified) parameters are saved at calculation time steps
when binary files are dumped during model calculation in console version. Calculation results
are save in binary files from graphical user interface (Reports. Save E100 binaries) only at
reporting time step (not calculation steps) (regardless of whether the keyword RPTONLY is
present or not).
Example
RPTONLY
12.17.5. RPTONLY 1194

12.17.6 DATE


Section
The keyword outputs the date to SUMMARY-file. The date is stored as three parameters:
DAY, MONTH, YEAR.
The keyword doesnt need any parameters after it.
Example
DATE
12.17.6. DATE 1195

12.17.7 SEPARATE / RUNSUM


Section
Keywords SEPARATE and RUNSUM activate export RSM file option for E100 and E300
models respectively.
If console version of tNavigator is used, then one can use option --ecl-rsm to activate
RSM file exporting.
Description of console version tNavigator section 8.
Example
SEPARATE
12.17.7. SEPARATE / RUNSUM 1196

12.18. Schedule section tNavigator-4.2
12.18 Schedule section

Keywords in this section are interpreted according to sequence in which they are specified in
user file, so user should first specify well, then its perforations and then its schedule.
In tNavigator the following format is recommended. The well should be defined first
via the keyword WELSPECS (see 12.18.3). Then well trajectory is defined via WELL-
TRACK (see 12.18.9) and after that perforations are defined via the keyword COMPDATMD
(see 12.18.10).
Data specification in ECLIPSE format.

In ECLIPSE format well is specified by keyword (WELSPECS (see 12.18.3)) and its perfo-
rated intervals by keyword (COMPDAT (see 12.18.6)).
tNavigator supports hybrid model (section 11.3) of input data:
1. Case 1. Basic model is specified in Eclipse format (all sections, except sched-
ule section). Schedule section is specified in MORE format the keyword RECU
(see 12.18.218).
2. Case 2. Basic model is specified in Eclipse format. Well data in MORE format can be
loaded additionally (for example, well trajectories, events, history are loaded).
3. Case 3. Basic model is specified in MORE format. Well events are created additionally
in Eclipse format.
To specify wells in ECLIPSE format in local grids (section 5.6) the following keywords
should be used:
WELSPECL (see 12.18.4) introduces a new well, defining information on its name
and coordinates in local grids (LGR). WELSPECL must be used in place of WELSPECS
(see 12.18.3) to set the general specification data for wells in local refined grids.
COMPDATL (see 12.18.7) defines well completions in local grids (LGR).

COMPDATL (see 12.18.7) must be used in place of COMPDAT (see 12.18.6) to
specify the connection data for wells in local refined grids.
COMPLMPL (see 12.18.23) (SCHEDULE section) lumps connections together into

completions to provide realization of simultaneous actions for wells in local grids
(LGR).
COMPLMPL (see 12.18.23) must be used in place of COMPLUMP (see 12.18.22)
to lump connections together into completions to provide realization of simultaneous
actions for wells in local refined grids.
WPIMULTL (see 12.18.29) (SCHEDULE section) multiplies well connection trans-

missibility factors by specified value for wells in local grids (LGR).
WPIMULTL (see 12.18.29) must be used in place of WPIMULT (see 12.18.28) to
12.18. Schedule section 1197

multiply well connection transmissibility factors by specified value for wells in local
refined grids.
WFRACL (see 12.18.123) (SCHEDULE section) specifies the hydraulic fracture for
wells in local refined grids (LGR). WFRACL (see 12.18.123) must be used in place
of WFRAC (see 12.18.122) to specify the hydraulic fracture for wells in local refined
grids.
WFRACPL (see 12.18.125) (SCHEDULE section) specifies the hydraulic fracture for
wells in local refined grids (LGR) in graphical interface. WFRACPL (see 12.18.125)
must be used in place of WFRACP (see 12.18.124) to specify the hydraulic fracture for
wells in local refined grids in graphical interface.
COMPFRACL (see 12.18.127) (SCHEDULE section) specifies the hydraulic fracture
for connection in the grid layer for wells in local refined grids (LGR). COMPFRACL
(see 12.18.127) must be used in place of COMPFRAC (see 12.18.126) to specify the
hydraulic fracture for connection in the grid layer for wells in local refined grids.
In order to set well schedule it is necessary to specify well name (or number) and name
of group it belongs to.
Either fully qualified well name or masked named may be used. In the latter case the
operation desired will be applied to subset of wells with names fitted to mask. In the well
mask along with usual alphabetic and numeric symbols the following special symbols may
be used:
* corresponds to 0 or more any symbols;
? corresponds to any single symbol;
[n-m] corresponds to any single symbol with code in the range from n to m.
Examples of well name specifications:
P123 specifies single well with name P123;
* specifies all wells;
P* specifies all wells with names starting from letter P;
P1?3 specifies all wells with 4 letter names and 2 first letters are P1 and the last is
3;
P1[1-3]3 specifies wells with names P113, P123, P133 (if they are exist);
Mask as well name cannot be used for new well introduction, but the only for changing of
work mode for existing wells.
To set parameter value equal to default, put asterisk *. If several successive parameters
are equal to default values, you can write N*, here N is number of parameters for which
program will take default values.
For any keyword in this section (except TSTEP and DATES) the optional date may be
specified. This date may be specified for the whole keyword block, for example,

Example
WCONPROD 1 JAN 2003
...
as well as for any entry in the keyword block, for example,
Example
COMPDAT
1043 14 10 1 2 OPEN 8* 21 MAY 2003 /
W13 16 13 1 3 OPEN 3* 20 1 1* Z 1* 21 JUN 2003 /
...
If both dates are specified (for whole block and for record in the block) the date for
record is used.
Traditional monotonic schedule section is also supported. If optional dates are specified
then monotonic section will be reconstructed and new dates will be inserted.

12.18.1 SCHEDULE


Section
The keyword specifies the beginning of data section which contains well data.
12.18.1. SCHEDULE 1200

12.18.2 WELSOMIN


Section
The keyword sets minimum oil saturation in a block for automatic opening of well
connections (well working mode AUTO in WCONPROD (see 12.18.34)). If the limit WEL-
SOMIN isnt reached connections can be opened manually (using the keyword COMPDAT
(see 12.18.6)). If the keyword isnt specified well connections (well working mode AUTO),
will be opened automatically for any block oil saturation.
Example
WELSOMIN
0.35 /
12.18.2. WELSOMIN 1201

12.18.3 WELSPECS


Section
This keyword introduces a new well, defining information on its name and coordinates. A
set of data for every well should be terminated with a slash /. All data should be terminated
1. well name (or number),
2. name of the group to which this well belongs,
3. bottom hole or well head coordinates in X direction (IW);
4. bottom hole or well head coordinates in Y direction (JW); those are i and j in 5.7.1;
These coordinates (IW and JW) will be later used as default perforation coordinates if
parameters 2 and 3 are defaulted in COMPDAT (see 12.18.6),
5. reference depth for bottom hole pressure.

Recommended location - first perforated interval depth (METRIC: m, FIELD: f t ),
6. preferred phase for well: OIL, WATER, GAS, LIQ. This data is used to determine the
worst offending well or connection for closure when a group production rate limit is
exceeded GCONPROD (see 12.18.72) (7-th parameter).
This data is also used to define the productivity/injectivity index of well or potential
flow rate (parameter 7 of this keyword)
7. drainage radius productivity/injectivity index calculations (METRIC: m, FIELD: f t ).

Productivity/injectivity index is calculated from a steady-state relationship and is printed
in the well reports.
If 0 is specified, then is used the pressure equivalent radius of the grid blocks containing
the well connections. The productivity index is equal to the sum over the connections
of the product of the connection factor and the local mobility of the preferred phase.
If the value is negative, the wells potential flow rate is printed in the well reports
instead of the productivity index. (The wells potential rate is the flow rate it would
achieve in the absence of any rate constraint, limited only by its BHP and THP con-
straint),
8. flag of a special inflow equation to model the flow of gas between the completed grid
blocks and the well completions:
12.18.3. WELSPECS 1202

STD (or NO) the standard inflow equations will be used,

GPP generalized pseudo-pressure equation (this option may be used by gas con-
densate producers the keyword PICOND (see 12.18.187)). Generalized pseudo-
pressure equation alters both the gas and oil mobilities and takes accounts also of
the effects of condensate dropout,
R-G (or YES) Russell-Goodrich equation,
P-P dry gas pseudo-pressure equation (should not be used for gas condensate).
9. well can be automatically shut or stopped if a well or group economic limit or group
flow limit is violated: CodeSTOP - stop well above formation, SHUT - isolate well
from the formation,
10. crossflow ability flag: YES - crossflow allowed in the well, NO - crossflow not allowed
in the well, connection is a one-way valve, which prevents reverse drawdown flow;
11. pressure table number for wellbore fluid properties. If 0 is specified, the pressure table
number is equal to PVT region number of the lowest grid block with wells connection;
12. type of density calculations for the wellbore hydrostatic head:
SEG segmented model of density calculations. This model is supported in

tNavigator for black-oil models and compositional models, this option can also be
used with BRINE (see 12.1.58) option.
The mixture density in the wellbore is calculated in each segment between two
connections, and depends on the relative quantities of the phases that are flowing
in this segment of the wellbore. This calculation model is more accurate than AVG
if different mixtures of fluids flows to the well through each connection.
AVG averaged density calculation model. The mixture density is considered as
uniform in the wellbore at formation level, depends on the total inflow rates of
each phase and the wells BHP.
13. number of FIP region, that will be used in the calculations of the well rate in reservoir
conditions:
positive value is set: this number is considered as a number of FIP region, that
will be used in the calculations of the well rate in reservoir conditions;
zero value is set: the average hydrocarbon conditions in the field will be used;
negative value is set: the region number is set equal to the FIP region number of
the lowest grid block where the well is perforated.
Default:
well group name: FIELD,
bottom hole or well head coordinates in X direction (IW);
12.18.3. WELSPECS 1203

bottom hole or well head coordinates in Y direction (JW)

Values IW and JW can be defaulted (*). In this case one need to specify parameters
2 and 3 of the keyword COMPDAT (see 12.18.6). Otherwise model read error will
occur;
reference depth for bottom hole pressure - first perforated interval depth,
drainage radius 0,
flag of a special inflow equation STD,
automatically shut or stopped if a well or group economic limit or group flow limit is
violated SHUT,
crossflow ability flag YES.
pressure table number for wellbore fluid properties 0;
type of density calculations for the wellbore hydrostatic head SEG (for black-oil and
compositional models), AVG (for thermal models).
number of FIP region, that will be used in the calculations of the well rate in reservoir
conditions 0.
Example
DIMENS
25 20 3
...
WELSPECS
1043 G1 14 10 5* NO/
W13 1* 16 13 /
/
Here two wells are defined: well 1043, from group G1, its bottom hole situated at X = 14
and Y = 10, crossflow not allowed in the well; and well W13, from group FIELD, bottom
hole situated at X = 16 and Y = 13.
12.18.3. WELSPECS 1204

12.18.4 WELSPECL


Section
This keyword introduces a new well, defining information on its name and coordinates in
local grids (LGR) section 5.6.
WELSPECL must be used in place of WELSPECS (see 12.18.3) to set the general
specification data for wells in local refined grids. The keyword data is similar to that for
WELSPECS (see 12.18.3), except there is an additional item at parameter 3 which gives the
name of the local grid refinement in which the well is located. The connection data for these
wells must be specified using the keyword COMPDATL (see 12.18.7) instead of COMPDAT
(see 12.18.6).
A set of data for every well should be terminated with a slash /. All data should be
2. name of the group to which this well belongs,
3. name of the local refined grid in which the well is located (CARFIN (see 12.2.87)),
4. bottom hole or well head coordinates in X direction (IW);
5. bottom hole or well head coordinates in Y direction (JW); those are i and j in 5.7.1;
These coordinates (IW and JW) will be later used as default perforation coordinates if
parameters 3 and 4 are defaulted in COMPDATL (see 12.18.7),
6. reference depth for bottom hole pressure.

Recommended location - first perforated interval depth (METRIC: m, FIELD: f t ),
7. preferred phase for well: OIL, WATER, GAS, LIQ. This data is used to determine the
worst offending well or connection for closure when a group production rate limit is
exceeded GCONPROD (see 12.18.72) (7-th parameter).
This data is also used to define the productivity/injectivity index of well or potential
flow rate (parameter 7 of this keyword)
8. drainage radius productivity/injectivity index calculations (METRIC: m, FIELD: f t ).

Productivity/injectivity index is calculated from a steady-state relationship and is printed
12.18.4. WELSPECL 1205

in the well reports.

If 0 is specified, then is used the pressure equivalent radius of the grid blocks containing
the well connections. The productivity index is equal to the sum over the connections
of the product of the connection factor and the local mobility of the preferred phase.
If the value is negative, the wells potential flow rate is printed in the well reports
instead of the productivity index. (The wells potential rate is the flow rate it would
achieve in the absence of any rate constraint, limited only by its BHP and THP con-
straint),
9. flag of a special inflow equation to model the flow of gas between the completed grid
blocks and the well completions: STD (or NO) the standard inflow equations will
be used, GPP generalized pseudo-pressure equation (this option may be used by gas
condensate producers the keyword PICOND (see 12.18.187)). Generalized pseudo-
pressure equation alters both the gas and oil mobilities and takes accounts also of the
effects of condensate dropout,
10. well can be automatically shut or stopped if a well or group economic limit or group
flow limit is violated: CodeSTOP - stop well above formation, SHUT - isolate well
from the formation,
11. crossflow ability flag: YES - crossflow allowed in the well, NO - crossflow not allowed
in the well, connection is a one-way valve, which prevents reverse drawdown flow.
12. pressure table number for wellbore fluid properties. If 0 is specified, the pressure table
number is equal to PVT region number of the lowest grid block with wells connection;
13. type of density calculations for the wellbore hydrostatic head:
SEG segmented model of density calculations. This model is supported in
tNavigator for black-oil and compositional models.
The mixture density in the wellbore is calculated in each segment between two
connections, and depends on the relative quantities of the phases that are flowing
in this segment of the wellbore. This calculation model is more accurate than AVG
if different mixtures of fluids flows to the well through each connection.
AVG averaged density calculation model. The mixture density is considered as
uniform in the wellbore at formation level, depends on the total inflow rates of
each phase and the wells BHP.
Default:
well group name: FIELD,
bottom hole or well head coordinates in X direction (IW);
bottom hole or well head coordinates in Y direction (JW)
Values IW and JW can be defaulted (*). In this case one need to specify parameters
3 and 4 of the keyword COMPDATL (see 12.18.7). Otherwise model read error will
occur;
12.18.4. WELSPECL 1206

reference depth for bottom hole pressure - first perforated interval depth,
drainage radius 0,
flag of a special inflow equation STD,
automatically shut or stopped if a well or group economic limit or group flow limit is
violated SHUT,
crossflow ability flag YES.
pressure table number for wellbore fluid properties 0;
type of density calculations for the wellbore hydrostatic head SEG (for black-oil and
compositional models), AVG (for thermal models).
Example
WELSPECL
WELL1 G1 LGR1 6 8 2500 /
WELL2 G1 LGR2 28 16 2300 /
/
In this example two wells are defined: WELL1, its bottom hole situated at X = 6 and
Y = 8, from group G1. This well is located in local grid refinement LGR1, reference depth
2500m. WELL2, its bottom hole situated at X = 28 and Y = 16, from group G1. This well
is located in local grid refinement LGR2, reference depth 2300m.
12.18.4. WELSPECL 1207

12.18.5 WELLSPEC


Section
This keyword can be used in tNavigator, but it is highly recommended to use the keyword
WELSPECS (see 12.18.3) instead of WELLSPEC.
12.18.5. WELLSPEC 1208

12.18.6 COMPDAT


Section
This keyword defines well completions. A set of data for every well should be terminated
with a slash /. All data should be terminated with a final slash /.
2. perforated interval coordinate in X direction (IW); there is i in 5.7.1,
3. perforated interval coordinate in Y direction (JW); there is j in 5.7.1,
4. number of layer where this vertical perforated interval starts (layers are numbered
top-down starting from 1); this is number k in 5.7.1,
5. number of layer where this vertical perforated interval ends, this is number k in 5.7.1,
6. completion status:
OPEN,
SHUT,
AUTO connection is initially closed. It will be opened automatically when
another well connection is closed during an automatic workover. A connection on
AUTO is opened each time the well is worked over, in the order in which the
connections are first defined in COMPDAT.
7. saturation table number,
8. transmissibility factor (CF - connection factor) (METRIC: cPrm3 /daybar , FIELD:

cP rb/day psi) for each connection in this interval (if it is specified, well diameter,
skin and KH are ignored), this is coefficient T (t) in 5.7.1,
9. well diameter (METRIC: m, FIELD: f t ), value dw in 5.7.2,
10. effective KH (METRIC: mD m, FIELD: mD f t ) (permeability x thickness) for

each connection in this interval, (see 5.7.2),
11. skin factor, this is value s in 5.7.2,
12.18.6. COMPDAT 1209

12. D-factor for non-Darcy flow handling (METRIC: day/sm3 , FIELD: day/Msc f ) (the
connections D-factor can be entered here directly: one should specify it here with
negative sign. tNavigator takes this value without negative sign). Wells D-factor may
be entered via WDFAC (see 12.18.146);
Calculation of D-factor.
If D-factor for well is specified, then connection D-factor is calculated via formula:
Dconn = (Dwell c f )/c fconn
If D-factors for connections are specified then for wells:
Dwell = Dconn c fconn /( c f )
13. direction in which this interval penetrates grid block: X, Y or Z,
14. effective radius (METRIC: m, FIELD: f t ), this is value ro in 5.7.2.

This keyword may be defined several times at any time step for the same well for different
connections. Perforated intervals for the same well may be spaced (may not form a continuous
interval) and have different orientation in space.
Default:
1. non specified,
2. i is taken from WELSPECS (see 12.18.3) parameter 3 (if that parameter in WEL-
SPECS is also defaulted, then model read error will occur),
3. j is taken from WELSPECS (see 12.18.3) parameter 4 (if that parameter in WEL-
4. starting block of vertical perforated interval: 1,
5. ending block of vertical perforated interval: NZ ,
6. connection status: OPEN,
7. saturation table number tNavigator will use the saturation table number that is speci-
fied for block with connection via SATNUM (see 12.4.3);
8. transmissibility factor: calculated,
9. well diameter: dw = 0.3048 m,
10. KH value: calculated,
11. skin factor: s = 0,
12. non specified,
12.18.6. COMPDAT 1210

13. well orientation in space: Z,
14. effective radius: calculated.
If all connections for a well are in SHUT mode then this well automatically will be
switched to working mode SHUT (WCONPROD (see 12.18.34), WCONINJE (see 12.18.36)).
Example
DIMENS
25 20 3
...
COMPDAT
1043 14 10 1 2 OPEN 5* /
W13 16 13 1 3 OPEN 2* 0.16 20 1 1* Z 1* /
PRO4 5 5 1 1 OPEN 2* 0.16 3* X /
PRO4 5 5 2 2 OPEN 2* 0.16 1* -1 3* /
PRO4 5 5 3 3 OPEN 2* 0.16 50 2* Y /
/
This example defines perforation intervals for three wells, for a grid 25x20x3. All wells
belong to the same group FIELD, perforations are open.
Well 1043 has coordinates X = 14, Y = 10, first two layers are perforated, well diameter,
skin factor and orientation are taken by default: diameter dw = 0.156 m, skin s = 0 and
orientation in Z direction; KH and effective radius are calculated.
Well W13 has coordinates X = 16, Y = 13, layers from the first one to the third one are
perforated, diameter is set to dw = 0.16 m, skin is s = 1, KH = 20 and orientation in space
is in Z direction.
The third well, PRO4, is also perforated in all three layers: in the first layer skin and
KH are defaulted, orientation in space is in X direction; in the second layer skin is equal to
s = 1, KH and orientation in space are defaulted (orientation=Z), in the third layer default
skin factor is taken s = 0, KH multiplier is set to KH = 50 and orientation in space is in Y
direction.
12.18.6. COMPDAT 1211

12.18.7 COMPDATL


Section
This keyword defines well completions in local grids section 5.6. A set of data for
every well should be terminated with a slash /. All data should be terminated with a final
slash /.
COMPDATL must be used in place of COMPDAT (see 12.18.6) to specify the connec-
tion data for wells in local refined grids, after the wells have been introduced with keyword
WELSPECL (see 12.18.4) (instead of WELSPECS (see 12.18.3)). The keyword data for
COMPDATL (see 12.18.7) is the same as for COMPDAT (see 12.18.6), except for an ex-
tra parameter 2 which names the local grid containing the connections specified in the record.

2. local grid name (CARFIN (see 12.2.87)),
OPEN,
SHUT,
AUTO connection is initially closed. It will be opened automatically when
another well connection is closed during an automatic workover. A connection on
AUTO is opened each time the well is worked over, in the order in which the
connections are first defined in COMPDAT.
8. saturation table number (IGNORED, this is an Eclipse compatibility field),
cP rb/day psi) for each connection in this interval (if it is specified, well diameter,
skin and KH are ignored), this is coefficient T (t) in 5.7.1,
12.18.7. COMPDATL 1212

11. effective KH (METRIC: mD m, FIELD: mD f t ) (permeability x thickness) for

each connection in this interval, (see 5.7.2),
13. D-factor for non-Darcy flow handling (METRIC: day/sm3 , FIELD: day/Msc f ) (the
connections D-factor can be entered here directly: one should specify it here with
negative sign. tNavigator takes this value without negative sign). Wells D-factor may
be entered via WDFAC (see 12.18.146);
14. direction in which this interval penetrates grid block: X, Y or Z,
15. effective radius (METRIC: m, FIELD: f t ), this is value ro in 5.7.2.

This keyword may be defined several times at any time step for the same well for different
connections. Perforated intervals for the same well may be spaced (may not form a continuous
interval) and have different orientation in space.
Default:
1. non specified,
2. non specified,
3. i is taken from WELSPECL (see 12.18.4) parameter 3 (if that parameter in WELSPECS
is also defaulted, then model read error will occur),
4. j is taken from WELSPECL (see 12.18.4) parameter 4 (if that parameter in WEL-
5. starting block of vertical perforated interval: 1,
6. ending block of vertical perforated interval: NZ ,
7. connection status: OPEN,
8. non specified,
9. transmissibility factor: calculated,
12.18.7. COMPDATL 1213

10. well diameter: dw = 0.3048 m,
11. KH value: calculated,
12. skin factor: s = 0,
13. non specified,
14. well orientation in space: Z,
15. effective radius: calculated.
Example
DIMENS
25 20 3
...
COMPDATL
1043 LGR1 14 10 1 2 OPEN 5* /
W13 LGR2 16 13 1 3 OPEN 2* 0.16 20 1 1* Z 1* /
/
This example defines perforation intervals for three wells, for a grid 25x20x3. All wells
belong to the same group FIELD, perforations are open.
Well 1043 has coordinates X = 14, Y = 10, first two layers are perforated, well diameter,
skin factor and orientation are taken by default: diameter dw = 0.156 m, skin s = 0 and
orientation in Z direction; KH and effective radius are calculated. This well is located in
local grid refinement LGR1.
Well W13 has coordinates X = 16, Y = 13, layers from the first one to the third one are
perforated, diameter is set to dw = 0.16 m, skin is s = 1, KH = 20 and orientation in space
is in Z direction. This well is located in local grid refinement LGR2.
12.18.7. COMPDATL 1214

12.18.8 COMPDATM


Section
This keyword is an analogue for the keyword COMPDATL (see 12.18.7).
12.18.8. COMPDATM 1215

12.18.9 WELLTRACK


Section
This keyword is used to define well trajectory, including different well branches. The
well should be defined first via the keyword WELSPECS (see 12.18.3). Then well trajectory
is defined via WELLTRACK (see 12.18.9) and after that perforations are defined via the
keyword COMPDATMD (see 12.18.10).
This keyword cant be used inside any of ACTION (see 12.18.131) type keywords.
The data for each well should be terminated with a slash /.
Case 1: There is only one well branch (main branch).

The following parameters should be specified in the first line:
WELLTRACK keyword;
well name (only well name is allowed; no * or well mask).

The following parameters should be specified in each next line:
X (METRIC: m, FIELD: f t );
Y (METRIC: m, FIELD: f t );
Z (absolute depth) (METRIC: m, FIELD: f t );
MD measured depth (depth along the well bore) (METRIC: m, FIELD: f t ).

Any number of lines can be specified for one well.
Example
WELLTRACK PROD1'
'
21500.716 30890.824 -1.501 60.000

21500.304 30890.612 18.493 80.000
21499.167 30890.004 38.449 100.000
21442.479 30873.750 217.226 290.000
21292.330 30852.813 464.342 580.000
21094.197 30827.983 810.860 980.000
20934.052 30811.399 1110.313 1320.000
20807.357 30788.941 1403.000 1640.000
20722.508 30782.704 1752.275 2000.000 /
12.18.9. WELLTRACK 1216

Case 2: There are several well branches.

WELLTRACK keyword should be used to define each branch. The data for each branch
The following parameters should be specified in the first line:
WELLTRACK keyword;
well name : well branch number.

If the well branch number is not specified then it is considered as a main branch
(number 0).
The following parameters should be specified in each next line:
X (METRIC: m, FIELD: f t );
Y (METRIC: m, FIELD: f t );
Z (absolute depth) (METRIC: m, FIELD: f t );
MD measured depth (depth along the well bore) (METRIC: m, FIELD: f t ).
Any number of lines can be specified for one branch.
Example
WELLTRACK 'PROD1'
5296.82 20531.05 2188.63 2188.63
5296.82 20531.05 2237.75 2237.75
4979.02 20901.82 2241.00 2726.10
4633.34 21305.11 2243.07 3257.27
4298.81 21695.40 2244.84 3771.31
3953.13 22098.69 2245.28 4302.48 /
WELLTRACK 'PROD1:1'
5296.82 20531.05 2237.75 2237.75
5442.35 20361.27 2241.19 2461.39
5530.29 20258.67 2244.14 2596.55
5569.37 20213.07 2245.08 2656.61 /
In this example 2 well branches are defined: main well branch and the branch number 1.
12.18.9. WELLTRACK 1217

12.18.10 COMPDATMD


Section
This keyword defines well perforations in measured depth (upper measured depth MDU
and lower measured depth MDL).
To use this keyword first define well using the keyword WELSPECS (see 12.18.3), and
wells trajectory using the keyword WELLTRACK (see 12.18.9).
If this keyword COMPDATMD is used tNavigator automatically intersects the well bore with
the grid and open connections inside defined values of MDU and MDL. Connection factor
and effective KH are calculated.
This keyword cant be used inside any of ACTION (see 12.18.131) type keywords.
This keyword has Eclipse compatible analogues COMPDAT (see 12.18.6), COMPDATL
(see 12.18.7).
An arbitrary number of data lines can be entered, terminated with a slash /. All data
The following parameters should be specified in one line:
1. well name (or number);
2. well bore branch number (branches can be set in WELLTRACK (see 12.18.9));
3. MDU upper depth (METRIC: m, FIELD: f t );
4. MDL lower depth (METRIC: m, FIELD: f t );
5. depth type: MD (measured depth) or TVD (true vertical depth) to set perforated interval
in parameters 3 and 4;
OPEN,
SHUT,
7. saturation table number; this parameter should be defaulted;

cP rb/day psi) this is coefficient T (t) in 5.7.1; this parameter should be de-
faulted, tNavigator calculates it automatically;
12.18.10. COMPDATMD 1218

10. effective KH (METRIC: mD m, FIELD: mD f t ) (permeability x thickness),

(see 5.7.2); this parameter should be defaulted, tNavigator calculates it auto-
matically;
12. D-factor for non-Darcy flow handling (METRIC: day/sm3 , FIELD: day/Msc f ).
so using this formula we get D-factor for well, then it can be used to calculate D-
factors for connections.
So if we set in the model in all COMPDATMD the same D-factor for the well, then the
calculation will be the same if WDFAC (see 12.18.146) with this value is specified.
13. connection factor multiplier;
14. completion type. This parameter should be used in Dual porosity and Dual permeability
runs. The following values can be used:
FRAC complete in fracture blocks only;

MAT complete in matrix blocks only;
BOTH complete in both fracture and matrix blocks.
Default:
well bore branch number 0 (main branch);
MDU upper measured depth top depth of the reservoir;
MDL lower measured depth bottom depth of the reservoir;
depth type: MD (measured depth);
completion status OPEN;
saturation table number tNavigator will use the saturation table number that is speci-
fied for block with connection via SATNUM (see 12.4.3); ;
transmissibility factor: calculated;
12.18.10. COMPDATMD 1219

well diameter: dw = 0.3048 m;
effective KH: calculated;
skin factor: s = 0;
D-factor for non-Darcy flow handling: non specified;
connection factor multiplier: 1;
completion type: FRAC.
Example
COMPDATMD
'W1' 1* 1250.0 1400.0 MD 'OPEN' 1* 1* 0.3 1* -3 1* /
'W2' 1* 1350.0 1580.0 MD 'OPEN' 1* 1* 0.3 1* -3 1* /
'W3' 1* 1250.0 1380.0 MD 'OPEN' 1* 1* 0.3 1* -3 1* /
/
12.18.10. COMPDATMD 1220

12.18.11 WELSEGS


Section
The keyword specifies the segment structure of a multisegment well (section 2.19.4). One
keyword can specify only one well. The well should be previously defined via the keyword
WELSPECS (see 12.18.3) (WELSPECL (see 12.18.4)).
The keyword consists of the following data: first data record defines the well and its top
segment (nearest to the wellhead), next data records defines other segments. Each data record
should be terminated with a slash /. All data should be terminated with a final /.
First data record the following data for the first segment should be entered:
1. well name (or well number);
2. depth of the nodal point of the top segment (BHP reference depth) (METRIC: m,
FIELD: f t );
3. length down the tubing to the nodal point of the top segment (METRIC: m, FIELD:
f t ). The position of top segments node is fixed relative to the zero tubing length
reference point (from which all the tubing length values are measured). For this segment
(above the nodal point of the top segment pressure losses are not calculated). Pressure
losses between the BHP reference depth and the tubing head should normally be
handled by VFP tables;
4. effective wellbore volume of the top segment (METRIC: m3 , FIELD: f t 3 );
5. type of tubing length and depth information entered in second (etc.) data records of
this keyword:
INC length and depth values entered in parameter 5 and 6 of the next data records refer
to the incremental changes of these quantities along each segment (increase gradually).
ABS length and depth values entered in parameter 5 and 6 of the next data records
refer to the absolute values of the tubing length and depth at the segment nodes.
6. components of the pressure drop that will be included in the calculation for wells
segments:
HFA hydrostatic + friction + acceleration (the acceleration pressure drop is calculated
using a homogeneous flow model and is added to the pressure drop calculated from
interpolation of VFP table);
HF- hydrostatic + friction;
H hydrostatic.
12.18.11. WELSEGS 1221

7. default Multi-phase Flow Model for the wells segments:

HO homogeneous flow (the phases all flow with the same velocity) (tNavigator
supports only this flow type);
8. X-coordinate of the nodal point of the top segment, relative to the origin of the grid
(METRIC: m, FIELD: f t ); IGNORED, this is an Eclipse compatibility field;
9. Y-coordinate of the nodal point of the top segment, relative to the origin of the grid
(METRIC: m, FIELD: f t ); IGNORED, this is an Eclipse compatibility field.
Default:
length down the tubing to the nodal point of the top segment 0 (m).
effective wellbore volume of the top segment 1.0e-5 (m3 ).
components of the pressure drop that will be included in the calculation for wells
segments: HFA.
default Multi-phase Flow Model for the wells segments: HO.
Second and other data records the following data for the second segment should
be entered (other segments the same way):
1. segment number at the start of the range (nearest the top segment) (all parameters of
this keyword (from 3) specify the properties of the segments in the range given by
parameters 1 and 2. Parameter 1 should be equal to parameter 2 if one need to enter
properties of one segment);
2. segment number at the end of the range (all parameters of this keyword (from 3) specify
the properties of the segments in the range given by parameters 1 and 2. Parameter 1
should be equal to parameter 2 if one need to enter properties of one segment);
3. branch number (1 segments situated on the main stem. Lateral branches should have
numbers 2 etc.);
4. number of outlet segment (number of the segment to which the segment at the start of
the range (parameter 1) is joined, that is its neighbor in the direction of the wellhead).
A node in a multi-lateral well can be the outlet segment of two or more segments of
different branches;
5. if parameter 5 of first data record (for top segment) INC:

length of each segment in the range, that is the distance between its nodal point
and that of its neighbor in the direction of the wellhead (METRIC: m, FIELD:
f t ).
12.18.11. WELSEGS 1222

if parameter 5 of first data record (for top segment) ABS:

length down the tubing (from the zero tubing length reference point) at the nodal
point of the last segment in the range. The length between this point and the node
of the ranges outlet segment (parameter 4) is divided into equal lengths (this
value is equal to the number of segments in the range) (METRIC: m, FIELD:
f t ).

depth change along each segment in the range, that is the depth of its nodal point
minus the depth of its outlet segments nodal point (METRIC: m, FIELD: f t ).
depth of the nodal point of the last segment in the range. The depths of any
other segments in this range is calculated by interpolating between this depth and
the depth of the ranges outlet segment (parameter 4), linearly according to their
length down the tubing (METRIC: m, FIELD: f t ).
7. tubing internal diameter (METRIC: m, FIELD: f t );
8. effective absolute roughness of the tubing (METRIC: m, FIELD: f t );
9. cross-sectional area for fluid flow (METRIC: m2 , FIELD: f t 2 );
10. segments volume (METRIC: m3 , FIELD: f t 3 );

length of each segment in the range projected onto the X-axis, that is the X-
coordinate of its nodal point minus that of its neighbor in the direction of the
wellhead (METRIC: m, FIELD: f t ).
X-coordinate of the nodal point of the last segment in the range, relative to the
origin of the grid. X-coordinates of any other segments in this range is calculated
by interpolating between this value and the X coordinate of the ranges outlet seg-
ment ( parameter 4), linearly according to their length down the tubing (METRIC:
m, FIELD: f t ).

length of each segment in the range projected onto the Y-axis, that is the Y-
coordinate of its nodal point minus that of its neighbor in the direction of the
wellhead (METRIC: m, FIELD: f t ).
Y-coordinate of the nodal point of the last segment in the range, relative to the
origin of the grid. Y-coordinates of any other segments in this range is calculated
by interpolating between this value and the Y-coordinate of the ranges outlet seg-
ment (parameter 4), linearly according to their length down the tubing (METRIC:
m, FIELD: f t ).
12.18.11. WELSEGS 1223

Example
WELSEGS
W875 516.5 1.0 1.0 ABS HF- /
2 2 1 1 76.0 515.5 0.0762 1.0E-3 2* /
3 3 1 2 176.0 516 0.0762 1.0E-3 2* /
4 4 1 3 276.0 514.5 0.0762 1.0E-3 2* /
5 5 1 4 351.0 514 0.0762 1.0E-3 2* /
6 6 1 5 401.0 514.5 0.0762 1.0E-3 2* /
7 7 1 6 401.1 514.5 0.0651 1.0E-3 2* /
8 8 1 7 451.1 514 0.0651 1.0E-3 2* /
9 9 1 8 526.1 514.5 0.0651 1.0E-3 2* /
10 10 1 9 626.1 516 0.0651 1.0E-3 2* /
11 11 1 10 726.1 515.5 0.0651 1.0E-3 2* /
12 12 1 11 801.1 516.5 0.0651 1.0E-3 2* /
/
In this example for the well W875 depth of the nodal point of the top segment 516.5
m, length down the tubing to the nodal point of the top segment 1 m, effective wellbore
volume of the top segment 1 m3 , type of tubing length and depth information ABS,
components of the pressure drop hydrostatic + friction.
There is 1 branch.
12.18.11. WELSEGS 1224

12.18.12 WSEGTABL


Section
The keyword defines calculation of segment pressure drop from VFP tables (section
2.19.4). Multi-segment well should be entered via the keyword WELSEGS (see 12.18.11),
tables should be entered via VFPPROD (see 12.18.57) (VFPCORR (see 12.18.61)).
The data for each well should be terminated with a slash /. All data should be terminated
2. segment number at the start of the range (all parameters of this keyword (from 4)
specify the properties of the segments in the range given by parameters 2 and 3.
Parameter 2 should be equal to parameter 3 if one need to enter properties of one
segment);
3. segment number at the end of the range (all parameters of this keyword (from 4) specify
the properties of the segments in the range given by parameters 2 and 3. Parameter 2
should be equal to parameter 3 if one need to enter properties of one segment);
4. production VFP table number (VFPPROD (see 12.18.57), VFPCORR (see 12.18.61)).
Second parameter of the main data in the keyword VFPPROD (see 12.18.57) is either
datum length or datum depth of the segment. Pressure drop along each segment in
proportion to its length or depth span. The table may extend into negative flows, which
are interpreted as flow in the direction away from the wellhead.
5. components of the pressure drop that are included in the VFP table. tNavigator supports
only F- option friction option. The hydrostatic pressure drop is calculated from the
fluid density in the segment and added to the friction pressure drop interpolated from
the VFP table.
6. procedure for handling flows that are more negative (or less positive) than the first
flow value in the VFP: only REV is supported (reverse the flows and pressure losses in
the table). The first flow value in the VFP table should be positive. For negative flows,
reverse of the table is used. For flows in between + and - the first value, the pressure
loss is linearly interpolated between these two points.
Default:
12.18.12. WSEGTABL 1225

production VFP table number 0. Pressure drop is calculated according homogeneous

flow model.
Example
WSEGTABL
WELL1 6 10 3 F- /
/
In this example for the well WELL1 for segments from 6 to 10 3-rd VFP table is specified.
12.18.12. WSEGTABL 1226

12.18.13 WSEGVALV


Section
This keyword specifies calculation of segment pressure drops for sub-critical valve (Multi-
segment well should be specified via the keyword WELSEGS (see 12.18.11), section
2.19.4).
The data for each well should be terminated with a slash /. All data should be terminated
1. well name (or number), or well list specified via WLIST (see 12.18.26),
2. number of segment which contains the valve;
3. Cv flow coefficient for the valve;
4. Ac cross-section area for flow in the constriction (METRIC: m2 , FIELD: f t 2 );
5. L additional length of pipe for the friction pressure drop (METRIC: m, FIELD: f t ).
This parameter should be zero if there is no additional friction pressure loss;
6. D pipe diameter for the friction pressure drop (METRIC: m, FIELD: f t ). This
parameter overrides the 7-th parameter of WELSEGS (see 12.18.11);
7. absolute roughness of the pipe wall (METRIC: m, FIELD: f t ). This parameter over-
rides the 8-th parameter of WELSEGS (see 12.18.11);
8. A p pipe cross-section area for the friction pressure drop (METRIC: m2 , FIELD:
f t 2 ). This parameter overrides the 9-th parameter of WELSEGS (see 12.18.11);
9. flag that indicates if ICD (inflow control device) is open or shut:
OPEN ICD is open, flow is allowed;

SHUT ICD is shut, flow is not allowed. If the crossflow is enable, it is allowed
for this segment.
10. Amax maximum cross-sectional area for flow in the constriction (METRIC: m2 ,
FIELD: f t 2 );
Default:
12.18.13. WSEGVALV 1227

L additional length of pipe for the friction pressure drop accordingly to WELSEGS
(see 12.18.11);
D pipe diameter for the friction pressure drop 7-th parameter of the keyword
WELSEGS (see 12.18.11);
absolute roughness of the pipe wall 8-th parameter of the keyword WELSEGS (see
12.18.11);
A p pipe cross-section area for the friction pressure drop 9-th parameter of the
keyword WELSEGS (see 12.18.11);
Amax maximum cross-sectional area for flow in the constriction 8-th parameter of
this keyword or 9-th parameter of the keyword WELSEGS (see 12.18.11).
Valve simulation.
The pressure drop in the segment ploss that is a sub-critical valve is simulated as a flow
through a pipe containing a constriction with specified cross-section area:
f ric
ploss = pcons
loss + ploss
where:
pcons
loss takes into account the effect of a constriction
v2c
pcons
loss = C
2Cv2
C units conversion constant;
- density of the fluid mixture;
vc flow velocity of the mixture through the constriction (depends on the cross-section
area of the constriction Ac and volumetric flow rate of the mixture through the segment
Q, see below);
Cv flow coefficient for the valve;

f ric
ploss takes into account the effect of additional pressure loss due to friction
f ric L 2
ploss = 2C f v
D p
f Fanning friction factor;
L additional length of pipe for the friction pressure drop;
D pipe diameter (not constriction diameter);
12.18.13. WSEGVALV 1228

v p flow velocity of the mixture through the pipe (depends on the cross-section area
of the pipe A p and volumetric flow rate of the mixture through the segment Q, see
below);
Q = vc Ac = v p A p
Example
WSEGVALV
WELL43 6 0.70 0.02 0 /
/
12.18.13. WSEGVALV 1229

12.18.14 WSEGAICD


Section
This keyword designates specific well segments to represent an autonomous inflow control
device (ICD) in a multisegment well (see section 2.19.4). This type of device controls the
inflow profile along a horizontal well or branch by imposing an additional pressure drop
between the sand face and the tubing.
Pressure drop is given by:
cal y

mix
P = mix K q2 ,
cal mix
where:
K is the base strength of the AICD, with dimension of inverse area squared, defined
as:
K = aAICD qx2
aAICD the strength of the AICD (parameter 4);
x is the volume flow rate exponent (parameter 13);
y is the viscosity function exponent (parameter 14);
mix is the density of the fluid mixture in the segment at local conditions;
cal is the density of the fluid used to calibrate the ICD;
cal is the viscosity of the fluid used to calibrate the ICD;
mix = o o + w w + g g ;
o , w , g is the volume fraction of the free oil, water and gas phases at local
conditions;
o , w , g is the viscosity of the oil, water and gas phases at local conditions.
1. well name, well list (see the keyword WLIST (see 12.18.26)), or name ended by *,
i.e. mask;
2. segment number at the start of the segment range;
12.18.14. WSEGAICD 1230

3. segment number at the end of the segment range;
4. the strength of the AICD. This is an empirical constant based on measurements of fluid
flow through a particular type of ICD (METRIC: bars/((kg/m3 )(rm3 /day)x ), FIELD:
psi/((lb/ f t 3 )(r f t 3 /day)x ));
5. the length of the ICD (METRIC: m, FIELD: f t ). This and 11-th parameters are used
to determine a scaling factor which is used to scale the flow from the reservoir in order
to establish the flow, q, through each ICD. There are 3 possible ways to calculate this
factor (see description of parameter 11);
6. the density of the calibration fluid (METRIC: kg/m3 , FIELD: lb/ f t 3 );
7. the viscosity of the calibration fluid (METRIC: cP, FIELD: cP);
11. the way to calculate flow scale factor:
value 0 the flow scale factor is equal to the ratio of ICD length to the length
of the tubing segment, that is the parent of the ICD device (ICD segment may
represent a number of ICDs in parallel);
value 1 the flow scale factor is equal to the absolute value of segment length;
value 2 the flow scale factor is equal to the ratio of ICD length to the total
length of all completions which feed the ICD.
If this value is negative, then if item 5 is positive then the flow scaling factor is
equal to ratio of the ICD length to the length of the encased tubing segment, and
if item 5 is negative then the flow scaling factor is the absolute value of item 5.
13. volume flow rate exponent;
14. viscosity function exponent;
15. flag to indicate if the device is open or shut:
OPEN ICD is open and flow is allowed through the device;

SHUT ICD is shut and flow is not allowed through the device.
slash /.
Default:
12.18.14. WSEGAICD 1231

length of the ICD: METRIC: 12m, FIELD: 39.37 f t ;
density of the calibration fluid: METRIC: 1000.25kg/m3 , FIELD: 62.416lb/ f t 3 ;
viscosity of the calibration fluid: 1.45 cP;
the way to calculate flow scale factor: -1;
flag to indicate whether the device is open or shut: OPEN.
Example
WSEGAICD
PROD 18 18 1 -3.28083989501312 5* 0 1* 2 0.25/
PROD 19 19 0.0002 3.28083989501312 5* 2 1* 1 0.25 /
PROD 20 20 0.0002 3.28083989501312 5* 2 1* 1 1.25/
PROD 21 21 0.0002 3.28083989501312 5* 2 1* 1 0 /
PROD 22 22 0.0002 3.28083989501312 5* 2 1* 2 0.25/
/
In the example segment 18-22 of well PROD are designated as the autonomous inflow
control device.
12.18.14. WSEGAICD 1232

12.18.15 WSEGEXSS


Section
This keyword imports or removes fluids to or from a segment in a multisegment well.

Importing or removing fluid rate value is specified explicitly or via segment pressure value
dependence. The source or sink for this fluid is external. Each line should be ended by a
symbol /. The data should be terminated with a slash /.
1. well name or well list WLIST (see 12.18.26);
2. number of segment which contains the external source/sink;
3. source/sink type:
WIMPR water import at a specified rate;

GIMPR gas import at a specified rate;
WIMPP water import at a specified external pressure;
GIMPP gas import at a specified external pressure;
NONE remove the external source/sink from the segment.
4. import fluid rate value:
if the 3rd parameter is WIMPR, then water rate at surface conditions should be
specified (METRIC: sm3 /day, FIELD: stb/day);
if the 3rd parameter is GIMPR, then gas rate at surface condition should be
specified (METRIC: sm3 /day, FIELD: Msc f /day);
if the 3rd parameter is WIMPP, then limit on water rate should be specified
(METRIC: sm3 /day, FIELD: stb/day);
if the 3rd parameter is GIMPP, then limit on water rate should be specified
(METRIC: sm3 /day, FIELD: Msc f /day).
5. rate of fluid to add per unit of pressure difference (only with WIMPP or GIMPP
options) (METRIC: sm3 /day/bar , FIELD: stb/day/psi (for liquid) or Msc f /day/psi
(for gas)). Then import rate will be calculated via the following formula:
Q = R(Pe Ps ) while Pe > Ps ,
where
12.18.15. WSEGEXSS 1233

Q rate of fluid to add at surface conditions;

R rate of fluid to add per unit of pressure difference (this parameter of the
keyword);
Pe external pressure (6-th parameter of this keyword);
Ps segment pressure.
The import rate has an upper limit specified by 4-th parameter of this keyword;
6. external pressure (only for WIMPP or GIMPP) (METRIC: bar , FIELD: psi).
Default:
source/sink type: NONE;
rate value which is specified with option:
WIMPR 0;
GIMPR 0;
WIMPP no limit;
GIMPP no limit.
Example
WSEGEXSS
P1 9 WIMPR 350 /
/
Into the 9th segment of well P1 water will be added. Import rate value is 350 sm3 /day.
12.18.15. WSEGEXSS 1234

12.18.16 WSEGFLIM


Section
The keyword defines segment of multisegment well as a flow limiting valve.

Limiting valve is simulated as a device that limits the flow rate of fluid (at surface
conditions) through the segment to a specified maximum value. The effect is reaching by
exceeding this limit by sharply increasing the frictional pressure drop across the segment. It
is possible to limit two flows in one valve segment.
Frictional pressure drop in a segment is calculated via the following formula:
Pf = P1 + P2
where P1 = A1 (Q1 L1 ), P2 = A2 (Q2 L2 ).

Here:
A1 , A2 large coefficients to provide a promptly increasing pressure drop;
Q1 , Q2 flow of selected phase (see below) in the segment at a surface conditions;
L1 , L2 limit for values of Q1 and Q2 .
If coefficient L is negative, then corresponding value Pi is used to limit flows in injection

well.
Any number of data lines can be specified. Each of them should be ended by a symbol
One data line should contain:
1. well name (or name beginning, which ends by a *, i.e. a mask, or well list created via
WLIST (see 12.18.26));
2. segment number at the start of the interval (integer not less than 2);
3. segment number at the end of the interval (integer not less than 2);
4. first phase which flow is should be limited:
OIL oil total at surface conditions;

WAT water total at surface conditions;
GAS gas total at surface conditions;
12.18.16. WSEGFLIM 1235

LIQ liquid total at surface conditions;

NONE flow is not limited.
5. value of phase flow limit, which is specified by parameter 4 (METRIC: sm3 /day,
FIELD: stb/day);
6. coefficient A1 (in formula for pressure drop of the first phase). The larger the value,
then the operation of the valve is more effective in preventing the flow rate exceeding
the limit. Coefficient should be non-negative;
7. second phase which flow is should be limited:
OIL oil total at surface conditions;
WAT water total at surface conditions;
GAS gas total at surface conditions;
LIQ liquid total at surface conditions;
NONE flow is not limited.
8. value of phase flow limit, which is specified by parameter 7 (METRIC: sm3 /day,
FIELD: stb/day);
9. coefficient A2 (in formula for pressure drop of the first phase). The larger the value,
then the operation of the valve is more effective in preventing the flow rate exceeding
the limit. Coefficient should be non-negative;
10. flag to indicate whether the valve is open or shut:
OPEN opened;
SHUT shut; flow through the valve is absent.
Default:
first phase which flow is should be limited: NONE;
second phase which flow is should be limited: NONE;
If values of parameters 4 and 7 are equal to NONE, then flow limiting valve is not defined
for the segment.
Example
WSEGFLIM
WINJ 2 2 WAT -1000 10 /
/
In the example water flow limit for the 2nd segment of injection well WINJ is defined
as water flow limiting valve. Flow limiting will happen when injection rate will gain 1000
stb/day. Coefficient A1 is 10.
12.18.16. WSEGFLIM 1236

12.18.17 WFRICTN


Section
The keyword specifies a friction well. tNavigator will calculate for this well the frictional
pressure losses between the connections and the wells bottom hole reference point. This data
is taken into account in the connection head terms calculations.
This option can be used in multi-lateral and multisegment well simulation (section 2.19.4).
One keyword can specify only one well. Wells geometry should be previously defined via
the keyword COMPDAT (see 12.18.6).
The keyword consists of the following data: first data record (defines the well) and next
data records. Each data record should be terminated with a slash /. All data should be ter-
minated with a final /.
First data record:

2. tubing internal diameter (METRIC: m, FIELD: f t ). This parameter is used to calcu-
late the frictional pressure drop between the connections and the wells bottom hole
reference point (it can be not equal to the 9-th parameter of COMPDAT (see 12.18.6);
3. effective absolute roughness of the tubing (is used in the Fanning friction factor calcu-
lations) (METRIC: m, FIELD: f t );
4. flow scaling factor. In the friction pressure drop calculations the volumetric flow rate
in the wellbore is multiplied by the scaling factor.
Default:
flow scaling factor 1.
Second and other data records describe connections.
For horizontal well: each connection should be entered in the keyword just once, (individ-
ually or as part of a block range).
For multi-lateral well: the branches are defined with a special connections at each branch
point. If a connection is entered second time individually or as part of a block range, then
it is considered that the subsequent connections form a branch that joins the well at this
location. If the well is not perforated in the branch location point, then this block should be
marked as SHUT in COMPDAT (see 12.18.6).
Second and other data records:
12.18.17. WFRICTN 1237

1. I-coordinate of one connection (or I-coordinate of the connection at the start of the
range (nearest the wells bottom hole reference point));
2. J-coordinate of one connection (or J-coordinate of the connection at the start of the
3. K-coordinate of one connection (or K-coordinate of the connection at the start of the
4. distance down the tubing from the wells bottom hole reference point to the start of the
perforations in the grid block, specified via parameters 1-3 (METRIC: m, FIELD: f t );
5. distance down the tubing from the wells bottom hole reference point to the end of the
6. direction of penetration through the grid block or the block range (parameter 7): X (I),
Y (J), Z (K).
This parameter should be specified if the 5-th parameter is defaulted or the 7-th param-
eter specifies the block range;
7. I, J, or K coordinate of the grid block at the end of the range. Direction of penetration
is specified in the parameter 6;
8. tubing internal diameter for this one connection (or range of connections) (METRIC:
m, FIELD: f t ). This parameter is used in pressure loss calculations instead of value,
specified in 2-nd parameter in the first data record. This is a tool to enter different
diameters for branches in multi-lateral wells.
Default:
distance down the tubing from the wells bottom hole reference point to the start of the
perforations in the grid block, specified via parameters 1-3: For the first data line 0,
for next data lines the distance to the end of the previous connection or range;
distance down the tubing from the wells bottom hole reference point to the end of
the perforations in the grid block, specified via parameters 1-3: The sum of value of
parameter 4 and the thickness of the grid block in the direction of penetration, specified
via parameter 6;
tubing internal diameter for this one connection (or range of connections) 2-nd
parameter in the first data record.
12.18.17. WFRICTN 1238

Example
WELSPECS
WELL1 1* 10 22 2200 OIL /
/
COMPDAT
WELL1 7 22 8 8 OPEN 2* 0.2 3* X /
WELL1 8 22 8 8 OPEN 2* 0.2 3* X /
WELL1 9 22 8 8 OPEN 2* 0.2 3* X /
WELL1 10 22 8 8 OPEN 2* 0.2 3* X /
/
WFRICTN
WELL1 0.1 0.001 /
10 22 8 2* I 7 /
/
In this example horizontal WELL1 is specified. Well diameter is 0.2m (9-th parameter of
COMPDAT). Perforated blocks: from 7-th to 10-th in X-direction, in 8-th layer in Z-direction,
22-th layer in Y-direction.
The keyword WFRICTN specifies tubing internal diameter 0.1m. Effective absolute rough-
ness of the tubing 0.001m.
The penetration range is from 10-th to 7-th block in X-direction (in 8-th layer in Z-
direction, 22-th layer in Y-direction). The distance down the tubing from the wells bottom
hole reference point to the start (and end) of the perforations in the grid block is defaulted.
12.18.17. WFRICTN 1239

12.18.18 WFRICTNL


Section
The keyword specifies a friction well in local grid (LGR). tNavigator will calculate for
this well the frictional pressure losses between the connections and the wells bottom hole
reference point. This data is taken into account in the connection head terms calculations.
This option can be used in multi-lateral and multisegment well simulation (section 2.19.4).
One keyword can specify only one well. Wells geometry should be previously defined via
the keyword COMPDATL (see 12.18.7).
The keyword consists of the following data: first data record (defines the well) and next
data records. Each data record should be terminated with a slash /. All data should be ter-
minated with a final /.
First data record:

2. tubing internal diameter (METRIC: m, FIELD: f t ). This parameter is used to calcu-
late the frictional pressure drop between the connections and the wells bottom hole
reference point (it can be not equal to the 10-th parameter of COMPDATL (see 12.18.7);
3. effective absolute roughness of the tubing (is used in the Fanning friction factor calcu-
lations) (METRIC: m, FIELD: f t );
4. flow scaling factor. In the friction pressure drop calculations the volumetric flow rate
in the wellbore is multiplied by the scaling factor.
Default:
flow scaling factor 1.
Second and other data records describe connections.
For horizontal well: each connection should be entered in the keyword just once, (individ-
ually or as part of a block range).
For multi-lateral well: the branches are defined with a special connections at each branch
point. If a connection is entered second time individually or as part of a block range, then
it is considered that the subsequent connections form a branch that joins the well at this
location. If the well is not perforated in the branch location point, then this block should be
marked as SHUT in COMPDAT (see 12.18.6).
Second and other data records:
12.18.18. WFRICTNL 1240

1. name of LGR that contains the specified range of connections. Parameters 2, 3, 4, 8

below are in local grid coordinates;
2. I-coordinate of one connection (or I-coordinate of the connection at the start of the
3. J-coordinate of one connection (or J-coordinate of the connection at the start of the
4. K-coordinate of one connection (or K-coordinate of the connection at the start of the
5. distance down the tubing from the wells bottom hole reference point to the start of the
6. distance down the tubing from the wells bottom hole reference point to the end of the
7. direction of penetration through the grid block or the block range (parameter 7): X (I),
Y (J), Z (K).
This parameter should be specified if the 5-th parameter is defaulted or the 7-th param-
eter specifies the block range;
8. I, J, or K coordinate of the grid block at the end of the range. Direction of penetration
is specified in the parameter 6;
9. tubing internal diameter for this one connection (or range of connections) (METRIC:
m, FIELD: f t ). This parameter is used in pressure loss calculations instead of value,
specified in 2-nd parameter in the first data record. This is a tool to enter different
diameters for branches in multi-lateral wells.
Default:
distance down the tubing from the wells bottom hole reference point to the start of the
perforations in the grid block, specified via parameters 1-3: For the first data line 0,
for next data lines the distance to the end of the previous connection or range;
distance down the tubing from the wells bottom hole reference point to the end of
the perforations in the grid block, specified via parameters 1-3: The sum of value of
parameter 4 and the thickness of the grid block in the direction of penetration, specified
via parameter 6;
tubing internal diameter for this one connection (or range of connections) 2-nd
parameter in the first data record.
Example
WFRICTN
WELL1 0.1 0.001 /
LGR1 10 22 8 2* I 7 /
/
12.18.18. WFRICTNL 1241

12.18.19 WFRICSEG / WFRICSGL


Section
This keyword is used to define the segment structure and the connection locations of a
multisegment well via parameters of the keyword WFRICTN (see 12.18.17) (WFRICTN (see
12.18.17) for LGR case). WFRICSEG (WFRICSGL (see 12.18.19) for LGR case) provides an
easy way of transformation a friction well into a multisegment well by changing the keyword
name to WFRICSEG (WFRICSGL (see 12.18.19)).
Friction wells and multisegment wells cant exist in the same run. If this keyword is used,
then all friction wells should be converted.
Parameters of the keyword WFRICSEG (see 12.18.19) (WFRICSGL (see 12.18.19)) is
analogous to the keyword WFRICTN (see 12.18.17) (WFRICTN (see 12.18.17)) ones.
Example
WELSPECS
WELL1 1* 10 22 2200 OIL /
/
COMPDAT
WELL1 7 22 8 8 OPEN 2* 0.2 3* X /
WELL1 8 22 8 8 OPEN 2* 0.2 3* X /
WELL1 9 22 8 8 OPEN 2* 0.2 3* X /
WELL1 10 22 8 8 OPEN 2* 0.2 3* X /
/
WFRICSEG
WELL1 0.1 0.001 /
10 22 8 2* I 7 /
/
In this example horizontal WELL1 is specified. Well diameter is 0.2m (9-th parameter of
COMPDAT). Well segments: from 7-th to 10-th in X-direction, in 8-th layer in Z-direction,
22-th layer in Y-direction.
The keyword WFRICTN specifies tubing internal diameter 0.1m. Effective absolute rough-
ness of the tubing 0.001m.
The penetration range is from 10-th to 7-th block in X-direction (in 8-th layer in Z-
direction, 22-th layer in Y-direction). The distance down the tubing from the wells bottom
hole reference point to the start (and end) of the perforations in the grid block is defaulted.
12.18.19. WFRICSEG / WFRICSGL 1242

12.18.20 COMPSEGS


Section
The keyword specifies completions in a multisegment well (section 2.19.4). One keyword
can specify only one well. The well should be previously defined via the keyword WEL-
SPECS (see 12.18.3) (WELSPECL (see 12.18.4)) and the segment structure WELSEGS
(see 12.18.11).
The keyword consists of the following data: first data record defines the well, next data
records defines location of well connections in grid blocks. Each data record should be ter-
minated with a slash /. All data should be terminated with a final /.
First data record

1. well name (or well number) (should be terminated with /).
Second and other data records.
These records specify the start and end of connections perforations as a distance along
the tubing from the wells zero tubing length reference point, and the branch number. The
zero tubing length reference point is specified relative to the nodal point of the top segment
(parameter 3 of the first record of WELSEGS (see 12.18.11). All connections should be
defined via COMPDAT (see 12.18.6).
All connections can be specified individually, or in ranges. A range a row (column)

of grid blocks that are fully penetrated by this branch of the well. (The well penetrates a
range perpendicularly through the center of each grid block in the direction, specified via this
keyword). The distance along well bore to the start and end of each connection in the range
is calculated as sum of DX, DY or DZ thicknesses of the grid blocks in this range.
1. X-coordinate (i) of one connection, or the connection at the start of the range (nearest
the tubing head);
2. Y-coordinate (j) of one connection, or the connection at the start of the range (nearest
the tubing head);
3. Z-coordinate (k) of one connection, or the connection at the start of the range (nearest
the tubing head);
4. branch number (where this connection or range is situated);
12.18.20. COMPSEGS 1243

5. length down the well bore from the wells zero tubing length reference point to the
start of the connection in this grid block (METRIC: m, FIELD: f t );
6. length down the well bore from the wells zero tubing length reference point to the end
of the connection in this grid block (METRIC: m, FIELD: f t );
7. penetration direction of the grid block or the range (this parameter should be specified
if parameter 6 of this keyword is defaulted, or if the range is specified in parameter 8):
X (or I) horizontal penetration in X-axis direction;

Y (or J) horizontal penetration in Y-axis direction;
Z (or K) vertical penetration in Z-axis direction;
8. i, j or k grid block coordinate at the end of the range (depends on penetration direction
specified via parameter 7);
9. depth of the well connections within the range (METRIC: m, FIELD: f t ), i.e. the depth
of the center of the perforations within each grid block in the range. Default or zero
value then the depth of perforation intervals are calculated according to the segment
data (with depth of start and end of the segment and the place inside the perforation).
Negative depth of intervals of perforations their previous values are used (equal to
the depth of blocks centers and specified via COMPDAT (see 12.18.6)).
10. thermal contact length (length of the well in the completion cell), IGNORED, this is
an Eclipse compatibility field;
11. segment number to allocate to all connections within the specified range. If this pa-
rameter is zero or negative, then the grid block connection is allocated to the segment,
which nodal point is near to the center of connection. If a segment number is specified
then it is used.
Default:
length down the well bore from the wells zero tubing length reference point to the start
of the connection in this grid block (m) zero (for first data record) and the distance
to the end of the previous connection or range (for other records);
length down the well bore from the wells zero tubing length reference point to the end
of the connection in this grid block (m) parameter 5 plus thickness of the grid block
in penetration direction;
depth of the well connections within the range (m) zero.
segment number to allocate to all connections in the specified range 0.
12.18.20. COMPSEGS 1244

Example
COMPSEGS
'PROD'/
1 1 2 2 30 1* 'X' 5 /
/
In this example for the well PROD coordinates of connection (1, 1, 2) are specified. This
connection is situated on branch number 2. Length down the well bore from the wells zero
tubing length reference point to the start of the connection in this grid block 30m. Length
down the well bore from the wells zero tubing length reference point to the end of the
connection in this grid block default value. Penetration direction - X. i-coordinate of grid
block at the end of the range 5.
12.18.20. COMPSEGS 1245

12.18.21 COMPSEGL


Section
The keyword specifies completions in a multisegment well (section 2.19.4) in local grid
LGR.
One keyword can specify only one well. The well should be previously defined via the
keyword WELSPECL (see 12.18.4) and the segment structure WELSEGS (see 12.18.11).
All the parameters of this keyword are identical to parameters of COMPSEGS (see
12.18.20). Additionally in the second and other data records name of LGR should be speci-
fied. Parameters 2, 3, 4, 8 are in local grid coordinates.
Example
COMPSEGL
'PROD'/
LGR1 1 1 2 2 30 1* 'X' 5 /
/
12.18.21. COMPSEGL 1246

12.18.22 COMPLUMP


Section
This keyword lumps connections together into completions to provide realization of

simultaneous actions. Completions numbers could be used in the keywords WPIMULT
(see 12.18.28), WELOPEN (see 12.18.107), WBHZONE (see 12.18.130), WPIFUNC
(see 12.18.128), WSKFUNC (see 12.18.129). Connections should first have been defined
with the keyword COMPDAT (see 12.18.6). When a connection is first defined with COMP-
DAT (see 12.18.6), it is given a completion number equal to its order of introduction in the
well. If the keyword COMPLUMP (see 12.18.22) is not used, each connection is in its own
separate completion and the terms completion and connection are equivalent.
Any number of data records could be specified. Each record should be terminated with a
Each record should contain the following parameters:
1. well name (or number) or well list WLIST (see 12.18.26);
2. connection coordinate in X direction;
3. connection coordinate in Y direction;
4. coordinate of upper connection block in this completion;
5. coordinate of lower connection block in this completion;
6. completion number of these connections.

Default:
connection coordinate in X direction 0 (any value);
connection coordinate in Y direction 0 (any value);
coordinate of upper connection block in this completion 0 (the top connection of this
well);
coordinate of lower connection block in this completion 0 (the bottom connection of

this well);
The set of connections in the well which match the location indexes specified in pa-
rameters 2-5 will be given the completion number specified in parameter 6. All connections
having the same number of completion are treated as belonging to the same completion and
12.18.22. COMPLUMP 1247

can be used together in the keywords WPIMULT (see 12.18.28), WBHZONE (see 12.18.130),
WPIFUNC (see 12.18.128), WSKFUNC (see 12.18.129).
If a location index is defaulted to zero, it plays no part in selecting the set of connections.
Thus if X and Y coordinates are defaulted to zero, all connections in the well that are located
between layers specified in parameters 4 and 5 will be given the completion number specified
in parameter 6. If all four location indexes are defaulted, all the wells connections will be
given this completion number.
Example
COMPLUMP
WELL5 2* 1 10 1 /
WELL5 2* 11 28 2 /
/
In this example for well WELL5: connections from layer 1 to 10 (Z direction) have the
completion number 1, connections from layer 11 to 28 have the completion number 2.
12.18.22. COMPLUMP 1248

12.18.23 COMPLMPL


Section
This keyword lumps connections together into completions to provide realization of si-
multaneous actions for the wells in local grids (section 5.6). Completions numbers could be
used in the keywords WPIMULT (see 12.18.28), WELOPENL (see 12.18.108). Connections
should first have been defined with the keyword COMPDATL (see 12.18.7). When a connec-
tion is first defined with COMPDATL (see 12.18.7), it is given a completion number equal to
its order of introduction in the well. If the keyword COMPLMPL (see 12.18.23) is not used,
each connection is in its own separate completion and the terms completion and connection
are equivalent.
COMPLMPL must be used in place of COMPLUMP (see 12.18.22) to lumps connections

together into completions for wells in local refined grids, after the wells have been introduced
with keywords WELSPECL (see 12.18.4), COMPDATL (see 12.18.7). The keyword data for
COMPLMPL is the same as for COMPLUMP (see 12.18.22), except for an extra parameter
2 which names the local grid containing the connections specified in the record.
1. well name (or number) or well list WLIST (see 12.18.26);
2. local grid name (CARFIN (see 12.2.87));
3. connection coordinate in X direction;
4. connection coordinate in Y direction;
5. coordinate of upper connection block in this completion;
6. coordinate of lower connection block in this completion;
7. completion number of these connections.
Default:
connection coordinate in X direction 0 (any value);
connection coordinate in Y direction 0 (any value);
12.18.23. COMPLMPL 1249

coordinate of upper connection block in this completion 0 (the top connection of this
well);
coordinate of lower connection block in this completion 0 (the bottom connection of

this well);
The set of connections in the well which match the location indexes specified in pa-
rameters 3-6 will be given the completion number specified in parameter 7. All connections
having the same number of completion are treated as belonging to the same completion and
can be used together in the keywords WPIMULT (see 12.18.28).
If a location index is defaulted to zero, it plays no part in selecting the set of connections.
Thus if X and Y coordinates are defaulted to zero, all connections in the well that are located
between layers specified in parameters 5 and 6 will be given the completion number specified
in parameter 7. If all four location indexes are defaulted, all the wells connections will be
given this completion number.
Example
COMPLMPL
WELL5 LGR3 2* 1 10 1 /
WELL5 LGR3 2* 11 28 2 /
/
In this example for well WELL5 (situated in local grid LGR3): connections from layer 1
to 10 (Z direction) have the completion number 1, connections from layer 11 to 28 have the
completion number 2.
12.18.23. COMPLMPL 1250

12.18.24 COMPORD


Section
The keyword specifies the order of well connections.
The connection order determines which connections will be closed in a +CON workover
(parameter 7 of the keyword WECON (see 12.18.62)). In these workovers, all connections
below (further from the wellhead according to the connection order) the offending one will
be closed.
2. method for ordering wells connections:
DEPTH Connections order: according to their depth (from top downward). Con-
nections with the same depth will be ordered in the sequence they are declared in
COMPDAT (see 12.18.6) (or COMPDATL (see 12.18.7)).
INPUT Connections order: according to their declaration in COMPDAT (see
12.18.6) (or COMPDATL (see 12.18.7)).
LASTINPT Analogous to INPUT, but in case if the connection is defined the
second time, is will be removed from its place and moved to the end of connection
list (this type of ordering is used to read MORE models).
TRACK Connections order: according to tracing the well track through the grid
from the grid blocks where these connections are located. If all connections are
vertical (according to parameter 13 of COMPDAT (see 12.18.6), connections or-
der: according to DEPTH (see 12.3.27). If any connection has X- or Y-direction,
connections are ordering with the following rule: the connection whose I,J coor-
dinates are nearest the wellhead I,J (parameters 3,4 of the keyword WELSPECS
(see 12.18.3), WELSPECL (see 12.18.4)) is taken. If more than one connection
can be taken with this rule, the one with the minimum depth is selected. The rest
of the ordering is according to the location and orientation of connections.
Default: TRACK.
12.18.24. COMPORD 1251

Example
COMPORD
PROD1 INPUT /
PROD2 INPUT /
INJ17 DEPTH /
/
The differences between INPUT and LASTINPT.
Example
COMPDAT
'W' 1 1 3 3 /
'W' 1 1 5 5 /
/
...
COMPDAT
'W' 1 1 1 1 /
'W' 1 1 3 3 /
'W' 1 1 5 5 /
/
In this case if one uses INPUT the ordering will be 3 -> 5 -> 1, if one uses LASTINPT
the ordering will be 1 -> 3 -> 5.
12.18.24. COMPORD 1252

12.18.25 COMPINJK


Section
The keyword is used to specify the injection well relative permeabilities.
For injecting well connections the mobility of the injected phase is varied as the total
fluid mobility in the grid block:
kr (O, j) r (W, j) kr (G, j)
(O, j) + k(W, j) + (G, j)
M(P, j) =
B(P, j)
where:
(P, j) phase P viscosity,
B(P, j) phase P formation volume factor,
kr (P, j) relative phase P permeability.
If gas or water is injected into a grid block (which contains oil), this relationship causes
wells injectivity to vary until the grid block will be full of injected phase. In real field most
of the pressure drop is over a region near the well, and when this region is full of injected
phase the injectivity stays constant. In case when this region size is smaller than the grid
block size, the calculated injectivity might be incorrect until the whole grid block will be full
of injected phase.
When this keyword is used the well injects the fluid whose mobility is different from
mobility of the fluid initially in the block, and grid blocks (containing the well) are large.
Injected phase mobility:
kr (P, )
M(P, j) =
(P, j)B(P, j)
where:
kr (P, ) relative permeability of the injected phase (a constant value specified via this
keyword) (relative permeability in the region that is full of injected phase);
relative permeabilities of other phases are zero.

12.18.25. COMPINJK 1253

1. well name (or well list specified via WLIST (see 12.18.26));
2. X-coordinate of well connection;
3. Y-coordinate of well connection;
4. Z-coordinate of upper well connection;
5. Z-coordinate of lower well connection;
6. relative permeability of the injected phase (positive value). This value is applied to all
connections specified by parameters 2-5. If 0 value is specified the calculations will be
as without this keyword.
Default:
1. well name (or well list specified via WLIST (see 12.18.26)) no default value;
2. X-coordinate of well connection 0 (any value);
3. Y-coordinate of well connection 0 (any value);
4. Z-coordinate of upper well connection 0 (any value);
5. Z-coordinate of lower well connection 0 (any value);
6. relative permeability of the injected phase in case of default or negative value relative
permeability of the injected phase will be taken from saturation table, used by this
connection and depending on the injected phase:
krW (SW = 1 SOW cr SGco ), for water injectors;
krG (SG = 1 SOGcr SW co ), for gas injectors.
Example
COMPINJK
WELL1 4* 1.0 /
/
In this example for all WELL1 connections (all connection coordinates are defaulted)
relative permeability of the injected phase is set to 1.
12.18.25. COMPINJK 1254

12.18.26 WLIST


Section
The keyword is used to specify well lists. These well lists can be used in schedule section
keywords to specify several wells at once.
1. well list name (first character should be *);
2. operation:
NEW new well list is started with the name specified in 1-st parameter. The
following well names are put in this list (these wells shouldnt be members of any
other list);
ADD adds the following well names to this list (these wells shouldnt be mem-
bers of any other list);
MOVE moves the following well names to this list specified in parameter 1
(they are added to the end of the list, specified in parameter 1);
DEL removes the following well names from this list.
3. list of well names. Wells should be specified via WELSPECS (see 12.18.3). If an
operation DEL is used only full well names should be entered. If NEW, ADD are used
both well names and well masks could be entered.
Example
WLIST
'*L1' NEW W1 W3 W17 W22 /
'*L2' NEW W2 W6 W12 W14 W18 /
/
WELOPEN
'*L1' OPEN /
'*L2' OPEN /
/
WLIST
'*L1' ADD W19 W13 /
/
12.18.26. WLIST 1255

In this example two well lists are created L1 and L2. All wells are opened via the
keyword WELOPEN (see 12.18.107). Then 2 wells are added to the list L1.
12.18.26. WLIST 1256

12.18.27 WLISTDYN


Section
The keyword sets dynamic wells list. Such lists refresh automatically at the end of each
timestep. Belonging of a well to this list is defining by a specified condition.
1. well list name in quotes (first character should be *);
2. well group name or mask. All wells of this group (or these groups) are wells of this
list at initial timestep;
3. quantity for well, defining list membership. The following quantities are supported:
WOPR Well oil production rate;

WOPT Well oil production total;
WOIR Well oil injection rate;
WOIT Well oil injection total;
WWPR Well water production rate;
WWPT Well water production total;
WWIR Well water injection rate;
WWIT Well water injection total;
WGPR Well gas production rate;
WGPT Well gas production total;
WGIR Well gas injection rate;
WGIT Well gas injection total;
WLPR Well liquid production rate;
WLPT Well liquid production total;
WVPR Well voidage production rate;
WVPT Well voidage production total;
WVIR Well voidage injection rate;
12.18.27. WLISTDYN 1257

WVIT Well voidage injection total;

WGOR Well gas oil ratio;
WWCT Well water cut;
WWGR Well water gas ratio;
WBHP Well bottom hole pressure (production type quantity);
WTHP Well tubing head pressure (production type quantity).
4. comparison or selection operator:
>;
<;
HIGHEST;
LOWEST;
5. number n. If operator > or < is specified in 4-th parameter, then 3-rd parameter value
will be compared with n. If operator HIGHEST or LOWEST is specified in 4-th
parameter, then n top (or bottom) wells by parameter 3 will be included to list.
Example
WLISTDYN
'*WCTHIGH' ' FIELD' ' WWCT' HIGHEST'
' 5 /
/
In the example dynamic well list *WCTHIGH is specified. It contains 5 wells of all field
with the highest watercut.
12.18.27. WLISTDYN 1258

12.18.28 WPIMULT


Section
This keyword is used to multiply well connection transmissibility factors by specified

value. A set of data for every well should be terminated with a slash /. The following
parameters are to be specified:
1. well name (or number) or well list WLIST (see 12.18.26),
2. connection transmissibility factor multiplier,
3. perforated interval coordinate in X direction, this is i in 5.7.1,
4. perforated interval coordinate in Y direction, this is j in 5.7.1,
5. perforated interval coordinate in Z direction, this is k in 5.7.1.
6. number of first completion in range (completion numbers are set via COMPLUMP (see
12.18.22)),
7. number of last completion in range (completion numbers are set via COMPLUMP (see
12.18.22)).
If WPIMULT is used several times for the same connection transmissibility factor (such
specifications of WPIMULT should be separated by keywords DATES (see 12.18.105) or
TSTEP (see 12.18.106)), its effect is cumulative, i.e. multiplying factor is applied each time
the keyword is entered.
If a COMPDAT (see 12.18.6) keyword contains data inducing transmissibility factor
recalculation, multiplier previously defined by WPIMULT is reset to 1.0.
Default:
connection transmissibility factor multiplier 1.0,
coordinate in X direction any,
coordinate in Y direction any,
coordinate in Z direction any,
number of first completion in range any,
number of last completion in range any.
12.18.28. WPIMULT 1259

Note:
The keyword WPIMULT has different behavior for model E100 and E300 formats in the case
below. If at one time step there are several WPIMULT keywords with defaulted parameters
then only the last one is used in E100 format, but all of them are used in E300 format. See
example 1.
Example 1
Example
WPIMULT
W1 1.1 3* /
W1 0.7 3* /
W1 1.2 3* /
/
Example 2
Example
DIMENS
25 20 3
...
DATES
1 JUN 2003
/
COMPDAT
1043 14 10 1 2 OPEN 1* 5 /
1044 20 10 1 1 OPEN 8* /
/
...
DATES
1 JUN 2004
/
WPIMULT
1043 2 14 10 1 /
1044 2 20 10 1 /
/
...
DATES
1 JUN 2005
/
WPIMULT
1043 0.25 14 10 1 /
1044 2 /
1020 2 1 /
/
12.18.28. WPIMULT 1260

In this example on the 1st of June, 2003 new completions are specified for wells 1043
and 1044. For well 1043 completion factor is specified explicitly and is equal to 5. In a year
completion factors for both wells in the first layer are multiplied by 2; so, completion factor
for well 1043 is now equal to 10.
In one more year it is multiplied again on 0.25 and becomes equal to 2.5. At the same
time completion factors for all completions of well 1044 are multiplied by 2, and for well
1020 only those with i-coordinate equal to 1 are doubled.
12.18.28. WPIMULT 1261

12.18.29 WPIMULTL


Section
This keyword is used to multiply well connection transmissibility factors by specified

value for the wells in local grids (section 5.6). A set of data for every well should be termi-
WPIMULTL must be used in place of WPIMULT (see 12.18.28) to multiply well connec-
tion transmissibility factors by specified value for wells in local refined grids, after the wells
have been introduced with keywords WELSPECL (see 12.18.4), COMPDATL (see 12.18.7).
The keyword data for WPIMULT is the same as for WPIMULT (see 12.18.28), except for
an extra parameter 3 which names the local grid containing the connections specified in the
record.
2. connection transmissibility factor multiplier,
4. perforated interval coordinate in X direction, this is i in 5.7.1,
5. perforated interval coordinate in Y direction, this is j in 5.7.1,
6. perforated interval coordinate in Z direction, this is k in 5.7.1.
7. number of first completion in range (completion numbers are set via COMPLMPL (see
12.18.23)),
8. number of last completion in range (completion numbers are set via COMPLMPL (see
12.18.23)).
If WPIMULTL is used several times for the same connection transmissibility factor (such
specifications of WPIMULTL should be separated by keywords DATES (see 12.18.105) or
TSTEP (see 12.18.106)), its effect is cumulative, i.e. multiplying factor is applied each time
the keyword is entered.
If a COMPDATL (see 12.18.7) keyword contains data inducing transmissibility factor
recalculation, multiplier previously defined by WPIMULTL is reset to 1.0.
Default:
12.18.29. WPIMULTL 1262

connection transmissibility factor multiplier 1.0,
coordinate in X direction any,
coordinate in Y direction any,
coordinate in Z direction any,
number of first completion in range any,
number of last completion in range any.
Note:
The keyword WPIMULTL has different behavior for model E100 and E300 formats in the
case below. If at one time step there are several WPIMULTL keywords with defaulted pa-
rameters then only the last one is used in E100 format, but all of them are used in E300
format. See example 1.
Example 1
Example
WPIMULT
W1 1.1 'LGR1' 3* /
W1 0.7 'LGR1' 3* /
W1 1.2 'LGR1' 3* /
/
Example 2
12.18.29. WPIMULTL 1263

Example
DIMENS
25 20 3
...
DATES
1 JUN 2003
/
COMPDATL
1043 'LGR1' 14 10 1 2 OPEN 1* 5 /
1044 'LGR1' 20 10 1 1 OPEN 8* /
/
...
DATES
1 JUN 2004
/
WPIMULTL
1043 'LGR1' 2 14 10 1 /
1044 'LGR1' 2 20 10 1 /
/
...
DATES
1 JUN 2005
/
WPIMULTL
1043 'LGR1' 0.25 14 10 1 /
1044 'LGR1' 2 /
1020 'LGR1' 2 1 /
/
In this example on the 1st of June, 2003 new completions are specified for wells 1043 and
1044 (situated in local grid LGR1). For well 1043 completion factor is specified explicitly
and is equal to 5. In a year completion factors for both wells in the first layer are multiplied
by 2; so, completion factor for well 1043 is now equal to 10.
In one more year it is multiplied again on 0.25 and becomes equal to 2.5. At the same
time completion factors for all completions of well 1044 are multiplied by 2, and for well
1020 only those with i-coordinate equal to 1 are doubled.
12.18.29. WPIMULTL 1264

12.18.30 WPITAB


Section
The keyword can be used to assign PI multiplier table to the well. The tables scale the
wells connection factors according to the maximum water cut it achieved. Tables are speci-
fied via the keyword PIMULTAB (see 12.18.31).
An arbitrary number of data lines can be entered. Each data line should be followed by a
The following parameters should be entered in each data line:
1. well name (or number) or well mask, which defines a subset of wells or well list
WLIST (see 12.18.26);
2. PI multiplier table number, (tables are specified via PIMULTAB (see 12.18.31)). Zero
or negative value of this parameter means that no PI multiplier table is assigned to the
well.
Default:
PI multiplier table number 0.
Example
WPITAB
W1 1 /
W1 2 /
/
12.18.30. WPITAB 1265

12.18.31 PIMULTAB


Section
The keyword can be used to specify PI multiplier tables, that are used to scale well con-
nection factors according to the maximum watercut it has achieved. The tables are assigned
to the wells via the keyword WPITAB (see 12.18.30).
1. maximum watercut (METRIC: sm3 /sm3 , FIELD: stb/stb);
2. corresponding value of PI scaling factor.
Empty table, that contains only a slash /, are considered as the copy of previous table.
Example
PIMULTAB
0 1
0.2 0.86
0.3 0.44
0.7 0.39 /
12.18.31. PIMULTAB 1266

12.18.32 COMPRP


Section
This keyword specifies the data for rescaling saturations at wells connections (well con-
nections should be previously defined via COMPDAT (see 12.18.6)).
The set of data for each well should be terminated with a slash /. All data should be
For each well the following parameters should be specified:
2. X-coordinate of connection i number of grid block;
3. Y-coordinate of connection j number of grid block;
4. Z-coordinate of upper connection k number of grid block;
5. Z-coordinate of lower connection k number of grid block;
6. saturation table number for connection relative permeabilities (connections are specified
via parameters 2-5). If 0 or positive value is specified, then it will override the saturation
table number specified in the 7-th parameter of COMPDAT (see 12.18.6). In case with
hysteresis this number is used in both imbibition and drainage processes.
7. SWMIN scaled value of the minimum water saturation;
8. SWMAX scaled value of the maximum water saturation;
9. SGMIN scaled value of the critical gas saturation;
10. SGMAX scaled value of the maximum gas saturation.
Default:
X-coordinate of connection all possible i numbers of grid block;
Y-coordinate of connection all possible j number of grid block;
Z-coordinate of upper and lower connection all possible k number of grid block; If
all coordinates i, j, k are defaulted, then all well connections will be considered;
12.18.32. COMPRP 1267

saturation table number for connection relative permeabilities negative (data specified
via 7-th parameter of COMPDAT (see 12.18.6) are not overridden).
SWMIN scaled value of the minimum water saturation SW c ;
SWMAX scaled value of the maximum water saturation 1 SOW cr (for three-phase
cases or water-oil systems) or 1 SGcr (for gas-water systems);
SGMIN scaled value of the critical gas saturation SGcr ;
SGMAX scaled value of the maximum gas saturation 1 SOGcr SW c .
Example
COMPRP
W1 1* 1* 5 20 1 /
W2 4* 3 /
/
In this example for well W1 for all connections in layers from 5 to 25 the saturation table
number 1 is used. For all connections of the well W2 saturation table number 3 is used.
12.18.32. COMPRP 1268

12.18.33 WINJMULT


Section
The keyword specifies pressure-dependent injectivity multipliers. These injectivity multi-

pliers can be used simulate approximately account of hydraulic fracturing at injectors.
Fluid mobility at each well connection is multiplied by a factor:
1 + a(Pw Pf )
if Pw > Pf or multiplied by 1, if Pw < Pf .
Where:
a multiplier gradient (parameter 3 of this keyword);
Pw instantaneous value of the well BHP or the wellbore pressure adjacent to the
individual connections (see parameter 4 of this keyword);
Pf fracturing pressure (parameter 2 of this keyword).
An arbitrary amount of data lines can be entered (terminated with a slash /). All data
1. well name (or number) or well list, specified via WLIST (see 12.18.26),
2. Pf fracturing pressure (METRIC: barsa, FIELD: psia),
3. a multiplier gradient (METRIC: 1/bars, FIELD: 1/psi),
4. mode of operation:
WREV All connections have the same injectivity multiplier, which determined
by BHP. Parameters 5 - 7 are ignored. Injectivity increase is reversed if the BHP
subsequently declines.
CREV Injectivity multiplier is applied to connections defined by parameters 5 - 7,
and is determined by the wellbore pressure adjacent to each connection. Injectivity
increase is reversed for all connections if the wellbore pressure subsequently
declines.
12.18.33. WINJMULT 1269

CIRR Injectivity multiplier is applied to connections defined by parameters 5 - 7,

and is determined by the wellbore pressure adjacent to each connection. Injectivity
increase is not reversed for all connections. Connections continue working with
its maximum attained injectivity multiplier.
5. i-coordinate of grid block with connection,
6. j-coordinate of grid block with connection,
7. k-coordinate of grid block with connection.
Default:
Pf fracturing pressure can be defaulted only if multiplier gradient is defaulted,
a multiplier gradient (1/bars) 0,
mode of operation: WREV,
i-coordinate of grid block with connection negative (allows any value),
j-coordinate of grid block with connection negative (allows any value),
k-coordinate of grid block with connection negative (allows any value).
Example
WELL1 350 0.0044 /
WELL2 340 0.0041 CIRR 0 0 7 /
/
In this example the well WELL1 uses the mode WREV (all connections have the same
reversible injectivity multiplier). WELL2 has its own irreversible injectivity multiplier for
connections in the 7-th layer.
12.18.33. WINJMULT 1270

12.18.34 WCONPROD


Section
This keyword could be specified for a well or a group of wells that work as producing.
A set of data for every well should be terminated with a slash /.

1. well name (or number), or well list WLIST (see 12.18.26),
2. well working mode (OPEN, STOP, SHUT or AUTO - well connection will open auto-
matically when the value of oil saturation runs up to WELSOMIN (see 12.18.2)),
3. well control:
LRAT liquid rate control,

ORAT oil rate control,
WRAT water rate control,
GRAT gas rate control,
WGRA wet gas rate control (only for E300 format models),
RESV reservoir liquid rate control,
THP tubing head pressure control or
BHP bottom hole pressure control;
TMRA total molar rate control;
STRA steam rate control (only for thermal E300 models);
SATP water saturation pressure control (see parameter 16; only for thermal
E300 models);
SATT water saturation temperature control (see parameter 17; only for thermal
E300 models);
CVAL calorific rate control (only for E300 models);
NGL NGL rate control (only for E300 models);
GRUP control of group rate wells fracture. Group rate value is specified via
the keyword GCONPROD (see 12.18.72).
12.18.34. WCONPROD 1271

4. oil rate (or upper limit) (METRIC: sm3 /day, FIELD: stb/day),
5. water rate (or upper limit) (METRIC: sm3 /day, FIELD: stb/day),
6. gas rate (or upper limit) (METRIC: sm3 /day, FIELD: Msc f /day),
7. liquid rate on the surface (or upper limit) (METRIC: sm3 /day, FIELD: stb/day),
8. liquid rate in reservoir conditions (or upper limit) (METRIC: rm3 /day, FIELD:
rb/day),
9. BHP value or lower limit (METRIC: barsa, FIELD: psia),
10. THP value or lower limit (METRIC: barsa, FIELD: psia). A zero value will prevent
the well switching to THP control, whatever the value of its calculated THP (VFP table
number should be specified in next parameter of this keyword),
11. well VFP table number (VFPPROD (see 12.18.57), VFPCORR (see 12.18.61)); if zero,
THP will not be reported.
12. artificial lift quantity (ALQ), that will be used in THP calculations (see the keyword
VFPPROD (see 12.18.57));
13. wet gas production rate (or upper limit) (METRIC: sm3 /day, FIELD: Msc f /day);
14. total molar rate (or upper limit) (METRIC: kg.M/day, FIELD: lb.M/day);
15. steam production (or upper limit), CWE cold water equivalent) (METRIC: sm3 /day,
FIELD: stb/day). This parameter can be used only in THERMAL (see 12.1.50) runs.
Can be specified by user via UDQ (see 12.18.138).
16. pressure offset for saturation pressure control P (METRIC: bar , FIELD: psia). This
parameter can be used only in THERMAL (see 12.1.50) runs. Can be specified by user
via UDQ (see 12.18.138).
The constraint for BHP is BHP Psat + P, where Psat is maximum saturated water
pressure in all blocks with prodicing connections;
17. temperature offset for saturation temperature control T (METRIC: C , FIELD: F ).

This parameter can be used only in THERMAL (see 12.1.50) runs. Can be specified
by user via UDQ (see 12.18.138).
The constraint for BHP is BHP Psat (T + T ), where T is maximum temperature in
all blocks with prodicing connections;
18. calorific rate (or upper limit) (METRIC: kJ/day, FIELD: BTU/day),
19. linearly combined rate target or upper limit; IGNORED, this is an Eclipse compatibility
field;
12.18.34. WCONPROD 1272

20. natural gas liquid (NGL) rate (or upper limit) (METRIC: sm3 /day, FIELD: stb/day).
User should specify well control and, if needed, rate and pressure limits. If limit is not
set or set to zero, default value will be used. Well is first set to control specified by user.
Then all limits are checked, if one of them is violated, well will switch to corresponding
control. Limits check will proceed until all of them are satisfied. If well produces negative
rate according to its current control, it is closed. Otherwise simulator will make step with
this control. Next step the procedure is repeated. Bottom hole pressure pBH for rate control
wells and rates for pressure control wells are calculated from (2.106).
All well control switching times are logged, REPORTFILE / REPORTSCREEN
(see 12.1.3).
Default:
well status: OPEN;
liquid rate upper limit: 1e + 20 m 3 / day;
BHP limit: for E100 format models patm = 14.7 psia (atmosphere pressure), for
E300 format models 100 atma = 1470 psia;
THP value or lower limit: 0;
well VFP table number: 0;
artificial lift quantity: 0.
Example
WCONPROD
1043 OPEN LRAT 18.19 0 0 18.99 2* /
1054 OPEN ORAT 16.38 1.765 0 18.14 1* 50 /
/
This example sets controls for two wells. Well 1043 is on liquid rate control; total liquid
rate in surface conditions is 18.99. There is no bottom hole pressure limit, so the simulator
will set liquid production equal to 18.99; if calculated pressure is lower than atmospheric
(default bottom hole limit is atmospheric pressure), then the well will switch to bottom hole
pressure control. If calculated oil rate is above 18.19, well will switch to oil rate control.
Well 1054 is on oil rate 16.38 control. There is a BHP limit for this well, equal to 50;
so, if pressure goes below 50, the well will automatically switch to BHP control. Liquid and
water controls are also checked each time; if one of them is violated, well is switched to
corresponding control.
Example
WCONPROD
43 OPEN BHP 18.19 0 0 18.9 1* 55 /
54 OPEN BHP 16.38 1.765 0 1* 1* 45 /
/
12.18.34. WCONPROD 1273

In this example both wells are on BHP control. In this case rates are calculated by
simulator. If liquid rate for well 43 exceeds 18.9, it will switch to LRAT control. If oil rate
exceeds 18.19, well will switch to ORAT control.
Correspondingly, if water rate for well 54 exceeds 1.765 (or oil rate exceeds 16.38), it
will switch to WRAT control (correspondingly, ORAT control).
12.18.34. WCONPROD 1274

12.18.35 WCONHIST


Section
This keyword may be specified for a well or a group of wells (instead of the keyword
WCONPROD (see 12.18.34)) that work as producers and are being history matched. The
keyword WCONINJH (see 12.18.39) is used for wells that work as injectors and are being
history matched.

2. well status (OPEN, STOP or SHUT),
3. well control:
LRAT liquid rate control,

ORAT oil rate control,
WRAT water rate control,
GRAT gas rate control,
WGRA wet gas rate control (only for E300 format models),
RESV reservoir liquid rate control,
BHP bottom hole pressure;
4. observed oil rate (METRIC: sm3 /day, FIELD: stb/day),
5. observed water rate (METRIC: sm3 /day, FIELD: stb/day),
6. observed gas rate (METRIC: sm3 /day, FIELD: Msc f /day),
THP will not be reported; if non-zero, THP will be calculated and reported,
12.18.35. WCONHIST 1275

9. observed tubing head pressure THP (METRIC: barsa, FIELD: psia), will be used for
reporting, its not a limit,
10. observed bottom hole pressure BHP (METRIC: barsa, FIELD: psia);
11. observed wet gas production rate (METRIC: sm3 /day, FIELD: Msc f /day);
12. observed natural gas liquid (NGL) rate (METRIC: sm3 /day, FIELD: stb/day).
Well defined by this keyword is on rate control. Control value will be calculated on basis
of historical data; in case of LRAT limit rate is calculated as sum of historical water and oil
rates. Bottom hole pressure (and tubing head pressure) are indicated for historical purposes
and these are not limits.
To limit bottom hole pressure, use WELTARG keyword, see WELTARG (see 12.18.51).
Otherwise default BHP limit equal to atmospheric pressure patm is used and the following
warning will be displayed:
Warning: Bottom hole pressure limit not set for well P1. Will use default value of
1.013000 bar.
If calculated pBH is lower than BHP limit, the well will switch to BHP control. During
the calculation process the simulator checks whether the well can switch back to specified
rate control. If the switch doesnt violate BHP limit, the well will return to rate control mode.
(see 12.1.3).
This keyword is convenient for history matching purposes.
Default:
well status: OPEN,
well VFP table number (VFPPROD (see 12.18.57)): last indicated value;
observed tubing head pressure, THP: 0;
observed bottom hole pressure, BHP: 0;
bottom hole pressure limit: patm (atmospheric pressure);
observed wet gas production rate: 0;
observed natural gas liquid (NGL) rate: 0.
Example
WCONHIST
1043 OPEN LRAT 18.9 0 0 /
1054 OPEN LRAT 16.38 1.765 0 3* 57 /
/
12.18.35. WCONHIST 1276

This example sets controls for two wells. Well 1043 is on liquid rate control; oil rate is
equal to 18.9, water and gas are not produced, hence total liquid rate is 18.9. The simulator
will set liquid production equal to 18.9; if calculated pressure is lower than atmospheric
(default bottom hole limit is atmospheric pressure), then the well will switch to bottom hole
pressure control.
Well 1054 is also on liquid rate control; oil and water rates are equal to 16.38 and 1.765;
hence total surface liquid rate is 18.145. There is a historical BHP value equal to 57.
12.18.35. WCONHIST 1277

12.18.36 WCONINJE


Section
This keyword could be specified for a well or a group of wells that work as injectors.


1. name of well (or number), or well list WLIST (see 12.18.26),
2. injected fluid:
WATER (also WAT is possible),

OIL,
GAS.
Note: for model in E300 format the composition of the injected gas should be
specified via WINJGAS (see 12.18.164), unless the well belongs to the group
with gas injection control where the injected gas is defined.
MULTI multi-phase injection (water, oil, gas). In this case the preferred phase of
the well will be injected (specified via WELSPECS (see 12.18.3)); 5-th parameter
of this keyword specifies the surface flow rate of the preferred phase. Parameters
12-14 specify surface volume proportion of phases in a multi-phase injector.
3. well working mode (OPEN, STOP or SHUT),
4. well control (RATE controlled by surface flow rate target, BHP controlled by BHP
target, THP controlled by THP target, RESV controlled by reservoir volume rate
target, GRUP group control (the keyword GCONINJE (see 12.18.81))),
5. surface rate of injected fluid (or limit) (METRIC: sm3 /day (for all phases); FIELD:
stb/day for oil and water, Msc f /day for gas).
In the case of MULTI-phase injection this parameter specifies the surface flow rate of
the preferred phase (specified via WELSPECS (see 12.18.3)).
6. reservoir rate of injected fluid (METRIC: rm3 /day, FIELD: rb/day),
7. BHP for injection or limit (METRIC: barsa, FIELD: psia),
8. THP for injection or limit (METRIC: barsa, FIELD: psia).
12.18.36. WCONINJE 1278

9. VFP table number for the injector (the keyword VFPINJ (see 12.18.56));
10. oil concentration in the injected gas or gas concentration in the injected oil (METRIC:
sm3 /sm3 , FIELD: Msc f /stb oil injection, stb/Msc f gas injection), IGNORED,
this is an Eclipse compatibility field,
12. surface volume proportion of oil in case of MULTI injection;
13. surface volume proportion of water in case of MULTI injection;
14. surface volume proportion of gas in case of MULTI injection.
User may specify one of the following combinations:
Specify BHP value pBH , and set well to BHP control, in this case injection rate is
calculated from (2.106). If injection rate exceeds limit, the well will switch to RATE
control.
During the calculation the simulator will check whether the rate limit is still violated if
the well switches to BHP control. If not, the well will switch back.
Set the well to RATE control, and specify well injection rate; in this case if computed
BHP is higher than the BHP limit, then well control is switched to BHP with BHP
value being equal to this limit.
During the calculation the simulator will check whether the BHP limit is still violated
if the well switches to RATE control. If not, the well will switch back.
All well control switching times are logged, REPORTFILE / REPORTSCREEN (see 12.1.3).
Default:
well status: OPEN,
injection rate limit: 1000000 m 3 / day,
BHP limit: 6801patm ,
surface volume proportion of oil in case of MULTI injection 0;
surface volume proportion of water in case of MULTI injection 0;
surface volume proportion of gas in case of MULTI injection 0;
Example 1.
12.18.36. WCONINJE 1279

Example
WCONINJE
1043 WATER OPEN RATE 253.1 2* /
1054 WATER OPEN RATE 253.1 1* 400/
/
This example sets controls for two wells. Well 1043 is on injection rate control, the rate
is equal to 253.1. There is no bottom hole pressure limit, so the simulator will set injection
rate equal to 253.1. If the user specifies an injection rate so high that necessary bottom hole
pressure exceeds default limit (6801patm ), the well will automatically switch to BHP control.
Well 1054 is also on injection rate control, the rate is equal to 253.1. This well has
bottom hole pressure limit equal to 400; so, if calculated pressure goes above 400, the well
will automatically switch to BHP control.
Example 2.
Example
WCONINJE
43 WATER OPEN BHP 255 1* 55/
54 WATER OPEN BHP 255 1* 45/
/
In this example both wells are on BHP control. In this case injection rate is calculated by
the simulator. If it exceeds 255, well will switch to RATE control.
Example 3. Multi-phase injection.
Example
WCONINJE
121R MULTI OPEN BHP 100 1* 4000 4* 0.8 0.2 /
/
In this example the parameter MULTI specifies multi-phase injection. Surface volume
proportion of oil 0.8, Surface volume proportion of water 0.2
12.18.36. WCONINJE 1280

12.18.37 WCONINJ


Section
This keyword can be used in tNavigator, but it is highly recommended to use the keyword
WCONINJE (see 12.18.36) instead of WCONINJ.


2. injected fluid:
WATER (also WAT is possible);

OIL;
GAS.
3. well working mode:
OPEN;
STOP;
SHUT.
4. well control:
RATE controlled by surface flow rate target;

BHP controlled by BHP target;
THP controlled by THP target;
RESV controlled by reservoir volume rate target.
5. surface rate of injected fluid (or limit) (METRIC: sm3 /day (for all phases); FIELD:
stb/day for oil and water, Msc f /day for gas);
6. reservoir rate of injected fluid (METRIC: rm3 /day, FIELD: rb/day);
7. reinjection or voidage replacement fraction;
12.18.37. WCONINJ 1281

8. reinjection or voidage replacement flag:

NONE no reinjection or voidage replacement;
GPRD well reinjects a fraction of its groups production;
FPRD well reinjects a fraction of the fields production;
GVDG well replaces a fraction of its groups voidage;
FVD well replaces a fraction of the fields voidage;
GPRD: then the target or limiting surface flow rate = parameter 5 + parameter 7
group production rate.
FPRD: then the target or limiting surface flow rate = parameter 5 + parameter 7 field
production rate.
GVDG: then the target or limiting reservoir volume rate = parameter 6 + parameter 7
group voidage rate.
FVDG: then the target or limiting reservoir volume rate = parameter 6 + parameter 7
field voidage rate.
11. VFP table number for the injector (the keyword VFPINJ (see 12.18.56)).
Default:
well status: OPEN;
surface rate of injected fluid (or limit): 1020 m 3 /day;
reservoir rate of injected fluid (or limit): 1020 m 3 /day;
reinjection or voidage replacement fraction: 0;
reinjection or voidage replacement flag: NONE;
BHP limit: 6804patm ;
THP limit: 1020 patm ;
VFP table number for the injector: 0.
Example
WCONINJ
'AB17H1' ' WATER' ' OPEN' ' RATE' 0 0 1.0 'FPRD' 3200 /
/
In the example the well AB17H1 reinjects all water which was produced by reservoir.
Limit of BHP is 3200 psia.There is no limit for THP.
12.18.37. WCONINJ 1282

12.18.38 WCONINJP


Section
The keyword specifies the injector which injects at a rate equal to the sum of parts of
volumes of production (reservoir volume) of neighboring producers. For example, in a five
spot pattern one can specify the injector whose injection rate is equal to the sum of one
quarters of the production volume of its four neighboring producers.
The keyword can specify this type of control only for one well. If there are several injec-
tors with this type of control, one should use this keyword several times.
If the well has this type of control, it cant have the control of group it belongs to. So
this well can switch only from this type of control to BHP limit and vice versa.
The data consists of two parts: 1st part description of injector (this part should be
terminated with a slash /), 2nd part producers, which influence on the injection volume of
the injector in part 1 (the data of each producer should be terminated with a slash /). The
2nd part should be terminated with single slash /.
The following data should be specified (Part 1):
1. name of well (or number),
2. injected fluid:

OIL,
GAS,
MULTI multi-phase injection (water, oil, gas). In this case the preferred phase
of the well will be injected (specified via WELSPECS (see 12.18.3)). Parameters
9-11 specify surface volume proportion of phases in a multi-phase injector.
5. THP for injection or limit (METRIC: barsa, FIELD: psia),
12.18.38. WCONINJP 1283

8. factor; calculated injection volume for this injector will be multiplied by this factor.
11. surface volume proportion of gas in case of MULTI injection;
Default:
injected fluid WATER,
well working mode OPEN,
factor 1,
Part 2. The following data should be specified for each well:
1. producer name (or number)
2. the fraction (a value between 0 and 1). This fraction is equal to the part of production
volume of this producer. Injector in part 1 will inject at a rate equal to the sum of
parts of volumes of production of corresponding producers. Default. This value is re-
computing at each time step if an injector (corresponding to this producer) with the
same type of control starts working or stops.
3. fluid-in-place region number.
Example
WCONINJP
WELL1 WATER OPEN 320/
P111 1 /
P112 0.25 /
P113 0.25 /
P114 0.5 /
P115 0.5 /
/
12.18.38. WCONINJP 1284

This example sets the injector WELL1 is open, injects water and has BHP limit 320.
WELL1 injects at a rate equal to the sum of following volumes: total production volume of
P111, one quarter of production volume of P112, one quarter of production volume of P113,
one half of production volume of P114, one half of production volume of P115.
12.18.38. WCONINJP 1285

12.18.39 WCONINJH


Section
This keyword may be specified for a well or a group of wells (instead of the keyword
WCONINJE (see 12.18.36)) that work as injectors and are being history matched. The key-
word WCONHIST (see 12.18.35) is used for wells that work as producers and are being
history matched.

2. injected fluid:

OIL,
GAS,
MULTI multi-phase injection (water, oil, gas). In this case the preferred phase of
the well will be injected (specified via WELSPECS (see 12.18.3)); 4-th parameter
of this keyword specifies the historical surface flow rate of the preferred phase.
Parameters 9-11 specify surface volume proportion of phases in a multi-phase
injector.
4. observed surface rate of injected fluid (METRIC: sm3 /day, FIELD: stb/day for oil
and water, Msc f /day for gas).
In the case of MULTI-phase injection this parameter specifies the historical surface flow
rate of the preferred phase (specified via WELSPECS (see 12.18.3)).
5. observed bottom hole pressure BHP (METRIC: barsa, FIELD: psia), will be used for
reporting, its not a limit (well will not switch to BHP control if the calculated BHP is
above this value),
6. observed tubing head pressure THP (METRIC: barsa, FIELD: psia), will be used for
reporting, its not a limit (well will not switch to BHP control if the calculated BHP is
above this value),
12.18.39. WCONINJH 1286

7. well VFP table number,
11. surface volume proportion of gas in case of MULTI injection;
12. well control mode:
RATE well is controlled by injection rate;

BHP well is controlled by bottom hole pressure.
If calculated pBH is lower than BHP limit, the well will switch to BHP control. During
the calculation process the simulator checks whether the well can switch back to injection
rate control. If the switch doesnt violate BHP limit, the well will return to injection rate
control mode.

(see 12.1.3).
This keyword is convenient for history matching purposes.
Default:
well status: OPEN,
injector type WATER,
observed tubing head pressure, THP: 0;
observed bottom hole pressure, BHP: 0;
bottom hole pressure limit: patm (atmospheric pressure);
well control mode: RATE.
12.18.39. WCONINJH 1287

Example
WCONINJH
1043 WATER OPEN 105.968 4* /
1112 WATER OPEN 99.3 4* /
1054 GAS OPEN 400 220 100 2 1*/
988 GAS OPEN 340 230 100 3 1*/
/
In this example there are four injectors that are being history matched. Well 1043 injects
water, observed surface rate of injected fluid 105.968 (sm3 /day).
Well 1112 injects water, observed surface rate of injected fluid 99.3 (sm3 /day).
Well 1054 injects gas, observed surface rate of injected fluid 400 (sm3 /day), observed
BHP 220 (barsa), observed THP 100 (barsa), VFP table number - 2.
Well 988 injects gas, observed surface rate of injected fluid 340 (sm3 /day), observed BHP
230 (barsa), observed THP 100 (barsa), VFP table number - 3.
12.18.39. WCONINJH 1288

12.18.40 WELLINJE


Section

2. nature of injected fluid (tNavigator supports the following options):

GAS gas composition corresponds to the field separator gas composition;
ST molar composition of the injected fluid is defined via the keyword WELL-
STRE (see 12.18.159) (stream name should be entered via parameter 3 of this
keyword);
MIX molar composition of the injected fluid is defined as a mixture via the
keyword WINJMIX (see 12.18.162) or WINJORD (see 12.18.163) (mixture name
should be entered via parameter 3 of this keyword);
GV injected gas composition corresponds to gas composition, produced by
specified group (group name should be entered via parameter 3 of this keyword);
WV injected gas composition corresponds to gas composition, produced by
specified well (well name should be entered via parameter 3 of this keyword);
GR injected fluid is specified for the superior group.
3. character string that specifies the data in accordance with the parameter 2 of the
keyword:
if the 2-nd parameter is ST, the stream name should be specified here;
if the 2-nd parameter is MIX, the mixture name should be specified here;
if the 2-nd parameter is GV, the group name should be specified here;
if the 2-nd parameter is WV, the well name should be specified here.
4. method specifying the injection rate:
12.18.40. WELLINJE 1289

WAT injects a target water volume specified via parameter 6;

GAS injects a target gas volume specified via parameter 7;
BHP maintains a target BHP specified via parameter 8;
THP maintains a target THP specified via parameter 9;
RV injects a target fluid volume in reservoir conditions specified via parameter
10;
GR the well is under group control;
5. oil volume rate at surface conditions (target or limit) (METRIC: sm3 /day, FIELD:
stb/day);
6. water volume rate at surface conditions (target or limit) (METRIC: sm3 /day, FIELD:
stb/day);
7. gas volume rate at surface conditions (target or limit) (METRIC: sm3 /day, FIELD:
Msc f /day for gas);
10. fluid volume rate at reservoir conditions (or limit) (METRIC: rm3 /day, FIELD:
rb/day);
11. wet gas volume rate at surface conditions (or limit) IGNORED, this is an Eclipse
12. re-injection fraction (or limit), IGNORED, this is an Eclipse compatibility field;
13. production type that is used to define the rate under re-injection, IGNORED, this is an
Eclipse compatibility field;
14. name of the production well or group that controls the re-injection, IGNORED, this is
15. gas rate that is subtracted from the re-injection rate target, IGNORED, this is an Eclipse
17. wellstream which will be used as make-up gas. IGNORED, this is an Eclipse compati-
bility field;
18. the way in which reinjection or voidage replacement fraction in parameter 12 is to be

interpreted. IGNORED, this is an Eclipse compatibility field;
12.18.40. WELLINJE 1290

19. the stage of the separator which defines the fluid composition for injection. IGNORED,
this is an Eclipse compatibility field;
20. the target or limit total molar rate (METRIC: kg M/day, FIELD: lb M/day);
21. the steam quality of the injected fluid (can be used only with the thermal option). The
value must be between 0 and 1. If specified, either the temperature (parameter 22) or
the pressure (parameter 23) must also be specified, but not the specific enthalpy rate
(parameter 24).
22. the temperature of the injected fluid (METRIC: C , FIELD: F ). It can be used only
with the thermal or temperature option. If specified, either the steam quality (parameter
21) or the pressure (parameter 23) must also be specified, but not the specific enthalpy
rate (parameter 24);
23. the pressure of the injected fluid (METRIC: bar , FIELD: psia). It can be used only
with the thermal or temperature option. If specified, one of the steam quality (parameter
21), the pressure (parameter 22) or specific enthalpy rate (parameter 24) should be
specified;
24. the specific enthalpy rate of the injected fluid (METRIC: kJ/kg M , FIELD: Btu/lb
M ). It can be used only with the thermal option. If specified, the pressure (parameter
22) must also be specified and neither the steam quality (parameter 21) nor temperature
(parameter 23) may be specified.
Example
WELLINJE
CSS-2 WAT 1* WAT 1* 203.89 1* 4500 12* 0.8 520 1* /
/
In the example well CSS-2 injects water. Limit value of injection rate is 203.89 stb/day,
BHP limit value is 4500 psia, steam quality is 0.8, temperature of injection water is 520 F .
The other parameters are defaulted, either they dont need to be specified (3-rd, 5-th, 7-th
and 24-th) or they are ignored (9-20-th).
12.18.40. WELLINJE 1291

12.18.41 GRUPINJE


Section
This keyword could be specified for a group of injector wells.

1. well group name, group name mask or FIELD.
2. composition of injection fluid:
WATER (also WAT is possible) water;

keyword);
specified group group name should be entered via parameter 3 of this keyword);
specified well (well name should be entered via parameter 3 of this keyword).
keyword:
12.18.41. GRUPINJE 1292


RV inject the fluid to make up a target reservoir volume injection rate set by
parameter 8;
WG inject the fluid at a target wet gas rate set in parameter 9;
RE reinjection or voidage replacement control, at a fraction set in parameter 10;
NONE rate control is absent.
5. oil volume rate at surface conditions (or limit) (METRIC: sm3 /day, FIELD: stb/day);
6. water volume rate at surface conditions (or limit) (METRIC: sm3 /day, FIELD:
stb/day);
7. gas volume rate at surface conditions (or limit) (METRIC: sm3 /day, FIELD:
Msc f /day);
rb/day);
9. wet gas volume rate at surface conditions (or limit) (METRIC: sm3 /day, FIELD:
Msc f /day);
10. the target/limit reinjection fraction or voidage replacement fraction:
if parameter 15 is set to S, parameter 10 is interpreted as a reinjection fraction.

When this is a target, the group attempts to inject the fluid specified in parameter
2 at a surface rate equal to the reinjection fraction multiplied by the water or
available gas rate of the group or well named in parameter 12;
if parameter 15 is set to R, parameter 10 is interpreted as a voidage replacement
fraction. When this is a target, the group attempts to inject the fluid specified
in parameter 2 to make up a total reservoir volume injection rate equal to the
voidage replacement fraction multiplied by the total reservoir volume production
rate of the group or well named in parameter 12.
11. type of production used to define the rate under reinjection or voidage replacement
control:
W implies the reinjection or voidage replacement depends on the production of

the well specified by parameter 12;
G Implies the reinjection or voidage replacement depends on the production of
the well group specified in parameter 12.
12. name of the production well or group that controls the reinjection or voidage replace-
ment rate:
12.18.41. GRUPINJE 1293

if parameter 11 is W, then producer well name should be specified here;

if parameter 11 is G, then well group name should be specified here.
14. mnemonic for a wellstream to be used as make-up gas. This is only required if make-
up gas is to be used when the injected gas rate exceeds the advance and/or available
produced gas from the source group or well.
15. parameter 10 definition (reinjection or voidage replacement):
S reinjection;
R voidage replacement.
16. separator stage that defines the fluid composition for injection.
Default:
the target/limit reinjection fraction or voidage replacement fraction:
if parameter 4 is RE: 1;
otherwise: 0.
type of production used to define the rate under reinjection or voidage replacement
control:
if parameter 2 is WV: W;
if parameter 2 is GV: G.
name of the production well or group that controls the reinjection or voidage replace-
ment rate: if this name is not specified, it defaults to the fluid composition source name
(parameter 3) for injection fluids WV or GV in parameter 2, and to the name of the
group in item 1 otherwise.
parameter 10 definition: S;
separator stage that defines the fluid composition for injection: 0.
Example
GRUPINJE
FIELD WA 1* RE 10* R /
/
In the example FIELD reinjects water. Injection water rate is unlimited, parameters from
5 to 14 is defaulted. Parameter 10 is interpreted as voidage replacement.
12.18.41. GRUPINJE 1294

12.18.42 WCYCLE


Section
The keyword can be used to specified automatic cycling of wells on and off.
For example for WAG cycle 2.19.6 (alternating injection of water and gas).

2. well on-period (days).

The well is turned off at the beginning of the first time step that goes after the end of
well on-period. If 0 or negative value is specified the well finish its cycling work;
3. well off-period (days).

If the well was closed at the cycling process, then it is turned on at the beginning of
the first time step that goes after the end of well off-period. If the well was closed
manually or because of violation of economic limits then it should be opened manually
to continue cycling work. If 0 or negative value is specified the well finish its cycling
work;
4. well start-up time Tstart (days).

The wells efficiency factor will be increasing when it is turned on by automatic
cycling. At each timestep after reopening efficiency factor is multiplied by
T T0
Tstart
till the moment, when T T0 < Tstart .
T the time at the end of the timestep, T0 the time the well was turned on.
This option provides the possibility to start the well gradually;
5. maximum timestep length, at which the well is turned on by automatic cycling (days).
This value at the current time step (only one time step) overrides the maximum time
step length (parameter DTMAX in RUNCTRL (see 12.18.119)).
This option provides the possibility to reduce the length of the time step to avoid the
convergence problems when a high-rate well is opened. If zero or negative value is
specified the default length of the time step will be used.
12.18.42. WCYCLE 1295

6. are the timesteps controlled to coincide exactly with the on/off cycling times of this
well:
YES The timesteps coincide with this wells on/off cycling times. Well works
with cycles with specified periods.
NO The timesteps does not automatically coincide with this wells on/off cycling
times. The well cycles at the beginning of the next timestep which starts after the
specified period has elapsed.
Default:
well on-period 0 (days);
well off-period 0 (days);
well start-up time Tstart 0 (days) (instantaneous start-up);
maximum timestep length, at which the well is turned on by automatic cycling (days)
0 (default length of the time step will be used);
are the timesteps controlled to coincide exactly with the on/off cycling times of this
well NO.
Example
WCYCLE
WELL1 50 30 /
/
In this example WELL1 on-period is 50 days, off-period 30 days.
12.18.42. WCYCLE 1296

12.18.43 WELLWAG


Section
The keyword can be used to specified WAG option (water and gas injection).
The keyword WELLINJE (see 12.18.40) (or WCONINJE (see 12.18.36)) should be de-
fined before this keyword to set injection parameters.

2. type of WAG cycle: T time; M months, Y years;
3. the first fluid that is injected at WAG cycle: W water, or G gas;
4. injection time for the first fluid (days);
5. the second fluid that is injected at WAG cycle: W water, or G gas (in the case if
the first fluid was water, then the second must be gas, and analogous if the first was
gas, then the second must be water);
6. injection time for the second fluid (days);
7. VFP table number for the first injected fluid (VFPINJ (see 12.18.56));
8. VFP table number for the second injected fluid (VFPINJ (see 12.18.56));
9. control for the first injected fluid (RATE control by surface flow rate (5-th parameter
of WCONINJE (see 12.18.36) or WELTARG (see 12.18.51)), BHP BHP control,
THP THP control);
10. control for the second injected fluid (RATE control by surface flow rate (5-th pa-
rameter of WCONINJE (see 12.18.36) or WELTARG (see 12.18.51)), BHP BHP
control, THP THP control);
11. BHP (or BHP upper limit) for the first injected fluid (METRIC: barsa, FIELD: psia);
12.18.43. WELLWAG 1297

12. BHP (or BHP upper limit) for the second injected fluid (METRIC: barsa, FIELD:
psia);
13. THP (or THP upper limit) for the first injected fluid (METRIC: barsa, FIELD: psia);
14. THP (or THP upper limit) for the second injected fluid (METRIC: barsa, FIELD:
psia).
Default:
type of WAG cycle: T time;
VFP table number for the first injected fluid: the value that was previously specified
for this well;
VFP table number for the second injected fluid: the value that was previously specified
for this well;
control for the first injected fluid: RATE control by surface flow rate;
control for the second injected fluid: RATE control by surface flow rate;
BHP (or BHP upper limit) for the first injected fluid: the value that was previously
specified for this well via WCONINJE (see 12.18.36) or WELTARG (see 12.18.51);
BHP (or BHP upper limit) for the second injected fluid: the value that was previously
THP (or THP upper limit) for the first injected fluid: the value that was previously
THP (or THP upper limit) for the second injected fluid: the value that was previously
specified for this well via WCONINJE (see 12.18.36) or WELTARG (see 12.18.51).
Example
WELLWAG
WELL1 T W 50 G 100 /
WELL2 T G 120 W 50 /
/
In this example: WELL1 injects water for 50 days, then it injects gas for 100 days;
WELL2 injects gas for 120 days, then it injects water for 50 days.
12.18.43. WELLWAG 1298

12.18.44 WWAG


Section
The keyword can be used to specified automatic cycling of wells on and off.
The data consists of two sets of parameters:
1. injection well parameters (should be terminated with a slash /),
2. description of well cycling mode (each row should be terminated with /). All the data
First set of parameters:
2. well cycling mode:
ON turn on the cycling process;

OFF turn off the cycling process (if previously this keyword was specified and
the well cycling process was turned ON, then OFF will turn it off and the well
will work in the mode it works before this keyword is used with ON). Example
2 below;
SINGLE make only one cycle;
SWITCH switch to the next cycle stage, terminate the current stage. Example 3
below.
3. type of the specified value:
TIME time;
RATE injection rate in the surface conditions;
RESV injection rate in the reservoir conditions.
Default values for the first set of parameters:
well cycling mode ON;
type of the specified value TIME.
12.18.44. WWAG 1299

The second set of parameters describes the cycling process. One data row consists of:
1. time if in the first set of parameters TIME type is specified (days).
2. nature of injected fluid (tNavigator supports the following options):

keyword);
GR injected fluid is specified for the superior group.
keyword:
4. surface rate of injected fluid (or limit)

BHP maintains a target BHP specified via parameter 8;
THP maintains a target THP specified via parameter 9;
RV injects a target fluid volume in reservoir conditions specified via parameter
10;
6. oil volume rate at surface conditions (or limit) (METRIC: sm3 /day, FIELD: stb/day);
12.18.44. WWAG 1300

7. water volume rate at surface conditions (or limit) (METRIC: sm3 /day, FIELD:
stb/day);
8. gas volume rate at surface conditions (or limit) (METRIC: sm3 /day, FIELD:
Msc f /day for gas);
rb/day);
12. wet gas volume rate at surface conditions (or limit) IGNORED, this is an Eclipse
13. re-injection fraction (or limit), IGNORED, this is an Eclipse compatibility field;
14. production type that is used to define the rate under re-injection, IGNORED, this is an
Eclipse compatibility field;
15. name of the production well or group that controls the re-injection, IGNORED, this is
16. gas rate that is subtracted from the re-injection rate target, IGNORED, this is an Eclipse
17. VFP table number for the injector (the keyword VFPINJ (see 12.18.56)).
Example 1.
Example
WWAG
INJ1 ON TIME/
30 WATER 1* bhp 1* 400 1* 350 /
30 GAS 1* bhp 1* 1* 100000 350 /
/
/
In this example cycling working mode is turned on for the well INJ1. Parameter TIME
is specified. First 30 days the well injects water (controlled by bottom hole pressure) with
the following limits: surface rate of injected fluid 400 sm3 /day, BHP 350 barsa.
Next 30 days the well injects gas (controlled by bottom hole pressure) with the following
limits: surface rate of injected fluid 100000 sm3 /day, BHP 350 barsa.
Then the cycling work takes place: 30 days water, 30 days gas, 30 days water, 30 days
12.18.44. WWAG 1301

gas etc.
Example 2.
Example
WWAG
INJ1 OFF/
/
In this example INJ1 cycling working mode is turned off. If this keyword is used at any
time step after it is turn on (as in the Example 1) then the well cycling working mode is
turned off at the specified time step.
Example 3.
Example
DATES
1 JAN 2013 /
/
WWAG
INJ1 ON TIME/
50 WATER 1* bhp 1* 400 1* 350 /
100 GAS 1* bhp 1* 1* 100000 350 /
/
...
DATES
1 APR 2013 /
/
WWAG
INJ1 SWITCH/
/
In this example cycling process is turned on the 1-st January. Water injection takes place
50 days, then gas injection starts. The second usage of this keyword WWAG at the 1-st April
with SWITCH: gas injection is terminated (not extend 100 days) and water injection starts
again.
12.18.44. WWAG 1302

12.18.45 WHISTCTL


Section
The keyword specifies parameters for all History Matching wells (WCONHIST (see
12.18.35) history matching producers, WCONINJH (see 12.18.39) history matching
injectors. The data should be terminated with a slash /.
1. new control which will be applied to all wells specified in WCONHIST (see 12.18.35)
below:
ORAT control by the observed oil rate;

WRAT control by the observed water rate;
GRAT control by the observed gas rate;
LRAT control by the observed liquid rate;
RESV control by the reservoir fluid volume rate;
NONE no new control. Control specified in WCONHIST (see 12.18.35) below
will be used.
2. termination of the run if a history matching well is switched to BHP control:
YES run termination;

NO continue the run with the well on BHP control.
Default: new control which will be applied to all wells specified in WCONHIST (see
12.18.35) below NONE (no new control).
Example
WHISTCTL
LRAT YES/
In this example a new control LRAT (control by the observed liquid rate) is specified and
the parameter to end the run if a history matching well is switched to BHP control.
12.18.45. WHISTCTL 1303

12.18.46 WCUTBACK


Section
The keyword specifies well cutback limits (for producers and injectors).
The keyword can be followed by an arbitrary number of data lines. Each data line should
be terminated with a slash /. All data should be terminated with a final slash /.
One data line consists of the following data:

2. water cut upper limit for producer rate cutback (METRIC: sm3 /sm3 , FIELD: stb/stb)
(0 switches off this limit);
3. gas-oil ratio upper limit for producer rate cutback (METRIC: sm3 /sm3 , FIELD:
Msc f /stb) (0 switches off this limit);
4. gas-liquid ratio upper limit for producer rate cutback (METRIC: sm3 /sm3 , FIELD:
Msc f /stb) (0 switches off this limit);
5. water-gas ratio upper limit for producer rate cutback (METRIC: sm3 /sm3 , FIELD:
stb/Msc f ) (0 switches off this limit);
6. rate cutback factor (the ratio of reduced flow rate to current flow rate), the value should
be less than 1;
7. control phase, to which the reduced rate will be applied (one should choose a phase
that does not have a user defined rate limit, because it would be overwritten):
OIL reduced oil rate;
WAT reduced water rate;
GAS reduced gas rate;
LIQ reduced liquid rate;
RESV reduced reservoir fluid volume rate.
If the well violates one of the cutback limits specified by parameters 2-5, then it will
be set to operate at a reduced rate of the phase specified in parameter 7. Well control
will be switched to the parameter 7 (if it is not under that control). The target rate of
the control phase will be equal to the wells current flow rate, multiplied by the cutback
factor specified in parameter 6.
12.18.46. WCUTBACK 1304

Default:
water cut upper limit for producer rate cutback no limit;
gas-oil ratio upper limit for producer rate cutback no limit;
gas-liquid ratio upper limit for producer rate cutback no limit;
water-gas ratio upper limit for producer rate cutback no limit.
Example
WCUTBACK
1095 0.7 3.0 2* 0.8 OIL /
/
12.18.46. WCUTBACK 1305

12.18.47 GCUTBACK


Section
The keyword specifies well cutback limits (for producers and injectors).
1. name of group (or group name root),
2. water cut upper limit for group rate cutback (METRIC: sm3 /sm3 , FIELD: stb/stb) (0
or value greater than 1 switches off this limit);
3. gas-oil ratio upper limit for group rate cutback (METRIC: sm3 /sm3 , FIELD:
Msc f /stb) (0 or value greater than 1.0E19 switches off this limit);
4. gas-liquid ratio upper limit for group rate cutback (METRIC: sm3 /sm3 , FIELD:
Msc f /stb) (0 or value greater than 1.0E19 switches off this limit);
5. water-gas ratio upper limit for group rate cutback (METRIC: sm3 /sm3 , FIELD:
stb/Msc f ) (0 or value greater than 1.0E19 switches off this limit);
be less than 1;

If the group violates one of the cutback limits specified by parameters 2-5, then it will
be set to operate at a reduced rate of the phase specified in parameter 7. The target
rate of the control phase will be equal to the groups current flow rate of that phase,
multiplied by the cutback factor (parameter 6). The groups production rate target is met
12.18.47. GCUTBACK 1306

by guide rate control GCONPROD (see 12.18.72) (unless the group is under GCONPRI
(see 12.18.75)).
Default:
water cut upper limit for group rate cutback no limit (1.0E20);
gas-oil ratio upper limit for group rate cutback no limit (1.0E20);
gas-liquid ratio upper limit for group rate cutback no limit (1.0E20);
water-gas ratio upper limit for group rate cutback no limit (1.0E20).
Example
GCUTBACK
'FIELD' 1* 1* 1* 55E-3 0.90 'GAS' /
/
12.18.47. GCUTBACK 1307

12.18.48 WBHGLR


Section
This keyword specifies two ways of limiting the bottom hole gas liquid ration (GLR)
at the bottom hole pressure of the well (datum depth is specified in the 5-th parameter of
WELSPECS (see 12.18.3)).
The keywords works analogously to WCUTBACK (see 12.18.46) and WECON (see
12.18.62).
If the well violates the cutback limit (parameter 2) at the end of the time step, then the
reduced target rate will be specified for the selected phase (parameter 5). The target rate of
the control phase is equal to the wells current flow rate of that phase, multiplied by the
cutback factor (parameter 4).
Reversing the cutback process: if wells GLR at bottom hole pressure is below then parameter
3, then the rate will nor be reduced.
1. name of well (or number) or well list specified via WLIST (see 12.18.26);
2. upper limit bottom hole GLR for well rate cutback (METRIC: rm3 /rm3 , FIELD:
rb/rb)
3. lower limit bottom hole GLR for reversing the cutback process (METRIC: rm3 /rm3 ,
FIELD: rb/rb)
be less than 1 (the same cutback factor is applied also in the keyword WCUTBACK (see
12.18.46). If WCUTBACK (see 12.18.46) is specified, then this parameter overwrites
parameter 6 of WCUTBACK (see 12.18.46). Or if WCUTBACK (see 12.18.46) is
specified later, then its 6-th parameter overwrites the parameter of WBHGLR);

12.18.48. WBHGLR 1308


The same control phase is applied also in the keyword WCUTBACK (see 12.18.46). If
WCUTBACK (see 12.18.46) is specified, then this parameter overwrites parameter 7
of WCUTBACK (see 12.18.46). Or if WCUTBACK (see 12.18.46) is specified later,
then its 7-th parameter overwrites the parameter of WBHGLR);
6. upper economic limit of bottom hole GLR (METRIC: rm3 /rm3 , FIELD: rb/rb). Value
0 or the value that is greater then 1e19 switches off this check;
7. workover action for bottom hole GLR violation:
NONE do nothing,
CON shut in the worst offending perforation,
CON+ close worst offending perforation and all below,
+CON the same as CON+,
WELL shut in or step the well (9-th parameter of WELSPECS (see 12.18.3)).
Default:
upper limit bottom hole GLR for well rate cutback 1e20;
lower limit bottom hole GLR for reversing the cutback process 0;
rate cutback factor (the ratio of reduced flow rate to current flow rate) 1 or 6-th
parameter of WCUTBACK (see 12.18.46) (is it was previously specified);
control phase, to which the reduced rate will be applied RESV or 7-th parameter
WCUTBACK (see 12.18.46), is it was previously specified;
upper economic limit of bottom hole GLR 1e20;
workover action for bottom hole GLR violation NONE or 7-th parameter of WECON
(see 12.18.62), is it was previously specified.
Example
WBHGLR
1095 0.25 0.09 0.7 GAS /
/
12.18.48. WBHGLR 1309

12.18.49 WTMULT


Section
The keyword is used to multiply control or limit value for the well, defined by WCON-
PROD (see 12.18.34), WCONINJE (see 12.18.36) by a multiplying factor.
2. control or limit to be changed:
ORAT oil rate;

WRAT water rate;
GRAT gas rate;
LRAT liquid rate;
THP tubing head pressure (non zero VFP table number should be specified);
RESV reservoir fluid volume rate;
LIFT artificial lift quantity (non zero VFP table number should be specified);
GUID guide rate (for wells under group control). Can be changed only is was
previously defined by user in the keyword WGRUPCON (see 12.18.80).
CVAL calorific rate;
NGL nature gas liquid rate (NGL).
3. multiplying factor for this control or limit.
4. number of times multiplication will be performed.
Default:
number of times multiplication will be performed: 1 time.
12.18.49. WTMULT 1310

Example
WTMULT
WELL1 WRAT 1.3 /
WELL2 ORAT 1.5/
WELL3 RESV 0.7 /
/
In this example for the well WELL1 multiplying factor for water rate is 1.3, for the well
WELL2 multiplying factor for water rate is 1.5, for the well WELL3 multiplying factor
for reservoir fluid volume rate is 0.7.
12.18.49. WTMULT 1311

12.18.50 WTADD


Section
The keyword is used to increase control or limit value for the well, defined by WCON-
PROD (see 12.18.34), WCONINJE (see 12.18.36) by a specified value.
ORAT oil rate;
WRAT water rate;
GRAT gas rate;
LRAT liquid rate;
RESV reservoir fluid volume rate;
GUID guide rate (for wells under group control). Can be changed only is was
previously defined by user in the keyword WGRUPCON (see 12.18.80).
CVAL calorific rate;
NGL nature gas liquid rate (NGL).
3. value to add to this control or limit.
4. number of times addition will be performed.
Default:
number of times addition will be performed: 1 time.
Example
WTADD
B3 GRAT -17740 /
In the example gas control value decreased by 17740.
12.18.50. WTADD 1312

12.18.51 WELTARG


Section
This keyword resets the value of well control or limit, defined by WCONPROD (see
12.18.34), WCONINJE (see 12.18.36).
For the wells that work in history matching mode (WCONHIST (see 12.18.35), WCON-
INJH (see 12.18.39)) BHP limit can be changed, VFP table number, artificial lift quantity. If
for these wells the limit is not specified via WELTARG, then the BHP default value will be
used, patm , and the following warning will be displayed:
Warning: Bottom hole pressure limit not set for well P1. Will use default value of
1.013000 bar.


ORAT oil rate;

WRAT water rate;
GRAT gas rate;
LRAT liquid rate;
RESV reservoir fluid volume rate (reservoir conditions);
VFP VFP table number (VFPPROD (see 12.18.57), VFPCORR (see 12.18.61));
WGRA wet gas production rate;
TMRA molar rate;
STRA steam production rate (can be used in THERMAL (see 12.1.50) option
only);
GUID guide rate (for wells under group control);
12.18.51. WELTARG 1313

CVAL calorific production rate;

NGL natural gas liquid rate.
3. new value of this control or limit.
Default: none
For a well on BHP control, WELTARG will simply reset control value.
For a well on rate control, WELTARG will change the BHP limit.
Example
WELTARG
245 BHP 20/
/
In this example bottom hole pressure limit (or control) is changed for well 245 using
WELTARG.
Example
WCONHIST
p45 OPEN LRAT 18.9 0 0 3* 67 /
/
WELTARG
p45 BHP 30/
/
In this example first historical production and control mode are defined for well p45.
Historical bottom hole pressure 67 is indicated. Then bottom hole pressure limit is set using
WELTARG.
12.18.51. WELTARG 1314

12.18.52 WELLTARG


Section
This keyword is an alias for WELTARG (see 12.18.51).
12.18.52. WELLTARG 1315

12.18.53 WELCNTL


Section
This keyword is an alias for WELTARG (see 12.18.51).
12.18.53. WELCNTL 1316

12.18.54 GRUPTARG


Section
This keyword resets control or limit value for the well, defined by GCONPROD (see
12.18.72), GCONPRI (see 12.18.75).
An arbitrary number of data lines could be entered (ended with /). All data should be
The following options are available:
1. name of group or group name root,
ORAT oil rate;

WRAT water rate;
GRAT gas rate;
LRAT liquid rate;
RESV liquid rate in reservoir conditions;
WGRA wet gas rate.
3. new value of this control or limit.
Default: none.
Example
WELTARG
GROUP1 LRAT 30000/
/
12.18.54. GRUPTARG 1317

12.18.55 WELPI


Section
The keyword specifies productivity (injectivity) index (PI) for the wells. Well connections
should be specified via the keywords COMPDAT (see 12.18.6). Connection transmissibility
factors are calculated so that calculated productivity index (PI) and the value specified in this
keyword are equal.
(Productivity index (PI) is equal to the production (injection) rate of the phase divided by
the pressure drop. Pressure drop - difference between wells BHP and the reservoir pressure
at wells drainage radius.)
The following parameters are to be specified in one data line:
2. steady-state productivity (injectivity) index (PI) (METRIC: sm3 /day bar , FIELD:
stb/day psi).
Example
WELPI
Producer514 0.78 /
Producer312 1.4 /
Injector1* 18 /
/
In this example productivity index for the well Producer514 is 0.78, for the well Pro-
ducer312 1.4 and for the wells which name begins with Injector1 18.
12.18.55. WELPI 1318

12.18.56 VFPINJ


Section
This keyword inputs a table of BHP values versus FLO (oil, water or gas injection rate),
THP (tubing head pressure) for injectors.
If there are wells defined that require THP calculation, at least one vertical flow table
should be input. If several tables are used in calculation, each one is input separately by
VFPINJ keyword.
If in the model calculation the values are outside the range specified in the table,
the linear extrapolation will be used (to calculate the missing values from the available
values). Linear extrapolation may lead to unphysical results and should be avoided.
Make sure that the given values in the table cover all cases that may occur during
your model calculation.
If the extrapolation is used the following warning will be displayed:
Warning: At 0.9 (01 JAN 1997 21:54:00.999999) for well PROD1 extrapolation of
VFP table N 1 was performed. Current GOR value = 5.908955, max GOR value in table =
4.000000.
Warning: At 0.9 (01 JAN 1997 21:54:00.999999) extrapolation of VFP table N 1 for
well PROD1 resulted in THP value out of table range. Current THP value = 0.000000, min
THP value = 200.000000.
If the BHP is calculated using THP value that exceeds limits (specified by table) then the
following warning will be displayed:
Warning: At 9.7 (10 JAN 1997 17:21:59.867983) for well PROD1 extrapolation of VFP
table N 1 was performed. Current THP value = 10.000000, min THP value = 200.000000.
Calculated BHP value = 2071.422084.
The table consists of the following records of data, each record terminated with a slash
(/).
1. Basic data
12.18.56. VFPINJ 1319

table number (a number between 1 and the 3-rd parameter of VFPIDIMS (see
12.1.30));
bottom hole datum depth for this table (METRIC: m, FIELD: f t );
definition of variable FLO (OIL Oil injection rate, WAT water injection rate,
or GAS Gas injection rate; for models in E300 format: WG Hydrocarbon wet
gas rate, TM - total molar rate);
definition of variable THP (only THP value is supported);
units of this VFP table (METRIC or FIELD);
definition of the tabulated quantity in the body of the table, parameter number 4
(BHP bottom hole pressure).
2. FLO (flow rate) values ((METRIC: sm3 /day, FIELD: stb/day for oil and wa-
ter, Msc f /day for gas); for models in E300 format molar rate (METRIC:
kg moles/day, FIELD: lb moles/day)) (NFLO values), entered in ascending or-
der, terminated with a slash (/) (the number NFLO should not be greater than the 1-st
parameter of VFPIDIMS (see 12.1.30)).
3. THP values (METRIC: barsa, FIELD: psia) (NTHP values), entered in ascending
order, terminated with a slash (/) (the number NTHP should not be greater than the
2-nd parameter of VFPIDIMS (see 12.1.30)).
4. Next records, from fourth to NTHP+6.
NTHP successive records each containing the following items, and each terminated
with a slash (/).
NT (THP value number);
BHP at 1st FLO value, NTth THP value;
BHP at 2nd FLO value, NTth THP value;
.......................................
BHP at Last FLO value, NTth THP value.
All combinations of NF = 1 to NFLO, NT = 1 to NTHP must be covered.
Example
VFPINJ
1 5200 'WAT' 'THP' 'METRIC' 'BHP'/
1 200 800 900 1500 /
2500 /
1000 /
1 1.75243E+003 1.75243E+003 1.75244E+003 1.80749E+003
1.80749E+003
/
12.18.56. VFPINJ 1320

This example defines a VFP table for water injector: NFLO is equal to 5, NTHP 1.
12.18.56. VFPINJ 1321

12.18.57 VFPPROD


Section
In tNavigator VFP tables can be generated automatically using the selected corre-
lation via the keyword VFPCORR (see 12.18.61).
This keyword inputs a table of BHP values versus FLO, versus THP, versus WFR, versus
GFR, versus ALQ where
FLO is the oil, liquid or gas production rate
THP is the tubing head pressure
WFR is the water-oil ratio, water cut or water-gas ratio
GFR is the gas-oil ratio, gas-liquid ratio or oil-gas ratio
ALQ is the level of artificial lift.
If there are wells defined that require THP calculation, at least one vertical flow table
should be input. If several tables are used in calculation, each one is input separately by
VFPPROD keyword.
If in the model calculation the values are outside the range specified in the table,
the linear extrapolation will be used (to calculate the missing values from the available
values). Linear extrapolation may lead to unphysical results and should be avoided.
Make sure that the given values in the table cover all cases that may occur during
your model calculation.
If the extrapolation is used the following warning will be displayed:
Warning: At 0.9 (01 JAN 1997 21:54:00.999999) for well PROD1 extrapolation of
VFP table N 1 was performed. Current GOR value = 5.908955, max GOR value in table =
4.000000.
Warning: At 0.9 (01 JAN 1997 21:54:00.999999) extrapolation of VFP table N 1 for
well PROD1 resulted in THP value out of table range. Current THP value = 0.000000, min
THP value = 200.000000.
12.18.57. VFPPROD 1322

If the BHP is calculated using THP value that exceeds limits (specified by table) then the
following warning will be displayed:
Warning: At 9.7 (10 JAN 1997 17:21:59.867983) for well PROD1 extrapolation of VFP
table N 1 was performed. Current THP value = 10.000000, min THP value = 200.000000.
Calculated BHP value = 2071.422084.
The table consists of the following records of data, each record terminated with a slash
(/).
1. Basic data
table number (a number between 1 and the 6-th parameter of VFPPDIMS (see
12.1.31));
bottom hole datum depth for this table (METRIC: m, FIELD: f t );
definition of variable FLO (OIL Oil production rate, LIQ Liquid (oil + water)
production rate, GAS Gas production rate; for models in E300 format: WG
Hydrocarbon wet gas rate, TM - total molar rate);
definition of variable WFR (WOR Water-oil ratio, WCT Water cut (water-
liquid ratio), WGR Water-gas ratio; for models in E300 format: WWR - Water-
wet gas ratio, WTF water molar fraction);
definition of variable GFR (GOR Gas-oil ratio, GLR Gas-liquid ratio, OGR
Oil-gas ratio; for models in E300 format: MMW Mean molecular weight);
definition of variable THP (only THP value is supported);
definition of variable ALQ (GRAT lift gas injection rate (for gas-lift), COMP
compressor power);
units of this VFP table (METRIC or FIELD);
definition of the tabulated quantity in the body of the table, parameter number 7
(BHP bottom hole pressure, TEMP tubing head temperature THT).
2. FLO (flow rate) values ((METRIC: sm3 /day, FIELD: stb/day for oil and wa-
ter, Msc f /day for gas); for models in E300 data format molar rate (METRIC:
kg moles/day, FIELD: lb moles/day)) (NFLO values), entered in ascending order,
terminated with a slash (/) (the number NFLO should not be greater than the 1-st
parameter of VFPPDIMS (see 12.1.31)).
3. THP values (METRIC: barsa, FIELD: psia) (NTHP values), entered in ascending
order, terminated with a slash (/) (the number NTHP should not be greater than the
2-nd parameter of VFPPDIMS (see 12.1.31)).
4. WFR values (METRIC: sm3 /sm3 , FIELD: stb/stb WOR, WCT, stb/Msc f WGR)
(NWFR values), entered in ascending order, terminated with a slash (/) (the number
NWFR should not be greater than the 3-rd parameter of VFPPDIMS (see 12.1.31)).
12.18.57. VFPPROD 1323

5. GFR values (METRIC: sm3 /sm3 , FIELD: Msc f /stb GOR, GLR, stb/Msc f OGR)
(NGFR values), entered in ascending order, terminated with a slash (/) (the number
NGFR should not be greater than the 4-th parameter of VFPPDIMS (see 12.1.31)).
6. ALQ values (METRIC: sm3 /day, FIELD: Msc f /day if ALQ=GRAT) (NALQ values),
entered in ascending order, terminated with a slash (/) (the number NALQ should not
be greater than the 5-th parameter of VFPPDIMS (see 12.1.31)).
7. Next records, from seventh to NTHP*NWFR*NGFR*NALQ+6.

NTHP*NWFR*NGFR*NALQ successive records each containing the following items,
and each terminated with a slash (/).
NT (THP value number);

NW (WFR value number);
NG (GFR value number);
NA (ALQ value number);
BHP or THT at 1st FLO value, NTth THP value, NWth WFR value, NGth GFR
value, NAth ALQ value;
BHP or THT at 2nd FLO value, NTth THP value, NWth WFR value, NGth GFR
value, NAth ALQ value;
.......................................
BHP or THT at Last FLO value, NTth THP value, NWth WFR value, NGth GFR
value, NAth ALQ value.
All combinations of NF = 1 to NFLO, NT = 1 to NTHP, NW = 1 to NWFR, NG = 1

to NGFR, NA = 1 to NALQ must be covered.
Default:
In Basic data:
definition of the tabulated quantity in the body of the table, parameter number 7 (BHP
bottom hole pressure).
12.18.57. VFPPROD 1324

Example
VFPPROD
1 2200 'OIL' 'WCT' 'GOR' 'THP' ' ' ' METRIC' ' BHP'/
1 30 300 /
10 20 /
0 0.7 /
1 100 500 /
0 /
1 1 1 1 1.75243E+002 1.75243E+002 1.75244E+002 /
2 1 1 1 1.80749E+002 1.80749E+002 1.80750E+002 /
1 2 1 1 1.91358E+002 1.91359E+002 1.91362E+002 /
2 2 1 1 1.96743E+002 1.96744E+002 1.96747E+002 /
1 1 2 1 1.71599E+002 1.71599E+002 1.71601E+002 /
2 1 2 1 1.77093E+002 1.77093E+002 1.77095E+002 /
1 2 2 1 1.88482E+002 1.88483E+002 1.88487E+002 /
2 2 2 1 1.93865E+002 1.93866E+002 1.93869E+002 /
1 1 3 1 1.45582E+002 1.45526E+002 1.45462E+002 /
2 1 3 1 1.50977E+002 1.50978E+002 1.50979E+002 /
1 2 3 1 1.71277E+002 1.71278E+002 1.71282E+002 /
2 2 3 1 1.71277E+002 1.71278E+002 1.71282E+002 /
This example inputs table of BHP values for 3 different oil rate values, two different
THP-s, two different water cuts and three gas oil ratios.
12.18.57. VFPPROD 1325

12.18.58 VFPCHK


Section
The keyword sets the threshold BHP value for VFP table check (METRIC: barsa, FIELD:
psia). The data should be terminated with a slash /.
The keyword should be specified before VFPPROD (see 12.18.57). The case if BHP is equal
or above the threshold value is ignored in VFP table check.
VFP table check: VFP tables for producers are checked, if the curves of BHP versus flow
rate at adjacent THP values do not cross. If they cross (if the BHP increases with decreasing
THP) a warning will be printed.
Default: 1e10.
Example
VFPCHK
400 /
12.18.58. VFPCHK 1326

12.18.59 VFPTABL


Section
This keyword sets interpolation method for Artifitial Lift Quantity ALQ in VFP tables.
By default all parameter in VFP tables (FLOW, THP, WFR, GFR, ALQ) are interpolated
linearly.
The following values can be used:
1 all parameter in VFP tables (FLOW, THP, WFR, GFR, ALQ) are interpolated
linearly;
2 cubic spline interpolation is used for Artifitial Lift Quantity ALQ for producers
and linear interpolation for the other parameters. Limitation: if there are more than 20
ALQ values in the table then linear interpolation will be used for this table.
Default: 1.
Example
VFPTABL
2 /
12.18.59. VFPTABL 1327

12.18.60 WVFPEXP


Section
The keyword specifies optional closing of the well if it is found to be operating on the
stabilized part of its VFP curve. The keyword also specifies the VFP table interpolation
method.
Any number of data lines can be specified. Each line should be terminated with a slash
/. All data should be terminated with a final slash /.
2. implicit or explicit flag:
IMP VFP table for the well will be interpolated implicitly (values of the last
time step of the water and gas flowing fractions will be taken);
EXP VFP table for the well will be interpolated explicitly (values of the previous
time step of the water and gas flowing fractions will be taken);
3. flag if the well should be closed if it is found to be operating on the stabilized part
of its VFP curve: NO check is not performed, YES check is performed at the end
of each timestep, if the well is a THP-controlled producer and it is operating on a
stabilized region of its VFP curve (identification is made via zero gradient of BHP
versus flow rate) then it is closed.
4. prevent the well changing from rate control to THP control when it is constrained to
operate on the unstable side of its VFP curve? In other words, it is the flag saying
whether one can consider THP control is satisfied if THP control can be satisfied at
fluid rate value greater than the answer. Here the answer is fluid rate value at specified
THP control.
YES control can be considered as satisfied;

NO then THP value will be calculated at calculated fluid rate value. If a new
THP value doesnt satisfy control one, then well will be closed.
5. the way to extrapolate VFP table values for water fracture, gas fracture and ALQ:
WG constant values for water and gas fraction, linear interpolation for ALQ;
WGA constant values for water and gas fraction and ALQ;
12.18.60. WVFPEXP 1328

NONE linear interpolation for water and gas fraction and ALQ.
Default:
implicit or explicit flag IMP;
flag if the well should be closed if it is found to be operating on the stabilized part of
its VFP curve NO;
flag of THP control satisfying: NO;
the way to extrapolate VFP table values: WG.
Example
WVFPEXP
p45 1* YES /
p46 1* YES /
/
12.18.60. WVFPEXP 1329

12.18.61 VFPCORR


Section
The keywords sets correlation properties for producers. VFPPROD (see 12.18.57) table
is calculated by this data. Correlation methods description and calculation formulas are in the
section VFP tables generation.
Any number of data lines can be specified. Each line should be terminated with a slash
1. correlation number;
2. table type:
PROD producing;
3. correlation type (correlation formulas are in the articles [11], [14], [12], [13], [15],
[16]):
PA Petalaz & Aziz;

HB Hagedorn & Brown;
BB Beggs & Brill;
O Orkiszewski;
G Gray;
AGF Aziz, Govier & Fogarasi;
MB Mukherjee & Brill.
4. absolute roughness (METRIC: m, FIELD: f t );
5. well bore radius (METRIC: m, FIELD: f t );
6. TD Target Depth (METRIC: m, FIELD: f t ) (parameter Z2 on the picture 26). This

is the bottom hole datum depth for the VFPCORR line which is comparable to the
bottom hole reference depth in the heading of a VFP table defined in VFPPROD (see
12.18.57). This is used in case the BHP depth of a well using a particular VFP table is
different to the VFP table reference depth so that a simple hydrostatic correction can
be calculated;
12.18.61. VFPCORR 1330

Figure 26: Well bore illustration
7. MD Measured Depth (well bore length) (METRIC: m, FIELD: f t ) (parameter l =

a + b on the picture 26). This is the length of the tube that is used for pressure drop
calculations;
8. temperature inside well bore (METRIC: C , FIELD: F );
9. KOP Kick-off point (METRIC: m, FIELD: f t ) (parameter Z1 on the picture 26).

This is the TVD of the heel of the well;
10. PVT-region number.
Default:
table type: PROD;
correlation type: PA.
For the Beggs & Brill correlation angle is used (see the picture 26). This angle is
calculated from the triangle (as we know its sides).
Example
VFPCORR
1 1* HB 0.0015 0.05 2200 3437 40 2200 1 /
/
12.18.61. VFPCORR 1331

In the example the keyword VFPCORR sets correlation properties: correlation number,
table type, correlation type Hagedorn & Brown and other parameters.
Example
VFPCORR
1 1* HB 0.0015 0.05 1200 1200 40 1200 1 /
2 1* HB 0.0015 0.05 2200 3437 40 2200 2 /
/
In this example 2 tables are specified.
12.18.61. VFPCORR 1332

12.18.62 WECON


Section
This keyword defines economic limit for production wells.

The following parameters are to be specified (terminated with a slash /):
2. lower economic limit of oil rate (METRIC: sm3 /day, FIELD: stb/day), in case of
violation well will be SHUT or STOP according to the 9-th parameter of the keyword
WELSPECS (see 12.18.3);
3. lower economic limit of gas rate (METRIC: sm3 /day, FIELD: Msc f /day), in case of
WELSPECS (see 12.18.3);
4. upper economic limit of water cut (METRIC: sm3 /sm3 , FIELD: stb/stb).
tNavigator additional functionality: if negative value X is specified, the value X
will be used as lower economic limit of watercut;
5. upper economic limit of gas-oil ratio (METRIC: sm3 /sm3 , FIELD: Msc f /stb).
will be used as lower economic limit of gas-oil ratio;
6. upper economic limit of water-gas ratio (METRIC: sm3 /sm3 , FIELD: stb/Msc f ).
will be used as lower economic limit of water-gas ratio;
7. workover action for watercut violation, gas-oil ratio violation, water-gas violation or
gas-liquid ratio violation:
NONE do nothing,
WELL shut in or step the well (9-th parameter of WELSPECS (see 12.18.3)).
8. end run flag;
NO the run continues,
12.18.62. WECON 1333

YES the run will be stopped at the next report time step in case if the well is
shut or stopped for any reason after being opened;
9. name of well that will be open if the well, specified in parameter 1, is shut due
to violation of economic limits. This well should be specified as SHUT producer or
injector There will be non-zero time to open this well in case if it is specified in the
keyword WDRILTIM (see 12.18.202). Also there can be a non-zero waiting time of
drilling rig availability (GRUPRIG (see 12.18.207));
10. parameter to which minimum economic limits will be applied (limits in parameters 2,
3, 14).
RATE The limits are applied to well flow rates.

Minimal rate is not checked for wells if their rate targets is cut back because of
prioritization (GCONPRI (see 12.18.75)). This prevents them from being closed
while temporarily flowing with a small target rate.
POTN The limits are applied to well production potential (possible rate in case
if there are no rate limits but there are limits BHP, THP and the drawdown limit
(WELDRAW (see 12.18.104)). Well potentials 5.7.7.
If the wells rate was cut to meet group target, then this option provides not to
check minimal economical limit.
If the well is under prioritization (GCONPRI (see 12.18.75)), then its potential
is checked against the minimum economic limits (also is case if the well is not
currently working). The well will be closed if the potential is too small.
11. secondary maximum watercut limit. This parameter is applied according to the
workover action for watercut violation specified in 12-th parameter;
12. workover action for secondary watercut (parameter 11) violation.

For the operations CON, CON+, WELL tNavigator works the following way.
If workover operations were applies to the well because the the violation of the primary
water cut limit (parameter 4), then it is shut when its last connection is closed. If the
secondary water cut limit is specified then the well will be reopened at the the next time
step and the secondary water cut limit will be checked instead of primarily limit. All
wells connections that were closed in the previous workovers are reopened (they can
be closed again according to workover specified in 12-th parameter when the secondary
water cut limit is violated).
Possible workover operations:
NONE do nothing,
WELL shut in or step the well (9-th parameter of WELSPECS (see 12.18.3)),
12.18.62. WECON 1334

LAST this action is applied to the last open connection in the well. If the well
has only one connection left open and it begins to violate its primary watercut
limit (parameter 4) again, the well remains open until it exceeds its secondary
watercut limit (parameter 11). Other connections, that were closed in previous
workovers can not be reopened.
RED The well is worked over each time it violates its primary watercut limit
(parameter 4). Each workover closes the number of connections to reduce the
wells watercut to the value below the specified secondary limit (parameter 11).
In case if the well can be worked over to achieve its secondary limit, it is not
worked over again until the primary limit is again violated.
13. upper economic limit of gas-liquid ratio (METRIC: sm3 /sm3 , FIELD: Msc f /stb).
will be used as lower economic limit of gas-liquid ratio;
14. lower economic limit of liquid rate (METRIC: sm3 /day, FIELD: stb/day), in case of
WELSPECS (see 12.18.3).
Default:
lower oil rate economic limit 0;
lower gas rate economic limit 0;
upper water cut economic limit 0 (no limit);
upper gas-oil ratio economic limit no limit;
upper water-gas ratio economic limit no limit;
workover action: NONE;
end run flag NO the run continues;
lower liquid rate economic limit 0;
parameter to which minimum economic limits will be applied (limits in parameters 2,

3, 14) RATE
secondary maximum watercut limit 0 (no limit);
workover action for secondary watercut (parameter 11) violation workover action
specified in 7-th parameter;
upper gas-liquid ratio economic limit no limit.
12.18.62. WECON 1335

Example
WECON
p45 30 1* 0.95 2* CON /
p35 30 4* WELL /
/
This example sets limits for two wells. For well p45 minimum possible oil rate is equal
to 30, and maximum possible water cut is 95%. If oil rate falls below 30, well will be shut
in; if watercut exceeds 95%, the worst offending perforation will be closed.
For well p35 minimum possible oil rate is also equal to 30, and there is no water cut
limit. If calculated oil rate is lower than 30, the well will be automatically shut in.
12.18.62. WECON 1336

12.18.63 WECONX


Section
The keyword allows to specify economical limits of any type. This keyword is an exten-
sion of the keyword WECON (see 12.18.62), which is used by Eclipse.
1. well name/mask;
2. value to check. It can be a number or, for example, value of expression, which is
specified by the keyword UDQ (see 12.18.138);
3. comparison sign (> greater, < less, >= greater or equal, <= less or equal,
== equal, != not equal);
4. the value of the economical limit of this parameter. It can be a number or, for example,
value of expression, which is specified by the keyword UDQ (see 12.18.138);
5. workover operation:
WELL stop or shut a well;

NONE no action.
6. end calculation option:
YES calculation stops at the next timestep if the well is shut or stopped;
NO calculation will not be stopped.
7. [additional parameter] name of well to be opened if the well specified in parameter

1 will be stopped or shut.
Each line should be ended by a symbol /. The data should be terminated with a slash /.
This keyword has an Eclipse compatible analogue WECON (see 12.18.62).
Default:
workover operation: NONE;
end calculation option: NO;
12.18.63. WECONX 1337

Example
UDQ
DEFINE WUBHP WBHP /
UNITS WUBHP CONS /
/
WECONX
'WELL' WUBHP < 100 WELL /
/
In the example parameter WUBHP (which is equal to the value of WBHP) is specified
by the keyword UDQ (see 12.18.138). Then it is specified that well WELL will be shut if
pressure value will fall below 100 atm.
12.18.63. WECONX 1338

12.18.64 WECONCMF


Section
The keyword sets economical limits on component mole fractions for production wells.
1. well name (or number), or well list WLIST (see 12.18.26);
2. component index corresponding with the keyword COMPS (see 12.13.3);
3. maximal mole fraction of this component in the produced fluid. It can be specified by
the keyword UDQ (see 12.18.138);
4. workover operation:
WELL shut or stop well;

CON shut worst-offending perforation;
+CON shut worst-offending perforation and all perforations below;
NONE no action.
5. end calculation option:
YES calculation stops at the next timestep if the well is shut or stopped;
NO calculation will not be stopped.
Each line should be ended by symbol /. The data should be terminated with a slash /.
By default:
workover operation: NONE;
end calculation option: NO;
Example
WECONCMF
'PROD '1 0.4 CON NO /
In the example for the well PROD economical limit on component 1 mole fraction is set.
If mole fraction is greater than 0.4, then worst-offending perforation will be shut.
12.18.64. WECONCMF 1339

12.18.65 WGORPEN


Section
The keyword is used to control wells oil production rate target for each month via the
value of its previous months average gas-oil ratio (GOR).
The value of oil rate limit is changing each month during calculation by the following
formula:
[base GOR] [maximum rate limit]
[oil rate] = ,
[average GOR over previous month]
if oil rate doesnt exceed maximum rate limit.
1. well name (or number), or well list WLIST (see 12.18.26);
2. base GOR (METRIC: sm3 /sm3 , FIELD: Msc f /stb);
3. maximum rate limit (METRIC: sm3 /day, FIELD: stb/day);
4. initial average value of GOR (METRIC: sm3 /sm3 , FIELD: Msc f /stb).
Each line with data should be ended by symbol /. The data should be terminated with a
slash /.
Default:
initial average GOR:
if limit on GOR has just been turned on, then the value average GOR over previous
month is used by default;
if limit on GOR is not in use yet, then set equal to the wells GOR at the previous
step. If the well has just been opened, then the second value is taken by default.
Example
WGORPEN
vw1 60 8000 60 /
horw1 60 300000 60 /
/
12.18.65. WGORPEN 1340

In the example limit on GOR value is set for wells vw1 and horw1. In both cases base
and initial average values of GOR are equal to 60 sm3 /sm3 . Maximum rate limit is equal to
8000 and 300000 sm3 /day correspondingly.
12.18.65. WGORPEN 1341

12.18.66 WELLLIM


Section
This keyword is an alias for WECON (see 12.18.62).
12.18.66. WELLLIM 1342

12.18.67 CECON


Section
This keyword defines economic limit for production well connections. If any connection
violates one of its economic limits it will be automatically closed.
If COMPLUMP (see 12.18.22) lumps connections into completions, the connection eco-
nomic limits are applied to completions. All connections in one completion should have the
same limits.
2. i - coordinate of connection (connections) in X-axis direction;
3. j - coordinate of connection (connections) in Y-axis direction;
4. k1 - coordinate of upper connection in Z-axis direction;
5. k2 - coordinate of lower connection in Z-axis direction. Economic limits are applied to

all well connections (with the indexes defined by parameters 2 - 5. If i, j are defaulted,
then economic limits are applied to all well connections between layers k1 k2. If all
coordinates are defaulted - to all wells connections.
6. upper economic limit of water cut (METRIC: sm3 /sm3 , FIELD: stb/stb),
7. upper economic limit of gas-oil ratio (METRIC: sm3 /sm3 , FIELD: Msc f /stb),
8. upper economic limit of water-gas ratio (METRIC: sm3 /sm3 , FIELD: stb/Msc f ),
9. workover action for limit violation:
CON shut the connection,

+CON shut the connection and all below (the keyword COMPORD (see
12.18.24)),
WELL the well will be stopped or shut (depends on parameter 9 of the keyword
WELSPECS (see 12.18.3)).
10. continue checking stopped wells? IGNORED, this is an Eclipse compatibility field,
12.18.67. CECON 1343

11. lower economic limit of oil rate (in case of violation connection will be shut and
all connections below if it is specified in parameter 9) (METRIC: sm3 /day, FIELD:
stb/day),
12. lower economic limit of gas rate (in case of violation connection will be shut and
all connections below if it is specified in parameter 9) (METRIC: sm3 /day, FIELD:
Msc f /day).
Default:
upper economic limit of water cut no limit,
upper economic limit of gas-oil ratio no limit,
upper economic limit of water-gas ratio no limit,
workover action for limit violation CON.
lower economic limit of oil rate no limit,
lower economic limit of gas rate no limit.
Example
CECON
p45 2* 5 8 0.6 /
/
In this example there are economic limits for connection of well p45, which are located
from layer 5 to 8. Upper economic limit of water cut 0.6.
12.18.67. CECON 1344

12.18.68 WECONINJ


Section
This keyword defines economic limit for injection wells. The data (for every well) should
be terminated with a slash /. All the data should be terminated with a final slash /.
2. economic limit for water injection rate (METRIC: sm3 /day, FIELD: stb/day (water)
or Msc f /day (gas)), if the injection rate falls below the specified minimum, the well
is shut.
Default: none
Example
WECONINJ
i35 100/
/
This example sets minimum possible injection rate for well i45 equal to 100 sm3 /day.
12.18.68. WECONINJ 1345

12.18.69 WEFAC


Section
This keyword defines well efficiency factor. An arbitrary number of rows (terminated
with a slash /) can be entered. All data should be terminated with a final slash /.
The following parameters for one row are to be specified:
1. name of well (or number) or well list WLIST (see 12.18.26),
2. well efficiency factor,
3. should a wells efficiency factor be included in calculations of the branch flows and
pressure losses in the Extended Network (keywords BRANPROP (see 12.18.87),
NODEPROP (see 12.18.88)):
YES The extended network branch pressure losses is calculated using the wells
time averaged flow rate (well rate is multiplied by its efficiency factor).
NO The extended network branch pressure losses is calculated using the wells
maximum flow (well rate is not multiplied by its efficiency factor).
Default:
well efficiency factor 1;
should a wells efficiency factor be included in calculations of the branch flows and
pressure losses in the Extended Network (BRANPROP (see 12.18.87), NODEPROP
(see 12.18.88)) YES.
Example
WEFAC
P25 .89 NO/
P12 .7 /
P13 .8 /
I* .97 /
/
In this example well P25 efficiency factor is set to 89%. A wells efficiency factor is not
included in calculations of the branch flows and pressure losses in the Extended Network.
Well P12 efficiency factor is set to 70%.
Well P13 efficiency factor is set to 80%.
For all wells with name starting from letter I efficiency factor is set to 97%.
12.18.69. WEFAC 1346

12.18.70 GEFAC


Section
This keyword defines group efficiency factor. An arbitrary number of rows (terminated
with a slash /) can be entered. All data should be terminated with a final slash /.
The following parameters for one row are to be specified:
1. name of group,
2. group efficiency factor (a part of time for which the group is working. If the group
doesnt work for 15% of time, then its efficiency factor should be 0.85),
3. IGNORED, this is an Eclipse compatibility field.
Default: 1
Example
GEFAC
GROUP1 0.89 /
GROUP2 0.97 /
GROUP3 0.7 /
GROUP4 0.8 /
/
In this example efficiency factor of group GROUP1 is set to 89%. GROUP2 has efficiency
factor 97%. GROUP3 has efficiency factor 70%. GROUP4 has efficiency factor 80%.
12.18.70. GEFAC 1347

12.18.71 WORKTHP


Section
This keyword specifies the workover procedure for the well if the well cant produce at
its THP limit. (The well is under THP control).
The workover is done at the end of the time step when the well cant work, then the well is
opened at the next time step to check if it can continue working at the reduced water cut. If
the work is still not possible then the workovers are performed until all wells connection are
shut.
If the connections are lumped into completions (COMPLUMP (see 12.18.22)), then all con-
nections is the worst completion will be closed.
An arbitrary number of data lines can be specified, each terminated with a slash /. All
the data should be terminated with a final slash /.

1. name of well (or number) or well list WLIST (see 12.18.26),
2. workover procedure for the well if the well cant produce at its THP limit:
NONE do nothing (the well stops working),
CON shut connection with the highest water cut,
CON+ shut connection with the highest water cut and all connections below.
Default:
workover procedure for the well if the well cant produce at its THP limit NONE.
Example
WORKTHP
W1 CON /
W2* NONE /
WELL3 CON+ /
/
In this example the following workover procedures are provided for wells:
for the well W1 shut connection with the highest water cut;
for all wells whose names started with W2 do nothing;
for the well WELL3 shut connection with the highest water cut and all connections below.
12.18.71. WORKTHP 1348

12.18.72 GCONPROD


Section
This keyword could be specified for a well group or several groups with the same group
name root.
Any number of lines can be specified, each terminated with a slash /. all data should be
1. group name (or group name root, i.e. name ending with asterisk), or FIELD (for field
control),
2. control mode (it indicates which parameter is used for group rate calculation):
NONE no immediate control,

LRAT liquid rate control (specified via parameter 6),
ORAT oil rate control (specified via parameter 3),
WRAT water rate control (specified via parameter 4),
GRAT gas rate control (specified via parameter 5),
RESV reservoir fluid volume production rate control (specified via parameter
14),
PRBL group/field reservoir fluid volume production rate control to meet the
target production balancing fraction (specified via parameter 15),
WGRA wet gas rate control (specified via parameter 16) (only for models with
E300 type),
PBGS surface gas production rate control (target is specified via parameter 18)
(only for models with E300 type),
PBWS surface water production rate control (target specified via parameter 19)
(only for models with E300 type),
FLD group is immediately under control from a higher level group or the
FIELD, producing its share of these groups target rate, according to its guide rate
(specified via parameters 9 and 10).
3. oil rate (or limit) (METRIC: sm3 /day, FIELD: stb/day),
12.18.72. GCONPROD 1349

4. water rate (or limit) (METRIC: sm3 /day, FIELD: stb/day),
5. gas rate (or limit) (METRIC: sm3 /day, FIELD: Msc f /day),
6. liquid rate on the surface (or limit) (METRIC: sm3 /day, FIELD: stb/day),
7. workover action for oil rate violation, water rate violation, gas rate violation or liquid
rate violation:
NONE do nothing
CON shut in the worst offending perforation (in the worst offending well),
CON+ close worst offending perforation and all below (in the worst offending
well),
WELL shut in the worst offending well,
RATE group production rate is equal the violated upper limit;
TARG [this option is compatible only with tNavigator] when group rate limit
is broken, it is removed. The option works analogously to the RATE option with
the following difference. When RATE option is specified, then the corresponding
limit is always checked, when TARG option is specified, then the group limit is
removed when it cant be performed.
8. group availability for higher group production rate target: YES means that group will
switch to control from higher group if higher group level limit is violated; NO means
that group rate is not influenced by controls from above groups,
9. dimensionless number governing the groupSs share of a higher level production rate
target; phase (OIL, WAT, GAS or LIQ) is set using the next parameter of this keyword,
10. phase for the previous parameter of this keyword:
OIL,
WAT,
GAS,
LIQ liquid,
WGA wet gas,
CVAL calorific value production,
POTN groups guide rate in the beginning of each time step is set equal to the
groups production potential (sum of subordinate producers potentials). Parameter
9 is ignored in this case.
Wells potentials section 5.7.7.
12.18.72. GCONPROD 1350

FORM groups guide rate is calculated via the potential formula defined in the
keyword GUIDERAT (see 12.18.73) (this formula can be used to decrease the
input of groups with high gas-oil ratio or watercut). Parameter 9 is ignored in this
case.
11. workover action for water rate violation (limit is specified via parameter 4); Workover
choice is the same as in parameter 7 (NONE, CON, CON+, +CON, WELL, RATE);
12. workover action for gas rate violation (limit is specified via parameter 5); Workover
13. workover action for liquid rate violation (limit is specified via parameter 6); Workover
14. reservoir fluid volume production rate (or limit) (METRIC: rm3 /day, FIELD: rb/day);
15. reservoir volume production balancing fraction target or upper limit. It is calculated as
RATE group production rate is equal the violated upper limit;
16. wet gas production rate target (or limit) (METRIC: sm3 /day, FIELD: Msc f /day);
17. calorific rate target or upper limit, IGNORED, this is an Eclipse compatibility field;
18. surface gas production balancing fraction target or upper limit. The groups surface gas
volume production rate is limited so that the available gas (production gas minus fuel
gas minus sales gas) is the specified fraction (or multiple) of the groups surface gas
volume injection rate. Workover if the limit is exceeded RATE,
19. surface water production balancing fraction target or upper limit. The groups surface
water volume production rate is limited to the specified fraction (or multiple) of the
groups surface water volume injection rate. Workover if the limit is exceeded RATE.
If user specifies group control, and control mode is not NONE, simulator will modify
rates of wells (or groups) from this group to match chosen limit. For example, if ORAT is
set, rates of group producers will be recalculated in order to make group oil rate equal to oil
limit. Well rates are recalculated with weight coefficients, corresponding to their potentials.
Well potential by our definition is well production in absence of rate controls (description of
wells potential flow rate is in the section 5.7.7).
In the current version only the limit chosen by control mode will be matched, all other
limits are ignored.
Default:
group name: default group (group of wells with default group in WELSPECS (see
12.18.3)),
control mode: NONE,
oil rate limit: no rate or limit,
12.18.72. GCONPROD 1351

water rate limit: no rate or limit,
gas rate limit: no rate or limit,
liquid rate limit: no rate or limit,
group availability: YES,
groups share of a higher rate of phase production: no limit,
wet gas production rate target (or limit): no limit,
workover action for water rate violation (limit is specified via parameter 4) workover
specified in parameter 7;
workover action for gas rate violation (limit is specified via parameter 5) workover
specified in parameter 7;
workover action for liquid rate violation (limit is specified via parameter 6) workover
specified in parameter 7.
Example
GCONPROD
GROUP11 LRAT 3* 1000 RATE YES /
GROUP2* ORAT 500 3* RATE YES /
/
First line sets control for group GROUP11. It will be on liquid rate control, maximum
liquid rate for group is 1000. If group rate exceeds this limit, well rates will be recalculated
to satisfy this condition. New rates of wells will be proportional to their production potentials
(well liquid rate in absence of rate controls); all limits on well BHP and maximum rate etc
will be observed.
Second line sets control for all groups with names starting with GROUP2. They will be
on oil rate control, maximum oil rate for group is 500. If group rate exceeds this limit, well
rates will be recalculated to satisfy this condition. New rates of wells will be proportional to
their production potentials (well oil rate in absence of rate controls); all limits on well BHP
and maximum rate etc will be observed.
12.18.72. GCONPROD 1352

12.18.73 GUIDERAT


Section
The keyword specifies a general formula for calculating production guide rates (for group
control, keyword GCONPROD (see 12.18.72)).
Group flow rate targets are distributed among the wells in proportion to their guide rates.
Default: wells guide rate is equal to its potential flow rate at the beginning of each time
step. This keyword provides a means of automatically weighting production well guide rates
to take account of their production ratios. Because it could be advantageous to weight the
guide rates to discriminate against wells with high gas-oil ration or water cut.
The guide rate is calculated via the formula at the beginning of each time step:
(POT GUIDERAT E p )A
GUIDERAT E p =
B +C(R1 )D + E(R2 )F
where:
POT GUIDERAT E p wells or groups potential flow rate of the phase p (description
of wells potential flow rate is in the section 5.7.7);
A, B, C , D, E , F coefficients specified via this keyword;
R1 , R2 ratios of phase potentials, depending on the phase p (parameter 2 of the
keyword).
/.):
1. minimum time interval between guide rate calculations, IGNORED, this is an Eclipse
2. phase p (if the phase here is different from the phase under group control, calculated
guide rate is converted into a guide rate for the controlled phase using the wells or
groups production ratios at the beginning of the time step). Phase:
OIL (oil phase guide rate), phase potential ratios: R1 water-oil ratio, R2 gas-oil
ratio, (METRIC: sm3 /sm3 , FIELD: Msc f /stb);
LIQ (liquid phase guide rate), phase potential ratios: R1 watercut, R2 gas-
liquid ratio, (METRIC: sm3 /sm3 , FIELD: Msc f /stb);
12.18.73. GUIDERAT 1353

GAS (gas phase guide rate), phase potential ratios: R1 water-gas ratio, R2
oil-gas ratio, (METRIC: sm3 /sm3 , FIELD: stb/Msc f );
RES (reservoir fluid volume guide rate), phase potential ratios: R1 water-oil
ratio, R2 gas-oil ratio, (METRIC: sm3 /sm3 , FIELD: Msc f /stb);
NONE formula is not applied (guide rates are equal to wells production potentials
at every time step).
3. A;
4. B (not negative);
5. C ;
6. D;
7. E ;
8. F ;
9. can guide rate increase or not:
YES guide rates can increase if the formula gives a value higher than previous
value;
NO phase guide rates cant increase if formula gives a value higher than previous
value. Guide rate can only decrease or remain as before. If the formula gives a
value higher than previous value, tNavigator will keep the guide rate value equal
to the previous one.
10. damping coefficient, GRDAMP. The value should obtain the interval (0;1). It provides
a means of damping guide rate oscillations that may result from rate-dependent water
cut or gas-oil ratio. Each time a new guide rate is calculated for a well or group, it is
averaged with its previous value via the formula:
GRused = GRDAMP GRcalculated + (1 GRDAMP)GR previous .
11. use free gas and not total gas potential rates in the phase potential ratio R2 :
YES only use free gas (at well-block conditions) in the potential ratio;
NO use total (free and dissolved) gas in the potential ratio.
12. minimum guide rate GRmin . If the calculated guide rate GR p is less than the minimum
GRmin , it will be set to the minimum. GRmin should satisfy condition GRmin > 1019
f low.
Default:
phase p NONE;
12.18.73. GUIDERAT 1354

A 0;
B 0;
C 0;
D 0;
E 0;
F 0;
can guide rate increase or not YES;
damping coefficient 1;
use free gas and not total gas potential rates in the phase potential ratio R2 : NO;
GRmin 106 .
Example
GUIDERAT
1* RES 1.0 1.0 2* 10 2 /
In this example phase - reservoir fluid volume, A 1, B 1, C , D 0 (default values),

E 10, F 2.
The formula is:
POT GUIDERAT ERES
GUIDERAT ERES =
1 + 10(R2 )2
In this case for the wells with low gas-oil ratio the reservoir fluid volume guide rate is equal
to their potentials. For the wells with high gas-oil ratio the reservoir fluid volume guide rate
is equal to their potentials reduced according to the formula above.
12.18.73. GUIDERAT 1355

12.18.74 WREGROUP


Section
This keyword sets automatic regrouping of wells depending of watercut, oil rate or an-
other specified parameter.
The well transfer take place at the start of the next time step after a time step when
specified limit of parameter has been passed. The transfer take place instantaneously.
1. well name, well name template or well list (WLIST (see 12.18.26)),
2. parameter name that controls regrouping process:
WCT watercut,
GOR gas-oil ratio,
WGR water-gas ratio,
ORAT oil rate,
GRAT gas rate,
THP tubing head pressure,
' ' no automatic regrouping for this well.
3. group name into which the well should be moved when its specified parameter value
exceeds the value in parameter 4;
4. value of the parameter (specified in 2) above which the well is moved into the group
specified in parameter 3 (the value should be not less than the value of parameter 6);
5. group name into which the well should be moved when its specified parameter value
falls below the value in parameter 6;
6. value of the parameter (specified in 2) below which the well is moved into the group
specified in parameter 5 (the value should be not greater than the value of parameter
4).
12.18.74. WREGROUP 1356

Default:
parameter name that controls regrouping process: ' ' ;
group name into which the well should be moved when its specified parameter value
exceeds the value in parameter 4: the group to which the well was assigned in the
keyword WELSPECS (see 12.18.3);
value of the parameter (specified in 2) above which the well is moved into the group
specified in parameter 3: 1e20;
group name into which the well should be moved when its specified parameter value
falls below the value in parameter 6: the group to which the well was assigned in the
value of the parameter (specified in 2) below which the well is moved into the group
specified in parameter 5: 0.
Example
WREGROUP
WELL3 THP GROUP4 50 1* 30 /
WELL1 WCT GROUP1 0.45 1* 0.2 /
/
In this example:
WELL3 will be moved to the GROUP4 in case if the THP exceeds 50 bar, if THP falls
below 30 bar, then the well will be moved to the group to which the well was assigned in
the keyword WELSPECS (see 12.18.3).
WELL1 will be moved to the GROUP1 in case if the watercut exceeds 45%, if watercut
falls below 20%, then the well will be moved to the group to which the well was assigned
in the keyword WELSPECS (see 12.18.3).
12.18.74. WREGROUP 1357

12.18.75 GCONPRI


Section
This keyword specifies production rate limits for well group when an option of well
prioritization is used 2.19.11. Priority formulas are specified in PRIORITY (see 12.18.78).

control),
2. oil production rate upper limit (METRIC: sm3 /day, FIELD: stb/day),
3. workover action for oil rate violation:
NONE no action,
well),
PRI control group production rate by prioritization (using the first priority for-
mula if there are two formulas in PRIORITY (see 12.18.78)),
PR2 control group production rate by prioritization (using the second formula).
4. water production rate upper limit (METRIC: sm3 /day, FIELD: stb/day),
5. workover action for water rate violation:
NONE no action,
well),
12.18.75. GCONPRI 1358

6. gas production rate upper limit (METRIC: sm3 /day, FIELD: Msc f /day),
7. workover action for gas rate violation:
NONE no action,
well),
8. liquid production rate or upper limit in surface conditions (METRIC: sm3 /day, FIELD:
stb/day),
9. workover action for liquid rate violation:
NONE no action,
well),
10. liquid production rate upper limit in reservoir conditions (METRIC: rm3 /day, FIELD:
rb/day). If this limit is violated PRI is taken.
11. reservoir volume production balancing fraction upper limit. IGNORED. This is an
Eclipse compatibility field.
12. wet gas production rate upper limit (METRIC: sm3 /day, FIELD: Msc f /day),
13. workover action for wet gas rate violation:
12.18.75. GCONPRI 1359

NONE no action,
well),
Default:
oil production rate upper limit no limit,
workover action for oil rate violation: NONE no action,
water production rate upper limit no limit,
workover action for water rate violation: NONE no action,
gas production rate upper limit no limit,
workover action for gas rate violation: NONE no action,
liquid production rate upper limit in surface conditions no limit,
workover action for liquid rate violation: NONE no action,
liquid production rate upper limit in reservoir conditions no limit,
wet gas production rate upper limit no limit,
workover action for wet gas rate violation no action.
Example
GCONPRI
GR2 750 PR2 2* 9000 PRI/
In this example: open wells in decreasing order of priority (via PR2) if oil rate upper
limit is violated. Open wells in decreasing order of priority (via PRI) if gas rate upper limit
is violated.
12.18.75. GCONPRI 1360

12.18.76 GPMAINT


Section
The keyword specifies well group data for pressure maintenance in fluid-in-place re-
gions (FIP-regions) (E100) or in pressure maintenance region (E300, regions are specified
via PMANUM (see 12.4.16)) at specified target value.
Groups flow targets (for the quantity specified in parameter 2) is calculated for each time
step via the following formula:
(E l)
V = Vi + K(E + )
Ctime
where:
Vi initial rate at the time when the keyword is specified;

K proportionality constant (parameter 6 of this keyword);
E integral time constant (parameter 7 of this keyword);
Ctime regions pressure error at the end of the previous time step (Ptarg Preg ), (Ptarg
pressure target, parameter 5 of this keyword);
(E l) cumulative sum of the pressure error times the time-step length, up to the
previous time step, starting from the time the keyword was most recently entered.
Any number of lines can be specified for this keyword, each terminated with a slash /.
all data should be terminated with a final slash /.

1. group name (or group name root ending with *), or FIELD.
This group maintains the average pressure in the specified region, by adjusting its
production or injection rate (parameter 2). One or more groups can maintain pressure
in one region.
2. flow target to pressure control:
PROD groups production rate in reservoir conditions is adjusted (RESV) (for
PROD the group shouldnt be under prioritization group control GCONPRI (see
12.18.75)),
12.18.76. GPMAINT 1361

OINJ groups oil injection rate in reservoir conditions is adjusted (RESV),

WINJ groups water injection rate in reservoir conditions is adjusted (RESV),
GING groups gas injection rate in reservoir conditions is adjusted (RESV)
(for compositional models composition of injected gas should be specified via
GINJGAS (see 12.18.165)),
OIS groups oil injection rate in surface conditions is adjusted,
WINS groups water injection rate in surface conditions is adjusted,
GINS groups gas injection rate in surface conditions is adjusted (for composi-
tional models composition of injected gas should be specified via GINJGAS (see
12.18.165)),
NONE groups flow is no longer adjusted to maintain pressure.
3. region number, whose pressure this group controls.
E100 models. Fluid-in-place region number. 0 FIELD. The fluid-in-place region
family (to which this region belongs) is specified in the next parameter.
E300 models. Pressure maintenance region number (regions are specified via the
keyword PMANUM (see 12.4.16)).
4. fluid-in-place region family, to which belongs the region, specified in 3-rd parameter
(region FIPNUM (see 12.4.10), FIP (see 12.4.11) etc.);
5. target pressure for the region (METRIC: barsa, FIELD: psia). The well group tries to
maintain the regions average pressure at this value;
6. proportionality constant. At each time step, the groups target rate is equal to the
proportionality constant multiplied by the regions pressure error term (METRIC: rm3
or sm3 /day/bar , FIELD: rb or stb/day/psi);
7. integral time constant. The integral of the regions pressure error over time, divided
by the integral time constant, is added to the current pressure error (METRIC: days,
FIELD: days).
Default:
fluid-in-place region family, to which belongs the region, specified in 3-rd parameter
FIPNUM (see 12.4.10);
Example
GPMAINT
FIELD WINJ 0 1* 245 30 70 /
/
In this example group FIELD will try to maintain the field average pressure at the value
245 bar, via groups water injection rate in reservoir conditions is adjusting.
12.18.76. GPMAINT 1362

12.18.77 GPMAINT3


Section
The keyword is using to control group production and injection rate so as to maintain the
average pressure in a particular pressure maintenance region at a specified target value. This
keyword is deprecated, it is recommended to use the keyword GPMAINT (see 12.18.76).
In each line the following parameters should be specified:
1. group name;
2. flow target to control the pressure:
PROD the groups production in reservoir conditions (RESV) rate is controlled;

WINJ the groups water injection rate in reservoir conditions (RESV) rate is
controlled,
GINJ the groups gas injection rate in reservoir conditions (RESV) rate is con-
trolled, (only for E100 models for E300 models gas composition should be
specified by the keyword GINJGAS (see 12.18.165)),
WINS the groups water injection rate in surface conditions rate is controlled,
GINS the groups gas injection rate in surface conditions rate is controlled, (only
for E100 models for E300 models gas composition should be specified by the
keyword GINJGAS (see 12.18.165)),
WAT water is injected, the target specified in parameter 9 is controlled;
GAS water is injected, the target specified in parameter 9 is controlled;
ST the molar composition of the injected fluid which defined by the keyword
WELLSTRE (see 12.18.159). The name of the injection stream must be specified
in item 8. The target specified in parameter 9 is controlled;
MIX The molar composition of the injected fluid has been defined as a mix-
ture using either the WINJMIX (see 12.18.162) or WINJORD (see 12.18.163)
keywords. The name of the mixture must be specified in parameter 8. The target
specified in parameter 9 is controlled;
WV the molar composition of the injected fluid is to be taken from the va-
por production of a specified well. The name of the well must be specified in
parameter 8. The target specified in parameter 9 is controlled;
12.18.77. GPMAINT3 1363

GV the molar composition of the injected fluid is to be taken from the vapor
production of a specified group. The name of the group must be specified in
parameter 8. The target specified in parameter 9 is controlled;
NONE the groups flow is no longer adjusted to maintain pressure.
3. pressure maintenance region number. Specified group controls pressure of this region;
4. this item is not used in E300 models; it is retained for compatibility with E100 models.
This parameter must be defaulted;
5. the target pressure value for the region (METRIC: barsa, FIELD: psia);
6. the proportionality constant for controlling the groups rate (METRIC: rm3 /day/bar ;
FIELD: rb/day/psi);
7. the integral time constant, for controlling the groups flow rate (METRIC: Day; FIELD:
Day);
8. name of the wellstream, mixture, well or group that defines or supplies the injection
stream (it is should be specified, if the composition of the injection fluid was specified
in parameter 2 using the ST, MIX, GV or WV methods);
9. the target which is controlled to maintain the pressure:
WA water injection rate in surface conditions;
GA gas injection rate in surface conditions;
RV volume injection rate in reservoir conditions;
WG wet gas rate.
It is required if item 2 was set to WAT, GAS, ST, MIX, WV or GV;
10. maximum reinjection fraction. This parameter provides an upper limit on the rate at
which the group in parameter 1 may inject, with this rate limit defined as the reinjection
fraction multiplied by the water or available gas rate of the group or well named in
parameter 12;
11. the type of production that the reinjection fraction multiplies (this need only be supplied
if a reinjection fraction has been set in parameter 10):
W the production rate of the well specified in parameter 12;
G the production rate of the group specified in parameter 12.
12. the name of the group or well that controls the reinjection limit. This need only be
supplied if a reinjection fraction has been set in parameter 10. If parameter 11 is W
it should be the name of a production well. If parameter 11 is G then it should be
the name of a group. If this name is not specified, it defaults to the fluid composition
source name (parameter 8) for injection fluids WV or GV in parameter 2, and to the
name of the group in parameter 1 for the other cases;
12.18.77. GPMAINT3 1364

13. name of a wellstream to be used as make-up gas (specified via WELLSTRE (see
12.18.159)). This is only required if make-up gas is to be used when there is insufficient
available gas from the source group or well to supply the injection gas for pressure
maintenance;
14. interpretation of the reinjection fraction defined in parameter 10 for gas injection:
TOT the gas injection rate of the group is limited by the reinjection fraction
multiplied by the available produced gas rate of the group.
Default:
pressure maintenance region number: 1;
maximum reinjection fraction: 0;
the type of production that the reinjection fraction multiplies:
W, if parameter 2 is WV;
G otherwise.
interpretation of the reinjection fraction: TOT.
Example
GPMAINT3
ARAB-A2 MIX 2 1* 5100 100 30 IGAS GA /
ARAB-B MIX 3 1* 5100 100 30 IGAS GA /
ARAB-C MIX 4 1* 5100 100 30 IGAS GA /
ARAB-D MIX 5 1* 5100 100 30 IGAS GA /
/
In the example 4 well groups (ARAB-A2, ARAB-B, ARAB-C, ARAB-D) holds pressure
value of 5100 psia in regions 2, 3, 4 and 5 correspondingly. The proportionality constant
for controlling the groups rate is 100 rb/day/psi, controlling time of the groups rate is 30
days. Fluid 'IGAS'is injected, target which is controlled to maintain the pressure is gas at
surface conditions.
12.18.77. GPMAINT3 1365

12.18.78 PRIORITY


Section
The keyword sets coefficients to the well priority formula in group control with well
prioritization option 2.19.11, keyword GCONPRI (see 12.18.75).
This option is alternative to the method of distribution group production rates among
wells according to their guide rates (is this case groups are specified via GCONPROD (see
12.18.72)).
Well prioritization option description.

Wells priorities are calculated according to formula specified in PRIORITY (see
12.18.78).
Wells are turned on in decreasing order of their priority (well with the highest priority
is the first).
Wells are turned on until groups production rate limit is exceeded.
A rate of well, which exceeds the groups limit, is cut to meet the limit (in spite of its
own limits WCONPROD (see 12.18.34)).
Wells with low priority are closed until they are selected to produce.
Wells, which violate economic limits, and are closed manually cant be selected to
produce.
2 priority formulas can be specified and they can be used as PRI and PR2 in GCONPRI
(see 12.18.75)).
If 2 limits that have different priority formulas are exceeded, then to close the well
with the lowest priority the formula is chosen for which limit is exceeded more (in
percentage terms).
Priorities are calculated for the well at each Newton iteration of time step for first
NUPCOL (see 12.18.208) iterations via the formula (coefficients are specified in
PRIORITY (see 12.18.78)):
A + BPO +CPW + DPG
PRIORITY =
E + FPO + GPW + HPG
where:
12.18.78. PRIORITY 1366

Pp potential well rate for the phase p (description of wells potential flow rate
is in the section 5.7.7);
A, B, C , D, E , F , G, H coefficient from PRIORITY (see 12.18.78).
Wells priorities calculated via formulas PRIORITY (see 12.18.78) can be overridden
via numbers specified directly in the keyword WELPRI (see 12.18.79);
In group hierarchy both methods of potential guide rates GCONPROD (see 12.18.72)
and well prioritization GCONPRI (see 12.18.75) can be used at the same time, except
for the case when the group uses guide rate method and this group is subgroup of the
group that uses well prioritization.
When 2 methods are used at the same time, then first prioritization groups are solved,
and then the producers in the remaining part of group hierarchy that use guide rates.
/.):
1. minimum time interval between well priority calculations. If zero value is specified
priorities will be recalculated every timestep;
2. not negative coefficients A H for the first priority formula (PRI in GCONPRI (see
12.18.75)). One or more coefficient from first four coefficients and one of more coef-
ficient from next four coefficients should be not zero;
3. not negative coefficients A H for the second priority formula (PR2 in GCONPRI
(see 12.18.75)). One or more coefficient from first four coefficients and one of more
coefficient from next four coefficients should be not zero.
Default:
A H 0.
Example
PRIORITY
1* 0 0 0 1 1 0 0 0 0 1 0 0 1 0 0 0 /
2 priority formulas are specified.

There is the first formula (Open wells in decreasing order of gas potential):
A + BPO +CPW + DPG 1 PG
PRI = = = PG
E + FPO + GPW + HPG 1
There is the second formula (Open wells in decreasing order of oil potential):
A + BPO +CPW + DPG 1 PO
PR2 = = = PO
E + FPO + GPW + HPG 1
12.18.78. PRIORITY 1367

12.18.79 WELPRI


Section
This keyword sets priority numbers for production wells. These numbers will override
priority values calculated via priority formulas (the keyword PRIORITY (see 12.18.78)).

2. first priority number for the well:
positive number is specified this number will override priority value calculated
via the first priority formula;
negative number is specified well priority value is calculated via the first priority
formula.
3. first priority factor. The wells first priority number (specified via 2-nd parameter or
calculated via the first priority formula) is multiplied by this factor;
4. second priority number for the well:
positive number is specified this number will override priority value calculated
via the second priority formula;
negative number is specified well priority value is calculated via the second
priority formula.
5. second priority factor. The wells second priority number (specified via 4-th parameter
or calculated via the second priority formula) is multiplied by this factor;
Default:
first priority number for the well negative;
first priority factor 1;
second priority number for the well negative;
second priority factor 1.
12.18.79. WELPRI 1368

Example
WELPRI
W1 1* 2.0 /
/
12.18.79. WELPRI 1369

12.18.80 WGRUPCON


Section
The keyword specifies well guide rates for group control. An arbitrary number of data
lines can be specified (terminated with a slash /). All data should be terminated with a final
slash /.
1. well name or well list specified via WLIST (see 12.18.26);
2. is the well available for group control: YES yes, the well automatically works under
group control if a rate target is set for its group, NO no, the well flows according to
its own limits;
3. wells guide rate (the value that specifies wells share in the groups target rate). The
target well rates (that are under group control) are calculated proportionally to their
guide rates. If zero or negative guide rate is specified, then in the beginning of the time
step it will be calculated according to the formula in GUIDERAT (see 12.18.73). If
the formula is not specified then it is equal to wells production or injection potentials
(description of wells potential flow rate is in the section 5.7.7);
4. phase to which the wells guide rate applies:
OIL oil phase;

WAT water phase;
GAS gas phase;
LIQ liquid phase;
RAT flow rate of the injected phase in surface conditions (for injectors);
RES fluid volume rate in reservoir conditions.
5. guide rate factor (wells guide rate, specified in parameter 3, or calculated will be
multiplied by this factor.
Default:
is the well available for group control: YES yes;
wells guide rate negative;
12.18.80. WGRUPCON 1370

guide rate factor 1.
Example
WGRUPCON
WELL1 YES 10 OIL/
WELL2 YES 20 OIL/
WELL3 YES 40 OIL/
WELL4 YES 10 OIL/
WELL5 NO/
WELL6 NO/
/
In this example wells that are available for group control: WELL1, WELL2, WELL3,
WELL4. For these wells guide rates for oil phase are specified. Wells flow according to its
own limits: WELL5, WELL6.
12.18.80. WGRUPCON 1371

12.18.81 GCONINJE


Section
This keyword could be specified for a well group or several groups with the same group
name root. The following parameters should be specified:
control),
2. injected fluid to which group control will apply (WATER; GAS or OIL).
Note: for model in E300 format the composition of the injected gas should be specified
via GINJGAS (see 12.18.165), unless the group is under control of the group with gas
injection control where the injected gas is defined,
3. group control:
NONE no immediate control,

RATE injection rate control,
RESV reservoir volume injection rate (total reservoir volume injection rate of
the group meets the parameter 5 of this keyword),
REIN group injection will be equal to group production of the same phase
multiplied by re-injection fraction specified in parameter 6,
VREP group injection in reservoir conditions will be equal to group production
in reservoir conditions multiplied by voidage replacement fraction specified in
parameter 7,
4. surface rate of injected fluid (or limit) (METRIC: sm3 /day, FIELD: stb/day for oil
and water, Msc f /day for gas),
5. reservoir rate of injected fluid (or limit) (METRIC: rm3 /day, FIELD: rb/day). If the
value is specified by this parameter the phase (parameter 2) is declared the top-up
phase. Its target or limited reservoir volume injection rate will be equal to the value
specified here minus the reservoir volume injection rate of other phases. The phase
injection rate is calculated to top up the total group injection to the required reservoir
volume rate, after allowing for any injection of the other phases. There can be only
one top-up phase at any given time in the simulation run,
6. re-injection fraction target (limit), used when group control is set to REIN,
7. voidage replacement target (limit), used when group control is set to VREP,
12.18.81. GCONINJE 1372

8. group availability for higher group production rate target: YES means that group will
switch to control from higher group if higher group level limit is violated; NO means
that group rate is not influenced by controls from above groups,
9. groups injection guide rate (phase is set using the 2-nd parameter of this keyword).
The next parameter of this keyword defines the type of the guide rate. This parameter
should be defaulted if the next parameter is NETV.
Note. For models in E300 format if a zero guide rate is specified: the groups guide
rate at the beginning of each timestep is set equal to the groups injection potential (the
sum of the injection potentials of all of its subordinate open injectors).
10. definition of the guide rate for the previous parameter. Current version of tNavigator
support the following options:
RATE guide rate applies to groups surface injection rate;

NETV guide rate is set at the beginning of each time step equal to the groups
net voidage potential (that is its voidage production potential minus the reservoir
volume injection potential of any other phases).
11. group name. The group, specified in parameter 1 can re-inject a fraction of another
groups production rate, the name of this group should be specified here. The re-
injection fraction is specified in parameter 6.
12. group name. The group, specified in parameter 1 can replace a fraction of another
groups voidage, the name of this group should be specified here. The voidage replace-
ment fraction is specified in parameter 7.
If user specifies group control, and control mode is not NONE, simulator will modify
rates of wells (or groups) from this group to match chosen limit. For example, if RATE is
set, and phase is WATER, rates of group water injectors will be recalculated in order to
make group water injection rate equal to specified limit. Well rates are recalculated with
weight coefficients, corresponding to their potentials. Well potential by our definition is well
injection in absence of rate controls.
In the current version only the limit chosen by control mode will be matched, all other
limits are ignored.
Default:
12.18.3)),
control mode: NONE,
rate limit: no rate or limit,
group availability: YES,
12.18.81. GCONINJE 1373

groupss share of a higher rate of phase injection: no limit.
group name. The group, specified in parameter 1 can re-inject a fraction of another
groups production rate, the name of this group should be specified here: The group,
specified in parameter 1 re-injects a fraction of its own production rate.
group name. The group, specified in parameter 1 can replace a fraction of another
groups voidage, the name of this group should be specified here: The group, specified
in parameter 1 replaces a fraction of its own voidage.
Example
GCONINJE
INJ11 WATER RATE 253.1 2* /
GRP1* WATER VREP 3* 1.1 /
/
First line sets control for group INJ11. It is on water injection rate control, the rate is
equal to 253.1. If group water injection rate exceeds this limit, water injector rates will
be recalculated to satisfy this condition. New rates of wells will be proportional to their
injection potentials (well injection rate in absence of rate controls); all limits on well BHP
and maximum rate etc will be observed.
Second line sets control for all groups with names starting with GRP1. They will be
on voidage replacement control, i.e. injectors will inject in reservoir conditions the same
volume, as produced by this group, multiplied by voidage replacement coefficient (1.1).
If group injection exceeds this limit, well injection rates will be recalculated to satisfy
this condition. New rates of wells will be proportional to their injection potentials (water
injection rate in absence of rate controls); all limits on well BHP and maximum rate etc will
be observed.
12.18.81. GCONINJE 1374

12.18.82 GCONSUMP


Section
The keyword sets gas consumption and import rates for well groups.
For group re-injection control (GCONINJE (see 12.18.81)):

Groups gas injection rate = Groups re-injection fraction *
(Groups gas production rate + Gas import rate to the group (and subordinate) -
Groups gas consumption rate (and subordinate groups gas consumption)).
An arbitrary number of data lines can be entered (terminated with a slash /). All data

1. group name (or group name root, i.e. name ending with asterisk), or FIELD;
2. gas consumption rate for the group (METRIC: sm3 /day, FIELD: Msc f /day). Also a
negative value from the interval (-1, 0) can be entered. This value is used to specify
gas consumption rate as a fraction of group gas production.
A value -0.3: gas consumption is equal to 30% of group gas production rate.
Can be specified by user via UDQ (see 12.18.138);
3. gas import rate for the group (METRIC: sm3 /day, FIELD: Msc f /day).
Default:
gas consumption rate for the group 0 (METRIC: sm3 /day, FIELD: Msc f /day);
gas import rate for the group 0 (METRIC: sm3 /day, FIELD: Msc f /day).
Example
GCONSUMP
GROUP1 1* 800 /
GROUP2 -0.2 /
/
In this example GROUP1 imports 800 sm3 /day of gas, GROUP2 consumes 20% of its
gas production rate.
12.18.82. GCONSUMP 1375

12.18.83 GSATPROD


Section
The keyword specifies oil, water, gas rate for satellite group.
Satellite groups can be used to take into account known production and injection flows from
other reservoirs or regions that are not part of this model. Satellite groups act as sources of
production and injection flow. Satellite groups shouldnt have associated wells or subordinate
groups.
The rates (specified by the keyword) stay constant until they are replaced via the values
from the next keyword GSATPROD. Injection rate for satellite groups should be set via the
keyword GSATINJE (see 12.18.84).
1. satellite group name (or group name root, i.e. name ending with asterisk).
When the group is used first time in the keyword GSATPROD (see 12.18.83) or
GSATINJE (see 12.18.84), it is defined as a satellite group. In a multilayer hierarchy
the group should be defined previously in the keyword GRUPTREE (see 12.18.85) (to
define its position in the group hierarchy) else it will be directly subordinate to FIELD.
2. oil production rate from the satellite group (METRIC: sm3 /day, FIELD: stb/day),
3. water production rate from the satellite group (METRIC: sm3 /day, FIELD: stb/day),
4. gas production rate from the satellite group (METRIC: sm3 /day, FIELD: Msc f /day),
5. fluid production rate from the satellite group in reservoir conditions (METRIC:
rm3 /day, FIELD: rb/day).
Default:
oil production rate from the satellite group 0 (METRIC: sm3 /day, FIELD: stb/day),
water production rate from the satellite group 0 (METRIC: sm3 /day, FIELD:
stb/day),
gas production rate from the satellite group 0 (METRIC: sm3 /day, FIELD: stb/day),
12.18.83. GSATPROD 1376

fluid production rate from the satellite group in reservoir conditions 0 (METRIC:
rm3 /day, FIELD: rb/day).
Example
GRUPTREE
I FIELD /
J FIELD /
PRODSAT1 FIELD /
PRODSAT2 FIELD /
/
...
GSATPROD
PRODSAT1 1* 2000 /
PRODSAT2 1* 1000 /
/
In this example group hierarchy is specified via the keyword GRUPTREE (see 12.18.85).
2 satellite groups are defined: PRODSAT1, PRODSAT2.
Oil production rate is defaulted for both groups - 0. Water production rate for PRODSAT1 -
2000sm3 /day, water production rate for PRODSAT1 - 1000sm3 /day.
12.18.83. GSATPROD 1377

12.18.84 GSATINJE


Section
The keyword specifies oil, water, gas injection rate for satellite group.
Satellite groups can be used to take into account known production and injection flows from
other reservoirs or regions that are not part of this model. Satellite groups act as sources of
production and injection flow. Satellite groups shouldnt have associated wells or subordinate
groups.
The rates (specified by the keyword) stay constant until they are replaced via the values
from the next keyword GSATINJE. Production rate for satellite groups should be set via the
keyword GSATPROD (see 12.18.83).
1. satellite group name (or group name root, i.e. name ending with asterisk).
When the group is used first time in the keyword GSATPROD (see 12.18.83) or
GSATINJE (see 12.18.84), it is defined as a satellite group. In a multilayer hierarchy
the group should be defined previously in the keyword GRUPTREE (see 12.18.85) (to
define its position in the group hierarchy) else it will be directly subordinate to FIELD.
2. phase to which the injection rate is specified in next parameters: OIL, WAT, GAS (if
satellite group injects several phases then each phase should be specified in its own
data line),
3. phase injection rate in surface condition (METRIC: sm3 /day, FIELD: stb/day for
oil and water, Msc f /day for gas),
4. phase injection rate in reservoir condition (METRIC: rm3 /day, FIELD: rb/day).
Default:
phase injection rate in surface condition 0 (METRIC: sm3 /day, FIELD: stb/day),
phase injection rate in reservoir condition 0 (METRIC: rm3 /day, FIELD: rb/day).
12.18.84. GSATINJE 1378

Example
GRUPTREE
I FIELD /
J FIELD /
INJSAT1 FIELD /
INJSAT2 FIELD /
/
...
GSATINJE
INJSAT1 WAT 20 /
INJSAT2 GAS 250 /
INJSAT2 WAT 10 /
/
In this example group hierarchy is specified via the keyword GRUPTREE (see 12.18.85).
2 satellite groups are defined: INJSAT1, INJSAT2.
Water injection rate for INJSAT1 - 20sm3 /day. Water injection rate for INJSAT2 - 10
sm3 /day, gas injection rate - 250 sm3 /day.
12.18.84. GSATINJE 1379

12.18.85 GRUPTREE


Section
The keyword sets tree structure for multi-level group control. The tree can consist of an
arbitrary number of levels. The field FIELD occupies the top of this tree.
Groups that have other groups as children cannot have wells. (Wells are assigned to
groups in the keyword WELSPECS (see 12.18.3)). Thus a group either contains wells (that
is a well-group) or has other groups as children (that is a node-group). Groups without a
parent group will have a parent group FIELD.
An arbitrary number of data rows can be specified (each row should be ended with a
slash /). Each row contains the following data:
1. name of child group;
2. name of parent group (this group is the parent group for the child group in item1).
All data should be terminated with a slash /.
Example
GRUPTREE
'GAS1' 'FIELD'/
'GAS2' 'FIELD'/
'G1' 'GAS1'/
'G2' 'GAS1'/
'G3' 'GAS2'/
'G4' 'GAS2'/
In this example the FIELD (level 0) contains 2 child groups GAS1, GAS2 (level 1). GAS1
contains child group G1 and G2 (level 2), GAS2 - child groups G3 and G4 (level 2).
12.18.85. GRUPTREE 1380

12.18.86 DGRDT


Section
This keyword specified maximum rate of change of guide rate for wells under group
control (it the default guide rate option is used potentials are used instead of used defined
values or GUIDERAT (see 12.18.73)).
The keyword limits the current timesteps guide rate inside the bounds defined by the previ-
ous timesteps guide rate. The data should be terminated with a slash /.
1. limiting fractional rate of change of guide rate (METRIC: 1/days, FIELD: 1/days);
Calculation of a lower fractional bound on the guide rate: multiplication of the value
in this parameter by the current timestep and subtracting the result from 1.0.
Calculation of an upper fractional bound on the guide rate: multiplication of the value
in this parameter by the current timestep and adding the result to 1.0.
Calculation of the limiting bounds on the current timesteps guide rate: multiplication
of the above fractional bounds by the previous timesteps guide rate.
2. the smallest permitted lower fractional bound as calculated above;
3. the largest permitted upper fractional bound as calculated above.
Default:
limiting fractional rate of change of guide rate 100;
the smallest permitted lower fractional bound as calculated above 0.5;
the largest permitted upper fractional bound as calculated above 1.5.
Example
DGRDT
0.05 /
12.18.86. DGRDT 1381

12.18.87 BRANPROP


Section
The keyword specifies the extended network branches (extended network model is speci-
fied via the keyword NETWORK (see 12.1.84)). This network structure can be different from
the structure specified by GRUPTREE (see 12.18.85) (the bottom nodes in the tree should
be the same (i.e. well groups)). An extended network should be defined via BRANPROP and
NODEPROP (see 12.18.88).
An arbitrary number of data rows can be entered (ended with a slash /). One data row
consists of the following parameters:
1. name of the branchs downtree node (this node is nearer to the well);
2. name of the branchs uptree node (this node is nearer to the top of tree);
3. VFP table number VFPPROD (see 12.18.57) (for producers) and VFPINJ (see
12.18.56) (for injectors).
Several pipelines can have the same VFP table if they have similar pressure loss char-
acteristics. If there is no pressure loss in the network branch defined by parameters 1
and 2, a value 9999 should be entered.
Branches representing chokes (parameter 3 of the keyword NODEPROP (see
12.18.88)), should have a value 9999.
A value 0 closes the branch (removes it from the network). Nodes production (or
nodes injection) is not added to the network flows;
4. artificial Lift Quantity (ALQ) that is used in the pressure loss calculations for the
branch. This number is used as a look-up parameter for the VFP table (parameter 3)
(may be considered as the pump or compressor power). If the branch has an automatic
compressor (NETCOMPA (see 12.18.92)), this value should correspond to its off
position (usually 0).
Default:
artificial Lift Quantity (ALQ) that is used in the pressure loss calculations for the
branch 0.
12.18.87. BRANPROP 1382

Example
GRUPTREE
'GAS1' 'FIELD'/
'GAS2' 'FIELD'/
'G1' 'GAS1'/
'G2' 'GAS1'/
'G3' 'GAS2'/
'G4' 'GAS2'/
BRANPROP
'GASALL' 'FIELD' 2 /
'GAS1' 'GASALL' 2 /
'GAS2' 'GASALL' 2 /
'G1' 'GAS1' 9999 /
'G2' 'GAS1' 9999 /
'G3' 'GAS2' 9999 /
'G4' 'GAS2' 9999 /
/
NODEPROP
'FIELD' 20 /
'GASALL' 1* 'NO'/
'GAS1' 1* 'NO'/
'GAS2' 1* 'NO'/
'G1' 1* 'YES'/
'G2' 1* 'YES'/
'G3' 1* 'YES'/
'G4' 1* 'YES'/
/
GRUPTREE (see 12.18.85):

BRANPROP (see 12.18.87):
Table VFPPROD (see 12.18.57) number 2 corresponds to the branches GASALL FIELD,
GAS1 GASALL, GAS2 GASALL.
Branches G1 GAS1, G2 GAS1, G3 GAS2, G4 GAS2 represent chokes (flag YES is
specified by the keyword NODEPROP (see 12.18.88) for nodes G1, G2, G3, G4).
NODEPROP (see 12.18.88):

The terminal node FIELD has terminal pressure 20barsa.
12.18.87. BRANPROP 1383

12.18.88 NODEPROP


Section
The keyword defines the extended network node properties (extended network model
is specified via the keyword NETWORK (see 12.1.84)). The keyword BRANPROP (see
12.18.87) should previously describe branch properties. An extended network should be
defined via BRANPROP (see 12.18.87) and NODEPROP (see 12.18.88).
The top node of each network tree (the terminal node) should be a fixed pressure node.
Only the fixed pressure node, and other nodes with non-default properties need to be specified
here.
An arbitrary number of data rows can be entered (ended with a slash /).
One data row consists of the following parameters:
1. node name;
2. fixed pressure for the terminal node (METRIC: barsa, FIELD: psia) (if the node is
not a terminal node, this parameter should be defaulted, or set negative);
3. flag indicating whether the uptree branch from this node should act as an automatic
choke to impose a flow rate limit. (The uptree branch is the one towards the terminal
node; the outlet branch for a production network or the inlet branch for an injection
network.) An automatic choke controls the flow of a target group by adjusting the
pressure drop across the choke. The branch specified via BRANPROP (see 12.18.87)
should have a VFP table number 9999, so that its only pressure drop is that of the
choke. The terminal node cannot be selected for this purpose, because it has no uptree
branch and its pressure is fixed.
YES The nodes uptree branch acts as an automatic choke. NO A production tar-
get applied to the corresponding group is met by the standard methods of group control.
Manifold groups, and groups for automatic chokes, should have their rate targets set
directly with GCONPROD (see 12.18.72) or indirectly as a share of a higher level
groups rate target. In the latter case, that is, if they are subordinate to a higher level
group having a production rate target (or a limit that becomes a rate target if violated),
they should be given guide rates in keyword GCONPROD (see 12.18.72). Groups sub-
ordinate to an automatic chokes target group should not have guide rates. Production
12.18.88. NODEPROP 1384

wells subordinate to an automatic chokes target group are not subject to guide rate
group control.
4. flag indicating whether gas-lift gas from the corresponding groups subordinate wells
should be added to the produced gas entering the network at this source node: YES or
NO.
If the node isnt a source node in a production network this parameter should be
defaulted;
5. group name for which the automatic choke attempts to match rate target by adjusting the
pressure drop across it. For a production (injection) network node, the choke attempts
to match this groups production (injection) rate target (GCONPROD (see 12.18.72)
for production, GCONINJE (see 12.18.81) for injection).
The 3-rd parameter should be set YES to use this parameter.
Default:
flag indicating whether the uptree branch from this node should act as an automatic
choke to impose a flow rate limit NO;
flag indicating whether gas-lift gas from the corresponding groups subordinate wells
should be added to the produced gas entering the network at this source node: NO;
group name for which the automatic choke attempts to match rate target by adjusting
the pressure drop across it is the same as the parameter 1.
12.18.88. NODEPROP 1385

Example
GRUPTREE
'GAS1' 'FIELD'/
'GAS2' 'FIELD'/
'G1' 'GAS1'/
'G2' 'GAS1'/
'G3' 'GAS2'/
'G4' 'GAS2'/
BRANPROP
'GASALL' 'FIELD' 2 /
'GAS1' 'GASALL' 2 /
'GAS2' 'GASALL' 2 /
'G1' 'GAS1' 9999 /
'G2' 'GAS1' 9999 /
'G3' 'GAS2' 9999 /
'G4' 'GAS2' 9999 /
/
NODEPROP
'FIELD' 20 /
'GASALL' 1* 'NO'/
'GAS1' 1* 'NO'/
'GAS2' 1* 'NO'/
'G1' 1* 'YES'/
'G2' 1* 'YES'/
'G3' 1* 'YES'/
'G4' 1* 'YES'/
/
GRUPTREE (see 12.18.85):

BRANPROP (see 12.18.87):
Table VFPPROD (see 12.18.57) number 2 corresponds to the branches GASALL FIELD,
GAS1 GASALL, GAS2 GASALL.
Branches G1 GAS1, G2 GAS1, G3 GAS2, G4 GAS2 represent chokes (flag YES is
specified by the keyword NODEPROP (see 12.18.88) for nodes G1, G2, G3, G4).
NODEPROP (see 12.18.88):

The terminal node FIELD has terminal pressure 20barsa.
12.18.88. NODEPROP 1386

12.18.89 NCONSUMP


Section
This keyword is used to set a gas consumption rate at a specified node in the extended
network (see the keyword NETWORK (see 12.1.84)) and to assign the consumption also to a
group (see the keyword GRUPTREE (see 12.18.85)). (Section: NETWORK option. Automatic
chokes. Compressors. 2.19.10.)
1. node name;
2. gas consumption rate at the node (METRIC: sm3 /day, FIELD: Msc f /day);
3. name of the group from which the nodes consumption should also be removed.
/.The data should be terminated with a slash /.
Default:
gas consumption rate at the node: 0;
name of the group from which the nodes consumption should also be removed: no
group.
Example
NCONSUMP
T-ALP 20 T-ALP /
/
In the example for node T-ALP gas consumption rate is assigned. It is equal to 20
Msc f /day. The nodes consumption is removed from group T-ALP.
12.18.89. NCONSUMP 1387

12.18.90 GNETDP


Section
This keyword contains parameters for the dynamic changing of fixed pressures. The key-
word can be used to adjust the pressure of a fixed-pressure group or network node to maintain
the production flow rate within the specified limits.
(Network option NETWORK (see 12.1.84). Automatic chokes. Compressors. 2.19.10.)
Actions in case if the flow into the fixed-pressure group (or node) falls below the
minimum rate (parameter 3):
the pressure value is adjusted by subtracting a pressure increment (parameter 5), then the
network is rebalanced.
Adjustment process continues until one of two conditions is satisfied: the flow exceeds the
minimum value (parameter 3) or the pressure falls to the minimum (parameter 7).
Actions in case if the flow into the fixed-pressure group (or node) exceeds the
maximum rate (parameter 4):
the pressure value is adjusted by adding a pressure increment (parameter 6), then the network
is rebalanced.
Adjustment process continues until one of two conditions is satisfied: the flow falls below
the maximum value (parameter 4) or the pressure increases to the maximum (parameter 8).
Any number of data line can be specified. Each line should be terminated with a slash.
1. name of the fixed-pressure group (fixed-pressure node);
2. phase to which parameters 3 and 4 correspond: OIL, WAT, GAS, LIQ;
3. minimum rate (for group/node) that triggers a pressure adjustment (METRIC: sm3 /day,
FIELD: stb/day for oil, water, liquid, Msc f /day for gas);
4. maximum rate (for group/node) that triggers a pressure adjustment (METRIC:

sm3 /day, FIELD: stb/day for oil, water, liquid, Msc f /day for gas);
5. pressure increment that is subtracted from the fixed pressure when the flow rate falls
below the minimum (parameter 3) (METRIC: barsa, FIELD: psia);
12.18.90. GNETDP 1388

6. pressure increment that is added to the fixed pressure when the flow rate exceeds the
maximum (parameter 4) (METRIC: barsa, FIELD: psia);
7. minimum allowed pressure in the group (node) (METRIC: barsa, FIELD: psia);
8. maximum allowed pressure in the group (node) (METRIC: barsa, FIELD: psia).
Default:
phase to which parameters 3 and 4 correspond: GAS,
minimum rate (for group/node) that triggers a pressure adjustment 0 (no pressure
adjustment to increase the flow);
maximum rate (for group/node) that triggers a pressure adjustment 1e+20 (no pressure
adjustment to decrease the flow);
pressure increment that is subtracted from the fixed pressure when the flow rate falls
below the minimum (parameter 3) 0;
pressure increment that is added to the fixed pressure when the flow rate exceeds the
maximum (parameter 4) 0;
minimum allowed pressure in the group (node) 0;
maximum allowed pressure in the group (node) 1e+20.
Example
GCONPROD
GR1 GRAT 2* 26787212 1* RATE YES /
GR2 GRAT 2* 18582903 1* RATE YES /
/
GNETDP
GR1 GAS 26519340 27055084 0.5 0.5 43 300 /
GR2 GAS 18397074 18768732 0.5 0.5 43 300 /
/
12.18.90. GNETDP 1389

12.18.91 GNETINJE


Section
The keyword defines the injection network in extended network model (NETWORK (see
12.1.84)). The keyword BRANPROP (see 12.18.87) should previously describe branch prop-
erties. An extended production network should be defined via BRANPROP (see 12.18.87)
and NODEPROP (see 12.18.88).
1. group name or group mane root;
2. phase of the injection network: WAT water or GAS;
3. fixed pressure for the group if it is the terminal node (METRIC: barsa, FIELD: psia)
(if the node is not a terminal node, this parameter should be defaulted, or set negative);
4. injection VFP table number VFPINJ (see 12.18.56) for the pipeline between the group
and its parent group.
Several pipelines can have the same VFP table if they have similar pressure loss
characteristics.
If there is no pressure loss in the network branch between this group and its parent
group, then a value 9999 should be entered.
If a group is a node with fixed pressure (parameter 3 of the keyword NODEPROP (see
12.18.88)), then this parameter should be defaulted (a group with fixed pressure is a
terminal node and it cant be connected with a parent group.)
Default:
injection VFP table number VFPINJ (see 12.18.56) for the pipeline between the group
and its parent group 0.
12.18.91. GNETINJE 1390

Example
GNETINJE
GAS1 GAS 10 /
G1 GAS 1* 9999 /
G2 GAS 1* 3 /
GAS2 GAS 30 /
G3 GAS 1* 9999 /
G4 GAS 1* 3 /
/
12.18.91. GNETINJE 1391

12.18.92 NETCOMPA


Section
The keyword defines automatic compressors or pumps in the extended production net-
work (extended network model is specified via the keyword NETWORK (see 12.1.84)). An
extended network should be defined via BRANPROP (see 12.18.87) and NODEPROP (see
12.18.88).
Compressor (pump) occupies a branch of the network, and its operation is modeled by
changing the VFP table number or ALQ value of the branch.
1. inlet node name of the branch where the compressor is;
2. outlet node name of the branch where the compressor is;
3. name of group whose production rate this compressor will respond to; The compressor
will be activated if this group fails to meet its target production rate set for the phase
in parameter 4. If the group does not have a target set, but has a guide rate defined in
GCONPROD (see 12.18.72) and is under FLD control from a higher level group, then
the compressor is activated when the group cannot make its share of the higher level
groups production target.
4. phase whose production rate this compressor responds to.
OIL, GAS.
5. VFP table number for the branch when the compressor is on. When the compressor
is switched on this replaces the table number previously specified in BRANPROP (see
12.18.87), which is applied whenever the compressor is off. 0 original VFP table
number will be unchanged.
6. ALQ Artificial Lift Quantity to be applied when the compressor is fully on. When
the compressor is fully on this replaces the ALQ value previously specified in key-
word BRANPROP (see 12.18.87), which is applied whenever the compressor is off.
Multi-level compressors operating at an intermediate level has an intermediate value
of the ALQ (parameters 9, 10 and 11). The artificial lift quantity may be regarded as
the compressor or pump power, according to the definition used when the table was
calculated (for example with VFP).
12.18.92. NETCOMPA 1392

7. rate of gas consumption by the compressor when fully on. This is an Eclipse compati-
bility field. IGNORED.
8. name of the group from which the compressors gas consumption should also be
extracted. This is an Eclipse compatibility field. IGNORED.
9. compressor type
PERM compressor remains on permanently after being turned on.

TEMP compressor can be turned off manually (for example if the target pro-
duction rate is reduced). It turns on automatically again as soon as it is needed.
In gas field operation model the compressor turns off automatically whenever the
contract groups target rate decreases. It turns on automatically again as soon as
it is needed.
MULT Similar to TEMP, but with multiple compression levels. Compression is
increased one level at a time until the groups target rate is satisfied.
10. number of compression levels in a multi-level compressor.

This parameter should be specified only if parameter 9 is MULT.
If there are levels the ALQ and consumption rate at level are:
i1
ALQi = ALQ1 + (ALQN ALQ1 ( ))
N 1
i
CONSi = CONSN
N
where ALQ1 is specified in parameter 11. VFP table number is specified in parameter
5, when the compressor is working at the first level and above.
11. artificial lift quantity at level 1 of multi-level compressor, ALQ1 .

This parameter should be specified only if parameter 9 is MULT.
12. compressor switching sequence number. This parameter specifies the order in which
compressors is turned on if there are two or more compressors corresponding to the
same group (parameter 3). If the group cannot satisfy its rate target, the compressor
with the lowest sequence number that corresponds to the group is turned on. If the
group still cannot satisfy its target when this is fully on, but has other compressors
that correspond to it, these other compressors are turned on in increasing order of their
sequence number. If two compressors in the network have the same sequence number,
they are both turned on at the same time (it is so also if they respond to different
groups). In this case it is possible to turn on all compressors simultaneously if the
compression is needed anywhere in the field. All multi-level compressors with the
same sequence number have their levels increasing simultaneously.

Default:
12.18.92. NETCOMPA 1393

name of group whose production rate this compressor will respond to compressor is
turned off;
phase whose production rate this compressor responds to GAS;
VFP table number for the branch when the compressor is on 0.
Example
NETCOMPA
'GASALL' 'FIELD' ' FIELD' ' GAS' 2 100 2* 'MULT' 200 1 /
/
In this example compressor is in the branch GASALL FIELD, corresponds to the

production rate of the group FIELD, phase gas. VFP table number for this branch 2.
Compressor type MULT. Number of compression levels 1.
12.18.92. NETCOMPA 1394

12.18.93 COMPOFF


Section
This keyword switches off automatic compressors defined by NETCOMPA (see 12.18.92),
except for compressors that define to stay on permanently (9-th parameter PERM in the key-
word NETCOMPA (see 12.18.92)). If necessary all compressors will turn on automatically.
This keyword doesnt switch off compressors specified by GNETPUMP (see 12.18.95).
12.18.93. COMPOFF 1395

12.18.94 NWATREM


Section
The keyword removes water from a node in the extended network (extended network
NETWORK (see 12.1.84)). An extended network should be defined via BRANPROP (see
12.18.87) and NODEPROP (see 12.18.88). (Section: NETWORK (see 12.1.84) option. Au-
tomatic chokes. Compressors. 2.19.10.)
The removal of water influences the pressure loss in the lower lying branches because of
their VFP tables are considered with a smaller water fraction. There is no keyword influence
to the reported group production rates or the operation of any group water rate limits, group
economic limits.
1. node name;
2. maximum rate of water removal from the node (METRIC: sm3 /day, FIELD: stb/day)
(the specified water rate will be corresponding to a maximum fraction of the nodes
water flow specified via parameter 3);
3. maximum fraction of the nodes water flow to be removed (the specified fraction of
the nodes water flow will be removed, corresponding to a maximum rate specified via
parameter 2).

Default:
maximum rate of water removal from the node e20 ;
maximum fraction of the nodes water flow to be removed 1.
Example
NWATREM
W1NODE1 1* 0.6 /
W1NODE2 1* 0.2 /
W1NODE3 1* 0.3 /
/
12.18.94. NWATREM 1396

60% of water that flows through the node W1NODE1 will be removed. 20% of water
that flows through the node W1NODE2 will be removed. 30% of water that flows through
the node W1NODE3 will be removed.
12.18.94. NWATREM 1397

12.18.95 GNETPUMP


Section
This keyword defines automatic pump (compressor) switching in a standard network

2.19.9.
An arbitrary number of data rows can be entered (ended with a slash /). All data should
1. group name or group name root;
2. production rate below which the pump (compressor) will be switched on (METRIC:
sm3 /day, FIELD: stb/day for oil, Msc f /day for gas);
3. phase to which production rate (specified in parameter 2) corresponds: OIL oil, GAS
gas;
4. new VFP table number. When the compressor is switched on this replaces the table
number previously specified in GRUPNET (see 12.18.96). 0 or negative number
original VFP table number will be unchanged.
5. new ALQ (Artificial Lift Quantity). IGNORED. This is an Eclipse compatibility field.
Default:
production rate below which the pump (compressor) will be switched on 0 (METRIC:
sm3 /day, FIELD: stb/day);
phase to which production rate (specified in parameter 2) corresponds: OIL oil;
new VFP table number 0.
Example
GNETPUMP
GROUP1 3000000 GAS 2/
/
In this example pumps for group GROUP1 are switched on when group gas rate falls
below 3000000 sm3 /day.
12.18.95. GNETPUMP 1398

12.18.96 GRUPNET


Section
The keyword defines standard production network structure 2.19.9.
An arbitrary number of data rows can be entered (ended with a slash /). All data should

2. fixed pressure for the group corresponding to the terminal node barsa (if the group is
not a terminal node, this parameter should be defaulted, or set negative);
3. VFP table number for the pipeline from the group to its parent group.
Several pipelines can have the same VFP table if they have similar pressure loss
characteristics. If there is no pressure loss in the network branch between the group
and its parent group, a value 9999 should be entered.
If this group is a node with fixed pressure (positive value in parameter 2), then this
parameter 3 should be defaulted (i.e. the group with fixed pressure terminal node and
it cant have a pipe connection with a higher group).
A value 0 the group doesnt have a pipeline to its parent group..
4. artificial lift quantity (ALQ) value, that is used in the pressure loss calculations for the
groups pipeline;
5. flag indicating whether a group production target is achieved by adjusting its wells
THP limits instead of the standard method of flowing the wells in proportion to their
guide rates.
YES group production target is achieved by adjusting its wells THP limits, so that
all wells can work at the same THP values. NO A production target is achieved by
the standard methods of group control; the wells can work with different THP values.
6. flag indicating whether gas-lift gas from the subordinate wells flows through this
groups pipeline:
NO no; only formation gas flows along the pipeline;
FLO yes; add the lift gas flows of the subordinate producers to the gas flow
rate along the pipeline. The lift gas flow is assumed to be equal to the sum of the
ALQ values of the subordinate producers, multiplied by their efficiency factors.
12.18.96. GRUPNET 1399

ALQ set ALQ value for this pipeline to be equal to the sum of the ALQ values
of the subordinate producers, multiplied by their efficiency factors. If this flag is
set, then parameter 4 is ignored.
If FLO is entered for a well group, then the lift gas flows of its wells are included in
the network source term and are included in the network flows up to the terminal node
independently of the parameter 6 setting for superior groups.
Default:
VFP table number for the pipeline from the group to its parent group 0;
artificial lift quantity (ALQ) value, that is used in the pressure loss calculations for the
groups pipeline 0;
flag indicating whether a group production target is achieved by adjusting its wells
THP limits instead of the standard method of flowing the wells in proportion to their
guide rates NO.
Example
GRUPNET
FIELD 20
GROUP1 1* 3/
GROUP2 1* 4/
/
Group FIELD is specified as a node with fixed pressure.
12.18.96. GRUPNET 1400

12.18.97 DRSDT


Section
The keyword sets maximum rate of increase of solution gas-oil ratio. The data should be
1. maximum rate at which the solution gas-oil ratio (RG,O ) in any grid block is allowed
to increase (METRIC: sm3 /sm3 /day, FIELD Msc f /stb/day);
2. flag: ALL parameter 1 is applied to all grid blocks, FREE parameter 1 is applied
only to grid blocks that contain free gas.
Default: flag: ALL.

The keyword defines how free gas and undersaturated oil interact in a grid block. If
maximum rate 0, RG,O cannot rise and free gas does not dissolve in undersaturated oil. If
maximum rate is large, RG,O rises until the oil is saturated or no free gas remains (this way
is if this keyword isnt specified).
If the keyword is not used, the resolution rate limit is infinity.
Example
DRSDT
0.000001365/
12.18.97. DRSDT 1401

12.18.98 DRSDTVP


Section
This keyword sets maximum rate of increase of solution gas-oil ratio as a function of
pressure (can be used only in black-oil models).
This keyword is an extension of the keyword DRSDT (see 12.18.97).

The description and formulas are in the section 2.16.
The table should be specified. The data should be terminated with a slash /.
1. dimensionless pressure (p in the section 2.16);
2. maximum rate at which the solution gas-oil ratio (RG,O ) in any grid block is allowed
to increase (METRIC: sm3 /sm3 /day, FIELD Msc f /stb/day);
Default: flag: ALL.
Example
DRSDTVP
1 0.0 ALL
2 0.5 ALL
/
12.18.98. DRSDTVP 1402

12.18.99 DRSDTVPE


Section
This keyword allows to use an alternative model of gas dissolution that takes into account
the exponential nature of the system relaxation (can be used only in black-oil models).
This keyword is an extension of the keyword DRSDT (see 12.18.97).

The description and formulas are in the section 2.16.
The table should be specified. The data should be terminated with a slash /.
1. dimensionless pressure (p in the section 2.16);
2. relaxation parameter of nonequilibrium Rs to equilibrium;
Default: flag: ALL.
Example
DRSDTVPE
1 0.01 ALL
/
12.18.99. DRSDTVPE 1403

12.18.100 DRVDT


Section
The keyword sets maximum rate of increase of vapor oil-gas ratio (METRIC:
sm3 /sm3 /day, FIELD Msc f /stb/day). One real number should be specified. The data should
Default: if this keyword isnt specified the re-vaporization rate is unrestricted.
The keyword defines how free oil and undersaturated gas interact in a grid block. If
maximum rate 0, RO,G cannot rise and free oil does not vaporize in undersaturated gas. If
maximum rate is large, RO,G rises until the gas is saturated or no free oil remains (the case
of total re-vaporization).
Example
DRVDT 0.0065/
12.18.100. DRVDT 1404

12.18.101 COMPENSATION


Section
This keyword defines compensation factor and type for group of wells. The following
parameters are to be specified:
1. group name,
2. compensation fraction (between 0 and 1),
3. compensation type.
The only supported in current version compensation type is INTEGRAL. For this type of
compensation the total injection rate of all injection wells in the group will be proportional
increased or decreased to reach the specified compensation fraction from the total production
rate of all production wells in the group. If computed bottom hole pressure for an injection
well exceeds limit on BHP, then this well is switched on control by BHP and compensation
does not reach the specified compensation fraction.
Default: none
Example
COMPENSATION
Group1 1.0 INTEGRAL /
Group2 0.9 INTEGRAL /
/
In this example for group Group1 compensation fraction is set to 100% of liquid produced.
For group Group2 compensation fraction is set to 90%.
12.18.101. COMPENSATION 1405

12.18.102 GECON


Section
This keyword defines economic limit for group or several groups with the same group
name root. The following parameters should be specified:
control),
2. lower economic limit of oil rate (METRIC: sm3 /day, FIELD: stb/day), if violated,
all wells in the group will be SHUT or STOP according to the 9-th parameter of the
3. lower economic limit of gas rate (METRIC: sm3 /day, FIELD: Msc f /day), if violated,
all wells in the group will be SHUT or STOP according to the 9-th parameter of the
4. upper economic limit of water cut (METRIC: sm3 /sm3 , FIELD: stb/stb),
5. upper economic limit of gas-oil ratio (METRIC: sm3 /sm3 , FIELD: Msc f /stb),
6. upper economic limit of water-gas ratio (METRIC: sm3 /sm3 , FIELD: stb/Msc f ),
7. workover action in case of water cut violation:
NONE do nothing
CON+ shut in worst offending perforation and all below,
WELL shut in the worst offending well
8. end calculations flag:
YES model calculations stops at the next report time if all the producers in
the group are shut or stopped (if the group had at least one previously opened
producer);
NO calculation is running.
12.18.102. GECON 1406

9. maximum allowed number of open wells subordinate to this group. This parameter
doesnt allow wells to be opened automatically (option AUTO in WCONPROD (see
12.18.34), WCONINJE (see 12.18.36), WELOPEN (see 12.18.107)) or from the drilling
queue QDRILL (see 12.18.203), if their number will violate this limit. But the wells
can be opened manually (OPEN in WCONPROD (see 12.18.34), WCONINJE (see
12.18.36)).
Default:
lower oil rate economic limit 0,
lower gas rate economic limit 0,
upper water cut economic limit no limit,
upper gas-oil ratio economic limit no limit,
upper water-gas ratio economic limit no limit,
workover action: NONE,
end calculations flag: NO,
maximum allowed number of open wells subordinate to this group 0 (no limit).
Example
GECON
LEFT_SIDE 30 1* 0.95 2* CON /
PROD* 30 4* WELL /
/
This example sets limits for several groups. For group LEFT_SIDE minimum possible oil
rate is equal to 30, and maximum possible water cut is 95%. If group oil rate falls below
30, all wells in the group will be shut in; if group water cut exceeds 95%, the maximum
offending perforation in maximum water cut well will be closed.
For groups with name starting with PROD minimum possible oil rate is also equal to 30,
and there is no water cut limit. If calculated oil rate is lower than 30, all wells in the group
will be shut in.
12.18.102. GECON 1407

12.18.103 GRUPLIM


Section
This keyword is the full analogue of the keyword GECON (see 12.18.102).
12.18.103. GRUPLIM 1408

12.18.104 WELDRAW


Section
The keyword sets maximum drawdown allowed for production wells (single well or group
of wells). The data for each well (group) should be terminated with a slash /. At the end of
the data one should put an extra slash /. The following parameters are to be specified for
each well (group of wells):
1. well name or group name (or group name root, i.e. name ending with asterisk),
or FIELD (to set maximum drawdown allowed for field) or well list (WLIST (see
12.18.26));
2. maximum drawdown allowed for production well (group of wells) (METRIC: bars,
FIELD: psi);
3. phase; production rate limit for this phase will be calculated at every time step us-
ing the maximum drawdown allowed for this well (group) and phases mobility in
corresponding connections:
LIQ if well produces oil;

GAS if well produces gas.
This formula converts maximum drawdown allowed for the well (group) into maximum
production rate for the phase:
QMax = DMax (Tci Mi ) (12.5)

i
QMax maximum production rate for the phase, DMax maximum drawdown allowed
for the well, Tc connection transmissibility factor, M phases mobility in this
connection, i the sum is over all open connection at current time step.
4. maximum drawdown allowed for the well availability for wells production potential:
YES means that the wells production potential depends on limits: BHP, THP
and drawdown,
NO means that the wells production potential depends on limits: BHP and THP.
5. Do you want to limit the PI-weighted average of the drawdowns within the grid blocks
with connections, or the maximum drawdown with the set of connection grid blocks?
12.18.104. WELDRAW 1409

AVG Limit the PI-weighted average drawdown using formula: The formula 12.5
calculates the drawdown as
D = pavg pwell
where:
pwell wells bottom hole pressure;
pavg PI-weighted (productivity index) average of the pressures p in the grid
blocks with wells open connections calculated as:
(Tci Mi (pi Hwi ))

i
pavg =
(Tci Mci )
i
where:
Hwi - hydrostatic wellbore pressure head between the connection i and the wells
bottom hole pressure reference depth.
MAX Limit the maximum drawdown.
In this case minimal allowed bottom hole pressure is calculated via the formula:
pw,Min = Maxi (pi Hwi DMax )
Maximal production rate (using the current fluid mobilities):
QMax = (Tci Mi ) (pi Hwi pw,Min )

i
Default:
phase (the third parameter of this keyword) LIQ,
the 4th parameter NO: the wells production depends on limits: BHP, THP.
Do you want to limit the PI-weighted average of the drawdowns within the grid blocks
with connections, or the maximum drawdown with the set of connection grid blocks?
AVG.
If maximum production rate is calculated from maximum drawdown allowed for the well,
the well will be on gas or liquid control (phase is set by 3rd parameter of this keyword).
Phase rate limit QMax . If the rate limit of this phase is set manually (with the help of
keywords WCONPROD (see 12.18.34) or WELTARG (see 12.18.51)), tNavigator will take
the minimum of these two values.
Example
WELDRAW
LEFT_SIDE 4 LIQ NO /
WELL136 3 GAS YES /
/
12.18.104. WELDRAW 1410

This example sets maximum drawdown allowed for the group of wells LEFT_SIDE to 4
bar, phase LIQ (production rate limit for this phase will be calculated at every time step
using the maximum drawdown allowed for this group and phases mobility in correspond-
ing connections), wells production potential doesnt depend on drawdown limit. Maximum
drawdown allowed for the well WELL136 is set to 3 bar, phase GAS, wells production
potential depends on drawdown limit.
12.18.104. WELDRAW 1411

12.18.105 DATES


Section
This keyword defines sequential dates for input and output data. Dates must be written in
ascending order.
On the next strings date is written in format: DD MONTH YYYY, each date must end with
a slash /. The date should be entered in the following format (The data should be terminated
with a slash /.):
1. day;
2. month. Here month can take the following values: JAN, FEB, MAR, APR, MAY, JUN,
JUL, AUG, SEP, OCT, NOV, DEC, or JLY, which is acceptable alternative to JUL;
3. year (4 digits);
4. time in the format hours-minutes-seconds-milliseconds HH:MM:SS.SSSS
Default: time 00:00:00.
Example
DATES
01 MAR 2000 15:00:00/
/
In this example the following date is specified the 1-st march of 2000, 15 hours.
12.18.105. DATES 1412

Example
DATES
01 JUL 2011
/
...
DATES
01 JAN 2012
/
...
DATES
01 JUL 2012 /
...
DATES
01 JAN 2013 /
...
DATES
01 JUL 2013 /
...
DATES
01 JAN 2014 /
...
DATES
01 JUL 2014 /
...
DATES
01 JAN 2015 /
...
DATES
01 JUL 2015 /
...
/
This example sets dates for input and output: every half a year between 01 JUL 1984 and
01 JUL 1986.
12.18.105. DATES 1413

Example
DATES
01 FEB 1985
/
...
DATES
01 MAR 1985
/
WELSPECS
1043 G1 14 10 /
1054 1* 15 8 /
/
COMPDAT
1043 14 10 1 1 OPEN 2* 0.16 3* Z /
1054 15 8 1 1 OPEN 2* 0.16 3* Z /
/
WCONPROD
1043 OPEN LRAT 63.4 0 0 63.4 2* /
1054 OPEN LRAT 59.6 6.4 0 66 2* /
/
DATES
01 MAY 1985
/
WCONPROD
1043 OPEN LRAT 80 0 0 90 2* /
1054 OPEN LRAT 67 9 0 76 2* /
/
DATES
01 JAN 1986
/
DATES
01 JAN 1987
/
In this example during development stage two new wells are added (on the 1st of March
in 1985) and all appropriate controls are set; in two months (May 1st, 1985) these controls
change.
12.18.105. DATES 1414

12.18.106 TSTEP


Section
This keyword explicitly defines sequential time step sizes for input and output data (in
days). The amount of time steps should not exceed 1000 (the rest will be ignored).
Time step sizes should be separated by spaces, it is possible to use short form with as-
terisks and braces. If DATE keyword is used after TSTEP keyword, the user should provide
that the date of new time step start is later then the date of the last time step.
Default: none
Example
TSTEP
31 30
2*31 2*30
/
This example sets the following simulation time steps: 31 day, 30 days, 31 day, 31 day,
30 days, 30 days.
Example
DATES
01 MAR 1990
/
...
TSTEP
31
/
...
DATES
01 MAY 1990
/
...
TSTEP
31
/
...
This example sets the following date sequence: 1st of March, 1990; 1st of April, 1990;
1st of May, 1990, 1st of June, 1990.
12.18.106. TSTEP 1415

12.18.107 WELOPEN


Section
The keyword shuts or reopens wells and well connections. The data for each well should
be terminated with a slash /. The data for all wells should be terminated with a final slash
/.
To shut or open a well one should specify first and second parameter of the keyword. To
change the current status of one connection enter its coordinates using 3-5 parameters. A
zero value of parameter 3-5 is considered as any number.
If you need to open (close) any completions COMPLUMP (see 12.18.22) their numbers
should be specified via parameters 6-7.
1. well name (well number) or well list WLIST (see 12.18.26),
2. status (OPEN, STOP, SHUT or AUTO well connection will open automatically when
the value of oil saturation runs up to WELSOMIN (see 12.18.2)),
3. X - coordinate of connection,
4. Y - coordinate of connection,
5. Z - coordinate of connection,
6. number of the first completion in the range (completions are specified via COMPLUMP
(see 12.18.22)),
7. number of the last completion in the range (completions are specified via COMPLUMP
(see 12.18.22)).
Note. For wells with perforations both in local and global grid, the keyword WELOPEN
(see 12.18.107) is able to close perforations in global grid only. If you need to close perfo-
rations in local grid, then use the keyword WELOPENL (see 12.18.108).
In this case (shut connections in global grid but connections in local grid stay open) the
following message will be displayed:
Connection [25, 59, 1] for well W closed by WELOPEN keyword. Use WELOPENL key-
word to shut connections in LGR blocks.
12.18.107. WELOPEN 1416

Example
WELOPEN
Well1 SHUT /
Well2 OPEN /
Well3 OPEN 0 0 5/
Well4 SHUT 0 0 0 8 12/
/
This example shuts Well1, opens Well2, opens all connections of Well3 in layer 5, shuts
all connections in completions 8, 9, 10, 11, 12 of Well4.
12.18.107. WELOPEN 1417

12.18.108 WELOPENL


Section
The keyword shuts or reopens wells and well connections in Local Grid Refinement (LGR
- 5.6). In case without LGR the keyword WELOPEN (see 12.18.107).
The data for each well should be terminated with a slash /. The data for all wells should
To shut or open a well one should specify first and second parameter of the keyword. To
change the current status of one connection enter its coordinates using 3-5 parameters. A
zero value of parameter 3-5 is considered as any number.
If you need to open (close) any completions COMPLMPL (see 12.18.23) their numbers
should be specified via parameters 7-8.
1. well name (well number) or well list WLIST (see 12.18.26),
2. local grid refinement name that contains the wells connection;
3. status (OPEN, STOP, SHUT or AUTO well connection will open automatically when
the value of oil saturation runs up to WELSOMIN (see 12.18.2)),
4. X - coordinate of connection,
5. Y - coordinate of connection,
6. Z - coordinate of connection,
7. number of the first completion in the range (completions are specified via COMPLMPL
(see 12.18.23)),
8. number of the last completion in the range (completions are specified via COMPLMPL
(see 12.18.23)).
Default: local grid refinement name that contains the wells connection is taken from
WELSPECL (see 12.18.4).
12.18.108. WELOPENL 1418

Example
WELOPENL
Well1 LGR1 SHUT /
Well2 LGR2 OPEN /
Well3 LGR2 OPEN 0 0 5/
Well4 LGR3 SHUT 0 0 0 8 12/
/
This example shuts Well1, opens Well2, opens all connections of Well3 in layer 5, shuts
all connections in completions 8, 9, 10, 11, 12 of Well4.
12.18.108. WELOPENL 1419

12.18.109 WELLOPEN


Section
The keyword opens wells which were shut automatically.
The data for each well should be terminated with a slash /. The data for all wells should
The analogue of this keyword is WELOPEN (see 12.18.107).
1. well name (well number) or well list WLIST (see 12.18.26).
Example
WELLOPEN
Well1 /
Well2 /
Well3 /
/
This example opens wells Well1, Well2, Well3.
12.18.109. WELLOPEN 1420

12.18.110 CVCRIT


Section
The keyword sets simulator Eclipse control parameters.

To set tNavigator iteration process parameters use the keyword RUNCTRL (see 12.18.119).
12.18.110. CVCRIT 1421

12.18.111 MATCORR


Section
This keyword enables a material balance correction option.

To do optimization of error of material balance use an option SMARTMB.
12.18.111. MATCORR 1422

12.18.112 NETBALAN


Section
This keyword sets the network (NETWORK (see 12.1.84)) calculation parameters. The
1. network balancing interval, IGNORED, this is an Eclipse compatibility field;
2. convergence tolerance for network nodal pressures (METRIC: bars, FIELD: psi);
3. maximum number of iterations in the network balancing calculation. If there is no

convergence, but this number is reached, then tNavigator will print a warning. In this
case this parameter can be increased (Note: tNavigator uses solution methods different
from Eclipse, thats why this number of iterations can be different).
4. convergence tolerance for calculating the pressure drop across automatic chokes con-
trolling a groups production rate. The specified value is the fraction of each groups
rate target that is a possible error.
Default:
convergence tolerance for network nodal pressures 0.1 bars;
maximum number of iterations in the network balancing calculation 20;
convergence tolerance for calculating the pressure drop across automatic chokes con-
trolling a groups production rate 0.01. There is a convergence of iterations when the
groups rate target is met within one percent.
Example
NETBALAN
1* 0.05 10.0 /
12.18.112. NETBALAN 1423

12.18.113 WSEGITER


Section
This keyword sets an iteration parameters for multi-segment wells. slashend
1. maximum number of well iterations per cycle of calculation.
Default:
maximum number of well iterations per cycle of calculation: 20 (for E100 and E300
format models).
Example
WSEGITER
25 /
12.18.113. WSEGITER 1424

12.18.114 TUNING / TUNINGDP / TUNINGL / TUNINGS


Section

12.18.114. TUNING / TUNINGDP / TUNINGL / TUNINGS 1425

12.18.115 TIGHTENP / TSCRIT


Section

12.18.115. TIGHTENP / TSCRIT 1426

12.18.116 ZIPPY2


Section

12.18.116. ZIPPY2 1427

12.18.117 NEXTSTEP / NSTACK


Section
The keyword sets simulator control parameters and time step parameters.
12.18.117. NEXTSTEP / NSTACK 1428

12.18.118 LGRLOCK / LGRFREE


Section
This keyword sets calculation parameters for LGRs in simulator Eclipse.

In tNavigator local grid is always calculated with global grid that corresponds to LGR-
LOCK method.
12.18.118. LGRLOCK / LGRFREE 1429

12.18.119 RUNCTRL
Data x tNavigator x E300 x MORE x GEM

format x E100 x IMEX x STARS

Section
The keyword is used to specify the iterative process parameters. If it is used in section
SCHEDULE it will be applied from the time step when it is specified. The following options
may be used (The data should be terminated with a slash /.):
1. AIM N.
If N = 0, fully implicit method is used.
It is used by default for black oil models;
If N = 1, AIM adaptive implicit method is used.
This method is used by default for compositional models.
If N = 2 etc. The number after AIM stands for the number of primary variables
that are calculated implicitly in AIM blocks. tNavigator chooses variables auto-
matically, only their number should be specified. N can have the values up to the
number of components in the system plus one. This last case corresponds to the
fully implicit method.
AIM can be switched on via the keyword AIM (see 12.1.93). AIM 1 is used if this
keyword is specified.
Settings of AIM can be changed in the keyword AIMCTRL (see 12.1.5).
AIM can be used together with WATERZONE option (speed-up calculations of models
having a water zone).
2. CHECKSAT N
If N = 0, no additional actions are performed;
If N =! 0 (not equal to 0; you can set any number), then other than default initial
approximation is used to get a first guess for the new time step, tNavigator
makes linear extrapolation of variable values from last two time steps.
This option can be used successfully for the models with stable calculation (uni-
form changes of pressure, rates), i.e. if there are no significant jumps of rates and
pressures between the calculation steps.
This option is used by default for 2-phase water-gas models.
3. CHOPSAT n
Possible values: 0 (default), 1
12.18.119. RUNCTRL 1430

This option reduces free gas variations. It can be used successfully for the 3-phase
models, when pressure drops fast and free gas is released in large quantity (for the
2-phase models this option is often ineffective).
If 0 is specified - nothing will be done; if 1 is specified, then additionally the following
controls will be done:
the difference of saturations for each phase (P) on two successive Newton itera-
tions is checked:
|SPi SPi+1 | 0.1
If for some phases this inequality is violated (the new saturation differs from the
previous one by more than 0.1), then the new saturation is taken closer to the
old one, i.e., if SPi+1 SPi = 0.2232, SPi+1 is taken equal to SPi+1 = SPi + 0.1, and
additional iteration is performed.
tNavigator checks that saturation does not pass through the point of immobility
(keeping physically valid saturation);
4. DNLIM n, maximal allowed molar volume relative variation. The positive number
should be specified fraction.
For example if the value 0.5 is specified this corresponds to 50% variation of this
parameter comparing to its value on the previous calculation step. Variation can be
greater than the specified value.
The length of the next calculation step depends on this parameter: if at the current
step molar volume variation exceeds this value then the length of the time step will be
reduced. For example, if the allowed variation is set to 10, and at the current calculation
step the molar volume variation exceeds 1000% (is 1200%), then the length of the time
step will be reduced 1200/1000 = 1.2 times (proportionally to the specified variation
value).
5. DPLIM n, maximal allowed pressure relative variation. The positive number should be
specified fraction.
The length of the next calculation step depends on this parameter: if at the current step
pressure variation exceeds this value then the length of the time step will be reduced.
For example, if the allowed variation is set to 10, and at the current calculation step
the pressure variation exceeds 1000% (is 1200%), then the length of the time step will
be reduced 1200/1000 = 1.2 times (proportionally to the specified variation value).
6. DPREDUCE n, if 0 this option is not used, 1 option is used. This option can be
used to speed up calculations of dual porosity (DUALPORO (see 12.1.76)) but not
dual permeability (DUALPERM (see 12.1.77)) models.
This option is used by default for dual porosity models;
12.18.119. RUNCTRL 1431

7. DSLIM n, maximal allowed phase saturation relative variation (maximum is taken over
all phases). The positive number should be specified fraction.
step molar phase saturation variation exceeds this value then the length of the time
step will be reduced. For example, if the allowed variation is set to 10, and at the
current calculation step the phase saturation variation exceeds 1000% (is 1200%), then
the length of the time step will be reduced 1200/1000 = 1.2 times (proportionally to
the specified variation value).
8. DTINITIAL n, length of first time step at model start;
9. DTLIM n, maximal allowed temperature relative variation. The positive number should
be specified fraction.
step temperature variation exceeds this value then the length of the time step will be
step the temperature variation exceeds 1000% (is 1200%), then the length of the time
value).
10. DTLOGIC n, the strategy of choice of the first calculation step length on the new time
step (reporting step). If the option is enabled (1 is set), the length of the first calculation
step on the new time step is taken equal to the length of last calculation step on the
previous time step.
If the option is not defined (0 is set), then the strategy of choice of the length of the
first calculation step in a new time step is used by default.
11. DTMAX n, maximal allowed time step;
12. DTMIN n, minimal allowed time step;
13. DVLIM n, maximal allowed pore volume relative variation. The positive number should
be specified fraction.
step pore volume variation exceeds this value then the length of the time step will be
step the pore volume variation exceeds 1000% (is 1200%), then the length of the time
12.18.119. RUNCTRL 1432

value).
14. INCVCE n, the main variable (the last hydrocarbon component) can be excluded. The
value 0 (the variable is excluded by default) is used for thermal models speed-up. The
value 1 should be specified to include the variable 1;
15. MATBALERRPROD n, maximal value of material balance error relative to current
production;
16. MATBALERRTOT n, maximal value of material balance error relative to total fluid
amount;
17. MAXELAPSED n, maximal time of one calculation step (minutes);
18. MAXLINIT n, maximal number of iterations in linear solver;
19. MAXNEWTIT n, maximal number of Newton iterations;
20. MAXWELLIT n, maximal number of iterations for one well;
21. MINNEWTIT n, minimal number of Newton iteration.
MINNEWTIT 1 is used by default for 2-phase water-gas models and MINNEWTIT 0
is used for other models.
Default: In all models if on some steps computational step is equal to report step, then
on next time step MINNEWTIT would be set to 1. To switch it off use MINNEWTIT 0;
22. NDTAVG n, the number of the last calculation steps that are used for selecting the new
calculation step length. If this option is not used, this parameter is equal to 1, i.e. a
new step length depends only on the length of the last calculation step. If we specify
a different number n, tNavigator will take as a basis the average length of the last n
calculation steps;
23. NTOLVARWELL n, this parameter is related to parameter TOLVARWELL - if a condition
for well rate variation is not satisfied additional iterations are made, but not more
than the number specified here;
24. OVERDRAFT n, the coefficient to choose new time step length. MAXNEWTIT divided
by the parameter OVERDRAFT, MAXLINIT divided by the parameter OVERDRAFT;
25. PAVWEIGHT n, In the case that the value of this parameter is even (or not specified) -
average field pressure is the hydrocarbon pore volume weighted average. Odd value -
average field pressure is the pore volume weighted average;
26. SMARTMB n, if the option is enabled (1 is set), then the test (experimental) solver will
be used. Significant optimization of error of material balance is possible (this option
can not be used with dual porosity and dual permeability models).
This option is experimental and is not part of the standard procedures recom-
mended to increase the accuracy of the numerical convergence process;
12.18.119. RUNCTRL 1433

27. TMAXMULT n, allowed maximal time step increasing factor per one time step (must
be > 1);
28. TOLLIN n, tolerance of linear solver (the appliance of this parameter see in the section
5.4);
29. TOLNEWT n, maximal allowed residual to finish Newton iterations (the appliance of
this parameter see in the section 5.4);
30. TOLVARAQ n, maximal allowed aquifer flow relative variation;
31. TOLVARNEWT n, maximal allowed main variables variation to finish Newton iterations
(the appliance of this parameter see in the section 5.4);
32. TOLVARWELL n, maximal allowed well rate variation between Newton iterations;
33. TOLWELL n, tolerance of linear solver for one well;
34. USEDIFFNORM n, if 0 norm of molar densities is calculated for all N together, i.e. for
vector (N11 , ..., N1n , N21 , ..., N2n , ..., Nn c1 , ..., Nn cn ) its norm is calculated, else norms
of vectors (N11 , ..., N1n ), (N21 , ..., N2n ), ..., (Nn c1 , ..., Nn cn ) are calculated independently
(n number of active blocks). So if 0 one number is calculated, if 1 nc numbers
are calculated and then their maximum is found;
35. WATERZONE n, option to speed-up calculations of models having a water zone

(water saturation in the grid block is equal to 1). This option is used by default for
compositional and thermal models.
1 option is used; 0 option is not used.
36. WDENIMP n, 0 use well average density from previous step, else density is calculated
implicitly;
37. WELLDENWEIGHT n, option that averages with a predefined weight densities inside
the well bore for the current and the previous calculation steps.
One should specify the number from 0 to 1.
The option can be effective for models with convergence problems because of oscilla-
tion in the wells caused by oscillating density of the mixture in the well bore.
Density at the current time step is calculated via the formula: DENSITY = (1
VALUE) DENSITYNEW +VALUE DENSITYOLD . where
VALUE value specified in this option; DENSITYOLD density value from the pre-
vious time step; DENSITYNEW the actual value of the density, which is obtained by
taking into account well rate and the crossflow;
38. WELLEQUATIONS n, if 0 this option is not used, 1 option is used. This option can
be used to do a fast distribution of well data between parallel processors to get better
performance for long/fractured wells.
This option change the method of adding equations for wells. The system of equations
12.18.119. RUNCTRL 1434

approximating the filtering problem consists of two parts, describing flow in the grid
blocks and the flow in the wells respectively.
By default (when the option WELLEQUATIONS is not used) the equations for wells
are inserted into the general system. The number of added non-zero elements of the
matrix is equal to the number of perforations in the square. I.e. the resulting system
is obtained by excepting for the unknowns for wells from the equations for the grid
blocks.
When the option WELLEQUATIONS is used general system is obtained by combining
equations for blocks and wells. Equations for wells are added as separate additional
equations. This adds as many non-zero elements of the matrix as many perforations we
have.
In the first case (the default) we have a matrix of smaller dimension, but with a more
complicated structure, and in the second case a matrix of larger dimension, but with
a simpler structure.
The first method can be better for models with dozens of thousands of wells with
less than one hundred perforations in each well. The second method can be better for
a small number of wells with thousands of perforations (defined via COMPDAT (see
12.18.6)).
39. WFRACFLOW n, 0 use flows between well and fracture connections in Jacobian, 1
in Jacobian all flows between fractures and well bore are used.
Default average field pressure (the hydrocarbon pore volume weighted average):
Porvhc pO
PRESSURE =
Porvhc
Porvhc = Porv(1 Sw ) hydrocarbon pore volume; Porv block pore volume; pO
oil phase pressure.
Average field pressure is the pore volume weighted average (odd value of this OP-
TIONS parameter):
Porv pO
PRESSURE =
Porv
The 31-th parameter of OPTIONS (see 12.18.217) is converted into this keyword.
Material balance error.

In tNavigator material balance error is calculated for the components (material balance equa-
tion is made for components, while in the classical formulation - for phases). The material
balance for each component (expressed in kilograms (for black-oil models) or in moles (in
the compositional case) is actually regulated by the option TOLNEWT). The residual of the
equation is equal to the difference of material balance of the left and right sides. The default
12.18.119. RUNCTRL 1435

value of this residual is 1.e-3 (kg). Which corresponds to 1.e-6 (m 3 at reservoir conditions)
for the liquid phases.
Default:
AIM 0 AIM is not used by default for black-oil and thermal models and AIM 1
AIM is used by default for compositional models;
CHECKSAT 1 option is used by default for 2-phase water-gas models and CHECKSAT
0 option is not used for other models;
CHOPSAT 0;
DNLIM 1;
DPLIM 1;
DPREDUCE 1 speed up calculations of dual porosity models; DPREDUCE 0 option

is not used for other types of models;
DSLIM 0.0025;
DTINITIAL 0.1;
DTLIM 1;
DTLOGIC 0;
DTMAX 100;
DTMIN. For compositional and black-oil models: 0.001; for thermal models: 1.e-6;
DVLIM 0.2;
INCVCE 0 the main variable (the last hydrocarbon component) is excluded.
MATBALERRPROD 1.1e+8;
MATBALERRTOT 1.1;
MAXELAPSED -1 no time limit for time step calculation;
MAXLINIT 200;
MAXNEWTIT 100 (if the option CHECKSAT is on this limit is set to 10);
MAXWELLIT 8;
MINNEWTIT 1 is used by default for 2-phase water-gas models and MINNEWTIT 0

is used for other models;
12.18.119. RUNCTRL 1436

NDTAVG 1;
NTOLVARWELL 4;
OVERDRAFT 2;
PAVWEIGHT 0 average field pressure is the hydrocarbon pore volume weighted

average;
SMARTMB 0;
TMAXMULT 4;
TOLLIN 1.e-3;
TOLNEWT 1.e-3;
TOLVARAQ 0.3;
TOLVARNEWT 1.e-3;
TOLVARWELL 1.e+20;
TOLWELL 1.e-3;
USEDIFFNORM 0;
WATERZONE 1 option is used for compositional ant thermal models and WATER-
ZONE 0 option is not used for black-oil models;
WDENIMP 0;
WELLDENWEIGHT 0
WELLEQUATIONS 0;
WFRACFLOW 1.
12.18.119. RUNCTRL 1437

Example
...
DATES
01 JUN 2000
/
RUNCTRL
MAXLINIT 100
MAXNEWTIT 5
TOLLIN 0.00001
TOLNEWT 0.001
/
...
DATES
01 AUG 2000
/
RUNCTRL
DTMAX 10.0
DTMIN 0.0002
/
...
DATES
01 JAN 2001
/
RUNCTRL
DTMAX 1.0
DTMIN 0.00002
TOLLIN 0.00001
/
...
DATES
01 JAN 2003
/
RUNCTRL
MAXELAPSED 2.5
/
...
In this example first we set values of 4 parameters maximum numbers of linear solver
and Newton iterations, and target precision for linear solver and for Newton process. On the
first of August 2000 new settings are added for some reason, for example, due to massive
well switches, we reduce maximum time step down to 10 (the default is 100) and also reduce
minimum time step down to 0.0002. From the first of January 2001 the minimum time step
will reduce even more, as well as maximum admissible time step.
From the first of January 2003 the maximal time of one calculation step will be 2,5 minutes.
12.18.119. RUNCTRL 1438

12.18.120 MULTSIG


Section
This keyword can be used in dual porosity run 2.28 (DUALPORO (see 12.1.76)) if sigma-
factor is set using the keywords SIGMA (see 12.2.67), SIGMAV (see 12.2.68). Sigma-factor
is multiplied by the multiplier MULTSIG.
One value for all blocks should be entered. The data should be terminated with a slash
/. Different multipliers for grid blocks can be entered using the keyword MULTSIGV (see
12.18.121).
Example
MULTSIG 0.3 /
12.18.120. MULTSIG 1439

12.18.121 MULTSIGV


Section
This keyword can be used in dual porosity run 2.28 (DUALPORO (see 12.1.76)) if sigma-
factor is set using the keywords SIGMA (see 12.2.67), SIGMAV (see 12.2.68). Sigma-factor
is multiplied by the multiplier MULTSIGV.
One should enter NX * NY * (NZ/2) values (matrix blocks). The data should be termi-
nated with a slash /. The common multiplier for all grid blocks can be entered using the
keyword MULTSIG (see 12.18.120).
Example
MULTSIGV 20*0.44 30*0.21/
This example sets the multiplier for 50 blocks: for 20 blocks 0.44, for 30 blocks -
0.21.
12.18.121. MULTSIGV 1440

12.18.122 WFRAC


Section
The keyword specifies the hydraulic fracture. An arbitrary number of data lines, termi-
nated with a slash /, can be specified (one line for one well). All data should be terminated


(see 12.18.125)). WFRAC (see 12.18.122) and COMPFRAC (see 12.18.126) are its reductions.
The differences between COMPFRAC (see 12.18.126) and WFRAC (see 12.18.122):
The following parameters should be specified in one line of WFRAC (see 12.18.122):
1. well name;
2. first connection (or trajectory) coordinate in X direction;
3. first connection (or trajectory) coordinate in Y direction;
4. first connection (or trajectory) coordinate in Z direction;
5. last connection (or trajectory) coordinate in X direction;
6. last connection (or trajectory) coordinate in Y direction;
12.18.122. WFRAC 1441

7. last connection (or trajectory) coordinate in Z direction;

8. azimuth angle (from 0 to 360 );
9. zenith angle (from 0 to 90 );
10. half of fracture length (METRIC: m, FIELD: f t );
11. fracture width (METRIC: m, FIELD: f t );
12. proppant name (the name should be input via the keyword PROPANTNAMES
(see 12.8.2));
13. dependence between fracture permeability and flown phase volume or time. One of the
flow function name (the dependence between fracture permeability and phase
flow). Phase is specified via the next parameter of this keyword. The function
specifies the washing out of the proppant from the fracture. (keywords FLOW-
FUNC (see 12.8.4), FLOWFTAB (see 12.8.7), FLOWFNAMES (see 12.8.6));
phase volume (m3 ) (the next parameters specifies a phase), when this volume
passes through fracture permeability becomes zero;
number of days (is case if the next parameter is TIME). Dependence of perme-
ability versus time is set via the the following formula:
DT
F(T ) = e days
where:
D current date;
T fraction creation date (difference of D and T measured in days);
days value of days which set there.
14. phase (flow function in previous parameter depends on this phase flow) or time depen-
dence (OIL oil, WAT water, GAS gas, LIQ liquid, TIME - time).
Default:
proppant name not defined; infinite permeability along the fracture (pipe);
dependence between fracture permeability and flown phase volume or time not de-
fined; there is no dependence from flow.
Example
WFRAC
'WELL123' 38 426 13 38 426 21 30 0.5 250 5 'propant 16/20'
'func 5' 'LIQ'
12.18.122. WFRAC 1442

In this example hydraulic fracture if specified the following way: well WELL123, first
connection [38, 426, 13], last connection [38, 426, 21], azimuth angle 30 , zenith angle
0.5 , half of fracture length 250, fracture width 5, propant 16/20, flow function
func 5, dependence of liquid flow LIQ.
Example
WFRAC
'PROD5' 39 14 2 39 14 11 110 0 140 0.02 'PROPPANT0' ' FLOWFUNC0'
'TIME' /
'PROD6' 39 32 1 39 32 11 110 0 140 0.02 'PROPPANT1' ' FLOWFUNC1'
'TIME' /
/
In this example there is hydraulic fracture for two wells with propants and flow functions.
12.18.122. WFRAC 1443

12.18.123 WFRACL


Section
The keyword specifies the hydraulic fracture for the wells in local grids (section 5.6). An
arbitrary number of data lines, terminated with a slash /, can be specified (one line for one
well). All data should be terminated with a final slash /.

WFRACL must be used in place of WFRAC (see 12.18.122) to specify the hydraulic
fracture for wells in local refined grids, after the wells have been introduced with keywords
WELSPECL (see 12.18.4), COMPDATL (see 12.18.7). The keyword data for WFRACL is
the same as for WFRAC (see 12.18.122), except for an extra parameter 2 which names the
local grid containing the connections specified in the record.

(see 12.18.125)).
The following parameters should be specified in one line of WFRACL (see 12.18.123):
1. well name;
12.18.123. WFRACL 1444

3. first connection (or trajectory) coordinate in X direction;
4. first connection (or trajectory) coordinate in Y direction;
5. first connection (or trajectory) coordinate in Z direction;
6. last connection (or trajectory) coordinate in X direction;
7. last connection (or trajectory) coordinate in Y direction;
8. last connection (or trajectory) coordinate in Z direction;
11. half of fracture length (METRIC: m, FIELD: f t );
(see 12.8.2));
DT
F(T ) = e days
where:
D current date;
dence (OIL oil, WAT water, GAS gas, LIQ liquid, TIME - time).
Default:
12.18.123. WFRACL 1445

fined; there is no dependence from flow.
Example
WFRACL
'WELL123' 'LGR2' 38 426 13 38 426 21 30 0.5 250 5 'propant
16/20' 'func 5' 'LIQ'/
/
In this example hydraulic fracture if specified the following way: well WELL123 (situated
in local grid LGR2), first connection [38, 426, 13], last connection [38, 426, 21], azimuth
angle 30 , zenith angle 0.5 , half of fracture length 250, fracture width 5, propant
16/20, flow function func 5, dependence of liquid flow LIQ.
12.18.123. WFRACL 1446

12.18.124 WFRACP


Section
The keyword specifies the hydraulic fracture. This keyword is the expansion of the key-
word WFRAC (see 12.18.122). WFRACP is used to specify hydraulic fracture from graphical
interface. An arbitrary number of data lines, terminated with a slash /, can be specified (one
line for one well). All data should be terminated with a final slash /.

On the pictures below there is scheme of hydraulic fracture in the plane, which contains
the well bore, - picture 27, and hydraulic fracture for horizontal well, which contains one
connection, - picture 28.
Fractures are visualized as a part of a plane, virtual connections are made in all blocks
that this plane crosses.
Fracture, specified via keywords WFRAC (see 12.18.122), WFRACL (see 12.18.123),
WFRACP (see 12.18.124), WFRACPL (see 12.18.125), COMPFRAC (see 12.18.126),
COMPFRACL (see 12.18.127) passes through the inactive blocks until it reaches its half-
1. well name;
2. i1 first connection coordinate in X direction;
3. j1 first connection coordinate in Y direction;
4. k1 first connection coordinate in Z direction;
5. i2 last connection coordinate in X direction. If hydraulic fracture is in the plane that

is perpendicular to the well bore, only one connection should be specified, i.e. i1 = i2;
6. j2 last connection coordinate in Y direction. If hydraulic fracture is in the plane that

is perpendicular to the well bore, only one connection should be specified, i.e. j1 = j2;
7. k2 last connection coordinate in Z direction. If hydraulic fracture is in the plane that

is perpendicular to the well bore, only one connection should be specified, i.e. k1 = k2;
12.18.124. WFRACP 1447

8. azimuth angle (from 0 to 360 ). Azimuth angle in tNavigator is the angle between
positive direction of X-axis and fracture right half-length l2.
On the pictures below there is a scheme (29) and tNavigator 3D map (30) of the
fractures with different azimuth angles: 0 degrees (well PROD 14 4), 90 degrees (well
PROD 18 3) and 110 degrees (well PROD 18 5). l1 and l2 directions are on the
scheme, positive direction of X-axis for each well is specified via vector O1 X1 .
Note 1: If the fracture direction (azimuth angle) doesnt correspond to this logic in
graphical interface check please if the keyword MAPAXES (see 12.2.62) is specified
or the visualization option Flip vertically is used.
Note 2: Default values of azimuth angle and GEOMECH (see 12.1.91) option provide
calculation of azimuthal angle according to the elastic state of the cells belonging to
the fracture and to the well (example is below);
9. zenith angle (from 0 to 90 ).
10. l1 fracture left half-length from the well bore (METRIC: m, FIELD: f t ) (if azimuth
angle is 0, this half-length will be directed to the left from the well bore);
11. l2 fracture right half-length from the well bore (METRIC: m, FIELD: f t ) (if azimuth
angle is 0, this half-length will be directed to the right from the well bore);
12. h1 fracture height in one direction from the well bore (METRIC: m, FIELD: f t );
13. h2 fracture height in second direction from the well bore (METRIC: m, FIELD: f t );
14. fracture width (METRIC: m, FIELD: f t ) (in case if the width is not specified, then the
25-th parameter (proppant volume) and 15-th parameter (proppant permeability) should
be specified. tNavigator will calculate fracture width);
15. proppant properties. One of the following parameters should be specified:
proppant name (the name should be input via the keyword PROPANTNAMES
(see 12.8.2));
proppant permeability (mD). In this case proppant will have constant permeability
(see Example 5).
12.18.124. WFRACP 1448

Figure 27: Fracture in the plane, which contains the well bore
Figure 28: Fracture on horizontal well
12.18.124. WFRACP 1449

DT
F(T ) = e days
where:
D current date;
dence (OIL oil, WAT water, GAS gas, LIQ liquid, TIME - time);
18. fracture productivity multiplier (dimensionless). This is an additional correction param-
eter that can be used to history match the production data when the fracture is created.
The productivity of virtual perforations added by fracture is multiplied by this multi-
plier to account for the contribution of fracture to the well productivity.
The initial value to start history matching with this parameter can be taken
PERM proppant /PERMmodel . For heterogeneous permeability model, PERMmodel can
be taken as the average permeability of all the grid cells intersected by the fracture.
PERM proppant can be estimated from fracture conductivity and width.
19. X1-coordinate of bounding box (the fracture shouldnt be outside this box) (number of
layer in X direction should be specified);
20. Y1-coordinate of bounding box (the fracture shouldnt be outside this box) (number of
layer in Y direction should be specified);
21. Z1-coordinate of bounding box (the fracture shouldnt be outside this box) (number of
layer in Z direction should be specified);
layer in Z direction should be specified).
25. proppant volume V (m3 ). In case if injected proppant volume is specified, tNavigator
calculates fracture geometry see description and formula 5.10, 5.11.
Default:
if parameters 2-7 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then all wells
connections will be taken;
12.18.124. WFRACP 1450

Figure 29: Scheme: Azimuth angle and half-length L1 and L2
Figure 30: 3D map: Azimuth angle and half-length L1 and L2
12.18.124. WFRACP 1451

azimuth angle. Default values of azimuth and zenith angle and GEOMECH (see
12.1.91) option provide calculation of azimuthal angle according to the elastic state
of the cells belonging to the fracture and to the well (example is below), zenith angle
is 0 ;
zenith angle 0 ;
fined; there is no dependence from flow;
fracture productivity multiplier 1;
X1-coordinate of bounding box (the fracture shouldnt be outside this box) (number of
layer in X direction should be specified) 1;
Y1-coordinate of bounding box (the fracture shouldnt be outside this box) (number of
layer in Y direction should be specified) 1;
Z1-coordinate of bounding box (the fracture shouldnt be outside this box) (number of
layer in Z direction should be specified) 1;
layer in X direction should be specified) NX (see 12.1.25);
layer in Y direction should be specified) NY (see 12.1.25);
layer in Z direction should be specified) NZ (see 12.1.25).
Example 1.
Example
WFRACP
'PROD5' 39 14 2 39 14 11 110 0 140 140 0 0 0.02 'PROPPANT0'
'FLOWFUNC0' 'TIME' 3 0 0 0 0 0 0 0 /
'PROD6' 39 32 1 39 32 11 110 0 140 140 0 0 0.02 'PROPPANT1'
'FLOWFUNC1' 'TIME' 3 0 0 0 0 0 0 0 /
/
In this example hydraulic fracture if specified the following way: Well PROD5, first
connection [39, 14, 2], last connection [39, 14, 11], azimuth angle 110 , zenith angle
0 , fracture length in one direction 140 m, fracture length in second direction - 140 m,
fracture width 0.02 m, proppant PROPPANT0, flow function name - FLOWFUNC0 (time
12.18.124. WFRACP 1452

dependence), fracture productivity multiplier - 3, coordinate of bounding box non specified

(i.e. the reservoir).
Well PROD6, first connection [39, 32, 1], last connection [39, 32, 11], azimuth angle
110 , zenith angle 0 , fracture length in one direction 140 m, fracture length in second
direction - 140 m, fracture width 0.02 m, proppant PROPPANT1, flow function name -
FLOWFUNC1 (time dependence), fracture productivity multiplier - 3, coordinate of bounding
box non specified (i.e. the reservoir).
Example 2.
Example
WFRACP
'WU1' 28 63 3 28 63 3 110 0 140 140 1 1 0.02 'PROPPANT1' ' FLOW-
FUNC1' 'TIME' 3 0 0 0 0 0 0 0 /
/
In this example for horizontal well fraction is specified for connection [28, 63, 3], azimuth
angle 110 , zenith angle 0 , fracture length in one direction 140 m, fracture height
in one direction - 1 m, fracture height in second direction - 1 m, fracture width 0.02 m,
propant PROPPANT1, flow function FLOWFUNC1, time dependence (TIME).
Example 3.
12.18.124. WFRACP 1453

Example
PROPS
PROPANTNAMES
'proppant 12/18' ' proppant 16/20'/
PROPANTTABLE
30 1000. 3000.
50 900. 2500.
100 800. 2000.
150 700. 1500.
200 600. 1300.
250 500. 1100.
300 400. 1000.
350 300. 900.
400 200. 700.
800 100. 100.
1000 10. * /
...
WFRACP
'WU351' 6* 90 0 0 0 0 0 0.1 'PROPPANT 12/18' ' FLOWFUNC1' ' TIME'
3 0 0 0 0 0 0 70 /
/
In this example fracture height and half-length are defaulted. Azimuth angle 90 . Width
0.1 m. Injected proppant volume is specified - 70 m3 . Also in the PROPS section there is
proppant permeability from pressure dependence table.
In this case tNavigator takes fracture height from first to last connection, half-length is cal-
culated via formula using proppant volume. The report panel displays the following message
on the calculated geometry of the fracture:
Example
All connection of well 'WU351' was fractured. Fracture ge-
ometry: phi = 90.000000; width = 0.100000; half length =
44.077829; height = 7.940500; for volume 70.000000
Example 4.
12.18.124. WFRACP 1454

Example
GEOMECH
/
ROCKSTRE
300 150 200/
ROCKAXES
0.5 -0.5 0 0.5 0.5 0 0 0 1/
...
WFRACP
'INJ3' 2* 6 2* 8 2* 150 150 0 0 0.02 9*/
In this example the keyword ROCKSTRE (see 12.5.20) specifies the diagonal elements
of the stress tensor (the regional stress), the keyword ROCKAXES (see 12.5.19) specifies
the direction of the principal axes X, Y, Z of stress tensor (the regional stress). 8 and 9
parameters of WFRACP (see 12.18.124) are defaulted. Azimuth angle is calculated and there
will be a message at report table:
Example
Well 'INJ3': the fracture is formed. The azimuthal angle of the
formed fracture equals 45.00000 grad (WFRACP with GEOMECH op-
tion).
Example 5.
Example
DATES
01 DEC 2008 /
/
WFRACP
'PROD5' 39 14 2 39 14 11 110 0 140 140 0 0 0.02 3000 365 'TIME'
3 0 0 0 0 0 0 0 /
/
In this example fracture is made on 1-st December 2008. Proppant permeability 3000
mD, fracture living time - 365 days.
12.18.124. WFRACP 1455

12.18.125 WFRACPL


Section
The keyword specifies the hydraulic fracture for the wells in local grids (section 5.6).
This keyword is the extension of the keyword WFRAC (see 12.18.122). WFRACP is used to
specify hydraulic fracture from graphical interface.

An arbitrary number of data lines, terminated with a slash /, can be specified (one line
for one well). All data should be terminated with a final slash /.
WFRACPL must be used in place of WFRACP (see 12.18.124) to specify the hydraulic
fracture for wells in local refined grids, after the wells have been introduced with keywords
WELSPECL (see 12.18.4), COMPDATL (see 12.18.7). The keyword data for WFRACPL is
the same as for WFRACP (see 12.18.124), except for an extra parameter 2 which names the
local grid containing the connections specified in the record.
On the pictures in the description of the keyword WFRACP (see 12.18.124) there is
scheme of hydraulic fracture in the plane, which contains the well bore, - picture 27, and
hydraulic fracture for horizontal well, which contains one connection, - picture 28.
Fractures are visualized as a part of a plane, virtual connections are made in all blocks
that this plane crosses.
Fracture, specified via keywords WFRAC (see 12.18.122), WFRACL (see 12.18.123),
WFRACP (see 12.18.124), WFRACPL (see 12.18.125), COMPFRAC (see 12.18.126),
COMPFRACL (see 12.18.127) passes through the inactive blocks until it reaches its half-
1. well name;
12.18.125. WFRACPL 1456


is perpendicular to the well bore, only one connection should be specified, i.e. i1 = i2;
7. j2 last connection coordinate in Y direction. If hydraulic fracture is in the plane that
is perpendicular to the well bore, only one connection should be specified, i.e. j1 = j2;
8. k2 last connection coordinate in Z direction. If hydraulic fracture is in the plane that
is perpendicular to the well bore, only one connection should be specified, i.e. k1 = k2;
9. azimuth angle (from 0 to 360 ). Azimuth angle in tNavigator is the angle between
positive direction of X-axis and fracture right half-length l2.
On the pictures there is a scheme (29) and tNavigator 3D map (30) of the fractures
with different azimuth angles: 0 degrees (well PROD 14 4), 90 degrees (well PROD
18 3) and 110 degrees (well PROD 18 5). l1 and l2 directions are on the scheme,
positive direction of X-axis for each well is specified via vector O1 X1 .

angle is 0, this half-length will be directed to the left from the well bore);
angle is 0, this half-length will be directed to the right from the well bore);
13. h1 fracture height in one direction from the well bore (METRIC: m, FIELD: f t );
14. h2 fracture height in second direction from the well bore (METRIC: m, FIELD: f t );
16. proppant properties. One of the following parameters should be specified:
proppant name (the name should be input via the keyword PROPANTNAMES
(see 12.8.2));
proppant permeability (mD). In this case proppant will have constant permeability.
12.18.125. WFRACPL 1457

phase volume (m3 ) (the next parameter specifies a phase), when this volume
DT
F(T ) = e days
where:
D current date;
PERM proppant can be estimated from fracture conductivity and width.
layer in Z direction should be specified).
26. proppant volume V (m3 ). In case if injected proppant volume is specified, tNavigator
calculates fracture geometry see description and formula 5.10, 5.11.
Default:
12.18.125. WFRACPL 1458

if parameters 3-8 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then all wells
connections will be taken;
zenith angle 0 ;
Fracture is presented as a part of plane (is visualized in graphical interface), virtual

perforations are made in all grid blocks, which this plane crosses.
Example
WFRACPL
'WELL123' 'LGR2' 22 27 1 22 27 8 110 0 140 140 0 0 0.02
'propant 12/18' 1* 1* 5 6* /
/
In this example hydraulic fracture if specified the following way: well WELL123 (situated
in the local grid LGR1), first connection [22, 27, 1], last connection [22, 27, 8], azimuth
angle 110 , zenith angle 0 , fracture length in one direction 140 m, fracture length in
second direction 140 m fracture width 0.02 m, proppant propant 12/18, flow function
name not defined; there is no dependence from flow, fracture productivity multiplier - 5,
coordinate of bounding box not specified (i.e. the reservoir).
12.18.125. WFRACPL 1459

12.18.126 COMPFRAC


Section
The keyword sets the hydraulic fracture for connection in the grid layer.


(see 12.18.125)).
The following parameters should be specified in one line of COMPFRAC (see 12.18.126):
1. well name well name;
2. i connection coordinate in X direction. For vertical wells coordinates i, j can

be defaulted (the values specified via the keyword COMPDAT (see 12.18.6)). Via
ACTIONC (see 12.18.140) all values could be defaulted, i.e. "the value should be taken
from the connection for which "ACTIONC" condition is satisfied";
3. j connection coordinate in Y direction; For vertical wells coordinates i, j can

12.18.126. COMPFRAC 1460

4. k connection coordinate in Z direction. Via ACTIONC (see 12.18.140) all values

could be defaulted, i.e. "the value should be taken from the connection for which
"ACTIONC" condition is satisfied";
5. flag two values are possible OPEN, SHUT (open, shut hydraulic fracture). If SHUT
is used all the parameters below can be defaulted;
(see 12.8.2));
DT
F(T ) = e days
where:
D current date;
10. skin fracture efficiency; specified as skin-factor in classical approximation of hy-

draulic fracture;
if skin = 0 (default value) the fracture is not created (this is the same as flag = SHUT)
if skin < 0 the fracture efficiency and length is as big, as the absolute value of skin is;
11. pi fracture productivity multiplier;
12. mult fracture length multiplier;
12.18.126. COMPFRAC 1461

13. formula type for fracture length BLOCK or SKIN. For BLOCK type fracture length
is calculated as the product of skin, mult and block diagonal (root from the sum of
squares of DX / DY / DZ (see 12.2.2)). For SKIN type fracture length is calculated
as the product of skin, mult and 50 (there is no dependence of block size).
Default:
skin = 0;
pi = 1;
mult = 1;
formula type for fracture length BLOCK.
The keyword creates the hydraulic fracture. The differences with the fracture, created
with WFRAC (see 12.18.122), are the following:
Example
COMPFRAC
'WELL123' 38 426 13 OPEN 30 'propant 16/20' ' func 5' ' LIQ' -4
3* /
/
In this example hydraulic fracture is specified the following way: well WELL123, con-
nection [38, 426, 13], azimuth angle 30 , propant 16/20, flow function (dependence of
phase LIQ) func 5, skin = -4.
Example
COMPFRAC
'WELL123' 38 426 13 OPEN 30 3* -4 3* /
/
In this example hydraulic fracture is specified the following way: well WELL123, connec-
tion [38, 426, 13], azimuth angle 30 , proppant name not defined (infinite permeability
along the fracture (pipe)), flow function name not defined (there is no dependence from
flow), skin = -4.
12.18.126. COMPFRAC 1462

12.18.127 COMPFRACL


Section
The keyword sets the hydraulic fracture for connection in the grid layer for the wells in
local grids (section 5.6).

COMPFRACL must be used in place of COMPFRAC (see 12.18.126) to specify the hy-
draulic fracture for connection in the grid layer for wells in local refined grids, after the wells
have been introduced with keywords WELSPECL (see 12.18.4), COMPDATL (see 12.18.7).
The keyword data for COMPFRACL is the same as for COMPFRAC (see 12.18.126), except
for an extra parameter 2 which names the local grid containing the connections specified in
the record.

(see 12.18.125)).
The following parameters should be specified in one line of COMPFRACL (see 12.18.127):
1. well name well name;
12.18.127. COMPFRACL 1463

3. i connection coordinate in X direction. For vertical wells coordinates i, j can

4. j connection coordinate in Y direction; For vertical wells coordinates i, j can

5. k connection coordinate in Z direction. Via ACTIONC (see 12.18.140) all values

could be defaulted, i.e. "the value should be taken from the connection for which
"ACTIONC" condition is satisfied";
6. flag two values are possible OPEN, SHUT (open, shut hydraulic fracture). If SHUT
is used all the parameters below can be defaulted;
(see 12.8.2));
DT
F(T ) = e days
where:
D current date;
12.18.127. COMPFRACL 1464

11. skin fracture efficiency; specified as skin-factor in classical approximation of hy-

draulic fracture;
if skin = 0 (default value) the fracture is not created (this is the same as flag = SHUT)
if skin < 0 the fracture efficiency and length is as big, as the absolute value of skin is;
12. pi fracture productivity multiplier;
13. mult fracture length multiplier;
14. formula type for fracture length BLOCK or SKIN. For BLOCK type fracture length
is calculated as the product of skin, mult and block diagonal (root from the sum of
squares of DX / DY / DZ (see 12.2.2)). For SKIN type fracture length is calculated
as the product of skin, mult and 50 (there is no dependence of block size).
Default:
skin = 0;
pi = 1;
mult = 1;
formula type for fracture length BLOCK.
The keyword creates the hydraulic fracture. The differences with the fracture, created
with WFRACL (see 12.18.123), are the following:
Example
COMPFRACL
'WELL123' 'LGR2' 38 426 13 OPEN 30 'propant 16/20' ' func 5'
'LIQ' -4 3* /
/
In this example hydraulic fracture is specified the following way: well WELL123 (situated
in local grid LGR1), connection [38, 426, 13], azimuth angle 30 , propant 16/20, flow
function (dependence of phase LIQ) func 5, skin = -4.
12.18.127. COMPFRACL 1465

12.18.128 WPIFUNC


Section
The keyword specifies for the connection the function of dependence between permeabil-
ity and phase flow. Efficiency factor (the keyword WPIMULT (see 12.18.28)) is multiplied
by this function (5.14). The data should be terminated with a slash /.
The data should be terminated with final slash /.
1. well name;
2. flow function name (the dependence between fracture permeability and phase flow).
Phase is specified via the next parameter of this keyword. The function specifies the
washing out of the proppant from the fracture. (keywords FLOWFUNC (see 12.8.4),
FLOWFTAB (see 12.8.7), FLOWFNAMES (see 12.8.6));
4. connection (or trajectory) coordinate in X direction;
5. connection (or trajectory) coordinate in Y direction;
6. connection (or trajectory) coordinate in Z direction;
12.18.22)),
12.18.22)).
Flow function is specified for connection which have: connections with coordinates XYZ,
specified by parameters 4-6 of this keyword; number of completion should be between num-
bers specified by parameters 7-8.
Default:
flow function name not defined; there is no dependence from flow rate,
number of first completion in range any number,
number of last completion in range any number.
12.18.128. WPIFUNC 1466

Example
WPIFUNC
'WELL123' ' func 5' ' LIQ' 38 426 13 3 9 /
/
12.18.128. WPIFUNC 1467

12.18.129 WSKFUNC


Section
The keyword specifies for the connection the function of dependence between skin-factor
and phase flow. Skin-factor (the keyword COMPDAT (see 12.18.6)) is multiplied by this
function (5.15). The data should be terminated with a slash /.
1. well name;
2. flow function name (the dependence between fracture permeability and phase flow).
Phase is specified via the next parameter of this keyword. The function specifies the
washing out of the proppant from the fracture. (keywords FLOWFUNC (see 12.8.4),
FLOWFTAB (see 12.8.7), FLOWFNAMES (see 12.8.6));
12.18.22)),
12.18.22)).
Flow function is specified for connection which have: connections with coordinates XYZ,
specified by parameters 4-6 of this keyword; number of completion should be between num-
bers specified by parameters 7-8.
Default:
12.18.129. WSKFUNC 1468

Example
WSKFUNC
'WELL34' func 2'
' ' OIL' 38 426 13 3 9 /
/
12.18.129. WSKFUNC 1469

12.18.130 WBHZONE


Section
The keyword specifies the properties of well bottom zone (5.15). The data should be
1. well name;
w,l
2. radius of well bottom zone rbhz (5.15) (METRIC: m, FIELD: f t );
3. flow function name (the dependence between well bottom zone radius and phase flow
rate). Phase is specified via the next parameter of this keyword. The function specifies
the plugging of the well bottom zone. (keywords FLOWFUNC (see 12.8.4), FLOWFTAB
(see 12.8.7), FLOWFNAMES (see 12.8.6));
w,l
5. permeability of well bottom zone in radial direction Kbhz (5.15);
6. permeability of well bottom zone in vertical direction K w,l (5.15);
12.18.22)),
12.18.22)).
Well bottom zone properties are specified for connections which have: connections with
coordinates XYZ, specified by parameters 7-9 of this keyword; number of completion should
be between numbers specified by parameters 10-11.
Default:
12.18.130. WBHZONE 1470

w,l
radius of well bottom zone rbhz not specified;
phase LIQ liquid,

w,l
permeability of well bottom zone in radial direction Kbhz not specified;
permeability of well bottom zone in vertical direction K w,l not specified;
Example
WBHZONE
'PROD' 2 'func 2' ' OIL' 10 0.1 4 17 2/
/
12.18.130. WBHZONE 1471

12.18.131 ACTION


Section
This keyword initiates a set of keywords to be processed when a specified field condition
is satisfied.
The keyword ACTION (G, R, W) marks the start of a set of SCHEDULE section keywords
that are to be stored for later processing when a specified condition is satisfied. The key-
word ACTION specifies a field condition for triggering an action. Keywords ACTIONG (see
12.18.132), ACTIONR (see 12.18.133), ACTIONW (see 12.18.134) offer greater flexibility,
and specify actions triggered by group, region, well conditions respectively.
Keyword ACTIONX (see 12.18.135) is more flexible, and specifies the check of a set of
conditions for wells, groups, regions in one keyword (The following operators AND, OR
can be used).
The set of keywords must be terminated with the keyword ENDACTIO. The keywords
between ACTION and ENDACTIO are processed when the condition defined in the ACTION
keyword is satisfied.
Almost any SCHEDULE section keyword may be placed between ACTION and ENDAC-
TIO, with the exception of time stepping keywords (TSTEP (see 12.18.106), DATES (see
12.18.105), etc.).
Each action initiated with the ACTION keyword is executed only once, at the end of the
timestep during which its triggering condition is first satisfied. Each action keyword set must
be bracketed by a pair of ACTION (G, R, W) and ENDACTIO keywords, and is distinguished
by its action name defined in parameter 1 of the keyword. If an ACTION family keyword is
re-entered with the same action name as a previously declared action, the action keyword set
is overwritten by the new data.
The following parameters are to be specified (The data should be terminated with a slash
/.):
1. action name;
2. quantity to which the triggering condition applies:
FOPR Field oil production rate,

FWPR Field water production rate,
12.18.131. ACTION 1472

FGPR Field gas production rate,

FGOR Field gas oil ratio,
FWCT Field water cut,
FPR Field average pressure,
FOPT Field oil production cumulative total,
FWPT Field water production cumulative total,
FGPT Field gas production cumulative total,
FOIR Field oil injection rate,
FWIR Field water injection rate,
FGIR Field gas injection rate,
FOIT Field oil injection cumulative total,
FWIT Field water injection cumulative total,
FGIT Field gas injection cumulative total.
3. the operator for the triggering condition:
< Less than;

> Greater than.
4. the value of the triggering condition.
Example
ACTION
A1 FWIR > 4000 /
WELOPEN
INJ1 SHUT 0 0 5 /
INJ2 SHUT 0 0 5 /
/
ENDACTIO
In this example the following action is specified: if Field water injection rate is greater
than 4000, then all connections in 5 layer of wells INJ1 and INJ2 will be shut.
12.18.131. ACTION 1473

12.18.132 ACTIONG


Section
This keyword initiates a set of keywords to be processed when a group specifies a specific
condition.
The keyword ACTIONG marks the start of a set of SCHEDULE section keywords that are
to be stored for later processing when a nominated group satisfies a specified condition. The
set of keywords must be terminated with the keyword ENDACTIO.
The keywords between the ACTIONG and ENDACTIO keywords are processed at the end
of the timestep when the condition defined in the ACTIONG keyword is satisfied by a group
named in parameter 2. You can choose whether the action is to be performed only once, or
repeatedly each timestep while the triggering condition is satisfied. If a group keyword is
placed between ACTIONG and ENDACTIO, instead of entering the name of a specific group
in the keyword you may enter a question mark. That applies the keyword data to whichever
group (or groups) triggered the action.
Almost any SCHEDULE section keyword may be placed between ACTIONG and EN-
DACTIO, with the exception of time stepping keywords (TSTEP (see 12.18.106), DATES
(see 12.18.105), etc.).
Each action keyword set must be bracketed by a pair of ACTION (G, R, W) and
]ENDACTIO keywords, and is distinguished by its action name defined in parameter 1.
This name must be unique across all the action keyword family. If an ACTION (G, R, W)
keyword is re-entered with the same action name as a previously declared action, the previ-
ously declared action is deleted and replaced with the new action.
/.):
1. action name;
2. group name (or name root) of the group(s) that triggers this action, or FIELD (for an
action triggered by a field quantity). A group name root, enclosed in quotes and ending
with an asterisk (*), can be used to make this actions triggering condition apply to
more than one group. The action will then be performed if one or more groups having
this name root satisfy the triggering condition. The action is performed at most once
per timestep, even if more than one group satisfies the triggering condition at the end
of the timestep;
12.18.132. ACTIONG 1474

3. the quantity to which the triggering condition applies:
GOPR Group oil production rate,

GPOT Group oil production cumulative total,
GOIR Group oil injection rate,
GOIT Group oil injection cumulative total,
GWPR Group water production rate,
GWPT Group water production cumulative total,
GWIR Group water injection rate,
GWIT Group water injection cumulative total,
GGPR Group gas production rate,
GGPT Group gas production cumulative total,
GGIR Group gas injection rate,
GGIT Group gas injection cumulative total GVPR,
GVPR Group voidage production rate,
GVPT Group voidage production cumulative total,
GVIR Group voidage injection rate,
GVIT Group voidage injection cumulative total,
GLPR Group liquid production rate,
GLPT Group liquid production cumulative total,
GGOR Group gas oil ratio,
GWCT Group water cut.
4. the operator for the triggering condition.:
< Less than;

> Greater than.
5. the value of the triggering condition;
6. number of times this action can be triggered. The action is performed once at the end of
each timestep while any group named in parameter 2 satisfies the triggering condition,
until it has been performed the specified number of times. A number of 10000 or
greater is interpreted as infinity;
7. increment to the triggering condition. After each time the action is performed, the
specified increment is added to the triggering condition value (initialized in parameter
5). The increment may be negative, if desired.
Default:
12.18.132. ACTIONG 1475

The value of the triggering condition: 1;
Increment to the triggering condition: 0.
Example
ACTIONG
A1 'GROUP2' GGPR < 20000 /
WELOPEN
W1 OPEN /
W7 OPEN /
W8 OPEN /
/
ENDACTIO
In this example there is one action keyword set. The action A1 will open wells W1, W7,
W8, when the Group gas production rate of group GROUP2 falls below 20000.
12.18.132. ACTIONG 1476

12.18.133 ACTIONR


Section
The keyword initiates a set of keywords to be processed when a region satisfies a speci-
fied condition.
The ACTIONR keyword marks the start of a set of SCHEDULE section keywords that are
to be stored for later processing when a nominated fluid-in-place region satisfies a specified
condition. The set of keywords must be terminated with the ENDACTIO keyword.
The keywords between the ACTIONR and ENDACTIO keywords are processed at the end
of the timestep when the condition defined in the ACTIONR keyword is satisfied by a region
identified in parameters 2 and 3. You can choose whether the action is to be performed only
once, or repeatedly each timestep while the triggering condition is satisfied.
Almost any SCHEDULE section keyword may be placed between ACTIONR and EN-
DACTIO, with the exception of timestepping keywords (TSTEP (see 12.18.106), DATES
(see 12.18.105), etc.).
/.):
1. action name;
2. fluid-in-place region number, whose conditions trigger this action. This should be an
integer. Region 0 refers to the whole field. Fluid-in-place regions are defined with the
keyword FIPNUM (see 12.4.10);
3. the fluid-in-place region family, to which the specified region belongs. A default (1*)
or blank (' ') entry refers to the standard set of fluid-in-place regions defined with
the keyword FIPNUM (see 12.4.10). Additional families of fluid-in-place regions may
optionally be defined, using the keyword FIP (see 12.4.11).
12.18.133. ACTIONR 1477

RPR Region pressure,

ROIP Region oil in place,
RWIP Region water in place,
RGIP Region gas in place (in liquid and gas phases).
< Less than;

> Greater than.
6. the value of the triggering condition;
7. number of times this action can be triggered. The action is performed once at the end
of each timestep while the triggering condition is satisfied, until it has been performed
the specified number of times. A number of 10000 or greater is interpreted as infinity;
Default:
The value of the triggering condition: 1;
Increment to the triggering condition: 0.
Example
ACTIONR
A1 3 WELRG ROIP < 800000 1 /
WELOPEN
P31 SHUT /
P32 SHUT /
P33 SHUT /
P34 SHUT /
P7 OPEN 0 0 7 /
/
ENDACTIO
In this example there is one action keyword set. The action A1 shuts wells P31, P32, P33,
P34 and opens all connection of the well P7 in layer 7, when Region oil in place in region 3
of the family WELRG is less than 800000.
12.18.133. ACTIONR 1478

12.18.134 ACTIONW


Section
The keyword initiates a set of keywords to be processed when a well satisfies a specified
condition.
The ACTIONW keyword marks the start of a set of SCHEDULE section keywords that are
to be stored for later processing when a nominated well satisfies a specified condition. The
set of keywords must be terminated with the ENDACTIO keyword. The keywords between
the ACTIONW and ENDACTIO keywords will be processed at the end of the timestep when
the condition defined in the ACTIONW keyword is satisfied by a well named in parameter 2.
You can choose whether the action is to be performed only once, or repeatedly each timestep
while the triggering condition is satisfied.
Almost any SCHEDULE section keyword may be placed between ACTIONW and EN-
(see 12.18.105), etc.).
/.):
1. action name;
2. well name (or name root) of the well(s) that triggers this action. A well name root,
enclosed in quotes and ending with an asterisk (*), can be used to make this actions
triggering condition apply to more than one well. The action is then performed if one
or more wells having this name root satisfy the triggering condition. The action will be
performed at most once per timestep, even if more than one well satisfies the triggering
condition at the end of the timestep;
WOPR Well oil production rate,

WOPT Well oil production cumulative total,
12.18.134. ACTIONW 1479

WOIR Well oil injection rate,

WOIT Well oil injection cumulative total,
WWPR Well water production rate,
WWPT Well water production cumulative total,
WWIR Well water injection rate,
WWIT Well water injection cumulative total,
WGPR Well gas production rate,
WGPT Well gas production cumulative total,
WGIR Well gas injection rate,
WGIT Well gas injection cumulative total,
WLPR Well liquid production rate,
WLPT Well liquid production cumulative total,
WVPR Well voidage production rate,
WVPT Well voidage production cumulative total,
WVIR Well voidage injection rate,
WVIT Well voidage injection cumulative total,
WGOR Well gas oil ratio,
WWCT Well water cut,
WBHP Well bottom hole pressure,
WTHP Well tubing head pressure.
< Less than;

> Greater than.
5. the value of the triggering condition.;
6. number of times this action can be triggered. The action will be performed once at
the end of each timestep while any well named in parameter 2 satisfies the triggering
condition, until it has been performed the specified number of times. A number of
10000 or greater is interpreted as infinity;
Default:
number of times this action can be triggered: 1;
12.18.134. ACTIONW 1480

increment to the triggering condition: 0.
Example
ACTIONW
A1 'PROD*' WWCT > 0.5 /
WELOPEN
W1 OPEN /
W4 OPEN /
PROD3 SHUT 0 0 7 /
PROD6 SHUT 0 0 7 /
/
ENDACTIO
In this example there is one action keyword set. The action A1 opens wells W1, W4 and
shuts all connections in 7-th layer of wells PROD3 and PROD6, when watercut of any of the
wells whose names begin with PROD is greater than 0.5.
12.18.134. ACTIONW 1481

12.18.135 ACTIONX


Section
This keyword initiates a set of keywords to be processed when a specified field condition
is satisfied.
The keyword ACTIONX marks the start of a set of SCHEDULE section keywords that
are to be stored for later processing when a specified condition is satisfied. The keyword
ACTIONX specifies a field condition for triggering an action. The set of keywords must be
terminated with the keyword ENDACTIO.
The keywords between ACTIONX and ENDACTIO are processed when the condition de-
fined in the ACTIONX keyword is satisfied. The action can be processed one time or can be
processed at each time step when a specified condition is satisfied.
Almost any SCHEDULE section keyword may be placed between ACTIONX and EN-
(see 12.18.105), etc.).
Keywords ACTION (G, R, W) set the condition only for one parameter for group, well,
field. Keyword ACTIONX (see 12.18.135) is more flexible, and specifies the check of a set
of conditions for wells, groups, regions in one keyword (The following operators AND, OR
can be used).
ACTIONX can be specified for well list (WLIST (see 12.18.26)). The condition on spec-
ified date can be specified.
If the keyword ACTION (G,R,W,X) is entered the second time with the same action name,
then the previous action is replaced by the first one.
The keyword consist of:
ACTIONX;
first row with action name and the number of times this action can be triggered;
several rows, specified a set of conditions to be checked;
the keywords of SCHEDULE section, that will be applied if the specified set of condi-
tions is satisfied;
12.18.135. ACTIONX 1482

ENDACTIO.
The parameters of first row (The data should be terminated with a slash /.):
1. action name;
2. number of times this action can be triggered. The action will be applied at the end of
each time step since the specified set of conditions is satisfied and since the action is
applied this number of times. The number 10000 or greater is interpreted as an infinity;
3. minimum time interval between action triggers (days). An action is proceeded if two
conditions are satisfied: specified set of conditions is satisfied and the simulation has
passed the specified time interval since the last time this action was triggered;
Default:
number of times this action can be triggered: 1;
minimum time interval between action triggers 0 (days).
Second and next data rows (The data should be terminated with a slash /.). At the
end of all data the final slash / should be put:
1. a left hand quantity. All parameters and expressions that can be used are described
below.
A well name root (or group name root), followed by an asterisk (*), can be used to
evaluate a set of conditions for several wells or groups. In this case a set of conditions
is true if it is true for at least one well or group.
In the case of conditions for well connections it is true if it is true for at least one
connection.
2. operator for the triggering condition:
< less than;

> greater than;
<= less or equal;
>= greater of equal;
= equal;
!= not equal.
3. a right hand quantity. All parameters and expressions that can be used are described
below. In the right hand quantity well root names ant group root names cant be used;
4. boolean operator that links this condition with conditions in subsequent data rows:
AND and (conditions in this and next data row must be true simultaneously);
12.18.135. ACTIONX 1483

OR or (a condition specified in this row OR a condition in the next row must

be true).
Parameter types and definitions.
Constant quantity:
1. triggering condition value;
2. increment to the triggering condition value (specified by 1-st parameter). After each
time the action is proceeded, the specified increment is added to the triggering condition
value. This increment can be negative.
Default:
increment to the triggering condition value (specified by 1-st parameter) 0.
Time:
1. time value:
DAY current simulation date;
MNTH current simulation month;
YEAR current simulation year.
Region:
1. parameter for region:
RPR average pressure in FIP region;
ROIP region oil in place;
RWIP region water in place;
RGIP region gas in place (in liquid and gas phases);
RUxxx the parameter specified by used in FIP region.
2. FIP region number:
3. FIP region family to which the specified region belongs: default FIP regions FIPNUM
(see 12.4.10), or additional families of FIP region specified by user FIP (see 12.4.11).
Syntax examples for FIP regions:
Example 1.
Example
ACTIONX
ACT_U246 100000 30/
RPR 58 NUM > 280 AND /
WWPR 425 < 500/
/
12.18.135. ACTIONX 1484

In this example the following condition is checked: is the pressure in the FIP-region 58
greater than 280 or not. FIP region family is set via NUM after the region number.
Example 2.
Example
ACTIONX
ACT_D234 100000 30/
RPR__NUM 1 < 186.4 /
/
In this example the following condition is checked: is the pressure in the FIP-region 1
less than 186.4 or not. FIP region family is set via NUM after the average pressure RPR and
two underscore symbols.
Well:
1. parameter for well: all parameters that are supported in SUMMARY (see 12.17.1) are
available.
FIELD:
1. parameter for FIELD: all parameters that are supported in SUMMARY (see 12.17.1)
are available.
Group:
1. parameter for group: all parameters that are supported in SUMMARY (see 12.17.1) are
available.
Connection:
1. parameter for connection: all parameters that are supported in SUMMARY (see 12.17.1)
are available.
2. well name;
3. i-coordinate of grid block with connection;
4. j-coordinate of grid block with connection;
5. k-coordinate of grid block with connection.
Default:
i,j,k coordinates of grid block with connection negative (allows any value).
12.18.135. ACTIONX 1485

Below the list of options that are not supported in ACTIONX (see 12.18.135) in this
moment.
ALWAYS condition: Not supported.
Multisegment well: Not supported.
LGR. Connections in LGR: Not supported.
Aquifer: Not supported.
Block: Not supported.
Example 1.
Example
ACTIONX
ACTSAT 1 /
YEAR = 2028 AND /
MNTH = APR AND /
DAY >= 1 /
/
GSATPROD
GR1 1248 137.28 1497600 /
/
GSATINJE
GR1 WATER 10000 2* /
/
ENDACTIO
The action with name ACTSAT is specified, it is proceeded one time. If the date is later
than specified data 1 April 2028, then oil, water and gas rate are specified for satellite
group GR1 (GSATPROD (see 12.18.83)) and water injection rate is specified for satellite
group (GSATINJE (see 12.18.84)).
Example 2.
12.18.135. ACTIONX 1486

Example
ACTIONX
SN1 1 /
WLPR W8 < 120 AND /
WLPR W9 < 90 /
/
WELOPEN
N1 SHUT /
/
ENDACTIO
The action with name SN1 is specified: If liquid rate of the well W8 is less than 120 and
liquid rate of the well W9 is less than 90, then the well N1 will be closed.
12.18.135. ACTIONX 1487

12.18.136 DELAYACT


Section
The keyword defines delayed well actions. These actions perform if separately specified
action is performed and if specified time period has passed. List of actions must be ended by
the keyword ENDACTIO (see 12.18.137).
1. delayed action name. If action with the same name is specified in the model, then the
new one will overwrite the old;
2. action name which if performed, then performs action in the 1-st parameter;
3. time delay, after which action in the 1-st parameter will be performed (METRIC: days;
FIELD: days);
4. number of times this action can be performed. Action is performed at the end of each
timestep on which action in the 2-nd parameter performed as many times as specified
there;
5. number of days to add to delay after each action activating (METRIC: days; FIELD:
days).
slash /.
Default:
number of times this action can be performed: 1;
number of days to add to delay after each action activating: 0.
12.18.136. DELAYACT 1488

Example
ACTIONX
ACT1 6 0 /
FOPR < 50 /
/
WELTARG
'P1' 'BHP' 98 /
/
ENDACTIO
DELAYACT
ACTDELAY ACT1 20 2 -10 /
/
WELTARG
'P1' 'BHP' 88 /
/
ENDACTIO
In the example the keyword DELAYACT (see 12.18.136) defines action ACTDELAY,
which performs twice: firstly, 20 days after ACT1 has performed, secondly, after 10 days
ACT1 has performed again. Action ACT1 is defined via the keyword ACTIONX (see
12.18.135).
12.18.136. DELAYACT 1489

12.18.137 ENDACTIO / ENDACTION


Section
These keyword are used at the end of data when keywords ACTION (see 12.18.131), AC-
TIONG (see 12.18.132), ACTIONR (see 12.18.133), ACTIONW (see 12.18.134), ACTIONX
(see 12.18.135) of DELAYACT (see 12.18.136) are used.
ENDACTION is full analogue of ENDACTIO.
12.18.137. ENDACTIO / ENDACTION 1490

12.18.138 UDQ


Section
The keyword allows to specify User defined quantities in SCHEDULE (see 12.18.1) sec-
tion. User defined quantities can be specified for field, groups, regions, wells, connections,
segments.
User defined quantities can be:
constants;
any parameter from SUMMARY (see 12.17.1) section;
a combination of parameters from SUMMARY (see 12.17.1) section with mathematical

functions and operations.
User defined quantities can be used one of the following ways:
for output in SUMMARY (see 12.17.1) section. If the value of any quantity remain
uninitialized then it will be replaced by the value specified in 3-rd parameter of the
keyword UDQPARAM (see 12.1.41);
in the keywords ACTIONG (see 12.18.132), ACTIONR (see 12.18.133), ACTIONW

(see 12.18.134), ACTIONX (see 12.18.135) (If the value of any quantity remain
uninitialized then it will be replaced by the value specified in 3-rd parameter of the
keyword UDQPARAM (see 12.1.41)).
as user defined argument UDA in keywords WCONINJE (see 12.18.36), WECON (see
12.18.62), WELDRAW (see 12.18.104), WCONPROD (see 12.18.34), GCONPROD
(see 12.18.72), GCONINJE (see 12.18.81), GECON (see 12.18.102).
The keyword consists of an arbitrary number of data lines, each data row specifies its own
user defined quantity. Each row should be terminated with a slash /. All data row should be
1. operation name:
ASSIGN assigns a numeric value to elements of a quantity (this operation takes

place at the moment of operation initialization);
12.18.138. UDQ 1491

DEFINE defines a mathematical expression (an expression is applied after the

current time step. Expression is recalculated at each time step);
UPDATE specifies time of next evaluation of quantity definition. The quantity
should already be initialized in order to perform this operation.
2. quantity name: CU connection quantity, FU field quantity, GU group quantity, RU

region quantity, WU well quantity.
3. operation data (in the syntax that is described below) (for UPDATE operation on of the
following: ON, OFF, NEXT at which time step an expression should be calculated: at
all, none, nest time step).
Syntax. All parameters of SUMMARY (see 12.17.1) section can be used.
1. connection quantity. For example:
CWPR water rate for all connections for all wells (set of numbers);
CWPR WELL1 water rate for all connections for the well WELL1 (set of
numbers);
CWPR GR* water rate for all connections for all wells which names begins
with GR (set of numbers).
2. field quantity. For example: FWPR field water rate (one number).
3. group quantity. For example:
GWPR water rate for all groups (set of numbers);

GWPR GROUP4 water rate for the group GROUP4 (one number).
4. region quantity. For example:
RWPR water rate for all regions (set of numbers);

RWPR 4 water rate for region 4 (one number).
5. well quantity. For example:
WWPR water rate for all wells (set of numbers);

WWPR WELL1 water rate for the well WELL1 (one number);
WWPR GR* water rate for all wells which names begins with GR (set of
numbers).
6. multisegment well quantity. For example:
SWFR water rate for all multisegment wells (set of numbers);

SWFR GR* water rate for all multisegment wells which names begins with GR
(set of numbers);
12.18.138. UDQ 1492

SWFR GR* 2 water rate for 2-nd segment of multisegment wells which names
begins with GR (set of numbers);
SWFR WELL1 2 water rate for 2-nd segment of WELL1 (one number).
Available mathematic functions and operations.
Definition Function or operation description
+ Addition
- Subtraction
* Multiplication
/ Division
^ Exponentiation
<= Less or equal
>= Greater or equal
< Less
> Greater
== Comparison (returns 1, if the left argument is equal to the right argument)
!= Not equal
( Opening bracket
) Closing bracket
SUM () Sum of specified elements
MIN () Minimum of specified elements
MAX () Maximum of specified elements
ABS () Module (absolute value) of specified elements
EXP () Exponential of specified elements
LOG () Natural logarithm of specified elements
LOG10 () Base 10 logarithm of specified elements
UADD () Sum with the following difference from an ordinary sum. If one of the items
is undefined, then operation + returns undefined, but UADD returns the
sum of other defined items.
UMAX () Maximum with the following difference from an ordinary maximum. If one
of the items is undefined, then operation MAX returns undefined, but
UMAX returns the maximum of other defined items.
UMIN () Minimum with the following difference from an ordinary minimum. If one
of the items is undefined, then operation MIN returns undefined, but
UMIN returns the minimum of other defined items.
UMUL () Multiplication with the following difference from an ordinary multiplication.
If one of the items is undefined, then operation UMUL returns undefined,
but UMUL returns the result of multiplication of other defined items.
TU*[] Values from user defined tables UDT (see 12.18.139). One parameter for
each table dimension should be specified. Inside square brackets any com-
putations cant be used.
NINT() Nearest integer to a given number. Numbers which fraction part is 0.5 are
rounded to nearest even.
12.18.138. UDQ 1493

Dates that are available in ACTIONX (see 12.18.135): TIME current simulation
time; TIMESTEP length of time step.
Example
UDQ
DEFINE WUGOR3 (WGOR > (FGOR*4)) /
/
ACTIONW
ACTGOR3 'P*' WUGOR3 > 1 99999 /
WELOPEN
'?' SHUT /
/
ENDACTIO
In this example user defined quantity with a name WUGOR3 is specified. A quantity
returns 1 (is true), if well gas-oil ratio (WGOR) is 4 times greater than field gas-oil ratio
(FGOR*4). If this quantity false it returns 0.
Then a new action ACTGOR3 is created via the keyword ACTIONW. This action takes
place for all well which name begins with P and a quantity WUGOR3 is true. The action
shut well, which name begins with P and quantity WUGOR3 is true.
12.18.138. UDQ 1494

12.18.139 UDT


Section
This keyword allows to set user defined lookup table in the SCHEDULE (see 12.18.1)
section. These tables can be used to assign values to user defined quantities UDQ (see
12.18.138). Dimensions are set via UDTDIMS (see 12.1.43).
The number of lines depends on table dimension. Each line should be terminates with a
First table row (terminated with a slash /):

1. table name (begins with TU);
2. number of dimensions in the table (NUMDIM).
Second table row and next rows till NUMDIM+1 (each one terminated with a slash /):
1. interpolation type that will be used in this direction:
NV the nearest value will be used;
LC linear interpolation within the table but equal to the first or last value
correspondingly outside the table;
ID linear interpolation within the table, linear extrapolation outside it.
2. interpolation points for this dimension (ascending order).
Row number NUMDIM+2 and next (each one terminated with a slash /) according to the
following rules (see an Example 2):
Each row contains one value for each interpolation point in the first dimension (termi-
nated with a slash /);
First row sets the numbers for fixed 2-nd, 3-rd and 4-th dimensions (if present), which
are equal to 1. Second row sets the numbers for fixed 2-nd dimension (equal 2) and
3-rd and 4-th dimension (if present) equal 1, etc.;
At the end of the rows for the 2-nd, there is a record containing only a slash /, to
indicate the end of this dimension;
A slash / should be entered every time we end the dimension. So after the row which
corresponds to the last point in the 2-nd dimension and the last point in the 3-rd
dimension, we should have two rows containing only slashes /;
12.18.139. UDT 1495

Second dimension should always be terminated with a slash /, even for one-
dimensional table (see an Example 1).
Example 1. One-dimensional table
Example
UDT
TUDIM1 1 /
LC 5.0 15.0 18.0 20.0 50.0 175.0 / reservoir pressure
1 0.8618 0.8580 0.8519 0.8451 0.8451 / multiplier
/ terminates 2-nd dimension
/ terminates UDT keyword
...
UDQ
DEFINE FUTUDIM1 TUDIM1[FOPR] / reference to one-dimensional
table UDT
/
Example 2. Three-dimensional table
12.18.139. UDT 1496

Example
UDT
TUDIM3 3 /
LL 21 22 23 24 /
NV 0.1 0.2 /
LC 0.5 10 20 /
2 rows below correspond to the 1-st value in LC dimension
21 22 23 24 / corresponds to the 1-st value in NV dimension
28 38 48 58 / corresponds to the 2-nd value in NV dimension
/ terminates NV dimension
2 rows below correspond to the 2-nd value in LC dimension
2 rows below correspond to the 3-rd value in LC dimension
/ terminates LC dimension
/ terminates UDT keyword
...
UDQ
DEFINE FUTUDIM3 TUDIM3[FUTUDIM1,FUFOO,FUTOT] / reference to
three-dimensional table UDT
/
12.18.139. UDT 1497

12.18.140 ACTIONC


Section
The keyword specifies the action which takes place if a specified condition is satisfied
for the block with connection.
The keyword ACTIONC can be entered in any place in SCHEDULE section. It can also
be specified once in the beginning of SCHEDULE section. In this case actionc operations
will take place each time a specified condition is satisfied for the block with connection until
limit of times is exhausted.
For example (see Example 5 below) to create fractures for injectors when block pres-
sure is greater than a specified value, ACTIONC can be specified once in the beginning of
SCHEDULE section, parameter times is specified 10000 (the operation of fracture creation
will take place until limit of times is exhausted).
The keyword should be used the following way:

ACTIONC keyword. All parameters, ended with a slash /.
Then actionc operations should be specified actions which take place if a specified
condition is satisfied for the block with connection.
At the end of action the keyword ENDACTIO should be entered.
Example
ACTIONC
action name well name well status i1 i2 j1 j2 k1 k2 quantity operation
value times increment /
...
actionc operations
...
ENDACTIO

1. action name name of this action;
12.18.140. ACTIONC 1498

2. well name well name (or well list defined via WLIST (see 12.18.26));
3. well status well status, for which actionc operations will take place:
ALL all;
PROD producers;
INJ injectors;
STOP stopped.
5. i2 last connection coordinate in X direction;
7. j2 last connection coordinate in Y direction;
9. k2 last connection coordinate in Z direction;
10. quantity the quantity to which the triggering condition applies:
BPR pressure in the block i, j , k ;

CSKIN skin-factor for the connection in block i, j , k .
11. operation the operator for the triggering condition; the following operators are pos-
sible:
< less than value;

> greater than value.
12. value the value of the triggering condition;
13. times number of times this action can be triggered;
14. increment increment to the triggering condition value.
Default:
well name all wells;
well status well status, for which actionc operations will take place: ALL;
i1 first connection coordinate in X direction: 1;
i2 last connection coordinate in X direction: NX;
j1 first connection coordinate in Y direction: 1;
12.18.140. ACTIONC 1499

j2 last connection coordinate in Y direction: NY;
k1 first connection coordinate in Z direction: 1;
k2 last connection coordinate in Z direction: NZ;
times number of times this action can be triggered: 1;
increment increment to the triggering condition value: 0.
The keywords in actionc operations syntax.
In actions enumerated in actionc operations (for example in the keyword COMPFRAC

(see 12.18.126)) one can use the following expressions to identify connection in block (i, j ,
k ) of well well name, for which the condition is satisfied:
? as parameter well name in actionc operations. For example to take all the wells
for which the condition in ACTIONC is satisfied: in the keyword ACTIONC the well
name should be * (all wells), in the COMPFRAC (see 12.18.126) on the place of
well name the symbol ? should be used, and connections coordinates should be *
(all connections for which condition in ACTIONC is satisfied);
* as a number of connection i, j, k in actionc operations stands for the corresponding

value from well well name;
* as a parameter skin in actionc operations stands for skin-factor of the well well
name.
Example 1.
Example
ACTIONC
'ACT1' '2*' 6* BPR > 300 /
COMPFRAC
'?' 3* OPEN 45 3* -4 3*/
/
ENDACTIO
For all connections of all wells: if pressure in block with connection is greater than 300
bar an operation COMPFRAC (see 12.18.126) should be done one time in this block. The
fracture with following properties is created: azimuth angle - 45 , infinite permeability along
the fracture, there is no dependence from flow, fracture efficiency with skin-factor -4.
Example 2.
12.18.140. ACTIONC 1500

Example
ACTIONC
'ACT2' '2*' 6* BPR < 200 /
COMPFRAC
'?' 3* SHUT 45 3* -4 3*/
/
ENDACTIO
For all connections of all wells: if pressure in block with connection is less than 200 bar
an operation COMPFRAC (see 12.18.126) should be done one time in this block. The fracture
with following properties is closed: azimuth angle - 45 , fracture efficiency with skin-factor
-4.
Example 3.
Example
ACTIONC
'ACT3' '2*' 6* CSKIN < 0 /
COMPFRAC
'?' 3* OPEN 45 4* 3*/
/
ENDACTIO
For all connections of all wells with nonzero skin-factor: an operation COMPFRAC
(see 12.18.126) should be done one time in this block. The fracture with following prop-
erties is created: azimuth angle - 45 , infinite permeability along the fracture, there is no
dependence from flow, fracture efficiency with skin-factor equal to skin-factor of this con-
nection.
Example 4.
12.18.140. ACTIONC 1501

Example
ACTIONC
'INJSKIN' '*' 'INJ' 6* 'BPR' '>' 308 10000 1* /
/
COMPFRAC
'?' 1* 1* 1* 'OPEN' 110 1* 1* 1* -1.5 10 1.0 1*/
/
ENDACTIO
/
For all connections of all injectors: if pressure in block with connection is greater than
308 bar an operation COMPFRAC (see 12.18.126) should be done in this block. The fracture
with following properties is created: azimuth angle - 100 , infinite permeability along the
fracture, there is no dependence from flow, fracture efficiency with skin-factor -1.5, produc-
tivity multiplier 10, fracture length multiplier 1. Operation will take place until limit of
times is exhausted (parameter times is 10000).
12.18.140. ACTIONC 1502

12.18.141 WLIMTOL


Section
The keyword sets tolerance fractures for economic and other limits. The data should be
The tolerance fraction is applied to the following limits:
1. connection, well, group, field economic limits (WECON (see 12.18.62), GECON (see
12.18.102), 12.18.68);
2. group, field maximum rate limits resulting in well workovers or closures (GCONPROD
(see 12.18.72)).
Default: Not specified.
If one of the limits above is violated during any time step then at the end of the time step
wells switch to the corresponding control. So the limit is violated for one time step before the
control was switched. If the limit is violated by more than the tolerance fraction multiplied
by the limiting value, the time step is recalculated after the control was switched. Thus, the
change of control takes effect from the beginning of the time step during which the limit
would otherwise have been violated.
Example
WLIMTOL
0.15 /
12.18.141. WLIMTOL 1503

12.18.142 SEPVALS


Section
This keyword defines the initial separator conditions (first use of the keyword) and
changes them during the simulation (next uses of the keyword). The first SEPVALS must
be followed by the keyword GSEPCOND (see 12.18.143), which allocates well groups to
separators. If the separator corresponds to a group, all wells of this group use this separator.
If the separators conditions are altered by redefining them via SEPVALS, then the oil and
gas rates of these wells are transformed to reflect the change in conditions.
The keyword can only be used in "black oil" run.

There must be at least one TSTEP (see 12.18.106) or DATES (see 12.18.105) between two
entries of SEPVALS, in order to specify the moment of condition changes.
The keyword can be followed by any number of data rows. Each row should be terminated
with a slash /. The data should be terminated with a final slash /.
Each row consists of the following parameters:
1. separator name; the number of separators should be less or equal to the number of well
groups (the 3-rd parameter of the keyword WELLDIMS (see 12.1.36));
2. formation volume factor of bubble point oil when flashed from reservoir conditions to
stock tank conditions through the separator (METRIC: rm3 /sm3 , FIELD: rb/stb);
3. solution gas-oil ratio of bubble point oil, when flashed from reservoir conditions to
stock tank conditions through the separator (METRIC: sm3 /sm3 , FIELD: Msc f /stb).
Example
SEPVALS
SEP1A 1.24 0.49 /
SEP1B 1.243 0.50 /
SEP1C 1.252 0.514 /
/
...
GSEPCOND
GROUP1 SEP1A /
GROUP2 SEP1B /
P* SEP1C /
/
12.18.142. SEPVALS 1504

In this example there are 3 separators. Well group GROUP1 uses the separator SEP1A,
well group GROUP2 uses the separator SEP1B, all wells which name begins with P uses the
separator SEP1C.
12.18.142. SEPVALS 1505

12.18.143 GSEPCOND


Section
This keyword assigns separators to well groups. Each separator should be specified earlier
via SEPVALS (see 12.18.142). If the separator corresponds to a group, all wells of this group
use this separator. If the separators conditions are altered by redefining them via SEPVALS
(see 12.18.142), then the oil and gas rates of these wells are transformed to reflect the
change in conditions.
The keyword can be followed by any number of data rows. Each row should be terminated
with a slash /. The data should be terminated with a final slash /.
group name (or a first part of name ending with an asterisk), or FIELD (if the separator
is at the field level);
name of the separator associated with this group;
(and its subordinate groups and wells).
In this example well group GROUP1 uses the separator SEP1A, well group GROUP2
uses the separator SEP1B, all wells which name begins with P uses the separator SEP1C.
12.18.143. GSEPCOND 1506

12.18.144 SEPCOND


Section
This keyword specifies separator conditions (the first usage of this keyword) or re-
specifies separator conditions (the nest usages of this keyword). The separator conditions
are associated with the well via the keyword WSEPCOND (see 12.18.145).
data lines.
be terminated with a final slash /..
1. separator name;
2. group name (for with this separator is used as default). If a well in this group has a
different separator (assigned via the keyword WSEPCOND (see 12.18.145), then it will
be used instead of group separator. Analogously if one group contains the subgroups
with default separator, then these subgroups will use its separator instead of group
separator;
3. stage number;
4. separator stage temperature (METRIC: C, FIELD: F);
gas plant table is not used and calculation of equation of state will be done.
12.18.144. SEPCOND 1507

Default:
group name (for with this separator is used as default) not specified.
stage number 1;
separator stage (for all stages except the last one), or the stock-tank (for the last stage);
Example
SEPCOND
S1 GROUP1 1 37.000 110.81469 3 2 /
S1 GROUP1 2 -25.000 49.03305 3 1* /
S1 GROUP1 3 -8.73 12.491 4 1* /
S1 GROUP1 4 20.000 1.01325 1* 1* /
/
In this example four-stage separator is specified. The wells from the group GROUP1 use
this separator S1 for defaults.
Liquid from the stage 1 goes to the stage 3. From the stage 2 to the stage 3, from the stage
3 to the stage 4, from the stage 4 to the stock-tank.
Gas from the stage 1 goes to the stage 2. From stages 2, 3, 4 to the stock-tank (for default).
12.18.144. SEPCOND 1508

12.18.145 WSEPCOND


Section
This keyword assigns separator to well. Separator name should be previously defines via
the keyword SEPCOND (see 12.18.144).
The keyword can be followed by any number of data rows. Each row should be termi-
nated with a slash /. The data should be terminated with a final slash /.
well name (or a first part of name ending with an asterisk), or well list specified via
WLIST (see 12.18.26);
name of the separator associated with this well (separator name should be previously
defines via SEPCOND (see 12.18.144)).
Example
WSEPCOND
719 S1 /
720 S1 /
721 S1 /
722 S1 /
540 S2 /
/
In this example wells 719, 720, 721, 722 use a separator S1, well 540 uses a separator
S2.
12.18.145. WSEPCOND 1509

12.18.146 WDFAC


Section
The keyword sets wells D-factor (flow-dependent skin for gas).

2. D-factor for this well (METRIC: day/sm3 , FIELD: day/Msc f ).
Default: D-factor = 0.
Wells D-factor can also be specified via the 12-th parameter of COMPDAT (see 12.18.6),
COMPDATL (see 12.18.7), COMPDATMD (see 12.18.10).
Connections D-factor is calculated from wells D-factor. Connections D-factor can be
entered directly via the 12-th parameter of COMPDAT (see 12.18.6), COMPDATL (see
12.18.7), COMPDATMD (see 12.18.10).
Example
WDFAC
W872 8.0E-6 /
W890 8.0E-6 /
W800 5.0E-6 /
W720 5.0E-6 /
/
In this example D-factor is specified for wells W872, W890 and W800, W720.
12.18.146. WDFAC 1510

12.18.147 WDFACCOR


Section
The keyword sets D-factor correlation (flow-dependent skin factor for gas).
2. coefficient A in D-factor formula below;
3. power B of permeability of grid block with connection in D-factor formula below;
4. power C of porosity of grid block with connection in D-factor formula below.
Default:
coefficient A in D-factor formula below 0;
power B of permeability of grid block with connection in D-factor formula below 0;
power C of porosity of grid block with connection in D-factor formula below 0.
D-factor correlation formula, the expression for non-Darcy flow (following Dake):
k 1 G
D = A kB C
h rw G
,
where
A, B, C are specified via this keyword;
k effective permeability of grid block with connection (For a vertical well this per-
meability is calculated as the geometric mean of the X and Y direction permeabilities);
porosity of grid block with connection;
h connection length;
rw wellbore radius;
12.18.147. WDFACCOR 1511

G relative density of gas (produced or injected) at surface conditions with respect

to air at standard temperature and pressure;
G gas viscosity at bottom hole pressure.
For a well connection D-factor is calculated based on the permeability and porosity of
the grid block with connection together with the fluid properties of the wellbore.
Wells D-factor can also be specified via the 12-th parameter of COMPDAT (see 12.18.6).
Connections D-factor is calculated from wells D-factor. Connections D-factor can be en-
tered directly via the 12-th parameter of COMPDAT (see 12.18.6).
Example
FIELD /
WDFACCOR
WELLPR1 4.48E-5 -1.018 0 /
/
In this example the coefficients for D-factor formula are set for the well WELLPR1.
12.18.147. WDFACCOR 1512

12.18.148 WTRACER


Section
The keyword sets the value of concentration of a tracer in the injection streams of its
associated phase. If the tracer isnt present in the list of tracer names in this keyword, con-
centration is assumed to be equal to 0.
The keyword is followed by any number of lines. Each line should be terminated with a
Each line consists of the following parameters:
1. well name (each well should be previously declared as injector) or well list WLIST
(see 12.18.26),
2. tracer name (specified via the keyword TRACER (see 12.7.1); in Eclipse tracer name
may consist of up to 3 characters, but in tNavigator tracer name may consist of any
number of characters),
3. value of the tracer concentration in the injection stream Tconc (a value from 0 to 1),
4. IGNORED. This is an Eclipse compatibility field

Value of the cumulative tracer factor Tcum . Using the cumulative tracer factor the tracer
concentration can be specified as a linear function of the total cumulative injection of
the well. If the cumulative tracer factor is specified, then the tracer concentration in the
injection stream is given by: Tc = MIN(CI Tcum , Tconc ), where CI - total cumulative
injection at the previous timestep,
5. IGNORED. This is an Eclipse compatibility fieldGroup name.
Example
WTRACER
302 'B' 1 /
303 'B' 1 /
304 'B' 1 /
305 'B' 1 /
/
In this example the concentration of tracer B is equal to 1 for four injectors: 302, 303,
304, 305.
12.18.148. WTRACER 1513

12.18.149 WSURFACT


Section
The keyword specifies the concentration of surfactant in the injection stream of injector.
Surfactants section 2.25.
The keyword can be followed by an arbitrary number of data lines. Each line should be
terminated with a slash /. All data should be terminated with a final slash /.
One data line consists of the following parameters:
1. well name (the well should be specified as injector) or well list WLIST (see 12.18.26),
2. concentration of surfactant in the injection stream (METRIC: kg/sm3 , FIELD: lb/stb).
Example
WSURFACT
'753R' 10 /
/
In this example the concentration of surfactant in the injection stream is 10 (kg/sm3 ) for
the injector 753R.
12.18.149. WSURFACT 1514

12.18.150 WALKALIN


Section
The keyword specifies the concentration of alkaline in the injection stream of injector.
Alkaline Flooding section 2.24.

2. concentration of alkaline in the injection stream (METRIC: kg/sm3 , FIELD: lb/stb).
Example
WALKALIN
'W75' 10 /
/
In this example the concentration of alkaline in the injection stream is 10 (kg/sm3 ) for
the injector W75.
12.18.150. WALKALIN 1515

12.18.151 WPOLYMER


Section
The keyword specifies the concentration of polymer in the injection stream of injector.
(Polymer Flood section 2.20).

2. concentration of polymer in the injection stream (METRIC: kg/sm3 , FIELD: lb/stb).
Example
WPOLYMER
'WPOL1' 0.1 /
/
In this example the concentration of polymer in the injection stream is 0.1 (kg/sm3 ) for
the injector WPOL1.
12.18.151. WPOLYMER 1516

12.18.152 WSALT


Section
The keyword is used to specify the concentration of salt in the injection stream of each
well. If the keyword WSALT doesnt appear, then concentration values of zero are assumed.
The keyword is followed by any number of data records. Each data record should termi-
nated with a slash /. All data should terminated with a final slash /.
Each data record should consist of the following parameters:
(see 12.18.26),
2. the concentration of salt in the injection stream of well (METRIC: kg/sm3 , FIELD:
lb/stb).
Example
WSALT
105 80/
126 80/
/
In this example the concentration of salt in the injection stream of wells 105, 126 is 80
kg/sm3 .
12.18.152. WSALT 1517

12.18.153 WTEMP


Section
The keyword specifies the temperature of injected water when temperature option is used
(2.30).
(see 12.18.26),
2. temperature of injected water (METRIC: C, FIELD: F).
Example
WTEMP
Well1 10/
Well2 10/
Well3 18/
Well4 18/
/
In this example the temperature of water injected by Well1 10 C, the temperature of

water injected by Well2 10 C, Well3 18 C, Well4 18 C.
12.18.153. WTEMP 1518

12.18.154 WHTEMP


Section
The keyword specifies the data for tubing head temperature calculations (THT) for pro-
ducers.
Each data record should consist of the following parameters (parameter 2 or 3 should be
specified: they cant be defined simultaneous):
1. well name (each well should be previously declared as producer) or well list WLIST
(see 12.18.26),
2. VFP table number (tables are specified via VFPPROD (see 12.18.57), VFPCORR
(see 12.18.61), the table should contains THT values. To provide well THT calculations
the well should have 2 tables: pressure VFP table and THT VFP table);
3. constant THT (METRIC: C, FIELD: F), IGNORED, this is an Eclipse compatibility

field.
Example
WHTEMP
Well1 2 /
Well2 1* 38 /
/
In this example for the Well1 the 2-nd VFP table is assigned, for the Well2 the constant
THT is specified 38 C.
12.18.154. WHTEMP 1519

12.18.155 WINJTEMP


Section
The keyword specifies the temperature of injected water when thermal option is used
THERMAL (see 12.1.50).
1. well name;
2. steam quality of the injected fluid (a value from 0 to 1).

If this value is specified, the temperature or the pressure should be specified, but not
the specific enthalpy rate;
3. temperature of the injected fluid (METRIC: C, FIELD: F).

If this value is specified, one should specify also the steam quality or the pressure, but
not the specific enthalpy rate;
4. pressure of the injected fluid (METRIC: barsa, FIELD: psia).

If this value is specified, one should also specify the steam quality, temperature, or
specific enthalpy rate (one of these parameters);
5. specific enthalpy of the injected fluid (METRIC: kJ/kg/Mol , FIELD: Btu/lb/Mol ).

If this value is specified, one shouldnt specify the steam quality or the temperature.
Example
WINJTEMP
INJ840 0.7 350/
INJ219 0.8 210/
/
12.18.155. WINJTEMP 1520

12.18.156 WINJWAT


Section
The keyword in an alias to the keyword WINJTEMP (see 12.18.155).
12.18.156. WINJWAT 1521

12.18.157 HEATER


Section
The keyword specifies the parameters of a heater when thermal option is used THERMAL
(see 12.1.50).
The description of heater simulation is in the section 4.31.
1. name of the heater;
2. I-coordinate of the heater connection (X-axis);
3. J-coordinate of the heater connection (Y-axis);
4. K-coordinate of the heater connection (Z-axis);
5. maximum heat injection rate, Hmax (METRIC: kJ/day, FIELD: Btu/day);
6. maximum temperature in the block where heater is connected, Tmax (METRIC: C ,

FIELD: F );
7. temperature-dependent heat injection rate (proportional heat transfer coefficient be-

tween heat rate and the difference between current block temperature and maximum
temperature) R (METRIC: kJ/day/K , FIELD: Btu/day/R ).
Example
HEATER
PROD1 1 1 1 7.0E10 170 /
PROD2 1 1 1 7.0E10 170 /
PROD3 1 1 1 7.0E10 170 /
PROD4 1 1 1 7.0E10 170 /
/
12.18.157. HEATER 1522

12.18.158 WTEST


Section
The keyword sets instructions for testing of closed wells.

2. interval for testing (day). The well will be tested at the first time step that starts after
this interval has expired since the well was closed. Next tests will be done at each time
step that starts after the specified interval has expired since the previous test;
3. closure reason, valid for testing (string). tNavigator supports the following reasons:
the string contains P.
The well will be tested if it was closed because of a physical reason (BHP or
THP limits). It will be opened if the test shows that it can operate again;
the string contains E.
The well will be tested if it was closed because of economic limits violation
(WECON (see 12.18.62), CECON (see 12.18.67), WECONINJ (see 12.18.68)).
If there is at least one open connection then the well is opened if all limits are
satisfied in WECON (see 12.18.62). (All closed connections will not be reopened.)
If the well doesnt have any open connections, then it should be closed according
to corresponding workover operation in case of limit violation in watercut, GOR
and WGR. In this case all closed connections will be tested individually.
Connection will be reopened in case if its watercut, GOR and WGR limits are
note violated (WECON (see 12.18.62) and CECON (see 12.18.67)). (Connection
that were closed manually are not tested). A well will be opened in case if at least
one of its connections is reopened.
the string contains G.
The well will be tested if it was closed because of GROUP or FIELD limits
violation in the keywords GECON (see 12.18.102) or GCON-. The well will
be opened unconditionally, because it cant be tested in isolation. In the case if
a group or field limit will be violated, then the workover action is performed
at the end of the timestep. If the well doesnt have open connections, then all
connections (closed due to automatic workovers) are reopened.
12.18.158. WTEST 1523

4. number of times the well can be tested. If the well was tested this number of times, it
is not tested any more (or WTEST should be used one more time). 0 the well can be
tested unlimited number of times;
5. start-up time time (days). At each time step after wells reopening, its efficiency
factor is multiplied by the value
T T0
time
T T0 < time; T time at the end of time step, T0 time when the well is reopened.
If the start-up time is larger then the time step size, the well is brought on gradually.
Default:
number of times the well can be tested 0;
start-up time 0.
Example
WTEST
Well1 120 P 20 10/
/
In this example for the well Well1 the following data is specified: interval for testing -
120 days, closure reason - P, number of times the well can be tested 20, start-up time - 10
days.
12.18.158. WTEST 1524

12.18.159 WELLSTRE


Section
The keyword specifies the composition of the injected stream (oil or gas). Well stream
can be used in the keyword WINJGAS (see 12.18.164), GINJGAS (see 12.18.165).
well stream name;
x1 -mole fraction of the 1-st component;
x2 -mole fraction of the 2-nd component;
...;
xNc mole fraction of the Nc component (Nc number of components in the run. The
sum of the mole fractions should be equal to 1).
Example
WELLSTRE
'stream1' 0.4 0.2 0.2 0.15 0.05/
'stream2' 0.4 0.1 0.5/
/
12.18.159. WELLSTRE 1525

12.18.160 COMPMOBI


Section
This keyword specifies the total voidage mobility for injector.

The total mobility is calculated via the formula:
krW krO krG
+ +
W O G
Injection volume is calculated as the product of a mass or energy density times the total
mobility times the connection factor times the drawdown.
2. i-coordinate of connecting grid block;
3. j-coordinate of connecting grid block;
4. k1-coordinate of upper connecting grid block;
5. k2-coordinate of lower connecting grid block;
6. total voidage mobility (METRIC: cP1 , FIELD: cP1 ).
Default:
i-coordinate of connecting grid block 0 (any value is allowed);
j-coordinate of connecting grid block 0 (any value is allowed);
k1-coordinate of upper connecting grid block 0 (any value is allowed);
k2-coordinate of lower connecting grid block 0 (any value is allowed);
total voidage mobility 1.0 cP1 .
12.18.160. COMPMOBI 1526

Example
COMPMOBI
I1 4* 10.0 /
I2 7 14 22 34 10.0 /
/
12.18.160. COMPMOBI 1527

12.18.161 COMPMBIL


Section
This keyword specifies the total voidage mobility for injector connections in local refined
grids (LGR).
The total mobility is calculated via the formula:
krW krO krG
+ +
W O G
Injection volume is calculated as the product of a mass or energy density times the total
mobility times the connection factor times the drawdown.

2. LGR name;
3. i-coordinate of connecting grid block;
4. j-coordinate of connecting grid block;
5. k1-coordinate of upper connecting grid block;
6. k2-coordinate of lower connecting grid block;
7. total voidage mobility (METRIC: cP1 , FIELD: cP1 ).

Default:
i-coordinate of connecting grid block 0 (any value is allowed);
j-coordinate of connecting grid block 0 (any value is allowed);
k1-coordinate of upper connecting grid block 0 (any value is allowed);
k2-coordinate of lower connecting grid block 0 (any value is allowed);
total voidage mobility 1.0 cP1 .
12.18.161. COMPMBIL 1528

Example
COMPMBIL
I1 LGR1 4* 10.0 /
I2 LGR4 7 14 22 34 10.0 /
/
12.18.161. COMPMBIL 1529

12.18.162 WINJMIX


Section
The keyword specifies the mixture composition of the injected stream. The contribution
of each fluid is specified as a fraction. Well stream can be used in the keyword WINJGAS
(see 12.18.164), GINJGAS (see 12.18.165) (parameter MIX).
1. mixture name;
2. mixture contribution index of the fluid defined below (integer number); calculation of
the injection mixture doesnt depend on the order of fluid specification;
3. fraction of this fluid in the mixture;
4. nature of injected gas:

STREAM molar composition of the injected fluid is defined via the keyword
WELLSTRE (see 12.18.159) (stream name should be entered via parameter 5 of
this keyword);
specified well (well name should be entered via parameter 5 of this keyword).
keyword:
if the 4-th parameter is STREAM, the stream name should be specified here;
if the 4-th parameter is GV, the group name should be specified here;
if the 4-th parameter is WV, the well name should be specified here.
6. stage of the separator which defines the fluid composition for injection. The vapor from
any stage can be used as a source of injection fluid.
12.18.162. WINJMIX 1530

Default:
Stage of the separator which defines the fluid composition for injection 0 (the vapor from
the whole separator is used as the injection fluid).
Example
WINJMIX
M1 1 0.5 GV GROUP1 /
M1 2 0.5 GV GROUP2 /
/
12.18.162. WINJMIX 1531

12.18.163 WINJORD


Section
The keyword defines composition of fluids for injection. It specifies fluids order. These
are taken in this order subject to their availability.

1. mixture name (maximum number of mixtures is set the keyword WELLDIMS (see
12.1.36));
2. mixture contribution index of the fluid defined below. The fluids will be taken in
increasing order of their contribution fraction (maximum number of mixture fluids is
set in the keyword WELLDIMS (see 12.1.36)).
3. The nature of fluid:
GAS the composition of the fluid is set to that of the field separator gas;
STREAM the molar composition of the fluid has been defined using the key-
word WELLSTRE (see 12.18.159). The name of the stream must be entered in
parameter 4;
GV The fluid is to be taken from the vapor production of a group, which name
must be entered in parameter 4;
WV The fluid is to be taken from the vapor production of a well, which name
must be entered in parameter 4.
Only the first two characters are significant.
4. the name of the wellstream, well or group (accordingly to value of the 3-rd parameter)
that defines the fluids composition. It is necessary if value of parameter 3 is not GAS;
5. stage of the separator that defines the fluid composition.
Default:
stage of the separator that defines the fluid composition: 0.
Example
WINJORD
IGAS 1 GV FIELD /
IGAS 2 ST A1GAS /
/
12.18.163. WINJORD 1532

In the example mixture IGAS consist of one part of vapor of reservoir (FIELD) and
two parts of A1GAS stream which composition defined by the keyword WELLSTRE (see
12.18.159).
12.18.163. WINJORD 1533

12.18.164 WINJGAS


Section
The keyword specifies the nature of injected gas. The keyword should be used in composi-
tional runs to specify data for injectors when the keyword WCONINJE (see 12.18.36) is used.

2. nature of injected gas (tNavigator supports the following options):
this keyword);
MIX the molar composition of injected fluid is specified as a mixture via WIN-
JMIX (see 12.18.162) (the name of the mixture should be specified via parameter
3 of this keyword);
GRUP injected fluid is specified for the superior group.
keyword:
if the 2-nd parameter is STREAM, the stream name should be specified here;
12.18.159)). Make up gas is used in case if there is no enough gas for injection from
the source specified via parameters 2 and 3;
12.18.164. WINJGAS 1534

Default:
nature of injected gas GRUP.
stage of the separator which defines the fluid composition for injection 0 (the vapor
from the whole separator as the injection fluid).
Example
WINJGAS
Well1 STREAM 'stream1'/
/
12.18.164. WINJGAS 1535

12.18.165 GINJGAS


Section
The keyword specifies the nature of injected gas for well groups. The keyword should be
used in compositional runs to specify data for injectors when the keyword GCONINJE (see
12.18.81) is used.
1. group name or group name root ending with ;
2. nature of injected gas (tNavigator supports the following options):

this keyword);
MIX the molar composition of injected fluid is specified as a mixture via WIN-
JMIX (see 12.18.162) (the name of the mixture should be specified via parameter
3 of this keyword);
GRUP injected fluid is specified for the superior group.
keyword:
if the 2-nd parameter is STREAM, the stream name should be specified here;
12.18.165. GINJGAS 1536


12.18.159)). Make up gas is used in case if there is no enough gas for injection from
the source specified via parameters 2 and 3;
Default:
nature of injected gas GRUP.
stage of the separator which defines the fluid composition for injection 0 (the vapor
from the whole separator as the injection fluid).
Example
GINJGAS
G1 STREAM 'stream1'/
G2 GV GROUP1 /
'GINJ3*' GAS /
/
In this example for the group G1 the stream name stream1 is specified; for the group G2
injected gas composition corresponds to gas composition, produced by group GROUP1; for
the groups that names begin with GINJ3 gas composition corresponds to the field separator
gas composition.
12.18.165. GINJGAS 1537

12.18.166 GADVANCE


Section
The keyword specifies a supply of advance import gas to a group that provides gas for
reinjection (GINJGAS (see 12.18.165)).
First, the advance import gas for this group is used for re-injection. Second, the gas
produced by this group is used for re-injection. If the quantity of import gas is enough for
re-injection, then the produced gas is not used (it is available for fuel or sale).
1. group name or group name root ending with ;
2. name of the well stream, that specifies the molar composition of the imported gas (well
streams are defined via WELLSTRE (see 12.18.159));
3. maximum rate at which advance gas can be supplied (METRIC: sm3 /day, FIELD:
Msc f /day).
Example
GADVANCE
GROUP1 STREAM2 1000000 /
GROUP2 STREAM1 2000000 /
/
12.18.166. GADVANCE 1538

12.18.167 GRUPSALE


Section
This keyword specifies the group gas sales rate (the volume of gas available for re-
injection is reduced by this amount).
Gas available for re-injection.

The available for re-injection gas of a group is equal to the groups gas production rate minus
its fuel rate (GRUPFUEL (see 12.18.169)) minus its sales rate (GRUPSALE (see 12.18.167)).
The keyword GRUPSALE is followed by any number of data records. Each data record
should terminated with a slash /. All data should terminated with a final slash /.
1. group name or name root or FIELD;
2. constant gas sales rate (METRIC: sm3 /day, FIELD: Msc f /day);
3. fractional gas sales rate;
4. each component fraction to sale.
Default:
constant gas sales rate 0 (METRIC: sm3 /day, FIELD: Msc f /day);
fractional gas sales rate 0;
each component fraction to sale: 1 for each component.
Example
GRUPSALE
GROUP1 42500 /
GROUP2 34000 /
GROUP3 67000 /
/
In this example constant gas sales rate is specified for three groups.
12.18.167. GRUPSALE 1539

12.18.168 GCONSALE


Section
The keyword sets value of gas rate for sale. To calculate gas injection rate gas rate for
sale will be subtracted from total gas production rate. Each line should be ended by a symbol
1. group name or a mask of group name;
2. value of gas rate for sale (METRIC: sm3 /day, FIELD: Msc f /day). It could be defined
by the keyword UDQ (see 12.18.138).
3. maximum permitted sales gas production rate (METRIC: sm3 /day, FIELD:
Msc f /day). The value should be greater than the value specified in parameter 2.
In the case if the maximum rate is exceeded at the end of the timestep the action,
specified via 5-th parameter, will be made.
4. minimum permitted sales gas production rate (METRIC: sm3 /day, FIELD:
Msc f /day). The value should be less than the value specified in parameter 2.
In the case if the gas rate falls below the minimum then at the end of the timestep the
following actions will be made:
If the group is limited by a maximum gas production rate then its gas rate limit
will be increased by the amount necessary to reach the sales gas target.
Open the next producer in the drilling queue. This producer should be subordinate
to the group needing more sales gas, and not subordinate to a group under gas
rate control or a prioritization group.
5. procedure on exceeding a maximum rate limit (specified via parameter 3):
NONE do nothing,
CON shut worst-offending connection in worst-offending well,
CON+ shut worst-offending connection and all connections below it in worst-
offending well,
+CON analogue of CON+,
WELL shut or stop the worst-offending well (parameter 9 WELSPECS (see
12.18.3)),
12.18.168. GCONSALE 1540

RATE groups gas production rate target will be reduced to a value that meets
the sales gas target after allowing for any consumption and the current rate of
reinjection. The group will be put on gas production rate control,
MAXR acts the same as RATE, but maximizes the future production rate by
setting the reinjection fraction limit to 1. If the injection capacity subsequently
increases then the gas production target increases correspondingly.
We consider the well (or connection) as the worst-offending if it has the highest ratio
of gas to the wells preferred phase (parameter 6 WELSPECS (see 12.18.3)).
Default:
maximum permitted sales gas production rate no limit;
minimum permitted sales gas production rate 0;
procedure on exceeding a maximum rate limit (specified via parameter 3) NONE.
Example
GCONSALE
FIELD 50000 /
/
Value of gas rate of a field for sale is 50000 Msc f /day.
12.18.168. GCONSALE 1541

12.18.169 GRUPFUEL


Section
This keyword specifies the group gas fuel rate (the volume of gas available for re-injection
is reduced by this amount).
Gas available for re-injection.

The available for re-injection gas of a group is equal to the groups gas production rate minus
its fuel rate (GRUPFUEL (see 12.18.169)) minus its sales rate (GRUPSALE (see 12.18.167)).
The keyword GRUPFUEL is followed by any number of data records. Each data record
should terminated with a slash /. All data should terminated with a final slash /.
1. group name or name root or FIELD;
2. constant gas fuel usage rate (METRIC: sm3 /day, FIELD: Msc f /day);
3. fractional gas fuel usage rate;
4. each component fraction to use as fuel.
Default:
constant gas fuel usage rate 0 (METRIC: sm3 /day, FIELD: Msc f /day);
fractional gas fuel usage rate 0;
each component fraction to use as fuel: 1 for each component.
Example
GRUPFUEL
GROUP1 42500 /
GROUP2 34000 /
GROUP3 67000 /
/
In this example constant gas fuel usage rate is specified for three groups.
12.18.169. GRUPFUEL 1542

12.18.170 WTAKEGAS


Section
This keyword defines the order in which fuel, sales and reinjection gas are takes from
production gas steam (fuel gas GRUPFUEL (see 12.18.169), sales GRUPSALE, reinjec-
tion GCONINJE (see 12.18.81)). One values are below. The data should be terminated with
a slash /.
Possible order:
FRS Fuel, then Reinjection, then Sales;
FSR Fuel, then Sales, then Reinjection;
RFS Reinjection, then Fuel, then Sales;
RSF Reinjection, then Sales, then Fuel;
SFR Sales, then Fuel, then Reinjection;
SRF Sales, then Reinjection, then Fuel.
Default: FSR.
Example
WTAKEGAS SRF /
12.18.170. WTAKEGAS 1543

12.18.171 WAVAILIM


Section
This keyword sets that the availability of injection fluids can be taken into account in
injection rate calculations. This keyword doesnt have any parameters.
In case if the injection rate target is greater than the amount of injection fluid from
the production system that is available for the injector then the injector stays onto fluid
availability control.
The source of injection stream is group or well (keywords GINJGAS (see 12.18.165),
WINJGAS (see 12.18.164) or WELLINJE (see 12.18.40), parameter 2 is GV or WV).
In case if the injection target is greater then the available gas from this source, then the
injection controls depends on this keyword WAVAILIM. If the keyword is not specified
then injecting more gas than is available takes place and it can result to a negative gas
rate. If the keyword is specified, then the injection rate is limited by the amount of
available gas for injection.
If the source of injection stream is a group then the gas available for injection is
produced gas, minus fuel (GRUPFUEL (see 12.18.169)) and sales gas (GRUPSALE)
(unless other conditions are specified in WTAKEGAS (see 12.18.170)), plus advance
gas rate specified via GADVANCE (see 12.18.166).
If the source of injection stream is a well then the gas available for injection is its
produced gas.
12.18.171. WAVAILIM 1544

12.18.172 SWINGFAC


Section
The keyword activates the Gas Field Model section 2.19.7.

The swing and profile factors for FIELD are entered (seasonality profile).
One should specify an annual profile monthly multipliers to the mean rate or DCQ
(Daily Contracted Quantity). For each month: target gas production rate for FIELD is equal
to the DCQ multiplied by the months profile factor.
The keywords GASYEAR (see 12.18.175) and GASPERIO (see 12.18.176) sets contract
periods. These keywords should be used instead of DATES (see 12.18.105), TSTEP (see
12.18.106). Swing and profile factors, specified via this keyword are used to define field
target gas rate and to adjust the DCQ.
If there are several contract groups that have its own seasonality profiles (not only one
FIELD), then the keyword GSWINGF (see 12.18.173) should be used instead of SWING-
FAC.
The keyword GASFIELD (see 12.1.90) sets if multiple contract groups are required.
The keyword should be followed by 24 numbers (The data should be terminated with a
slash /.):
the first 12 numbers swing factors for each month from January to December.
next 12 numbers profile factors for each month from January to December.
It is not recommended to set for one month profile factor greater than swing factor.
The normalization condition should be performed for profile factors.

Annual Contracted Quantity ACQ = 365, 25 DCQ
where DCQ Daily Contracted Quantity for gas. 365,25 the average number of days in a
year, with a leap year every fourth year.
The normalization condition for profile factors:

12
(Coe f fi Daysi) = 365, 25
i=1
where:
12.18.172. SWINGFAC 1545

i number of the month;
Coe f fi profile factor for the month number i;
Daysi the number of days in a month i (28,25 days in February).
In this case the Annual Contracted Quantity ACQ for constant DCQ will be calculated
according to the formula above.
Example
SWINGFAC
2*2.0036 3*1.5024 3*1.0012 3*1.5024 2.0036
2*1.6036 3*1.0000 2*0.4080 0.4077 3*1.0000 1.6036
/
12.18.172. SWINGFAC 1546

12.18.173 GSWINGF


Section
The keyword activates the Gas Field Model section 2.19.7.

The swing and profile factors for contract groups are entered (seasonality profile).
If one contract group FIELD is used than the keyword SWINGFAC (see 12.18.172)
should be used instead of this keyword.
When GSWINGF is used each contract group can have its own set of swing and profile
coefficients and its own DCQ will be calculated.
One specifies an annual profile monthly multipliers to the mean rate or DCQ (Daily
Contracted Quantity). For each month: target gas production rate for contract group is equal
to the DCQ multiplied by the months profile factor.
The keywords GASYEAR (see 12.18.175) and GASPERIO (see 12.18.176) sets contract
periods. These keywords should be used instead of DATES (see 12.18.105), TSTEP (see
12.18.106). Swing and profile factors, specified via this keyword are used to define target
gas rates and to adjust the DCQ.
The keyword should be followed by 25 numbers (the data for each group should be
terminated with a slash /):
name or name root of the contract group;
the first 12 numbers swing factors for each month from January to December.
next 12 numbers profile factors for each month from January to December.
It is not recommended to set for one month profile factor greater than swing factor.
The normalization condition should be performed for profile factors.

Annual Contracted Quantity ACQ = 365, 25 DCQ
where DCQ Daily Contracted Quantity for gas. 365,25 the average number of days in a
year, with a leap year every fourth year.
The normalization condition for profile factors:

12
(Coe f fi Daysi) = 365, 25
i=1
where:
12.18.173. GSWINGF 1547

i number of the month;
Coe f fi profile factor for the month number i;
Daysi the number of days in a month i (28,25 days in February).
In this case the Annual Contracted Quantity ACQ for constant DCQ will be calculated
according to the formula above.
Example
GSWINGF
G1 2*2.0036 3*1.5024 3*1.0012 3*1.5024 2.0036
2*1.6036 3*1.0000 2*0.4080 0.4077 3*1.0000 1.6036 /
G2 2*2.0000 3*1.5000 3*1.0000 1.2000 3*1.5000 2.0000
2*1.6036 3*1.0000 2*0.4080 0.4077 3*1.0000 1.6036 /
G3 2*2.0036 3*1.5024 3*1.0012 3*1.5024 2.0036
2*1.4036 3*1.1000 2*0.4052 0.4051 3*1.1000 1.4036 /
12.18.173. GSWINGF 1548

12.18.174 GDCQ


Section
The keyword sets initial DCQ for each contract group (Gas Daily Contracted Quantity.
The keyword is used in the Gas Field Model section 2.19.7.
Contract groups are defined via GSWINGF (see 12.18.173); each contract group has its
name, swing and profile factors. The keywords GASYEAR (see 12.18.175) and GASPERIO
(see 12.18.176) sets contract periods. These keywords should be used instead of DATES (see
12.18.105), TSTEP (see 12.18.106).
Initial DCQ value can be reset at any time by further use of QDCQ.
An arbitrary number of lines can be entered, each line should be terminated with a slash
/. All the data should be terminated with a final slash /.
2. initial DCQ of the group (METRIC: sm3 /day, FIELD: Msc f /day);
3. is the groups DCQ variable or fixed?
VAR group DCQ is reduced to obey the swing requirement, that is specified
by parameter 3 of the keyword GASYEAR (see 12.18.175) (or parameter 4 of
GASPERIO (see 12.18.176)). If there are several contract groups VAR, then only
the options YEAR or PER and NO can be used. For automatic DCQ reduction
the options YEAR or PER can be used.
FIX1 DCQ of the group remains equal to the value of parameter 2 (also in the
case if the group cant meet its target rate). At the first pass of each contract
period the groups target rate is equal to DCQ, multiplied by a swing factor. If in
the keyword GASYEAR (see 12.18.175) parameter 3 is (or parameter 4 in the
keyword GASPERIO (see 12.18.176)) PRO, then groups target rate is equal to
DCQ, multiplied by a profile factor. At the second pass of each contract period
the groups target rate is equal to DCQ, multiplied by a profile factor;
FIX2 the calculation is the same of for FIX1. The difference is the following: at
delivery capacities calculation the maximum gas production rate is equal to DCQ,
multiplied by a swing factor.
12.18.174. GDCQ 1549

Default:
initial DCQ of the group the groups current DCQ;
is the groups DCQ variable or fixed? VAR.
Example
GDCQECON
G1 78000 VAR /
G2 45000 FIX1 /
G2 50000 FIX1 /
/
12.18.174. GDCQ 1550

12.18.175 GASYEAR


Section
This keyword sets the contract years (advances simulation over the specified number of
years). The data should be terminated with a slash /.
GASPERIO (see 12.18.176) should be used instead of GASYEAR (see 12.18.175) if the
length of the contract period is less than a year (These keywords should be used instead of
DATES (see 12.18.105), TSTEP (see 12.18.106)).
The keyword is used in the Gas Field Model section 2.19.7. Seasonality profile is
calculated according to the profile coefficients specified via SWINGFAC (see 12.18.172) (or
GSWINGF (see 12.18.173), if there are several contract groups). DCQ (Daily Contracted
Quantity) is automatically reduced to obey the required swing factors, specified via SWING-
FAC (see 12.18.172) (or GSWINGF (see 12.18.173), if there are several contract groups).
1. number of contract years to simulate (the contracts year begins when the keyword
GASYEAR (see 12.18.175) is specified);
2. initial DCQ for FIELD (METRIC: sm3 /day, FIELD: Msc f /day).
If there is only one gas supply contract, then this parameter should be defaulted in the
next entries of this keyword.
If there are several contract groups then this parameter should be defaulted and initial
DCQ for groups should be specified via GDCQ (see 12.18.174);
3. swing requirement for automatic reduction of the DCQ:
YEAR or YES. The group must be able to work for the whole contract year at the
DCQ, multiplied by the swing factor.
PRO. The group must be able to increase the production rate at any time of
the contract year from the DCQ, multiplied by the profile factor, to the DCQ,
multiplied by the swing factor.
ACQ. The group must be able to work at the DCQ, multiplied by the swing factor
until it has produced its annual contracted quantity ACQ (ACQ = 365, 25 DCQ).
JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC, and JLY
(the same for JUL).
The group must be able to work at the DCQ, multiplied by the swing factor until
12.18.175. GASYEAR 1551

it has produced a fraction of its annual contracted quantity ACQ proportional to

the sum of profile factors up to the end of the specified month.
NO. There are no swing requirements. DCQ remains equal the current value, also
in the case if the group cant meet its target rate. Parameters 5-8 are ignored in
this case.
For all the options (except for NO), each contract year is simulated two times. The
first pass the calculation to decide how much the DCQ should be reduced to obey
the swing requirement for the current contract year. The second pass calculation of
the actual performance of the field: the sales gas rate target at each month is equal to
the new value of DCQ multiplied by the monthly profile factor.
If the are several contract groups with varying DCQ (parameter VAR in the keyword
GDCQ (see 12.18.174)), then one can use only options YEAR or NO.
4. flag that specifies if the timesteps should be limited so that each month starts with a
new timestep? In tNavigator always YES.
5. limiting DCQ reduction factor allowed in a single iteration of the first pass of the
contract year (a value from 0 to 0.99).
The nearer the reduction factor is to 1 the more accurate will be the result, but the
more iterations of the first pass will be necessary.
If DCQ should be reduced to a fraction less than the specified value, then it will be
reduced only for this value (DCQ, multiplied by limiting DCQ reduction factor), the
first pass of the contract year is calculated one more time (the maximum number of
iterations is specified in parameter 7);
6. anticipated annual DCQ reduction factor (a number from 0.01 to 1).

When DCQ was reduced automatically below the specified initial value, the DCQ is
multiplied by the anticipated reduction factor at the beginning of each contract year.
This factor can help to reduce the number of iterations of the first pass due to bringing
the starting value nearer to the final value.
If during the first pass it is calculated that DCQ should be reduced to the value of
DCQnew , then this value is used in the second pass.
If the anticipated annual DCQ reduction factor was specified, then the calculation of
the next year is specified with initial DCQ, multiplied by this anticipated annual DCQ
reduction factor;
7. maximum allowed number of iterations of the first pass of each contract year to
calculate the DCQ;
8. convergence tolerance for the calculation DCQ when using the accelerated iteration.
IGNORED. This is an Eclipse compatibility field. tNavigator doesnt use tNavigator
the accelerated iteration scheme.
Default:
12.18.175. GASYEAR 1552

initial DCQ for FIELD current value of DCQ;
swing requirement for automatic reduction of the DCQ YEAR;
flag that specifies if the timesteps should be limited so that each month starts with a
new timestep? YES;
limiting DCQ reduction factor 0, unlimited DCQ reduction is allowed;
anticipated annual DCQ reduction factor 1 (the reduction is not anticipated);
maximum allowed number of iterations of the first pass of each contract year to
calculate the DCQ 3.
Example
GASYEAR
2 150000 MAR /
/
GASYEAR
20 1* MAR /
/
12.18.175. GASYEAR 1553

12.18.176 GASPERIO


Section
This keyword sets the contract periods (advances simulation over the specified number of
periods). The data should be terminated with a slash /.
GASPERIO (see 12.18.176) should be used instead of GASYEAR (see 12.18.175) if the
length of the contract period is less than a year (These keywords should be used instead of
DATES (see 12.18.105), TSTEP (see 12.18.106)).
The contract period the time over which the DCQ remains fixed. The contract period
can be equal to any number of months that is a factor of 12 (1, 2, 3, 4 or 6).
The keyword is used in the Gas Field Model section 2.19.7. Seasonality profile is
calculated according to the profile coefficients specified via SWINGFAC (see 12.18.172) (or
GSWINGF (see 12.18.173), if there are several contract groups). DCQ (Daily Contracted
Quantity) is automatically reduced to obey the required swing factors, specified via SWING-
FAC (see 12.18.172) (or GSWINGF (see 12.18.173), if there are several contract groups).
1. number of contract periods to simulate (the contract period begins when the keyword
GASPERIO (see 12.18.176) is specified);
2. number of months in a contract period (1, 2, 3, 4, 6 or 12);
3. initial DCQ for FIELD (METRIC: sm3 /day, FIELD: Msc f /day).
If there is only one gas supply contract, then this parameter should be defaulted in the
next entries of this keyword.
If there are several contract groups then this parameter should be defaulted and initial
DCQ for groups should be specified via GDCQ (see 12.18.174);
4. swing requirement for automatic reduction of the DCQ:
PER or YES. The group must be able to work for the whole contract period at the
DCQ, multiplied by the swing factor.
PRO. The group must be able to increase the production rate at any time of
the contract period from the DCQ, multiplied by the profile factor, to the DCQ,
multiplied by the swing factor.
12.18.176. GASPERIO 1554

PCQ. The group must be able to work at the DCQ, multiplied by the swing factor
until it has produced its contracted gas quantity (DCQ, multiplied by the number
of days in the period).
NO. There are no swing requirements. DCQ remains equal the current value, also
in the case if the group cant meet its target rate. Parameters 5-8 are ignored in
this case.
For all the options (except for NO), each contract period is simulated two times. The
first pass the calculation to decide how much the DCQ should be reduced to obey
the swing requirement for the current contract period. The second pass calculation
of the actual performance of the field: the sales gas rate target at each month is equal
to the new value of DCQ multiplied by the monthly profile factor.
If the are several contract groups with varying DCQ (parameter VAR in the keyword
GDCQ (see 12.18.174)), then one can use only options PER or NO.
5. flag that specifies if the timesteps should be limited so that each month starts with a
new timestep? In tNavigator always YES.
6. limiting DCQ reduction factor allowed in a single iteration of the first pass of the
contract year (a value from 0 to 0.99).
The nearer the reduction factor is to 1 the more accurate will be the result, but the
more iterations of the first pass will be necessary.
If DCQ should be reduced to a fraction less than the specified value, then it will be
reduced only for this value (DCQ, multiplied by limiting DCQ reduction factor), the
first pass of the contract year is calculated one more time (the maximum number of
iterations is specified in parameter 7);
7. anticipated annual DCQ reduction factor (a number from 0.01 to 1).

When DCQ was reduced automatically below the specified initial value, the DCQ is
multiplied by the anticipated reduction factor at the beginning of each contract year.
This factor can help to reduce the number of iterations of the first pass due to bringing
the starting value nearer to the final value.
If during the first pass it is calculated that DCQ should be reduced to the value of
DCQnew , then this value is used in the second pass.
If the anticipated annual DCQ reduction factor was specified, then the calculation of
the next year is specified with initial DCQ, multiplied by this anticipated annual DCQ
reduction factor;
8. maximum allowed number of iterations of the first pass of each contract year to
calculate the DCQ;
9. convergence tolerance for the calculation DCQ when using the accelerated iteration.
IGNORED. This is an Eclipse compatibility field. tNavigator doesnt use tNavigator
the accelerated iteration scheme.
Default:
12.18.176. GASPERIO 1555

number of months in a contract period 12;
initial DCQ current value of DCQ;
swing requirement for automatic reduction of the DCQ YEAR;
flag that specifies if the timesteps should be limited so that each month starts with a
new timestep? YES;
limiting DCQ reduction factor 0, unlimited DCQ reduction is allowed;
anticipated annual DCQ reduction factor 1 (the reduction is not anticipated);
maximum allowed number of iterations of the first pass of each contract year to
calculate the DCQ 3.
Example
GASPERIO
3 4 150000 PER /
/
12.18.176. GASPERIO 1556

12.18.177 DCQDEFN


Section
This keyword defines whether the DCQ targets set in keywords GASYEAR (see
12.18.175), GASPERIO (see 12.18.176) or GDCQ (see 12.18.174) correspond to energy
or gas production rate. In tNavigator always gas production rate.
1. GAS DCQ corresponds to gas production rate.
Example
DCQDEFN
GAS /
12.18.177. DCQDEFN 1557

12.18.178 GDCQECON


Section
This keyword sets the minimum economic DCQ limit for contract . The keyword is used
in the Gas Field Model section 2.19.7.
If DCQ falls below the specified value for the group then all producers in this group will
be shut or stopped (corresponding to the 9-th parameter of the keyword WELSPECS (see
12.18.3)). If the contract group is FIELD, then the calculation will be terminated.
An arbitrary number of lines can be entered, each line should be terminated with a slash
/. All the data should be terminated with a final slash /.
2. minimum economic DCQ value (METRIC: sm3 /day, FIELD: Msc f /day).
Default: minimum economic DCQ value 0 (no limit).
Example
GDCQECON
G1 38000 /
G2 45000 /
/
12.18.178. GDCQECON 1558

12.18.179 GASBEGIN


Section
This keyword starts the set of keywords that specify well operations and reports during
the contract period.
After this keyword the keyword that are listed below can go, they should be terminated with
GASEND (see 12.18.180). Time in the contract period (between GASBEGIN (see 12.18.179)
and GASEND (see 12.18.180)) when the operation should take place are specified via GAS-
MONTH (see 12.18.181).
Creation of Annual Scheduling File.

The keywords GASYEAR (see 12.18.175) and GASPERIO (see 12.18.176) advance the
simulation for one or more contract years or contract periods. Well operation at the end of
the contract period can be performed in the usual way. To perform well operations or to make
a report during the contract period the Annual Scheduling File should be created.
All the required operations should be between the keywords GASBEGIN (see 12.18.179)
and GASEND (see 12.18.180) before the keywords GASYEAR (see 12.18.175) and GASPE-
RIO (see 12.18.176). The data between GASBEGIN (see 12.18.179) and GASEND (see
12.18.180) is read but not performed until the keywords GASYEAR (see 12.18.175) or
GASPERIO (see 12.18.176) are used.
If the Annual Scheduling File doesnt change then it can be specified only once. An-
nual Scheduling File will be automatically performed from its beginning when any new
GASYEAR (see 12.18.175) or GASPERIO (see 12.18.176) is read. If the Annual Schedul-
ing File is varied then a new File should be specified at the beginning of the contract year
via GASBEGIN (see 12.18.179) and GASEND (see 12.18.180).
To specify an empty Annual Scheduling File (no well operations and reports during the
contract period) you should specify GASBEGIN (see 12.18.179), and immediately after it
GASEND (see 12.18.180).
Possible keywords for Annual Scheduling File creation:
BRANPROP (see 12.18.87);
GASMONTH (see 12.18.181);
GCONPRI (see 12.18.75);
12.18.179. GASBEGIN 1559

GCONPROD (see 12.18.72);
GCONSUMP (see 12.18.82);
GRUPNET (see 12.18.96);
GRUPTARG (see 12.18.54);
GRUPTREE (see 12.18.85);
GSATINJE (see 12.18.84);
GSATPROD (see 12.18.83);
NODEPROP (see 12.18.88);
RPTSCHED;
WEFAC (see 12.18.69);
WELOPEN (see 12.18.107);
WELTARG (see 12.18.51);
WGRUPCON (see 12.18.80).
12.18.179. GASBEGIN 1560

12.18.180 GASEND


Section
This keyword ends the set of keywords that specify well operations and reports during
the contract period after the keyword GASBEGIN (see 12.18.179).
well operations and reports during the contract period are specified between GASBEGIN
(see 12.18.179) and GASEND (see 12.18.180). Time in the contract period (between GAS-
BEGIN (see 12.18.179) and GASEND (see 12.18.180)) when the operation should take place
are specified via GASMONTH (see 12.18.181).
12.18.180. GASEND 1561

12.18.181 GASMONTH


Section
This keyword specifies a month when in Annual Scheduling File creation the well oper-
ations will be performed or reports will be written.
Time moments in the contract period are specified between the keywords GASBEGIN
(see 12.18.179) and GASEND (see 12.18.180)).
/.):
1. month. One of the following names: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG,
SEP, OCT, NOV, DEC, and JLY, is the same with JUL;
2. write a report: YES (or Y), NO (or N).
Example
GASMONTH
SEP YES /
...KEYWORDS...
In this example we specify the report at the end of a time step, ending the 1-st September.
We can also specify the well operations to be performed the 1-st September.
12.18.181. GASMONTH 1562

12.18.182 WGASPROD


Section
This keyword can be used to declare several production wells to be such gas producers,
that its opening from the drilling queue has higher priority than others one when the sales
gas production rate falls below the minimum limit (keyword GCONSALE (see 12.18.168)).
Initially the wells must be declared as shut producers (keyword WCONPROD (see
12.18.34)), and placed in the drilling queue (keyword QDRILL (see 12.18.203)).
The wells should be placed under GRAT control (GRAT value is set by 6-th parameter of
the keyword WCONPROD (see 12.18.34)). This gas rate value is overridden when the wells
are opened from the drilling queue, as their gas rate targets are set automatically at multiples
of the incremental rate set in parameter 2 below.
The purpose of such producers is to ensure sufficient gas to meet sales gas requirements
independently of any oil production target value. These producers are opened from the drilling
queue only when the sales gas rate has fallen below the minimum requirement. Group and
oil rate limits are ignored by these wells.
1. well name, well name mask, well list or well list mask;
2. gas rate value (METRIC: sm3 /day, FIELD: msc f /day). The wells target gas produc-
tion rate is increased by this amount;
3. Maximum permitted number of applying operation from parameter 2.
Example
WGASPROD
WGAS1 3000 4 /
/
In the example gas limit value of well WGAS1 can be increased by 3000 msc f /day not
greater than 4 times.
12.18.182. WGASPROD 1563

12.18.183 GASFTARG


Section

It sets monthly gas rate values which are the field to be produced in the second pass of
the gas field operations model.
1. 12 gas rate values which corresponds to each month of one calendar year (METRIC:
sm3/day, FIELD: Msc f /day).
For months in which a rate is specified the field is produced at the lesser of DCQ
PROFILE and the specified rate. For months in which values are defaulted the field is
produced at DCQ PROFILE . DCQ is Daily Contracted Quantity, PROFILE multipliers
for gas rates (the keyword SWINGFAC (see 12.18.172)).
The GASFTARG (see 12.18.183) keyword can also be used in conjunction with the
GASFDECR (see 12.18.184) keyword.
Example
GASFTARG
2*20000.0 3* 2*50000.0 3* 2*20000.0 /
In the example monthly gas rate values which are the field to be produced if they are
lesser than DCQ PROFILE value. These values are specified for January, February (20000
Msc f /day), June, July (50000 Msc f /day) and November and December (20000 Msc f /day).
For the others months values are defaulted.
12.18.183. GASFTARG 1564

12.18.184 GASFDECR


Section

It specifies values of decrement for contract gas rate which the field produced for the
second pass of the gas field operations model. So, value of producing gas rate is
DCQ PROFILE DEC.
DCQ Daily Contracted Quantity, PROFILE multipliers for gas rates (the keyword
SWINGFAC (see 12.18.172)), DEC decrement value which is set there.
This keyword can be used in conjunction with the keyword GASFTARG (see 12.18.183).
In this case field is to be produced lesser of DCQ PROFILE DEC and specified in GAS-
FTARG (see 12.18.183) gas rate value.
1. 12 decrement values which corresponds to each month of one calendar year (METRIC:
sm3/day, FIELD: Msc f /day).
Default:
decrement value: 0.
Example
GASFDECR
2*500.0 3* 2*500.0 2* 3*1000.0 /
In the example decrement values are specified for each month. For January, February,
June and July they are equal to 500 Msc f /day, for October, November and December they
are equal to 1000 Msc f /day. For the others months these values are defaulted and equal to
0.
12.18.184. GASFDECR 1565

12.18.185 GASFCOMP


Section

The keyword sets compressors for models with option of standard network (see section
2.19.9). For each network branch only one compressor can be set.
Compressors are activated when the field doesnt achieve target gas rate value. If this
value is decreased, then compressors would be disactivated it is necessary to see if the field
can meet it without them. The automatic compressors are also turned on while calculating
the fields maximal production.
Each data line should contain the following parameters:
1. well group name or mask, which defines a subset of well groups;
2. number of VFP table, which is used when the compressor is operating (see the keyword
3. artificial lift quantity (ALQ) which is used when the compressor is operating. Units
depend on what the ALQ was meant to represent when the VFP table was created (see
the keyword VFPPROD (see 12.18.57)).
Each data line should be ended by the symbol /. The data should be terminated with a
slash /.
Default:
number of VFP table: 0 (i.e. the same which is used in the keyword GRUPNET (see
12.18.96));
Example
GASFCOMP
'PLAT-*' 1* 50 /
/
In the example for groups which name starts from PLAT- compressor properties are set:
number of VFP table is taken from the keyword GRUPNET (see 12.18.96), ALQ is 50.
12.18.185. GASFCOMP 1566

12.18.186 WVFPDP


Section
The keyword specifies a pressure adjustment. The adjustment is added to the value of the
well BHP obtained by interpolating the VFP tables. (Could be used for matching a wells
flow rate at a given THP, by adjusting the effective pressure loss between the bottom hole
and the tubing head. A positive pressure adjustment (for production well) increases BHP and
decreases a wells production. Negative adjustment improves wells production).
The third parameter of the keyword is a tubing pressure loss scaling factor. Wells BHP
obtained from the VFP table adjusts by multiplying the tubing pressure loss (BHP-THP) by
this factor. For production well a scaling factor, greater than 1, increases BHP and decreases
a wells production.
The keyword is followed by any number of lines. Each line should be terminated with a
Each line consists of the following parameters:

1. well name or well list WLIST (see 12.18.26),
2. pressure adjustment (METRIC: bars, FIELD: psi),
3. tubing pressure loss scaling factor f p . Wells BHP will be adjusted to BHP1: BHP1 =
T HP + f p (BHPtab T HP).
Default:
pressure adjustment 0,
tubing pressure loss scaling factor f p 1.
Independently of the use of this keyword, wells BHP is automatically adjusted to take
account of any difference between its BHP reference depth (5-th parameter of WELSPECS
(see 12.18.3)) and reference depth of VFP-table (VFPPROD (see 12.18.57)), by adding or
subtracting a hydrostatic pressure correction based on the density of the fluid in the well
bore.
Example
WVFPDP
302 2.5 /
303 -11.2 /
304 2 1.21 /
/
12.18.186. WVFPDP 1567

In this example pressure adjustment is specified for wells 302, 303; for the well 304 both
pressure adjustment and tubing pressure loss scaling factor is specified.
12.18.186. WVFPDP 1568

12.18.187 PICOND


Section
The keyword controls the calculations of generalized pseudo-pressure option for model-
ing the effects of condensate dropout on the fluid mobilities at producing well connections.
(This option is activated in gas condensate runs for wells by entering GPP as 8-th parame-
ter of the keyword WELSPECS (see 12.18.3)). The data should be terminated with a slash /.

1. the maximum interval between pressure quadrature points below the dew point pressure
in the calculation of the generalized pseudo-pressure interval (METRIC: bars, FIELD:
psi),
2. the maximum interval between pressure quadrature points above the dew point pressure
in the calculation of the generalized pseudo-pressure interval (METRIC: bars, FIELD:
psi),
3. damping coefficient PPDAMP (from 0 to 1) for the blocking factor. It provides a means
of damping oscillations that may result from the explicit calculations of the blocking
factor (which is calculated at the beginning of each time step), by averaging it with
its value from the previous time step according to the formula: = PPDAMP calc +
(1 PPDAMP) previous , where calc - calculated value at the time step, previous -
value from previous time step;
5. coefficient PPBFAC to generate lower bound pL of generalized pseudo-pressure inte-

gral table:
pL = PPBFAC pcomp .
PPBFAC must obtain interval from 0 to 0.95;
6. coefficient PPBFAC to generate upper bound pL of generalized pseudo-pressure inte-

gral table:
pU = PPAFAC pcomp .
PPBFAC must obtain interval from 1.05 to 2;
Default:
the maximum interval between pressure quadrature points below the dew point pressure:
4 patm ( patm - atmospheric pressure),
12.18.187. PICOND 1569

the maximum interval between pressure quadrature points above the dew point pressure:
for e300 data format: 10 patm ( patm atmospheric pressure), for e100 data format: 0,
damping coefficient PPDAMP: 1.
coefficient PPBFAC : 0;
coefficient PPAFAC : 1.1;
Example
PICOND
28 0.1 0.7 2* 1.8/
In this example there are: the maximum interval between pressure quadrature points below
the dew point pressure - 28 bars, the maximum interval between pressure quadrature points
above the dew point pressure - 0.1 bars, damping coefficient PPDAMP - 0.7, coefficient
PPBFAC - 0, coefficient PPAFAC - 1.8.
12.18.187. PICOND 1570

12.18.188 WPAVE


Section
This keyword controls the calculation of well block average pressures. These averages
represent the average pressure of the grid blocks containing connections to a given well,
and optionally their adjacent and diagonal neighbors also, weighted according to either the
connection transmissibility factors or the grid block pore volumes. Additional options for
pressure weighting can be set in 5-th parameter of this keyword.
Well block average pressures can also can be written to the results binary files requested in
the keyword SUMMARY (see 12.17.1) via WBP, WBP4, WBP5 and WBP9. The averages
are used for reporting purposes only, and will not affect any other results.
If this keyword is not present, all items assume their default values, giving a poro
volume weighted average, evenly weighted between the inner blocks and the outer ring
of neighbors. The depth correction uses the wellbore density and only grid blocks associated
with currently open well connections are included in the average. The data should be termi-
1. the weighting factor F1 between the inner block and the outer ring of neighboring
blocks, in the connection factor weighted average. If the value lies between 0.0 and 1.0
(F1 0), the average block pressure for each connection k is the weighted average of
the inner block pressure Pi,k (i.e. the block containing the connection) and the average
of the pressures Po,k in the 4 or 8 blocks surrounding it:
o,k Po,k
Pk = F1Pi,k + (1 F1)
No,k
The value 1.0 gives total weighting to the inner blocks, containing the well connections.
The value 0.0 gives total weighting to the 4 or 8 blocks neighboring each inner block.
A value of F1 < 0 is used to indicate that the pressure of the inner block and its
outer ring of neighboring blocks should be averaged according to their pore volumes.
When F1 < 0, the average block pressure for each connection k is the average of the
pressures in the inner block Pi,k and in each of the 4 or 8 blocks surrounding it Po,k ,
weighted according to their pore volumes Vi,k and Vo,k :
12.18.188. WPAVE 1571

Vi,k Pi,k + o,k Vo,k Po,k

Pk =
Vi,k + o,k Vo,k
The pressure in each individual grid block Pi,k or Po,k is corrected to the wells bottom
hole reference depth according to the option selected in parameter 3. The number of
surrounding blocks No,k is 4 for 4-block and 5-block averages (WBP4, WBP5) and
8 for 9-block averages (WBP9). The configuration is shown in figure below. 4- and
5-block averages use the four immediate neighbors (n) of the connecting grid block. 9-
block averages use in addition the 4 diagonal neighbors (d). The inner block is ignored
in 4-block averages (WBP4). The number of neighbors is smaller if the well is situated
on the edge of the grid or adjacent to an inactive cell. The neighbors are selected in
the plane perpendicular to the direction of penetration of the connection (see parameter
13 of keyword COMPDAT (see 12.18.6)). Thus for horizontal wells, the neighbors are
in a vertical plane.
For 1-block averages (W BP) F1 is effectively 1.0, whatever the value entered here.
2. the weighting factor F2 between the connection factor weighted average and the pore
volume weighted average, which is used in the formula below. The value should lie
between 0.0 and 1.0. The value 1.0 gives a purely connection factor weighted average,
and 0.0 gives a purely pore volume weighted average.
The well block average pressure Pw for a given well is a weighted combination of
the connection factor weighted average pressure Pw,c f and the pore volume weighted
average pressure Pw,pw :
Pw = F2Pw,c
f + (1 F2)Pw,pv

Connection factor weighted average this is the average over connections of the
average block pressure Pk at each connection k , weighted according to the connection
transmissibility factors Tk :
f= k Tk Pk
Pw,c
k Tk
Pore volume weighted average this is simply the average depth-corrected pressure Pj
in the selected set of grid blocks j , weighted by their pore volumes V j :
= j V j Pj
Pw,pv
j Vj
3. depth correction flag. This flag controls how the grid block pressures are corrected to
the wells bottom hole reference depth (parameter 5 of the keyword WELSPECS (see
12.18.3)).
12.18.188. WPAVE 1572

WELL The hydrostatic head is calculated using the density of the fluid in the
wellbore at the well connections,
RES The hydrostatic head is calculated using a representative density for the
fluid in the reservoir. This density is calculated by averaging over fluid density for
all the grid blocks associated with the wells connections. The average over phases
is weighted by the phase saturation, and the average over grid blocks is weighted
by pore volume. Whether the averaging is performed over all grid blocks with
declared connections to the well or only those with currently open connections is
determined by parameter 4 of this keyword.
NONE Grid block pressures are not depth corrected.
The wellbore fluid density is set to zero whenever the well is shut. Thus if WELL is
selected there is a discontinuity in the reported pressure average when the wells status
changes between shut and open/stopped.
4. well connection flag. This flag controls whether the grid blocks associated with all the
wells declared connections contribute to the average pressure, or just those associated
with the currently open connections.
OPEN Only grid blocks associated with currently open connections are included
in the averaging calculation.
ALL Grid blocks associated with all currently defined connections (whether open
or closed) are included in the averaging calculation.
If OPEN is selected there is a discontinuity in the reported pressure average whenever

new connections are opened or existing ones are closed. This may be avoided by
selecting ALL and defining all the wells connections at the start of the run (whether
initially open or closed).
5. Type of weighting for pressure.
PV pore volume weighting;

CF weighting for connection factor;
MOB weighting for connections reservoir rate;
KH weighting for connections kh;
NONE no weighting, arithmetic average is calculated.
Default:
the weighting factor F1 0.5,
the weighting factor F2 1,
depth correction flag WELL,
12.18.188. WPAVE 1573

Figure 31: Grid block configuration in well block average pressure calculations
well connection flag OPEN,
type of weighting for pressure PV.
Example
WPAVE
0.33 0 2* /
In this example is given a purely pore volume weighted average, with increased weighting
to the outer blocks.
Example
WPAVE
0.33 1 /
In this example is given a connection factor weighted average, with increased weighting
to the outer blocks.
12.18.188. WPAVE 1574

12.18.189 WPAVEDEP


Section
The keyword can be used to modify reference depth for the calculation of well block
average pressures (keyword WPAVE (see 12.18.188)). The depth correction is calculated
according to parameter 3 of the keyword WPAVE (see 12.18.188).
The following parameters should be entered in each data line:
1. well name (or number) or well mask, which defines a subset of wells or well list
WLIST (see 12.18.26);
2. reference depth for the calculation of well block average pressures (METRIC: m,
FIELD: f t ).
Default:
reference depth for the calculation of well block average pressures well bottom hole
reference depth.
Example
WPAVEDEP
W1 2500 /
W1 3100 /
/
12.18.189. WPAVEDEP 1575

12.18.190 WRFT


Section
The keyword sets output of well RFT data. The following data will be written to RFT
file: pressure, saturation and depth for each grid block in which a well has a connection. An
arbitrary number of parameters can be entered. Each parameter should be followed by a slash
1. well name (or number) or well mask, which defines a subset of wells (for example,
all wells, PROD specifies all wells with names starting from PROD) or well list
WLIST (see 12.18.26).
If the keyword doesnt have any parameters, well RFT data will be output whenever a
well is first opened.
Example
WRFT
'WELL3*'/
'PROD11'/
12.18.190. WRFT 1576

12.18.191 WRFTPLT


Section
The keyword sets output of well RFT data (RFT file will be in the folder RESULTS).
The following data for output:
RFT depth, pressure, water and gas saturation for each block with connection.
PLT depth, pressure, oil, water and gas flows; tubing flows at each connection (total
upstream flow rates at surface conditions and local wellbore conditions); connection
transmissibility factor and Kh.
1. well name (or number) or well mask, which defines a subset of wells (for example,
all wells, PROD specifies all wells with names starting from PROD) or well list
WLIST (see 12.18.26).
2. RFT data output:
YES output the data for the wells at this time, describing conditions in the grid
blocks with well connections;
REPT output the data for the wells at this time and at all subsequent report
times;
NO dont output data.
3. PLT data output:
YES output the data for the wells at this time, describing the flows through the
well connections;
REPT output the data for the wells at this time and at all subsequent report
times at which the wells are open or stopped;
NO dont output data.
12.18.191. WRFTPLT 1577

Example
WRFT
'WELL3*'REPT REPT /
'P1'YES YES /
'P2'YES NO /
For the wells which names begins with WELL3, output of RFT and PLT data at this time
and at all subsequent report times. For the well P1 output of RFT and PLT data at current
time. For the well P2 output of RFT data at current time.
12.18.191. WRFTPLT 1578

12.18.192 SKIP


Section
The keyword provides all data below this keyword to be ignored till the keyword END-
SKIP (see 12.18.199), which terminates the skipping of the keywords.
This keyword can be used in any section (not only SCHEDULE section).
All the keywords specifying data skipping are the following: SKIP (see 12.18.192),
SKIP100 (see 12.18.194), SKIP300 (see 12.18.195), SKIPTNAV (see 12.18.196), SKIPON
(see 12.18.198), SKIPOFF (see 12.18.197), ENDSKIP (see 12.18.199).
Example
SKIP
WCONPROD
214 OPEN LRAT 30.4045 1* 1* 30.4045 1* 30.0000 /
213 OPEN LRAT 68.6742 1* 1* 68.6742 1* 30.0000 /
102 OPEN LRAT 73.5618 0.6640 1* 74.2258 1* 30.0000 /
103 OPEN LRAT 4.4876 1* 1* 4.4876 1* 30.0000 /
/
WCONINJE
104 WATER OPEN RATE 178.3000 1* 450.0000 /
126 WATER OPEN RATE 241.9000 1* 450.0000 /
/
ENDSKIP
All data between SKIP and ENDSKIP will be ignored.
12.18.192. SKIP 1579

12.18.193 SKIPREST


Section
This keyword allows to ignore all subsequent keywords in SCHEDULE section, until a
restart time has been reached RESTART (see 12.1.14). You shouldnt delete the keywords
(that should be ignored) manually.
Example
SKIPREST
12.18.193. SKIPREST 1580

12.18.194 SKIP100


Section
The keyword provides all data below this keyword to be ignored (if the model is open in
tNavigator as e100 model) till the keyword ENDSKIP (see 12.18.199), which terminates the
skipping of the keywords. (If the model is open in tNavigator as e300 model the data will
be read and used.)
Example
SKIP100
WCONPROD
214 OPEN LRAT 30.4045 1* 1* 30.4045 1* 30.0000 /
213 OPEN LRAT 68.6742 1* 1* 68.6742 1* 30.0000 /
102 OPEN LRAT 73.5618 0.6640 1* 74.2258 1* 30.0000 /
103 OPEN LRAT 4.4876 1* 1* 4.4876 1* 30.0000 /
/
WCONINJE
104 WATER OPEN RATE 178.3000 1* 450.0000 /
126 WATER OPEN RATE 241.9000 1* 450.0000 /
/
ENDSKIP
All data between SKIP100 and ENDSKIP will be ignored.
12.18.194. SKIP100 1581

12.18.195 SKIP300


Section
The keyword provides all data below this keyword to be ignored (if the model is open in
tNavigator as e300 model) till the keyword ENDSKIP (see 12.18.199), which terminates the
skipping of the keywords. (If the model is open in tNavigator as e100 model the data will
be read and used.)
Example
SKIP300
WCONPROD
214 OPEN LRAT 30.4045 1* 1* 30.4045 1* 30.0000 /
213 OPEN LRAT 68.6742 1* 1* 68.6742 1* 30.0000 /
102 OPEN LRAT 73.5618 0.6640 1* 74.2258 1* 30.0000 /
103 OPEN LRAT 4.4876 1* 1* 4.4876 1* 30.0000 /
/
WCONINJE
104 WATER OPEN RATE 178.3000 1* 450.0000 /
126 WATER OPEN RATE 241.9000 1* 450.0000 /
/
ENDSKIP
All data between SKIP300 and ENDSKIP will be ignored.
12.18.195. SKIP300 1582

12.18.196 SKIPTNAV


Section
The keyword provides all data below this keyword to be ignored till the keyword END-
SKIP (see 12.18.199), which terminates the skipping of the keywords.
The keyword is analogous to the Eclipse compatible keyword SKIP (see 12.18.192). This
keyword can be used in any section (not only SCHEDULE section).
Example
SKIPTNAV
WCONPROD
214 OPEN LRAT 30.4045 1* 1* 30.4045 1* 30.0000 /
213 OPEN LRAT 68.6742 1* 1* 68.6742 1* 30.0000 /
102 OPEN LRAT 73.5618 0.6640 1* 74.2258 1* 30.0000 /
103 OPEN LRAT 4.4876 1* 1* 4.4876 1* 30.0000 /
/
WCONINJE
104 WATER OPEN RATE 178.3000 1* 450.0000 /
126 WATER OPEN RATE 241.9000 1* 450.0000 /
/
ENDSKIP
All data between SKIPTNAV and ENDSKIP will be ignored.
12.18.196. SKIPTNAV 1583

12.18.197 SKIPOFF


Section
The keyword switches off data skipping, that was started via the keywords SKIP (see
12.18.192), SKIP100 (see 12.18.194), SKIP300 (see 12.18.195), SKIPTNAV (see 12.18.196).
The data after SKIPOFF will be read till the keyword SKIPON (see 12.18.198), which
switches data skipping on again.
So the keywords SKIPON (see 12.18.198) and SKIPOFF (see 12.18.197) should be used
between SKIP (see 12.18.192) (SKIP100 (see 12.18.194), SKIP300 (see 12.18.195), SKIPT-
NAV (see 12.18.196)) and ENDSKIP (see 12.18.199).
Example
SCHEDULE
SKIP
INCLUDE
'sch1.inc'/
SKIPOFF
INCLUDE
'sch2.inc'/
SKIPON
INCLUDE
'sch3.inc'/
INCLUDE
'sch4.inc'/
ENDSKIP
In this example the file sch1.inc is ignored (between SKIP and SKIPOFF), then the file
12.18.197. SKIPOFF 1584

sch2.inc is read and used (between SKIPOFF and SKIPON), files sch3.inc and sch4.inc are
ignored (between SKIPON and ENDSKIP).
12.18.197. SKIPOFF 1585

12.18.198 SKIPON


Section
The keyword switches on data skipping which was switched of via the keyword SKIPOFF
(see 12.18.197). The data after SKIPON (see 12.18.198) will be ignored till the keyword END-
SKIP (see 12.18.199).
So the keywords SKIPON (see 12.18.198) and SKIPOFF (see 12.18.197) should be used
between SKIP (see 12.18.192) (SKIP100 (see 12.18.194), SKIP300 (see 12.18.195), SKIPT-
NAV (see 12.18.196)) and ENDSKIP (see 12.18.199).
Example
SCHEDULE
SKIP
INCLUDE
'sch1.inc'/
SKIPOFF
INCLUDE
'sch2.inc'/
SKIPON
INCLUDE
'sch3.inc'/
INCLUDE
'sch4.inc'/
ENDSKIP
In this example the file sch1.inc is ignored (between SKIP and SKIPOFF), then the file
sch2.inc is read and used (between SKIPOFF and SKIPON), files sch3.inc and sch4.inc are
ignored (between SKIPON and ENDSKIP).
12.18.198. SKIPON 1586

12.18.199 ENDSKIP


Section
The keyword terminates data that is below the keyword SKIP (see 12.18.192) (SKIP100
(see 12.18.194), SKIP300 (see 12.18.195), SKIPTNAV (see 12.18.196)) and is ignored. The
data after ENDSKIP will be read and used.
Example
SKIP
WCONPROD
214 OPEN LRAT 30.4045 1* 1* 30.4045 1* 30.0000 /
213 OPEN LRAT 68.6742 1* 1* 68.6742 1* 30.0000 /
102 OPEN LRAT 73.5618 0.6640 1* 74.2258 1* 30.0000 /
103 OPEN LRAT 4.4876 1* 1* 4.4876 1* 30.0000 /
/
WCONINJE
104 WATER OPEN RATE 178.3000 1* 450.0000 /
126 WATER OPEN RATE 241.9000 1* 450.0000 /
/
ENDSKIP
All data between SKIP and ENDSKIP will be ignored.
12.18.199. ENDSKIP 1587

12.18.200 DRILPRI


Section
The keyword defines the default priority formula for the prioritized drilling queue
section 2.19.12. A well can be placed to prioritized drilling queue via the keyword WDRIL-
PRI (see 12.18.201) without a fixed priority (parameter 2 of the keyword WDRILPRI (see
12.18.201).
Drilling priorities for the prioritized drilling queue are calculated at constant time inter-
vals, specified via the 1-st parameter of this keyword.
For producers:
a + bQO + cQW + dQG
Priority =
e + f QO + gQW + hQG
where:
QO , QW , QG wells potential oil, water and gas production rates (description of wells
potential flow rate is in the section 5.7.7),
a, b, c, d, e, f , g, h coefficients specified via this keyword. These coefficients shouldnt be
negative. At least one of the first four coefficients must be non-zero, and at least one of the
last four coefficients must be non-zero.
For injectors drilling priorities are equal to their potential injection rates.
Calculated via this formula drilling priorities may be replaced by fixed priorities specified
via the keyword WDRILPRI (see 12.18.201).
The following parameters should be entered (The data should be terminated with a slash
/.):
1. minimal time interval between drilling priority calculation days (except for wells which
have fixed priorities specified via the 2-nd parameter of the keyword WDRILPRI (see
12.18.201));
2. a;
3. b;
4. c;
5. d ;
6. e;
12.18.200. DRILPRI 1588

7. f ;
8. g;
9. h.
Default: a, b, c, d, e, f , g, h 0.
Example
DRILPRI
150 0.0 1.0 0.0 0.0 1.0 0.0 0.0 0.0 /
In this example minimal time interval between drilling priority calculation - 150 days.
Wells will be drilled in decreasing order of their oil potentials:
a + bQO + cQW + dQG 1 Q0
Priority = = = Q0
e + f QO + gQW + hQG 1
12.18.200. DRILPRI 1589

12.18.201 WDRILPRI


Section
The keyword puts wells into the prioritized drilling queue and defines their drilling pri-
ority values section 2.19.12. The wells should be specified as shut or stopped producers or
injectors. (Drilling queue doesnt work for open wells.)
Drilling priorities, entered via 2-nd parameter of this keyword will replace the values, calcu-
lated via formula DRILPRI (see 12.18.200).
Any number of data rows could be entered (terminated with a slash /). All data should
1. well name of well list (WLIST (see 12.18.26));
2. priority value:
positive value drilling priority will be fixed at this value;

zero value this well will be removed from the drilling queue;
negative value drilling priorities for the prioritized drilling queue are calculated
at constant time intervals, specified via the 1-st parameter of the keyword DRILPRI
(see 12.18.200) from wells potential rates via the formula, whose coefficients are
set in DRILPRI (see 12.18.200) (for producers). For injectors drilling priority is
equal to their injection potentials.
Default: priority value negative.
Example
WDRILPRI
15 -1.0 /
13 -1.0 /
14 -1.0 /
16 2000.0 /
/
In this example negative priority values are set for wells 15, 13, 14. Well 16 has drilling
priority 2000.
12.18.201. WDRILPRI 1590

12.18.202 WDRILTIM


Section
The keyword specifies the time taken to drill the well. Section Prioritized drilling queue.
Sequential drilling queue 2.19.12.

1. well name or well list (WLIST (see 12.18.26));
2. time taken to drill the well (days) (time not earlier than which may well be open next
well from drilling queue QDRILL (see 12.18.203) or WDRILPRI (see 12.18.201)).
3. closure of well during drilling and workovers:

YES the well will be closed during its drilling and workovers (wells efficiency
factor WEFAC (see 12.18.69) is temporary set to zero) at the time steps during drilling
and workovers. The closure time for workovers is set via WORKLIM (see 12.18.206)
(zero by default).
NO well starts working at the beginning of the timestep in which its drilling starts,
and is not shut during workovers.
Default:
time taken to drill the well 0 days;
closure of well during drilling and workovers NO.
Example
WDRILTIM
PROD1 /
PROD3 /
PROD4 20 /
PROD6 30 /
/
In this example the time taken to drill the well PROD1 and PROD3 - default value (0
days). Time taken to drill the well PROD4 20 days, PROD6 30 days.
12.18.202. WDRILTIM 1591

12.18.203 QDRILL


Section
The keyword places the wells to sequential drilling queue. Section Prioritized drilling
queue. Sequential drilling queue 2.19.12.
The wells should be specified as shut or stopped producers or injectors. (Drilling queue
doesnt work for open wells.)
The keyword should be followed by well names, terminated with a slash /.
Example
QDRILL
W6 W4 W3 W8 W2 W12 W23 W1 W14
/
12.18.203. QDRILL 1592

12.18.204 GDRILPOT


Section
This keyword defines minimum potential rates for drilling. In the case if the groups
production or injection potential falls below the specified limit then in the drilling queue
(QDRILL (see 12.18.203) or WDRILPRI (see 12.18.201)) a new well will be found to open
to support the groups potential.
2. potential (the value of which is specified by the 3-rd parameter):
OPRD oil production potential;

WPRD water production potential;
GPRD gas production potential;
OING oil injection potential;
WING water injection potential;
GING gas injection potential;
For production only one potential limit can be defined for each group at one time.
For injection several limits may be defined simultaneously (one need to enter multiple
records of this keyword for the same group);
3. minimum potential rate (potential is specified via 2-nd parameter) (METRIC: sm3 /day,
FIELD: stb/day for oil and water or Msc f /day for gas).
Example
GDRILPOT
GROUP1 OPRD 5000 /
GROUP2 WINJ 4000 /
12.18.204. GDRILPOT 1593

12.18.205 WDRILRES


Section
The keyword prevents from drilling two wells in one grid block.
If this keyword is specified the the well from drilling queue (or on automatic opening
AUTO in WCONPROD (see 12.18.34)) will not be open if it goes through the grid block
where there is a well that is already open. Drilling queue is specified via the keywords
QDRILL (see 12.18.203), WDRILPRI (see 12.18.201), the section Prioritized drilling queue.
Sequential drilling queue 2.19.12).
In this case the well will be removed from drilling queue or automatic opening queue.
This keyword doesnt prevent if a new well is opened manually via the keyword
WELOPEN (see 12.18.107).
12.18.205. WDRILRES 1594

12.18.206 WORKLIM


Section
The keyword specifies the time taken for well automatic workover days. The data should
So there is a limit on the number of workovers that can be done by one workover rig at
time step. Workovers can be performed in case of instructions in the keywords WECON (see
12.18.62), CECON (see 12.18.67), GECON (see 12.18.102), GCONPROD (see 12.18.72),
GCONPRI (see 12.18.75), GCONSALE (see 12.18.168), PRORDER (see 12.18.212) e
WORKTHP (see 12.18.71).
Priority when several workovers need to be done at one time:
1. workovers that occur when a well cannot produce at its THP limit;
2. workovers that occur because of connection economic limit violations;
3. workovers that occur because of well economic limit violations;
4. workovers that occur because of group economic limit violations;
5. workovers that occur because of group flow limit violations;
6. workovers that occur because of field economic limit violations;
7. workovers that occur because of field flow limit violations.
Default: time taken to do well automatic workover 0 days.
Example
WORKLIM 7 /
12.18.206. WORKLIM 1595

12.18.207 GRUPRIG


Section
This keyword assigns workover and drilling rigs to well groups.

A rig, assigned to a high-level group can be used by all wells in subordinate groups. Several
groups can share the same rig.
A workover rig.
An automatic workover takes a time that is specified in the keyword WORKLIM (see
12.18.206). One rig is assigned for one well during the time of automatic workover
and is unavailable for other wells. If the well needs automatic workover and all rigs
that can be assigned to it are occupied until the end of the timestep then its workover
is postponed.
Workovers contains automatic closure and opening of well connections, according to
WECON (see 12.18.62), GECON (see 12.18.102), CECON (see 12.18.67), GCON-
PROD (see 12.18.72), GCONPRI (see 12.18.75), PRORDER (see 12.18.212), WORK-
THP (see 12.18.71).
Manual closure and opening of connections (COMPDAT (see 12.18.6)) dont depend
of rig availability and dont occupy any rig.
A drilling rig.
A drilling of a well takes a time that is specified in the keyword WDRILTIM (see
12.18.202). One rig is assigned for one well during the time of drilling and is unavail-
able for other wells. If the well needs to be drilled and all rigs that can be assigned to
it are occupied until the end of the timestep then its drilling is postponed.
The drilling processes controlled by rig availability are: drilling queue (QDRILL (see
12.18.203), WDRILPRI (see 12.18.201)), wells on automatic opening (parameter 2 of
the keyword WCONPROD (see 12.18.34) is AUTO) or if there are wells that are
opened on the closure of another well (parameter 8 of the keyword WECON (see
12.18.62)).
Manual well opening doesnt depend of drilling rig availability and doesnt occupy any
rig.
12.18.207. GRUPRIG 1596

1. group name or group name root or FIELD;
2. workover rig number (integer number from -2 to 99):
number from 1 to 99. A workover rig number that is added to the group (or
removed from the group) (according to parameter 4 of this keyword);
number 0. Dont make any changes to existing groups rigs;
number -1. A workover rig with this number prevents workovers on any well
subordinate to the group, regardless of the availability of other rigs;
number -2. All workover rigs, assigned to this group, will be removed.
3. drilling rig number (integer number from -2 to 99):
number from 1 to 99. A drilling rig number that is added to the group (or removed
from the group) (according to parameter 4 of this keyword);
number 0. Dont make any changes to existing groups rigs;
number -1. A drilling rig with this number prevents any well subordinate to the
group to be drilled, regardless of the availability of other rigs;
number -2. All drilling rigs, assigned to this group, will be removed.
4. add or remove specified rigs: ADD add these rigs to group, REM delete these rigs
from group.
Default:
workover rig number: 0;
drilling rig number: 0;
add or remove specified rigs: ADD.
Example
GRUPRIG
GROUP1 1 1 ADD /
GROUP2 2 2 ADD /
GROUP3 2 2 ADD /
FIELD 3 1 ADD /
/
12.18.207. GRUPRIG 1597

12.18.208 NUPCOL


Section
This keyword specifies the number of Newton iterations (non-linear iterations) for a time
step, for which well targets will be updated (for wells working under group control or with
limits on the amount of pressure drop). At next non-linear iterations at the time step the well
targets will stay unchanged.
One integer number should be specified. The data should be terminated with a slash /.
In case of group control the value of well production rates and injection rates are depen-
dent on each other and on other reservoir wells.
Wells targets are updated only for the number of iterations specified via this keyword. Group
and field flow targets will be exactly met, if the convergence of Newtons method for the
time step is reached in NUPCOL iterations.
Default: 3.
Example
NUPCOL
5 /
12.18.208. NUPCOL 1598

12.18.209 WELLOPTS


Section
This keyword is a full analogue of the keyword NUPCOL (see 12.18.208).
12.18.209. WELLOPTS 1599

12.18.210 GCONTOL


Section
This keyword will override the value of NUPCOL (see 12.18.208), specified earlier.
(NUPCOL (see 12.18.208) This keyword specifies the number of Newton iterations
(non-linear iterations) for a time step, for which well targets will be updated (for wells work-
ing under group control or with limits on the amount of pressure drop). At next non-linear
iterations at the time step the well targets will stay unchanged.)
/.):
2. the number of Newton iterations (non-linear iterations) for a time step, for which
well targets will be updated. This value will override NUPCOL (see 12.18.208) or
previously defined GCONTOL.
Example
GCONTOL
* 4 /
12.18.210. GCONTOL 1600

12.18.211 WLIFT


Section
This keyword specifies an automatic retubing and THP or lift switching.
Retubing, THP or lift switching are performed in the following cases:
wells production rate falls below the value specified in parameter 2,
wells water cut exceeds the value specified in parameter 7,
wells gas-liquid ratio exceeds the value specified in parameter 9,
the well dies under THP control.
Operations that are performed:
if a new THP limit is specified (parameter 8), the well switches on it (this is analog to
the switching the well to a separator with lower pressure to increase wells productivity).
If parameter 11 specifies a decrement, then THP switching is performed in stages: each
time THP is reduced by the specified decrement until the final THP value is reached
(final value is specified in parameter 8).
if in parameter 4 a VFP table number is specified, the well switches to this table (this
is analog to the retubing operation, if the new table has been calculated with a different
tubing diameter from the original table).
if an artificial lift quantity is specified in parameter 5, then the well will use it to
interpolate the VFP table (this is analog to the switching on or updating of artificial lift
in the well). If parameter 10 is specified, then each time ALQ will be increased by the
specified increment (ALQ switching is performed in stages). A new efficiency factor
can be specified in parameter 6.
Multi-stage process (non zero values of parameters 4, 5, 8 are specified):

Operations are performed if well production rate, water cut or gas-liquid ratio violates its
limit (parameters 2, 7, 9). Operations order:
switching to lower THP limit;
switching to new VFP table;
switching to new artificial lift quantity.
12.18.211. WLIFT 1601

1. well name or well list, specified via WLIST (see 12.18.26);
2. well production rate (METRIC: sm3 /day, FIELD: stb/day), below which the switching
operations are performed.
Negative or zero value: switching operation is not performed in case of low production
rate. Default value can be used if the switching operations are performed only by the
group production rules (PRORDER (see 12.18.212)) or if the well dies under THP
control.
3. phase to which the production rate is specified in parameter 2: OIL or LIQUID;
4. new VFP table number for retubing (this number replaces the number, specified in
WCONPROD (see 12.18.34)).
Negative or zero value: retubing operation is not performed;
5. new artificial lift quantity for lift switching (this number replaces the number, specified
in WCONPROD (see 12.18.34) WELTARG (see 12.18.51)). To perform lift switching
in stages the increment value should be specified in parameter 10.
Negative or zero value: lift switching operation is not performed;
6. new well efficiency factor after lift switching (this number replaces the number, speci-
fied in WEFAC (see 12.18.69).
Negative or zero value: original value of well efficiency factor stays unchanged;
7. wells water cut limit (METRIC: sm3 /sm3 , FIELD: stb/stb), above which the switch-
ing operations are performed.
Negative or zero value: switching operation is not performed in case of high water cut.
Default value can be used if the switching operations are performed only by the group
production rules (PRORDER (see 12.18.212)) or if the well dies under THP control.
8. new THP limit (this number replaces the number, specified in WCONPROD (see
12.18.34) or WELTARG (see 12.18.51)). To perform THP switching in stages the
decrement value should be specified in parameter 11.
Negative or zero value: switching operation is not performed;
9. wells gas-liquid ratio (METRIC: sm3 /sm3 , FIELD: Msc f /stb), above which the
switching operations are performed.
Negative or zero value: switching operation is not performed in case of high gas-liquid
ratio. Default value can be used if the switching operations are performed only by the
group production rules (PRORDER (see 12.18.212)) or if the well dies under THP
control.
12.18.211. WLIFT 1602

10. increment that will be added to (or subtracted from) the wells ALQ value at each lift
switching event until the final ALQ value (specified in parameter 5) will be reached;
11. decrement (METRIC: barsa, FIELD: psia), that will be subtracted from the wells THP
value at each THP switching event, until the final THP value (specified in parameter
8) will be reached.
Default:
well production rate 0;
phase to which the production rate is specified in parameter 2: OIL;
new VFP table number for retubing 0;
new artificial lift quantity for lift switching 0;
new well efficiency factor after lift switching 0;
wells water cut limit 0;
new THP limit 0;
wells gas-liquid ratio 0;
increment that will be added to (or subtracted from) the wells ALQ value at each lift
switching;
decrement that will be subtracted from the wells THP value at each THP switching
event.
Example
WLIFT
WLIST1 40 OIL 2 4 /
/
In this example for all wells from the well list WLIST1: if oil production rate falls below
40 sm3 /day a new VFP table number 2 is specified and a new ALQ value 4.
12.18.211. WLIFT 1603

12.18.212 PRORDER


Section
The keyword specifies the order of actions to be performed is a group cant meet its pro-
duction rate target specified in GCONPROD (see 12.18.72). The data should be terminated
with a slash /.
Actions will be performed in the order in which they are specified. Next action is per-
formed if no actions of previous type can be performed any more.
Possible actions:
DRILL open new wells from the drilling queue.

The drilling queue should be specified: Sequential (QDRILL (see 12.18.203)) or
Prioritized WDRILPRI (see 12.18.201). Time of drilling one well is specified in
WDRILTIM (see 12.18.202), drilling rigs GRUPRIG (see 12.18.207).
REPERF open new connections on AUTO mode in existing wells.

Wells connections should stay on automatic opening (parameter 6 of the keyword
COMPDAT (see 12.18.6) or the keyword WELOPEN (see 12.18.107)). Time of wells
workover is specified in WORKLIM (see 12.18.206), workover rigs GRUPRIG (see
12.18.207).
THP reduce each wells THP limit to a specified lower value.

If a new THP limit is specified (parameter 8 of WLIFT (see 12.18.211)), the well
switches on it (this is analog to the switching the well to a separator with lower
pressure to increase wells productivity). If parameter 11 of WLIFT (see 12.18.211)
specifies a decrement, then THP switching is performed in stages: each time THP is
reduced by the specified decrement until the final THP value is reached (final value is
specified in parameter 8).
RETUBE change VFP table numbers.

If in parameter 4 of WLIFT (see 12.18.211) a VFP table number is specified, the well
switches to this table (this is analog to the retubing operation, if the new table has been
calculated with a different tubing diameter from the original table).
LIFT change ALQ values.

If an artificial lift quantity is specified in parameter 5 of WLIFT (see 12.18.211), then
the well will use it to interpolate the VFP table (this is analog to the switching on
or updating of artificial lift in the well). If parameter 10 of WLIFT (see 12.18.211)
12.18.212. PRORDER 1604

is specified, then each time ALQ will be increased by the specified increment (ALQ
switching is performed in stages). A new efficiency factor can be specified in parameter
6 of WLIFT (see 12.18.211).
Restrictions on the total amount of groups lift can be specified via GLIFTLIM (see
12.18.214).
If no parameter of this keyword are specified (the keyword is terminated by a slash /),
then no operations will be performed in case if the group cant meet its production rate
target.
Example
PRORDER
DRILL RETUBE /
12.18.212. PRORDER 1605

12.18.213 LIFTOPT


Section
This keyword sets that Gas Lift Optimization option is used 2.19.8.
The keyword should be specified before GLIFTOPT (see 12.18.215), WLIFTOPT (see

1. increment size for lift gas injection rate (METRIC: sm3 /day, FIELD: Msc f /day). The
Lift gas is allocated to wells in whole numbers of increment. Gas lift optimization is
turned off if 0 or negative value is specified in this parameter;
2. minimum economic gradient of improvement in oil production rate for increase in lift
gas injection rate by one (METRIC: m3 /sm3 , FIELD: stb/Msc f ). For each well the
value Winc (weighted incremental gradient) is calculated the increment of field oil
production rate (due to increment in the gas lift at one increment value) multiplied by
wells weighting factor and divided by value of increment in the gas lift. If the result
value is less than the minimum economic gradient, then the next lift gas increment is
not allocated to this well;
3. minimum interval between gas lift optimizations (days). Gas lift optimization is made
at each time step which starts after the end of this minimum interval time from previous
optimization;
4. should tNavigator optimize gas lift during each of the first NUPCOL (see 12.18.208)
iterations of the time step: tNavigator supports only YES (the value of NUPCOL can
be also redefined via GCONTOL (see 12.18.210)).
Default:
minimum interval between gas lift optimizations 0 (days);
should tNavigator optimize gas lift during each of the first NUPCOL (see 12.18.208)
iterations of the time step: YES.
Example
LIFTOPT
35000 0.0 50.0 /
12.18.213. LIFTOPT 1606

12.18.214 GLIFTLIM


Section
The keyword specifies the maximum group capacity for artificial lift 2.19.8.
2. maximum total lift capacity.

This value is a limit of the sum of the artificial lift quantity (ALQ) values of all
subordinate open producer wells multiplied by their efficiency factors. The value will
limit the total pump power that can be applied in the group (in case when ALQ refers
to the pump power), or this value will limit the groups total lift gas injection rate (in
case when ALQ refers to the lift gas injection rate);
3. maximum number of wells on artificial lift.
Example
GLIFTLIM
GROUP1 520.0 /
/
12.18.214. GLIFTLIM 1607

12.18.215 GLIFTOPT


Section
This keyword specifies the group lift gas limits for gas lift optimization option 2.19.8.
2. maximum lift gas supply limit for the group (METRIC: sm3 /day, FIELD: Msc f /day).
The groups lift gas supply is equal to the sum of the lift gas injection rates of its wells
or groups, multiplied by their efficiency factors (for wells WEFAC (see 12.18.69),
for groups GEFAC (see 12.18.70));
3. maximum total gas rate for the group (METRIC: sm3 /day, FIELD: Msc f /day). The
groups total gas rate is equal to the sum of the lift gas plus the gas produced from the
formation for its well or group, multiplied by the wells or groups efficiency factor
(for wells WEFAC (see 12.18.69), for groups GEFAC (see 12.18.70)). The wells
below this group are not assigned a lift gas increments if they would cause this limit
to be exceeded.
Example
GLIFTOPT
GROUP1 100000 /
GROUP2 90000 /
/
12.18.215. GLIFTOPT 1608

12.18.216 WLIFTOPT


Section
This keyword sets well parameters for Gas lift optimization 2.19.8.
1. well name, or number, or well list (WLIST (see 12.18.26));
2. should tNavigator calculate the wells lift gas injection rate with optimization: YES or
NO in this case the wells lift gas injection rate is equal to the value that can be set
in 3-rd parameter of this keyword, 12-th parameter of WCONPROD (see 12.18.34) or
WELTARG (see 12.18.51);
3. maximum rate of lift gas injection for the well (METRIC: sm3 /day, FIELD:
Msc f /day). If the 2-nd parameter of this keyword is NO, then this parameter specifies
the fixed lift gas injection rate for the well;
4. well weighting factor for preferential allocation of lift gas fw ; An increment of lift gas
supply is allocated to the well that has the largest value of Winc . (For each well the
value Winc (weighted incremental gradient) is calculated the increment of field oil
production rate (due to increment in the gas lift at one increment value) multiplied by
wells weighting factor and divided by value of increment in the gas lift. If the result
value is less than the minimum economic gradient, then the next lift gas increment is
not allocated to this well.
Formula of Winc (formula is different if the 6-th parameter of this keyword is specified,
see below):
fw TO
Winc =
GLinc
where:
fw wells weighting factor (this parameter of the keyword);
TO increment (or decrement) in field oil production rate;
GLinc increment (or decrement) in the gas lift.
12.18.216. WLIFTOPT 1609

5. minimum rate of lift gas injection for the well (METRIC: sm3 /day, FIELD:
Msc f /day). A positive value: the well is allocated at least that amount of lift gas
(except for the case when the well can already meet one of its rate limits before re-
ceiving its minimum lift gas rate).
A negative value: the well is allocated at least enough lift gas to enable it to flow (but
less than maximum value specified in 3-rd parameter).
Not enough lift gas available to satisfy all the wells minimum requirements: the wells
are allocated their minimum requirements in decreasing order of their weighting factors
(parameter 4).
6. fG gas rate weighting factor.
If this parameter is specified then the formula for Winc is the following:
fw TO
Winc =
GLinc + fG TG
where:
fG gas production rate weighting factor (this parameter of the keyword);
TG increment (or decrement) in field gas production rate.
7. allocate additional lift gas when a group gas target has been achieved but the oil rate
limit has not been reached: YES the well can receive next lift gas, NO the well
cant receive next lift gas.
If YES, then for a group on gas target control the constraint for additional gas lift
allocation is removed that provides a possibility of gas lift optimization to increase the
oil rate.
Default:
maximum rate of lift gas injection for the well: if 2-nd parameter is YES, then the
largest ALQ in wells VFP table; if 2-nd parameter is NO, then stays unchanged;
well weighting factor for preferential allocation of lift gas 1;
minimum rate of lift gas injection for the well 0;
gas rate weighting factor 0;
allocate additional lift gas when a group gas target has been achieved but the oil rate
limit has not been reached: NO.
Example
WLIFTOPT
W34 YES 100000 1.01 1* 1.0 YES /
/
12.18.216. WLIFTOPT 1610

12.18.217 OPTIONS


Section
The keyword activates special option of model reading, calculation and saving results.
tNavigator supports only 31-st, 47-th, 48-th and 117-th parameters of this keyword. All
other parameters are ignored (tNavigator reads them but they doesnt change model calcula-
tion Eclipse data format compatibility).
Description of supported parameters:
31. If the value is greater than 0, this parameter is converted into tNavigator keyword
RUNCTRL (see 12.18.119) parameter PAVWEIGHT.
Parameter PAVWEIGHT of RUNCTRL (see 12.18.119) works the following way.
In the case that the value of this parameter is even (or not specified) - average field
pressure is the hydrocarbon pore volume weighted average. Odd value - average field
pressure is the pore volume weighted average.
Default average field pressure (the hydrocarbon pore volume weighted average):
Porvhc pO
PRESSURE =
Porvhc
Porvhc = Porv(1 Sw ) hydrocarbon pore volume; Porv block pore volume; pO
oil phase pressure.
Average field pressure is the pore volume weighted average (odd value of parameter):
Porv pO
PRESSURE =
Porv
Field oil potential (FPPO in section SUMMARY (see 12.17.1)) is specified one of the
following ways:
default
POTO SO Porv
FPPO =
SO Porv
where POTO oil potential, SO oil saturation;
12.18.217. OPTIONS 1611

in the case that the value of this parameter is even
POTO Porv
FPPO =
Porv
Oil potential of a block calculations (oil potential oil phase pressure, corrected to
a datum depth):
POTO = pO O g(D Ddat )
where:
O oil average density in PVT region;

g gravity acceleration;
D block depth;
Ddat reference depth. Reference depth can be specified via the keyword DATUM
(see 12.15.34) or it can be taken from the 1-st equilibration region reference
depth, specified via EQUIL (see 12.15.2). If keywords DATUM (see 12.15.34),
EQUIL (see 12.15.2) are not specified, then reference depth is set to zero. One
can specify reference depth different for different fluid-in-place (FIP) regions via
the keyword DATUMR (see 12.15.35).
46. This parameter controls MINPV (see 12.2.30) or MINPVV (see 12.2.32) values
inheriting (copying) on LGR, when at least one of them is defined in global grid, but
not in local. If value 1 is set, then the threshold pore volumes are not copied from
global host cells; if value is omitted or it equals to 0, then:
if MINPV (see 12.2.30) and MINPVV (see 12.2.32) are specified both, but MINPV
(see 12.2.30) is first, then values for blocks specified in the array erase MINPV
(see 12.2.30) values. So, MINPV (see 12.2.30) value is used only for blocks
unspecified in MINPVV (see 12.2.32) array;
otherwise, MINPV (see 12.2.30) erases all MINPVV (see 12.2.32) values.
If in the current grid only MINPVV (see 12.2.32) is used, then:
MINPVV (see 12.2.32) is set for each grid block;

otherwise, volume limit for parent grid calculated by rule above is used. This limit
is applied to blocks for which MINPVV (see 12.2.32) of current grid is not set.
If limits in current grid are not set, then limits of parent grid are used.
47. This parameter prevents (if > 0) perforation pressures fall below atmospheric pres-
sure.
12.18.217. OPTIONS 1612

48. If this parameter value is greater than 0 in a model with dual porosity single perme-
ability option: then if any fracture blocks are made inactive because the fracture blocks
pore volumes fall below the value MINPV (see 12.2.30) or MINPVV (see 12.2.32), the
corresponding matrix blocks will be inactivated too.
If this parameter value is greater than 1: then any active matrix blocks with a corre-
sponding inactive fracture blocks will be made inactive.
117. This parameter affects dual porosity and dual permeability values using the key-
words MULTNUM (see 12.4.23), FLUXNUM (see 12.4.18), PINCHNUM (see 12.2.57)
or OPERNUM (see 12.4.22). If this parameter value is 1, then regions specified via
the keyword MULTNUM (see 12.4.23) must be specified separately for matrix and
fracture.
If this parameter value is 2 or greater, then regions specified by all of these keywords
must be specified separately for matrix and fracture.
Example
OPTIONS
30* 1 /
/
In this example average field pressure is the pore volume weighted average.
Example
OPTIONS
30* 0 /
/
In this example average field pressure is the hydrocarbon pore volume weighted average.
12.18.217. OPTIONS 1613

12.18.218 RECU


Section
This keyword provides hybrid model loading: model in ECLIPSE format, well data in
MORE format.
The keyword SCHEDULE shouldnt be used in this case (sharing SCHEDULE and RECU
will lead to errors).
In the example below there is data in ECLIPSE format first, then there is the keyword
RECU and then data in MORE format.
12.18.218. RECU 1614

Example
SOLUTION
EQUIL
2515 350 2530 0 2500 0 1 0 0 /
/
SUMMARY
/
RECU
GENE PRES FLIP REST CMPL WELL GROUP FIELD WLAY GLAY AQUI RTEM
CPLY STORE ESUM EQUA MONTHS WELLS FIELD STATS
1 /
ESOL MONTHS EQUA
1 /
RATE 1 MON FIELD GROUP WELL CRATE EXACT SLIM LRATE

FREQ 0 1 1
/
ARRAY DATE END

1 JAN 1995
1 FEB 1995
1 MAR 1995
1 APR 1995
1 MAY 1995
1 JUN 1995
1 JUL 1995
1 AUG 1995
1 SEP 1995
1 OCT 1995
1 NOV 1995
1 DEC 1995
/
welltrack '107R'
1050 1050 2500.0 2500.000
...
12.18.218. RECU 1615

12.18.219 USERFILE


Section
This keyword allows to include files in user specified order. It can be used for example
in hybrid models when there is data in MORE and Eclipse format in the same time and it is
necessary to define the order in which tNavigator must read it. There is an example in the
section 11.3.
This keyword has an Eclipse compatible analogue INCLUDE (see 12.1.73).
12.18.219. USERFILE 1616

12.18.220 COMPVAL


Section
The keyword sets length of perforated interval in specified block. To set this in local grid
refinement use the keyword COMPVALL (see 12.18.221)
1. well name;
2. X -coordinate of well connection;
3. Y -coordinate of well connection;
4. Z -coordinate of upper neighbor block for well connection;
5. Z -coordinate of lower neighbor block for well connection;
6. type of 7-th parameter:
LENGTH;
7. length of perforated interval (METRIC: m, FIELD: f t ).
Default:
X -coordinate of well connection: 0 (any value);
Y -coordinate of well connection: 0 (any value);
Z -coordinate of upper neighbor block for well connection: 0 (any value);
Z -coordinate of lower neighbor block for well connection: 0 (any value);
Example
COMPVAL
'NO_HTWI' 3 3 1 1 LENGTH 3.048 /
'NO_HTWI' 3 3 2 2 LENGTH 3.048 /
'NO_HTWI' 3 3 3 3 LENGTH 3.048 /
'NO_HTWI' 3 3 4 4 LENGTH 3.048 /
/
In the example for well NO_HTWI lengths of four perforated intervals in four consec-
utive blocks are set. Length of each perforated interval is equal to 3.048 ft.
12.18.220. COMPVAL 1617

12.18.221 COMPVALL


Section
The keyword sets length of perforated interval in specified block.

1. well name;
2. name of the local grid refinement where this well is (LGRs name is set via CARFIN
(see 12.2.87));
3. X -coordinate of well connection;
4. Y -coordinate of well connection;
5. Z -coordinate of upper neighbor block for well connection;
6. Z -coordinate of lower neighbor block for well connection;
7. type of 7-th parameter:
LENGTH;
8. length of perforated interval (METRIC: m, FIELD: f t ).

Default:
X -coordinate of well connection: 0 (any value);
Y -coordinate of well connection: 0 (any value);
Z -coordinate of upper neighbor block for well connection: 0 (any value);
Z -coordinate of lower neighbor block for well connection: 0 (any value);
Example
COMPVALL
'NO_HTWI' 'LGR1' 3 3 1 1 LENGTH 3.048 /
/
12.18.221. COMPVALL 1618

In the example for well NO_HTWI (that is in the LGR1) lengths of four perforated
intervals in four consecutive blocks are set. Length of each perforated interval is equal to
3.048 ft.
12.18.221. COMPVALL 1619

12.18.222 WNETDP


Section
The keyword is should be used only with the option NETWORK (2.19.10). It sets fixed
pressure drop value between a wells tubing head pressure and its groups corresponding node
in the network.
1. well name, name mask or well list;
2. fixed pressure drop value between a wells tubing head pressure and its groups corre-
sponding node in the network (METRIC: bar , FIELD: psi).
Each line should be ended by /. The data should be terminated with a slash /.
Default:
fixed pressure drop value: 0.
Example
WNETDP
'28' 5.0 /
'29' 2.0 /
'30' 5.0 /
In the example fixed pressure drop values are specified for 3 wells.
12.18.222. WNETDP 1620

12.18.223 WELLPROD


Section
This keyword sets the production targets for a well.
The keyword is obsolete. It is recommended to use the keyword WCONPROD (see

12.18.34).
1. well name, well name mask or well list WLIST (see 12.18.26),
2. well control mode:
OIL oil rate;

WAT water rate;
GAS gas rate;
LIQ liquid rate;
THP tubing head pressure;
RV rate value in reservoir conditions;
WG wet gas rate;
TM total molar rate;
ST steam production (using with thermal option only);
SATP water saturation pressure (see parameter 15; only for models with THER-
MAL (see 12.1.50) option);
SATT water saturation temperature (see parameter 16; only for models with
THERMAL (see 12.1.50) option);
GROUP specifies that the well is under group control.
3. oil rate (METRIC: sm3 /day, FIELD: stb/day);
4. water rate (METRIC: sm3 /day, FIELD: stb/day);
5. gas rate (METRIC: sm3 /day, FIELD: Msc f /day);
6. liquid rate (METRIC: sm3 /day, FIELD: stb/day);
12.18.223. WELLPROD 1621

7. BHP value or limit (METRIC: barsa, FIELD: psia);
8. THP value or limit (METRIC: barsa, FIELD: psia). A zero value will prevent the
well switching to THP control, whatever the value of its calculated THP (VFP table
number should be specified in next parameter of this keyword);
9. liquid rate in reservoir conditions (METRIC: rm3 /day, FIELD: rb/day);
10. wet gas rate or limit (METRIC: sm3 /day, FIELD: /day);
THP will not be reported.
13. the target or limit total molar rate (METRIC: kg M/day, FIELD: lb M/day);
14. The target or limit steam rate, (CWE Cold Water Equivalent). (METRIC: sm3 /day,
FIELD: stb/day). Available only with the Thermal option THERMAL (see 12.1.50).
Rate can be set by UDQ (see 12.18.138).
15. pressure offset P for water saturation pressure control (METRIC: bar , FIELD: psia).
This parameter can be used only in THERMAL (see 12.1.50) runs. Can be specified
by user via UDQ (see 12.18.138).
The constraint for BHP is BHP Psat + P, where Psat is maximum saturated water
pressure in all blocks with prodicing connections;
16. temperature offset T for water saturation temperature control (METRIC: C , FIELD:
F ). This parameter can be used only in THERMAL (see 12.1.50) runs. Can be
specified by user via UDQ (see 12.18.138).

The constraint for BHP is BHP Psat (T + T ), where T is maximum temperature in
all blocks with prodicing connections;
Each line of data should be ended by /. The data should be terminated with a slash /.
Default:
rate limit: 1e + 20 m3 /day;
BHP limit: for E100 format models 1atma = patm (atmosphere pressure), for E300
format models 100 atma = 1470 psia;
THP value or limit: 0;
well VFP table number: 0;
12.18.223. WELLPROD 1622

Example
WELLPROD
'HAIL-3' 'GROUP' 2* 20000 1* 2000 6* /
/
In the example well HAIL-3 is controlled by a group. Limit on gas rate is 20000
Msc f /day. Limit on BHP value is 2000 psia. Values of other parameters are set by default.
12.18.223. WELLPROD 1623

12.18.224 GRUPPROD


Section
This keyword specifies the production targets and limits for a group.
The keyword is obsolete. It is recommended to use the keyword GCONPROD (see

12.18.72).
1. group name (or group name mask, i.e. name ending with asterisk), or FIELD (for field
control),
2. control mode:
NONE no immediate control;

LIQ liquid volume rate;
OIL oil volume rate;
WAT water volume rate;
GAS gas volume rate;
RV reservoir volume rate;
WGV wet gas volume rate;
GR group is immediately under control from a higher level group.
3. oil rate (or limit) (METRIC: sm3 /day, FIELD: stb/day);
4. water rate (or limit) (METRIC: sm3 /day, FIELD: stb/day);
5. gas rate (or limit) (METRIC: sm3 /day, FIELD: Msc f /day);
6. liquid rate on the surface (or limit) (METRIC: sm3 /day, FIELD: stb/day);
7. reservoir fluid volume production rate (or limit) (METRIC: rm3 /day, FIELD: rb/day).
8. wet gas production rate target (or limit) (METRIC: sm3 /day, FIELD: Msc f /day).
Each line of data should be ended by /. The data should be terminated with a slash /.
Default:
12.18.224. GRUPPROD 1624

12.18.3));
control mode: NONE;
rates: no rate or limit.
Example
GRUPPROD
'GC' 'GAS' 2* 200000 3* /
/
In the example well group GC is on the gas rate control. Limit on gas rate value is
200000 Msc f /day. There are no limits on other rates.
12.18.224. GRUPPROD 1625

12.18.225 WELLCOMP


Section
The keyword sets location and properties of one or several connections of specified well.
It should be used after the keyword WELSPECS (see 12.18.3), which defines that well.
The keyword is obsolete. It is recommended to use the keyword COMPDAT (see 12.18.6).
Each line of data should be ended by a symbol /. The data should be terminated with a
slash /.
1. well name, well name mask or well list WLIST (see 12.18.26),
6. saturation table number,
7. well diameter (METRIC: m, FIELD: f t );
8. transmissibility factor (METRIC: cP rm3 /day bar , FIELD: cP rb/day psi) for
each connection in this interval (if it is specified, well diameter, skin and KH are
ignored), this is coefficient T (t) in 5.7.1,
10. imbibition table number, IGNORED, this is an Eclipse compatibility field;
11. effective KH (METRIC: mD-m, FIELD: mD- f t ) (production of permeability and
thickness) for each connection in this interval, (see 5.7.2),
12. direction in which this interval penetrates grid block: X, Y or Z.
This keyword may be defined several times at any time step for the same well for dif-
ferent connections. Perforated intervals for the same well may be spaced (may not form a
continuous interval) and have different orientation in space.
Default:
12.18.225. WELLCOMP 1626

perforated interval coordinate in X direction (IW): taken from 12.18.3,
perforated interval coordinate in Y direction (JW): taken from 12.18.3,
starting block of vertical perforated interval: 1,
ending block of vertical perforated interval: 1,
saturation table number: tNavigator will use the saturation table number that is specified
for block with connection via SATNUM (see 12.4.3);
well diameter: dw = 0.156 m,
transmissibility factor: calculated,
skin factor: s = 0,
KH value: negative,
well orientation in space: Z,
Example
WELLCOMP
'HAIL-3' 33 44 8 8 1* 0.5 1* -3 2* 'Z'/
/
In the example well HAIL-3 is perforated at block (33, 44, 8). Number of saturation
table is taken from parameters of the keyword SATNUM (see 12.4.3), well diameter is 0.5
f t , transmissibility factor is calculated, skin factor is 3, KH is negative, well orientation is
Z.
12.18.225. WELLCOMP 1627

12.18.226 TRANGE


Section
The keyword specifies minimal and maximal temperature of formation. The values can
be changed during calculation. The data should be terminated with a slash /.
1. minimal formation temperature (METRIC: C , FIELD: F );
2. maximal formation temperature (METRIC: C , FIELD: F ).
By default:
minimal formation temperature: 1 C ;
maximal formation temperature: 500 C ;
Example
TRANGE
50 250
12.18.226. TRANGE 1628

12.18.227 SCDPTAB


Section
The keyword defines total rate of scale deposition per unit flow rate of water into a well
connection dependence of the fraction of sea water present in the water flowing through this
connection via table.
The sea water fraction is equated to the concentration of a passive water tracer which
is noted in keyword SCDPTRAC (see 12.18.228). Tables which defined via SCDPTAB are
allocated to individual wells with the keyword WSCTAB (see 12.18.230). The effect of the
deposited scale on the productivity index of the well should be defined in scale damage tables
(keyword SCDATAB (see 12.18.229)).
The number of tables is set via the keyword SCDPDIMS (see 12.1.108). Each table
should be ended by a symbol /.
Table should contain the following columns:
1. the fraction of sea water in the water flowing into a well connection. Values should be
increasing from line to line;
2. the corresponding total rate of scale deposition per unit flow rate of water through the
connection (METRIC: gm/m3 , FIELD: lb/ f t 3 ).
Example
SCDPTAB
0 0
0.1 0.1
1 10 /
In the example the keyword SCDPTAB (see 12.18.227) sets one dependence table. The
left column contains sea water concentration values, the right one values of total rate of
scale deposition.
12.18.227. SCDPTAB 1629

12.18.228 SCDPTRAC


Section
This keyword is used to note the tracer whose concentration represents the fraction of sea
water present in the water flowing into a well (Section Scale deposition model 2.27). This
tracer is used to calculate the current amount of scale deposited around well connections. The
tracer must be already defined as a water phase tracer (the keyword TRACER (see 12.7.1))
with water injectors given a tracer value of 1.0 (keyword WTRACER (see 12.18.148)), while
the tracer value of the water initially in the reservoir is set to 0.0.
1. tracer name.
Example
SCDPTRAC
AAA /
In the example the keyword SCDPTRAC (see 12.18.228) notes tracer name AAA.
12.18.228. SCDPTRAC 1630

12.18.229 SCDATAB


Section
The keyword is used to set the reduction coefficient for the productivity index of each
connection in a well dependence of the current amount of scale deposited per unit length of
perforated interval as a table.
Parameters of this keyword are tables which number is set via the keyword SCDPDIMS
(see 12.1.108). The data should be terminated with a slash /.
Each table should contain the following columns:
1. the current amount of scale deposited per unit length of perforated interval in a well
connection. (METRIC: gm/m, FIELD: lb/ f t ). Values must be increasing;
2. the corresponding reduction factor for the productivity index of the connection.
Initial productivity index is multiplied by this value.
Example
SCDATAB
0 1
36051.3058209 0.1 /
In the example one table of reduction coefficients for the productivity index of connections
is specified. In the first column values of scale deposited per unit length of perforated interval
in a well connection are set. in the second one reduction coefficients.
12.18.229. SCDATAB 1631

12.18.230 WSCTAB


Section
This keyword may be used to assign scale deposition (the keyword SCDPTAB (see
12.18.227)) and scale damage (the keyword SCDATAB (see 12.18.229)) tables to individual
wells.
Section Scale deposition model Scale deposition model.
Each line of the parameters should be ended by a symbol /. The data should be terminated
with a slash /.
1. well name, well name template and symbol * (i.e. a mask) or well list (the keyword
WLIST (see 12.18.26));
2. scale deposition table number;
3. scale damage table number.
Default:
scale deposition table number: 0. A value which is less or equal to 0 means that no
scale deposition table will be assigned to that well. So, there is no scale is deposited
around its connections.
scale damage table number: 0. A value which is less or equal to 0 means that no
scale damage table is assigned to that well. So, there is the well performance has no
influence from the currently deposited scale.
Example
WSCTAB
WA-1 1 1 /
WA-2 1 1 /
WA-3 1 1 /
/
In the example the keyword WSCTAB (see 12.18.230) assigns scale deposition and scale
damage tables to three wells (WA-1, WA-2, WA-3). In each case table z1 is assigned.
12.18.230. WSCTAB 1632

12.18.231 WSEGCNTL


Section
The keyword is used to specify settings of precision of equations system solution manu-
ally. The data should be terminated with a slash /.
1. well name;
2. residual value which leads to exit of Newtons iterations;
3. variation of main variables which leads to exit of Newtons iterations;
4. weight;
5. minimal variation from pressure in perforation which is used as initial approximation.
Default:
residual value which leads to exit of Newtons iterations: 1e-3;
variation of main variables which leads to exit of Newtons iterations: 1e-3;
weight: 0.5;
minimal variation from pressure in perforation which is used as initial approximation:

1.
Example
WSEGCNTL
W9 1e-1 100 1 0.3 /
In the example settings of precision of equations system solution are specified for well
W9.
12.18.231. WSEGCNTL 1633

12.18.232 PSEUPRES


Section
The keywords activates option of Generalized Pseudo-pressure (GPP) for all wells inflow
calculations. This keyword should be specified before any keyword which uses well opera-
tions or timesteps.
Additional parameters for this option should be specified via PICOND (see 12.18.187)
keyword.
Example
PSEUPRES
12.18.232. PSEUPRES 1634

12.18.233 GWRATMUL


Section
The keyword specifies group name, name of well, which enters into this group, and a
coefficient with which well enters into this group. This way only part of well rate can be
assigned to group rate. So, well rate can be divided into several groups.
1. group name;
2. name of well from specified group;
3. coefficient with which specified well enters into this group. This coefficient should
belong to interval from 0 to 1.
Several data lines can be specified. Each line should be ended by a symbol /. The data
Example
GWRATMUL
G1 W1 0.5 /
/
In the example well W1 enters into group G1 with coefficient 0.5, i.e. only half of the
well W1 rate will be assigned to the group G1 rate.
12.18.233. GWRATMUL 1635

12.18.234 APILIM


Section
This keyword is used to control API tracking calculation in simulator Eclipse.

In tNavigator this keyword is IGNORED due to different mathematical approach.
Fully implicit method is used for API calculation by default. It can be changed to explicit
via the keyword TRACEROPTS (see 12.7.3).
The list of supported keywords is in the section 2.10.
12.18.234. APILIM 1636

12.18.235 AUTOSAVE


Section
This keyword is used to control frequency of SAVE file writing in simulator Eclipse.
In tNavigator this keyword is IGNORED due to different approach to saving calculation
results.
12.18.235. AUTOSAVE 1637

12.18.236 WELLGR


Section
The keyword sets guide well rate values. Any number of data lines can be specified, each
of them should be ended by a symbol /. The data should be terminated with a slash /.
1. well name, well list name (see the keyword WLIST (see 12.18.26)) or name which
ends by *, i.e. mask;
2. flag indicating if the well is available for group control:
Y well is available for control by a parent group;

N well is not available for control by a parent group.
3. guide rate value;
4. guide rate type:
OIL oil production guide rate;

WAT water production guide rate;
GAS gas production guide rate;
LIQ liquid production guide rate;
WG wet gas production guide rate;
VP voidage production guide rate;
IG gas surface volume injection guide rate;
IW water surface volume injection guide rate;
VG gas voidage injection guide rate;
VW water voidage injection guide rate;
VI injection voidage guide rate (i.e. sets VG and VW simultaneously);
RV reservoir voidage guide rate (i.e. sets VP, VG and VW simultaneously);
INJ injection guide rate (sets IG and IW);
NONE no guide rate specified, potentials are used;
ALL set all guide rates.
12.18.236. WELLGR 1638

Default:
flag indicating if the well is available for group control: Y;
guide rate type: NONE;
Example
WELLGR
W10 Y 50.0 INJ /
/
In the example for well W10 gas surface volume injection and water surface volume
injection guide rates are specified. They are equal to 50 m3 /day.
12.18.236. WELLGR 1639

12.18.237 SLAVES


Section
This keyword is used in master model to start the simulation of the slave model in Reser-
voir coupling option. The detailed description of Reservoir Coupling is in the section 5.15.
This keyword should be entered in MASTER model only one time (the calculation of all
slaves should be started at one time).
Any number of lines can be specified, each one terminated with a slash /. The data
1. name of SLAVE (will be used later in the keyword GRUPMAST (see 12.18.238));
2. root name of the slave reservoirs data file;
3. this parameter should be defaulted (*) (the host name where the model should be
calculated; this is an Eclipse compatibility field);
4. path-name of the folder in which the data file is located, from the root folder of the
host.
Example
SLAVES
'SLAVE1' 'test1' * 'folder1'/
/
12.18.237. SLAVES 1640

12.18.238 GRUPMAST


Section
This keyword sets principal (master) and subordinate (slave) groups in Reservoir coupling
option. The detailed description of Reservoir Coupling is in the section 5.15.
1. master groups name or group name root. Master groups should be set in the keyword
GRUPTREE (see 12.18.85). They can not contains wells or subordinate groups;
2. the name of SLAVE model, containing the slave group associated with this one. Slave
group should be activated with the keyword SLAVES (see 12.18.237);
3. name of the master groups associated slave group in the slave reservoir. The names of
master and associated with it slave group can be different. For example, slave group
can be on the top level in its model and can have the name FIELD.
On the picture 32 there is a scheme of MASTER group and SLAVES that are set in this
example.
12.18.238. GRUPMAST 1641

Figure 32: Reservoir Coupling example
Example
GRUPTREE
G FIELD /
W FIELD /
W1 W /
W2 W /
W3 W /
G1 G /
G2 G /
G3 G /
/
GRUPMAST
W1 SLAVE1 W /
W2 SLAVE2 W /
W3 SLAVE3 W /
G1 SLAVE1 G /
G2 SLAVE2 G /
G3 SLAVE3 G /
/
GCONPROD FIELD WRAT 1* 80 /

G ORAT 40 /
W WRAT 1* 10 /
/
12.18.238. GRUPMAST 1642

12.18.239 GRUPSLAV


Section
This keyword sets slave group in the slave model in Reservoir coupling option. The de-
tailed description of Reservoir Coupling is in the section 5.15.
1. slave groups name or group name root. Groups are set via GRUPTREE (see 12.18.85)
or WELSPECS (see 12.18.3).
The slave model should contain one or more slave groups. They can be on different
levels in the group tree, but a slave group cannot be subordinate to another slave group.
Production or injection rate constraints that act for groups in higher level in group tree
should not be applied to the slave group;
2. name of the slave groups associated master group in the master model;
3. filter flag for oil production rate constraints: BOTH or MAST.

tNavigator checks the pairs of principal-subordinate groups, set using the keywords
GRUPMAST (see 12.18.238) and GRUPSLAV (see 12.18.239). Two options are
possible. If in MASTER model we have GRUPMAST (see 12.18.238) for the group
G in the model SLAVE1, and in the model SLAVE1:
the corresponding GRUPSLAV (see 12.18.239) is not specified, then the group
limits set in SLAVE1 continue to act on group G (option BOTH);
the corresponding GRUPSLAV (see 12.18.239) is specified, then its parameters
3-9 define if the group limits (specified in SLAVE1) will affect on the group G.
In particular if parameters 3-9 are not specified then GCONPROD (see 12.18.72),
GCONINJE (see 12.18.81) specified in SLAVE model for SLAVE group will be
ignored (option MAST).
4. filter flag for water and liquid production rate constraints. Analogously to parameter 3;
5. filter flag for gas production rate constraints. Analogously to parameter 3;
6. filter flag for reservoir fluid volume production rate constraints. Analogously to param-
eter 3;
12.18.239. GRUPSLAV 1643

7. filter flag for oil injection rate constraints. Analogously to parameter 3;
8. filter flag for water injection rate constraints. Analogously to parameter 3;
9. filter flag for gas injection rate constraints. Analogously to parameter 3.
Defauls:
parameters 3-9: MAST.
Example
GRUPSLAV
W W1 /
G G1 /
/
12.18.239. GRUPSLAV 1644

12.18.240 CSKIN


Section
The keyword updates skin factor values for specified perforations. Single data line should
contain the following parameters:
2. I coordinate of block with perforation;
3. J coordinate of block with perforation;
4. upper K coordinate of block with perforation;
5. lower K coordinate of block with perforation;
6. skin factor value.
Any number of data lines can be specified. Each of them should be ended by the symbol
Default:
I coordinate of block with perforation: 0;
J coordinate of block with perforation: 0;
upper K coordinate of block with perforation: coordinate of top connection of well;
bottom K coordinate of block with perforation: coordinate of bottom connection of

well;
skin factor value: 0.
Example
CSKIN
'*' 4* -1 /
/
In this example skin factor for all perforations of each well is -1.
12.18.240. CSKIN 1645

12.18.241 WFOAM


Section
The keyword sets foam concentration in injecting stream. It can be used only if foam
model option (see 2.21) is activated by the keyword FOAM (see 12.1.64). The following
2. foam concentration in injecting stream. Units depends on the first parameter of

FOAMOPTS (see 12.11.2):

One can set any number of data lines. Each data line should be ended by the symbol
Example
WFOAM
'INJECTOR' 1.1 /
/
In the example foam concentration in the stream which is injected by well INJECTOR is
1.1 lb/stb.
12.18.241. WFOAM 1646

13. Keywords compatible with tNavigator and IMEX, STARS, GEM tNavigator-4.2
13 Keywords compatible with tNavigator and IMEX,

STARS, GEM
model formats:
tNavigator;
IMEX;
STARS;
GEM.
tNavigator or which use is different from CMG.
For convenience keyword are grouped in several sections similar to IMEX, STARS, GEM
sections.
Input Input/Output Control (13.2)
Reservoir Reservoir description (13.3)
Other Other Reservoir Properties (13.4)
Component Component properties (13.5)
Rockfluid Rock-Fluid data (13.6)
Initial Initial conditions (13.7)
Numerical Numerical methods control (13.8)
Well Well and recurrent data (13.9)
13. Keywords compatible with tNavigator and IMEX, STARS, GEM 1647
13.1. Data entry system tNavigator-4.2
13.1 Data entry system
13.1. Data entry system 1648

13.1.1 MATRIX

format E100 x IMEX x STARS
Input x Reservoir Other Component

Section
Rockfluid Initial Numerical Well
The keyword is used after keywords which set grid properties. The keyword specifies that
properties correspond to matrix blocks.
In dual porosity run (DUALPORO (see 12.1.76)) both MATRIX and FRACTURE (see
13.1.2) are used. FRACTURE (see 13.1.2) specifies fracture properties.
Example
PERMI MATRIX ALL
25.5188 25.841 26.0421 26.0878 25.9532 25.6303 25.1359
24.5015 23.7728
This example sets X-direction permeabilities for 9 matrix blocks.
13.1.1. MATRIX 1649

13.1.2 FRACTURE


Section
The keyword is used after keywords which set grid properties. The keyword specifies that
properties correspond to fracture blocks.
In dual porosity run (DUALPORO (see 12.1.76)) both FRACTURE and MATRIX (see
13.1.1) are used. MATRIX (see 13.1.1) specifies matrix properties.
Example
POR FRACTURE ALL
0.114087 0.114805 0.115251 0.115352 0.115054 0.114336
0.113228 0.11179
This example sets porosity for 9 fracture blocks.
13.1.2. FRACTURE 1650

13.1.3 CON

The keyword is used after the keyword, if constant value array is entered. After CON one
should specify the value (which is equal to all array elements).
Example
DIFRAC CON 0.1
PB MATRIX CON 6500
The keyword sets the distances between fractures (matrix block sizes) in X-direction
DIFRAC are equal to 0.1. Bubble point pressure for matrix blocks PB is equal to 6500.
13.1.3. CON 1651

13.1.4 IVAR / JVAR / KVAR


Section
The keywords specify common constant values for all blocks of the layer in X -, Y -
and Z -direction. IVAR (see 13.1.4) specifies common value for blocks of the layer in X -
direction, JVAR (see 13.1.4) - in Y -direction, KVAR (see 13.1.4) - in Z -direction. The
value assigned to blocks for each layer in X - / Y - / Z -direction correspondingly. The

number of values should be equal to the number of layers in corresponding direction.
Example
HEATR KVAR
4*0 1500 5*0
In the example for 10 layers of the model heat transfer rate values are specified (the
keyword HEATR (see 13.9.1)). In all blocks of the layer in Z -direction transfer rate is the
same. Values are equal to 0 in the first 4 layers, 1500J/day in the fifth one and 0 for five
other layers of the model.
13.1.4. IVAR / JVAR / KVAR 1652

13.2. Input/Output Control tNavigator-4.2
13.2 Input/Output Control
13.2. Input/Output Control 1653

13.2.1 TITLE1 / TITLE2 / TITLE3

x Input Reservoir Other Component

Section
The keyword is used to specify model name (this name can consist of letters and num-
bers).
It has an Eclipse compatible analogue TITLE (see 12.1.2).
Example
TITLE1 'Model number 1'
This example sets the model name Model number 1.
13.2.1. TITLE1 / TITLE2 / TITLE3 1654

13.2.2 INUNIT

x Input Reservoir Other Component

Section
The keyword is used to specify units system. The data can be read by tNavigator in
following units:
SI;
LAB;
FIELD.
Also, one can change pressure unit from kPa to bar in SI by the keyword. It can be
done by the following command:
Example
INUNIT SI EXCEPT 3 3
Example
INUNIT FIELD
The keyword sets FIELD units system.
13.2.2. INUNIT 1655

13.3. Reservoir description tNavigator-4.2
13.3 Reservoir description
13.3. Reservoir description 1656

13.3.1 GRID


Section
The keyword sets the reservoir grid. In the Reservoir description section 13.3 it must
be used first. The following parameters should be specified:
1. type grid: CART / VARI / CORNER
CART - rectangular Cartesian grid will be used;

VARI - rectangular grid will be used. Variable depth/thickness layers can be set
for this grid;
CORNER - rectangular grid will be used. In this grid location of block is defined
by eight coordinates of it tops. Each top is defined by x , y and z coordinates.
2. ni - the number of blocks in X -direction;
3. n j - the number of blocks in Y -direction;
4. nk - the number of blocks in Z -direction;
Example
GRID VARI 150 1 6
In the example rectangular grid is set. The number of blocks in X -direction is 150, the
number of blocks in Y -direction is 1, the number of blocks in Z -direction is 6. Variable
depth/thickness layers can be set for this grid.
13.3.1. GRID 1657

13.3.2 DI / DJ / DK


Section
The keywords specify block length. DI (see 13.3.2) specifies block length along X -
direction, DJ (see 13.3.2) - specifies one along Y -direction, DK (see 13.3.2) - specifies one
along Z -direction. The following parameters should be specified:
1. block lengths (SI: m, FIELD: f t ). The number of input lengths should be equal to the
number of blocks along corresponding direction.
Example
GRID VARI 150 1 6
DI IVAR
150*5
DJ JVAR
1
DK ALL
600*2 150*1 150*1.5
In the example block lengths along three directions are specified: length of each block
along X -direction is equal to 5 m, the one along Y -direction is equal to 1 m, along Z -
direction 600 blocks have length 2 m, 150 ones have length 1 m, and other 150 blocks have
length 1.5 m.
13.3.2. DI / DJ / DK 1658
13.3.3 ZCORN


Section
The keyword enables the depths of each corner of each grid block (8 corners) to be
separately specified.
It has an Eclipse compatible analogue ZCORN (see 12.2.9). Data input is identical with
this keyword.
13.3.3. ZCORN 1659

13.3.4 COORD


Section
The keyword is used to specify coordinate lines in Z-direction.

It has an Eclipse compatible analogue COORD (see 12.2.8). Data input is identical with
this keyword.
13.3.4. COORD 1660

13.3.5 DUALPOR


Section
The keyword sets dual porosity run. One should specify matrix block properties and
fracture block properties using keywords MATRIX (see 13.1.1) and FRACTURE (see 13.1.2).
It has an Eclipse compatible analogue DUALPORO (see 12.1.76).
Example
DUALPOR
13.3.5. DUALPOR 1661

13.3.6 SHAPE


Section
The keyword sets the type of shape factor which will be used in calculation of matrix-
fracture flows in dual porosity run.
There are two possible types:
GK (Gilman and Kazemi) Matrix-fracture flow in one block is proportional to trans-

missibility:
20 1 1 1
k ( + + )2 MV
3 lx ly lz
k permeability, lx, ly, lz distances between fractures in X, Y and Z directions,
entered using keywords DIFRAC / DJFRAC / DKFRAC (see 13.3.7), MV matrix
volume.
WR (Warren and Root) Matrix-fracture flow in one block is proportional to transmis-

sibility:
1 1 1
4 k ( 2 + 2 + 2 ) MV
lx ly lz
Current version of Navigator support only GK type.
It has an Eclipse compatible analogue VISCD (see 12.1.82). VISCD sets that the viscous
displacement option will be used (matrix-fracture flows), but doesnt specify the type of
shape-factor. Eclipse compatible analogue sigma-factor (keywords SIGMA (see 12.2.67),
LTOSIGMA (see 12.2.69)).
Example
SHAPE GK
13.3.6. SHAPE 1662

13.3.7 DIFRAC / DJFRAC / DKFRAC


Section
The keyword sets the distances between fractures (matrix blocks sizes) in X, Y and Z
directions. The keywords can be used if DUALPOR (see 13.3.5) is enable. Matrix-fracture
flows are calculated using this keyword (one can observe formula in the description of the
keyword SHAPE (see 13.3.6)).
It has an Eclipse compatible analogue LX / LY / LZ (see 12.2.64).
13.3.7. DIFRAC / DJFRAC / DKFRAC 1663

13.3.8 NULL


Section
The keyword sets if block is active or inactive (doesnt participate in the run).
0 inactive block,
1 active block.
Default: all blocks are active.
It has an Eclipse compatible analogue ACTNUM (see 12.2.29).
Example
NULL MATRIX 22*1 3*0
This example sets first 22 matrix blocks active, next 3 - inactive. However inactive block
is set only for matrix (MATRIX (see 13.1.1)), flows can appear for fracture part FRACTURE
(see 13.1.2).
13.3.8. NULL 1664

13.3.9 POR


Section
The keyword sets porosity values (between 0 and 1). Reference pressure at which these
porosities are given, is specified using the keyword PRPOR (see 13.4.4).
The description of models that can be used in tNavigator (Linear Elastic, Nonlinear Elastic,
Dilation- Recompaction) is in the section 4.24.
It has an Eclipse compatible analogue PORO (see 12.2.24).
Example
POR MATRIX ALL
0.114087 0.114805 0.115251 0.115352 0.115054 0.114336
0.113228 0.11179
POR FRACTURE ALL
0.110115 0.108315 0.106498 0.104755 0.103144 0.10169 0.100393
0.0992395
This example sets porosity for 8 blocks (values are different for matrix and fracture
blocks).
13.3.9. POR 1665

13.3.10 PERMI / PERMJ / PERMK


Section
These keywords specify absolute permeabilities in X (PERMI), Y (PERMJ), Z (PERMK)

directions. In dual porosity run (DUALPOR (see 13.3.5)) one should enter permeabilities for
matrix blocks (MATRIX (see 13.1.1)) and fracture blocks (FRACTURE (see 13.1.2)). MA-
TRIX permeabilities are used in calculations of matrix-fracture flows and matrix-matrix flows
(in dual permeability run). FRACTURE permeabilities are used in calculations of fracture-
fracture flows.
Three keywords have an Eclipse compatible analogue PERMX / PERMY / PERMZ (see
12.2.13).
Example
PERMI MATRIX ALL
25.5188 25.841 26.0421 26.0878 25.9532 25.6303 25.1359
24.5015 23.7728
PERMI FRACTURE ALL
2551.88 2584.1 2604.21 2608.78 2595.32 2563.03 2513.59
2450.15 2377.28
This example sets absolute permeabilities for 9 matrix and fracture blocks.
13.3.10. PERMI / PERMJ / PERMK 1666

13.3.11 NETGROSS


Section
The keyword sets net to gross values of grid blocks. The same number of values as
number of blocks must be specified.
It has an Eclipse compatible analogue NTG (see 12.2.25).
Example
NETGROSS FRACTURE CON 0.32
NETGROSS MATRIX CON 0.32
This example sets net to gross values of matrix and fracture grid blocks equal to 0.32
(dual porosity model).
13.3.11. NETGROSS 1667

13.3.12 PINCHOUTARRAY


Section
The keyword sets pinched out blocks and not pinched out blocks (blocks with small void
volume are not used in the calculations). One should specify the same number of values as
the number of blocks in the model.
0 block is pinched out,
1 block is not pinched out.
This keyword has an Eclipse compatible analogues PINCH (see 12.2.54), PINCHREG
(see 12.2.56), PINCHNUM (see 12.2.57).
Example
PINCHOUTARRAY CON 1
This example sets that no one block is pinched out.
13.3.12. PINCHOUTARRAY 1668

13.3.13 VOLMOD


Section
The keyword sets a multiplier (x, y, z) for each grid block. Geometric volume Vgeom is
multiplied by (x, y, z). The same number of values should be specified as the number of
grid blocks.
Bulk grid block volume section 4.26, pore block volume section 4.25.
The keyword has an Eclipse compatible analogue MULTPV (see 12.2.28).
Default: 1.
Example
VOLMOD
120*2 200*1 2500*3
In this example (x, y, z) in 120 blocks is 2, in 200 blocks 1, in 2500 blocks 3.
13.3.13. VOLMOD 1669

13.3.14 NETPAY


Section
The keyword defines net thickness of grid blocks. Net thickness values are used in
porosity calculations. The description of models that can be used in tNavigator (Linear
Elastic, Nonlinear Elastic, Dilation-Recompaction) is in the section 4.24.
This keyword is fully analogous to the keyword DZNET (see 12.2.26) which is used by
Eclipse. More details are in DZNET (see 12.2.26) description.
13.3.14. NETPAY 1670

13.3.15 AQLEAK


Section
The keyword specifies whether waterflow from reservoir into the aquifer is allowed where
the block pressure is higher than the aquifer pressure.
ON - waterflow is allowed;
OFF - waterflow is denied;
By default: OFF.
Example
AQLEAK ON
13.3.15. AQLEAK 1671

13.3.16 AQMETHOD
Data x tNavigator E300 MORE x GEM


Section
The keyword specifies the aquifer type in a model.
CARTER-TRACY Carter-Tracys aquifer;
FETKOVITCH Fetkovitchs aquifer.
SEMI-ANALYTICAL semi-analytical aquifer.
By default: CARTER-TRACY.
The keyword has an Eclipse compatible analogues AQUCT (see 12.16.8), AQUFET (see
12.16.4).
13.3.16. AQMETHOD 1672

13.3.17 AQVISC


Section
The keyword sets aquifer water viscosity. It can be used only with SEMI-ANALYTICAL
aquifer type (see AQMETHOD (see 13.3.16)).
1. aquifer water viscosity (cp).
Default:
if this keyword is omitted, then calculated water viscosity is taken.
Example
AQVISC 0.61
13.3.17. AQVISC 1673

13.3.18 AQPROP


Section
The keyword specifies aquifers properties. The following parameters should be specified:
1. thickness (SI: m, FIELD: f t );
2. porosity;
3. permeability (SI: mD, FIELD: mD);
4. radius (SI: m, FIELD: f t );
5. angle of influence (expressed by a fraction (a ratio to 360 )).
Radius and angle of influence should be specified for Carter-Tracy and Fetkovitch aquifer.
For SEMI-ANALYTICAL model one should enter 0 value.
By default:
thickness: For this parameter default value is supported according to the logic of STARS
syntax.
porosity: average porosity of reservoir (For this parameter default value is supported
according to the logic of STARS syntax.)
permeability: average permeability of reservoir in aquifer flow direction (For this pa-
rameter default value is supported according to the logic of STARS syntax.)
radius: For this parameter default value is supported according to the logic of STARS
syntax.
angle of influence: For this parameter default value is supported according to the logic
of STARS syntax.
The keyword has an Eclipse compatible analogues AQUCT (see 12.16.8), AQUNUM (see
12.16.11).
Example
INUNIT FIELD
...
AQPROP
100 0.28 70 15500 0.2
13.3.18. AQPROP 1674

In the example is specified aquifer with following properties: thickness is equal to 100
f t , porosity is equal to 0.28, permeability is equal to 70 mD, radius is equal 15500 f t and
angle of influence is equal to 72 degrees (as one fifth of 360 ).
13.3.18. AQPROP 1675

13.3.19 AQUIFER


Section
The keyword specifies the aquifer location in a model. tNavigator supports one option to
specify it:
BOTTOM aquifer will be connected to the bottom of reservoir;
BOUNDARY aquifer will be connected to all boundary blocks of reservoir except

inactive ones;
RESBND aquifer will be connected to all boundary blocks of reservoir including

inactive ones.
REGION aquifer will be connected to arbitrary blocks. Coordinates of these blocks

are specified by intervals i1 (: i2), j1 (: j2), k1 (: k2) correspondingly in I -, J -
, K -directions. When this option is used, one of the following parameters can be
specified:
[additional parameter] IDIR, JDIR or KDIR aquifer will be connected to the

reservoir boundary block in the specified direction.
The keyword has an Eclipse compatible analogue AQUANCON (see 12.16.10).
Example
AQUIFER REGION 1:3 1:187 1:35 IDIR
In the example an aquifer is connected to specified blocks in I -direction.
13.3.19. AQUIFER 1676

13.3.20 AQFUNC


Section
The keyword is full analog of the keyword AQUTAB (see 12.16.9).
13.3.20. AQFUNC 1677

13.3.21 DUALPERM


Section
The keyword sets dual permeability run. One should specify matrix block properties and
fracture block properties using keywords MATRIX (see 13.1.1) and FRACTURE (see 13.1.2).
It has an Eclipse compatible analogue DUALPERM (see 12.1.77).
13.3.21. DUALPERM 1678

13.3.22 CORNERS


Section
The keyword is an analog of the keyword CORNERS (see 12.2.102) which is used by
tNavigator.
The keyword sets coordinates of block grid tops (METRIC: m, FIELD: f t ).
Data specification.
In case if in the model there are nx ny nz blocks, then one should set 3 8 nx ny nz
coordinates of their tops. The order is the following:
8 nx ny nz - X coordinates of blocks;
8 nx ny nz - Y coordinates of blocks;
8 nx ny nz - Z coordinates of blocks.
13.3.22. CORNERS 1679

Example
CORNERS
0 50 50 100
0 50 50 100
0 50 50 100
0 50 50 100
0 50 50 100
0 50 50 100
0 50 50 100
0 50 50 100
0 0 0 0
50 50 50 50
50 50 50 50
100 100 100 100
0 0 0 0
50 50 50 50
50 50 50 50
100 100 100 100
500 500 500 500
500 500 500 500
500 500 500 500
500 500 500 500
502 502 502 502
502 502 502 502
502 502 502 502
502 502 502 502
In the example grid of 2x2x1-size is specified. Length of block along x - and y-directions
is equal to 50 m, along z-direction it is equal to 2 m. Deep of a top layer is 500 m, thats
why z-coordinates of a top layer is 500.
13.3.22. CORNERS 1680

13.3.23 CROCKTYPE

format E100 x IMEX STARS

Section
The keyword is used if it is necessary to specify more than one types of rock in different
regions of grid or specify table of transmissibility and porosity dependence on pressure (the
keyword CROCKTAB (see 13.3.26)).
1. number of a rock type.
Example
CROCKTYPE 1
CROCKTAB
490 0.971 0.105 0.105
800 0.972 0.105 0.105
1300 0.974 0.11 0.11
1800 0.975 0.115 0.115
In the example for the 1-st type of rock the table of transmissibility and porosity depen-
dence on pressure is specified.
13.3.23. CROCKTYPE 1681

13.3.24 CTYPE


Section
The keyword set rock type number for each grid block. The following parameters should
be specified:
1. rock type number for each grid block.
Rock type is defined via the keywords CROCKTYPE (see 13.3.23) and CROCKTAB (see
13.3.26). Keywords ROCKNUM (see 12.4.14) and ROCKOPTS (see 12.5.21) which are
used by Eclipse are analogs for this keyword.
Example
CTYPE KVAR 1 2 3 4 5
In the example 5 different rock properties are set for 5 grid layers.
13.3.24. CTYPE 1682

13.3.25 CCPOR


Section
The keyword is equivalent to the keyword CPOR (see 13.4.5), but there is a difference:
CCPOR (see 13.3.25) is used to set the rock compressibility coefficient c p only in region
which is specified by CROCKTYPE (see 13.3.23). So, the keyword should be used after the
keyword CROCKTYPE (see 13.3.23).
13.3.25. CCPOR 1683

13.3.26 CROCKTAB


Section
This keyword is used to set tables of transmissibility and porosity dependence on pressure
for each rock region. The following parameters are to be specified (one table row):
1. pressure (SI: kPa , FIELD: psia). Minimal value is 101 kPa (14.7 psia). Values
should increase down the column;
2. porosity multiplier. Values should be the same or increase down the column;
3. horizontal transmissibility multiplier;
4. vertical transmissibility multiplier.
By default:
horizontal transmissibility multiplier: 1;
vertical transmissibility multiplier: horizontal transmissibility multiplier.
The keyword has an Eclipse compatible analogue ROCKTAB (see 12.5.18).
Example
CROCKTYPE 1
CROCKTAB
490 0.971 0.105 0.105
800 0.972 0.105 0.105
1300 0.974 0.11 0.11
1800 0.975 0.115 0.115
In the example the table of transmissibility and porosity dependence on pressure is spec-
ified for the 1st type of rock.
13.3.26. CROCKTAB 1684

13.3.27 TRANSI / TRANSJ / TRANSK


Section
The keywords specify transmissibility multipliers in I , J and K directions correspond-

ingly. The following parameters should be specified:
1. transmissibility multipliers in corresponding directions. The number of multipliers must

be equal to the number of grid blocks.
By default:
transmissibility multipliers: 1.0.
These keywords have Eclipse-compatible analogues MULTX (see 12.2.15), MULTY (see
12.2.17) and MULTZ (see 12.2.19).
Example
TRANSI
1.1 1.6 1.2 1.2 1.1 1.8 1.4 1.0
In the example transmissibility multipliers in I direction specified for 8 blocks of grid.
13.3.27. TRANSI / TRANSJ / TRANSK 1685

13.3.28 TRANLI / TRANLJ / TRANLK


Section
These keywords are full analogs of keywords MULTX- (see 12.2.16), MULTY- (see
12.2.18) and MULTZ- (see 12.2.20) correspondingly.
13.3.28. TRANLI / TRANLJ / TRANLK 1686

13.3.29 TRANSF


Section
The keyword sets coordinates of fault cells and multipliers of transmissibility between
them. The following parameters should be specified:
in the line with the keyword:
1. single quoted fault name;

2. transmissibility multiplier for this fault;
in the next line cells coordinates and fault direction are specified:
1. X-coordinate of starting cell of the fault;

2. Y-coordinate of starting cell of the fault;
3. Z-coordinate of starting cell of the fault;
4. fault direction:
IDIR / JDIR / KDIR I-, J- and K-direction correspondingly. In this case
X-, Y- and Z-coordinates of neighbor cell in specified direction should be
specified further;
IDIR+ / IDIR- / JDIR+ / JDIR- / KDIR+ / KDIR- I+/-, J+/- and K+/-
directions correspondingly. In this case it is considered that connections are
set for all cells in this direction starting from specified cell. Sign + means
cells which have specified coordinate greater will be selected; sign - means
the same about lesser coordinate.
These keyword has Eclipse-compatible analogues FAULTS (see 12.2.37) and MULTFLT
(see 12.2.38).
Example
TRANSF 'fault1' 0
1 1 1 IDIR 2 1 1
In the example transmissibility multiplier between neighbor cells (1,1,1) and (2,1,1) is
equal to 0. That is, connection between them is eliminated.
13.3.29. TRANSF 1687

13.3.30 FRFRAC


Section
This keyword should be used in dual porosity model. The keyword sets value fracture
volume in a cell as a fraction of the cell volume.
1. value of cell volume fraction which corresponds to fracture volume.
Default:
if fracture doesnt contain rock, then the FRFRAC value is equal to porosity fracture
value;
if this keyword is absent, then the fracture doesnt contain rock.
Example
FRFRAC ALL
0.7
In the example for all cells value fracture volume in a cell is set. It is equal to 0.7.
13.3.30. FRFRAC 1688

13.3.31 FORMINFRAC


Section
This keyword should be used in dual porosity model. It sets value of ratio between rock
volume in fracture and fracture volume.
1. value of ratio between rock volume in fracture and fracture volume.
Default:
if the keyword is absent, then fracture doesnt contain rock.
Example
FORMINFRAC ALL
0.4
In the example for each cell value of ratio between rock volume in fracture and fracture
volume is set. It is equal to 0.4.
13.3.31. FORMINFRAC 1689

13.3.32 SECTORARRAY


Section
The keyword specifies named FIP-region.

1. FIP-region name;
2. coordinate of the first cell along X-direction;
3. coordinate of the last cell along X-direction;
4. coordinate of the first cell along Y-direction;
5. coordinate of the last cell along Y-direction;
6. coordinate of the first cell along Z-direction;
7. coordinate of the last cell along Z-direction.
8. number of this FIP-region.
First and last coordinates along the same axis should be separated by a colon. If only one
layer is needed to specify, then second coordinate can be omitted (see the example).
Example
SECTORARRAY 'ABC' 1:7 2:9 2 1
In the example the keyword SECTORARRAY (see 13.3.32) specifies FIP-region ABC.
Layers 1-7 along X-axis, 2-9 along Y-axis and 7 along Z-axis are selected.
13.3.32. SECTORARRAY 1690

13.3.33 DEPTH


Section
The keyword sets reservoir depth of specified block. The following parameters should be
specified:
1. TOP or CENTRE:
TOP flag indicating that the depth of the centre of the top block face is specified;
CENTRE flag indicating that the depth of the block centre is specified.
2. coordinate i of the block;
3. coordinate j of the block;
4. coordinate k of the block;
5. block depth (METRIC: m; SI: f t ).
This keyword has an Eclipse compatible analogue DEPTH (see 12.3.27).

Default:
TOP or CENTRE: if nothing is specified, then CENTRE.
Example
DEPTH 1 1 1 600
13.3.33. DEPTH 1691

13.3.34 DTOP


Section
The keyword sets depths of the centre of the top face of each grid block in the top layer
of the grid. The following parameters should be specified:
1. depths of the centre of the top face of each grid block in the top layer of the grid
(METRIC: m; SI: f t ). ni n j values should be specified.
Example
DTOP 10*1200
In the example all blocks of the top layer has depths 1200 m.
13.3.34. DTOP 1692

13.3.35 PVCUTOFF


Section
The keyword sets pore volume value. All blocks which pore volume is less than specified
are considered to be blocks with zero pore volume. The following parameters should be
specified:
1. pore volume margin value (METRIC: m3 ; SI: f t 3 ).
This keyword has an Eclipse compatible analogue MINPV (see 12.2.30).
Example
PVCUTOFF 1000
In the example all blocks which pore volume is less than 1000 f t 3 are considered to be
blocks with zero pore volume.
13.3.35. PVCUTOFF 1693

13.3.36 REFINE


Section
The keyword specifies local grid refinement. The following parameters should be speci-
fied:
1. coordinates of block to refine. Block to refine can be specified by 2 following ways:
one-level refinement. Three coordinates of the block (x, y, z) or coordinates of

blocks interval (x1 : x2 , y1 : y2 , z1 : z2 ) are specified. Each block of the interval will
be refined;
multi-level refinement. It is used when you need to refine block which is already
refined. Three coordinates of the block (x, y, z) are specified, then it is refining,
then three coordinates inside result block are specified and so on. See example.
2. flag INTO which signals about new refinement;
3. number of refined blocks in the I direction inside each block to refine;
4. number of refined blocks in the J direction inside each block to refine;
5. number of refined blocks in the K direction inside each block to refine.
This keyword has an Eclipse compatible analogue CARFIN (see 12.2.87).
Example
REFINE 1:2 2:3 1 INTO 2 3 3
In the example 4 blocks are refined: blocks of the 1-st and 2-nd layer in X direction, of
the 2-nd and 3-rd layers in Y direction and of the 1-st layer in Z direction. Each of them
will be refined on 2 blocks in X direction, and on 3 blocks in Y and Z directions.
Example
REFINE 2 3 2 / 2 2 2 INTO 2 3 2
In the example multi-level refinement is used. Block (2,3,2) is refined on 2 blocks in X

and Z directions, and on 3 in Y direction. Then block (2,2,2) inside refined block is refined
on 2 blocks in X and Z directions, and on 3 in Y direction.
13.3.36. REFINE 1694

13.3.37 SCONNECT


Section
The keyword sets non-neighbor connection between two cells. The following parameters
1. I -coordinate of the first cell;
4. I -coordinate of the second cell;
7. transmissibility value (METRIC: md -m; FIELD: md - f t ).
This keyword has an Eclipse compatible analogue NNCGEN (see 12.2.50).
Example
SCONNECT 2 1 2 10 1 3 100
In the example the keyword SCONNECT (see 13.3.37) sets connection between cells
(2,1,2) and (10,1,3). Transmissibility value is 100 md - f t .
13.3.37. SCONNECT 1695

13.4. Other Reservoir Properties tNavigator-4.2
13.4 Other Reservoir Properties
13.4. Other Reservoir Properties 1696

13.4.1 ROCKTYPE

Input Reservoir x Other Component

Section
The keyword is used to define multiple rock regions.

This keyword sets the number of rock region the following rock properties are assigned to.
Rock properties: PRPOR (see 13.4.4), CPOR (see 13.4.5), CTPOR (see 13.4.6), ROCKCP
(see 13.4.3), THCONG (see 13.4.11), THCONO (see 13.4.10), THCONS (see 13.4.12),
THCONR (see 13.4.8), THCONW (see 13.4.9), THCONMIX (see 13.4.13), HLOSST (see
13.4.14), HLOSSPROP (see 13.4.16), HLOSSTDIFF (see 13.4.15).
The keyword THTYPE (see 13.4.2) specifies for each grid block the number of rock
region to which it belongs.
Example
ROCKTYPE 1
PRPOR 16450
CPOR 1.2e-6
CTPOR 0.00015
ROCKCP 2.3E6 0
THCONR 187000
THCONS 5.1E5
THCONW 5.12E4
THCONO 1.22E4
THCONG 4000
THCONMIX SIMPLE
ROCKTYPE 2
PRPOR 16450
CPOR 1.4e-8
CTPOR 0.00015
ROCKCP 2.3E6 0
THCONR 187000
THCONS 4.5E5
THCONW 5.35E4
THCONO 1.11E4
THCONG 4000
THCONMIX SIMPLE
In this example rock properties are specified for 2 rock regions.
13.4.1. ROCKTYPE 1697

13.4.2 THTYPE


Section
The keyword is used to define multiple rock regions.

The keyword THTYPE (see 13.4.2) specifies for each grid block the number of rock region
to which it belongs. Only the number of rock region that has been defined earlier via ROCK-
TYPE (see 13.4.1) is allowed.
Default: all grid blocks belong to one region.
The keyword has an Eclipse compatible analogue ROCKNUM (see 12.4.14).
Example
ROCKTYPE 1
...
ROCKTYPE 2
...
THTYPE CON 2
In this example all grid blocks belong to the 2-nd rock region.
13.4.2. THTYPE 1698

13.4.3 ROCKCP


Section
The keyword sets the coefficients CP1 , CP2 of the rock enthalpy formula 4.51:
1
HR (T ) = (CP1 (T Tre f ) + CP2 (T Tre f )2 )
2
Tre f is set via TEMR (see 13.5.11).
1. CP1 (SI: J/m3 /C , FIELD: Btu/ f t 3 / F ),
2. CP2 (SI: J/m3 /C/C , FIELD: Btu/ f t 3 / F/ F ).
Different values can be entered for different rock regions (see an example in the descrip-
tion of ROCKTYPE (see 13.4.1)).
Default: CP1 = 2347kJ/m3 , CP2 = 0.
The keyword has an Eclipse compatible analogues HEATCR (see 12.14.10), HEATCRT
(see 12.14.11).
In tNavigator the coefficients CP1 , CP2 can be specified via the keyword HEATTCR
(see 12.14.12).
Example
ROCKTYPE 1
ROCKCP 3204500 0
In this example the coefficients of the rock enthalpy formula are specified for one rock
region.
13.4.3. ROCKCP 1699

13.4.4 PRPOR


Section
For models in IMEX, GEM data format these keywords should be in the section Reservoir
(Reservoir properties), for models in STARS format Other (Other reservoir properties).
The keyword sets the reference pressure pre f (SI: kPa, FIELD: psi), which is used in
porosity calculations.
Default: if PRPOR (see 13.4.4) is absent

for IMEX, GEM models: 1 atm;
for STARS models: the reference pressure is equal to the pressure in the first active
grid block.
The keyword is analogous to the 1-st parameter of Eclipse compatible keyword ROCK
(see 12.5.16).
Example
PRPOR 16550
In this example the reference pressure is 16550kPa.
Example
PRPOR FRACTURE 17820
PRPOR MATRIX 17820
CPOR FRACTURE 1e-6
CPOR MATRIX 1e-7
This example sets equal reference pressures for matrix and fracture parts and different
rock compressibility coefficients.
13.4.4. PRPOR 1700

13.4.5 CPOR


Section
For models in IMEX data format these keywords should be in the section Reservoir
(Reservoir properties), for models in STARS format Other (Other reservoir properties).
The keyword sets the rock compressibility coefficient c p (SI: 1/kPa, FIELD: 1/psi),
which is used in porosity calculations.
Different values can be entered for different rock regions (see an example in the description
of ROCKTYPE (see 13.4.1)).
Default: 0.
The keyword is analogous to the 2-nd parameter of Eclipse compatible keyword ROCK
(see 12.5.16).
Example
CPOR 1.3e-6
In this example the rock compressibility coefficient is 1.3e-61/kPa.
Example
PRPOR FRACTURE 17820
PRPOR MATRIX 17820
CPOR FRACTURE 1e-6
CPOR MATRIX 1e-7
This example sets equal reference pressures for matrix and fracture parts and different
rock compressibility coefficients.
13.4.5. CPOR 1701

13.4.6 CTPOR


Section
The keyword sets the effective thermal expansion coefficient of the formation cT (SI:
1/C , FIELD: 1/F ), which is used in porosity calculations.
Default: 0.
The keyword is analogous to the 1-st parameter of ROCKT (see 12.14.17), which is used
in tNavigator.
Example
CTPOR 0.00012
In this example the effective thermal expansion coefficient is 0.000121/C .
13.4.6. CTPOR 1702

13.4.7 CPTPOR


Section
The keyword sets the pressure-temperature cross-term coefficient of the formation effec-
tive porosity c pT (SI: 1/kPa C , FIELD: 1/psi F ), which is used in porosity calculations.
Default: 0.
The keyword is analogous to the 2-nd parameter of ROCKT (see 12.14.17), which is used
in tNavigator.
Example
CPTPOR 0.000042
In this example the pressure-temperature cross-term coefficient of the formation effective

porosity is 0.0000421/kPa C .
13.4.7. CPTPOR 1703

13.4.8 THCONR


Section
The keyword specifies the rock thermal conductivity kR (SI: J/m/day/C , FIELD:
Btu/ f t day F ), which is used in the block thermal conductivity calculations 4.66 when
THCONMIX (see 13.4.13) sets the option SIMPLE:

Default: 149.6kJ/m/day/C .
The keyword has an Eclipse compatible analogue THCONR (see 12.14.15).

The keyword is analogous to the 1-st parameter THCONT (see 12.14.18), which is used in
tNavigator.
Example
THCONR 187000
In this example the rock thermal conductivity is 187000J/m/day/C .
13.4.8. THCONR 1704

13.4.9 THCONW


Section
The keyword specifies the water thermal conductivity kW (SI: J/m/day/C , FIELD:

The keyword is analogous to the 2-nd parameter THCONT (see 12.14.18), which is used
in tNavigator.
Example
THCONW 4.85E4
In this example the water thermal conductivity is 4.85E4J/m/day/C .
13.4.9. THCONW 1705

13.4.10 THCONO


Section
The keyword specifies the oil thermal conductivity kO (SI: J/m/day/C , FIELD:

The keyword is analogous to the 3-rd parameter THCONT (see 12.14.18), which is used
in tNavigator.
Example
THCONO 2.03E4
In this example the oil thermal conductivity is 2.03E4J/m/day/C .
13.4.10. THCONO 1706

13.4.11 THCONG


Section
The keyword specifies the gas thermal conductivity kG (SI: J/m/day/C , FIELD:
Btu/ f t/day/F ), which is used in the block thermal conductivity calculations 4.66 when

The keyword is analogous to the 4-th parameter THCONT (see 12.14.18), which is used
in tNavigator.
Example
THCONG 3800
In this example the gas thermal conductivity is 3800J/m/day/C .
13.4.11. THCONG 1707

13.4.12 THCONS


Section
The keyword specifies the solid phase thermal conductivity kS (SI: J/m/day/C , FIELD:

The keyword is analogous to the 5-th parameter THCONT (see 12.14.18), which is used
in tNavigator.
Example
THCONS 152000
In this example the solid phase thermal conductivity is 152000J/m/day/C .
13.4.12. THCONS 1708

13.4.13 THCONMIX


Section
The keyword sets the method of block thermal conductivity calculation: SIMPLE or
COMPLEX.
The keyword has an analogue THCONMIX (see 12.14.19), which is used in tNavigator.
If the keyword THCONMIX specifies the option SIMPLE then thermal conductivity of
the grid block is ( 4.66):

Kb = 1 SS (kW SW + kO SO + kG SG ) + kS SbS + (1 ) kR
b
where

(see 13.4.12) = THCONR (see 13.4.8));
porosity.
If the keyword THCONMIX specifies the option COMPLEX then thermal conductivity
of the grid block is ( 4.66):

0
p kR p kR
kG kL
where
kW SW + KO SO
SW + SO
where
f mobile porosity.
13.4.13. THCONMIX 1709

Kb = Kb0 1.7524 105(T Tre f ) (Kb0 119616)

0
0.64 0 3
(3.6784106 Kb0 )
Kb Kb 1.8 10 T + 110644.8

Kb = (1 SG ) kR
where
SG gas saturation.
Example
THCONMIX SIMPLE
This example specifies the method of block thermal conductivity calculation SIMPLE.
13.4.13. THCONMIX 1710

13.4.14 HLOSST


Section
This keyword specifies the initial temperature of reservoir surroundings (SI: C, FIELD:
F),(see the section The heat exchange between the reservoir and surroundings 4.30).
The keyword is analogous to the 2-nd parameter of Eclipse compatible keyword ROCK-
PROP (see 12.2.78).
Example
HLOSST 43
In this example the initial temperature of reservoir surroundings is 43 C.
13.4.14. HLOSST 1711

13.4.15 HLOSSTDIFF


Section
This keyword specifies the minimal difference between temperatures when the calcula-
tions of the heat exchange should start (SI: C, FIELD: F), (see the section The heat
exchange between the reservoir and surroundings 4.30).
Default: 0.
Example
HLOSSTDIFF 1
In this example the minimal difference between temperatures when the calculations of the
heat exchange should start 1 C.
13.4.15. HLOSSTDIFF 1712

13.4.16 HLOSSPROP


Section
The keyword sets the connection between the reservoir and cap and base rocks, volumetric
heat capacity (SI: J/m3 C , FIELD: Btu/ f t 3 F ) and rock conductivity (SI: J/m day C ,
FIELD: Btu/ f t day F ) 4.30.
1. OVERBUR or (and) UNDERBUR or (and) +I, -I, +J, -J, +K, -K. This parameters are
not obligatory. One may not specify them or can specify part of them.
OVERBUR heat loss properties are applied to the outer grid block faces at the
reservoir top;
UNDERBUR heat loss properties are applied to the outer grid block faces at the
reservoir bottom;
+I, -I, +J, -J, +K, -K. Indicates the direction in which heat loss properties are
applied (I X-axis, J Y-axis, K Z-axis). OVERBUR and UNDERBUR can be
used together with +I, -I, +J, -J.
2. volumetric heat capacity (SI: J/m3 C , FIELD: Btu/ f t 3 F );
3. rock conductivity (SI: J/m day C , FIELD: Btu/ f t day F ).
The keyword has an Eclipse compatible analogues ROCKCON (see 12.2.79), ROCK-
PROP (see 12.2.78).
The keyword is also analogous to ROCKCONT (see 12.2.80), which is used in tNavigator.
Example
HLOSSPROP OVERBUR 1.7E6 1.002E5
In this example heat loss properties are applied to the outer grid block faces at the
reservoir top, volumetric heat capacity is 1.7E6 J/m3 C , rock conductivity 1.002E5 J/m
day C .
13.4.16. HLOSSPROP 1713

13.4.17 CPORPD


Section
The keyword specifies formation compressibility pressure dependence.

1. effective formation compressibility near the value of 3rd parameter (SI: 1/kPa, FIELD:
1/psi);
2. lower reference pressure for pressure-dependent formation compressibility (SI: kPa,

FIELD: psi). The value must be non-negative; At this value the formation compress-
ibility should be near the value specified via CPOR (see 13.4.5), and at pressure
specified via 3-rd parameter, the formation compressibility should be equal to the value
specified via 1-st parameter;
3. upper reference pressures for pressure-dependent formation compressibility (SI: kPa,

FIELD: psi). The value must be greater than the value of pressure at 2nd parameter.
The keyword is analogous to the 3rd, 4th and 5th parameters of the keyword ROCKT
(see 12.14.17), which is used in tNavigator.
Example
CPORPD 13.5E-06 1. 850.
13.4.17. CPORPD 1714

13.4.18 PORMAX


Section
The keyword specifies maximal fractional increase in porosity due to pressure.

1. fractional increase in porosity due to pressure.
The keyword is analogous to the 6th parameter of the keyword ROCKT (see 12.14.17),
which is used in tNavigator.
Example
PORMAX 0.1
13.4.18. PORMAX 1715

13.4.19 PBASE


Section
The keyword sets reference pressure for elastic curve in a reservoir dilation/recompaction
model.
1. reference pressure (SI: kPa, FIELD: psi).
Default:
reference pressure: corresponding with the keyword PRPOR (see 13.4.4).
Example
PBASE 200
13.4.19. PBASE 1716

13.4.20 CPEPAC


Section
The keyword sets pore volume compressibility value for elastic curve in a reservoir dila-
tion/recompaction model.
1. pore volume compressibility value (SI: 1/kPa, FIELD: 1/psi).
Default:
pore volume compressibility: corresponding with the keyword CPOR (see 13.4.5).
Example
CPEPAC
13.4.20. CPEPAC 1717

13.4.21 PDILA


Section
The keyword sets pressure value at which dilation begins. This keyword should be used
in a reservoir dilation/recompaction model.
1. pressure value (SI: kPa, FIELD: psi).
Default:
pressure value: 0.
Example
PDILA 420.0
13.4.21. PDILA 1718

13.4.22 CRD


Section
The keyword sets rock compressibility coefficient at dilation phase.

1. rock compressibility coefficient (SI: 1/kPa, FIELD: 1/psi).
Default: 0.
13.4.22. CRD 1719

13.4.23 PORRATMAX


Section
The keyword sets coefficient of maximal porosity increasing over reference porosity (see
the keyword POR (see 13.3.9)). Dilation process will stop when porosity value will be
maximal.
1. coefficient of maximal porosity increasing.
Default: 1.
Example
PORRATMAX 1.3
13.4.23. PORRATMAX 1720

13.4.24 PPACT


Section
The keyword sets boundary pressure value at which recompaction phase begins. This
value should be less than value specified at PDILA (see 13.4.21).
1. pressure value (SI: kPa, FIELD: psi).
Default: 0.
13.4.24. PPACT 1721

13.4.25 FR


Section
The keyword sets residual dilation fraction, i.e. ratio of difference between porosity value
after recompaction phase and initial porosity value to difference between changing of porosity
value during dilation phase.
Dilation-Recompaction) is in the section 4.24.
1. residual dilation fraction.
Default: 0.
Example
FR 0.4
13.4.25. FR 1722
13.4.26 CTD


Section
The keyword sets pore volume thermal expansion coefficient for dilation phase.
1. pore volume thermal expansion coefficient (SI: 1/C , FIELD: 1/ F ). This value must
be non-negative.
Default:
pore volume thermal expansion coefficient: correspondingly to the keyword CTPOR

(see 13.4.6).
Example
CTD 6E-6
13.4.26. CTD 1723

13.4.27 CTPPAC


Section
The keyword sets pore volume thermal expansion coefficient for recompaction phase.
1. pore volume thermal expansion coefficient (SI: 1/C , FIELD: 1/ F ). This value must
be non-negative.
Default:
pore volume thermal expansion coefficient: correspondingly to the keyword CTPOR

(see 13.4.6).
Example
CTPPAC 2E-6
13.4.27. CTPPAC 1724

13.4.28 DILATION


Section
The keyword specifies that dilation/recompaction model is used.
tic, Dilation-Recompaction) is in the section 4.24.
Example
DILATION
13.4.28. DILATION 1725

13.5. Component properties tNavigator-4.2
13.5 Component properties
13.5. Component properties 1726

13.5.1 K_SURF

Input Reservoir Other x Component

Section
The keyword specifies component K-values at surface conditions. The following param-
eters should be specified:
component name;
the value of Ks (i) (GAS-LIQUID) for this component at surface conditions. This
value will be used instead of the value, calculated form K-value at surface conditions
(pressure psur f and temperature Tsur f ).
Example
K_SURF 'N2C1' 2.0169E+02
K_SURF 'CO2' 5.8703E+01
K_SURF 'C2' 2.7216E+01
K_SURF 'C3' 6.9282E+00
K_SURF 'C4' 2.0053E+00
K_SURF 'C5' 5.5671E-01
K_SURF 'C6C10' 2.2811E-02
K_SURF 'C11C19' 2.6468E-05
K_SURF 'C20C35' 1.3923E-11
K_SURF 'C36P' 1.2174E-18
13.5.1. K_SURF 1727

13.5.2 SURFLASH


Section
This keyword is used to calculate phase resources and phase rates in surface conditions.
The keyword SURFLASH affects the option of component distribution between phases in
surface conditions. One of the following options should be specified:
1. SEGREGATED if this option is used, components are segregated into single phases.
If for the aqueous component K-value is Ks (i) < 1, then it will be considered in water
phase, else gas phase. If for the oleic component K-value is Ks (i) < 1, then it will
be considered in oil phase, else gas phase.
2. KVALUE - algorithm of phase distribution in the surface conditions corresponds to the

algorithm in the reservoir. (see 4.36).
Default:
SEGREGATED.
Example
SURFLASH KVALUE
13.5.2. SURFLASH 1728

13.5.3 MOLVOL


Section
The keyword sets the component molar volume at reference temperature TEMR (see
13.5.11) and reference pressure PRSR (see 13.5.10). This value is inverse to the component
molar density MOLDEN (see 13.5.14).
After the keyword the following parameters should be specified:
molar volume of each component (SI: m3 /gmol , FIELD: f t 3 /mol ). The same number
of values as the number of components in the oil or water phases (3-rd parameter of
MODEL (see 13.5.4)) should be specified.
The keyword has an Eclipse compatible analogue DREF (see 12.14.34).
13.5.3. MOLVOL 1729

13.5.4 MODEL


Section
For models in IMEX, STARS and GEM format this keyword has different syntax.
For models in IMEX format: (STARS and GEM are below)
The keyword specifies a type of model. tNavigator read the following types (the keyword
doesnt have in influence on the simulation):
BLACKOIL oil, gas, water;
OILWATER two-phase model, without gas phase;
MISCD pseudo-miscible model (solution gas always remain in solution);
MISNCG pseudo-miscible model (injected gas has the same composition as solution
gas);
POLY polymer model (oil, gas, water and polymer). Description of polymer flood
model is given in section Polymer flood in IMEX format;
POLYOW polymer model, without gas phase;
API-INT;
API-INTO;
GASWATER gas-water model, without gas phase.

Three keywords have an Eclipse compatible analogue OIL (see 12.1.52), WATER (see
12.1.54), GAS (see 12.1.53), VAPOIL (see 12.1.55), DISGAS (see 12.1.56).
Example
MODEL BLACKOIL
This example specifies the black oil model.
For models in STARS format:
The keyword sets the number of components and component volatility type.
The data should be entered in the following format:

MODEL
13.5.4. MODEL 1730

1. total number of components in the model (including water);
2. total number of components in the water, (or) oil, (or) gas phases;
3. total number of components in the water and (or) oil phases;
4. the number of water-like or aqueous components (default: 1 water).
The keyword has an Eclipse compatible analogue COMPS (see 12.13.3). COMPS (see
12.13.3) sets the number of hydrocarbon components, MODEL total number of components
(including water).
In the example below there are 7 components. 1 indicates in the table that the compo-
nent can be in this phase. There are 2 water-like components, 4 components water-like or
in the oil phase, 6 components water-like, in the oil or gas phases. Solid phase (coke) is
also enable.
Component name Water Oil Gas Solid phase

Water 1 0 1 0
Asphaltenes 0 1 0 0
Light oil 0 1 1 0
CO2 0 1 1 0
N2 / CO 0 0 1 0
Oxygen 0 0 1 0
Coke 0 0 0 1
Example
MODEL 7 6 4 1
COMPNAME 'Water' ' Asphaltenes' ' Light Oil' ' CO2' ' N2CO' ' Oxygen'
'Coke'
For models in GEM format:

In this case the keyword sets type of equation of state for a model. The following
1. type of equation of state:
SRK Soave-Redlich-Kwong equation;

PR Peng-Robinson equation.
Example
MODEL SRK
13.5.4. MODEL 1731

13.5.5 PVT


Section
The keyword sets PVT properties of oil and gas. The data should be entered the following
way:
PVT BG (EG of ZG) number
BG the gas formation volume factor will be used (EG gas expansion factor, ZG gas
compressibility factor). BG is equal to the volume of gas at reservoir conditions divided by
volume of gas at surface conditions, EG is equal to the volume of gas at surface conditions
divided by volume of gas at reservoir conditions.
number - PVT region number (the following table is specified for this PVT region).
The table consists of arbitrary number of lines (two or more). Pressure (the first parameter)
should increase down the column. Each line has 8 parameters:
1. the bubble point pressure (SI: kPa, FIELD: psi),
2. gas-oil ratio of saturated oil with bubble point pressure specified by the 1-st parameter
(SI: m3 /m3 , FIELD: sc f /ST B),
3. the formation volume factor of saturated oil at the bubble point pressure (SI: m3 /m3 ,
FIELD: rb/stb),
4. Bg the gas formation volume factor will be used (SI: m3 /m3 , FIELD: rb/sc f ) (Eg
gas expansion factor (SI: m3 /m3 , FIELD: sc f /rb), Zg gas compressibility factor,
if EG or ZG is specified after PVT),
5. the viscosity of saturated oil at the bubble point pressure (SI: mPa s, FIELD: cp),
6. the viscosity of gas at the bubble point pressure (SI: mPa s, FIELD: cp),
7. oil compressibility,
8. gas-oil surface tension (SI, FIELD: dyne/cm).
The keyword has an Eclipse compatible analogue PVCO (see 12.5.6), PVDG (see 12.5.7).
13.5.5. PVT 1732

Example
PVT BG 1
101.325 0.418766947 1.00121067 1.242456434 594.9490888
0.0124995 4.35E-06
527.904 2.185316651 1.006289406 0.235088062 587.1696078
0.0125406 4.35E-06
This example specifies PVT table for 1 PVT region (gas-oil surface tension isnt specified
- default value will be used).
13.5.5. PVT 1733

13.5.6 DENSITY


Section
The keyword sets oil, water and gas density (SI: kg/m3 , FIELD: lbm/ f t 3 ). To enter
phase density one should add phase name OIL, GAS or WATER after DENSITY.
The keyword has an Eclipse compatible analogue DENSITY (see 12.5.23).
Example
DENSITY OIL 948.2
DENSITY WATER 1001.48
This example sets oil density equal to 948.2 and water density - 1001.48.
13.5.6. DENSITY 1734

13.5.7 BWI / CW / REFPW / CVW / VWI


Section
These keywords specify for one PVT region the following data:
BWI - water formation volume factor (SI: m3 /m3 , FIELD: rb/stb),
CW - water compressibility (SI: 1/kPa, FIELD: 1/psi),
PEFPM - reference pressure (SI: kPa, FIELD: psi),
CVW - water viscosibility,
VWI - water viscosity (SI: mPa s, FIELD: cp).
If there are more then one PVT region, these five items should be specified for every
PVT region.
Five keywords have an Eclipse compatible analogue PVTW (see 12.5.5). 2-nd parameter
of PVTW corresponds to BWI, 3-rd CW, 1-st REFPW, 5-th CVW, 4-th VWI.
Example
BWI 1.0111
CVW 0
CW 8.64711e-006
REFPW 20000
VWI 0.613465
This example sets water formation volume factor equal to 1.0111, water compressibility -
8.64711e-006, reference pressure - 20000, water viscosibility - 0, water viscosity - 0.613465.
13.5.7. BWI / CW / REFPW / CVW / VWI 1735

13.5.8 PTYPE


Section
region to which it belongs. This keyword should be entered after all PVT tables for all PVT
regions.
The keyword has an Eclipse compatible analogue PVTNUM (see 12.4.2).
Example
PTYPE FRACTURE CON 1
PTYPE MATRIX CON 1
This example sets 1 PVT region (CON specifies an array, all elements of this array are
equal to 1).
13.5.8. PTYPE 1736

13.5.9 COMPNAME


Section
The keyword specifies component names. This keyword is used after the keyword MODEL
(see 13.5.4)
COMPNAME should be followed by the component names.
The keyword has an Eclipse compatible analogue CNAMES (see 12.13.4).

In the example below there are 7 components. 1 indicates in the table that the compo-
nent can be in this phase. There are 2 water-like components, 4 components water-like or
in the oil phase, 6 components water-like, in the oil or gas phases. Solid phase (coke) is
also enable.
Component name Water Oil Gas Solid phase

Water 1 0 1 0
Asphaltenes 0 1 0 0
Light oil 0 1 1 0
CO2 0 1 1 0
N2 / CO 0 0 1 0
Oxygen 0 0 1 0
Coke 0 0 0 1
Example
MODEL 7 6 4 1
COMPNAME 'Water' ' Asphaltenes' ' Light Oil' ' CO2' ' N2CO' ' Oxygen'
'Coke'
13.5.9. COMPNAME 1737

13.5.10 PRSR


Section
This keyword specifies the reference pressure (SI :kPa, FIELD: psi). The reference
pressure corresponds to the densities entered via the keywords MOLDEN (see 13.5.14),
MASSDEN (see 13.5.15), SOLID_DEN.
The reference pressure is used in the formulas: 4.7, 4.11 and 4.19 (component phase density
calculations).
The keyword has an Eclipse compatible analogues PREF (see 12.14.29), SPREF (see
12.14.23).
Example
PRSR 101
In this example reference pressure is equal to 101.
13.5.10. PRSR 1738

13.5.11 TEMR


Section
This keyword specifies the reference temperature (SI: C , FIELD: F ). The reference
temperature corresponds to the densities entered via the keywords MOLDEN (see 13.5.14),
MASSDEN (see 13.5.15), SOLID_DEN.
The reference temperature is used in the formulas: 4.7, 4.11, 4.19 (component phase density
calculations), 4.42, 4.45, 4.50, 4.51, 4.24.
The keyword has an Eclipse compatible analogues TREF (see 12.14.32), STREF (see
12.14.25).
Example
TEMR 70
In this example reference temperature is equal to 101.
13.5.11. TEMR 1739

13.5.12 PSURF


Section
The keyword sets the standard pressure (that corresponds to surface conditions) for cal-
culation od gas, oil, water volumes at surface conditions (SI: kPa, FIELD: psi).
Default: (SI:) 101kPa = (FIELD:) 14.65 psi.
The keyword has an Eclipse compatible analogue STCOND (see 12.13.8).
13.5.12. PSURF 1740

13.5.13 TSURF


Section
The keyword sets the standard temperature (that corresponds to surface conditions) for
calculation od gas, oil, water volumes at surface conditions (SI: K , FIELD: F ).
Default: (SI:) 290K = (FIELD:) 62F .
The keyword has an Eclipse compatible analogue STCOND (see 12.13.8).
13.5.13. TSURF 1741

13.5.14 MOLDEN


Section
The keyword sets the component molar density (SI: gmol/m3 , FIELD: lbmol/ f t 3 ) at
reference temperature TEMR (see 13.5.11) and reference pressure PRSR (see 13.5.10).
The same number of values as the number of components in the oil or water phases (3-rd
parameter of MODEL (see 13.5.4)) should be specified.
The component molar density is used in the formulas 4.7, 4.11.

Component mass density (MASSDEN (see 13.5.15)) is equal to the product of the
component molar density and molecular mass.
13.5.14. MOLDEN 1742

13.5.15 MASSDEN


Section
The keyword sets the component mass density (SI: kg/m3 , FIELD: lb/ f t 3 ) at reference
temperature TEMR (see 13.5.11) and reference pressure PRSR (see 13.5.10).
The component mass density is used in the formulas 4.7, 4.11.

Component mass density is equal to the product of the component molar density
(MOLDEN (see 13.5.14)) and molecular mass.
Example
MODEL 3 3 3 1
MASSDEN
982.12 964.17 267.25
This example sets the component mass density for 3 components (the number of compo-
nents in the oil and water phases 3-rd parameter of MODEL (see 13.5.4)).
13.5.15. MASSDEN 1743

13.5.16 CP


Section
The keyword sets the component compressibility (SI: 1/kPa, FIELD: 1/psi), which is
used in water mass and molar density calculations 4.7 and oil mass and molar density cal-
culations 4.11.
The keyword has an Eclipse compatible analogue CREF (see 12.14.31).
Example
MODEL 3 3 3 1
CP
6.28e-007 3.7e-006 3.7e-006
This example sets the component compressibility for 3 components (the number of com-
ponents in the oil and water phases 3-rd parameter of MODEL (see 13.5.4)).
13.5.16. CP 1744
13.5.17 CT1


Section
The keyword sets the first thermal expansion coefficient (SI: 1/C , FIELD: 1/F ) for each
component. This coefficient is used in water mass and molar density calculations 4.7 and oil
mass and molar density calculations 4.11.
The keyword has an Eclipse compatible analogue THERMEX1 (see 12.14.26).
Example
MODEL 3 3 3 1
CT1
0.0006643 4.8977e-006 4.3512e-006
This example sets the first thermal expansion coefficient for 3 components (the number
of components in the oil and water phases 3-rd parameter of MODEL (see 13.5.4)).
13.5.17. CT1 1745

13.5.18 CT2


Section
The keyword sets the second thermal expansion coefficient (SI: 1/C2 , FIELD: 1/F 2 ) for
each component. This coefficient is used in water mass and molar density calculations 4.7
and oil mass and molar density calculations 4.11.
Total thermal expansion coefficient is equal to ck,1,T + T ck,2,T The same number of values
as the number of components in the oil or water phases (3-rd parameter of MODEL (see
13.5.4)) should be specified.
The keyword has an analogue THERMEX2 (see 12.14.27), which is used in tNavigator.
There are no Eclipse compatible analogues.
Example
MODEL 3 3 3 1
CT2
0.00006643 4.8977e-007 4.3512e-007
This example sets the second thermal expansion coefficient for 3 components (the number
of components in the oil and water phases 3-rd parameter of MODEL (see 13.5.4)).
13.5.18. CT2 1746

13.5.19 CPT


Section
The keyword sets the coefficient of density dependence on temperature and pressure (SI:
1/kPa C , FIELD: 1/psi F ) for each component. This coefficient is used in water mass
and molar density calculations 4.7 and oil mass and molar The same number of values as the
number of components in the oil or water phases (3-rd parameter of MODEL (see 13.5.4))
should be specified.
The keyword has an analogue THERMEX3 (see 12.14.28), which is used in tNavigator.
Example
MODEL 3 3 3 1
0.000006643 4.8977e-006 4.3512e-006
3 components (the number of components in the oil and water phases 3-rd parameter of
MODEL (see 13.5.4)).
13.5.19. CPT 1747

13.5.20 PCRIT


Section
The keyword sets the component critical pressure (SI: kPa, FIELD: psi) which is used
in gas mass and gas molar density calculations 4.16.
The same number of values as the number of components in the oil, water or gas phases
(2-nd parameter of MODEL (see 13.5.4)) should be specified.
The keyword has an Eclipse compatible analogue PCRIT (see 12.13.19). The difference
is that Eclipse compatible PCRIT doesnt contain water critical pressure.
Example
MODEL 3 3 3 1
PCRIT
0 0 4326
This example sets the component critical pressure for 3 components (the number of
components in the oil, water or gas phases 2-nd parameter of MODEL (see 13.5.4)).
13.5.20. PCRIT 1748

13.5.21 TCRIT


Section
The keyword sets the component critical temperature (SI: C , FIELD: F ) which is used
in gas mass and gas molar density calculations 4.16.
The keyword has an Eclipse compatible analogue TCRIT (see 12.13.17). The difference
is that Eclipse compatible TCRIT doesnt contain water critical temperature.
Example
MODEL 3 3 3 1
TCRIT
0 0 -79.22
This example sets the component critical temperature for 3 components (the number of
components in the oil, water or gas phases 2-nd parameter of MODEL (see 13.5.4)).
13.5.21. TCRIT 1749

13.5.22 SOLID_DEN


Section
The keyword sets the properties of component k in the solid phase that are used in the
molar density calculations 4.19.
For each component the data should be entered in the following format:
1. 'component name' k (the number of component and component names are set via
MODEL (see 13.5.4), COMPNAME (see 13.5.9));
2. density of component k (kg/m3 ) at reference pressure PRSR (see 13.5.10) and refer-
ence temperature TEMR (see 13.5.11);
3. ck,p compressibility of the component k (1/kPa);
4. ck,T thermal expansion coefficient for component k (1/C );
5. ck,pT the coefficient of density dependence on temperature and pressure (1/kPa C ).
The keyword has Eclipse compatible analogues SDREF (see 12.14.22), SCREF (see
12.14.24), STHERMX1 (see 12.14.20). For the parameter ck,pT tNavigator uses this keyword
STHERMX2 (see 12.14.21).
13.5.22. SOLID_DEN 1750

13.5.23 SOLID_CP


Section
The keyword sets the properties of component k in the solid phase that are used in the
solid phase enthalpy calculations 4.50.
For each component the data should be entered in the following format:
1. 'component name' k (the number of component and component names are set via
MODEL (see 13.5.4), COMPNAME (see 13.5.9));
2. coefficient CP1,c (SI: J/gmol C , FIELD: Btu/lbmol F );
3. coefficient CP2,c (SI: J/gmol C2 , FIELD: Btu/lbmol F 2 );
This keyword is analogous to SPECHS (see 12.14.66), SPECHT (see 12.14.67) which are
used in tNavigator.
Example
SOLID_CP
'Comp1' 0.52 0.0076
In this example CP1,c and CP2,c are specified for the component Comp1.
13.5.23. SOLID_CP 1751

13.5.24 KVTABLIM


Section
The keyword sets the pressure and temperature range for Ki (p, T ) table. (Ki (p, T ) the
ratio of mole fractions of component in vapor and liquid phases.) These tables are used in
the formulas of thermodynamic equilibrium condition 4.9.
The table Ki (p, T ) is set via KVTABLE (see 13.5.25).
1. The minimal value of pressure for Ki (p, T ) (kPa) plow.
2. The maximal value of pressure for Ki (p, T ) (kPa) phigh.
3. The minimal value of temperature for Ki (p, T ) ( C ) T low.
4. The maximal value of temperature for Ki (p, T ) ( C ) T high.
The keyword has an Eclipse compatible analogues KVTEMP (see 12.14.6), KVTABTn
(see 12.14.7). tNavigator also uses the keyword KVTABLIM (see 12.14.8).
An example of use of KVTABLIM (see 13.5.24) is given in the description of the keyword
KVTABLE (see 13.5.25).
13.5.24. KVTABLIM 1752

13.5.25 KVTABLE


Section
The keyword sets the table Ki (p, T ). (Ki (p, T ) the ratio of mole fractions of compo-
nent in vapor and liquid phases.) These tables are used in the formulas of thermodynamic
equilibrium condition 4.9.
The pressure and temperature range for Ki (p, T ) table is set via KVTABLIM (see 13.5.24).
The keyword has an Eclipse compatible analogues KVTEMP (see 12.14.6), KVTABTn
(see 12.14.7). tNavigator also uses the keyword KVTABLIM (see 12.14.8).
After KVTABLE one should specify the component k name in quotes ' '(the number
of components and component names are set via MODEL (see 13.5.4), COMPNAME (see
13.5.9)) and the table for this component:
K(T low, plow) . . . K(T low, phigh)

... ... ...
K(T hight, plow) . . . K(T hight, phigh)
Interpolation between table entries:
between two Ki (p, T ) for two adjacent pressures: Ki (p, T ) varies linearly with the
coefficient 1/p;
between two non-zero Ki (p, T ) for two adjacent temperatures: ln(Ki (p, T )) varies
linearly with the coefficient 1/T ;
between two Ki (p, T ) (one of the value entries is zero) for two adjacent temperatures:
Ki (p, T ) varies linearly with the coefficient 1/T .
Example
KVTABLIM
10 500 20 250
KVTABLE
'COMPONENT2'
0.0001 0.0008
0.01 0.09
In this example the Ki (p, T ) table for COMPONENT2 has 2 rows and 2 columns. The
pressure varies within: 10 - 500 kPa, temperature varies within: 20 - 250 C .
13.5.25. KVTABLE 1753

13.5.26 KV1 / KV2 / KV3 / KV4 / KV5


Section
These keywords specify the coefficients of the correlation formula ( 4.24):
Ki (p, T ) = (Ai + Bi /p +Ci p) eDi /(T Ei ) (13.1)
where Ai KV3, Bi KV1 (SI: kPa, FIELD: psi), Ci KV2 (SI: 1/kPa, FIELD: 1/psi),
Di KV4 (SI: C , FIELD: F ), Ei KV5 (SI: C , FIELD: F ).
After each keyword (KV1, ... , KV5) one should specify the same number of coefficients
as the number of components in the oil or water phases (3-rd parameter of MODEL (see
The keywords have an Eclipse compatible analogue KVCR (see 12.14.4). 1-st parameter
of KVCR (see 12.14.4) corresponds to KV3, 2-nd parameter KV1, 3-rd parameter KV2,
4-th parameter KV4 (with opposite sign), 5-th parameter KV5.
Example
MODEL 3 3 3 1
KV1
0 0 185967
KV2
0 0 -2.34122e-007
KV3
0 0 15.4327
KV4
0 0 -633.552
KV5
0 0 -321.88
In this example the coefficients of the correlation formula are specified for 3 components.
13.5.26. KV1 / KV2 / KV3 / KV4 / KV5 1754

13.5.27 CPL1 / CPL2 / CPL3 / CPL4


Section
These keywords specify the coefficients in the component liquid enthalpy calculations
( 4.43):
4
1
i=1 i
where the coefficients:
CP1,c CPL1 (SI: kJ/kg/C , FIELD: Btu/lbmol/ F ),
CP2,c CPL2 (SI: kJ/kg/C2 , FIELD: Btu/lbmol/ F 2 ),
CP3,c CPL3 (SI: kJ/kg/C3 , FIELD: Btu/lbmol/ F 3 ),
CP4,c CPL4 (SI: kJ/kg/C4 , FIELD: Btu/lbmol/ F 4 ).
Default values: CP1,c = 0.5Btu/lbmol/F = 0.51.05506/0.4535921.8kJ/mol/C = 2.0934kJ/mol/C ,
the other coefficients 0.
After each keyword CPL1, CPL2, CPL3, CPL4 one should specify the same number of
coefficients as the number of components in the oil, water or gas phases (2-nd parameter of
The keywords CPL1, CPL2 have an Eclipse compatible analogues SPECHA (see
12.14.57), SPECHB (see 12.14.58). tNavigator also uses the keywords CP3,c = SPECHC
(see 12.14.59), CP4,c = SPECHD (see 12.14.60).
Example
CPL1
0.66 0.52
CPL2
0.0071 0.0054
CPL3
0.00062 0.00046
CPL4
0.000055 0.000078
In this example the coefficients of component liquid enthalpy formula are specified for 2
components.
13.5.27. CPL1 / CPL2 / CPL3 / CPL4 1755

13.5.28 CPG1 / CPG2 / CPG3 / CPG4


Section
These keywords specify the coefficients in the component gas enthalpy calculations
( 4.47):
4
1
Hc,G (T ) = hc,G + CPi,c (T Tre f )i
i=1 i
hc,G HVAPR (see 13.5.29),
CP1,c CPG1 (SI: kJ/kg/C , FIELD: Btu/lbmol/ F ),
CP2,c CPG2 (SI: kJ/kg/C2 , FIELD: Btu/lbmol/ F 2 ),
CP3,c CPG3 (SI: kJ/kg/C3 , FIELD: Btu/lbmol/ F 3 ),
CP4,c CPG4 (SI: kJ/kg/C4 , FIELD: Btu/lbmol/ F 4 ).
(CPG1 / CPG2 / CPG3 / CPG4 (see 13.5.28))
Default values: hc,G = 0.25Btu/lb/F = 0.251.05506/0.4535921.8kJ/kg/C = 1.0467kJ/kg/C ,

CP1,c = 0.25Btu/lb/F = 1.0467kJ/kg/C , the other coefficients 0.
After each keyword CPG1, CPG2, CPG3, CPG4 one should specify the same number of
coefficients as the number of components in the oil, water or gas phases (2-nd parameter of
The keywords CPG1, CPG2 have an Eclipse compatible analogues SPECHG (see
12.14.61), SPECHH (see 12.14.62). tNavigator also uses the keywords CP3,c = SPECHI
(see 12.14.63), CP4,c = SPECHJ (see 12.14.64).
Example
CPG1
0.0066 0.0052
CPG2
0.00071 0.00054
CPG3
0.000062 0.000046
CPG4
0.0000055 0.0000078
13.5.28. CPG1 / CPG2 / CPG3 / CPG4 1756

In this example the coefficients of component gas enthalpy formula are specified for 2
components.
13.5.28. CPG1 / CPG2 / CPG3 / CPG4 1757

13.5.29 HVAPR


Section
This keyword specifies the coefficients in the component gas enthalpy calculations ( 4.47):
4
1
Hc,G (T ) = hc,G + CPi,c (T Tre f )i
i=1 i

hc,G HVAPR (see 13.5.29),
CP1,c CPG1 (kJ/kg/C ),
CP2,c CPG2 (kJ/kg/C/C ),
CP3,c CPG3 (kJ/kg/C/C/C ),
CP4,c CPG4 (kJ/kg/C/C/C/C ).
(CPG1 / CPG2 / CPG3 / CPG4 (see 13.5.28))
Default values: hc,G = 0.25Btu/lb/F = 0.251.05506/0.4535921.8kJ/kg/C = 1.0467kJ/kg/C ,

CP1,c = 0.25Btu/lb/F = 1.0467kJ/kg/C , the other coefficients 0.
After the keyword HVAPR one should specify the same number of coefficients as the
number of components in the oil or water phases (3-rd parameter of MODEL (see 13.5.4))
should be specified.
The keyword has an Eclipse compatible analogue HEATVAPS (see 12.14.65).
Example
HVAPR 3*
In this example the coefficients hc,G of component gas enthalpy formula are specified on
default for 3 components.
13.5.29. HVAPR 1758

13.5.30 HVR


Section
These keywords specify the coefficients in the vaporization enthalpy calculations ( 4.44):

Bc

A0c HVR (kJ/mol/C ),
Bc EV (see 13.5.31).
Default values A0c = 0.25Btu/lbmol/F = 0.251.05506/0.4535921.8kJ/mol/C = 1.0467kJ/mol/C ,
Bc = 0.38.
Critical temperature of the component Tc,crit is specified via TCRIT (see 13.5.21).
If HVc (T ) = 0 then T Tc,crit .
After each keyword HVR and EV (see 13.5.31) one should specify the same number
of coefficients as the number of components in the oil or water phases (3-rd parameter of
The keyword has an Eclipse compatible analogue HEATVAP (see 12.14.13).
Example
HVR
1.33 2.11
EV
0.42 0.39
In this example the coefficients of the vaporization enthalpy formula are specified for 2
components.
13.5.30. HVR 1759

13.5.31 EV


Section
These keywords specify the coefficients in the vaporization enthalpy calculations ( 4.44):

Bc

A0c HVR (see 13.5.30) (kJ/mol/C ),
Bc EV.
Default values A0c = 0.25Btu/lbmol/F = 0.251.05506/0.4535921.8kJ/mol/C = 1.0467kJ/mol/C ,
Bc = 0.38.
Critical temperature of the component Tc,crit is specified via TCRIT (see 13.5.21).
If HVc (T ) = 0 then T Tc,crit .
After each keyword HVR (see 13.5.30) and EV one should specify the same number
of coefficients as the number of components in the oil or water phases (3-rd parameter of
The keyword has an Eclipse compatible analogue HEATVAPE (see 12.14.14).
Example
HVR
1.33 2.11
EV
0.42 0.39
In this example the coefficients of the vaporization enthalpy formula are specified for 2
components.
13.5.31. EV 1760
13.5.32 STOREAC


Section
The keyword specifies the stoichiometric coefficients for all reactants in each chemical
reaction as a line of numbers. Full description of chemical reactions is in the section 4.29.
The number of reaction (for which all properties are specified) is not set explicitly. So for
first reaction all keywords STOPROD (see 13.5.33), STOREAC (see 12.14.53), FREQFAC
(see 13.5.34), RENTH (see 13.5.38) etc. should appear as a group. Then for second reaction
all these keywords should appear, for third reaction, etc.
Each line should contain the same number of values as the number of components (first
parameter of MODEL (see 13.5.4)). If the component isnt the reactant of the reaction one
should enter zero.
The keyword has an Eclipse compatible analogue STOREAC (see 12.14.53).
C3 H8 + 5O2 3CO2 + 4H2 O
and five components there is an example:
Example
STOPROD 0 0 0 3 4
STOREAC 0 1 5 0 0
The reactants of this reaction are: the 2nd component (with the coefficient 1) and the 3rd
component (with the coefficient 5). 1st component isnt present in this reaction The products
of this reaction are: the 4th component (with the coefficient 3) and the 5th component (with
the coefficient 4).
13.5.32. STOREAC 1761

13.5.33 STOPROD


Section
The keyword specifies the stoichiometric coefficients for all products in each chemical
reaction as a line of numbers. Full description of chemical reactions is in the section 4.29.
parameter of MODEL (see 13.5.4)). If the component isnt the product of the reaction one
should enter zero.
The keyword has an Eclipse compatible analogue STOPROD (see 12.14.52).
C3 H8 + 5O2 3CO2 + 4H2 O
and five components there is an example:
Example
STOPROD 0 0 0 3 4
STOREAC 0 1 5 0 0
The reactants of this reaction are: the 2nd component (with the coefficient 1) and the 3rd
component (with the coefficient 5). 1st component isnt present in this reaction The products
of this reaction are: the 4th component (with the coefficient 3) and the 5th component (with
the coefficient 4).
13.5.33. STOPROD 1762

13.5.34 FREQFAC


Section
The keyword sets the reaction rate Ar of each chemical reaction. Full description of
chemical reactions is in the section 4.29.
The keyword has an Eclipse compatible analogue REACRATE (see 12.14.46).
Example
FREQFAC 0.0000038
In this example reaction rate is equal to 0.0000038.
13.5.34. FREQFAC 1763

13.5.35 FREQFACP


Section
The keyword sets reaction rate Ar dependence on pressure pr as a table of 2 columns.

In the first column pressure values are specifying (SI: kPa, FIELD: psi). They should be
increasing. In the second column values of reaction rate at corresponding pressure are speci-
fied. Full description of chemical reactions is in the section 4.29.
first reaction all keywords (STOPROD (see 13.5.33), STOREAC (see 12.14.53), FREQFAC
(see 13.5.34), RENTH (see 13.5.38) etc.). Then for second reaction all these keywords
should appear, for third reaction, etc. Pressure values must be increasing.
The keyword has an Eclipse compatible analogue REACRATE (see 12.14.46).
Example
FREQFACP
100 0.0000038
120 0.0000041
In the example the table of reaction rate dependent pressure is specified.
13.5.35. FREQFACP 1764

13.5.36 EACT


Section
The keyword sets the activation energy in chemical reaction rates Er of each chemical
reaction (SI: J/gmol , FIELD: Btu/lbmol ). Full description of chemical reactions is in the
section 4.29.
The keyword has an Eclipse compatible analogue REACACT (see 12.14.47).
Example
EACT 18400
In this example activation energy is equal to 18400 J/gmol .
13.5.36. EACT 1765

13.5.37 EACT_TAB


Section
The keyword sets activation energy of reactions values dependence on temperature.

at the same line with the keyword:
1. the number of a table row, where values of reference temperature and energy are
specified;
in the following lines a table is specified. In each line the following parameters should
be specified:
1. temperature value (SI: C , FIELD: F );

2. value of activation energy (SI: J/gmol , FIELD: Btu/lbmol ).
Default:
if keywords EACT (see 13.5.36) and EACT_TAB are absent, then reaction is inde-
pendable on temperature. It is equal to EACT 0.
Example
EACT_TAB 3
100 180000.8
120 187819.7
140 190000.0
In the example the keyword EACT_TAB sets activation energy of reactions values depen-
dence on temperature. Reference temperature and energy are specified in a 3-rd row.
13.5.37. EACT_TAB 1766

13.5.38 RENTH


Section
The keyword sets the reaction enthalpy Hr of each chemical reaction (SI: J/gmol ,
FIELD: Btu/lbmol ). Full description of chemical reactions is in the section 4.29.
The number of reaction (for which all properties are specified) is not set explicitly. So
for first reaction all keywords STOPRODCMG (see 12.14.52), STOREAC (see 12.14.53),
FREQFAC (see 13.5.34), RENTH (see 13.5.38) etc. should appear as a group. Then for
second reaction all these keywords should appear, for third reaction, etc.
The keyword has an Eclipse compatible analogue REACENTH (see 12.14.56).
Example
EACT 15200
In this example reaction enthalpy is equal to 15200 J/gmol .
13.5.38. RENTH 1767

13.5.39 RORDER


Section
The keyword specifies the order of component terms Nr of each chemical reaction as a
line of numbers. Full description of chemical reactions is in the section 4.29.
parameter of MODEL (see 13.5.4)). If the reaction rate doesnt depend of the component
concentration one should enter zero.
The keyword has an Eclipse compatible analogues REACCORD (see 12.14.48), REAC-
SORD (see 12.14.55).
Example
RORDER 0 0 1 1 0 0
In this example there are 6 components. The rate of this reaction depends (linearly) of
the concentration of 3rd and 4th components.
13.5.39. RORDER 1768

13.5.40 RPHASE


Section
The keyword sets the component phase in each chemical reaction. Full description of
chemical reactions is in the section 4.29.
parameter of MODEL (see 13.5.4)).
The values could be the following:
0 component doesnt react;
1 component reacts in water phase;
2 component reacts in oil phase;
3 component reacts in gas phase;
4 component reacts in solid phase.
The keyword has an Eclipse compatible analogue REACPHA (see 12.14.54).
Example
RPHASE 0 0 2 3 3 4
In this example there are 6 components. 1-st and 2-nd component doesnt react, 3-rd
component reacts in oil phase, 4-th and 5-th gas phase, 6-th solid phase.
13.5.40. RPHASE 1769

13.5.41 RTEMUPR


Section
The keyword sets the maximal temperature Tu (SI: C , FIELD: F ), which is used in the
reaction rate calculations 4.67. Full description of chemical reactions is in the section 4.29.
The keyword has an Eclipse compatible analogue REACLIMS (see 12.14.49).
Example
RTEMUPR 230
In this example the maximal temperature is equal to 230 C.
13.5.41. RTEMUPR 1770

13.5.42 RTEMLOWR


Section
The keyword sets the minimal temperature Tl (SI: C , FIELD: F ), which is used in the
reaction rate calculations 4.67. Full description of chemical reactions is in the section 4.29.
The keyword has an Eclipse compatible analogue REACLIMS (see 12.14.49).
Example
RTEMLOWR 120
In this example the minimal temperature is equal to 120 C.
13.5.42. RTEMLOWR 1771

13.5.43 RXCRITCON


Section
The keyword sets the critical value of reactant concentration (SI: kPa, FIELD: psi, if the
pressure is used or SI: gmol/m3 , FIELD: lbmol/ f t 3 , if the concentration is used), which is
used in the reaction rate calculations 4.67. Full description of chemical reactions is in the
section 4.29.
' component name';
critical value of concentration.
The keyword has an analogue REACCONC (see 12.14.50), which is used in tNavigator.
Example
RXCRITCON 'comp1' 0.00022
In this example the critical value of comp1 concentration is equal to 0.00022.
13.5.43. RXCRITCON 1772

13.5.44 O2PP


Section
The keyword sets that the gas partial pressure will be used in calculations of c0ri in the
formula 4.69. The keyword O2PP is used only for components in gas phase (if the 'com-
ponent name' is entered) and is the default value for oxygen (if the 'component name' is
not entered).
Full description of chemical reactions is in the section 4.29.
The keyword is analogous to GPP in Eclipse compatible keyword REACPHA (see

12.14.54).
Example
O2PP
In this example in calculations of c0ri will be used oxygen partial pressure.
13.5.44. O2PP 1773

13.5.45 VSTYPE


Section
The keyword is used to define multiple viscosity regions.

The keyword specifies for each grid block the number of viscosity region to which it belongs.
Only the number of viscosity region that has been defined earlier via VISCTYPE (see 13.5.46)
is allowed.
Default: all grid blocks belong to one region.
The keyword is analogous to VISCNUM (see 12.4.20), which is used in tNavigator.
Example
VISCTYPE 1
...
VISCTYPE 2
...
VSTYPE 2 2 2 2 2 1 1 1 1 1 1 1
2 2 2 2 1 1 1 1 1 1 1 1 1 1 1
There are two viscosity regions in this example.
13.5.45. VSTYPE 1774

13.5.46 VISCTYPE


Section
The keyword is used to define multiple viscosity regions.

This keyword sets the number of viscosity region the following viscosity properties are
assigned to. Viscosity data: AVISC (see 13.5.51), BVISC (see 13.5.52), VISCTABLE
(see 13.5.53), VSMIXCOMP (see 13.5.54), VSMIXCOMP (see 13.5.54), VSMIXFUNC
(see 13.5.56), AVG (see 13.5.57), BVG (see 13.5.58).
The keyword VSTYPE (see 13.5.45) specifies for each grid block the number of viscosity
region to which it belongs.
Example
VISCTYPE 1
AVISC 0.4 0.5 0.6
BVISC 12 18 20
AVG 0.00022 0.00017
BVG 0.8 0.7
...
VISCTYPE 2
AVISC 0.3 0.51 0.62
BVISC 14 17 21
AVG 0.00022 0.00017
BVG 0.8 0.7
...
VSTYPE 2 2 2 2 2 1 1 1 1 1 1 1
2 2 2 2 1 1 1 1 1 1 1 1 1 1 1
There are two viscosity regions in this example.
13.5.46. VISCTYPE 1775

13.5.47 VISCOR


Section
The keyword sets type of correlation to calculate hydrocarbon phase viscosities. The
1. correlation type:
HZYT Herning and Zipperer and Yoon and Thodos correlation formulas;
PEDERSEN Pedersen correlation (keyword PEDERSEN (see 12.13.52)).
Example
VISCOR HZYT
13.5.47. VISCOR 1776

13.5.48 VISVC


Section
This keyword specify critical volumes (which will be used for viscosity calculation only)
for each component of a compositional model. The following parameters should be specified:
1. critical volume for each component (METRIC: m3 /kg.M , SI: f t 3 /lb.M ).
This keyword has an Eclipse compatible analogue VCRITVIS (see 12.13.23).
Example
VISVC 5.350000E-01 5.340000E-01 4.320000E-01 3.890000E-01
13.5.48. VISVC 1777

13.5.49 VISCOEFF


Section
The keyword sets correlation coefficients. If PEDERSEN is set in VISCOR (see 13.5.47),
then this keyword sets Pedersen correlation coefficients; otherwise, Lorenz-Bray-Clark (LBC-
COEF (see 12.13.36)) correlation coefficients are set. The following parameters should be
specified:
1. 5 coefficients.
This keyword has Eclipse compatible analogs PEDTUNE (see 12.13.53) and LBCCOEF
(see 12.13.36).
Example
VISCOEFF 1 1 1.847 0.5173 7.378E-3
13.5.49. VISCOEFF 1778

13.5.50 MIXVC


Section
The keyword sets exponent in the critical volume mixing rule used to calculate the Jossi,
Stiel and Thodos correlation. The following parameters should be specified:
1. exponent value.
Default: 1.
Example
MIXVC 1.1
13.5.50. MIXVC 1779

13.5.51 AVISC


Section
This keyword specifies coefficients in water and oil viscosity correlation formulas AW
( 4.30) and A0k ( 4.32).
BW and B0k are specified via BVISC (see 13.5.52).
Different values can be entered for different viscosity regions (see an example in the
description of VISCTYPE (see 13.5.46)).
In e300 data format the coefficients of correlations are set via OILVISCC (see 12.14.41).
Grabovski correlation is used in water viscosity calculations 4.29.
Example
AVISC 0.4 0.5 0.6
BVISC 12 18 20
In this example correlation coefficients are specified for 3 components.
13.5.51. AVISC 1780

13.5.52 BVISC


Section
This keyword specifies coefficients in water and oil viscosity correlation formulas BW
( 4.30) and B0k ( 4.32).
AW and A0k are specified via AVISC (see 13.5.51).
In e300 data format the coefficients of correlations are set via OILVISCC (see 12.14.41).
Grabovski correlation is used in water viscosity calculations 4.29.
Example
AVISC 0.4 0.5 0.6
BVISC 12 18 20
13.5.52. BVISC 1781

13.5.53 VISCTABLE


Section
This keyword specifies the table viscosity-versus-temperature dependence (water viscosity

4.30, oil viscosity 4.32).
This table can specify the viscosity-versus-temperature-pressure dependence.
Temperature dependence.
One should enter a table. Each row of this table consists of parameters:
temperature (SI: C , FIELD: F );
viscosity for each component at this temperature (SI, FIELD: cp), (number of values
should be equal to the number of components in the oil or water phases (3-rd parameter
of MODEL (see 13.5.4)))
Temperature and pressure dependence.

One should enter a set of tables (one table for each pressure value):
1. keyword VISCTABLE;
2. keyword ATPRES;
3. pressure value (SI: kPa, FIELD: psi);
4. a table.
Each row of this table consists of parameters:
temperature (SI: C , FIELD: F );
viscosity for each component at this temperature (SI, FIELD: cp), (number of values
should be equal to the number of components in the oil or water phases (3-rd parameter
of MODEL (see 13.5.4)))
In e300 data format water viscosity as a function of temperature is specified via the
keyword WATVISCT (see 12.14.39), oil viscosity OILVISCT (see 12.14.40).
Example 1.
13.5.53. VISCTABLE 1782

Example
VISCTABLE
7 1.45 116456 1199
49 0.77 720 9.2
115 0.31 19.4 0.19
221 0.16 1.12 0.02
309 0.08 0.12 0.01
In this example viscosity values are specified for 3 components at 5 temperatures.
Example 2.
Example
VISCTABLE
ATPRES 300.000
50 0.00E+00 2.15E-02 1.20E-01 5.96E-02 4.14E-02 7.18E-02
110 0.00E+00 4.27E-02 1.54E-01 8.93E-02 4.28E-02 7.59E-02
200 0.00E+00 7.63E-02 1.91E-01 1.26E-01 1.47E-01 6.53E-02
320 0.00E+00 1.14E-01 2.17E-01 1.58E-01 1.71E-01 1.86E-01
410 0.00E+00 1.29E-01 2.19E-01 1.67E-01 1.75E-01 1.84E-01
440 0.00E+00 1.32E-01 2.17E-01 1.67E-01 1.74E-01 1.82E-01
530 0.00E+00 1.46E-01 2.33E-01 1.81E-01 1.85E-01 1.90E-01
620 0.00E+00 1.59E-01 2.39E-01 1.91E-01 1.92E-01 1.94E-01
ATPRES 600.000
50 0.00E+00 2.45E-02 1.26E-01 1.94E-02 4.49E-02 7.76E-02
110 0.00E+00 4.64E-02 1.64E-01 9.64E-02 4.48E-02 7.81E-02
200 0.00E+00 9.02E-02 2.10E-01 1.43E-01 3.57E-02 7.82E-02
320 0.00E+00 1.21E-01 2.24E-01 1.66E-01 1.80E-01 1.96E-01
410 0.00E+00 1.32E-01 2.18E-01 1.69E-01 1.78E-01 1.88E-01
440 0.00E+00 1.36E-01 2.18E-01 1.71E-01 1.79E-01 1.88E-01
530 0.00E+00 1.06E-01 1.60E-01 1.28E-01 1.32E-01 1.37E-01
620 0.00E+00 1.19E-01 1.74E-01 1.42E-01 1.44E-01 1.46E-01
In this example the dependence between viscosity and temperature and pressure is speci-
fied for 6 components.
13.5.53. VISCTABLE 1783

13.5.54 VSMIXCOMP


Section
This keyword specifies the function fk (x) (which is used in oil viscosity calculations
4.32).
Function fk (x) should be specified via 3 keywords:
VSMIXCOMP (see 13.5.54): 'component name';
VSMIXENDP (see 13.5.55): minimal and maximum values of x (in a range from 0 to
1);
VSMIXFUNC (see 13.5.56): 11 values of fk (x).
The keyword has an Eclipse compatible analogue OILVINDX (see 12.14.42). tNavigator
also uses the keyword OILVINDT (see 12.14.43).
Example
VSMIXCOMP 'Comp1'
VSMIXENDP 0 0.40
VSMIXFUNC 0 0.04 0.08 0.12 0.16 0.20 0.24 0.28 0.32 0.36 0.40
In this example fk (x) is specified for component Comp1.
13.5.54. VSMIXCOMP 1784

13.5.55 VSMIXENDP


Section
4.32).
1);
Example
VSMIXCOMP 'Comp1'
VSMIXENDP 0 0.40
VSMIXFUNC 0 0.04 0.08 0.12 0.16 0.20 0.24 0.28 0.32 0.36 0.40
13.5.55. VSMIXENDP 1785

13.5.56 VSMIXFUNC


Section
4.32).
1);
Example
VSMIXCOMP 'Comp1'
VSMIXENDP 0 0.40
VSMIXFUNC 0 0.04 0.08 0.12 0.16 0.20 0.24 0.28 0.32 0.36 0.40
13.5.56. VSMIXFUNC 1786

13.5.57 AVG


Section
This keyword specifies coefficients Ak in gas viscosity correlation formulas 4.35.

Bk are specified via BVG (see 13.5.58).
In e300 data format the coefficients of correlations are set via GASVISCF (see 12.14.45).
Example
AVG 0.00022 0.00017
BVG 0.8 0.7
13.5.57. AVG 1787

13.5.58 BVG


Section
This keyword specifies coefficients Bk in gas viscosity correlation formulas 4.35.

Ak are specified via AVG (see 13.5.57).
In e300 data format the coefficients of correlations are set via GASVISCF (see 12.14.45).
Example
AVG 0.00022 0.00017
BVG 0.8 0.7
13.5.58. BVG 1788

13.5.59 CMM


Section
The keyword specifies component molecular weight (SI: kg/gmol , FIELD: lb/lbmol ),
which is used in gas viscosity calculations 4.36
The same number of values as the number of components (1-st parameter of MODEL (see
In e300 data format molecular weight of hydrocarbon components is specified via the
keyword MW (see 12.13.27), molecular weight of water components MWW.
Example
CMM
0.011 0.35 0.05614
In this example molecular weight of 3 components is specified.
13.5.59. CMM 1789

13.5.60 GASD-ZCOEF


Section
The keyword is specifies the method of gas density calculations. Navigator supports
implicit method only.
Parameter IMPLICIT should be specified after the keyword.
13.5.60. GASD-ZCOEF 1790

13.5.61 GASLIQKV


Section
The keyword specifies the tables of K-values to manage equilibration of gas-liquid

phase. This tables are specified by keywords KVTABLIM (see 12.14.8) and KVTABLE
(see 12.13.16).
The keyword has an Eclipse compatible analogue KVTABLE (see 12.13.16).
Example
INUNIT FIELD
...
GASLIQKV
KVTABLIM 1.4500E+01 2.1895E+03 6.0000E+01 7.1000E+02
KVTABLE N2C1
2.0442E+02 2.1225E+00
4.3737E+02 1.3944E+00
In the example the table of K-values for component N2C1 is specified.
13.5.61. GASLIQKV 1791

13.5.62 COT


Section
The keyword sets compressibility oil, co , dependence on pressure, P, and on bubble

pressure Pbub in particular. This dependence is used to calculate oil formation volume factor,
Bo , which is given by:
Bo (P) = Bo (Pbub ) (1 co (P) (P Pbub ))

in the same line with the keyword:
1. oil compressibility PVT-region number.
in the following lines table is set. Each line of it should contain the following parame-
ters:
1. pressure (SI: kPa, FIELD: psi). The first value in this column is bubble pressure
value in specified PVT-region. Pressure values should be strictly increasing from
line to line;
2. oil compressibility value at this pressure (SI: 1/kPa, FIELD: 1/psi).
The keyword BOT (see 13.5.64) allows to set oil formation volume factor explicitly, as
a table.
Example
COT 1
4889 32.11e-6
5250 30.27e-6
5750 27.62e-6
6251 24.82e-6
6750 21.93e-6
7001 20.45e-6
In the example the keyword COT (see 13.5.62) sets oil compressibility dependence on
pressure in the 1-st PVT-region.
13.5.62. COT 1792

13.5.63 CO


Section
The keyword sets constant oil compressibility value, co , for pressure values which are
greater than bubble pressure value, Pbub . These values are used to calculate oil formation
volume factor, Bo , which is given by:
Bo (P) = Bo (Pbub ) (1 co (P Pbub )).

1. oil compressibility value for pressure values which are greater than bubble pressure
value (SI: 1/kPa, FIELD: 1/psi).
Via the keyword COT (see 13.5.62) it is available to set oil compressibility dependence
on pressure. The keyword BOT (see 13.5.64) allows to set oil formation volume factor
explicitly, as a table.
Example
CO 9.2810E-6
In the example via the keyword CO (see 13.5.63) oil compressibility value for pressure
values greater than bubble pressure is set. It is equal to 9.2810 106 /psi.
13.5.63. CO 1793
13.5.64 BOT


Section
The keyword sets oil formation volume factor, Bo , dependence on pressure, P, and on
bubble pressure Pbub in particular.
1. oil compressibility PVT-region number.
in the following lines table is specified. Each line should contain the following param-
eters:
value in specified PVT-region. Values should be increasing from line to line;
2. oil formation volume factor value at this pressure (SI: 1/kPa, FIELD: 1/psi).
Example
BOT 1
2501.7 1.35953
3000.0 1.35130
3500.0 1.34543
In the example the keyword BOT (see 13.5.64) sets oil formation volume factor depen-
dence on pressure.
13.5.64. BOT 1794

13.5.65 CVO


Section
The keyword sets constant oil viscosity value oconst . This value is used to calculate oil
viscosity values at pressure values which are greater than bubble pressure value, Pbub , by the
following formula:
o (P) = o + oconst (P Pbub ),
where o is oil viscosity value at Pbub value.
1. oil viscosity value (SI: mPa s/kPa, FIELD: cp/psi).
The keyword VOT (see 13.5.66) allows to set oil viscosity dependence on pressure
explicitly, as a table.
Example
CVO 4.6000E-5
In the example oil viscosity value is 4.6000 105 .
13.5.65. CVO 1795

13.5.66 VOT


Section
The keyword sets oil viscosity dependence on pressure, on bubble pressure in particular,
as a table.
1. oil viscosity PVT-region.
in the following lines table is set. Each line should contain the following parameters:
value in specified PVT-region. Values should be increasing from line to line;
2. oil viscosity value at this pressure value (SI: 1/kPa, FIELD: 1/psi).
Example
VOT 1
32.2 5.40
102.3 5.44
505.1 6.03
1503.4 9.04
2011.3 11.41
3000.0 18.06
3500.0 22.63
In the example the keyword VOT (see 13.5.66) sets oil viscosity dependence on pressure.
Bubble pressure Pbub the first value in the first column is 32.2 psi.
13.5.66. VOT 1796

13.5.67 IDEALGAS


Section
The keyword specifies that gas-phase density is obtained from the ideal gas law.
Note. Only one of IDEALGAS (see 13.5.67) and PCRIT (see 12.13.19) can be specified
in the model.
Example
IDEALGAS
13.5.67. IDEALGAS 1797

13.5.68 EOSSET


Section
The keyword sets index number of a new EoS region. The following parameters should
be specified:
1. index number of EoS region.
In the following lines component properties should be specified (keywords MW (see

12.13.27), PCRIT (see 12.13.19), VCRIT (see 12.13.21), TCRIT (see 12.13.17), ZCRIT
(see 12.13.24), BIN (see 13.5.70), PCHOR (see 13.5.71), AC (see 13.5.72), OMEGA (see
13.5.73), OMEGB (see 13.5.73), VSHIFT (see 13.5.74) and others).
Example
EOSSET 1
...
13.5.68. EOSSET 1798

13.5.69 EOSTYPE


Section
equation of state region (EoS region) to which it belongs.
This keyword has an Eclipse compatible analogue EOSNUM (see 12.4.21).
Default: each grid block belongs to the 1-st EoS region.
Example
EOSTYPE
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
This example defines disposition of four equation of state regions for a 5x3x2 grid.
13.5.69. EOSTYPE 1799

13.5.70 BIN


Section
The keyword sets interaction coefficients for user components. The following parameters
1. interaction coefficient. nuser(2nc1nuser)

2 numbers should be specified. nc is the total
number of components, nuser the total number of user components.
This keyword has an Eclipse compatible analogue BIC (see 12.13.32).

Default: 0.
Example
BIN
D41 D42 D43
D51 D52 D53 D54
In the example in the model 5 components are set, 3 of them are user ones. Di j are real
numbers which represent the interaction coefficients between component i and component
j . There interaction coefficients between 4-th and 5-th and each other components are set.
13.5.70. BIN 1800

13.5.71 PCHOR


Section
The keyword specifies component parachors. The following parameters should be speci-
fied:
1. component parachors. It is dimensionless value.The same number of values as the

number of user components in the model should be entered.
This keyword has an Eclipse compatible analogue PARACHOR (see 12.6.56).
Example
PCHOR 74.92 192.74 390.4 /
In the example parachors are entered for 3 user components.
13.5.71. PCHOR 1801

13.5.72 AC


Section
The keyword associates acentric factor with each user component of a compositional
model. The following parameters should be specified:
1. acentric factor. N values should be entered, where N is the number of user components.
This keyword has an Eclipse compatible analogue ACF (see 12.13.30).
Example
AC 0.225 0.132 0.385
In the example acentric factor values for 3 components are set.
13.5.72. AC 1802
13.5.73 OMEGA / OMEGB


Section
The keywords are used to overwrite values of a0 and b0 parameters of equation of

state. One value should be specified for one component.
These keywords have Eclipse compatible analogs OMEGAA (see 12.13.34) and OMEGAB
(see 12.13.34).
Default:
Peng-Robinson (PR) equation of state:
a0 = 0.45723553;
b0 = 0.077796074;
SRK equation of state:
a0 = 0.4274802;
b0 = 0.08664035;
Example
OMEGA 0.459 0.457 0.461 0.462 0.457
OMEGB 0.07791 0.07794 0.0777 0.0780 0.0777
In this example default values for 5 components will be overwritten.
13.5.73. OMEGA / OMEGB 1803

13.5.74 VSHIFT


Section
The keyword sets the volume shifts to be applied to the equation of state molar volumes.
1. volume shift. It is a dimensionless value. nc numbers should be specified, where nc is

the number of model components.
This keyword has an Eclipse compatible analogue SSHIFT (see 12.13.41).

Default: 0.
Example
VSHIFT 0.019066 -0.44122 -0.51069 -0.100732 -0.119513
In the example volume shift values are set for 5 components.
13.5.74. VSHIFT 1804

13.5.75 VGUST


Section
The keyword sets gas viscosity table dependence on pressure for condensate undersatu-
rated gas. The following parameters should be specified:
in the same line the keyword is:
1. PVT region number.
in the following line the table with the following columns is specified:
1. dew point pressure of a new saturated gas mixture formed by reducing the oil.
The first entry is the driest gas dew point pressure, the last entry is the original
saturated gas dew point pressure (SI: kPa; FIELD: psi);
2. corresponding gas viscosity value (cp).
Example
VGUST 1
101.32 0.016453
5000 0.016464
10000 0.016492
13.5.75. VGUST 1805

13.5.76 PADSORP


Section
The keyword sets polymer adsorption table. In each line of it two parameters are set:
1. polymer concentration (SI: kg/m3 ; FIELD: lb/ST B);
2. polymer adsorption level (SI: kg/m3 ; FIELD: lb/ST B).
This keyword is required when polymer model is used (see the keyword MODEL (see
13.5.4) and its parameter POLY). Description of polymer flood model is given in section
Polymer flood in IMEX format.
This keyword has an Eclipse compatible analogue PLYADS (see 12.8.17).
Example
PADSORP
0.000 0.000
0.150 0.042
0.300 0.083
0.450 0.125
0.600 0.166
0.750 0.208
0.900 0.250
1.050 0.291
13.5.76. PADSORP 1806

13.5.77 PPERM


Section
The keyword sets table of absolute permeability dependent polymer properties. Each line
of it should contain the following parameters:
1. absolute permeability (mD);
2. maximum adsorption level (SI: kg/m3 ; FIELD: lb/ST B);
3. residual sorption level (i.e. the amount of polymer left in the rock after injected water
washes some of the polymer away from the rock) (SI: kg/m3 ; FIELD: lb/ST B);
4. polymer accessible pore volume;
5. residual resistance rock factor (greater or equal to 1).
Example
PPERM
10.0 0.3 0.15 0.9 1.2
10000. 0.2 0.1 0.999 1.2
13.5.77. PPERM 1807

13.5.78 PMIX


Section
The keyword sets model of viscosity mixing solution. The following parameters should
be specified:
1. model of viscosity mixing solution:
LINEAR linear;
NONLINEAR nonlinear;
TABLE two column table is set:
(a) ratio of local polymer concentration to the reference one (the keyword PRE-
FCONC (see 13.5.79));
(b) ratio of polymer viscosity to water viscosity.
VELTABLE tables of viscosity dependence on velocity and polymer concentra-
tion are set. In the next lines the following is set:
(a) VWT vv subkeyword VWT and velocity value vv. One table corresponds to
each value (see description of the following parameter);
(b) table which is analogous to the one from the TABLE parameter.
Example
PMIX LINEAR
13.5.78. PMIX 1808

13.5.79 PREFCONC


Section
The keyword sets reference polymer concentration. The following parameters should be
specified:
1. reference polymer concentration (SI: kg/m3 ; FIELD: lb/ST B). It is recommended that
this value would be equal to or greater than polymer injection concentration value.
Example
PREFCONC 3.3
13.5.79. PREFCONC 1809

13.5.80 PVISC


Section
The keyword sets reference polymer viscosity value. The following parameters should be
specified:
1. reference polymer viscosity value, i.e. polymer viscosity value at reference polymer
concentration PREFCONC (see 13.5.79) (SI: mPa-s; FIELD: cp).
Example
PVISC 1.1
13.5.80. PVISC 1810

13.5.81 INCOMP


Section
The keyword sets polymer concentration in injecting phase. The following parameters
1. phase in which polymer is injecting:
WATER water.
2. polymer concentration in the phase (SI: kg/m3 ; FIELD: lb/ST B).
Default:
polymer concentration in the phase: 0.
This keyword has an Eclipse compatible analogue WPOLYMER (see 12.18.151).
Example
INCOMP WATER 1.1
13.5.81. INCOMP 1811

13.6. Rock-Fluid data tNavigator-4.2
13.6 Rock-Fluid data
13.6. Rock-Fluid data 1812

13.6.1 ROCKFLUID

Input Reservoir Other Component

Section
x Rockfluid Initial Numerical Well
The keyword starts the Rock-Fluid data section (13.6).
Example
ROCKFLUID
13.6.1. ROCKFLUID 1813

13.6.2 RPT


Section
The keyword should be entered after the keyword ROCKFLUID.

RPT sets the saturation function region number. After this number water-oil (SWT (see
13.6.3)) and liquid-gas (SLT (see 13.6.4)) permeability tables are entered. Then RTYPE (see
13.6.6) specifies for each grid block the number of saturation function region number to
which it belongs.
The data should be specified the following way:

RPT number COPY oldnumber STONE1 (STONE2),
where
number saturation function region number;
COPY oldnumber additional option: initializes saturation function region number

which has the same rock-fluid properties as the saturation function region oldnumber
(that properties were specified above for oldnumber region);
STONE1 (STONE2) additional option: allows to use Stone model in relative perme-
ability calculations: STONE1 or STONE2.
In the description of the keyword SLT (see 13.6.4) there is a common example for the
keywords RPT, SWT (see 13.6.3) and SLT (see 13.6.4).
13.6.2. RPT 1814

13.6.3 SWT


Section
The keyword specifies a smoothing method for table RP values and relative permeability
table for water-oil system for one saturation function region (RPT (see 13.6.2) sets saturation
function region number).
In the line with the keyword smoothing type is specified:

1. SMOOTHEND option to smooth table RP values via several interpolation types. The
following interpolation types are supported:
LINEAR or OFF linear interpolation;
QUAD quadratic interpolation;
CUBIC cubic interpolation.
This option has tNavigator special analogue the keyword KRSMOOTH (see 12.6.59).
In the following lines the table is specified. The table consists of arbitrary number of
lines (two or more). Water saturation (the first parameter) should increase down the column.
Each line has 4 parameters:
2. KRW (water permeability) (this is function krwo in 2.6)
3. KROW (oil permeability) (this is function krow in 2.6)
4. PCOW (oil-water capillary pressure) (SI: kPa, FIELD: psi) (this is function Pcow
in 2.15.2)
The keyword has an Eclipse compatible analogue SWOF (see 12.6.1).
Default:
SMOOTHEND:
1. in IMEX types models QUAD;
2. in STARS types models LINEAR.
In the description of the keyword SLT (see 13.6.4) there is a common example for the
keywords RPT (see 13.6.2), SWT (see 13.6.3) and SLT (see 13.6.4).
13.6.3. SWT 1815

13.6.4 SLT


Section
table for gas-oil system for one saturation function region (RPT (see 13.6.2) sets saturation
function region number).

lines (two or more). Liquid saturation(the first parameter) should increase down the column.
1. SL (liquid saturation) (this is argument value for functions below)
2. KRG (gas permeability) (this is function krgo in 2.6)
3. KROG (oil permeability) (this is function krog in 2.6)
4. PCOG (oil-gas capillary pressure) (this is function Pcog (SI: kPa, FIELD: psi)
in 2.15.1)
The keyword has an Eclipse compatible analogue SGOF (see 12.6.2).
Default:
SMOOTHEND:
1. in IMEX types models QUAD;

2. in STARS types models LINEAR.
13.6.4. SLT 1816

Example
RPT 1
SWT
0.202 0 1
0.317 0.003 0.413
0.413 0.011 0.119
0.721 0.063 0.011
0.753 0.121 0
SLT
0.585 0.122 0
0.721 0.089 0.003
0.854 0.031 0.042
0.923 0.01 0.171
0.99 0 1
RPT 2
SWT
0.0 0.0 1.00 0
1 1.0 0.00 0
SLT
0.01 1.0 0.0 0.0
0.99 0.0 1.0 0.0
This example sets relative permeability tables SWT (see 13.6.3), SLT (see 13.6.4) for
two saturation function regions (RPT 1, RPT 2).
13.6.4. SLT 1817

13.6.5 SGT


Section
dependence table for gas-oil system on gas saturation for one saturation function region (RPT
(see 13.6.2) sets saturation function region number).

lines (two or more). Gas saturation (the first parameter) should increase down the column.
2. KRG (gas permeability) (this is function krgo in 2.6)
3. KROG (oil permeability) (this is function krog in 2.6)
4. PCOG (oil-gas capillary pressure) (this is function Pcog (SI: kPa, FIELD: psi)
in 2.15.1)
The keyword has an Eclipse compatible analogue SGOF (see 12.6.2).
Default:
SMOOTHEND: QUAD.
13.6.5. SGT 1818

Example
RPT 1
SGT
0.000 0.0000 0.8000 0.00
0.020 0.0000 0.7284 0.00
0.100 0.0617 0.4847 0.00
0.205 0.1451 0.2567 0.00
0.287 0.2111 0.1393 0.00
0.335 0.2499 0.0911 0.00
0.410 0.3107 0.0403 0.00
0.533 0.4111 0.0047 0.00
0.677 0.5867 0.0000 0.00
0.800 0.9500 0.0000 0.00
This example sets table SGT (see 13.6.5) for one saturation function regions (RPT 1).
13.6.5. SGT 1819

13.6.6 RTYPE


Section
The keyword should be followed by one integer for every grid block specifying the satu-
ration function region to which it belongs. This keyword should be entered after the keyword
RPT (see 13.6.2) and tables SWT (see 13.6.3), SLT (see 13.6.4) for all saturation function
regions.
The keyword has an Eclipse compatible analogue SATNUM (see 12.4.3).

The keyword also has stars compatible analogue KRTYPE (see 13.6.7).
Example
RTYPE MATRIX ALL 1 1 2 2 2 2 3 3 3 3 3 3 3 3 3 2 2 2
RTYPE FRACTURE CON 4
In this example matrix blocks (MATRIX) belong to saturation function regions number 1,
2 and 3; fracture blocks (FRACTURE) belong to saturation function region number 4.
13.6.6. RTYPE 1820

13.6.7 KRTYPE


Section
The keyword is the full analogue of RTYPE (see 13.6.6).
13.6.7. KRTYPE 1821

13.6.8 KRTEMTAB


Section
The keyword specifies temperature dependence for critical saturations and endpoints. This
keyword should be entered after the keywords SWT (see 13.6.3), SLT (see 13.6.4). The
data should be specified for each saturation table region RPT (see 13.6.2).
Data format:
KRTEMTAB keyword(1) ... keyword(m)
Where:
keyword(1) ... keyword(m) the keywords from the following list: SWR (see 13.6.9),
SWCRIT (see 13.6.11), SOIRW (see 13.6.13), SGCON (see 13.6.15), SGR (see 13.6.17),
SOIRG (see 13.6.19), SORW (see 13.6.21), SORG (see 13.6.23), KRWIRO (see 13.6.25),
KRGCW (see 13.6.27), KROCW (see 13.6.29), PCGEND (see 13.6.31), PCWEND (see
13.6.33).
Each table row consists of parameters:
temperature (SI: C, FIELD: F);
the value of keyword(1) at this temperature;
...
the value of keyword(m) at this temperature.
The keyword has an Eclipse compatible analogue ENPTVT (see 12.14.69).
Detailed description of phase relative permeabilities scaling is in the section 4.35.2.
The keywords in the list above (SWR (see 13.6.9), SWCRIT (see 13.6.11) etc), specify
properties in whole saturation table region. To specify properties in each grid block, use the
keywords BSWR (see 13.6.10), BSWCRIT (see 13.6.12), BSOIRW (see 13.6.14), BSGCON
(see 13.6.16), BSGR (see 13.6.18), BSOIRG (see 13.6.20), BSORW (see 13.6.22), BSORG
(see 13.6.24), BKRWIRO (see 13.6.26), BKRGCW (see 13.6.28), BKROCW (see 13.6.30),
BPCGMAX (see 13.6.32), BPCWMAX (see 13.6.34).
13.6.8. KRTEMTAB 1822

Example
RPT 1
SWT
0.30 0 1 1
0.35 0.005 0.5 0.9
0.60 0.036 0.01 0.3
0.74 0.121 0 0.01
SLT
0.65 0.14 0 0.0
0.72 0.039 0.01 0.0
0.89 0.01 0.178 0.0
0.99 0 1 0.0
KRTEMTAB SORW SOIRW PCWEND
0 0.311 0.311 0
50 0.3 0.3 0
100 0.14 0.14 14
200 0.049 0.049 44
300 0.023 0.023 76
400 0.02 0.02 99
RPT 2
SWT
0.04 0 1 0
0.96 1 0 0
SLT
0.04 1 0.0 0.0
0.96 0.0 1 0.0
KRTEMTAB SORW SOIRW
0 0.04 0.04
50 0.04 0.04
100 0.04 0.04
200 0.04 0.04
300 0.04 0.04
400 0.04 0.04
In this example critical saturations and endpoints versus temperature are specified for two
saturation point regions (regions are set using RPT (see 13.6.2)).
13.6.8. KRTEMTAB 1823

13.6.9 SWR


Section
The keyword sets SW L minimal value of water saturation SW for one saturation table
region (RPT (see 13.6.2)).
The keyword is analogous to the 2-nd parameter of Eclipse compatible keyword ENPTVT
(see 12.14.69).
This keyword is used with KRTEMTAB (see 13.6.8); in the description of KRTEMTAB
(see 13.6.8) there is an example of theirs usage.
To specify properties in each grid block (not in saturation point region), use the keyword
BSWR (see 13.6.10).
13.6.9. SWR 1824

13.6.10 BSWR


Section
The keyword sets SW L minimal value of water saturation SW in each grid block.
The same number of values as the number of grid blocks should be entered.
This keyword has an Eclipse compatible analogue SWL (see 12.6.27).
This keyword should be entered after the keywords SWT (see 13.6.3), SLT (see 13.6.4),
KRTEMTAB (see 13.6.8).
To specify properties in whole saturation table region (not in each grid block), use the
keyword SWR (see 13.6.9).
13.6.10. BSWR 1825

13.6.11 SWCRIT


Section
The keyword sets SWCR maximal (critical) value of water saturation SW (for which
krW (SW ) = 0) for one saturation table region (RPT (see 13.6.2)).
The keyword is analogous to the 3-rd parameter of Eclipse compatible keyword ENPTVT
(see 12.14.69).
BSWCRIT (see 13.6.12).
13.6.11. SWCRIT 1826

13.6.12 BSWCRIT


Section
The keyword sets SWCR maximal (critical) value of water saturation SW (for which
krW (SW ) = 0) in each grid block.
This keyword has an Eclipse compatible analogue SWCR (see 12.6.30).
keyword SWCRIT (see 13.6.11).
13.6.12. BSWCRIT 1827

13.6.13 SOIRW


Section
The keyword sets SWU maximal value of water saturation SW for one saturation table
The keyword is analogous to the 4-th parameter of Eclipse compatible keyword ENPTVT
(see 12.14.69).
BSOIRW (see 13.6.14).
13.6.13. SOIRW 1828

13.6.14 BSOIRW


Section
The keyword sets SWU maximal value of water saturation SW in each grid block.
This keyword has an Eclipse compatible analogue SWU (see 12.6.34).
keyword SOIRW (see 13.6.13).
13.6.14. BSOIRW 1829

13.6.15 SGCON


Section
The keyword sets SGL minimal value of gas saturation SG for one saturation table
(see 12.14.69).
BSGCON (see 13.6.16).
13.6.15. SGCON 1830

13.6.16 BSGCON


Section
The keyword sets SGL minimal value of gas saturation SG in each grid block.
This keyword has an Eclipse compatible analogue SGL (see 12.6.29).
keyword SGCON (see 13.6.15).
13.6.16. BSGCON 1831

13.6.17 SGR


Section
The keyword sets SGCR maximal (critical) value of gas saturation SG (for which
krG (SG ) = 0) for one saturation table region (RPT (see 13.6.2)).
(see 12.14.69).
BSGR (see 13.6.18).
13.6.17. SGR 1832

13.6.18 BSGR


Section
The keyword sets SGCR maximal (critical) value of gas saturation SG (for which
krG (SG ) = 0) in each grid block.
This keyword has an Eclipse compatible analogue SGCR (see 12.6.31).
keyword SGR (see 13.6.17).
13.6.18. BSGR 1833

13.6.19 SOIRG


Section
The keyword sets SGU maximal value of gas saturation SG for one saturation table
(see 12.14.69).
BSOIRG (see 13.6.20).
13.6.19. SOIRG 1834

13.6.20 BSOIRG


Section
The keyword sets SGU maximal value of gas saturation SG in each grid block.
This keyword has an Eclipse compatible analogue SGU (see 12.6.35).
keyword SOIRG (see 13.6.19).
13.6.20. BSOIRG 1835

13.6.21 SORW


Section
The keyword sets SOWCR maximal (critical) value of the function SO = 1 SW SGL ,
for which krOW (SW ) = 0 for one saturation table region (RPT (see 13.6.2)).
(see 12.14.69).
BSORW (see 13.6.22).
13.6.21. SORW 1836

13.6.22 BSORW


Section
The keyword sets SOWCR maximal (critical) value of the function SO = 1 SW SGL ,
for which krOW (SW ) = 0 in each grid block.
This keyword has an Eclipse compatible analogue SOWCR (see 12.6.32).
keyword SORW (see 13.6.21).
13.6.22. BSORW 1837

13.6.23 SORG


Section
The keyword sets SOGCR maximal (critical) value of the function SO = 1 SG SW L ,

for which krOG (SG ) = 0 for one saturation table region (RPT (see 13.6.2)).
(see 12.14.69).
BSORG (see 13.6.24).
13.6.23. SORG 1838

13.6.24 BSORG


Section
The keyword sets SOGCR maximal (critical) value of the function SO = 1 SG SW L ,

for which krOG (SG ) = 0 in each grid block.
This keyword has an Eclipse compatible analogue SOGCR (see 12.6.33).
keyword SORG (see 13.6.23).
13.6.24. BSORG 1839

13.6.25 KRWIRO


Section
The keyword sets krW max maximal value of water relative permeability krW (SW ) for
one saturation table region (RPT (see 13.6.2)).
The keyword is analogous to the 2-nd parameter of Eclipse compatible keyword ENKRVT
(see 12.14.70).
BKRWIRO (see 13.6.26).
13.6.25. KRWIRO 1840

13.6.26 BKRWIRO


Section
The keyword sets krW max maximal value of water relative permeability krW (SW ) in
each grid block.
This keyword has an Eclipse compatible analogue KRW (see 12.6.43).
keyword KRWIRO (see 13.6.25).
13.6.26. BKRWIRO 1841

13.6.27 KRGCW


Section
The keyword sets krGmax maximal value of gas relative permeability krG (SG ) for one
saturation table region (RPT (see 13.6.2)).
The keyword is analogous to the 3-rd parameter of Eclipse compatible keyword ENKRVT
(see 12.14.70).
BKRGCW (see 13.6.28).
13.6.27. KRGCW 1842

13.6.28 BKRGCW


Section
The keyword sets krGmax maximal value of gas relative permeability krG (SG ) in each
grid block.
This keyword has an Eclipse compatible analogue KRG (see 12.6.44).
keyword KRGCW (see 13.6.27).
13.6.28. BKRGCW 1843

13.6.29 KROCW


Section
The keyword sets krOmax maximal value of oil relative permeability (functions
krOW (SW ) and krOG (SG )) for one saturation table region (RPT (see 13.6.2)).
The keyword is analogous to the 4-th parameter of Eclipse compatible keyword ENKRVT
(see 12.14.70).
BKROCW (see 13.6.30).
13.6.29. KROCW 1844

13.6.30 BKROCW


Section
The keyword sets krOmax maximal value of oil relative permeability (functions
krOW (SW ) and krOG (SG )) in each grid block.
This keyword has an Eclipse compatible analogue KRO (see 12.6.42).
keyword KROCW (see 13.6.29).
13.6.30. BKROCW 1845

13.6.31 PCGEND


Section
The keyword sets PCGmax maximal value of gas capillary pressure PcOG (SG ) (SI: kPa,
FIELD: psi) for one saturation point region (RPT (see 13.6.2)).
The keyword is analogous to the 2-nd parameter of Eclipse compatible keyword ENPCVT
(see 12.14.71).
BPCGMAX (see 13.6.32).
13.6.31. PCGEND 1846

13.6.32 BPCGMAX


Section
The keyword sets PCGmax maximal value of gas capillary pressure PcOG (SG ) (SI: kPa,
FIELD: psi) in each grid block.
This keyword has an Eclipse compatible analogue PCG (see 12.6.47).
keyword PCWEND (see 13.6.33). PCGEND (see 13.6.31).
13.6.32. BPCGMAX 1847

13.6.33 PCWEND


Section
The keyword sets PCW max maximal value of water capillary pressure PcOW (SW ) (SI:
kPa, FIELD: psi) for one saturation point region (RPT (see 13.6.2)).
The keyword is analogous to the 3-rd parameter of Eclipse compatible keyword ENPCVT
(see 12.14.71).
BPCWMAX (see 13.6.34).
13.6.33. PCWEND 1848

13.6.34 BPCWMAX


Section
The keyword sets PCW max maximal value of water capillary pressure PcOW (SW ) (SI:
kPa, FIELD: psi) in each grid blocks.
This keyword has an Eclipse compatible analogue PCW (see 12.6.46).
keyword PCWEND (see 13.6.33).
13.6.34. BPCWMAX 1849

13.6.35 PTHRESHI / PTHRESHJ / PTHRESHK


Section
The keyword sets pressure gradient threshold for the flow between block (I, J, K) and
another one connected to it in I + / J + / K + direction correspondingly. The following
1. pressure gradient threshold for each grid block (SI: kPa/m, FIELD: Psi/ f t );
Default:
pressure gradient threshold: 0.
This keyword has an Eclipse compatible analogue THPRES (see 12.15.7).
13.6.35. PTHRESHI / PTHRESHJ / PTHRESHK 1850


13.7.1 INITIAL


Section
Rockfluid x Initial Numerical Well
The keyword starts the section Initial conditions (13.7).
Example
INITIAL
13.7.1. INITIAL 1852

13.7.2 VERTICAL


Section
This option sets that pressures are obtained from hydrostatic equation and saturations
from capillary pressure tables.
The option has these suboptions:

VERTICAL DEPTH_AVE WATER_OIL EQUIL
DEPTH_AVE - block saturation is determined as average saturation over the depth

interval stretched over the grid block. Thisoption uses information from the keywords
DWOC (see 13.7.10), DGOC (see 13.7.11), SW (see 13.7.15), SO (see 13.7.13), SG
(see 13.7.14).
WATER_OIL - perform gravity-capillary equilibrium initialization of a reservoir ini-

tially containing no gas.
EQUIL - during the simulation a pressure correction is added to each phase thus
the reservoir initially is in gravitational equilibrium. Saturations are taken as average
saturations over depth. Hence gravitational equilibrium isnt established just by setting
saturations from capillary pressure tables.
13.7.2. VERTICAL 1853

13.7.3 SWINIT


Section
The keyword sets initial water saturation while maintaining gravity-capillary equilib-
rium generated by the DEPTH_AVE option (see the keyword VERTICAL (see 13.7.2)).
This keyword can be used only with the keyword VERTICAL (see 13.7.2) and its option
DEPTH_AVE.
1. initial water saturation for each cell.
Default:
if for some cell SWINIT (see 13.7.3) value is not specified, then its initial water
saturation is determined via option DEPTH_AVE or via keywords SW (see 13.7.15),
SO (see 13.7.13) and SG (see 13.7.14).
The keyword has an Eclipse compatible analogue SWATINIT (see 12.6.48).
Example
*SWINIT CON 0.3
In the example initial water saturation of entire reservoir is 0.3.
13.7.3. SWINIT 1854

13.7.4 PB


Section
The keyword sets initial bubble point pressure for each grid block (SI: kPa, FIELD: psi).
The keyword has an Eclipse compatible analogue PBUB (see 12.15.30).
Example
PB MATRIX CON 1200
PB FRACTURE CON 1200
This example sets initial bubble point pressure for matrix (MATRIX) and fracture
(FRACTURE) blocks equal to 1200. (CON (see 13.1.3) specifies an array, all elements
of this array are equal.)
13.7.4. PB 1855
13.7.5 DATUMDEPTH


Section
The keyword sets the datum depth for calculations of depth corrected pressures.
One should specify the same number of keywords DATUMDEPTH and values as the number
of FIP regions.
One can use this keywords with suboption INITIAL: the corrected datum pressures will
be calculated using the initial equilibrium pressure distribution.
The keyword has an Eclipse compatible analogue DATUM (see 12.15.34) (for whole
reservoir) and DATUMR (see 12.15.35) (for several FIP regions).
Example
DATUMDEPTH 2500 INITIAL
The example sets datum depth 2500.
Example
DATUMDEPTH 2500 INITIAL
DATUMDEPTH 1500
DATUMDEPTH 3125
This example sets datum depths for 3 FIP regions.
13.7.5. DATUMDEPTH 1856

13.7.6 INITREGION


Section
The keyword sets the initialization region number. The data below is assigned to this
region. The following keywords can be specified after INITREGION: REFPRES (see 13.7.8),
REFDEPTH (see 13.7.9), DWOC (see 13.7.10).
INTYPE (see 13.7.7) for every grid block specifies the initialization region to which it be-
longs.
Example
INITREGION 1
REFDEPTH 4500
REFPRES 1600
DWOC 2500
INITREGION 2
REFPRES 8500
REFDEPTH 1230
DWOC 1530
DGOC 1230
In this example there are two initialization regions. For each region reference depth
(REFDEPTH (see 13.7.9)), reference pressure (REFPRES (see 13.7.8)), water-oil contact
depth (DWOC (see 13.7.10)) and gas-oil contact depth (DGOC (see 13.7.11)) are given.
13.7.6. INITREGION 1857

13.7.7 INTYPE


Section
The keyword should be followed by one integer for every grid block specifying the ini-
tialization region to which it belongs.
Initialization regions are specified using INITREGION (see 13.7.6), properties of each region
REFPRES (see 13.7.8), REFDEPTH (see 13.7.9), DWOC (see 13.7.10).
Example
INITREGION 1
REFDEPTH 4500
REFPRES 1600
DWOC 2500
INTYPE CON 1
In this example there is one initialization region. For this region reference depth
depth (DWOC (see 13.7.10)) and gas-oil contact depth (DGOC (see 13.7.11)) are given. All
grid blocks belong to this initialization region (CON specifies the constant value array).
13.7.7. INTYPE 1858

13.7.8 REFPRES


Section
The keyword specifies the reference pressure (SI: kPa, FIELD: psi) at the reference
depth REFDEPTH (see 13.7.9).
REFDEPTH and REFPRES can be specified for multiple initialization regions (use INITRE-
GION (see 13.7.6)).
The keywords REFPRES (see 13.7.8), REFDEPTH (see 13.7.9), DWOC (see 13.7.10),
DGOC (see 13.7.11), VERTICAL (see 13.7.2) have an Eclipse compatible analogue EQUIL
(see 12.15.2).
1-st parameter of EQUIL (see 12.15.2) corresponds to REFDEPTH (see 13.7.9), 2-nd
REFPRES (see 13.7.8), 3-rd DWOC (see 13.7.10), 5-th DGOC (see 13.7.11).
Example
INITREGION 1
REFDEPTH 4500
REFPRES 1600
DWOC 2500
INITREGION 2
REFPRES 8500
REFDEPTH 1230
DWOC 1530
DGOC 1230
13.7.8. REFPRES 1859

13.7.9 REFDEPTH


Section
The keyword specifies the reference depth (SI: m, FIELD: f t ). At the reference depth
the keyword REFPRES (see 13.7.8) specifies the reference pressure.
REFDEPTH and REFPRES can be specified for multiple initialization regions (use INITRE-
GION (see 13.7.6)).
(see 12.15.2).
Example
INITREGION 1
REFDEPTH 4500
REFPRES 1600
DWOC 2500
INITREGION 2
REFPRES 8500
REFDEPTH 1230
DWOC 1530
DGOC 1230
13.7.9. REFDEPTH 1860

13.7.10 DWOC


Section
The keyword sets the water-oil contact depth (SI: m, FIELD: f t ).

DWOC can be specified for multiple initialization regions (use INITREGION (see 13.7.6)).
If VERTICAL DEPTH_AVE (VERTICAL (see 13.7.2)) is present, the resulting water

saturation will reflect the water-oil transition zone caused by non-zero capillary pressure.
(see 12.15.2).
Example
INITREGION 1
REFDEPTH 4500
REFPRES 1600
DWOC 2500
INITREGION 2
REFPRES 8500
REFDEPTH 1230
DWOC 1530
DGOC 1230
13.7.10. DWOC 1861

13.7.11 DGOC


Section
The keyword sets the gas-oil contact depth (SI: m, FIELD: f t ).

DGOC can be specified for multiple initialization regions (use INITREGION (see 13.7.6)).
If VERTICAL DEPTH_AVE (VERTICAL (see 13.7.2)) is present, the resulting gas satu-
ration will reflect the liquid-gas transition zone caused by non-zero capillary pressure.
(see 12.15.2).
Example
INITREGION 1
REFDEPTH 4500
REFPRES 1600
DWOC 2500
INITREGION 2
REFPRES 8500
REFDEPTH 1230
DWOC 1530
DGOC 1230
13.7.11. DGOC 1862

13.7.12 WOC_SW


Section
The keyword set water saturation value below water-oil contact in each initialization
region. The following parameters should be specified:
1. water saturation value.
This keyword has a MORE compatible analog AQUW (see 14.4.23).

Default:
water saturation value: 0.9999.
Example
INITREGION 1
WOC_SW 0.5
In the example in the 1-st initialization region water saturation below WOC is 0.5.
13.7.12. WOC_SW 1863

13.7.13 SO


Section
The keyword sets the initial oil saturation. The same number of values as the number of
grid blocks should be specified. The values of oil saturation should be in the range from 0
to 1.
The keyword has an Eclipse compatible analogue SOIL (see 12.15.12).
Example
SO CON 0.7
In this example the initial oil saturation in all grid blocks is equal to 0.7 (CON (see
13.1.3) specifies the constant value array).
13.7.13. SO 1864
13.7.14 SG


Section
The keyword sets the initial gas saturation. The same number of values as the number of
grid blocks should be specified. The values of gas saturation should be in the range from 0
to 1.
The keyword has an Eclipse compatible analogue SGAS (see 12.15.11).
Example
SG CON 0
In this example the initial gas saturation in all grid blocks is equal to 0 (CON (see 13.1.3)
specifies the constant value array).
13.7.14. SG 1865
13.7.15 SW


Section
The keyword sets the initial water saturation. The same number of values as the number
of grid blocks should be specified. The values of water saturation should be in the range
from 0 to 1.
The keyword has an Eclipse compatible analogue SWAT (see 12.15.10).
Example
SW CON 0.3
In this example the initial water saturation in all grid blocks is equal to 0.3 (CON (see
13.7.15. SW 1866
13.7.16 PRES


Section
The keyword specifies the initial reservoir pressure (SI: kPa|, FIELD: psi) for each grid
block. The same number of values as the number of grid blocks should be specified.
The keyword has an Eclipse compatible analogue PRESSURE (see 12.15.8).
Example
PRES CON 200
In this example the same initial pressure is specified in all grid blocks (CON (see 13.1.3)
specifies the constant value array).
13.7.16. PRES 1867

13.7.17 TEMP


Section
The keyword specifies the initial reservoir temperature (SI: C , FIELD: F ) for each grid
block. The same number of values as the number of grid blocks should be specified.
The keyword has an Eclipse compatible analogue TEMPI (see 12.15.26).
Example
TEMP CON 90
In this example the same initial temperature is specified in all grid blocks (CON (see
13.7.17. TEMP 1868

13.7.18 CONC_SLD


Section
The keyword specifies initial mole fraction of the components in the solid phase (SI:
gmol/m3 , FIELD: lbmol/ f t 3 ). One should specify the component name and the value of
initial mole fraction of this component in the solid phase for each grid block.
Default: 0.
Example
CONC_SLD 'Coke' CON 0.488
In this example the same initial mole fraction of the component 'Coke' in the solid
phase is specified in all grid blocks (CON (see 13.1.3) specifies the constant value array).
13.7.18. CONC_SLD 1869

13.7.19 MFRAC_OIL


Section
The keyword specifies initial mole fraction of the components in the oil phase. One
should specify the component name and the value of initial mole fraction of this component
in the oil phase for each grid block.
The keyword has an Eclipse compatible analogue XMF (see 12.15.17).
Default: 0.
Example
MFRAC_OIL 'DeadOil' CON 0.48223
In this example the same initial mole fraction of the component 'DeadOil' in the oil
13.7.19. MFRAC_OIL 1870

13.7.20 MFRAC_GAS


Section
The keyword specifies initial mole fraction of the components in the gas phase. One
should specify the component name and the value of initial mole fraction of this component
in the gas phase for each grid block.
The keyword has an Eclipse compatible analogue YMF (see 12.15.18).
Default: 0.
Example
MFRAC_GAS 'comp4' CON 0.0087
In this example the same initial mole fraction of the component 'comp4' in the gas
13.7.20. MFRAC_GAS 1871

13.7.21 PBC


Section
The keyword specifies bubble point pressure at initial temperature at each block for
specified component. This value is converted to initial mole fraction of this component by
the following formula:
1
Xi = ,
Ki (Pbi , T )
where Ki (Pbi , T ) K-value of this component (KV1 (see 13.5.26)), evaluated at initial tem-
perature T and Pbi value.
1. component name;
2. bubble point pressure (SI: kPa, FIELD: psi).
Example
PBC 'Soln_Gas' CON 1250
In the example the keyword PBC specifies initial bubble point pressure for component
Soln_Gas. It is equal to 1250 psi.
13.7.21. PBC 1872

13.7.22 SEPARATOR


Section
The keyword sets separator stages conditions. Parameters of this keyword can be entered
by two ways: standard one and advanced one. In standard way conditions are set via table.
Each line of it corresponds to one separator stage. Columns of this table set the following:
1. the separator pressure (METRIC: kPa; SI: psi);
2. the separator temperature (METRIC: kPa; SI: psi).

In advanced way it is expected to specify the following parameters:
1. subkeyword EOS indicating that EOS region number and 2 characteristics of the stage
will be entered next;
2. EOS region number (see keyword EOSSET (see 13.5.68));
3. stage pressure (SI: kPa, FIELD: psi);
4. stage temperature (SI: C , FIELD: F );
5. subkeyword LIQUID-TO or VAPOR-TO indicating that destination of water of vapor

will be set next;
6. stage number of fluid:
stage number stage of current separator to which stage output is fed;

fluid it specifies the surface stream which is the destination of the particular
output of the current stage. It can has 3 values: GAS, INL, OIL.
7. subkeyword STREAM-DEN indicating that density calculation method will be entered

next;
8. fluid type. It can has 3 values: GAS, INL, OIL;
9. fluid density calculation method:
EOS;
GASLAW.
10. if previous parameter is EOS, then EOS region number is specified. Otherwise, com-
pressibility factor value is specified;
13.7.22. SEPARATOR 1873

11. pressure at which density is calculated (SI: kPa, FIELD: psi);
12. temperature at which density is calculated (SI: C , FIELD: F );
This keyword has an Eclipse compatible analogue FIPSEP (see 12.15.21).
Example
*SEPARATOR 815.000 80.00000
65.00000 80.00000
14.70000 60.00000
Standard way to specify parameters.
Example
*SEPARATOR
*EOS 1 101.3 150.6 *LIQUID-TO 2
*EOS 1 10.3 360.0 *LIQUID-TO 'OIL'
*STREAM-DEN
'GAS' *GASLAW 1 14.69 60.
'OIL' *GASLAW 1 14.69 60.
Advanced way to specify parameters.
13.7.22. SEPARATOR 1874

13.8. Numerical methods control tNavigator-4.2
13.8 Numerical methods control
13.8. Numerical methods control 1875

13.8.1 NUMERICAL


Section
Rockfluid Initial x Numerical Well
The keyword starts the section Numerical methods control (13.8).
Example
NUMERICAL
13.8.1. NUMERICAL 1876

13.8.2 TFORM


Section
See the keyword TFORM (see 12.1.8).
13.8.2. TFORM 1877

13.8.3 ISOTHERMAL


Section
See description of the option ISOTHERMAL of the keyword TNAVCTRL (see 12.1.4).
13.8.3. ISOTHERMAL 1878

13.8.4 MINTEMP


Section
The keyword specifies minimal formation temperature. The following parameters should
be specified:
1. minimal formation temperature (SI: C, FIELD: F);
By default:
minimal formation temperature: 1 C .
Analogous to the keyword is the 1-st parameter of the keyword TRANGE (see 12.18.226),
which is used by Eclipse.
Example
MINTEMP 50
13.8.4. MINTEMP 1879

13.8.5 MAXTEMP


Section
The keyword specifies maximal formation temperature. The following parameters should
be specified:
1. maximal formation temperature (SI: C, FIELD: F).
By default:
maximal formation temperature: 2000 C .
Analogous to the keyword is the 2-nd parameter of the keyword TRANGE (see
12.18.226), which is used by Eclipse.
Example
MAXTEMP 250
13.8.5. MAXTEMP 1880

13.9. Well and recurrent data tNavigator-4.2
13.9 Well and recurrent data
13.9. Well and recurrent data 1881

13.9.1 HEATR


Section
Rockfluid Initial Numerical x Well
The keyword indicates constant heat transfer rate to blocks and sets the value of this
transfer rate (SI: J/day, FIELD: Btu/day). The value of rate should be specified for each
block.
Description of heater simulation is given in the section Heater simulation.
By default:
value of transfer rate is equal to 0.
The keyword has an Eclipse compatible analogue HEATER (see 12.18.157).
Example
HEATR ALL
0 0 0 0 0
0 0 0 0 0
0 0 0 0 0
1500 1500 1500 1500 1500
1500 1500 1500 1500 1500
1500 1500 1500 1500 1500
In the example for each grid block size of 5x3x2 heat transfer rate value is set. In the
first layer in Z-direction it is 0, in the second one it is 1500 J/day.
Example
HEATR KVAR
4*0 1500 5*0
In the example values of HEATR (see 13.9.1) are constant in each block of the layer in
Z -direction (it is specified by the keyword KVAR). They are equal to 0 in the first 4 layers,
1500 J/day in the fifth one and 0 for five other layers of the model.
13.9.1. HEATR 1882

13.9.2 TMPSET


Section
The keyword specifies maximal value of temperature for UHTR (see 13.9.3) coefficient
for each block (SI: C , FIELD: F ).
Description of heater simulation is given in the section 4.31.
Example
UNITS SI
...
TMPSET KVAR
4*15 500 5*15
In the example values of TMPSET (see 13.9.2) are constant in each block of the layer in
Z -direction (it is specified by the keyword KVAR) and equal correspondingly to 15C in the
first 4 layers, 500C in the fifth one and 15C for five other layers of the model.
13.9.2. TMPSET 1883

13.9.3 UHTR


Section
The keyword sets the proportional heat transfer coefficient between value of heat trans-
fer and difference of current block temperature and maximal block temperature which was
specified by the keyword TMPSET (see 13.9.2) (SI: J/day C , FIELD: Btu/day F ). The
keyword should be used in conjunction with the keyword TMPSET.
Description of heater simulation is given in the section 4.31.
UHTR > 0 - heat gain coefficient. The rate of heat gain is equal to UHT R(T MPSET
T ) while current temperature T < T MPSET . Otherwise, the rate is equal to 0;
UHTR < 0 - heat loss coefficient. The rate of heat loss is equal to |UHT R| (T
T MPSET ), while current temperature T > T MPSET . Otherwise, the rate is equal to
0.
By default:
coefficient is equal to 0.
Example
UHTR KVAR
4*0 1500 5*0
In the example values of UHTR (see 13.9.3) are constant in each layer in Z -direction (it
is specified by the keyword KVAR). They are equal to 0 in the first 4 layers, 1500J/day in
the fifth one and 0 for five other layers of the model.
13.9.3. UHTR 1884

13.9.4 RUN


Section
The keyword starts the section Well and recurrent data (13.9).
Example
RUN
13.9.4. RUN 1885

13.9.5 DATE


Section
The keyword sets the date and time when the well change occurs. This date should be
entered in the following format:
YYYY MM DD
YYYY - year (integer), MM - month (integer), DD - day (real number). If the well change
occurs at noon the day may be entered as DD.5.
This keyword DATE should be entered immediately after RUN (see 13.9.4) to denote the
date of simulation start (an Eclipse compatible analogue is START (see 12.1.13)).
If DATE is used two times and there are well changes between them, these well changes are
enable since the first DATE.
The keyword has an Eclipse compatible analogue DATES (see 12.18.105).
Example
DATE 1973 4 17.5
This example sets the date: April 17, 1973, at noon.
13.9.5. DATE 1886

13.9.6 WELL


Section
This keyword introduces a new well, defining information on its name and coordinates.
The data should be specified in the following format:
WELL well-number (well-name) (VERT ibl jbl) (ATTACHTO group-name)
well-number (well-name) well number (or name); one or two these parameters can be
entered.
One can use the suboptions:
VERT ibl jbl the well is vertical; ibl bottom hole or well head coordinates in X
direction (IW) and jbl bottom hole or well head coordinates in Y direction (JW),
ATTACHTO group-name name of the group to which this well belongs.
The keyword has an Eclipse compatible analogue WELSPECS (see 12.18.3) (four pa-
rameters of WELSPECS are the same).
Example
WELL 2 'ProducerL'
WELL 7 VERT 17 23
Here two wells are defined: well number 2 'ProducerL' and vertical well number 7, its
bottom hole is situated at X = 17 and Y = 23.
13.9.6. WELL 1887

13.9.7 PRODUCER


Section
The keyword specifies a producer (first a well should be entered using the keyword WELL
(see 13.9.6)).
PRODUCER well-number (well-name)
One should enter the well number and (or) well name.
The keyword is analogous to the first parameter of an Eclipse compatible keyword
WCONPROD (see 12.18.34).
Example
WELL 7
PRODUCER 7
The example specifies the well number 7 as producer.
13.9.7. PRODUCER 1888

13.9.8 INJECTOR


Section
The keyword specifies an injectorr (first a well should be entered using the keyword
WELL (see 13.9.6)).
1. INJECTOR
2. [additional parameter] . Injector type can be specified:
MOBWEIGHT total mobility weighted injector. tNavigator uses in calculation t

he total mobility of a grid block with connection. tNavigator allows to use only
the type IMPLICIT: the total mobility is calculated implicitly (the most up-to-date
value is used).
UNWEIGHT unweighted injector. Injected fluid mobility is considered as a part
of a well index.
3. name (number) of the well (wells).
This keyword has an Aclipse-compatible analogue WCONINJE (see 12.18.36).
Example
WELL 10
INJECTOR UNWEIGHT 10
In this example the well 10 is unweighted injector.
13.9.8. INJECTOR 1889

13.9.9 SHUTIN


Section
The keyword indicates that a well is shut in (first a well should be entered using the
keyword WELL (see 13.9.6), PRODUCER (see 13.9.7)).
SHUTIN well-number (well-name)
One should enter the well number and (or) well name.
The keyword has an Eclipse compatible analogue WELOPEN (see 12.18.107) (allows to
shut in a well or connection).
Example
WELL 7
PRODUCER 7
DATE 1973 4 17
SHUTIN 7
This example shuts in a well number 7 on April 17, 1973.
13.9.9. SHUTIN 1890

13.9.10 OPERATE


Section
This keyword sets the well controls and action to be done if one of controls is violated.
(First a well should be entered using the keyword WELL (see 13.9.6), PRODUCER (see
13.9.7). INJECTOR (see 13.9.8).) The data should be entered in one of the following formats:
OPERATE MAX (or MIN) well-control value action

or
OPERATE MIN STEAMTRAP value
where:
1. MAX (or MIN) - maximum (MAX) or minimum (MIN) control is specified using value;
2. well-control - well control:
STL liquid rate control (oil and water) (SI: m3 /day, FIELD: bbl/day) (LRAT
in Eclipse compatible keywords),
STO oil rate control (SI: m3 /day, FIELD: bbl/day) (ORAT in Eclipse compat-
ible keywords),
STG gas rate control (SI: m3 /day, FIELD: f t 3 /day) (GRAT in Eclipse com-
patible keywords),
STW water rate control (SI: m3 /day, FIELD: bbl/day) (WRAT in Eclipse
compatible keywords),
BHW water rate in reservoir conditions control (SI: m3 /day, FIELD: bbl/day);
BHP bottom hole pressure control (SI: kPa, FIELD: psi); minimum bottom
hole pressure for producers must be specified, otherwise it will be taken 101.3
kPa (BHP in Eclipse compatible keywords),
WHP tubing head pressure control (SI: kPa, FIELD: psi) (THP in Eclipse
compatible keywords),
BHF reservoir liquid rate control (oil, water, gas) (SI: m3 /day, FIELD:
bbl/day) (RESV in Eclipse compatible keywords).
STEAM steam rate expressed in CWE cold water equivalent (SI: m3 /day,
FIELD: bbl/day). In case if STEAM is used the 1-st parameter of OPERATE
13.9.10. OPERATE 1891

should be MAX. (STEAM corresponds to CWE, specified via 15-th parameter of

WCONPROD (see 12.18.34), compatible with Eclipse);
STEAMTRAP value the value is by how much the steam saturation tempera-
ture exceeds the temperature of the produced water (SI: C , FIELD: F ) (17-th
parameter of the keyword WCONPROD (see 12.18.34) is analogous for this one).
3. value - control value (if the 2-nd parameter is not STEAMTRAP);
4. action - action to be done if this control is violated: CONT well will switch to the
violated control.
The keyword has an Eclipse compatible analogue WCONPROD (see 12.18.34) (for
producers), WCONINJE (see 12.18.36) (for injectors).
Example
WELL 7
PRODUCER 7
OPERATE MAX STL 42 CONT
OPERATE MIN BHP 250 CONT
This example sets for producer number 7 maximum liquid rate control 42, minimum
bottom hole pressure control 250. If one of these controls is violated, well will switch to
the violated control.
13.9.10. OPERATE 1892

13.9.11 ALTER


Section
This keyword alters the first control value for the well, defined by OPERATE (see
12.3.25), Second and other controls defined by OPERATE (see 12.3.25) cant be altered
using ALTER.
ALTER well-name (well-number) value
where:
well-name (well-number) - well name (or number), whose first control value will be altered,
value - new control value.
The keyword has an Eclipse compatible analogue WELTARG (see 12.18.51).
Example
DATE 1975 6 28
PRODUCER 7
OPERATE MAX STL 42 CONT
...
DATE 1975 9 30
ALTER 7 47.5
June 28, 1975 this example specifies for producer number 7 two controls: liquid rate
(maximum 42) and bottom hole pressure (minimum 250). September 30, 1975 the value of
liquid rate control was altered: new value is 47.5 (bottom hole pressure value stays the same).
13.9.11. ALTER 1893

13.9.12 GEOMETRY


Section
The keyword specifies several geometric characteristics of the well. The data is used to
obtain the well flow index.
GEOMETRY I (or J, or K) rad geofac wfrac skin
where:
I (or J, or K) one should enter the coordinate axis which is parallel to the wellbore
(I X axis, J Y axis, K Z axis);
rad well radius (SI: m, FIELD: f t );
geofac geometric well factor;
wfrac a real number between 0 and 1, which specifies the part of circle which
corresponds to this well. Usually a hole circle corresponds to the well (the well is
inside the model) 1. If the well is situated at the corner of the grid block on the
grid boundary 0.25. If the well is situated at the edge of the grid block on the grid
boundary 0.5;
skin skin.
The keyword has an Eclipse compatible analogue COMPDAT (see 12.18.6) (several
parameters of COMPDAT correspond to GEOMETRY).
Example
WELL 8
PRODUCER 8
GEOMETRY K 0.0762 0.37 1. 0.
This example specifies for producer number 8 bottom hole pressure control (minimum
250). Using GEOMETRY are specified the following geometric characteristics of the well:
the wellbore is parallel to the Z axis;
13.9.12. GEOMETRY 1894

well radius is equal to 0.0762 m;
geometric well factor 0.37;
the hole circle is corresponding to the well;
skin 0.
13.9.12. GEOMETRY 1895

13.9.13 PERF


Section
The keywords sets grid blocks in which wellbore is situated. At first the well should be
initialized using keywords WELL (see 13.9.6), PRODUCER (see 13.9.7), GEOMETRY (see
13.9.12).
PERF GEO wn location well-index (status) (connection)
where:
1. GEO the keyword sets that the well index is calculated from the geometric information
(last GEOMETRY (see 13.9.12)), dimensions and permeability of the grid blocks in
which wellbore is situated.
2. wn well number.
3. location three numbers i, j, k X, Y and Z coordinates of grid block in which the
wellbore is situated.
4. well-index a number ff multiplier. Well index is multiplied by this multiplier. (Well
index is calculated from the geometric information (last GEOMETRY (see 13.9.12)),
dimensions and permeability of the grid blocks in which wellbore is situated.)
5. status block status: OPEN or CLOSED. OPEN perforated interval is open (this is
default status if status isnt specified). CLOSED this block is specified to define the
well trajectory. Perforated interval can be opened using the keyword PERF next time.
6. connection this parameter sets the number of previous block (specified for this well
using PERF keyword), i.e. the number of block in the direction of the flow at the time
of production.
The data should be entered in the following format: FLOW-TO ily.
Where ily - previous block number of the word SURFACE, if the first (top) well block
is specified.
One can add here REFLAYER. This word marks the block where bottom hole pressure
(BHP) is calculated. REFLAYER can be used only once for current PERF. If REFLAYER
is not specified, THP is calculated for the first entered block.
The keyword has an Eclipse compatible analogue COMPDAT (see 12.18.6) (several
parameters of COMPDAT correspond to PERF).
13.9.13. PERF 1896

Example
PERF GEO 12
48 7 3 5. OPEN FLOW-TO 'SURFACE' REFLAYER
48 7 4 5. OPEN FLOW-TO 1
48 7 6 5. CLOSED FLOW-TO 3
In this example the word GEO sets that the well index is calculated from the geometric
information (last GEOMETRY (see 13.9.12)), dimensions and permeability of the grid blocks
in which wellbore is situated.
Next we specify five grid blocks in which the wellbore of well 12 is situated (1-st block (48,
7, 3), 2-nd block: (48, 7, 4), 3-rd block: (48, 7, 5), 4-th block: (48, 7, 6), 5-th block: (48, 7,
7)).
The multiplier ff is equal to 5 for all these blocks (well index is multiplied by this multiplier).
Perforated intervals are opened in all blocks except 4-th block. The flow direction from
block to block is: 5-4-3-2-1-SURFACE. BHP is calculated for the 1-st block (the word
REFLAYER is present for the 1-st block).
13.9.13. PERF 1897

13.9.14 LAYERXYZ


Section
The keyword defines perforations which are situated on the deviated wellbore. Previously
these perforations should be initialized using the keyword PERF (see 13.9.13).
LAYERXYZ wn location x1 y1 z1 x2 y2 z2 plength
where:
1. wn well name (number).
2. location three numbers i, j, k X, Y and Z coordinates of grid block in which the

wellbore is situated. The part of wellbore in this block is considered as deviated.
3. x1 y1 z1 Cartesian coordinates of the entry point for the deviated wellbore in this
block. Points (x1, y1, z1) and (x2, y2, z2) define the wellbore direction.
4. x2 y2 z2 Cartesian coordinates of the exit point for the deviated wellbore in this
block. Points (x1, y1, z1) and (x2, y2, z2) define the wellbore direction.
5. plength length of the perforated interval within the grid block. This length can be
greater than the distance between (x1, y1, z1) and (x2, y2, z2).
The deviated well index in imex and stars:
2 w f rac K welllength f f
Well index = ,
ln re f f /rwell + skin
where
w f rac (0 6 w f rac 6 1) well angular fraction;
K average permeability (the description of calculation is below);
welllength length of the perforated interval within the grid block;
f f well index multiplier;
re f f drainage radius (the description of calculation is below);
rwell well radius;
13.9.14. LAYERXYZ 1898

skin skin.
Let u = (ux , uy , uz ) a unit vector in the wellbore direction; ex , ey , ez unit vectors
(parallel to the vectors which joins centers of mass of the opposite edges in this block).
When u is parallel to one of the vectors ex , ey or ez then
s
( j) V
re f f = re f f (e j ) = geo f ac (13.2)
h( j) w f rac
where
j x, y, z; geo f ac geometric well factor (see GEOMETRY (see 13.9.12));
V volume of the perforated block; h( j) the grid block thickness in the direction
j.
Let
x = (u, ex )2 1 (u, ey )2 1 (u, ez )2

y = (u, ey )2 1 (u, ex )2 1 (u, ez )2

z = (u, ez )2 1 (u, ex )2 1 (u, ey )2
In the general case the drainage radius is equal to:

(x) (y) (z)
re f f (u) = re f f x + re f f y + re f f z / (x + y + z ) (13.3)
tNavigator uses right formula:

1/2
(x) 2 (y) 2 (z) 2

re f f (u) = re f f x + re f f y + re f f z / (x + y + z )1/2 (13.4)
( j)
Average permeability K is calculated the same way: one should replace re f f = re f f (e j )
by s
K(e j ) = ki .
16i63
i6= j
Example
LAYERXYZ 14
8 10 4 394247.20378 373635.68824 1371.69128 394247.30153
373637.60444 1377.65544 0.00129
8 10 5 394247.30153 373637.60444 1377.65544 394247.77237
373646.83405 1406.38252 30.17704
8 10 6 394247.77237 373646.83405 1406.38252 394248.08057
373652.27302 1423.68686 18.14215
8 10 7 394248.08057 373652.27302 1423.68686 394248.61406
373660.44384 1450.54380 28.07750
This example sets four grid blocks in which wellbore of well 14 is deviated.
13.9.14. LAYERXYZ 1899

13.9.15 TINJW


Section
This keyword defines the temperature of the injected fluid (SI: C, FIELD: F).
This keyword is analogous to the 3-rd parameter of Eclipse-compatible keyword WIN-

JTEMP (see 12.18.155).
Default: For this parameter default value is supported according to the logic of STARS
syntax.
13.9.15. TINJW 1900

13.9.16 QUAL


Section
This keyword defines the steam quality of the injected fluid (a value should be in the
range from 0 to 1).
This keyword is analogous to the 2-nd parameter of Eclipse-compatible keyword WIN-

JTEMP (see 12.18.155).
Default: For this parameter default value is supported according to the logic of STARS
syntax.
13.9.16. QUAL 1901

13.9.17 WTMULT


Section
The keyword is used to multiply control or limit value for the well (specified via OPER-
ATE (see 12.3.25)) by a multiplying factor.
STO oil rate;

STW water rate;
BHW water rate in reservoir conditions;
STG gas rate;
STL liquid rate;
BHF reservoir fluid volume rate;
WHP tubing head pressure;
STEAM steam rate expressed in cold water equivalent CWE;
2. name (or number) of well(s);
3. multiplying factor for this control or limit (multipliers should be entered on one or
more new lines following the line with WTMULT).
This keyword has an Eclipse-compatible analogue WTMULT (see 12.18.49).
Example
WTMULT STW PR5
0.9
In this example for the well PR5 multiplying factor for water rate is 0.9.
13.9.17. WTMULT 1902

13.9.18 ON-TIME


Section
The keyword sets well efficiency factor (the fraction of time during which a well works).
This number should be between 0.001 and 1. If this number is less than 0.001 it is set equal
to 0.001 during the simulation.
ON-TIME well-name
OTF-input
where:
well-name well name (should be entered immediately after ON-TIME, on the same
line);
OTF-input well efficiency factor (the fraction of time during which a well works);
(should be entered on the next line after the line with ON-TIME).
The keyword has an Eclipse compatible analogue WEFAC (see 12.18.69).
Example
ON-TIME A2
0.6429
ON-TIME B3
1.
This example specifies well efficiency factor for the well A2 equal to 0.6429, for the well
B3 1.
13.9.18. ON-TIME 1903

13.9.19 STOP


Section
The keyword terminates the simulation. The data after STOP is ignored.
The keyword has an Eclipse compatible analogue END (see 12.1.104).
Example
DATE 1973 4 17
STOP
The simulation terminates on April 17, 1973.
13.9.19. STOP 1904

13.9.20 HTWELL / HTWRATE / HTWRATEPL / HTWTEMP / HTWI


Section
The keyword specifies properties of heater wells.

1. well name. It should be single quoted;
2. [additional parameter] HTWRATE or HTWRATEPL:
HTWRATE this parameter sets that maximum heating rate will be specified. The
value of rate is set by the parameter 3. A positive value denotes heating and a
negative value denotes cooling;
HTWRATEPL this parameter sets that maximum heating rate per well length
unit will be specified. The value of rate is set by the parameter 3.
3. maximum heating rate. The following units are used: for HTWRATE SI: J/day,
SI: Btu/day; for HTWRATEPL SI: J/day m, SI: Btu/day f t . This parameter is
required if HTWRATE or HTWRATEPL is specified;
4. [additional parameter] HTWTEMP - this parameter sets that well temperature will be
specified. The value of temperature is set by the parameter 5;
5. well temperature (SI: C , SI: F ). This parameter is required if HTWTEMP is specified;
6. [additional parameter] HTWI this parameter specifies that index conductivity value
is equal to index value of the well. If this parameter is absent then index value will be
calculated again.
One of parameters 2 and 4 has to be specified.
Instead of parameters 2-6 parameter OFF can be used, which turns off well heating.
Example
HTWELL 'C1P_Cir'
HTWTEMP 205
HTWELL 'C2P_Cir'
HTWTEMP 205
HTWELL 'C3P_Cir'
HTWTEMP 205
In the example temperature value of 205 F is specified for three wells: C1P_Cir,
C2P_Cir, C3P_Cir.
13.9.20. HTWELL / HTWRATE / HTWRATEPL / HTWTEMP / HTWI 1905

13.9.21 WELSEP


Section
The keyword assigns separator to wells. Assigning can be set in two formats:
format 1. The following parameters should be specified:
1. well number(s), to which separator will be assigned;

2. subkeyword STAGE indicating that separator stages will be entered next;
3. stage pressure;
4. stage temperature;
Pressure and temperature of each stage are set in separate line.
format 2. The following parameters should be specified:
1. well number(s), to which separator will be assigned;

2. subkeyword STAGE indicating that separator stages will be entered next;
3. subkeyword EOS indicating that EOS region number and 2 characteristics of the
stage will be entered next;
4. EOS region number (see keyword EOSSET (see 13.5.68));
5. stage pressure;
6. stage temperature;
7. subkeyword LIQUID-TO or VAPOR-TO indicating that destination of water of
vapor will be set next;
8. stage number of fluid:
stage number stage of current separator to which stage output is fed;
fluid it specifies the surface stream which is the destination of the particular
output of the current stage. It can has 3 values: GAS, INL, OIL.
This keyword has Eclipse compatible analogs WSEPCOND (see 12.18.145) and SEP-
COND (see 12.18.144).
Example
*WELSEP 1:4,5 *STAGES 400.0 100.0 101.3 60.0
13.9.21. WELSEP 1906

13.9.22 TRIGGER


Section
The keyword specifies a set of keywords to perform at defined conditions satisfied. The
1. trigger name;
2. trigger type. Each type has its own parameters. Supported types:
ON_WELL the trigger condition is to be applied to a well or list of wells. The

(a) well name or well names list. List can be specified by exact well names or
by 2 types of masks: with symbol * (instead of any number of symbols in
the end of well name) or ? (instead of one symbol in well name);
(b) well quantity characteristic. List of allowed ones is in table 1;
(c) comparison operator (< or >);
(d) characteristic value (i.e trigger value). 3 last parameters set trigger condition
to be tested.
ON_FIELD the trigger condition is to be applied to entire field. The following
(a) string FIELD which means field name;
(b) field quantity characteristic. List of allowed ones is in table 2;
(d) characteristic value (i.e trigger value). 3 last parameters set trigger condition
to be tested.
ON_ELAPSED the trigger condition which connected with data of its defining.
(a) string TIME, which means that type of using trigger is time;
(b) time condition. 2 possible variants:
TIMSIM the time value entered is time elapsed from the start of the run
(absolute time);
TRELTD the time value entered is relative to the time the trigger is
defined (relative time).
13.9.22. TRIGGER 1907

(d) time value (i.e trigger value) (SI: day, FIELD:day). 3 last parameters set
trigger condition to be tested.
3. [additional parameter] APPLY_TIMES subkeyword specifies the maximum number

of times that the actions specified with the trigger (parameter 8) can be taken. It should
be followed by one integer;
4. [additional parameter] INCREMENT subkeyword specifies the increment to the

trigger value. It should be followed by one real number;
5. [additional parameter] TEST_TIMES subkeyword specifies the maximum number

of times that the trigger can be tested to ascertain if the condition is satisfied. It should
be followed by one integer;
6. [additional parameter] TEST_AFTER_TIMER subkeyword used to specify the time

delay which must elapse before the first trigger condition test. It should be followed
by one real number (SI: day, FIELD:day);
7. [additional parameter] TEST_AFTER_TIMEA subkeyword used to specify the time

delay in days which must elapse before the trigger condition will begin to be tested. It
should be followed by one real number (SI: day, FIELD:day);
8. list of keywords of the section Well and recurrent data to perform during simulation
when trigger condition is satisfied;
9. END_TRIGGER This keyword marks the end of trigger definition. It should be

specified in new line.
Table 1. Well quantity characteristic.
STO-RP oil production rate at surface conditions (SI: m3 /day, FIELD: stb/day)
STO-CP oil cumulative production at surface conditions (SI: m3 , FIELD: stb)
STO-RI oil injection rate at surface conditions (SI: m3 /day, FIELD: stb/day)
STO-CI oil cumulative injection at surface conditions (SI: m3 , FIELD: stb)
STW-RP water production rate at surface conditions (SI: m3 /day, FIELD: stb/day)
STW-CP water cumulative production at surface conditions (SI: m3 , FIELD: stb)
STW-RI water injection rate at surface conditions (SI: m3 /day, FIELD: stb/day)
STW-CI water cumulative injection at surface conditions (SI: m3 , FIELD: stb)
STG-RP gas production rate at surface conditions (SI: m3 /day, FIELD: sc f /day)
STG-CP gas cumulative production at surface conditions (SI: m3 , FIELD: sc f )
STG-RI gas injection rate at surface conditions (SI: m3 /day, FIELD: sc f /day)
STG-CI gas cumulative injection at surface conditions (SI: m3 , FIELD: sc f )
STL-RP liquid production rate at surface conditions (SI: m3 /day, FIELD: stb/day)
STL-CP liquid cumulative production at surface conditions (SI: m3 , FIELD: stb)
BHF-RP the oil plus water plus gas phase production rate (SI: m3 /day, FIELD:
bbl/day)
13.9.22. TRIGGER 1908

BHF-CP the oil plus water plus gas phase production cumulative (SI: m3 , FIELD:
bbl)
BHF-RI the oil plus water plus gas injection rate (SI: m3 /day, FIELD: bbl/day)
BHF-CI the oil plus water plus gas phase injection cumulative (SI: m3 , FIELD:
bbl)
STI-RP intermediate liquid stream production rate at surface conditions (SI:
m3 /day, FIELD: stb/day)
STI-CP intermediate liquid stream cumulative production at surface conditions (SI:
m3 , FIELD: stb)
WTG-RP wet gas stream production rate at surface conditions (SI: m3 /day, FIELD:
sc f /day)
WTG-CP wet gas stream cumulative production at surface conditions (SI: m3 ,
FIELD: sc f )
BHP bottom hole pressure of the well (SI: kPa, FIELD: psi)
WHP tubing head pressure of the well (SI: kPa, FIELD: psi)
GOR gas oil ratio at surface conditions
WCUT water cut at surface conditions
WGR water gas ratio at surface conditions
GLR gas liquid ratio at surface conditions
MXX mole percent of component xx in the well stream
TEMP maximum temperature of all completions (SI: C, FIELD: F)
O2CONC maximum oxygen mole fraction of all completions of a well
Table 2. Field quantity characteristic.
STO-RP oil production rate at surface conditions (SI: m3 /day, FIELD: stb/day)
STO-CP oil cumulative production at surface conditions (SI: m3 , FIELD: stb)
STW-RP water production rate at surface conditions (SI: m3 /day, FIELD: stb/day)
STW-CP water cumulative production at surface conditions (SI: m3 , FIELD: stb)
STW-RI water injection rate at surface conditions (SI: m3 /day, FIELD: stb/day)
STW-CI water cumulative injection at surface conditions (SI: m3 , FIELD: stb)
STG-RP gas production rate at surface conditions (SI: m3 /day, FIELD: sc f /day)
STG-CP gas cumulative production at surface conditions (SI: m3 , FIELD: sc f )
STG-RI gas injection rate at surface conditions (SI: m3 /day, FIELD: sc f /day)
STG-CI gas cumulative injection at surface conditions (SI: m3 , FIELD: sc f )
STL-RP liquid production rate at surface conditions (SI: m3 /day, FIELD: stb/day)
STL-CP liquid cumulative production at surface conditions (SI: m3 , FIELD: stb)
BHF-RP the oil plus water plus gas phase production rate (SI: m3 /day, FIELD:
bbl/day)
BHF-CP the oil plus water plus gas phase production cumulative (SI: m3 , FIELD:
bbl)
BHF-RI the oil plus water plus gas injection rate (SI: m3 /day, FIELD: bbl/day)
13.9.22. TRIGGER 1909

BHF-CI the oil plus water plus gas phase injection cumulative (SI: m3 , FIELD:
bbl)
STI-RP intermediate liquid stream production rate at surface conditions (SI:
m3 /day, FIELD: stb/day)
STI-CP intermediate liquid stream cumulative production at surface conditions (SI:
m3 , FIELD: stb)
WTG-RP wet gas stream production rate at surface conditions (SI: m3 /day, FIELD:
sc f /day)
WTG-CP wet gas stream cumulative production at surface conditions (SI: m3 ,
FIELD: sc f )
GOR gas oil ratio at surface conditions
WCUT water cut at surface conditions
WGR water gas ratio at surface conditions
GLR gas liquid ratio at surface conditions
MPWS MXX mole percent of component xx in the well stream
GWGR Ratio of gas production rate at surface conditions to the wet gas production
rate at surface conditions
WWGR ratio of water production rate at surface conditions to the wet gas produc-
tion rate at surface conditions
RECYSTG minimum field gas recycling rate (SI: m3 /day, FIELD: sc f /day)
RECYSTW minimum field water recycling rate (SI: m3 /day, FIELD: stb/day)
VOIDRPG field voidage replacement ratio by gas injection
VOIDRPW field voidage replacement ratio by water injection
VOIDRPT field voidage replacement ratio by all injection streams
STOR Steam oil ratio (ratio of instantaneous steam injection / instantaneous oil
production) for the field
STORC cumulative steam oil ratio (ratio of cumulative steam injected / cumulative
oil production) for the field
OSTR oil steam ratio (ratio of instantaneous oil production / instantaneous stream
injection) for the field
OSTRC cumulative oil steam ratio (ratio of cumulative oil produced / cumulative
steam injected) for the group
STOR2 steam oil ratio (ratio of instantaneous steam injection / instantaneous oil
production) for the field. Difference from STOR is the following: trigger
condition will be satisfied only if field oil rate and water injection rate is
greater than 1.0e-20.
STORC2 cumulative steam oil ratio (ratio of cumulative steam injected / cumulative
oil production) for the field. Difference from STORC is the following: trig-
ger condition will be satisfied only if both field oil production cumulative
and group water injection cumulative values are above 1.0e-20.
13.9.22. TRIGGER 1910

OSTR2 oil steam ratio (ratio of instantaneous oil production / instantaneous stream
injection) for the field. Difference from OSTR is the following: trigger
condition will be satisfied only if both group oil production rate and group
water injection rate values are above 1.0e-20.
OSTRC2 cumulative oil steam ratio at any given time (instantaneous). Difference
from OSTRC is the following: trigger condition will be satisfied only if
both group oil production cumulative and group water injection cumulative
values are above 1.0e-20.
Symbol @ in quotes can be used as notion for list of well which satisfy trigger condition.
This keyword has an Eclipse compatible analogue ACTION (see 12.18.131).
Example
TRIGGER 'inj1' ON_WELL 'well* ' WHP < 5000.0
APPLY_TIMES 9000
*SHUTIN '@'
END_TRIGGER
In the example trigger inj1 is set. It has ON_WELL type, list of testing wells is set by
mask well*. Condition to test is tubing head pressure is less than 5000. Maximal number
of trigger performing is 9000 times. If trigger condition is satisfied then each well from list
well*, which satisfy it, will be shut.
13.9.22. TRIGGER 1911

14. Keywords compatible with tNavigator and MORE tNavigator-4.2
14 Keywords compatible with tNavigator and MORE

model formats:
tNavigator;
MORE.
tNavigator or which usage is different from MORE.
MORE keywords have 4 significant characters. For convenience (analogous to MORE)

keywords are written in upper case. Sometimes for clarity all characters of the keyword may
be written. For example: FLUI and FLUId. FLUI - the keyword with 4 significant characters.
For convenience keyword are grouped in several sections similar to MORE Roxar sections.
INPUt Data Section (14.1)
FLUId Data Section (14.2)
RELAtive Permeability Data Section (14.3)
GRID Data Section (14.4)
INIT Data Section (14.5)
RECUrrent Data Section (14.6)
14. Keywords compatible with tNavigator and MORE 1912

14.1. INPUt Data Section tNavigator-4.2
14.1 INPUt Data Section
14.1. INPUt Data Section 1913

14.1.1 INPUt
Data x tNavigator E300 x MORE GEM

x INPU FLUI RELA

Section
GRID INIT RECU
This keyword begins INPUt Data Section.
14.1.1. INPUt 1914

14.1.2 TITLe

x INPU FLUI RELA

Section
GRID INIT RECU
This keyword specifies a header of the output file. Two title lines may be specified.
Example
TITLE First Test run 1971
TITLE Special run
14.1.2. TITLe 1915

14.1.3 PRINt

x INPU FLUI RELA

Section
GRID INIT RECU
This keyword defines printing options for this section.

The following parameters may be specified:
NONE no printing of INPUt data,
ALL printing of INPUt data.
Example
PRIN ALL
14.1.3. PRINt 1916

14.1.4 UNIT

x INPU FLUI RELA

Section
GRID INIT RECU
This keyword specifies the unit system of the simulation.

The following systems are supported:
METR Metric units,
POFU practical oil field units,
FIELD analogue of POFU,
IMP analogue of POFU.
The table of units system is in the section 10.
Example
UNIT METR
14.1.4. UNIT 1917

14.1.5 IDATe

x INPU FLUI RELA

Section
GRID INIT RECU
The keyword specifies the initial date of the simulation.
1. day of the month (1 or 2 digits);
2. month (first 3 letters of month) JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG,
SEP, OCT, NOV, DEC. JLY (July) is also possible;
3. year (2 or 4 digits); if only 2 digits are specified, a 20th century data is assumed.
The keyword has an Eclipse compatible analogue START (see 12.1.13).
Example
IDATE 18 MAY 2003
14.1.5. IDATe 1918

14.1.6 SDATe

x INPU FLUI RELA

Section
GRID INIT RECU
The keyword specifies starting date or time. If the starting time is greater than zero or the
starting date is later then the initial date, the run will start at the date SDATe. If the keyword
isnt specified, the run will start at the initial date IDATe (see 14.1.5).
The date may be entered in the following formates:
1. value DAYS, where value - the number of days after the initial date IDATe (see 14.1.5);
2. value MONT, where value - the number of month after the initial date IDATe
(see 14.1.5);
3. value YEAR, where value - the number of years after the initial date IDATe (see 14.1.5);
4. data format is similar to IDATe (see 14.1.5).
Example
SDATE 0 YEARS
14.1.6. SDATe 1919

14.1.7 CNAMe

x INPU FLUI RELA

Section
GRID INIT RECU
The keyword specifies component names in the simulation.
The names of all components should be specified. For black-oil the following names are
possible:
OIL;
WATer;
GAS;
SOLVent;
STEAM;
The keyword has an Eclipse compatible analogue CNAMES (see 12.13.4).
Example
CNAMe OIL GAS WAT
14.1.7. CNAMe 1920

14.1.8 IMPLicit

x INPU FLUI RELA

Section
GRID INIT RECU
The keyword controls the degree of implicitness.
One of the following parameters should be specified after this keyword:
FULL - fully implicit method;
ADAP - adaptive implicit method;
IMPE - IMPES method.
The keyword has an Eclipse compatible analogue IMPLICIT (see 12.1.75).
Example
IMPL FULL
14.1.8. IMPLicit 1921

14.1.9 INCLude

x INPU x FLUI x RELA

Section
x GRID x INIT x RECU
This keyword is used to include input file with keyword into another file with keyword.
Including file can contain keywords INCLUDE too.
The file name should be enclosed in quotes. The only file can be specified after keyword
INCLUDE.
Example
INCLude
'Well/hist_events.mrecu'
In this example keyword is used to include file named hist_events.mrecu from Well
folder into a file with keyword.
14.1.9. INCLude 1922

14.1.10 SCMP

x INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies description of standard composition for a fluid stream. The fol-
1. in one line with the keyword:
composition name.
2. on the next line:
the list of mole fractions of each component in composition. The number of

components is specified by the keyword CNAMe (see 14.1.7). Either sum of
moles is 1, or quantity of moles of each component should be equal to 0. The
Default:
quantity of moles of each component: 0.
This keyword has an Eclipse compatible analogue WELLSTRE (see 12.18.159).
Example
CNAME: N2 CO2 H2S C1 C2 C3 IC4 C4 IC5 C5 C6 C71 C72 C73 C74
C75 WATR /
/
SCMP: GAS - injected CO2
0.0 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 /
/
In the example the keyword SCMP (see 14.1.10) sets composition named GAS - injected
CO2 and list of moles of each component.
14.1.10. SCMP 1923

14.1.11 DPORo

x INPU FLUI RELA

Section
x GRID INIT RECU
The keyword sets an option Dual Porosity enable during calculation. The following pa-
rameters should be specified:
[additional parameter] GRAV - use gravity drainage;
[additional parameter] NET - treat fracture permeabilities as net;
[additional parameter] SING - single grid will be used;
[additional parameter] FRAC - the number of matrix volume fractions in the single
grid. This option should be used with the option SING.
Default:
FRAC: 1.
The number of model layers must be even. If option GRAV is used, then values of DZMA
(see 14.4.31) should be specified.
This keyword has an Eclipse compatible analogue DUALPORO (see 12.1.76).
Example
DPOR
14.1.11. DPORo 1924

14.1.12 EPS

x INPU FLUI RELA

Section
GRID INIT RECU
The keyword sets scaling method of the relative permeability endpoints. The following
1. scaling method:
3POINT (analog: 3) - scale a capillary pressure curve at the connate, critical and
upper saturations;
if other is specified, then curve will be scaled by 2 points: connate and upper
saturations.
Default:
scaling method: 3POINT.
This keyword has an Eclipse compatible analogue SCALECRS (see 12.6.26).
Example
EPS 3
14.1.12. EPS 1925

14.1.13 EPSP

x INPU FLUI RELA

Section
GRID INIT RECU
The keyword sets scaling method of the capillary pressure endpoints. The following
1. scaling method:
0POINT (analogs: 0, OFF or NO) - turn off scaling;

2POINT (analog: 2) - scale at the connate and upper saturations;
3POINT (analog: 3) - scale at the connate, critical and upper saturations;
4POINT (analog: 4) - scale at the connate, critical, upper and other phase residual
saturations.
Default: Option which is specified in the keyword EPS (see 14.1.12) is used by default.
If EPS (see 14.1.12) is nit used, then option 3POINT will be set.
Example
EPS
ESPS 4
In the example scaling method of the capillary pressure endpoints at 4 points is chosen.
14.1.13. EPSP 1926

14.1.14 DWPW

x INPU FLUI RELA

Section
GRID INIT RECU
The keyword is used to set the default well pressure weighting method. The following
1. if drawdown target is used, then these options can be specified:
DDRC - use cell pressure corrected to the external radius (PREX (see 14.6.21));
NODD - use cell pressure.
Default:
drawdown target option: DDRC.
Example
DWPW NODD
14.1.14. DWPW 1927

14.1.15 OPEN

x INPU x FLUI x RELA

Section
x GRID x INIT x RECU
The keyword is used to:
1. put all output files into directory, which is differ from default directory;
2. make restart from a model with another name.
1. in one line with the keyword (correspondingly to using meaning of this keyword):
ALL - first meaning;

IRST - second meaning.
2. in the following line:
file name. It should be quoted, if it contains whitespaces or slashes /.
Example
OPEN ALL
rst100
In the example the keyword OPEN is used in first meaning. Output data will be written
to the file rst100.
14.1.15. OPEN 1928

14.1.16 ETUNe

x INPU FLUI RELA

Section
GRID INIT RECU
The keyword is used to calculate connection factor via the following formula for hybrid
and MORE-models: q
CF = (CFx )2 + (CFy )2 + (CFz )2 ,
where CFx ,CFy ,CFz connection factors in X -, Y -, Z -directions correspondingly.
More detailed information is in the section Connection transmissibility calculation (CF
and Kh).
Example
ETUN
14.1.16. ETUNe 1929

14.1.17 GPP

x INPU FLUI RELA

Section
GRID INIT RECU
The keywords activates option of Generalized Pseudo-pressure (GPP) for all wells inflow
calculations. The following parameters should be specified:
1. [additional parameter] ALL option will be applied to all wells. If this parameter is
absent, then keyword WGPP (see 14.6.65) should be specified.
This keyword has an Eclipse compatible analogue PSEUPRES (see 12.18.232)
Example
GPP ALL
14.1.17. GPP 1930

14.1.18 MPGP

x INPU FLUI RELA

Section
GRID INIT RECU
The keyword activates the using of multi-phase gas pseudo-pressure for well inflow
calculation. The following parameters should be specified:
absent, then keyword WMPG (see 14.6.66) should be specified.
This keyword has an Eclipse compatible analogue PSEUPRES (see 12.18.232)
Example
MPGP ALL
14.1.18. MPGP 1931

14.1.19 RG

x INPU FLUI RELA

Section
GRID INIT RECU
The keyword indicates that Russell-Goodrich inflow equation to model the flow of gas
between the completed grid blocks and the well will be used. The following parameters
absent, then keyword WRG (see 14.6.67) should be specified.
This keyword has an Eclipse compatible analogue WELSPECS (see 12.18.3) (8-th pa-
rameter).
Example
RG ALL
14.1.19. RG 1932
14.2. FLUId Data Section tNavigator-4.2
14.2 FLUId Data Section
14.2. FLUId Data Section 1933

14.2.1 FLUId

INPU x FLUI RELA

Section
GRID INIT RECU
This keyword begins FLUId Data Section.
The type of model should be specified:
BLACk oil - black oil model;
EOS - compositional model.
Example
FLUID BLACK
14.2.1. FLUId 1934

14.2.2 WATR

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword sets water properties.
1. water density at standard conditions (METRIC: kg/m3 , FIELD: lb/ f t 3 );
2. water density at reservoir temperature and reference pressure (METRIC: kg/m3 ,

FIELD: lb/ f t 3 );
3. water compressibility (METRIC: 1/bar , FIELD: 1/psi);
4. reference pressure (METRIC: barsa, FIELD: psia);
5. water viscosity at reservoir conditions (METRIC: cP, FIELD: cP).
The keyword has Eclipse compatible analogues DENSITY (see 12.5.23), PVTW (see
12.5.5).
Example
WATR 999.551 1008.59 4.77175e-05 276.804 0.31
14.2.2. WATR 1935

14.2.3 BASIc

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword is used to specify basic fluid properties.
1. oil density at stock tank conditions (METRIC: kg/m3 , FIELD: lb/ f t 3 );
2. oil molecular weight;
3. gas molecular weight (if a value greater than 2 is supplied) or gas gravity (If a value
less than 2 is supplied).
The keyword has an Eclipse compatible analogue DENSITY (see 12.5.23).
Example
BASI 786.684 190.0 0.792
In this example oil density at stock tank conditions is 786.684, oil molecular weight
190.0, gas gravity 0.792.
14.2.3. BASIc 1936

14.2.4 TEMPerature

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword is used to specify temperature for which PVT tables are entered (black oil
model) (METRIC: C, FIELD: F).
Example
TEMP 160
In this example temperature is 160 C.
14.2.4. TEMPerature 1937

14.2.5 OPVT

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword specifies oil PVT tables (black oil model). Each tables row should be ter-
minated with a slash /.
1. oil phase pressure (METRIC: barsa, FIELD: psia);
2. oil phase formation volume factor (METRIC: m3 /m3 , FIELD: rb/stb);
3. oil phase viscosity (METRIC: cP, FIELD: cP);
4. solution gas oil ratio (METRIC: 103 m3 /m3 , FIELD: msc f /stb);
5. [additional parameter] oil phase compressibility (METRIC: 1/bar , FIELD: 1/psi);
6. [additional parameter] normalized viscosity slope (METRIC: 1/bar , FIELD: 1/psi);
7. [additional parameter] surface tension (METRIC: dynes/cm, FIELD: dynes/cm).
The keyword has Eclipse compatible analogues PVCO (see 12.5.6), PVCDO (see 12.5.3),
DISGAS (see 12.1.56).
Example
OPVT
1.01 1.042 1.040 0.000178 /
17.25 1.130 0.975 0.016119 /
33.48 1.197 0.910 0.032059 /
68.96 1.265 0.830 0.066078 /
137.90 1.425 0.695 0.113277 /
171.38 1.480 0.641 0.138034 /
205.85 1.545 0.594 0.165640 /
273.80 1.675 0.510 0.226197 1.98702e-04 1.30534e-03 /
344.75 1.817 0.449 0.288179 /
620.54 2.337 0.203 0.531474 /
/
In this example oil PVT table is specified for 10 pressure values.
14.2.5. OPVT 1938

14.2.6 GPVT

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword specifies gas PVT tables (black oil model). Each tables row should be
1. gas phase pressure (METRIC: bar , FIELD: psi);
2. gas phase formation volume factor (METRIC: m3 /103 m3 , FIELD: rb/Msc f );
3. gas phase viscosity (METRIC: cP, FIELD: cP);
4. vapour oil-gas ratio (METRIC: m3 /103 m3 , FIELD: rb/Msc f ).
The keyword has Eclipse compatible analogues PVDG (see 12.5.7), PVTG (see 12.5.8),
VAPOIL (see 12.1.55).
Example
GPVT
1.014 935.9505 0.0080 /
18.250 67.8971 0.0096 /
35.487 35.2259 0.0112 /
69.961 17.9498 0.0140 /
138.909 9.0619 0.0189 /
173.382 7.2653 0.0208 /
207.856 6.0637 0.0228 /
276.804 4.5534 0.0268 /
345.751 3.6439 0.0309 /
621.541 2.1672 0.0470 /
/
In this example gas PVT table is specified for 10 pressure values.
14.2.6. GPVT 1939

14.2.7 EQUA

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword is specifies type of equation-of-state for compositional model.

1. type of equation:
RK - equation of Redlich-Kwong;
SRK - equation of Soave-Redlich-Kwong;
PR - equation of Peng-Robinson (1979 version).
Default:
equation type: PR.
This keyword has an Eclipse compatible analogue EOS (see 12.13.5).
Example
EQUA RK
14.2.7. EQUA 1940

14.2.8 KVSP

INPU x FLUI RELA

Section
GRID INIT RECU
This keyword is used to set tables of transmissibility dependence on pressure for each
rock region. Each line of the table should be terminated by a symbol /. The data should be
One line of the table should contain the following data:
1. pressure (METRIC: bar , FIELD: psi);
2. permeability multiplier;
3. pore volume multiplier.
This keyword has an Eclipse compatible analogue ROCKTAB (see 12.5.18).
Example
KVSP
21.74 0.9818 0.8915 /
65.22 0.9850 0.9012 /
108.70 0.9883 0.9341 /
195.65 0.9948 0.9768 /
282.61 1.0013 1.0194 /
/
This example sets one table of transmissibility dependence on pressure for one rock
region.
14.2.8. KVSP 1941

14.2.9 KVPX / KVPY / KVPZ

INPU x FLUI RELA

Section
GRID INIT RECU
These keywords sets tables of permeability multipliers in X , Y or Z -directions depen-

dence on pressure.
One line of the table should contain the following parameters:
1. pressure value (METRIC: bar , FIELD: psi);
2. permeability multiplier value.
This keyword has an Eclipse compatible analogue ROCKTAB (see 12.5.18).
Example
KVPX
21.74 0.8915
65.22 0.9123
108.70 0.9341
195.65 0.9768
282.61 1.0194
In the example permeability values in X direction dependence on pressure is specified.
14.2.9. KVPX / KVPY / KVPZ 1942

14.2.10 OPVD

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword sets table of black oil PVT properties for all PVT regions. Each line of the
table should contain the following parameters:
bubble point pressure (METRIC: bar , FIELD: psi);
oil formation volume factor (METRIC: m3 /103 m3 , FIELD: rb/stb);
oil viscosity (METRIC: cp, FIELD: cp).
Pressure values must increase with lines. Each table should be ended by a symbol /.
This keyword has an Eclipse compatible analogue PVDO (see 12.5.2).
Example
OPVD
83.20 1.15 2.45
239.00 1.12 2.93
/
102.34 1.15 2.56
267.67 1.11 2.89
/
In the example PVT-properties of black oil in 2 regions are specified.
14.2.10. OPVD 1943

14.2.11 OMGA

INPU x FLUI RELA

Section
GRID INIT RECU
The keywords sets parameter a for equation of state. It should be used after the keyword
TEMP in FLUId section. The data should be terminated with a slash /.
[additional parameter] parameter format (one of the following variants):

CONS - constant value of a is specified;
MULT - multiplier values are specified.
values for i-th component (one of the following variants):

multipler value (MULT);
constant value a (CONS).
Default:
parameter format: MULT.
Example
C75 WATR /
...
OMGA MULTIPLIERS:
1.0000000000 1.0000000000 1.0000000000 1.0000000000
1.0000000000 1.0000000000 1.0000000000 1.0000000000
1.0000000000 1.0000000000 1.0000000000 1.0000000000
1.0000000000 1.0000000000 1.0000000000 1.0000000000
In the example for each component multiplier values for a are specified. Components
are specified via the keyword CNAMe (see 14.1.7). Each multiplier is equal to 1.
14.2.11. OMGA 1944

14.2.12 OMGB

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword sets parameter b of equation of state. This parameter should be specified
for that temperature values for which non-default values are required. The data should be
[additional parameter] parameter format (one of the following variants):

CONS - constant value of b is specified;
MULT - multiplier values are specified.
values for i-th component (one of the following variants):

multipler value (MULT);
constant value a (CONS).
Default:
parameter format: MULT.
Example
C75 WATR /
...
OMGB MULTIPLIERS:
1.0000000000 1.0000000000 1.0000000000 1.0000000000
1.0000000000 1.0000000000 1.0000000000 1.0000000000
1.0000000000 1.0000000000 1.0000000000 1.0000000000
1.0000000000 1.0000000000 1.0000000000 1.0000000000
In the example for each component multiplier values for b are specified. Components
are specified via the keyword CNAMe (see 14.1.7). Each multiplier is equal to 1.
14.2.12. OMGB 1945

14.2.13 VOLU

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword is full analog of the keyword SSHIFT (see 12.13.41) which is used by
Eclipse.
14.2.13. VOLU 1946

14.2.14 SDEN

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword is used to specify oil and gas densities at surface conditions. By this key-
word it is possible to define different densities for each PVT-region.
1. oil density at surface conditions (METRIC: kg/m3 , FIELD: lb/ f t 3 );
2. gas density at surface conditions (METRIC: kg/m3 , FIELD: lb/ f t 3 );
Default:
oil density at surface conditions: 881 kg/m3 (METRIC), 55 lb/ f t 3 (FIELD);
gas density at surface conditions: 0.8446 kg/m3 (METRIC), 0.0527 lb/ f t 3 (FIELD).
Analogous to this keyword is 1st and 3rd parameters of the keyword DENSITY (see
12.5.23), which is used by Eclipse. Alternative for the keyword SDEN (see 14.2.14) is the
keyword BASI (see 14.2.3).
Example
UNIT METR
...
SDEN
600 1.0
In the example by the keyword SDEN (see 14.2.14) oil and gas densities at surface
conditions are specified. They are equal to 600 and 1 kg/m3 correspondingly.
14.2.14. SDEN 1947

14.2.15 VCOR

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword redefines coefficients in Lohrenz-Bray-Clark (3.3.1) equation of viscosity

correlation. The following parameters should be specified:
in one line with the keyword:
1. values format:
MULT - values specified below are used in 3.8 as multipliers for default
values of ai ;
CONS - values specified below are used in 3.8 instead of default values of
ai .
in the following line:
1. 5 values of ai , which will be used in 3.8.
Default:
coefficient values which are used in 3.8:
1. 0.10230;
2. 0.023364;
3. 0.058533;
4. -0.040758;
5. 0.0099324.
This keyword has an Eclipse compatible analogue LBCCOEF (see 12.13.36).
Example
VCOR MULT
3* 0.989 1.005
In the example the keyword VCOR specifies coefficients for Lohrenz-Bray-Clark equation
the following way: the first 3 coefficients are default, 4-th is multiplied by 0.989, 5-th is
multiplied by 1.005.
14.2.15. VCOR 1948

14.2.16 F(DE

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword sets system initial conditions dependence on depth. System must be at state
of equilibrium. The following parameters should be specified:
1. [additional parameter] EQUIL region number for which function is set.
in the following lines a table is specified. Each line of this table should contain:

2. temperature for fluid properties (only for black-oil models) (METRIC: C ,
FIELD: F );
3. initial saturation pressure (only for black-oil models) (METRIC: bar , FIELD:
psi).
4. initial composition. It can be set by name (see the keyword SCMP (see 14.1.10)),
or by entering a series of mole fractions. They must sum to 1.
Each data line should be ended by the symbol /..

Default:
EQUIL region number: if number is omitted then properties are applied to entire grid;
initial composition: 0 for each component.
Example
F(DE
300.000 2* 0.5 0.5 /
360.000 2* 0.5 0.5 /
400.000 2* 0.5 0.5 /
600.000 2* 0.5 0.5 /
14.2.16. F(DE 1949

14.2.17 INTE (FLUID)

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword is used to specify binary interaction coefficients for an equation-of-state

model. In the next lines a table with the following columns is set:
1. subkeyword ROW which sets coefficients input method: coefficients are specified for
all components with a lower component number. Components are numerated in the
same order in which they are defined in the keyword CNAM (see 14.1.7);
2. component name;
3. binary interaction coefficients. Their amount depends on a component number.
This keyword has an Eclipse compatible analogue BIC (see 12.13.32).

Default:
binary interaction coefficients: 0 for unspecified pairs.
Example
CNAM N2 CO2 H2S C1 C2 C3 WATR
INTE
ROW CO2 0.00000
ROW H2S 0.13000 0.05000
ROW C1 0.02500 0.10500 0.07000
ROW C2 0.01000 0.05000 0.08500 0.00000
ROW C3 0.09000 0.05000 0.08000 0.00000 0.00000
/
In the example the table of binary interaction coefficients for 6 components is specified.
14.2.17. INTE (FLUID) 1950

14.2.18 PROP

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword is used to define component properties in an equation-of-state model. The

1. name or number of the component (numbering is set by the order of specified compo-
nents in the keyword CNAM (see 14.1.7));
2. molecular weight;
3. critical temperature (METRIC: K , FIELD: R);
4. critical pressure (METRIC: bar , FIELD: psi);
5. acentric factor;
6. critical Z-factor;
7. this is a MORE compatibility field. Gravity of the liquid;
8. component parachor.
Example
PROP
N2 28.000 227.300 493.000 0.04500 0.28295 0.80800 41.000
CO2 44.000 547.600 1070.600 0.23100 0.27327 0.82700 70.000
H2S 34.100 672.400 1306.000 0.10000 0.28958 0.78920 41.000
C1 16.000 343.000 667.800 0.01200 0.32824 0.30000 77.000
C2 30.100 549.800 707.800 0.09100 0.32408 0.35630 108.000
C3 44.100 665.700 616.300 0.14500 0.31899 0.50690 150.300
/
In the example properties for 6 components are set.
14.2.18. PROP 1951

14.2.19 TRAC (FLUI)

INPU x FLUI RELA

Section
GRID INIT RECU
The keyword defines tracer. The following parameters should be specified:
1. tracer name;
2. component name which is assigned to tracer.
This keyword has an Eclipse compatible analogue TRACER (see 12.7.1).
Example
TRAC TRC1 H2S
In the example tracer TRC1 is assigned with component H2S.
14.2.19. TRAC (FLUI) 1952

14.3. RELAtive Permeability Data Section tNavigator-4.2
14.3 RELAtive Permeability Data Section
14.3. RELAtive Permeability Data Section 1953

14.3.1 RELA

INPU FLUI x RELA

Section
GRID INIT RECU
The keyword begins RELAtive Permeability Section.
Example
RELA
14.3.1. RELA 1954

14.3.2 WETT

INPU FLUI x RELA

Section
GRID INIT RECU
The keyword specifies wettability options and the method of three phase relative perme-
ability calculations.
The following options can be specified:
1. wettability (in order of decreasing wettability): OIL (oil, water and gas) or WATEr
(water, oil and gas);
2. method of three phase relative permeability calculations: STN1 (Stone 1 model) or

STN2 (Stone 2 model) or LINE (Three phase relative permeability data obtained as
straight line interpolation between the two phase relative permeability tables KRWO
(see 14.3.3), KRGO (see 14.3.4)).
STN1 is analogous to an Eclipse compatible keyword STONE1 (see 12.6.20); STN2 is

analogous to an Eclipse compatible keyword STONE2 (see 12.6.21); LINE is analogous to
Eclipse and tNavigator default interpolation of three phase relative permeability data.
Example
WETT LINE
14.3.2. WETT 1955

14.3.3 KRWO

INPU FLUI x RELA

Section
GRID INIT RECU
The keyword specifies relative permeability tables for water-oil systems. Each tables row
1. water saturation;
2. water permeability;
3. oil permeability;
4. oil-water capillary pressure;
5. ignored, this is a MORE compatibility field;
6. ignored, this is a MORE compatibility field.
The keyword has an Eclipse compatible analogue SWOF (see 12.6.1) (four parameters
of this keyword correspond to SWOF four parameters).
Example
KRWO
0.1200 0.00 1.0 /
0.200 0.00 1.0 /
0.6000 0.3 0.3 /
1.000 1.00 0.0 /
/
In this example relative permeability table for water-oil systems is specified for 4 pressure
values.
14.3.3. KRWO 1956

14.3.4 KRGO

INPU FLUI x RELA

Section
GRID INIT RECU
The keyword specifies relative permeability tables for gas-oil systems. Each tables row
1. gas saturation;
2. gas permeability;
3. oil permeability;
4. gas-oil capillary pressure;
5. ignored, this is a MORE compatibility field;
6. ignored, this is a MORE compatibility field.
The keyword has an Eclipse compatible analogue SGOF (see 12.6.2) (four parameters of
this keyword correspond to SGOF four parameters).
Example
KRGO
0.0000 0.0000 1.0000 /
0.0200 0.0000 0.9970 /
0.0500 0.0050 0.9800 /
0.1200 0.0250 0.7000 /
0.25 0.1250 0.2000 /
0.3 0.1900 0.090 /
0.45 0.6000 0.0100 /
0.5 0.7200 0.0010 /
0.7 0.9400 0.000 /
0.88 1.0000 0.0000 /
/
In this example relative permeability table for gas-oil systems is specified for 10 pressure
values.
14.3.4. KRGO 1957

14.4. GRID Data Section tNavigator-4.2
14.4 GRID Data Section
14.4. GRID Data Section 1958

14.4.1 GRID

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword begins GRID Section.
14.4.1. GRID 1959

14.4.2 VERT

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword specifies a vertical data input mode.
tNavigator supports the following MORE input data modes:
VERT BLOCK - grid array layers are input successively in a vertical order.
Example
VERT BLOCK
14.4.2. VERT 1960

14.4.3 HORI

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword specifies a horizontal data input mode.
tNavigator supports the following MORE input data modes:
HORI BLOCK - values of parameter enters in every cell of block layer.
14.4.3. HORI 1961

14.4.4 SIZE

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword specifies size and type of grid.
1. number of grid cells in X-direction;
2. number of grid cells in Y-direction;
3. number of grid cells in Z-direction;
4. CARTesian can be specified additionally - The Cartesian coordinate system (this option
can not be specified, because only the Cartesian system is supported).
The keyword is analogous to an Eclipse keyword DIMENS (see 12.1.25).
Example
SIZE 120 120 10
Coordinate system of size 120x120x10 is set in this example.
14.4.4. SIZE 1962

14.4.5 DATUm

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword specifies the value of datum depth.
There are two ways of specifying the datum depth:
specifies the value of depth only. In this case bottom hole pressures will be converted
to the datum depth (METRIC: m, FIELD: f t );
specifies the value of depth and parameter TOPC. In this case bottom hole pressures
will be set to the top open completion of a well (or the top completion if no completions
are open).
The keyword is analogous to an Eclipse keyword DATUM (see 12.15.34).
Example
DATUM 2560.32
In this example the specified value of datum depth is 2560.32 meters. Bottom hole
pressures will be calculated for specified depth.
14.4.5. DATUm 1963

14.4.6 X-DIrection

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword defines grid spacing in the X-direction.
The next line after keyword has to contain the way of specifying data. tNavigator supports
the following MORE ways:
VARI - definition of block sizes in X-direction (different block sizes, non-uniform grid).
After CONS should be specified all grid blocks lengths in X-direction in meters;
CONS - specify a uniform grid spacing in X-direction. After CONS total value of
length in X-direction should be specified in meters.
The keyword is analogous to an Eclipse keyword DX (see 12.2.2).
Example
X-DIRECTION
CONSTANT
3048.0
In the example specified a uniform grid spacing and a total grid length of 3048 in the
X-direction.
Example
X-DIRECTION
VARIABLE
100 2*95 5*110 200 400 600
In the example specified grid spacings of varying lengths in the X-direction.
14.4.6. X-DIrection 1964

14.4.7 Y-DIrection

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword defines grid spacing in the Y-direction.
The next line after keyword has to contain the way of specifying data. tNavigator supports
the following MORE ways:
VARI - definition of block sizes in Y-direction (different block sizes, non-uniform grid).
After CONS should be specified all grid blocks lengths in Y-direction in meters;
CONS - specify a uniform grid spacing in Y-direction. After CONS total value of length
in Y-direction should be specified in meters.
The keyword is analogous to an Eclipse keyword DY (see 12.2.2).
Example
Y-DIRECTION
CONSTANT
3048.0
In the example specified a uniform grid spacing and a total grid length of 3048 in the
Y-direction.
Example
Y-DIRECTION
VARIABLE
100 2*95 5*110 200 400 600
In the example specified grid spacings of varying lengths in the Y-direction.
14.4.7. Y-DIrection 1965

14.4.8 DEPTh / ZGRI

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword defines values of cells depth (METRIC: m, FIELD: f t ).
tNavigator supports the following MORE modes of input data and editing it in a vertical
direction:
l1 : l2 - region of block layers in a vertical direction. If region is not specified, then

all layers will be selected;
UNIForm - the array is constant layer-by-layer: then values are specified for one layer
only;
VARIable - the array is changed layer-by-layer;
TOPS (TOP) - values are specified only for the upper part of layer.
tNavigator supports the following MORE modes of data input and editing it in horizontal
direction:
VARIable - for every layer the full set of values should be entered;
CONStant - for every layer the only constant value should be entered;
ZVARiable - values are constant in one layer; values for all layers should be specified
once (one value for every layer).
The keyword has an Eclipse compatible analogue TOPS (see 12.2.6).
Example
DEPTH 1 TOP
CONSTANT
2537.46
In the example the depth of a top layer of cells is 2537.46 meters. The given depth is
constant for all cells of a top layer.
14.4.8. DEPTh / ZGRI 1966

14.4.9 THICkness

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword defines values of cells thickness (METRIC: m, FIELD: f t ).
direction:

only;
direction:
ZVARiable - values are constant in one layer; values for all layers are specified once
(one value for every layer).
The keyword has an Eclipse compatible analogue DZ (see 12.2.2).
Example
THICKNESS
ZVARIABLE
6.0 6.5 6.8
In the example the thickness of all cells of the first layer is 6 meters, of the second one
is 6.5 meters, of the third one is 6.8 meters.
14.4.9. THICkness 1967

14.4.10 POROsity

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword defines values of cells porosity.
direction:

only;
direction:
The keyword has an Eclipse compatible analogue PORO (see 12.2.24).
Example
POROSITY UNIF
CONSTANT
0.3
In the example porosity is defined as constant layer-by-layer (POROSITY UNIF). The

value is specified only in one layer. Porosity values in one layer are equal to 0.3.
14.4.10. POROsity 1968

14.4.11 MINPv

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword MINP is used to specify a minimum pore volume tolerance (rm3 ). The cells
which have pore volume less than specified value will be made inactive. The data should be
The keyword should be followed by parameters that define the way of data specification
and a number which defines minimal value of pore volume.
tNavigator supports the following parameters of MORE data input:

VALU. If this parameter is set, all cells, which has absolute pore volume less than the
specified value, will be inactive (Example 2).
MORE. Use MORE volume units (METRIC: m3 , FIELD: f t 3 ).
ECLI. Use Eclipse volume units (METRIC: m3 , FIELD: rb).
Default.
If the keyword is not specified at all, the minimum pore volume is 0.000001.
The keyword is set without additional parameters of data input (Example 1). The cells
which have pore volume less than specified ratio (to the average pore volume) will be
made inactive.
The keyword has an Eclipse compatible analogue MINPV (see 12.2.30).
Example 1:
Example
MINPV
0.001/
Make cells which have the value of pore volume less than 0.1% (to the average pore
volume) inactive.
Example 2:
Example
MINPV VALU
0.001/
Make cells with the value of pore volume less than 0.001 rm3 inactive.
14.4.11. MINPv 1969

14.4.12 K_X / K_Y / K_Z

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword defines values of cells permeability in X-, Y-, Z-direction (METRIC: mD,
FIELD: mD).
direction:
only;
direction:
CONStant - for every layer only one value should be entered;
The keyword has an Eclipse compatible analogue PERMX (see 12.2.13), PERMY (see
12.2.13), PERMZ (see 12.2.13).
Example
K_X
ZVARIABLE
500.0 500.0 500.0
K_Z
ZVARIABLE
50.0 50.0 50.0
In the example the value of permeability of all cells and all layers in X-direction is equal
to 500, the one in Z-direction is equal to 50.
14.4.12. K_X / K_Y / K_Z 1970

14.4.13 CROC

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword defines rock compressibility values for cells which are defined by the key-
word REFE (see 14.4.14) (METRIC: 1/bar , FIELD: 1/psi).
Default:
rock compressibility values: 0.
direction:
only;
direction:
Analogous to this keyword is the 2-nd parameter of the keyword ROCK (see 12.5.16),
Example
CROCK UNIF
CONSTANT
4.35114e-05
In the example value of rock compressibility is defined as constant layer-by-layer (CROCK

UNIF). The value is specified only in one layer. Rock compressibility values in one layer are
equal to 4.35114e-05.
14.4.13. CROC 1971

14.4.14 REFE

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword defines reference pressure, which defines rock compressibility values for
cells (CROC (see 14.4.13)) (METRIC: barsa, FIELD: psia).
Default:
reference pressure: 1.01325 atm.
tNavigator supports the following MORE modes of input data and editing it in vertical
direction:
only;
tNavigator supports the following MORE modes of input data and editing it in horizontal
direction:
Analogous to this keyword is the 1-st parameter of the keyword ROCK (see 12.5.16),
Example
REFE UNIF
CONSTANT
276.804
In the example reference pressure is defined as constant layer-by-layer(REFE UNIF). The

value is specified only in one layer. Reference pressure values in one layer are equal to
276.804.
14.4.14. REFE 1972

14.4.15 ACTN

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is used to specify active and inactive cells. 1 cell is active, 0 cell is
inactive. Symbol * can be used to specify repeating values in neighbour cells.
Default:
1 in all cells.
This keyword has an Eclipse compatible analogue ACTNUM (see 12.2.29).
Example
ACTN
100*1
In the example the value 1 is applied to 100 neighbour cells.
Example
ACTN
1 1 1 1 1
1 0 0 0 1
1 0 0 0 1
1 1 1 1 1
In the example cells activity of grid of size 5o4o1 is specified.
14.4.15. ACTN 1973

14.4.16 COORd

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword specify coordinate lines. Geometry of grid is building by these lines. The
1. ZXY or X&Y:
ZXY - (Nx + 1) (Ny + 1) coordinate lines are specified, each of them is
defined by two points with different depths. (Nx - the number of blocks in
X -direction, Ny - the number of blocks in Y -direction);
X&Y - only x - and y-coordinates specified. In z-direction lines are parallel
to other lines.
2. [additional parameter] VERT - make coordinate lines to be vertical by specifying
positions of all points below each line to average values of specified values.
in the next line:
1. values of coordinates.

This keyword has an Eclipse compatible analogue COORD (see 12.2.8).
Default:
ZXY or X&Y: ZXY;
Example
COOR
0 0 1 0 0 2
1 0 1 1 0 2
0 1 1 0 1 2
1 1 1 1 1 2
0 2 1 0 2 2
1 2 1 1 2 2
/
In the example 6 coordinate lines are specified; each of them is specified by three
coordinates of two points with different depths.
14.4.16. COORd 1974

14.4.17 FIPN

INPU FLUI RELA

Section
x GRID INIT RECU
For every grid block this keyword specifies the fluid-in-place region to which it belongs.
Default: 1.
This keyword has an Eclipse compatible analogue FIPNUM (see 12.4.10).
Example
FIPN
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4 /
In the example 4 regions are specified.
14.4.17. FIPN 1975

14.4.18 SATNum / ROCK

INPU FLUI RELA

Section
x GRID INIT RECU
saturation function region to which it belongs. The following parameters should be specified:
1. number of saturation region for each grid block.
Default:
number of saturation region: 1.
This keyword has an Eclipse compatible analogue SATNUM (see 12.4.3).
Example
SIZE
5 3 2
...
SATN
2 2 2 2 2 1 1 1 1 1 2 2 1 1 1
2 2 2 2 2 1 1 1 1 1 2 2 1 1 1
In the example 2 saturation regions are specified for grid 5x3x2.
14.4.18. SATNum / ROCK 1976

14.4.19 AQCD

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is used to connect aquifer at specified depth. The following parameters
1. aquifer name (it is specified via the keyword AQCT (see 14.4.21));
2. aquifer connection depth (METRIC: m, FIELD: f t );
3. [additional parameter] equilibration region of this connection.
Default:
equilibration regions: all regions.
Aquifer will be connected with all cells which are above specified depth. Any cell, which
is fully below specified depth, is inactive.
This keyword has an Eclipse compatible analogue AQUANCON (see 12.16.10).
Example
AQCD horizont 2300
In the example the keyword AQCD is used to connect aquifer horizont at depth 2300 in
all equilibration regions.
14.4.19. AQCD 1977

14.4.20 AQCO

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is used to specify blocks to which aquifer will be connected. The following
1. aquifer name (it is specified via the keyword AQCT (see 14.4.21));
2. i-coordinate of the first cell to connect aquifer;
3. i-coordinate of the last cell to connect aquifer;
4. j -coordinate of the first cell to connect aquifer;
5. j -coordinate of the last cell to connect aquifer;
6. k -coordinate of the first cell to connect aquifer;
7. k -coordinate of the last cell to connect aquifer;
8. face to connect aquifer. Possible values: X+, X, Y +, Y , Z+ or Z (or their
analogues, correspondingly I+, I, J+, J, K+, K).
Default:
i-coordinate of the first cell to connect aquifer: 1;
i-coordinate of the last cell to connect aquifer: Nx ;
j -coordinate of the first cell to connect aquifer: 1;
j -coordinate of the last cell to connect aquifer: Ny ;
k -coordinate of the first cell to connect aquifer: 1;
k -coordinate of the last cell to connect aquifer: Nz ;
face to connect aquifer: all possible faces (i.e. ones, which has no neighbor active
cells).
This keyword has an Eclipse compatible analogue AQUANCON (see 12.16.10).
Example
AQCO horizont_1 58 58 1 9 1* 1* x+/
AQCO horizont_2 27 27 1 10 1* 1* x+/
In the example the keyword AQCO is used to connect aquifer horizont.
14.4.20. AQCO 1978

14.4.21 AQCT

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword specifies Carter-Tracy aquifer properties. After that you need to specify
connections of the aquifer with grid via the keyword AQCO (see 14.4.20). The following
1. aquifer name;
2. reference depth (METRIC: m, FIELD: f t );
3. aquifer permeability (mD);
4. aquifer porosity;
5. total aquifer compressibility (sum of water and rock compressibility) (METRIC: 1/bar ,
FIELD: 1/psi);
6. inner aquifer radius (METRIC: m, FIELD: f t );
7. influence angle (angle between formation and aquifer) ( );
8. aquifer height (METRIC: m, FIELD: f t );
9. initial pressure at reference depth (METRIC: bar , FIELD: psi);
10. water viscosity (cP);
11. [additional parameter] water pressure table index. IGNORED, this is a MORE com-
patibility field;
12. [additional parameter] influence function table index AQUT, which specifies pressure
dependence on time. IGNORED, this is a MORE compatibility field;
13. [additional parameter] EQUI - the aquifer will be set up in equilibrium with the
pressure in reservoir;
14. [additional parameter] NOBACK - used to deny water backflow;
Default:
initial pressure at reference depth: initial reservoir pressure;
index of table AQUT: 0.
14.4.21. AQCT 1979

This keyword has an Eclipse compatible analogue AQUCT (see 12.16.8).
Example
AQCT horizont 3168 10 0.07 0.000045 2500 360 0.8 1*/
In the example Carter-Tracy aquifer is created. It is named horizont. Aquifer depth -

3168 m, permeability - 10, porosity - 0.07, total compressibility - 0.000045, inner radius
- 2500, influence angle - 360, height - 0.8. Initial pressure at reference depth is set up in
equilibrium with the pressure in reservoir.
14.4.21. AQCT 1980

14.4.22 AQFE

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword specifies Fetkovitch aquifer properties. After that you is need to specify
connections of the aquifer with grid via the keyword AQCO (see 14.4.20). The following
1. aquifer name;
2. reference depth (METRIC: m, FIELD: f t );
3. initial pore volume of the aquifer (METRIC: sm3 , FIELD: stb);
4. total aquifer compressibility (sum of water and rock compressibility) (METRIC: 1/bar ,
FIELD: 1/psi);
5. aquifer productivity coefficient (METRIC: sm3 /day/bar , FIELD: stb/day/psi);
This keyword has an Eclipse compatible analogue AQUFETP (see 12.16.6).
Example
AQFE horizont1 6250 1.0E9 3E-7 18800
In the example Fetkovitch aquifer horizont1 is defined. Aquifer depth is 6250, initial
pore volume is 1.0E9, total compressibility is 3E-7 and productivity coefficient is 18800.
14.4.22. AQFE 1981

14.4.23 AQUW

x INPU FLUI RELA

Section
GRID INIT RECU
The keyword sets water saturation in water zone. The following parameters should be
specified:
1. YES or NO:
YES set up water saturation in water zone to 1;

NO water saturation is set to maximal value of it in the table SWU.
It is allowed to use ON and OFF instead of YES and NO correspondingly.

Default:
YES or NO: YES.
Example
AQUW YES /
In the example water saturation value in water zone is set to 1.
Example
AQUW NO /
In the example water saturation value in water zone is set to residual saturation.
14.4.23. AQUW 1982

14.4.24 CONS (GRID)

INPU FLUI RELA

Section
x GRID x INIT RECU
The keyword is used to assign constant value of parameter to one or several layers of
grid. The following parameters should be specified:
1. value to assign to layers.
if this keyword is used after the keyword X-DI (see 14.4.6) or Y-DI (see 14.4.7).
In this case the keyword CONS specifies blocks size in X - or Y -direction correspond-
ingly. The following parameters should be specified:
1. total length of grid in X - or Y -direction (METRIC: m, FIELD: f t ).
Example
CROC
CONS
4e-05
CONS
3e-05 /
In the example values of rock compressibility coefficients are specified for the first and
the second grid layers. They are equal to 4e-05 and 3e-05 correspondingly.
Example
Y-DIRECTION
CONSTANT
3048.0
In the example uniform grid in Y-direction is specified. Its total length is 3048 m.
14.4.24. CONS (GRID) 1983

14.4.25 DEFI

INPU FLUI RELA

Section
x GRID x INIT RECU
The keyword is used to specify name of a new array. The following parameters should
be specified:
name to assign to a new array;
in the next line:
name of this array. it should be quoted. It can be empty, but then this line should
be empty. IGNORED, this is a MORE compatibility field.
Example
DEFI PINIT
ORIGINAL PERMEABILITY
In the example name PINIT is specified for a new array.
14.4.25. DEFI 1984

14.4.26 DPSS

INPU FLUI RELA

Section
x GRID x INIT RECU
The keyword sets that dual porosity source/sink model will be used during calculation.
This keyword is using single grid. The following parameters should be specified:
[additional parameter] GRAV - use gravity drainage option;
[additional parameter] NET - treat fracture permeabilities as net.
Example
DPSS NET
In the example the keyword DPSS (see 14.4.26) sets that dual porosity model with single
grid and net values of fracture permeabilities will be used.
14.4.26. DPSS 1985

14.4.27 FSAT

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword should be followed by one integer for every fracture grid block specifying
the saturation function region to which it belongs. This keyword is used in dual porosity
model with single grid (see DPOR (see 14.1.11)).
The number of specified values should be equal to the number of fracture cells. The
number of saturation region for each fracture block.
Default:
number of saturation region: correspondingly to the keyword SATN (see 14.4.18).
Example
FSAT
1 1 1 1 1 2 2 2 2 2
In the example disposition of two regions are specified.
14.4.27. FSAT 1986

14.4.28 FSWA

INPU FLUI RELA

Section
x GRID INIT RECU
By this keyword water saturation values for each fracture block is specified. This keyword
is in dual porosity model with single grid (see DPOR (see 14.1.11)). The following parameters
1. water saturation values for each fracture block.
This keyword has an Eclipse compatible analogue SWAT (see 12.15.10).
Example
FSWA
0.25 0.25 0.25 0.25 0.25 0.25
0.25 0.25 0.25 0.25 0.25
0.50 0.50 0.50 0.50 0.50 0.50
In the example water saturation values are specified for 17 fracture blocks.
14.4.28. FSWA 1987

14.4.29 FPVT

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword should be followed by one integer for every fracture block specifying the
PVT region to which it belongs. This keyword is in dual porosity model with single grid (see
DPOR (see 14.1.11)).
The number of specified values should be equal to the number of fracture cells. The
Default:
PVT region number: correspondingly to the keyword PVTN (see 14.4.30).
This keyword has an Eclipse compatible analogue PVTNUM (see 12.4.2).
Example
FPVT
1 1 1 1 1 2 2 2 2 3
In the example for 10 fracture blocks disposition of 3 PVT regions is specified.
14.4.29. FPVT 1988

14.4.30 PVTN

INPU FLUI RELA

Section
x GRID INIT RECU
region to which it belongs. The number of values should be equal to the number of blocks.
Default:
PVT region number: 1 for each block.
This keyword has an Eclipse compatible analogue PVTNUM (see 12.4.2).
Example
SIZE 5 3 2
...
PVTN
1 1 1 1 1 2 2 2 2 2 3 2 3 3 3
1 1 1 1 1 2 2 2 2 2 3 2 3 3 3 /
This example defines disposition of three PVT-regions with different PVT properties for
a 5x3x2 grid.
14.4.30. PVTN 1989

14.4.31 DZMA

INPU FLUI RELA

Section
x GRID INIT RECU
This keyword has an Eclipse compatible analogue DZMTRXV (see 12.2.76).
14.4.31. DZMA 1990

14.4.32 EQUI / EQLN

INPU FLUI RELA

Section
x GRID INIT RECU
equilibrium region to which it belongs. Use symbol * to specify the same consecutive
values.
For each equilibrium region its initial conditions must be specified via the keyword EQUI
(see 14.5.4).
Default:
1 for all blocks.
This keyword has an Eclipse compatible analogue EQLNUM (see 12.4.9).
Example
EQLN
2 2 2 2 2 1 1 1 1 1 2 2 1 1 1
2 2 2 2 2 1 1 1 1 1 2 2 1 1 1
This example defines disposition of two equilibration regions for a 5x3x2 grid.
14.4.32. EQUI / EQLN 1991

14.4.33 F(PO

INPU FLUI RELA

Section
x GRID x INIT RECU
The keyword specifies values array of some parameter as a porosity function. The fol-
1. [additional parameter] interpolation method: LOGA (logarithmic interpolation)

or LINE (linear interpolation).
in the following lines a table with two columns is specified. Each line of this table
should contain:
1. porosity value;
2. array value, which corresponds to this porosity value.
Porosity values should be specified before the keyword F(PO (see 14.4.33). The data
This keyword has an Eclipse compatible analogue PORO (see 12.2.24).

Default:
interpolation method: LINE.
Example
K_Y UNIF
F(PO
0.31 100
0.36 150
0.39 450
0.41 650
/
In the example permeability values in Y -direction are set via the keyword F(PO. Interpo-
lation method is linear.
14.4.33. F(PO 1992

14.4.34 FAUL

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is used to mark a group of connections as a fault for the following mod-
ification by the keyword FMUL (see 14.4.35). Marked connections can define a part of the
fault or several faults.The following parameters should be specified:
1. fault name;
2. starting layer in Z -direction;
3. ending layer in Z -direction;
in the next line:
1. i-coordinate of block corner of fault beginning;

2. j -coordinate of block corner of fault beginning;
3. TO-I / TO-J:
TO-I - fault is in I -direction;
TO-J - fault is in J -direction.
4. i- or j -coordinate (depending on value of previous parameter) of point, to which
fault directed.
Default:
starting layer: 1;
ending layer: nz .
This keyword has an Eclipse compatible analogue FAULTS (see 12.2.37).
Example
FAUL f607-611 1 19
58 83 TO-I 65 TO-J 86 TO-I 63 TO-J 88 TO-I 61 TO-J 92/
In the example via the keyword FAUL (see 14.4.34) faults are defined the following way:
fault name is f607-611; starting fault layer is 1, ending one is 19; coordinates of block corner
of fault beginning are: 58 in I , 83 in J ; then fault goes to coordinate 65 in I -direction; then
it goes to coordinate 86 in J -direction and so on.
14.4.34. FAUL 1993

14.4.35 FMUL

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword sets transmissibility multiplier of fault, which is defined by the keyword
FAUL (see 14.4.34). The following parameters should be specified:
1. fault name;
2. transmissibility multiplier value.
Default:
transmissibility multiplier value: 0.
This keyword has an Eclipse compatible analogue MULTFLT (see 12.2.38).
Example
FAUL f607-611 1 19
58 83 TO-I 65 TO-J 86 TO-I 63 TO-J 88 TO-I 61 TO-J 92/
/
FMUL f607-611 0.05 /
In the example the keyword FMUL (see 14.4.35) sets transmissibility multiplier value for
fault f607-611, which is equal to 0.05. Fault f607-611 was defined via the keyword FAUL
(see 14.4.34).
14.4.35. FMUL 1994

14.4.36 FCRO

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword sets rock compressibility values of fracture blocks. This keyword is used
in dual porosity model with single grid (see DPOR (see 14.1.11)). The following parameters
1. rock compressibility values for each fracture block.
Default:
rock compressibility values: correspondingly to the keyword CROC (see 14.4.13).
Example
FCRO UNIF
CONS
0.0197
In the example the keyword FCRO sets values of rock compressibility for fracture blocks.
They are equal to 0.0197.
14.4.36. FCRO 1995

14.4.37 FKX / FKY / FKZ

INPU FLUI RELA

Section
x GRID INIT RECU
These keywords specify the array of permeability values of fracture blocks in X - / Y - /

Z - directions correspondingly.
These keywords are used in dual porosity model with single grid (see DPOR
(see 14.1.11)). The following parameters should be specified:
1. permeability values of fracture blocks.
Default:
values of FKY and FKZ: FKX.
Example
FKX
0 0 0
0.56 0.58 0.55
0.55 0.55 0.54
0.59 0.58 0.58
0.57 0.55 0.56
0.53 0.53 0.53
0 0 0
In the example permeability values in X -direction are specified for 21 fracture blocks.
14.4.37. FKX / FKY / FKZ 1996

14.4.38 FMLX / FMLY / FMLZ

INPU FLUI RELA

Section
x GRID INIT RECU
These keywords set array of transmissibility multipliers of fracture blocks in Ox / Oy /

Oz- directions correspondingly. These keywords are used in dual porosity model with single
grid (see DPOR (see 14.1.11)). The following parameters should be specified:
1. transmissibility multipliers of fracture blocks.
Default:
transmissibility multipliers of fracture blocks: 1.
Example
FMLX
10*3
In the example the keyword FMLX sets value of transmissibility which, is equal 3, for all
fracture blocks.
14.4.38. FMLX / FMLY / FMLZ 1997

14.4.39 FEQL

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword should be followed by one integer for every fracture block specifying the
equilibrium region to which it belongs. This keyword is used in dual porosity model with
single grid (see DPOR (see 14.1.11)). The following parameters should be specified:
1. equilibrium region number to which belongs fracture block.
Default:
equilibrium region number: correspondingly to the keyword EQLN (see 14.4.32).
Example
EQLN
2 2 1 1 1
2 1 1 1 2
This example defines disposition of two equilibration regions for fracture.
14.4.39. FEQL 1998

14.4.40 FPOR

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword specifies porosity value for each fracture block. This keyword is used in
dual porosity model with single grid (see DPOR (see 14.1.11)). The following parameters
1. porosity value for each fracture block.
Default: None.
Example
FPOR
0.79 0.52 0.66 0.89
0.58 0.61 0.75 0.67
0.62 0.63 0.68 0.82
In the example porosity values are specified for all fracture blocks.
14.4.40. FPOR 1999

14.4.41 FREF

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword sets reference pressure values which defines rock compressibility values for
fracture blocks. This keyword is used in dual porosity model with single grid (see DPOR
(see 14.1.11)). The following parameters should be specified:
1. reference pressure values for each fracture block (METRIC: bar , FIELD: psi).
Default:
reference pressure values: correspondingly to the keyword REFE (see 14.4.14).
Example
FREF
5*15 5*20
In the example 2 different reference pressure values are specified for 10 fracture blocks.
They are equal to 15 and 20 bars correspondingly.
14.4.41. FREF 2000

14.4.42 IEQ

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword returns 1 if its parameters are equal and returns 0 otherwise. This keyword
has 2 parameters, each or them is value of some expression.
Example
K_X=0.001*IEQ (ACTNUM,0)+(692272*PORO**5.25)*IEQ (ACTNUM,1)
In the example value of K_X (see 14.4.12) is calculated. The value of ACTNUM
(see 12.2.29) is comparing with 0 and 1 via the keyword IEQ.
14.4.42. IEQ 2001

14.4.43 INTE (GRID)

INPU FLUI RELA

Section
x GRID x INIT RECU
The keyword specifies distance weighted interpolation for array of values. The following
1. exponential weighting coefficient (minimal value: 0.1; maximal value: 10);

2. number of nearest neighbors to interpolate (minimal value: 2; maximal value: is
not limited);
3. interpolation range (values outside this range will be ignored) (minimal value:
106 ; maximal value: is not limited);
4. NOXY or ALLX or TRIP:
NOXY - values of x and y are not specified, values which was entered before
will be used; function values at this points only are specified;
ALLX - all values of y and all function values are specified for all values x ;
TRIP - triplets (x, y, v) are specified, where v is the function value;
5. [additional parameter] SWIT - switch to another file with data to read.
in the next line:
1. coordinate of i-th point of interpolation in X -direction;

2. coordinate of i-th point of interpolation in Y -direction;
3. function value at point (xi , yi )
Default:
exponential weighting coefficient: 1.0;
number of nearest neighbors to interpolate: 4;
interpolation range: unlimited;
NOXY or ALLX or TRIP: TRIP;
14.4.43. INTE (GRID) 2002

Example
KZ UNIF /
INTE 1 4 1000 ALLX /
100 500 800 /
100 500 800 /
1 5 8 /
/
In the example the keyword INTE (see 14.4.43) with ALLX option is used to set perme-
ability values in Z -direction.
14.4.43. INTE (GRID) 2003

14.4.44 KPTA

INPU FLUI RELA

Section
x GRID INIT RECU
number of rock region - transmissibility dependence on pressure table - to which it belongs.
Tables for each rock region are specifying using the keyword KVSP (see 14.2.8).
1. the number of rock region for each cell of grid.
The number of specified integers should be equal to the number of grid cells. The table
number should not be less or equal the second parameter of the keyword KVSP (see 14.2.8).
Default:
the number of rock region: 1 for each grid cell.
This keyword has an Eclipse compatible analogue ROCKNUM (see 12.4.14).
Example
KPTA
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
2 2 2 2 2 1 1 1 1 1 3 3 4 4 4
This example defines disposition of four rock regions for 30 cells of grid.
14.4.44. KPTA 2004

14.4.45 LAYE

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword should be specified after the keyword Y-DI (see 14.4.7), but before pore
volume and transmissibility modifiers.
This keyword is used to unify grid layers into groups to specify their common properties.
Such groups are named geological layers. The following parameters should be specified:
the number of layers in each geological layer.
Example
LAYE
1 3 2 3*1 /
In the example 9 layers of model are grouped into 6 geological layers.
14.4.45. LAYE 2005

14.4.46 LEVJ

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is used to specify Leverett J-factors to modify capillary pressures (the
keywords XPCG, XPCW). They will be calculated via Leverett J-function:
r
PORO
XPCG = LEV J
KX
Analogous formula is true for the keyword XPCW too.

1
1. J-factors for each grid cell (METRIC, FIELD: md 2 ).
Example
LEVJ
50*4
1
In the example J-factors are specified for 50 grid cells. They are equal to 4 md 2 .
14.4.46. LEVJ 2006

14.4.47 LGRD

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword specifies a Cartesian local grid refinement (LGR). LGRD specifies a cell or
a box of cells identified by its global grid coordinates X1-X2, Y1-Y2, Z1-Z2, to be replaced
by refined cells. The following parameters should be specified:
1. number of refined cells along X -direction;
2. number of refined cells along Y -direction;
3. number of refined cells along Z -direction;
4. lower coordinate of the box in the parent grid (along X -direction);
5. upper coordinate of the box in the parent grid (along X -direction);
6. lower coordinate of the box in the parent grid (along Y -direction);
7. upper coordinate of the box in the parent grid (along Y -direction);
8. lower coordinate of the box in the parent grid (along Z -direction);
9. upper coordinate of the box in the parent grid (along Z -direction);
10. name of the local grid refinement.
This keyword has an Eclipse compatible analogue CARFIN (see 12.2.87).
Example
LGRD
3 3 4 18 18 3 3 1 2 LGR1
In this example there is local grid refinement LGR1 of global grid. Box: layers 1 and 2
of global l grid (in Z direction), layer 18 in X direction, layer 3 in Y , are replaced by
Cartesian LGR 3x3x4.
14.4.47. LGRD 2007

14.4.48 MINDznet

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is used to make cells inactive. Cell becomes inactive if its thickness is less
than specified value (METRIC: m, FIELD: f t ).
Default:
0.1 m (0.32808 ft).
Example
MIND 0.2
In the example cells, which thickness is less than 0.2 m, will become inactive.
14.4.48. MINDznet 2008

14.4.49 MODI

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is used to modify data array values. The following parameters should be
specified:
1. first coordinate of modifying block in X -direction;

2. last coordinate of modifying block in X -direction;
3. first coordinate of modifying block in Y -direction;
4. last coordinate of modifying block in Y -direction;
5. first coordinate of modifying block in Z -direction;
6. last coordinate of modifying block in Z -direction;
7. [additional parameter] ZERO - values which are less than minimal one will be
set to 0. Minimal value is set in the following line;
8. [additional parameter] NINT - round the values to the nearest integer.
1. value to add to all array values;

2. value by which all array values will be multiplied;
3. minimal value;
4. maximal value;
Default:
first coordinate of modifying block in X -direction: 1
last coordinate of modifying block in X -direction: Nx ;
first coordinate of modifying block in Y -direction: 1;
last coordinate of modifying block in Y -direction: Ny ;
first coordinate of modifying block in Z -direction: 1
last coordinate of modifying block in Z -direction: Nz ;
14.4.49. MODI 2009

value to add to all array values: 0;
value by which all array values will be multiplied: 1;
minimal value: 0;
maximal value: 1020 ;
Example
KX
MODI 1 63 1 65 2*
2* 120/
In the example values of array KX are changing.
14.4.49. MODI 2010

14.4.50 MULX / MULY / MULZ (MX / MY / MZ, M_X / M_Y / M_Z, M-X / M-Y
/ M-Z, MULTX / MULTY / MULTZ)

INPU FLUI RELA

Section
x GRID INIT RECU
These keywords are used to specify transmissibility multipliers in X -, Y - and Z -

directions. The following parameters should be specified:
transmissibility multipliers values.
Analogous to these keywords are the keywords MULTX (see 12.2.15), MULTX- (see
12.2.16), MULTY (see 12.2.17), MULTY- (see 12.2.18), MULTZ (see 12.2.19), MULTZ-
(see 12.2.20) which are used by Eclipse.
Example
SIZE 5 5 4
...
MULX
100*2
In this example transmissibility multipliers are specified for all cells in X-direction. They
all are equal to 2.
14.4.50. MULX / MULY / MULZ (MX / MY / MZ, M_X / M_Y / M_Z, M-X / M-Y / M-Z, MULTX / MULT
14.4.51 PINCh

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is used to pinch out blocks which thickness is less than specified value.
[additional parameter] ON or OFF

ON - pinchout is turned on;
OFF - pinchout is turned off.
block thickness (METRIC: m, FIELD: f t ).
Default:
ON or OFF: ON;
block thickness: 0.1 m.
This keyword has an Eclipse compatible analogue PINCH (see 12.2.54).
Example
UNITS FIELD
...
PINCH ON
1 /
In the example all blocks which thickness is less than 1 ft will be pinched out.
14.4.51. PINCh 2012

14.4.52 PORV

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is analogous to the keyword PVOL (see 14.4.53) with the option REPL.
This keyword uses another units METRIC: m3 , FIELD: stb.
14.4.52. PORV 2013

14.4.53 PVOL / RVOL / PVR

INPU FLUI RELA

Section
x GRID INIT RECU
These keywords are used to modify values of pore volume array (METRIC: m3 , FIELD:
f t 3 ).
1. coordinate of the first block to modify in X -direction;
2. coordinate of the last block to modify in X -direction;
3. coordinate of the first block to modify in Y -direction;
4. coordinate of the last block to modify in Y -direction;
5. coordinate of the first block to modify in Z -direction;
6. coordinate of the last block to modify in Z -direction;
7. modification type: MODI (see 14.4.49) or REPL (see 14.4.58).
In the following line should be specified:
1. if the keyword MODI (see 14.4.49) is used:
value to add (add );

multiplier (mult );
minimal value (min);
maximal value (max ).
New values (valuenew ) is calculated by the formula:
valuenew = MINIMUM{max, add + mult valueoriginal },
where valueoriginal - original value.
2. if the keyword REPL (see 14.4.58) is used:
new values for blocks, which coordinates are specified above.
Default:
14.4.53. PVOL / RVOL / PVR 2014

coordinate of the first block to modify in X -direction: 1;
coordinate of the last block to modify in X -direction: Nx ;
coordinate of the first block to modify in Y -direction: 1;
coordinate of the last block to modify in Y -direction: Ny ;
coordinate of the first block to modify in Z -direction: 1;
coordinate of the last block to modify in Z -direction: Nz ;
modification type: MODI;
value to add: 0;
multiplier: 1;
minimal value: 0;
maximal value: 1020 .
This keyword has an Eclipse compatible analogue PORV (see 12.2.27).
Example
PVOL 63 63 2 120 2* MODI
0 3000/
In the example the keyword PVOL is used to increase cells pore volume in 3000 times.
14.4.53. PVOL / RVOL / PVR 2015

14.4.54 T_X / T_Y / T_Z (TX / TY / TZ, T-X / T-Y / T-Z)

INPU FLUI RELA

Section
x GRID INIT RECU
These keywords are used to modify values of transmissibility array (METRIC: m3 ,

FIELD: f t 3 ). The following parameters should be specified:
1. coordinate of the first block to modify in X -direction;
2. coordinate of the last block to modify in X -direction;
3. coordinate of the first block to modify in Y -direction;
4. coordinate of the last block to modify in Y -direction;
5. coordinate of the first block to modify in Z -direction;
6. coordinate of the last block to modify in Z -direction;
7. modification type: MODI (see 14.4.49) or REPL (see 14.4.58).
In the following line should be specified:
1. if the keyword MODI (see 14.4.49) is used:
value to add (add );

multiplier (mult );
minimal value (min);
maximal value (max ).
New values (valuenew ) is calculated by the formula:
valuenew = MINIMUM{max, add + mult valueoriginal },
where valueoriginal - original value.
2. if the keyword REPL (see 14.4.58) is used:
new values for blocks, which coordinates are specified above.
Default:
coordinate of the first block to modify in X -direction: 1;
14.4.54. T_X / T_Y / T_Z (TX / TY / TZ, T-X / T-Y / T-Z) 2016
coordinate of the last block to modify in X -direction: Nx ;
coordinate of the first block to modify in Y -direction: 1;
coordinate of the last block to modify in Y -direction: Ny ;
coordinate of the first block to modify in Z -direction: 1;
coordinate of the last block to modify in Z -direction: Nz ;
modification type: MODI;
value to add: 0;
multiplier: 1;
minimal value: 0;
This keyword has an Eclipse compatible analogue TRANX (see 12.2.51), TRANY (see
12.2.52), TRANZ (see 12.2.53).
Example
TX 28 31 98 100 1 4
0 2
In the example transmissibility values along X for specified blocks are modified be the
keyword MODI (see 14.4.49). They are will increase in 2 times.
14.4.54. T_X / T_Y / T_Z (TX / TY / TZ, T-X / T-Y / T-Z) 2017
14.4.55 VARI

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword should be specified after one of the keyword X-DI (see 14.4.6), Y-DI
(see 14.4.7). This keyword specifies sizes of blocks in X - or Y -directions. The following
1. size of i-th grid interval (not more than Nx (or Ny ) values).
Example
Y-DIRECTION
VARIABLE
100 2*95 5*110 200 400 600
In the example non-uniform grid along Y with different interval values is specified.
14.4.55. VARI 2018

14.4.56 NNC

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is used to specify non-neighbour connections. The following parameters

1. MULT [additional parameter] - values are recognized as transmissibility values;
2. MORE / ECLI - use MORE units (METRIC: md m; FIELD: md f t ) or Eclipse
units (METRIC: rm3 cp/bar ; FIELD: rb cp/psi);
3. ONPD vp [additional parameter] - dont use these connections while the pressure
difference across them dont exceeds specified value vp.
1. X -coordinate of first cell from non-neighbour connection;
2. Y -coordinate of this cell;
3. Z -coordinate of this cell;
4. X -coordinate of last cell from non-neighbour connection;
5. Y -coordinate of this cell;
6. Z -coordinate of this cell;
7. non-neighbor connection transmissibility.
Default:
units: ECLI.
This keyword has an Eclipse compatible analogue NNC (see 12.2.48).
Example
NNC
123 70 14 126 68 16 1000
123 70 14 125 67 16 1000
115 64 65 115 62 67 1000
116 64 66 116 63 68 1000
/
In the example 4 non-neighbour connections are specified.
14.4.56. NNC 2019

14.4.57 NTG / NTOG

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is used to specify net-to-gross values for each cell of grid. Same values
Symbol * can be used to specify repeating values in neighbour cells.
Default: 1 for each cell.

This keyword has an Eclipse compatible analogue NTG (see 12.2.25).
Example
NTG
100*0.2784
In the example net-to-gross value 0.2784 is specified for 100 grid cells.
Example
NTG
0.60 0.60 0.60 0.60 0.60 0.62 0.62 0.62 0.62 0.62
0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62
0.60 0.60 0.60 0.60 0.60 0.62 0.62 0.62 0.62 0.62
0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62 0.62
In this example net-to-gross values are specified for 40 grid cells.
14.4.57. NTG / NTOG 2020

14.4.58 REPL

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is used to modify array values. The following parameters should be speci-
fied:
1. first coordinate of modifying block in X -direction;

2. last coordinate of modifying block in X -direction;
3. first coordinate of modifying block in Y -direction;
4. last coordinate of modifying block in Y -direction;
5. first coordinate of modifying block in Z -direction;
6. last coordinate of modifying block in Z -direction;
1. new values of modifying array;
Default:
first coordinate of modifying block in X -direction: 1
last coordinate of modifying block in X -direction: Nx ;
first coordinate of modifying block in Y -direction: 1;
last coordinate of modifying block in Y -direction: Ny ;
first coordinate of modifying block in Z -direction: 1
last coordinate of modifying block in Z -direction: Nz ;
Example
SWL
REPL 71 73 101 103 154 184
279*0.38/
In the example SWL (see 12.6.27) values are changed. New value of this parameter (0.38)
is assigned to specified blocks.
14.4.58. REPL 2021

14.4.59 SGCR

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword specifies critical gas saturation in each cell for end point scaling.
1. critical gas saturation for each cell.
The number of entered values must be equal to the number of grid blocks.
Default:
critical gas saturation: corresponding to the keyword KRGO (see 14.3.4).
This keyword has an Eclipse compatible analogue SGCR (see 12.6.31).
Example
SGCR
50*0.35 50*0.45
This example defines critical gas saturation which is equal to 0.35 for first 50 blocks of
the grid and to 0.45 for last 50 blocks.
14.4.59. SGCR 2022

14.4.60 SGL

INPU FLUI RELA

Section
x GRID INIT RECU
This keyword defines connate gas saturation for grid blocks, used for saturation end point
scaling.
1. connate gas saturation for each grid block.
Default:
connate gas saturation: corresponding to the keyword KRGO (see 14.3.4).
This keyword has an Eclipse compatible analogue SGL (see 12.6.29).
Example
SGL
50*0.35 50*0.45
This example defines connate gas saturation which is equal to 0.35 for first 50 blocks of
14.4.60. SGL 2023

14.4.61 SGU

INPU FLUI RELA

Section
x GRID INIT RECU
This keyword defines maximal gas saturation for grid blocks, used for saturation end
point scaling.
1. maximal gas saturation for each grid block.
Default:
maximal gas saturation: corresponding to the keyword KRGO (see 14.3.4).
This keyword has an Eclipse compatible analogue SGU (see 12.6.35).
Example
SGU
50*0.75 50*0.85
This example defines maximal gas saturation which is equal to 0.75 for first 50 blocks of
14.4.61. SGU 2024

14.4.62 SOGC

INPU FLUI RELA

Section
x GRID INIT RECU
This keyword defines critical oil-to-gas saturation for grid blocks, used for saturation end
point scaling.
1. critical oil-to-gas saturation for each grid block.
Default:
critical oil-to-gas saturation: corresponding to the keyword KRGO (see 14.3.4).
This keyword has an Eclipse compatible analogue SOGCR (see 12.6.33).
Example
SOGCR
50*0.35 50*0.45
This example defines critical oil-to-gas saturation which is equal to 0.35 for first 50
blocks of the grid and to 0.45 for last 50 blocks.
14.4.62. SOGC 2025

14.4.63 SOWC

INPU FLUI RELA

Section
x GRID INIT RECU
This keyword defines critical oil-to-water saturation for grid blocks, used for saturation
end point scaling.
1. critical oil-to-water saturation for each grid block.
Default:
critical oil-to-water saturation: corresponding to the keyword KRGO (see 14.3.4).
This keyword has an Eclipse compatible analogue SOWCR (see 12.6.32).
Example
SOWCR
50*0.15 50*0.20
This example defines critical oil-to-water saturation which is equal to 0.15 for first 50
blocks of the grid and to 0.20 for last 50 blocks.
14.4.63. SOWC 2026

14.4.64 SWU

INPU FLUI RELA

Section
x GRID INIT RECU
This keyword defines maximal water saturation for grid blocks, used for saturation end
point scaling.
1. maximal water saturation for each grid block.
Default:
maximal water saturation: corresponding to the keyword KRWO (see 14.3.3).
This keyword has an Eclipse compatible analogue SWU (see 12.6.34).
Example
SWU
0.94 1.00 1.00 1.00 1.00
0.99 1.00 0.95 1.00 1.00
1.00 0.96 1.00 1.00 1.00
1.00 1.00 0.97 0.96 0.99
In the example the keyword SWU sets maximal water saturation for 20 cells of grid.
14.4.64. SWU 2027

14.4.65 SWL

INPU FLUI RELA

Section
x GRID INIT RECU
point scaling.
1. minimal water saturation for each grid block.
Default:
minimal water saturation: corresponding to the keyword KRWO (see 14.3.3).
This keyword has an Eclipse compatible analogue SWL (see 12.6.27).
Example
SWL
50*0.35 50*0.45
This example defines minimal water saturation which is equal to 0.35 for first 50 blocks
of the grid and to 0.45 for last 50 blocks.
14.4.65. SWL 2028

14.4.66 SWCR

INPU FLUI RELA

Section
x GRID INIT RECU
This keyword defines critical water saturation for grid blocks, used for saturation end
point scaling.
1. critical water saturation for each grid block.
Default:
critical water saturation: corresponding to the keyword KRWO (see 14.3.3).
This keyword has an Eclipse compatible analogue SWCR (see 12.6.30).
Example
SWCR
50*0.35 50*0.45
This example defines critical water saturation which is equal to 0.35 for first 50 blocks
of the grid and to 0.45 for last 50 blocks.
14.4.66. SWCR 2029

14.4.67 XKRG

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword sets scaling multipliers for the relative permeability values of gas at the
maximum gas saturation which is defined by oil-gas relative permeability curve (the keyword
KRGO (see 14.3.4)). The following parameters should be specified:
1. multipliers for gas relative permeability values for each grid block.
The number of entering values should be equal to the number of grid blocks.
Default:
multipliers for gas relative permeability values: 1 for each grid block.
This keyword has an Eclipse compatible analogue KRG (see 12.6.44).
Example
XKRG
0.97 1.00 1.00 1.00 1.00
0.96 1.00 1.00 1.00 1.00
1.00 0.97 1.00 1.00 1.00
1.00 1.00 0.97 0.99 0.93
This example defines scaling multipliers for 20 grid blocks.
14.4.67. XKRG 2030

14.4.68 XKRO

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword sets scaling multipliers for the relative permeability values of oil at the max-
imum oil saturation which is defined by water-oil relative permeability curve (the keyword
KRWO (see 14.3.3)). The following parameters should be specified:
1. multipliers for the oil relative permeability values for each grid block.
Default:
multipliers for the oil relative permeability values: 1 for each grid block.
This keyword has an Eclipse compatible analogue KRO (see 12.6.42).
Example
XKRO
0.96 1.00 1.00 1.00 1.00
0.96 1.00 1.00 1.00 1.00
1.00 0.98 1.00 1.00 1.00
1.00 1.00 0.95 0.94 0.99
14.4.68. XKRO 2031

14.4.69 XKRW

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword sets scaling multipliers for the relative permeability values of water at the
maximum water saturation which is defined by water-oil relative permeability curve (the
keyword KRWO (see 14.3.3)). The following parameters should be specified:
1. multipliers for the water relative permeability values for each grid block.
Default:
multipliers for the water relative permeability values: 1 for each grid block.
This keyword has an Eclipse compatible analogue KRW (see 12.6.43).
Example
XKRW
0.94 1.00 1.00 1.00 1.00
0.99 1.00 0.95 1.00 1.00
1.00 0.96 1.00 1.00 1.00
1.00 1.00 0.97 0.96 0.99
14.4.69. XKRW 2032

14.4.70 XPCG

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword sets scaling multipliers for the capillary pressure values of gas-oil system
which is defined by gas-oil relative permeability curve (the keyword KRGO (see 14.3.4)).
1. multipliers for the capillary pressure values for each grid block.
Default:
multipliers for the capillary pressure values: 1 for each grid block.
Example
XPCG
0.96 1.00 1.00 1.00 1.00
0.96 1.00 1.00 1.00 1.00
1.00 0.98 1.00 1.00 1.00
1.00 1.00 0.95 0.94 0.99
14.4.70. XPCG 2033

14.4.71 XPCW

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword sets scaling multipliers for the capillary pressure values of water-oil system
which is defined by water-oil relative permeability curve (the keyword KRGO (see 14.3.4)).
1. multipliers for the capillary pressure values for each grid block.
Default:
multipliers for the capillary pressure values: 1 for each grid block.
Example
XPCW
0.96 1.00 1.00 1.00 1.00
0.96 1.00 1.00 1.00 1.00
1.00 0.98 1.00 1.00 1.00
1.00 1.00 0.95 0.94 0.99
14.4.71. XPCW 2034

14.4.72 YKRW

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is full analog of the keyword KRWR (see 12.6.43) which is used by Eclipse.
14.4.72. YKRW 2035

14.4.73 ZCORn

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword sets z-coordinate values of block tops, i.e. their depth values. The following
depth values (must be specified 8 Nx Ny Nz numbers) (METRIC: m, FIELD: f t ).
This keyword has an Eclipse compatible analogue ZCORN (see 12.2.9).
Example
ZCORn
36*1524.00
36*1534.00
36*1534.00
36*1544.00
36*1544.00
36*1554.00
In this example depth values are specified. They are specified for grid which size is
3x3x3.
14.4.73. ZCORn 2036

14.4.74 ZVAR

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is used to set layer-by-layer values of some parameter. ZVAR (see 14.4.74)
should be used with the name of data array. The following parameters should be specified:
1. values of a parameter for each layer.
Default:
values of a parameter: 0.
Example
SWL
ZVAR
43*0.375
In the example SWL (see 12.6.27) values in 43 layers of the model are equal to 0.375.
14.4.74. ZVAR 2037

14.4.75 TSUM

INPU FLUI RELA

Section
x GRID INIT RECU
The keyword is used to modify the ratio of sum of transmissibilities to pore volume in
each block. It limits the transmissibilities in selected areas of the reservoir so that reasonable
properties are saved and stability problems of calculation are avoided. This keyword should
be used at the end of the section GRID (see 14.4.1), before the section INIT (see 14.5.1).
1. x -coordinate of the first cell;

2. x -coordinate of the last cell;
3. y-coordinate of the first cell;
4. y-coordinate of the last cell;
5. z-coordinate of the first cell;
6. z-coordinate of the last cell;
1. multiplier of initial value;

2. maximal value. All ratio values which exceed this value will be reduced to this
maximal value.
Default:
x -coordinate of the first cell: 1;
x -coordinate of the last cell: Nx ;
y-coordinate of the first cell: 1;
y-coordinate of the last cell: Ny ;
z-coordinate of the first cell: 1;
z-coordinate of the last cell: Nz ;
multiplier of initial value: 1;
14.4.75. TSUM 2038

Example
TSUM 4* 7 7
1* 0.06
In the example the keyword TSUM (see 14.4.75) is applied to each block of the 7-th
layer, for which ratio of sum of transmissibilities to pore volume exceeds 0.06. For these
blocks this ratio will be set to this value.
14.4.75. TSUM 2039

14.5. INIT Data Section tNavigator-4.2
14.5 INIT Data Section
14.5. INIT Data Section 2040

14.5.1 INIT

INPU FLUI RELA

Section
GRID x INIT RECU
The keyword is a INIT section header and it should be used first.

The keyword has one parameter:
1. EQUI or NEQU:
EQUI - specifies equilibrium initialization;

NEQU - specifies non-equilibrium initialization.
Equilibrium initialization is used by default.
Example
INIT EQUI
14.5.1. INIT 2041

14.5.2 PBVD

INPU FLUI RELA

Section
GRID x INIT RECU
The keyword should be used with the option EQUI (see 14.5.4). It specifies dependence
between depth and oil bubble point in each equilibration region. These data will be used to
calculate initial conditions. This keyword is alternative to the keyword RSVD (see 14.5.3).
1. number of the region, for which data is specifying.
on the next line the table with two columns is specifying:

2. oil bubble point pressure at this depth (METRIC: barsa, FIELD: psia). The data
Default:
if a number of region is absent, then data will be applied to the whole grid.
This keyword has an Eclipse compatible analogue PBVD (see 12.15.4).
Example
PBVD
2000 250
2500 310
3000 350
/
In this example the data for one equilibration region is specified.
14.5.2. PBVD 2042

14.5.3 RSVD

INPU FLUI RELA

Section
GRID x INIT RECU
This keyword specifies solution gas-oil ratio distribution in each equilibration region.
This data is used in initial conditions computations. The keyword should be used with the
option EQUI (see 14.5.4). This keyword is alternative to the keyword PBVD (see 14.5.2). The
1. number of equilibration region to which data applies.
in the next line the table with two columns is specifying:

2. solution gas-oil ratio value at this depth (METRIC: ksm3 /sm3 , FIELD:
msc f /stb). The data should be terminated with a slash /.
Default:
This keyword has an Eclipse compatible analogue RSVD (see 12.15.3).
Example
RSVD
2000 0.06
2500 0.068
3000 0.0735
/
14.5.3. RSVD 2043

14.5.4 EQUI

INPU FLUI RELA

Section
GRID x INIT RECU
The keyword is specifies properties of each equilibration region which are used in calcu-
lation of initial conditions. The following parameters should be specified:
2. pressure at this depth (METRIC: bar , FIELD: psi);
3. depth of gas-oil contact (METRIC: m, FIELD: f t );
4. capillary pressure at depth of gas-oil contact (METRIC: bar , FIELD: psi);
5. depth of water-oil contact (METRIC: m, FIELD: f t );
6. capillary pressure at depth of water-oil contact (METRIC: bar , FIELD: psi).
Default:
depth of gas-oil contact: depth of top cell of reservoir;
capillary pressure at depth of gas-oil contact: 0;
depth of water-oil contact: depth of bottom cell of reservoir;
capillary pressure at depth of water-oil contact: 0.
This keyword has an Eclipse compatible analogue EQUIL (see 12.15.2).
Example
EQUI
2330 237 2* 2320.8 0
2330 237 2* 2335.8 0
14.5.4. EQUI 2044

14.5.5 RVVD

INPU FLUI RELA

Section
GRID x INIT RECU
This keyword specifies for each equilibrium region initial vaporized oil concentration
distribution, used in initial conditions computations. This keyword should be used with the
keyword EQUI (see 14.5.4). The following parameters should be specified:
1. number of equilibration region to which data is applied.
on the next line the table with two columns is specifying:

2. vaporized oil concentration value at this depth (METRIC: sm3 /sm3 , FIELD:
Msc f /stb). The data should be terminated with a slash /.
Default:
This keyword has an Eclipse compatible analogue RVVD (see 12.15.5).
Example
RVVD
2000 0.00060
2500 0.00068
3000 0.000735
/
14.5.5. RVVD 2045

14.5.6 CONS (INIT)

INPU FLUI RELA

Section
GRID x INIT RECU
if option EQUI is used at section definition.

Then this keyword is used to specify initial values of temperature, pressure, gas and
water saturation and components for system, which is in equilibrium. The following

1. [additional parameter] number of equilibration region for which data is
specified;
in the next line:
1. initial temperature for fluid properties (only for black-oil systems) (METRIC:
C , FIELD: F );
2. initial saturation pressure (only for black-oil systems) (METRIC: bar ,

FIELD: psi);
3. initial composition (for EOS-systems only). It can be specified be the keyword
SCMP (see 14.1.10) or by the mole values sum of which is 1.
if option NEQU is used at section definition.

Then this keyword is used to specify initial values of temperature, pressure, gas and
water saturation and components for system, which is not in equilibrium. The following

1. [additional parameter] number of equilibration region for which data is
specified;
in the next line:
1. initial temperature for fluid properties (METRIC: C , FIELD: F );
2. initial pressure (METRIC: bar , FIELD: psi);
3. initial saturation pressure (METRIC: bar , FIELD: psi);
4. initial gas saturation;
5. initial water saturation;
14.5.6. CONS (INIT) 2046

6. initial composition (for EOS-systems only). It can be specified be the key-

word SCMP (see 14.1.10) or by the mole values sum of which is 1.
Default:
number of equilibration region for which data is specified: all regions;
the mole values of initial composition: all values are 0.
initial water saturation: Swc ;
Example
UNIT METR
...
INIT EQUI
...
CONS 1
87 282 /
In the example properties for EOS-system are specified. Initial pressure is 87 , initial
saturation pressure is 282 bars.
14.5.6. CONS (INIT) 2047

14.5.7 GOCX

INPU FLUI RELA

Section
GRID x INIT RECU
The keyword can be used only if option EQUI (see 14.5.4) is used.
The keyword specifies that oil composition at gas-oil contact will be used as gas compo-
sition. The following parameters should be specified:
1. a number of equilibration region to which this data applies.
Default:
this condition will be applied to all blocks of grid.
Example
GOCX
14.5.7. GOCX 2048

14.5.8 GOCY

INPU FLUI RELA

Section
GRID x INIT RECU
The keyword can be used only if option EQUI (see 14.5.4) is used.
The keyword specifies that gas composition at gas-oil contact will be used as oil compo-
sition. The following parameters should be specified:
1. a number of equilibration region to which this data applies.
Default:
this condition will be applied to all blocks of grid.
Example
GOCY 2
In the example it is specified that this condition will be applied to the 2-nd region.
14.5.8. GOCY 2049

14.5.9 SEPA

INPU FLUI RELA

Section
GRID x INIT x RECU
The keyword sets separator properties. The following parameters should be specified:
1. well group to which separator to be applied;

2. flash calculation method:
EOS equation-of-state.
3. separator oil density calculation option:
ZFAC equation-of-state Z-factor is used.
in the next line:
1. separator values table. This table contains the following columns:

(a) temperature of the separator stage;
(b) pressure of the separator stage;
(c) [additional parameter] destination of the liquid of the stage. Possible values:
1 add this fluid to the stock tank total rate;
0 add this fluid to the next stage;
> 0 (index) add this fluid to the later stage with specified index.
If this parameter is specified, then parameter (d) must be specified too.
(d) [additional parameter] destination of the vapor of the stage. This parameter
has the same possible values as parameter (c).
This keyword has an Eclipse compatible analogue SEPCOND (see 12.18.144).
Example
SEPA ALL EOS ZFAC
90 815
80 65
60 14.7
14.5.9. SEPA 2050

14.6. RECUrrent Data Section tNavigator-4.2
14.6 RECUrrent Data Section
14.6. RECUrrent Data Section 2051

14.6.1 RECU

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is a RECU section header and it should be used first.
Example
RECU
14.6.1. RECU 2052

14.6.2 RATE

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword allows to control the rate output (record data on disk with specified time
period).
tNavigator supports the following options of this keyword:
step increment - time period value of information recording;
DAYS - unit of step increment is day;
MONThs - unit of step increment is month;
YEARs - unit of step increment is year;
The keyword has an tNavigator compatible analogue RPTGRAPHD (see 12.17.2).
Example
RATE 1 MONT
In the example record of graphs with period one time per month is configured.
14.6.2. RATE 2053

14.6.3 EFILe

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is used for including file which contains well events.
The EFILe (see 14.6.3) keyword should be preceded by the keyword EFORm (see 14.6.12)
which defines the format of the event data in the specified file.
Name of file should be quoted. After EFILe can be specified only one file name.
No symbols are required to indicate the end of data at the end of file. The end of included
file is regarded as the end of data.
Alternative way of data specification.

Events can be specified in a table in a text of a basic file (without including of a new file
by EFILe). In this case table should be enclosed with keywords ETAB (see 14.6.5) and ENDE
(see 14.6.7) (or /).
In the included file events are specified by the keywords which are sub-keywords of
EFILe (see 14.6.3) (or ETAB correspondingly) and these sub-keywords can not be used inde-
pendently. It is specified in the description of the given keywords.
The keyword has an Eclipse compatible analogue INCLUDE (see 12.1.73).
Example
EFORm WELL 'DD.MM.YYYY' MDL MDU RAD SKIN MULT
EFILe
'..INCLUDE/perf.inc'
EFILe
'..INCLUDE/events.inc'
In the example two event files from INCLUDE directory are included. For file of
connections perf.inc format is specified by the keyword EFORm (see 14.6.12): well name
(WELL), date (in DD.MM.YYYY format), first measured depth (MDL), second measured
depth (MDU), radius (RAD), skin (SKIN), transmissibility multiplier (MULT).
File perf.inc can contain, for example, the following data:
14.6.3. EFILe 2054

Example
6 01.12.1990 PERF 1405.0 1527.0 1* 1* 1*
6 01.12.1990 PERF 1534.0 1542.0 1* 1* 0.5
6 01.12.1990 PERF 1544.0 1550.0 1* 1* 1.5
6 01.12.1990 PERF 1559.0 1569.0 1* 1* 1.5
21 01.12.1990 PERF 1389.0 1536.0 1* 1* 2
21 01.12.1990 PERF 1560.0 1566.0 1* 1* 2
14.6.3. EFILe 2055

14.6.4 TFIL

INPU FLUI RELA

Section
GRID INIT x RECU
This keyword specifies the name of file, from which well trajectories data will be read.
1. name of file which contains well trajectories data.
Filename should be quoted. TFIL (see 14.6.4) can be used to specify well trajectories data
any times you want. Format of including file should be the following:

track_name
X Y Z MD
Example
W_11
159852.000 12038.380 49.560 49.560
159849.080 12032.740 849.320 849.558
159841.110 12013.670 1859.030 1859.546
W_12
159523.520 13485.260 6.010 6.010
159527.510 13470.680 455.750 456.008
159529.850 13395.750 1853.190 1856.006
In the first line well trajectory name is specified, in the following ones coordinates
X,Y, Z of points, through which the well goes and MD - measured depth. In this example
well trajectories W_11 and W_12 are specified.
Case of multi-branch well.
In this case data should be specified as follows:

track_name:branch_number
X Y Z MD
14.6.4. TFIL 2056

Example
'P1'
525 525 2950 1*

525 525 2960 1*
P1:1'
'
525 525 2954 0

575 525 2955 50
725 525 2956 200
Any number of lines can be specified for one branch.
Example
TFIL
"welltrack.txt"
In the example by the keyword TFIL file welltrack.txt with trajectories data is included.
14.6.4. TFIL 2057

14.6.5 ETAB

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is used for specifying the beginning of table which defines well events.
In this case table should be enclosed with keywords ETAB (see 14.6.5) and ENDE (see 14.6.7)
(or /).
The keyword EFORm (see 14.6.12), which precedes the keyword ETAB (see 14.6.5), de-
fines the format of including events.
The data in the table should be terminated with the keyword ENDE (see 14.6.7) or /.

Events can be specified in a file included by the keyword EFILe (see 14.6.3) without using
the keyword ETAB. No symbols are required to indicate the end of data at the end of includ-
ing file. The end of included file is regarded as the end of data.
Inside the ETAB table events are specified by the keywords which are sub-keywords
of ETAB (or EFILe (see 14.6.3) correspondingly) and these sub-keywords can not be used
independently. It is specified in the description of the given keywords.
Example
ETAB
6 01.12.1990 PERF 1405.0 1527.0 1* 1* 1*
6 01.12.1990 PERF 1534.0 1542.0 1* 1* 0
6 01.12.1990 PERF 1544.0 1550.0 1* 1* 0
6 01.12.1990 PERF 1559.0 1569.0 1* 1* 0
6 01.12.1990 PROD HLIQ HWEF BHPT 20
21 01.12.1990 PERF 1389.0 1536.0 1* 1* 2
21 01.12.1990 PERF 1560.0 1566.0 1* 1* 0
ENDE
The keyword ETAB specifies well events table. The keyword EFORm (see 14.6.12),
which precedes the given one, specifies the format of including events PERF (see 14.6.16)
and SQUEeze (see 14.6.17).
14.6.5. ETAB 2058

Supported subkeywords of ETAB section:
MD perforation settings:
Keyword Short description

PERF (see 14.6.16) Open well perforations
SQUE (see 14.6.17) Close well perforations
Open well perforations:

SHUT (see 14.6.27) Shut well
STOP (see 14.6.28) Stop well
OPEN (see 14.6.35) Open well
PROD (see 14.6.18) Set well to producer
INJE (see 14.6.19) Set well to injector
LTAB (see 14.6.20) Set lift table for THP calculations
DREF (see 12.14.34) Set reference depth
PREX (see 14.6.21) Set external radius
XFLO (see 14.6.37) Allow or deny well crossflow
Pressure targets:

BHPT (see 14.6.38) Set BHP target
THPT (see 14.6.39) Set THP target
DRAW (see 14.6.48) Set drawdown target
Well production targets:

OPT (see 14.6.40) Set oil production target
GPT (see 14.6.40) Set gas production target
WPT (see 14.6.40) Set water production target
LPT (see 14.6.40) Set liquid production target
VPT (see 14.6.40) Set voidage production target
14.6.5. ETAB 2059

Injection targets:

OIT (see 14.6.41) Set oil injection target
GIT (see 14.6.41) Set gas injection target
WIT (see 14.6.41) Set water injection target
Historical targets:

HOIL (see 14.6.29) Historical oil rate
HGAS (see 14.6.29) Historical gas rate
HWAT (see 14.6.29) Historical water rate
HLIQ (see 14.6.29) Historical liquid rate
HRES (see 14.6.29) Historical reservoir rate
HBHP (see 14.6.29) Historical BHP
HTHP (see 14.6.29) Historical THP
HWEF (see 14.6.29) Historical well efficiency factor
Other settings:

WEF (see 14.6.42) Well efficiency factor
STRE (see 14.6.43) Specify an injection composition
CWAG (see 14.6.52) Set continuous injection of water and gas
TEMP (see 12.1.60) Injection fluid temperature
WWAG (see 12.18.44) Set well water and gas injection
WFRA (see 14.6.25) Set well fracture
WFRP (see 14.6.26) Set well fracture (It is recommended to use it instead of WFRA)
TRAC (see 14.6.64) Tracer injection
Group production target:

GOPT (see 14.6.44) Set group oil production target
GGPT (see 14.6.44) Set group gas production target
GWPT (see 14.6.44) Set group water production target
GLPT (see 14.6.44) Set group liquid production target
14.6.5. ETAB 2060

Calculation:

RATE (see 14.6.2) Save graphs to disk
Group recycling targets:

RECY (see 14.6.50) Set recycle operation between two well groups
GGRT (see 14.6.51) Set group gas recycle target
GWRT (see 14.6.51) Set group water recycle target
VREP (see 14.6.49) Set up voidage replacement coefficient
GVRT (see 14.6.56) Settings of voidage replacement
Well and group limits:

PLIM (see 14.6.57) Set well lower limits
Limit types:

OIL (description: FLOW (see 14.6.31)) Oil rate
GAS (description: FLOW (see 14.6.31)) Gas rate
WAT (description: FLOW (see 14.6.31)) Water rate
LIQ (description: FLOW (see 14.6.31)) Liquid rate
BHP (see 14.6.34) BHP value
THP (see 14.6.32) THP value
GOR (description: RATI (see 14.6.33)) Gas-oil rate ratio
OGR (description: RATI (see 14.6.33)) Oil-gas rate ratio
WCT (description: RATI (see 14.6.33)) Watercut value
WOR (description: RATI (see 14.6.33)) Water-oil rate ratio
WGR (description: RATI (see 14.6.33)) Water-gas rate ratio
Other options:

HOURS (see 14.6.45) Time accuracy of event
14.6.5. ETAB 2061

14.6.6 TTAB

INPU FLUI RELA

Section
GRID INIT x RECU
This keyword is analogous to the keyword TFIL (see 14.6.4), but, unlike TFIL (see 14.6.4),
in TTAB well trajectories data is specifying in model .data-file. Data input should be ended
by the keyword ENDT (see 14.6.8).
After TTAB (see 14.6.6) well trajectories data should be specified. Format of these data
is analogous to the one described in the keyword TFIL (see 14.6.4).
Example
TTAB
W_11
159852.000 12038.380 49.560 49.560
159849.080 12032.740 849.320 849.558
159841.110 12013.670 1859.030 1859.546
W_12
159523.520 13485.260 6.010 6.010
159527.510 13470.680 455.750 456.008
159529.850 13395.750 1853.190 1856.006
ENDT
This example is equivalent to the example which is written in the description of the
keyword TFIL (see 14.6.4). By the keywords TTAB (see 14.6.6) and ENDT (see 14.6.8) well
trajectories W_11 and W_12 are specified.
14.6.6. TTAB 2062

14.6.7 ENDE

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword ends table input ETAB (see 14.6.5) which specifies well events.
14.6.7. ENDE 2063

14.6.8 ENDT

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword ends well trajectories data input. It is using with the keyword TTAB
(see 14.6.6).
14.6.8. ENDT 2064

14.6.9 HFILe

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is used to include the file which contains well history. Columns of an input
table of well history have to be matched with columns which are specified in the keyword
HFORM.
The HFILe (see 14.6.9) keyword should be preceded by the keyword HFORm (see 14.6.13)
which defines the format of the history data in the specified file.
Name of the file should be quoted. After HFILe only one file name can be specified.
No symbols are required to indicate the end of data at the end of including file. The end of
included file is regarded as the end of data.
Alternative way of specifying data.

History can be specified in a table in a text of a basic file (without addition of a new file by
HFILe). In this case table should be enclosed with keywords HTAB (see 14.6.10) and ENDH
(see 14.6.11) (or /).
In the included file history is specified by the keywords which are sub-keywords of EFILe
(see 14.6.3) (or ETAB correspondingly) and these sub-keywords can not be used indepen-
dently. It is specified in the description of the given keywords.
The keyword has an Eclipse compatible analogue INCLUDE (see 12.1.73).
Example
HFORm WELL 'DD.MM.YYYY' QOIL QLIQ QWATr WEF BHP
/
HFILe
'Well/hist_prod.mrecu'
In the example well history file is included. For well history file hist_prod.mrecu format is
specified by the HFORm (see 14.6.13) keyword: well name (WELL), date (in DD.MM.YYYY
format), oil rate (QOIL), liquid rate (QLIQ), production/injection water rate (QWAT), well
efficiency factor (WEF), bottom hole pressure (BHP).
File hist_prod.mrecu can contain, for example, the following data:
14.6.9. HFILe 2065

Example
6 01.01.1996 115.41 115.41 0 0.13 20
6 01.02.1996 63.44 63.44 0 0.83 20
2132 01.04.2005 0 0 6.03 0.97 300
2132 01.05.2005 0 0 5.34 0.99 300
In the example the oil rate, liquid rate, well efficiency factor and bottom hole pressure
are set for well 6 (production well). Injection water rate, well efficiency factor and bottom
hole pressure are set for well 2132 (injection well).
14.6.9. HFILe 2066

14.6.10 HTAB

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies the beginning of table which contains well history.
In this case table should be enclosed with keywords HTAB (see 14.6.10) and ENDH
(see 14.6.11) (or /).
The keyword HFORm (see 14.6.13), which precedes the keyword HTAB (see 14.6.10),
defines the format of including history. Columns of an input table of well history have to be
matched with columns which are specified in the keyword HFORM.
The data in the table should be terminated with the keyword ENDE (see 14.6.7) or /.

History can be specified in a file included by the HFILe (see 14.6.9) keyword without using
the HTAB keyword. No symbols are required to indicate the end of data at the end of includ-
ing file. The end of included file is regarded as the end of data.
Example
HTAB
6 01.01.1996 115.41 115.41 0 0.13 20
6 01.02.1996 63.44 63.44 0 0.83 20
2132 01.04.2005 0 0 6.03 0.97 300
2132 01.05.2005 0 0 5.34 0.99 300
ENDH
The HTAB keyword specifies a well history table. The HFORm (see 14.6.13) keyword,
which precedes a given one, specifies the format of including history: well name (WELL),
date (in DD.MM.YYYY format), oil rate (QOIL), liquid rate (QLIQ), production/injection
water rate (QWAT), well efficiency factor (WEF), bottom hole pressure (BHP).
In the example oil rate and liquid rate, well efficiency factor and bottom hole pressure
14.6.10. HTAB 2067

14.6.11 ENDH

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword ends table input ETAB (see 14.6.5) which specifies well history.
14.6.11. ENDH 2068

14.6.12 EFORm

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is uses for specifying format of including well events, PERF (see 14.6.16)
and SQUEeze (see 14.6.17) in particular.
The keyword should precede the keywords ETAB (see 14.6.5) or EFILe (see 14.6.3).
The following parameters should be specified (that ones which noted as [additional
parameter] are specified only if these columns are in events table):
1. WELL [additional parameter] well name will be specified in every line;
2. date format day DD, month MM or MMM (two-letter of three-letter notation for
month), year YYYY. Day, month and year can be specified in any order with points or
colons as delimiters. For example, DD.MM.YYYY;
3. MDL [additional parameter] first measured depth (METRIC: m, FIELD: f t );
4. MDU [additional parameter] second measured depth (METRIC: m, FIELD: f t );
5. RAD [additional parameter] well radius (METRIC: m, FIELD: f t );
6. DIAM [additional parameter] well diameter (METRIC: m, FIELD: f t );
7. SKIN [additional parameter] skin value;
8. MULT [additional parameter] transmissibility multiplier (METRIC: cP rm3 /day

bar , FIELD: cP rb/day psi).
Example
ETAB
6 01.12.1990 PERF 1405.0 1527.0 1* 1* 1*
6 01.12.1990 PERF 1534.0 1542.0 1* 1* 0
6 01.12.1990 PERF 1544.0 1550.0 1* 1* 0
6 01.12.1990 PERF 1559.0 1569.0 1* 1* 0
6 01.12.1990 PROD HLIQ HWEF BHPT 20
21 01.12.1990 PERF 1389.0 1536.0 1* 1* 2
21 01.12.1990 PERF 1560.0 1566.0 1* 1* 0
ENDE
14.6.12. EFORm 2069

The keyword ETAB specifies well events table. The keyword EFORm (see 14.6.12), which
precedes ETAB, specifies the format of including events PERF (see 14.6.16) and SQUEeze
(see 14.6.17): well name (WELL), date (in DD.MM.YYYY format), first measured depth
(MDL), second measured depth (MDU), radius (RAD), skin value (SKIN), transmissibility
multiplier (MULT).
14.6.12. EFORm 2070

14.6.13 HFORm

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is uses to specify the format of including well history.

The keyword should precede the keyword HTAB (see 14.6.10) or the keyword HFILe
(see 14.6.9).
The following parameters should be specified (the ones which noted as [additional pa-
rameter] are specified only if these columns are in history table; its can be specified in any
order corresponding with table columns):
1. WELL [additional parameter] well name will be specified in every line;
2. day DD, month MM or MMM (two-letter of three-letter notation for month), year
YYYY. Day, month and year can be specified in any order with points or colons as
delimiters. For example, DD.MM.YYYY;
3. QOIL [additional parameter] historical value of oil rate (METRIC: sm3 /day,
FIELD: stb/day),
4. QWAT [additional parameter] historical value of water rate (METRIC: sm3 /day,
FIELD: stb/day),
5. QLIQ [additional parameter] historical value of liquid rate (METRIC: sm3 /day,
FIELD: stb/day),
6. QGAS [additional parameter] historical value of gas rate (METRIC: sm3 /day,
FIELD: Msc f /day),
7. COIL [additional parameter] historical value of oil total (METRIC: sm3 , FIELD:
stb),
8. CWAT [additional parameter] historical value of water total (METRIC: sm3 ,
FIELD: stb),
9. CLIQ [additional parameter] historical value of liquid total (METRIC: sm3 , FIELD:
stb),
10. CGAS [additional parameter] historical value of gas total (METRIC: sm3 , FIELD:
Msc f ),
11. QWIN [additional parameter] historical value of water injected rate (METRIC:
sm3 /day, FIELD: stb/day),
14.6.13. HFORm 2071

12. CWIN [additional parameter] historical value of water injected total (METRIC:
sm3 , FIELD: stb),
13. QGIN [additional parameter] historical value of gas injected rate (METRIC:
sm3 /day, FIELD: Msc f /day),
14. CGIN [additional parameter] historical value of gas injected total (METRIC: sm3 ,
FIELD: Msc f ),
15. THP [additional parameter] historical value of tubing head pressure (METRIC:
barsa, FIELD: psia);
16. BHP [additional parameter] historical value of bottom hole pressure (METRIC:
barsa, FIELD: psia);
17. WEFA [additional parameter] historical value of efficiency factor.
QWAT and QGAS can be used for specifying the water/gas rate as well as water/gas
injection (see an example below). Rate is for production wells, injection is for injection
wells. It is possible only if one of the keywords QWIN or QGIN is absent. If QWIN and
QWAT are used contemporary: QWIN values of water injection only, QWAT values of
water rate only.
Example
HTAB
6 01.01.1996 115.41 115.41 0 0.13 20
6 01.02.1996 63.44 63.44 0 0.83 20
2132 01.04.2005 0 0 6.03 0.97 300
2132 01.05.2005 0 0 5.34 0.99 300
ENDH
The keywordHTAB specifies well history table. The keyword HFORm (see 14.6.13),
which precedes HTAB, specifies the format of including data: well name (WELL), date (in
DD.MM.YYYY format), oil rate (QOIL), liquid rate (QLIQ), production/injection water rate
(QWAT), well efficiency factor (WEF), bottom hole pressure (BHP).
In the example oil rate and liquid rate, well efficiency factor and bottom hole pressure
14.6.13. HFORm 2072

14.6.14 EUNIts

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies the units for the well events specified by the keyword ETAB
(see 14.6.5) or the keyword EFILe (see 14.6.3).
The following parameters should be specified (METRIC: m, FIELD: f t ):
1. Units for measured depth (METRIC: MET Res, FIELD: FEET );
2. Units for radius or diameter (METRIC: MET Res or CMS (meters or centimeters),
FIELD: FEET or INCHes (feet or inches)).
Example
EUNIts 1* CMS
ETAB
6 01.12.1990 PERF 1405.0 1527.0 16 1* 1*
6 01.12.1990 PERF 1534.0 1542.0 16 1* 0
In the example it is specified that the well diameters will be entered in CMS. The value
of radius is 16 centimeters for well 6.
14.6.14. EUNIts 2073

14.6.15 HUNIts

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies the units for the well history specified by the keyword HTAB
(see 14.6.10) or the keyword HFILe (see 14.6.9).
1. units for liquid rate METRIC: sm3 /day (or ksm3 /day), FIELD: stb/day (or
Mstb/day);
2. units for gas rate METRIC: sm3 /day (or ksm3 /day), FIELD: sc f /day or
(Msc f /day);
3. units for liquid total METRIC: ksm3 (or Msm3 ), FIELD: Mstb (or MMstb);
4. units for gas total METRIC: ksm3 (or Msm3 ), FIELD: Msc f (or MMsc f );
5. units for pressure METRIC: bar (or barg), FIELD: psia (or psig).
Default:
units for liquid rate METRIC: sm3 /day, FIELD: stb/day;
units for gas rate METRIC: sm3 /day, FIELD: sc f /day;
units for liquid total METRIC: ksm3 , FIELD: Mstb;
units for gas total METRIC: ksm3 , FIELD: Msc f ;
units for pressure METRIC: bar , FIELD: psia.
Example
HUNI
stb/day Mscf/day 2* psia
In the example the keyword HUNI sets units for historical data. Unit for liquid rate is
stb/day, unit for gas rate is Msc f /day, units for liquid and gas total are set by default (Mstb
and Msc f correspondingly), unit for pressure is psia.
14.6.15. HUNIts 2074

14.6.16 PERF

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is used to open completions. The keyword can be used only inside the table
ETAB (see 14.6.5) or inside the file EFILe (see 14.6.3).
Specified parameters have to be matched with format specified by the keyword EFORm
(see 14.6.12).
The following parameters should be specified (the ones which noted as [additional param-
eter] are specified only if it is necessary):
1. Well name [additional parameter] well name is in the line, if parameter WELL is in
EFORm. Otherwise well name can be specified separately in line, which precedes the
line that specify event;
2. Perforation date (date format should correspond to the format specified in EFORm. For
example, DD.MM.YYYY);
3. The keyword PERF which specifies event;
4. MDL first measured depth (METRIC: m, FIELD: f t ) (Default: is considered to be

specified in measured depth along trajectory MD);
5. MDU second measured depth (METRIC: m, FIELD: f t ) (Default: is considered to

be specified in measured depth along trajectory MD);
6. RAD [additional parameter] well radius (METRIC: m, FIELD: f t );
7. DIAM [additional parameter] well diameter (METRIC: m, FIELD: f t );
8. SKIN [additional parameter] skin value;
9. MULT [additional parameter] conductivity multiplier (METRIC: cP rm3 /day

bar , FIELD: cP rb/day psi).
10. CLOSE [additional parameter] completion will be closed (alternative is SQUEeze

(see 14.6.17));
11. TVD [additional parameter] MDL and MDU are specified in absolute depth (Default:
is considered to be specified in measured depth along trajectory MD);
12. ZONE [additional parameter] MDL and MDU are specified in block numbers (De-
fault: is considered to be specified in measured depth along trajectory MD).
14.6.16. PERF 2075

The keyword is analogous to an Eclipse keyword COMPDAT (see 12.18.6).
Example
ETAB
6 01.12.1990 PERF 1405.0 1527.0 1* 1* 1*
21 01.12.1990 PERF 1389.0 1536.0 1* 1* 2
G1 01.01.2012 PERF 1 20 0.1 0 1 ZONE
P3 01.01.2012 PERF 1 20 0.1 0 1 ZONE
ENDE
The keyword ETAB specifies well events table. The keyword EFORm (see 14.6.12), which
precedes ETAB, specifies the format of including events PERF and SQUEeze (see 14.6.17):
well name (WELL), date (in DD.MM.YYYY format), first measured depth (MDL), second
measured depth (MDU), radius (RAD), skin value (SKIN), conductivity multiplier (MULT).
For the wells G1 and P3 perforated intervals are specified in block numbers (instead of
MD). Perforations are from 1st to 20th layer in Z-direction (additional parameter ZONE is
specified).
14.6.16. PERF 2076

14.6.17 SQUEeze

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is used to close completions. The keyword can be used only inside the table
ETAB (see 14.6.5) or inside the file EFILe (see 14.6.3).
(see 14.6.12).
The following parameters should be specified (the ones which noted as [additional param-
eter] are specified only if it is necessary):
1. Well name [additional parameter] well name is in the line if parameter WELL is in
line specifying event;
2. Perforation closing date (date format should correspond to the format specified in
EFORm. For example, DD.MM.YYYY);
3. The keyword SQUEeze which specifies event;
4. MDL first measured depth (METRIC: m, FIELD: f t ) (Default: is considered to be

specified in measured depth along trajectory MD);
5. MDU second measured depth (METRIC: m, FIELD: f t ) (Default: is considered to

be specified in measured depth along trajectory MD);
6. TVD [additional parameter] MDL and MDU are specified in absolute depth (Default:
is considered to be specified in measured depth along trajectory MD);
7. ZONE [additional parameter] MDL and MDU are specified in block numbers (De-
fault: is considered to be specified in measured depth along trajectory MD).
The keyword is analogous to an Eclipse keyword COMPDAT (see 12.18.6).
Example
ETAB
6 01.12.1990 SQUE 1405.0 1527.0
P3 01.01.2012 SQUE 1 20 ZONE
ENDE
14.6.17. SQUEeze 2077

The keyword ETAB specifies well events table. The keywordEFORm (see 14.6.12), which
precedes ETAB, specifies the format of including events PERF and SQUEeze (see 14.6.17):
well name (WELL), date (in DD.MM.YYYY format), first measured depth (MDL), second
measured depth (MDU), radius (RAD), skin value (SKIN), conductivity multiplier (MULT).
For the well P3 closing perforation interval is specified in block numbers (instead of MD).
Perforation from 1st to 20th layer along Z-direction will be closed (additional parameter
ZONE is specified).
14.6.17. SQUEeze 2078

14.6.18 PROD

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword changes well status to production. The following parameters should be
specified:
1. well name [additional parameter] well name in line, if in the keyword EFORm
parameter WELL was specified. Otherwise, well name can be specified in previous
line;
2. date of status changing (date format should correspond to specified one in the keyword
EFORm (see 14.6.12). For example, DD.MM.YYYY);
3. the keyword PROD which defines event.
This keyword has an Eclipse compatible analogue WCONPROD (see 12.18.34).
Example
W_1 01.02.2002 PROD
W_1 well status will be changed to production at 01.02.2002.
14.6.18. PROD 2079

14.6.19 INJE

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword changes well status to injection. The following parameters should be
specified:
line;
3. the keyword INJE which defines event.
This keyword has an Eclipse compatible analogue WCONPROD (see 12.18.34).
Example
W_1 01.08.2006 INJE
W_1 well status will be changed to injection at 01.08.2006.
14.6.19. INJE 2080

14.6.20 LTAB

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets lift table for THP calculations. The keyword can be used only inside
the table ETAB (see 14.6.5) or inside the file EFILe (see 14.6.3).
(see 14.6.12).
line;
3. the keyword LTAB which defines event.
4. table name. If lift tables are specified using the keyword VFPPROD or VFPINJ, then
table should be respectively named as tubeprodXXX or tubeinjeXXX, where XXX is
the lift table number.
Example
ETAB
P-1 01.01.2014 LTAB tubeprod1
In the example for well P-1 lift table tubeprod1 is set.
14.6.20. LTAB 2081

14.6.21 PREX

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets well external radius. It should be used only after the keyword WELL
(see 13.9.6). The following parameters should be specified:
1. well external radius (re ) (METRIC: m, FIELD: f t );
Default:
well external radius - equivalent radius ro .
Example
UNITs METRic
...
130R 01.01.1995 PREX 4
In the example the keyword PREX (see 14.6.21) sets external radius for well 130R. Radius
is equal to 4 meters.
14.6.21. PREX 2082

14.6.22 P-RE

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is equivalent to the keyword PREX (see 14.6.21).
14.6.22. P-RE 2083

14.6.23 WELL

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword defines well and sets parameters of it control mode. The following param-
1. well name;
2. well type:
PROD - producer;
INJE - injector;
STOP - stopped;
SHUT - shut.
3. well limits (name of priority well limit):
for producing wells - OIL, WAT, GAS, LIQU or RESV;

for injecting - WAT, GAS;
historical rate limits - HOIL, HGAS, HWAT HLIQ, HRES;
historical pressure limits - HBHP, TBHP.
4. flow limit: if the only value is specified, then it should be the value of priority flow.
If values for all flows are specified, then one of them will be chosen according to
specified priority value (for liquid: METRIC: sm3 /day, FIELD: stb/day; for gas:
METRIC: 103 m3 /day, FIELD: msc f /day);
5. pressure limit: PLIM - minimal pressure for producing wells or maximal for injecting
(METRIC: bar , FIELD: psi);
6. [additional parameter] comments. They should be used to the left of sign =. Usually
first sign of equation means rate, second means pressure. But if a string starts with letter
Q and there are no whitespaces by both sides of =, then the value after it means
rate. The same way, if a string starts with P, the the value means pressure;
7. pressure type at parameter 5:
BHP - bottom hole pressure;

name of table which is defined by the keyword TUBI (see 14.6.30) - tubing head
pressure.
14.6.23. WELL 2084

8. AND - is using to set injection of 2 fluids (WWAG (see 12.18.44)). Fluid signed first
will be injected first;
9. HWEF - historical well efficiency factors are using.
Example
WELL 232 PROD HLIQ PMIN=110 QOIL=100 HWEF /
In the example for producing well 232 pressure and rate limits set up, which are equal to
110 bar and 100 sm3 /day correspondingly. Priority value is HLIQ. It is also specified that
historical well efficiency factors will be used.
14.6.23. WELL 2085

14.6.24 WWAG

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies that injecting fluid will be changing periodically (water or gas).
Fluid which will be injected first is defined by the keyword WELL (see 13.9.6). The following
1. well name;
2. time period of injection of the first fluid (METRIC: days, FIELD: days);
3. time period of injection of the second fluid (METRIC: days, FIELD: days).
The keyword has the analogue WWAG (see 12.18.44), with is used in tNavigator.
Example
WWAG 30311 31 30
In the example the keyword WWAG (see 12.18.44) specifies periods of gas and water
injection for well 30311, which are equal to 31 and 30 days correspondingly.
14.6.24. WWAG 2086

14.6.25 WFRA

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is used for specifying hydraulic fracture. The keyword can be used only
inside the table ETAB (see 14.6.5) or inside the file EFILe (see 14.6.3).
Recommendation.
It is recommended in tNavigator to simulate hydraulic fracture with the keyword WFRP
(see 14.6.26) instead of WFRA (see 14.6.25). The keyword WFRP (see 14.6.26) is prepared
to use in MORE models and hybrid models (see 11.3). This keyword is analogous to the
keywords WFRACP (see 12.18.124), WFRAC (see 12.18.122) COMPFRAC (see 12.18.126).
parameter] are specified if it is necessary):
1. Well name [additional parameter] well name should be specified in the line if in
EFORm there is WELL parameter. Else well name can be entered in the line preceding
the line with event;
2. Date of hydraulic fracture (date format should correspond to the format specified by
3. The keyword WFRA which specifies event;
4. Azimuth angle (from 0 to 360 ). Angle of fracture in the XY-plane (measured from
the positive x-axis towards the positive y-axis);
5. Number of the first layer in Z-direction containing vertical fracture;
6. Number of the last layer in Z-direction containing vertical fracture;
7. Half-length of fracture from well (METRIC: m, FIELD: f t ); left and right half-lengths
of fracture are the same;
8. Permeability of fracture (mD) (parameters 8 and 9 or parameter 10 should be specified);
9. Width of fracture (METRIC: m, FIELD: f t ) (parameters 8 and 9 or parameter 10

should be specified);
10. Conductivity of fracture (METRIC: mD m, FIELD: mD f t ) (parameters 8 and 9 or

parameter 10 should be specified);
14.6.25. WFRA 2087

11. Fracture time constant (days);
12. Lower measured depth for horizontal fracture case;
13. Upper measured depth for horizontal fracture case;
14. Type of fracture: V (vertical fracture type) or H (horizontal fracture type);
15. [additional parameter] horizontal well fractures connect to a specified range of layers
type LAYEr, well fractures connect to a specified range of depths type DEPTh;
16. [additional parameter] Lower layer or depth for use with LAYEr or DEPTh options,
respectively, in parameter 13 (for horizontal fracture);
17. [additional parameter] Upper layer or depth for use with LAYEr or DEPTh options,
respectively, in parameter 13 (for horizontal fracture);
Example
P3 01.01.2012 WFRA 90 2* 100 100000 0.004 1* 1095 /
P5 01.01.2012 WFRA 90 2* 100 100000 0.004 1* 1095 /
N4 01.01.2012 WFRA 90 2* 100 100000 0.02 1* 50000 /
14.6.25. WFRA 2088

14.6.26 WFRP

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is used for specifying hydraulic fracture.

The keyword can be used only inside the table ETAB (see 14.6.5) or inside the file EFILe
(see 14.6.3).
The keyword can be used in MORE models and hybrid models (see 11.3). This keyword is
analogous to the keywords WFRACP (see 12.18.124), WFRAC (see 12.18.122) COMPFRAC
(see 12.18.126).
parameter] are specified if it is necessary):
1. Well name [additional parameter] well name should be specified in the line if in
EFORm there is WELL parameter. Else well name can be entered in the line preceding
the line with event;
2. Date of hydraulic fracture (date format should correspond to the format specified by
3. The keyword WFRP which specifies event;
4. i1 first connection coordinate in X direction (coordinates of connection of well

fractures to blocks should be specified by parameters 4-9 or depths should be specified
by parameters 10-11);
5. j1 first connection coordinate in Y direction (coordinates of connection of well

6. k1 first connection coordinate in Z direction (coordinates of connection of well


is perpendicular to the well bore, only one connection should be specified, i.e. i1 = i2
14.6.26. WFRP 2089

(coordinates of connection of well fractures to blocks should be specified by parameters

4-9 or depths should be specified by parameters 10-11);
8. j2 last connection coordinate in Y direction. If hydraulic fracture is in the plane

that is perpendicular to the well bore, only one connection should be specified, i.e.
j1 = j2 (coordinates of connection of well fractures to blocks should be specified by
parameters 4-9 or depths should be specified by parameters 10-11);
9. k2 last connection coordinate in Z direction. If hydraulic fracture is in the plane

that is perpendicular to the well bore, only one connection should be specified, i.e.
k1 = k2 (coordinates of connection of well fractures to blocks should be specified by
parameters 4-9 or depths should be specified by parameters 10-11);
10. fracture lower depth (METRIC: m, FIELD: f t ) (coordinates of connection of well

11. fracture upper depth (METRIC: m, FIELD: f t ) (coordinates of connection of well

12. azimuth angle (from 0 to 360 ). Azimuth angle in tNavigator - is the angle between
positive direction of X-axis and fracture right half-length l2 (see examples with pic-
tures of various angles in the description of the keyword WFRACP (see 12.18.124)).
13. Zenith angle (from 0 to 90 );
angle is 0, this half length will be directed to the left from the well bore);
angle is 0, this half length will be directed to the right from the well bore);
16. h1 fracture height in some direction from the well bore (METRIC: m, FIELD: f t );
17. h2 fracture height in another direction from the well bore (METRIC: m, FIELD:
f t );
18. Fracture width (METRIC: m, FIELD: f t );
19. Proppant properties (mD). In this case proppant will have constant permeability
20. Dependence between fracture permeability and flown phase volume or time. One of
the following parameters should be specified:
14.6.26. WFRP 2090

specifies the washing out of the proppant from the fracture. (Keywords FLOW-
Phase volume (m3 ) (the next parameters specifies a phase), when this volume
DT
F(T ) = e days
where:
D current date;

PERM proppant can be estimated from fracture conductivity and width;
14.6.26. WFRP 2091

Default:
zenith angle 0 ;
flow function name not defined; there is no dependence from flow;
Example
G7 01.01.2012 WFRP 1* 1* 1* 1* 1* 1* 1* 1* 90 0 100 100 0 0
0.02 6300 1095 TIME 1* 6*
G1 01.01.2012 WFRP 1* 1* 1* 1* 1* 1* 2949 2951 90 0 100 100

0 2 0.02 6300 1095 TIME 1* 6*
G1 01.01.2012 WFRP 1* 1* 1* 1* 1* 1* 3114 3117 90 0 100 100

0 2 0.02 5000 10000 1* 1* 6*
G1 01.01.2012 WFRP 1* 1* 1* 1* 1* 1* 3474 3476 0 0 200 100

5 0 0.02 4000 10000 1* 1* 6*
N4 01.01.2012 WFRP 11 11 4 11 11 7 1* 1* 0 0 100 100 0 0 0.02

2000 1* TIME 1* 6*
In the example hydraulic fracture on well N4 is specified via its connection coordinates.
On well G7 all well perforation intervals are taken by default. On well G1 3 hydraulic
fractures are specified via depth.
14.6.26. WFRP 2092

14.6.27 SHUT

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is used to shut well. The keyword can be used only inside the table ETAB
(see 14.6.5) or inside the file EFILE (see 14.6.3).
1. well name [additional parameter] well name is in the line if parameter WELL is in
2. shut well date (date format should correspond to the format specified in EFORm. For
3. the keyword SHUT.
The keyword has an Eclipse compatible analogue WELOPEN (see 12.18.107).
Example
ETAB
6 01.12.1990 SHUT
ENDE
14.6.27. SHUT 2093

14.6.28 STOP

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is used to stop well. The keyword can be used only inside the table ETAB
(see 14.6.5) or inside the file EFILE (see 14.6.3).
1. well name [additional parameter] well name is in the line if parameter WELL is in
2. shut well date (date format should correspond to the format specified in EFORm. For
3. the keyword STOP.
The keyword has an Eclipse compatible analogue WELOPEN (see 12.18.107).
Example
ETAB
6 01.12.1990 STOP
ENDE
14.6.28. STOP 2094

14.6.29 HOIL / HGAS / HWAT / HLIQ / HRES / HBHP / HTHP / HWEF

INPU FLUI RELA

Section
GRID INIT x RECU
These keywords specify historical data targets. They are should be used after the keyword
ETAB (see 14.6.5) or in a file EFILE (see 14.6.3).
HOIL - historical oil rate target;
HGAS - historical gas rate target;
HWAT - historical water rate target;
HLIQ - historical liquid rate target;
HRES - historical reservoir rate target;
HBHP - historical bottom hole pressure value target BHP (see 14.6.34);
HTHP - historical tubing head pressure value target THP (see 14.6.32);
HWEF - historical well efficiency factor target.
For keywords HOIL, HGAS, HWAT and HLIQ option OFF is available. Applying this
option stops target limiting at specified time step.
Historical data include by the keyword HTAB (see 14.6.10) or HFIL (see 14.6.9).
Analogous for these keywords is the keyword WCONHIST (see 12.18.35), which is used
by Eclipse.
Example
ETAB
607 01.11.1999 HWAT HOIL HWEF 607 01.12.1999 HWAT OFF
In the example the keywords HWAT (see 14.6.29), HOIL (see 14.6.29) and HWEF
(see 14.6.29) 01.11.1999 specify targets, corresponding to these keywords, for well 607.
01.12.1999 limiting by historical water rate target is stopped.
14.6.29. HOIL / HGAS / HWAT / HLIQ / HRES / HBHP / HTHP / HWEF 2095
14.6.30 TUBI

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword indicates an input of tubing head pressure table. The following parameters
1. table name;
2. reference depth for values of bottom hole pressures, which are specified in the table
(METRIC: m; FIELD: f t );
3. format of input table:
PACK - for all values of RATI (see 14.6.33) one array of BHP (see 14.6.34) values
will be inputed;
LONG - subkeyword BHP (see 14.6.34) will be specified for each ratio value
specified by the keyword RATI (see 14.6.33).
Also after the keyword TUBI one or several keywords, which define values of variables
in the table, should be specified: FLOW (see 14.6.31), THP (see 14.6.32), RATI (see 14.6.33)
and BHP (see 14.6.34).

Default:
reference depth: value of depth, which defined by the keyword DATUm (see 14.4.5);
format of input table: PACK.
14.6.30. TUBI 2096

Example
UNITS METRic
...
TUBI TAB_43 3589 LONG
FLOW GAS
5 25 60 100 /
THP
15 35 75 /
RATI WGR
0 0.05 0.1 /
BHP WGR 0
18 19 23 30 /
42 43 45 49 /
93 93 94 96 /
BHP WGR 0.05
67 31 28 34 /
99 61 54 55 /
15 12 10 10 /
BHP WGR 0.1
66 32 30 36 /
98 63 56 58 /
156 122 112 111 /
In the example the keyword TUBI (see 14.6.30) specifies table TAB_43. Reference depth
is 3589 m. Each subtable contains values of bottom hole pressure for each rate value (FLOW
(see 14.6.31)). The first column of the table corresponds to the first rate value, the second
column corresponds to the second value and so on. The same way, the first line of the table
corresponds to the first value of tubing head pressure, the second line corresponds to the
second value and so on. Such subtable is set for each WGR value. So, 4 3 3 = 36 values
should be specified in total.
14.6.30. TUBI 2097

Example
UNITS METRic
...
TUBI TAB_43 3589
FLOW GAS
5 25 60 100 /
THP
15 35 75 /
RATI WGR
0 0.05 0.1 /
BHP
18 19 23 30 /
42 43 45 49 /
93 93 94 96 /
67 31 28 34 /
99 61 54 55 /
15 12 10 10 /
66 32 30 36 /
98 63 56 58 /
156 122 112 111 /
This example is equivalent to the previous one, but in this example option PACK is used
to specify array of BHP (see 14.6.34) values.
14.6.30. TUBI 2098

14.6.31 FLOW

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies fluid rates for THP-table (TUBI (see 14.6.30)). The keyword FLOW
should be used after the keyword TUBI (see 14.6.30). The following parameters should be
specified:
1. fluid type:
OIL - oil rates will be specified (METRIC: sm3 /day; FIELD: stb/day);
GAS - gas rates will be specified (METRIC: ksm3 /day; FIELD: msc f /day);
WAT - water rates will be specified (METRIC: sm3 /day; FIELD: stb/day);
LIQ - liquid rates will be specified (METRIC: sm3 /day; FIELD: stb/day).
on the next line:
1. rate values. This values must be increasing. The data should be terminated with a
slash /.
Default:
fluid type: OIL.
Example
UNITS METRic
...
TUBI TAB_43 3.58953E+003 LONG
FLOW GAS
5 25 60 100 /
THP
15 /
RATI WGR
0 0.05 0.1 /
BHP WGR 0
18 19 23 30 /
BHP WGR 0.05
67 31 28 34 /
BHP WGR 0.1
66 32 30 36 /
14.6.31. FLOW 2099

In the example 4 values of gas rate are specified.
14.6.31. FLOW 2100

14.6.32 THP

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies values of tubing head pressure for the keyword TUBI (see 14.6.30).
The keyword THP should be used after the keyword TUBI (see 14.6.30). The following
1. values of THP (METRIC: bar , FIELD: psi). The data should be terminated with a
slash /.
Default: If subkeyword THP (see 14.6.32) is not specified, then the pressure value, which
was specified at WELL (see 13.9.6), is considered as the only value of THP.
Example
UNITS METRic
...
FLOW GAS
5 25 60 100 /
THP
15 /
RATI WGR
0 0.05 0.1 /
BHP WGR 0
18 19 23 30 /
BHP WGR 0.05
67 31 28 34 /
BHP WGR 0.1
66 32 30 36 /
In the example one value of THP is specified. It is equal to 15 bar .
14.6.32. THP 2101

14.6.33 RATI

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies fluid rate ratios for tubing head pressure table (the keyword TUBI
(see 14.6.30)). The keyword RATI should be used only after the keywords TUBI (see 14.6.30),
FLOW (see 14.6.31) and THP (see 14.6.32). The following parameters should be specified:
1. ratio type:
WOR - water-oil ratio (METRIC: sm3 /sm3 ; FIELD: stb/stb);
WCT (WCUT) - watercut (METRIC: sm3 /sm3 ; FIELD: stb/stb);
WGR - water-gas ratio (METRIC: sm3 /ksm3 ; FIELD: stb/Msc f );
GOR - gas-oil ratio (METRIC: ksm3 /sm3 ; FIELD: Msc f /stb);
GLR - gas-liquid ratio (METRIC: ksm3 /sm3 ; FIELD: Msc f /stb);
OGR - oil-gas ratio (METRIC: sm3 /ksm3 ; FIELD: stb/Msc f ).
on the next line:
1. ratio values. They should be increasing. The data should be terminated with a
slash /.
Example
UNITS METRic
...
FLOW GAS
5 25 60 100 /
THP
15 /
RATI WGR
0 0.05 0.1 /
BHP WGR 0
18 19 23 30 /
BHP WGR 0.05
67 31 28 34 /
BHP WGR 0.1
66 32 30 36 /
In the example ratio type WGR is used.
14.6.33. RATI 2102

14.6.34 BHP

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies the bottom hole pressure table. This keyword should be used af-
ter the keyword TUBI (see 14.6.30) and all of its subkeywords (FLOW (see 14.6.31), THP
(see 14.6.32) and RATI (see 14.6.33)).

1. type of i-th ratio;
2. value of i-th ratio;
3. in the following lines bottom hole pressure table is specified. (METRIC: bar , FIELD:
psi).
BHP table is specified for each ratio value, which are specified via the keyword RATI
(see 14.6.33). Each line of the table should be ended by /.
Example
UNITS METRic
...
FLOW GAS
5 25 60 100 /
THP
15 /
RATI WGR
0 0.05 0.1 /
BHP WGR 0
18 19 23 30 /
BHP WGR 0.05
67 31 28 34 /
BHP WGR 0.1
66 32 30 36 /
In the example BHP tables are specified by the keyword BHP (see 14.6.34). These tables
are specified for each ratio value (RATI (see 14.6.33)). The number of columns of each table
is equal to the number of values of parameter FLOW (see 14.6.31). The number of lines is
equal to the number of values of parameter THP (see 14.6.32).
14.6.34. BHP 2103

14.6.35 OPEN (RECU)

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is used to open a well. This keyword should be used inside ETAB
(see 14.6.5) table or inside EFILE (see 14.6.3) file to specify well event.
1. well name [additional parameter] well name, if in EFORm (see 14.6.12) parameter
WELL was specified. Otherwise, well name can be specified in previous line;
2. date of well opening (date format should correspond to format which is specified via
3. the keyword OPEN.
This keyword has an Eclipse compatible analogue WELOPEN (see 12.18.107).
Example
ETAB
6 01.12.1990 OPEN
ENDE
In the example by the keyword OPEN well 6 is opened on 01.12.1990.
14.6.35. OPEN (RECU) 2104

14.6.36 DREF

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies a reference depth for wells bottom hole pressure. This keyword
should be used inside ETAB (see 14.6.5) table or inside EFILE (see 14.6.3) file to specify
well event.
If the keyword DREF is not specified, then the value of DATU (see 14.4.5) will be used.
1. reference depth of BHP (METRIC: m, FIELD: f t ).
This keyword is analogous to the 5-th parameter of the keyword WELSPECS (see
12.18.3), that is used by Eclipse.
Example
UNITs METRic
...
ETAB
6 01.12.1990 DREF 1360
...
ENDT
In the example for well 6 reference depth of BHP is specified. It is equal to 1360 m.
14.6.36. DREF 2105

14.6.37 XFLO

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword allows or denies possibility of crossflow inside a well. This keyword should
be used inside ETAB (see 14.6.5) table or inside EFILE (see 14.6.3) file to specify well event.
1. ON or OFF:
ON - crossflow inside a well is allowed;

OFF - crossflow inside a well is denied (i.e., perforation interval is one-sided).
This keyword is analogous to the 10-th parameter of the keyword WELSPECS (see
Example
ETAB
6 01.12.1990 XFLO ON
...
ENDE
In the example the crossflow inside a well 6 will be allowed on 01.12.1990.
14.6.37. XFLO 2106

14.6.38 BHPT

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets target for the value of bottom hole pressure. This keyword should be
used inside ETAB (see 14.6.5) table or inside EFILE (see 14.6.3) file to specify well event.
1. pressure value (METRIC: bar , FIELD: psi).
This keyword is analogous to the 9-th parameter of the keyword WCONPROD (see
Example
ETAB
93-2 01.07.2014 BHPT 225.0
...
ENDT
In the example the target value for bottom hole pressure for the well 93-2 is set on
01.07.2014.
14.6.38. BHPT 2107

14.6.39 THPT

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets target for the value of tubing head pressure. This keyword should be
1. pressure value (METRIC: bar , FIELD: psi).
This keyword is analogous to the 10-th parameter of the keyword WCONPROD (see
Example
UNIT METR
...
ETAB
P10 09.06.2021 THPT 30
ENDT
In the example the target value for tubing head pressure for the well P10 is set on
09.06.2021. This value is equal to 30 bar .
14.6.39. THPT 2108

14.6.40 OPT / WPT / GPT / LPT / VPT

INPU FLUI RELA

Section
GRID INIT x RECU
These keywords set targets for rates of oil (OPT), gas (GPT), water (WPT), liquid (LPT)
and voidage (at formation conditions) (VPT) correspondingly. These keywords should be used
inside ETAB (see 14.6.5) table or inside EFILE (see 14.6.3) file to specify well event.
1. rate value. Units:
if OPT / WPT / LPT is specified - METRIC: sm3 /day, FIELD: stb/day;

if GPT is specified - METRIC: sm3 /day, FIELD: Msc f /day;
if VPT is specified - METRIC: rm3 /day, FIELD: rb/day.
Analogous for this keywords are the 4-th, 5-th, 6-th, 7-th and 8-th parameters of the
keyword WCONPROD (see 12.18.34), which is used by Eclipse.
Example
A1 17/Dec/2013 OPT 2800
In the example the target for oil rate for the well A1 is set on 17.12.2013. It is equal to
2800 stb/day.
14.6.40. OPT / WPT / GPT / LPT / VPT 2109

14.6.41 OIT / GIT / WIT

INPU FLUI RELA

Section
GRID INIT x RECU
These keywords set targets for injection rate of oil (OIT), gas (GIT) and water (WIT)
correspondingly. These keywords should be used inside ETAB (see 14.6.5) table or inside
EFILE (see 14.6.3) file to specify well event.
1. injection rate. Units:
if OIT / WIT is specified - METRIC: sm3 /day, FIELD: stb/day;

if GPT is specified - METRIC: sm3 /day, FIELD: Msc f /day;
These keywords are analogous to the 5-th parameter of the keyword WCONINJE (see
Example
1019 01.10.2010 INJ WIT 1200.0
In the example the target for water injection rate for injection well 1019 is set on
01.10.2010. It is equal to 1200 sm3 /day.
14.6.41. OIT / GIT / WIT 2110

14.6.42 WEF

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies well efficiency factor. This keyword should be used inside ETAB
(see 14.6.5) table or inside EFILE (see 14.6.3) file to specify well event.
1. well efficiency factor (a number between 0 and 1).
This keyword has an Eclipse compatible analogue WEFAC (see 12.18.69).
Example
ETAB
...
93-2 01.07.2015 WEF 0.95
In the example the efficiency factor for the well 93-2 is set on 01.07.2015. It is equal to
0.95.
14.6.42. WEF 2111

14.6.43 STRE

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies an injection composition. This keyword should be used inside
ETAB (see 14.6.5) table or inside EFILE (see 14.6.3) file to specify well event.
1. component to inject. Use the keyword SCMP (see 14.1.10) to specify several compo-
nents to inject.
This keyword has an Eclipse compatible analogue WELLSTRE (see 12.18.159).
Example
T1 09.06.2021 STRE H2S
In the example the well T1 is injecting H2S component.
14.6.43. STRE 2112

14.6.44 GOPT / GGPT / GWPT / GLPT

INPU FLUI RELA

Section
GRID INIT x RECU
These keywords set targets for well injection groups for oil, gas, water and liquid rates
correspondingly. These keywords should be used inside ETAB (see 14.6.5) table or inside
EFILE (see 14.6.3) file to specify well event.
1. rate value. Units:
if GOPT / GWPT / GLPT is specified METRIC: sm3 /day, FIELD: stb/day;

if GGPT is specified METRIC: sm3 /day, FIELD: Msc f /day.
These keywords are analogous to the 3rd, 4th, 5th and 6th parameters of the keyword
GCONPROD (see 12.18.72), that is used by Eclipse.
Example
ETAB
ALLProd 01.01.2025 GGPT 16124.91781 /
ALLProd 01.01.2026 GGPT 15172.32877 /
In the example 2 events are set for group ALLProd. On 01.01.2025 group target for gas
rate, which is equal to 16124.91781 sm3 /day, is set. On 01.01.2026 group target for gas rate,
which is equal to 15172.32877 sm3 /day, is set.
14.6.44. GOPT / GGPT / GWPT / GLPT 2113

14.6.45 HOURS

INPU FLUI RELA

Section
GRID INIT x RECU
This subkeyword specifies the number of hours, which will be added to event date.
This way accuracy of event date can be increased. This subkeyword can be used with any
keyword, which specify well event (ETAB (see 14.6.5)).
1. the number of hours to add to event date.
Example
T1 09.06.2021 STRE H2S HOURS 10
In the example well T1 starts to inject H2S component at 10 AM on 09.06.2021.
14.6.45. HOURS 2114

14.6.46 DATE / READ / TIME

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies the time and simulator will read recurrent data until respective
date.
1. the time to be simulated:
the number of days/months/years;

date in DD MMM YYYY format. If in the field year 2 digits are specified,
then it is considered that this year is in XXth century;
2. time unit:
DAYS day. It is specified only if the first parameter sets number of days;
MONT month. It is specified only if the first parameter sets number of months;
YEAR year. It is specified only if the first parameter sets number of years;
DATE date. It is specified only if the first parameter sets certain date;
3. [additional parameter] HOUR - the number of hours to add to date.
Example
READ 01 JAN 2024 DATE
In the example it is specified that simulator will read recurrent data until on 01.01.2024.
14.6.46. DATE / READ / TIME 2115

14.6.47 GROU

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword specifies a well group. The following parameters should be specified:
1. group name;
2. [additional parameter] FRAC - option to set fraction of well rate in group rate;
3. [additional parameter] fraction of well rate in group rate (necessary, if FRAC is used);
4. well names list.
Default:
well rate in group rate (if FRAC is not used): 1.
This keyword has an Eclipse compatible analogue GRUPTREE (see 12.18.85).
Example
GROUP 0C1 122 123 124 125 FRAC 0.5 126 FRAC 0.5 127
In the example group 0C1 is specified by the keyword GROU. It contains wells 122, 123,
124 and 125 which have fraction rate 1 and wells 126 and 127 which have fraction rate 0.5.
14.6.47. GROU 2116

14.6.48 DRAW

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets well target for well drawdown value. This keyword should be used
inside ETAB (see 14.6.5) table or inside EFILE (see 14.6.3) file to specify well event.
1. drawdown value (METRIC: bar , FIELD: psi).
This keyword has an Eclipse compatible analogue WELDRAW (see 12.18.104).
Example
208 01.06.2009 PROD DRAW 9.19 BHPT 50 HWEF
In the example some events are specified for the well 208 on 1.06.2009:
well drawdown target is equal to 9.19 bars (via the keyword DRAW (see 14.6.48));
bottom hole pressure target value is equal to 50 bars (via the keyword BHPT
(see 14.6.38));
well historical efficiency factor value is used as a target (via the keyword HWEF
(see 14.6.29)).
14.6.48. DRAW 2117

14.6.49 VREP

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets voidage replacement for groups. This keyword should be used inside
ETAB (see 14.6.5) table or inside EFILE (see 14.6.3) file to specify well event.
1. group name which contains producing wells;
2. group name which contains injecting wells;
3. voidage replacement coefficient.
4. OFF [additional parameter] - event cancellation;
5. SGAS [additional parameter] - gas will be injected at a given fraction of the gas
production at surface conditions;
6. SWAT [additional parameter] - water will be injected at a given fraction of the gas
production at surface conditions.
Voidage replacement coefficient is set as an injection rate limit for a group which is spec-
ified by the parameter 2. It is equal to ratio of this group injection rate to group production
rate (name of this group is specified by the parameter 2). Volume replacement calculated as
a volume in surface conditions.
Default:
group name which contains producing wells: ALL;
group name which contains injecting wells: ALL;
voidage replacement coefficient: 1.
This keyword has an Eclipse compatible analogue GCONINJE (see 12.18.81).
Example
13 01.01.2014 VREP DOB4 NAG4 1.75
In the example the keyword VREP sets voidage replacement coefficient. Value of com-
pensating injection fluid rate will be greater than producing rate 1.75 times.
14.6.49. VREP 2118

14.6.50 RECY

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets recycle operation between two well groups. This keyword should be
1. recycle stream name;
2. name of group with producing wells;
3. name of group with injecting wells;
4. name of injecting component;
5. ON or OFF
ON - turn on recycle injection;

OFF - turn off recycle injection.
Default:
ON or OFF: ON.
Example
RECY PRDG GR_P GR_I WAT
In the example the keyword RECY is used to set recycle operation. Stream name -
PRDG, group of producing wells - GR_P, group of injecting wells - GR_I.
14.6.50. RECY 2119

14.6.51 GGRT / GWRT

INPU FLUI RELA

Section
GRID INIT x RECU
These keywords set group recycling targets:
GGRT - recycling gas;
GWRT - recycling water.
These keywords should be used inside ETAB (see 14.6.5) table or inside EFILE (see 14.6.3)
file to specify well event.
1. reinjection coefficient;
2. OFF [additional parameter] - turn off settings;
3. GROUP - type of object which produces fluid;
4. name of well group with producing wells. Fluid which is produced by this group will
be injected;
5. the way to calculate produced rate for the following calculate injection rate:
SURF - at surface conditions;

RESV - at reservoir conditions;
Default:
the way to calculate produced rate: RESV.
This keyword has an Eclipse compatible analogue GCONINJE (see 12.18.81).
Example
GR_I 01.01.2014 GGRT 1 GROUP GR_P
In the example well group GR_I starts to inject full volume of fluid produced by group
GR_P.
14.6.51. GGRT / GWRT 2120

14.6.52 CWAG

INPU FLUI RELA

Section
GRID INIT x RECU
This keyword specifies well event, thats why it should be used inside ETAB (see 14.6.5)
table or inside EFILE (see 14.6.3) file.
The keyword sets continuous simultaneous water and gas injection. The following param-
1. gas fraction in volume of injected water.
It is need to note that water injection rate should be specified to calculate gas volume to
inject. If gas injection rate is specified, than water volume to inject will be calculated.
Analogous for this keyword is the 2-nd, 13-th and 14-th parameters of the keyword
WCONINJE (see 12.18.36), that is used by Eclipse.
Example
T1iH2SW 09.06.2021 INJE CWAG 0.001
In the example 2 events for well T1iH2SW are specified: on 09.06.2021 its type is
changed to injection (the keyword INJE (see 14.6.19)) and fraction of gas in water volume
to inject is equal to 0.001 (the keyword CWAG).
14.6.52. CWAG 2121

14.6.53 KMOD

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is used to change cells permeability values during calculation. The following
1. X -coordinate of the first cell to change permeability;
2. X -coordinate of the last cell to change permeability;
3. Y -coordinate of the first cell to change permeability;
4. Y -coordinate of the last cell to change permeability;
5. Z -coordinate of the first cell to change permeability;
6. Z -coordinate of the last cell to change permeability;
7. SCALAR [additional parameter] - this option is used to specify one value to
multiply all initial permeability values by this value.
on the next line:
1. multipliers list to apply to initial permeability values. The number of these multi-
pliers should be equal to th number of cells, which are specified in the first line
(if option SCALAR is not specified).
Default:
X -coordinate of the first cell to change permeability: 1;
X -coordinate of the last cell to change permeability: Nx ;
Y -coordinate of the first cell to change permeability: 1;
Y -coordinate of the last cell to change permeability: Ny ;
Z -coordinate of the first cell to change permeability: 1;
Z -coordinate of the last cell to change permeability: Nz ;
Example
KMOD 32 38 84 88 1 6 SCALAR
10
In the example via the keyword KMOD (see 14.6.53) the values of cells permeability will
be multiplied by 10.
14.6.53. KMOD 2122

14.6.54 PARE

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is used to specify parent well group for a well group. The following
1. name of the group which will be assigned to a parent group;
2. name of the parent group.
Default:
name of the parent group: ALL.
Example
PARE PROD_1_2 PROD
PARE PROD_3_4 PROD
In the example well group PROD is set to be a parent one for groups PROD_1_2 and
PROD_3_4.
14.6.54. PARE 2123

14.6.55 PCSH

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets options for capillary pressure values shift to stabilize solution when
option EQUI (see 14.5.4) is used.
1. shift option: MIN, LIMI, FULL or OFF.
MIN - adds a minimal set of shifts to cells in which two phases are mobile;
LIMI - adds a minimal set of shifts to cells with the following notices:
PcOG shifts are calculated only for cells which are below gas-oil contact
defined by EQUI (see 14.5.4);
PcOW shifts are calculated only for cells which are above water-oil contact;
the stabilisation shifts will generally be less than generated ones by the MIN
option, but there may be some initial state movement for cells outside the
chosen contact depth interval.
FULL - shifts the capillary pressures of all the cells in the reservoir so that all
phases lie on their hydrostatic pressure curves;
OFF - shift of capillary pressure values is denied.
Default:
shift option: MIN.
Example
PCSH FULL
14.6.55. PCSH 2124

14.6.56 GVRT

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets settings of voidage replacement.

This keyword should be used inside ETAB (see 14.6.5) table or inside EFILE (see 14.6.3)
file to specify well event.
1. reinjection coefficient, i.e. injection rate expressed via production rate;
2. reinjection rate;
3. OFF [additional parameter] - turn off this option;
4. WELL name / GROUP name - instead of name you should to specify a name of
injection well or a well group which contains injection wells. This well or group will
inject producted fluid.
Default: None.
Example
ALL 12.05.2010 GVRT 1 0 GROUP ALL
In the example the keyword GVRT sets settings of voidage replacement. Producted fluid
will be injected by all injection well of a field.
14.6.56. GVRT 2125

14.6.57 PLIM

INPU FLUI RELA

Section
GRID INIT x RECU
This keyword specifies well event, then it should be used inside ETAB (see 14.6.5) table
or inside EFILE (see 14.6.3) file.
This keyword sets well lower limits.

1. limit type:
OIL - oil rate (METRIC: sm3 ; FIELD: stb);

GAS - gas rate (METRIC: sm3 ; FIELD: stb);
WCT (WCUT) - watercut (METRIC: sm3 /sm3 ; FIELD: stb/stb);
WGR - water-gas ratio (METRIC: sm3 /ksm3 ; FIELD: stb/Msc f );
GOR - gas-oil ratio (METRIC: ksm3 /sm3 ; FIELD: Msc f /stb);
GLR - gas-liquid ratio (METRIC: ksm3 /sm3 ; FIELD: Msc f /stb);
OGR - oil-gas ratio (METRIC: sm3 /ksm3 ; FIELD: stb/Msc f ).
2. limit value;
3. action to well if limit will be exceeded:
SHUT - shut well.
Example
P2 12.05.2010 PLIM GOR 0.5 SHUT
In the example limit on P2 is set. Limit will be active since 12.05.2010. If ratio of gas
rate and oil rate will exceed 0.5, then well P2 will be shut.
14.6.57. PLIM 2126

14.6.58 CIJK

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets coordinates of well perforations. The data should be terminated with a
slash /.
1. well name [additional parameter] well name is in the line, if parameter WELL is in
EFORm (see 14.6.12). Otherwise well name can be specified separately in line, which
precedes the line that specify event;
2. perforation date (date format should correspond to the format specified in EFORm
(see 14.6.12). For example, DD.MM.YYYY);
3. The keyword CIJK which specifies event;
4. perforation i-coordinate;
5. perforation j -coordinate;
6. first perforation interval k -coordinate;
7. second perforation interval k -coordinate;
8. [additional parameter] well radius (METRIC: m, FIELD: f t );
9. [additional parameter] multiplier of transmissibility coefficient;
10. [additional parameter] skin-factor;
11. [additional parameter] transmissibility coefficient (METRIC: cP-rm3 /day-bar ,

FIELD: cP-rb/day- psi);
12. [additional parameter] well Kh (METRIC: mD-m, FIELD: mD- f t );
Default:
well radius: 0.5 f t ;
transmissibility multiplier: 1;
14.6.58. CIJK 2127

skin: 0.
Example
ETAB
P2 0 CIJK 10 41 10 13
In the example the keyword CIJK sets well P2 perforation coordinates at initial time step.
Example
WELL P1 PROD Q=10 PLIM=2800 BHP
RADI 0.5
CIJK
10 41 10 10 /
10 41 11 11 /
10 41 12 12 /
10 41 13 13 /
/
This example is equivalent to the example above, but in this one perforation coordinates
are defined via the keyword WELL (see 14.6.23).
14.6.58. CIJK 2128

14.6.59 ARRAy

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets list of timesteps to output calculation model results at these steps. Dates
(or times) should be specified, but not step numbers.
in the line with the keyword:
1. time intervals unit:

DAYS day;
MONT month;
YEAR year;
DATE steps are specified in full date format.
2. [additional parameter] EQUA intervals between outputs are equal. Interval
length is equal to the first number in the next line;
3. [additional parameter] END additional output at the calculation end.
in the next line:
1. intervals or timestep dates list. The data should be terminated with a slash /.
Default:
time intervals unit: DATE.
Example
ARRA YEAR END
0 1 2 3 4 /
In the example the keyword ARRA sets date list. Calculation results will be outputed for
these dates. Data will be outputed at initial timestep at first, then data will be outputed one
time each year. Finally data will be outputed at the last timestep.
14.6.59. ARRAy 2129

14.6.60 FREQ

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is used to set a multiple for data output frequency. Data output is set via the
keyword RATE (see 14.6.2). The keyword FREQ (see 14.6.60) always follows the keyword
RATE (see 14.6.2).
1. a multiple for frequency of data output to monitor.
Default:
a multiple for frequency of data output to monitor: 0. In this case data will be outputed
at each time step.
Example
RATE 2 MONT
FREQ 2
In the example frequency of data output is equal to 4 months.
14.6.60. FREQ 2130

14.6.61 DELTa

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword is set length of calculation next time step.

The keyword is ignored, it is a MORE compatibility field.
14.6.61. DELTa 2131

14.6.62 COMP

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets perforation intervals along well which track was specified via the key-
words TFIL (see 14.6.4) or TTAB (see 14.6.6)/ENDT (see 14.6.8). This keyword can be used
only with the keyword WELL (see 13.9.6) and should be specified after it.
1. track name which set via the keywords TFIL (see 14.6.4) or TTAB (see 14.6.6)/ENDT
(see 14.6.8);
2. depth MD of the start of perforation interval (METRIC: m, FIELD: f t );
3. depth MD of the end of perforation interval (METRIC: m, FIELD: f t );
4. radius of well over this interval;
5. skin-factor;
6. transmissibility multiplier;
7. [additional parameter] cells type to perforate (for dual porosity and dual permeability
models):
FRAC complete fracture cells only;

MAT complete matrix cells only;
BOTH complete both cell types.
This keyword has a tNavigator analog COMPDATMD (see 12.18.10).
Default:
radius of well over this interval: 6 inches;
skin-factor: 0;
transmissibility multiplier: 1;
cells type to perforate (for dual porosity and dual permeability models): FRAC.
14.6.62. COMP 2132

Example
WELL 232 PROD HLIQ PMIN=110 QOIL=100 HWEF
COMP 232 4000 4030 0.25 0 1
In the example for well 232 perforation interval, well radius, skin-factor and transmissi-
bility multiplier are set.
14.6.62. COMP 2133

14.6.63 BRANch

INPU FLUI RELA

Section
GRID INIT x RECU
The subkeyword is optional for keyword PERF (see 13.9.13), which defines well perfora-
tion event. BRAN (see 14.6.63) sets number of branch which will be perforated. Trajectories
must first be defined using the keyword TFIL (see 14.6.4), or TTAB (see 14.6.6), or WELL-
TRACK (see 12.18.9).
Example
TTAB
'P1'
525 525 2950 1*

525 525 2960 1*
P1:1'
'
525 525 2954 0

575 525 2955 50
725 525 2956 200

ETAB
P1 01.01.2015 PERF 50 200 0.1 3 1* BRANCH 1
ENDE
In the example perforation of branch 1 of well P1 is set.
14.6.63. BRANch 2134

14.6.64 TRAC (RECU)

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets the beginning of tracer injection. The following parameters should be
specified:
1. well name [additional parameter] well name is in the line, if parameter WELL is in
EFORm (see 14.6.12). Otherwise well name can be specified separately in line, which
precedes the line that specify event;
2. perforation date (date format should correspond to the format specified in EFORm
(see 14.6.12). For example, DD.MM.YYYY);
3. The keyword TRAC which specifies event;
4. tracer concentration;
5. tracer name.
Example
P1 01.01.2015 TRAC 0.1 TRC1
14.6.64. TRAC (RECU) 2135

14.6.65 WGPP

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets well to which GPP (see 14.1.17) option will be applied. This keyword
is used only when parameter ALL is not used in keyword GPP (see 14.1.17). The following
1. well name. Only one well name can be specified.
Example
WGPP PROD1
14.6.65. WGPP 2136

14.6.66 WMPG

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets well to which MPGP (see 14.1.18) option will be applied. This keyword
is used only when parameter ALL is not used in keyword MPGP (see 14.1.18). The following
Example
WMPG PROD1
14.6.66. WMPG 2137

14.6.67 WRG

INPU FLUI RELA

Section
GRID INIT x RECU
The keyword sets well to which Russell-Goodrich equation will be applied (see details in
the description of keyword RG (see 14.1.19)). The following parameters should be specified:
Example
WRG PROD1
14.6.67. WRG 2138

15. Keyword definitions index E100, E300 tNavigator-4.2
15 Keyword definitions index E100, E300

A
ACF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928
ACFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
ACTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1472
ACTIONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1474
ACTIONR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1477
ACTIONW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1479
ACTIONX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1482
ACTNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
ADD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .641
ADDREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
ADDZCORN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
AIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
AIMFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
ALKADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
ALKALINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
ALKROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
ALPOLADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
ALSURFAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
ALSURFST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
AMALGAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
APIGROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
APIVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097
AQANTRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1161
AQUANCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165
AQUCHWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153
AQUCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169
AQUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1162
AQUDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1150
AQUFET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155
AQUFETP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1159
AQUFLUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1152
AQUNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167
AQUTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164
ASPFLRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
ASPHALTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
ASPP1P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
ASPP2P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
ASPPW2D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
ASPREWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
15. Keyword definitions index E100, E300 2139

ASPVISO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
B
BDENSITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
BIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
BICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
BIGMODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
BLACKOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
BOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
BRANPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1382
BRINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
C
CALVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073
CALVALR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074
CARFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
CART. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .401
CATYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878
CBMOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
CECON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1343
CNAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
CO2SOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
COAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
COALNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
COARSEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
COMPDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1209
COMPDATL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1212
COMPDATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215
COMPINJK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253
COMPLMPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1249
COMPLUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247
COMPMBIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1528
COMPMOBI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1526
COMPOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1395
COMPORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1251
COMPRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1267
COMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
COMPSEGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246
COMPSEGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1243
COMPVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
COORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
COORDSYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
COPYBOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638

COPYREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
CREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009
CSKIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1645
CVCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421
CVTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
D
DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1195
DATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1412
DATUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126
DATUMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127
DATUMRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1128
DCQDEFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1557
DELAYACT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1488
DENSITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
DEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
DGRDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1381
DIFFCBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
DIFFCGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 951
DIFFCOAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
DIFFCOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
DIFFMMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
DIFFUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
DIMENS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
DISGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
DNGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
DOMAINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
DPCDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
DPGRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
DPNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
DRAINAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
DREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
DREFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
DRILPRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1588
DRSDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1401
DRVDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404
DUALPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
DUALPORO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
DUMPFLUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
DX / DY / DZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
DXV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .466
DYV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .467
DZMATRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
DZMTRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554

DZMTRXV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
DZNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
DZV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
E
ECHO / NOECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
EDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
EDITNNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
EHYSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796
EHYSTRR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
END . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
ENDACTIO / ENDACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1490
ENDBOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
ENDFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
ENDNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
ENDSCALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
ENDSKIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1587
ENKRVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946
ENKRVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
ENKRVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1066
ENPCVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
ENPCVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
ENPCVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067
ENPTVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
ENPTVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
ENPTVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065
EOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
EOSNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
EOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
EPSCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945
EQLDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
EQLNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
EQLOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
EQUALREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
EQUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
EQUIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077
ESSNODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
F
FACTLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
FAULTDIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
FAULTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
FIELD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
FIELDSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104

FIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
FIPNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
FIPOWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
FIPSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1106
FLUXNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
FLUXREG / FLUXTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
FMTIN/ FMTSAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
FOAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
FOAMADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
FOAMDCYO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884
FOAMDCYW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883
FOAMMOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
FOAMMOBP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886
FOAMMOBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
FOAMOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881
FOAMROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882
FORMOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
FULLIMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
G
GADVANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1538
GAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
GASBEGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559
GASCCMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1143
GASCONC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1141
GASEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1561
GASFCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1566
GASFDECR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1565
GASFIELD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
GASFTARG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1564
GASMONTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1562
GASPERIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1554
GASSATC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142
GASVISCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
GASVISCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
GASYEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1551
GCONINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1372
GCONPRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1358
GCONPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1349
GCONSALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1540
GCONSUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1375
GCONTOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1600
GCUTBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306
GDCQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549

GDCQECON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558
GDFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
GDRILPOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1593
GECON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1406
GEFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1347
GEOMECH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
GINJGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1536
GLIFTLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1607
GLIFTOPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1608
GNETDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1388
GNETINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1390
GNETPUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1398
GPMAINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1361
GPMAINT3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1363
GPTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108
GPTABLE3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112
GPTABLEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1110
GPTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
GRAVDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
GRAVDRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
GRAVITY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .718
GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
GRIDFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
GRIDOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
GRIDUNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
GRUPFUEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1542
GRUPINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1292
GRUPLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1408
GRUPMAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1641
GRUPNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1399
GRUPPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1624
GRUPRIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1596
GRUPSALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1539
GRUPSLAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1643
GRUPTARG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317
GRUPTREE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1380
GSATINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1378
GSATPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1376
GSEPCOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506
GSWINGF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1547
GUIDERAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1353
H
HEATCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979

HEATCRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
HEATDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
HEATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1522
HEATVAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
HEATVAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
HEATVAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1061
HMMLCTAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174
HMMLFTAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1175
HMMLTPX / HMMLTPY / HMMLTPZ / HMMLTPXY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
HMMULTX / HMMULTY / HMMULTZ / HMMLTXY / HMMULTPV . . . . . . . . . . . . . . . 488
HMMULTX- / HMMULTY- / HMMULTZ- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
HWELLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
HXFIN / HYFIN / HZFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
I
IKRG, IKRGR, IKRW, IKRWR, IKRO, IKRORW, IKRORG . . . . . . . . . . . . . . . . . . . . . . . . . . 790
IMBNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
IMBNUMMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
IMPES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
IMPLICIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
IMPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
INCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
ISGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
ISGL, ISGCR, ISGU, ISWL, ISWLPC, ISWCR, ISWU, ISOGCR, ISOWCR . . . . . . . . . . . 778
J
JALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
JFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
JFUNCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
K
KRG, KRGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
KRNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
KRNUMMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
KRO, KRORW, KRORG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
KRW, KRWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
KVALUES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
KVCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
KVCRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
KVTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
KVTABTn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
KVTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
KVWI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978

L
LAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
LANGMEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
LANGMUIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
LANGMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
LBCCOEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
LBCCOEFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
LGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
LGRCOPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
LGRLOCK / LGRFREE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1429
LICENSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
LIFTOPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1606
LILIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 940
LOWSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
LSALTFNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
LTOSIGMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
LWSLTNUM / LSNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
LX / LY / LZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
M
MAPAXES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
MAPUNITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
MATCORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1422
MAXVALUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
MESSAGE / MESSAGES / MSGFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
METRIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
MIDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
MINDZNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
MINPORV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
MINPV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
MINPVV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
MINROCKV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
MINRV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
MINVALUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
MISCEXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
MISCIBLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
MISCNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
MISCSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
MISCSTRR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
MONITOR/ NOMONITO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
MULTFLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
MULTIN/ MULTSAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
MULTIPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631

MULTIREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
MULTMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
MULTNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
MULTOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
MULTPV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
MULTREGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
MULTREGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
MULTSIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1439
MULTSIGV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1440
MULTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
MULTX- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
MULTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
MULTY- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
MULTZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
MULTZ- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
MW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924
MWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
MWW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927
N
NCOMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962
NCONSUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387
NEI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
NETBALAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1423
NETCOMPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1392
NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
NEWTRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
NEXTSTEP / NSTACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1428
NNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
NNCGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
NODEPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384
NODPPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
NOMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
NONNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
NOSIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
NPROCX / NPROCKY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
NTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
NUMRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
NUPCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1598
NWATREM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1396
NXFIN / NYFIN / NZFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
O
OIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

OILAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1098
OILVINDX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
OILVISCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
OILVISCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
OLDTRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
OMEGAA / OMEGAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
OMEGAAS / OMEGABS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
OPERATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
OPERATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
OPERNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1611
OUTSOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
OVERBURD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
P
PARACHOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
PARALLEL / PARAOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
PATHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
PBUB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119
PBVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
PCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
PCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
PCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
PCW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .791
PDEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125
PDVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085
PEDERSEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958
PEDTUNE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
PEDTUNER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
PERMAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
PERMMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
PERMX / PERMY / PERMZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
PETOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
PICOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1569
PIMTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
PIMULTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1266
PINCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
PINCHNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
PINCHOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
PINCHREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
PLMIXNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
PLMIXPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
PLYADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
PLYMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848

PLYROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
PLYSHEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
PLYSHLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
PLYVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
PLYVISCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
PMANUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
POLYMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
PORO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
PORV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
PPCWMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
PRCORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942
PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
PREFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
PRESSURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087
PRIORITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1366
PROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
PRORDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1604
PRVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1089
PSEUPRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1634
PSPLITX/ PSPLITY/ PSPLITZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
PVCDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
PVCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
PVDG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
PVDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
PVTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
PVTNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
PVTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
PVTW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
PVTWSALT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .823
PVZG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
Q
QDRILL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1592
R
REACACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035
REACCORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
REACENTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051
REACLIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040
REACPHA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
REACPORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045
REACRATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
REACSORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
REACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

RECOVERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114
REFINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
REGDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
REGIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
RESORB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
RESVNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
RKTRMDIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
ROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
ROCKCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
ROCKCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
ROCKDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
ROCKDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
ROCKNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
ROCKOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
ROCKPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
ROCKTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
ROCKV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068
ROMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1148
RPTGRID/ RPTGRIDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
RPTHMD/ RPTHMG/ RPTHMW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
RPTISOL/ RPTPROPS/ RPTREGS/ RPTRUNSP/ RPTSCHED/ RPTSMRY/ RPTSOL . . 457
RPTONLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194
RPTRST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
RS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121
RSCONST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
RSCONSTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
RSVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1080
RSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145
RSWVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965
RTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
RTEMPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1116
RTEMPVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117
RUNSPEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
RV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123
RVCONST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
RVCONSTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
RVVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083
S
SALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1136
SALTNODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
SALTVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137
SATNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654

SATOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
SCALECRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
SCALELIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
SCDATAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1631
SCDPDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
SCDPTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1629
SCDPTRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1630
SCHEDULE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1200
SCREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999
SDREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
SEPARATE / RUNSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196
SEPCOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1507
SEPVALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1504
SFOAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146
SGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1092
SGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
SGFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
SGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
SGOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
SGU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
SGWFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
SIGMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
SIGMAGD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
SIGMAGDV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
SIGMAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
SKIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1579
SKIP100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1581
SKIP300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1582
SKIPREST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1580
SKIPSTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
SLAVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1640
SLGOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
SMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1099
SOF2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
SOF3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
SOGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
SOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094
SOILR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1147
SOLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
SOLUBILI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
SOLUTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1076
SOLVDIRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
SOMGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758

SOMWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
SOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
SOROPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890
SOWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
SPECGRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
SPECHA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052
SPECHB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
SPECHEAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1072
SPECHG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057
SPECHH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058
SPECHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062
SPECHT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063
SPECROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071
SPOLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1140
SPREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
SSHIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943
SSHIFTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
SSOLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096
START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
STCOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
STHERMX1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
STOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
STONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
STONE1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
STONE2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
STONEPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764
STOPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046
STOREAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047
STOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
STREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
STVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
SUMMARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177
SURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1139
SURFACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
SURFACTW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
SURFADDW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
SURFADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
SURFCAPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
SURFNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
SURFROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
SURFST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
SURFSTES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
SURFVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839

SURFWNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
SWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1090
SWATINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
SWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
SWFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
SWINGFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1545
SWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
SWLPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770
SWOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
SWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776
T
TABDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
TBLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1129
TCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
TCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913
TEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
TEMPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115
TEMPVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1064
THANALB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
THCGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
THCOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
THCONMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
THCONR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
THCONSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
THCROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
THCSOLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
THCWATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
THERMAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
THERMEX1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
THPRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086
THPRESFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
THSVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1069
THWVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070
TIGHTENP / TSCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1426
TITLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
TNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131
TOLCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
TOPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
TRACER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
TRACERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
TRANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1628
TRANX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
TRANY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526

TRANZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
TRDCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
TREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010
TREFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011
TSTEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1415
TUNING / TUNINGDP / TUNINGL / TUNINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1425
TVDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133
TZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
U
UDADIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
UDQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1491
UDQDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
UDQPARAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
UDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1495
UDTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
UNIFIN/ UNIFSAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
UNIFOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
USEFLUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
V
VAPOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
VCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
VCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
VCRITVIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
VDKRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953
VDKRGC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955
VDKRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
VELDEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
VFPCHK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1326
VFPIDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
VFPINJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1319
VFPPDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
VFPPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1322
VFPTABL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1327
VISCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
VISCREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
W
WAGHYSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
WALKALIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1515
WARN / NOWARN / NOWARNEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
WATDENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968
WATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
WATERTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901

WATVISCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019
WAVAILIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1544
WBHGLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1308
WCONHIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1275
WCONINJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281
WCONINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1278
WCONINJH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1286
WCONINJP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283
WCONPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1271
WCUTBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304
WCYCLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1295
WDFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1510
WDFACCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1511
WDRILPRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1590
WDRILRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1594
WDRILTIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1591
WECON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1333
WECONCMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1339
WECONINJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1345
WEFAC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1346
WELCNTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1316
WELDRAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1409
WELLCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1626
WELLDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
WELLGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1638
WELLINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1289
WELLLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1342
WELLOPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1420
WELLOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1599
WELLPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1621
WELLSPEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1208
WELLSTRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1525
WELLTARG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315
WELLWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1297
WELOPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1416
WELOPENL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1418
WELPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1318
WELPRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368
WELSEGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1221
WELSOMIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201
WELSPECL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205
WELSPECS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1202
WELTARG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1313

WFOAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1646
WFRICSEG / WFRICSGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1242
WFRICTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237
WFRICTNL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1240
WGASPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1563
WGORPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1340
WGRUPCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1370
WH2NUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
WH3NUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
WHISTCTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1303
WHTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1519
WINJGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1534
WINJMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1530
WINJMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269
WINJORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1532
WINJTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1520
WINJWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1521
WLIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1601
WLIFTOPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609
WLIMTOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1503
WLIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255
WLISTDYN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1257
WNETDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1620
WORKLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1595
WORKTHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1348
WPAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1571
WPAVEDEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1575
WPIMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1259
WPIMULTL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1262
WPITAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1265
WPOLYMER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1516
WREGROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1356
WRFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1576
WRFTPLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1577
WSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517
WSCTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1632
WSEGAICD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1230
WSEGDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
WSEGEXSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1233
WSEGFLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235
WSEGITER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1424
WSEGTABL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1225
WSEGVALV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1227

WSEPCOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1509
WSURFACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1514
WTADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1312
WTAKEGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1543
WTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1518
WTEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1523
WTMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1310
WTRACER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1513
WVFPDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1567
WVFPEXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1328
X
XMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1100
XMFVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
Y
YMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1101
YMFVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
Z
ZCORN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
ZCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
ZCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
ZCRITVIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
ZFACT1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
ZFACTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
ZI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902
ZIPPY2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1427
ZMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1102
ZMFVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907

16. Keyword definitions index IMEX, STARS, GEM tNavigator-4.2
16 Keyword definitions index IMEX, STARS, GEM

A
AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1802
ALTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1893
AQFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1677
AQLEAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1671
AQMETHOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1672
AQPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1674
AQUIFER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676
AQVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1673
AVG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1787
AVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1780
B
BIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1800
BKRGCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1843
BKROCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1845
BKRWIRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1841
BOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1794
BPCGMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1847
BPCWMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1849
BSGCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1831
BSGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1833
BSOIRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1835
BSOIRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1829
BSORG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1839
BSORW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1837
BSWCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1827
BSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1825
BVG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1788
BVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1781
BWI / CW / REFPW / CVW / VWI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1735
C
CCPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1683
CMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1789
CO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1793
COMPNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1737
CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1651
CONC_ SLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1869
COORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1660
CORNERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1679
COT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1792
16. Keyword definitions index IMEX, STARS, GEM 2158

CP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1744
CPEPAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1717
CPG1 / CPG2 / CPG3 / CPG4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1756
CPL1 / CPL2 / CPL3 / CPL4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1755
CPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1701
CPORPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1714
CPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1747
CPTPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1703
CRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1719
CROCKTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1684
CROCKTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1681
CT1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1745
CT2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1746
CTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1723
CTPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1702
CTPPAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1724
CTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1682
CVO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1795
D
DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1886
DATUMDEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1856
DENSITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1734
DEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1691
DGOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1862
DI / DJ / DK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1658
DIFRAC / DJFRAC / DKFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1663
DILATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1725
DTOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1692
DUALPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1678
DUALPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1661
DWOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1861
E
EACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1765
EACT_ TAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1766
EOSSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1798
EOSTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1799
EV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1760
F
FORMINFRAC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1689
FR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1722
FRACTURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1650
FREQFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1763

FREQFACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1764
FRFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1688
G
GASD-ZCOEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1790
GASLIQKV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1791
GEOMETRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1894
GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1657
H
HEATR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1882
HLOSSPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1713
HLOSST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711
HLOSSTDIFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1712
HTWELL / HTWRATE / HTWRATEPL / HTWTEMP / HTWI . . . . . . . . . . . . . . . . . . . . . . 1905
HVAPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1758
HVR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1759
I
IDEALGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1797
INCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1811
INITIAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1852
INITREGION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1857
INJECTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1889
INTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1858
INUNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1655
ISOTHERMAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1878
IVAR / JVAR / KVAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1652
K
K_ SURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1727
KRGCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1842
KROCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1844
KRTEMTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1822
KRTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1821
KRWIRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1840
KV1 / KV2 / KV3 / KV4 / KV5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1754
KVTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1753
KVTABLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1752
L
LAYERXYZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1898
M
MASSDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1743
MATRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1649

MAXTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1880
MFRAC_ GAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1871
MFRAC_ OIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1870
MINTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1879
MIXVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1779
MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1730
MOLDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1742
MOLVOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1729
N
NETGROSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1667
NETPAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1670
NULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1664
NUMERICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1876
O
O2PP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1773
OMEGA / OMEGB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1803
ON-TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1903
OPERATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1891
P
PADSORP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1806
PB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1855
PBASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1716
PBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1872
PCGEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1846
PCHOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1801
PCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1748
PCWEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1848
PDILA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1718
PERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1896
PERMI / PERMJ / PERMK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1666
PINCHOUTARRAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1668
PMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1808
POR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1665
PORMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1715
PORRATMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1720
PPACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1721
PPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1807
PREFCONC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1809
PRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1867
PRODUCER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1888
PRPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1700
PRSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1738

PSURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1740
PTHRESHI / PTHRESHJ / PTHRESHK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1850
PTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1736
PVCUTOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1693
PVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1810
PVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1732
Q
QUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1901
R
REFDEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1860
REFINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1694
REFPRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1859
RENTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1767
ROCKCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1699
ROCKFLUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1813
ROCKTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1697
RORDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1768
RPHASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1769
RPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1814
RTEMLOWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1771
RTEMUPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1770
RTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1820
RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1885
RXCRITCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1772
S
SCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1695
SECTORARRAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1690
SEPARATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1873
SG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1865
SGCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1830
SGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1832
SGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1818
SHAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1662
SHUTIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1890
SLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1816
SO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1864
SOIRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1834
SOIRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1828
SOLID_ CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751
SOLID_ DEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1750
SORG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1838
SORW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1836

STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1904
STOPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1762
STOREAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1761
SURFLASH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1728
SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1866
SWCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1826
SWINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1854
SWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1824
SWT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1815
T
TCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1749
TEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1868
TEMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1739
TFORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1877
THCONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1707
THCONMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1709
THCONO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1706
THCONR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704
THCONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1708
THCONW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1705
THTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1698
TINJW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1900
TITLE1 / TITLE2 / TITLE3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1654
TMPSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1883
TRANLI / TRANLJ / TRANLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1686
TRANSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1687
TRANSI / TRANSJ / TRANSK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1685
TRIGGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1907
TSURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1741
U
UHTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1884
V
VERTICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1853
VGUST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1805
VISCOEFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1778
VISCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1776
VISCTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1782
VISCTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1775
VISVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1777
VOLMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1669
VOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1796
VSHIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1804

VSMIXCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1784
VSMIXENDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1785
VSMIXFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1786
VSTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1774
W
WELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1887
WELSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1906
WOC_ SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1863
WTMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1902
Z
ZCORN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1659

17. Keyword definitions index RFD tNavigator-4.2
17 Keyword definitions index RFD

A
ACTIONC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1498
AIMCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
APILIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1636
AQUGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172
AQUOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157
ARITHMETIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
ARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
AUTOSAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1637
B
BLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
BNDNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
C
COMPDATMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1218
COMPENSATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1405
COMPFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1460
COMPFRACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1463
COMPVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1617
COMPVALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1618
COREYGO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
COREYGOMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
COREYWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
COREYWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
COREYWOMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
CORNERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
D
DEACDEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
DEFINES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
DRSDTVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1402
DRSDTVPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1403
E
ECDATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
ECINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
ECVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
ENPTRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
F
FIPPATT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
FLASHCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
17. Keyword definitions index RFD 2165

FLOWFNAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
FLOWFTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
FLOWFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
G
GWRATMUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1635
H
HEATTCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
I
IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
IF-THEN-ELSE-ENDIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
INTERPOLATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
J
JFPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
K
KRSMOOTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
KVTABLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
L
LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
LETGO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
LETWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
LETWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
N
NFLOWFTB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
NPROPANTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
O
OILVINDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026
OPEN_ BASE_ MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
P
PREDEFINES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
PROPANTNAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
PROPANTTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
PVTGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
R
REACCONC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043
RECU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614
REPORTFILE / REPORTSCREEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
RESTARTDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

RFD_ WFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

ROCKAXES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
ROCKCONT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
ROCKSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135
ROCKSTRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
ROCKT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
RPTMAPD/RPTGRAPHD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1189
RPTMAPL/RPTGRAPHL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1193
RPTMAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144
RPTMAPT/RPTGRAPHT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1191
RUNCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1430
S
SALTPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
SALTTRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
SKIPOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1584
SKIPON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1586
SKIPTNAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1583
SPECHC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054
SPECHD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056
SPECHI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059
SPECHJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1060
SRSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138
STANDG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
STANDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
STHERMX2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
STORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
SURFDW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
T
TEMPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
TFORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
THCONMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
THCONT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
THERMEX2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
THERMEX3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
TNAVCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
TRACERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
TRACEROPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
TRMMULTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
TRMMULTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
TRMTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821

U
USERFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1616
V
VDEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
VFPCORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1330
VISCNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
VISGRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
W
WBHZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1470
WECONX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337
WELLTRACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1216
WFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1441
WFRACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444
WFRACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1447
WFRACPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1456
WFRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2089
WORK/IWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
WPIFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1466
WSEGCNTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1633
WSKFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468
WTEMPDEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1118
WWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299
Z
ZONES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682

18. Keyword definitions index MORE tNavigator-4.2
18 Keyword definitions index MORE

A
ACTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1973
AQCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1977
AQCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1978
AQCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1979
AQFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1981
AQUW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1982
ARRAy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2129
B
BASIc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1936
BHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2103
BHPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2107
BRANch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2134
C
CIJK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2127
CNAMe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1920
COMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2132
CONS (GRID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1983
CONS (INIT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2046
COORd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1974
CROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1971
CWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2121
D
DATE / READ / TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2115
DATUm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1963
DEFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1984
DELTa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2131
DEPTh / ZGRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1966
DPORo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1924
DPSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1985
DRAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2117
DREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2105
DWPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1927
DZMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1990
E
EFILe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2054
EFORm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2069
ENDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2063
ENDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2068
18. Keyword definitions index MORE 2169

ENDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2064
EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1925
EPSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1926
EQUA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1940
EQUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2044
EQUI / EQLN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1991
ETAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2058
ETUNe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1929
EUNIts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2073
F
F(DE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1949
F(PO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1992
FAUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1993
FCRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1995
FEQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1998
FIPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975
FKX / FKY / FKZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1996
FLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2099
FLUId . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1934
FMLX / FMLY / FMLZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1997
FMUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1994
FPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1999
FPVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1988
FREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2000
FREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2130
FSAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1986
FSWA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987
G
GGRT / GWRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2120
GOCX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2048
GOCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2049
GOPT / GGPT / GWPT / GLPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2113
GPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1930
GPVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1939
GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1959
GROU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2116
GVRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2125
H
HFILe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2065
HFORm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2071
HOIL / HGAS / HWAT / HLIQ / HRES / HBHP / HTHP / HWEF . . . . . . . . . . . . . . . . . . . 2095
HORI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1961

HOURS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2114
HTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2067
HUNIts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2074
I
IDATe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1918
IEQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2001
IMPLicit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1921
INCLude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1922
INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2041
INJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2080
INPUt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1914
INTE (FLUID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1950
INTE (GRID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2002
K
K_ X / K_ Y / K_ Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1970
KMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2122
KPTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2004
KRGO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1957
KRWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1956
KVPX / KVPY / KVPZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1942
KVSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1941
L
LAYE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2005
LEVJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2006
LGRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2007
LTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2081
M
MINDznet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2008
MINPv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1969
MODI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2009
MPGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1931
MULX / MULY / MULZ (MX / MY / MZ, M_ X / M_ Y / M_ Z, M-X / M-Y / M-Z,
MULTX / MULTY / MULTZ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2011
N
NNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2019
NTG / NTOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2020
O
OIT / GIT / WIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2110
OMGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1944
OMGB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945

OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1928
OPEN (RECU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2104
OPT / WPT / GPT / LPT / VPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2109
OPVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1943
OPVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1938
P
P-RE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2083
PARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2123
PBVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2042
PCSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2124
PERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2075
PINCh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2012
PLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2126
POROsity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1968
PORV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2013
PREX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2082
PRINt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1916
PROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2079
PROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1951
PVOL / RVOL / PVR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2014
PVTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1989
R
RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2053
RATI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2102
RECU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2052
RECY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2119
REFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1972
RELA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1954
REPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2021
RG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1932
RSVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2043
RVVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2045
S
SATNum / ROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1976
SCMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1923
SDATe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1919
SDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1947
SEPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2050
SGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2022
SGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2023
SGU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2024
SHUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2093

SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1962
SOGC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2025
SOWC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2026
SQUEeze . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2077
STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2094
STRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2112
SWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2029
SWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2028
SWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2027
T
T_ X / T_ Y / T_ Z (TX / TY / TZ, T-X / T-Y / T-Z) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2016
TEMPerature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1937
TFIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2056
THICkness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1967
THP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2101
THPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2108
TITLe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1915
TRAC (FLUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1952
TRAC (RECU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2135
TSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2038
TTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2062
TUBI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2096
U
UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1917
V
VARI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2018
VCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1948
VERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1960
VOLU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1946
VREP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2118
W
WATR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935
WEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2111
WELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2084
WETT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955
WFRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2087
WGPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2136
WMPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2137
WRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2138
WWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2086

X
X-DIrection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1964
XFLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2106
XKRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2030
XKRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2031
XKRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2032
XPCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2033
XPCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2034
Y
Y-DIrection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965
YKRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2035
Z
ZCORn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2036
ZVAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2037

REFERENCES tNavigator-4.2
19 The bibliography
References
[1] Aziz, K., Settari A., Petroleum reservoir simulation, Applied Science Publishers LTD, London,
1979.
[2] Ertekin, T., Abou-Kassem, J.H., King, G.R., Basic applied reservoir simulation. SPE Textbook
Series, Richardson, Texas, 2001.
[3] Stone, H. L., Probability Model for Estimating Three-Phase Relative Permeability. Trans AIME
(JPT), 249, p. 214-218, 1970.
[4] Stone, H. L., Estimation of Three-Phase Relative Permeability and Residual Oil Data.
Can.Pet.Tech., Vol 12, p. 53-61, 1973.
[5] Carter, R. D., Tracy, G. W., An Improved Method for Calculating Water Influx. Trans AIME
(JPT), 219, p. 58-60, 1960.
[6] Fetkovich, M. J., A Simplified Approach to Water Influx Calculations - Finite Aquifer Systems.
JPT, p. 814-828, July 1971.
[7] Tarek Ahmed, Reservoir Engineering Handbook. Third Edition, 2006.
[8] Jorge Javier Velarde Pereira Correlation of black oil properties at pressures below the bubble-
point. 1996.
[9] Ahmed T. Equation of State and PVT Analysis.
[10] Economides, Michael J. Unified Fracture Design. Orsa Press, Alvin, Texas, 2002.
[11] Khalid Aziz, George W. Govier, Pressure Drop In Wells Producing Oil And Gas. Journal of
Canadian Petroleum Technology, volume 11, July 1972.
[12] J. Orkiszewski, Predicting Two-Phase Pressure Drops in Vertical Pipe. Journal of Petroleum
Technology, volume 19, June 1967.
[13] Alton R. Hagedorn, Kermit E. Brown, Experimental Study of Pressure Gradients Occurring
During Continuous Two-Phase Flow in Small Diameter vertical Conduits. Journal of Petroleum
Technology, volume 17, April 1965.
[14] D.H. Beggs, J.P. Brill, A Study of Two-Phase Flow in Inclined Pipes. Journal of Petroleum
Technology, volume 25, May 1973.
[15] Hemanta Mukherjee, James P. Brill, Empirical Equations to Predict Flow Patterns in Two-Phase
Inclined Flow. International Journal of Multiphase Flow, volume 11, issue 3, May-June 1985.
[16] Nicholas Petalas, A Mechanistic Model for Stabilized Multiphase Flow in Pipes. Stanford Uni-
versity, 1997.
[17] http://www.fekete.ca/SAN/WebHelp/Piper/WebHelp/c-te-pressure.htm, Gray correlation section.
19. The bibliography 2175

REFERENCES tNavigator-4.2
[18] M.J. King, Mark Mansfield, Flow Simulation of Geologic Models. SPE Reservoir Eval. & Eng.,
Vol. 2, No. 4, August 1999.
[19] Perrys Chemical Engineers Handbook, pp. 2-306.
[20] J. L. M. Fernandes, Correlations for fast computation of thermodynamic properties of saturated

water and steam. International journal of energy research, vol. 19, pp. 507-514, 1995.
[21] L.E.Baker, SPE / DOE 17369.
[22] Fayers and Matthews, SPEJ April 1984, pp. 224-232.
[23] Karen Schou Pedersen, Peter L. Christensen Phase Behavior of Petroleum Reservoir Fluids,
Taylor & Francis Group 2006, pp. 197-206.
REFERENCES 2176

T Nav User Manual English

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

T Nav User Manual English

Diunggah oleh

Hak Cipta:

Format Tersedia

Reservoir Simulator

Press to open User Guide

2.14 Phase mass density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

2.29 Coal Bed Methane Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

3 Compositional model 117

4 Compositional thermal model with chemical reactions 121

4.27 Bulk volume of rock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

5 Mathematical model 166

6 VFP tables generation 208

6.3.4 Beggs & Brill correlation . . . . . . . . . . . . . . . . . . . . . . . . 229

8 tNavigator Console version 270

9 Data files 279

11 Input data format 301

11.4 Keywords syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

12 Keywords compatible with tNavigator and E100, E300 308

12.1.41 UDQPARAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

12.1.84 NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

12.2.1 GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463

12.2.44 SOLVDIRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515

12.2.87 CARFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575

12.3.26 OPERATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648

12.5.11 STANDG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700

12.6.28 SWLPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770

12.7.10 TRMMULTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818

12.10Asphaltene properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871

12.13.23 VCRITVIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920

12.14.7 KVTABTn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975

12.14.50 REACCONC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043

12.15.14 APIVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097

12.16.3 AQUCHWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153

12.18.22 COMPLUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247

12.18.65 WGORPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1340

13 Keywords compatible with tNavigator and IMEX, STARS, GEM 1647

13.3.29 TRANSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1687

13.5.5 PVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1732

13.5.48 VISVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1777

13.6.9 SWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1824

13.7.16 PRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1867

14 Keywords compatible with tNavigator and MORE 1912

14.1.6 SDATe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1919

14.4.4 SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1962

14.4.47 LGRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2007

14.6.3 EFILe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2054

14.6.46 DATE / READ / TIME . . . . . . . . . . . . . . . . . . . . . . . . . 2115

15 Keyword definitions index E100, E300 2139

16 Keyword definitions index IMEX, STARS, GEM 2158

17 Keyword definitions index RFD 2165

18 Keyword definitions index MORE 2169

19 The bibliography 2175

isothermic systems (black-oil or compositional) section 2;

thermal compositional model with chemical reactions section 4.

Requirements for RAM per core.

Eclipse (c) Schlumberger,

IMEX, STARS, GEM (c) Computer Modelling Group Ltd,

MORE (c) Roxar.

CMG IMEX keywords;

CMG STARS keywords;

CMG GEM keywords;

tNavigator simulator is subject to future development. Any feedback is appreciated.

2.1 Differential equations for black-oil model

Nc = Nc (t, x, y, z) (unknown) c = 1, . . . , nc overall molar density of any component.

SP = SP (t, x, y, z) (unknown) phase P, P = O, G,W saturation,

BP = BP (pP ) phase formation volume factor (known function) (see 2.9),